aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKevin O'Connor <kevin@koconnor.net>2019-02-03 17:41:57 -0500
committerKevin O'Connor <kevin@koconnor.net>2019-02-03 17:41:57 -0500
commit5b9ce328e59b25757c0c8872cdf97008d320eb3b (patch)
tree7529a6d44ce9117a481d401fc93c89506352196e
parentd088a7ca72d867197d819c5464d4e92244722654 (diff)
downloadkutter-5b9ce328e59b25757c0c8872cdf97008d320eb3b.tar.gz
kutter-5b9ce328e59b25757c0c8872cdf97008d320eb3b.tar.xz
kutter-5b9ce328e59b25757c0c8872cdf97008d320eb3b.zip
docs: Clarify FAQ item on running multiple instances of klippy
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
-rw-r--r--docs/FAQ.md6
1 files changed, 5 insertions, 1 deletions
diff --git a/docs/FAQ.md b/docs/FAQ.md
index 7d2a9932..d9585566 100644
--- a/docs/FAQ.md
+++ b/docs/FAQ.md
@@ -167,7 +167,11 @@ scripts ultimately cause the following Unix command to be run:
~/klippy-env/bin/python ~/klipper/klippy/klippy.py ~/printer.cfg -l /tmp/klippy.log
```
One can run multiple instances of the above command as long as each
-instance has its own printer config file and its own log file.
+instance has its own printer config file, its own log file, and its
+own pseudo-tty. For example:
+```
+~/klippy-env/bin/python ~/klipper/klippy/klippy.py ~/printer2.cfg -l /tmp/klippy2.log -I /tmp/printer2
+```
If you choose to do this, you will need to implement the necessary
start, stop, and installation scripts (if any). The