aboutsummaryrefslogtreecommitdiff
path: root/jsmond.rst
diff options
context:
space:
mode:
Diffstat (limited to 'jsmond.rst')
-rw-r--r--jsmond.rst6
1 files changed, 5 insertions, 1 deletions
diff --git a/jsmond.rst b/jsmond.rst
index ae4dbc6..0f875d3 100644
--- a/jsmond.rst
+++ b/jsmond.rst
@@ -44,7 +44,7 @@ doesn't do the right thing for you. In this case, only these devices
will be monitored (no search is done).
jsmond should be started from your **.xinitrc** or whatever X startup
-script your windowmanager or desktop environment uses. By default, it
+script your window manager or desktop environment uses. By default, it
will exit when the X server does. There's no PID file: use "pkill jsmond"
if you need to kill the daemon.
@@ -122,6 +122,10 @@ device name that doesn't happen to exist yet because its device hasn't
been plugged in yet. Try to avoid typos, if you really have to use device
names (better to autodetect).
+Normally once daemonized, jsmond is very robust. However, if something
+does go wrong, there's no way to find out what. Probably there should
+be a log file, or use syslog.
+
jsmond isn't portable. It only works on Linux, at least for now, for
three reasons: