aboutsummaryrefslogtreecommitdiff
path: root/jsmond.1
diff options
context:
space:
mode:
Diffstat (limited to 'jsmond.1')
-rw-r--r--jsmond.16
1 files changed, 5 insertions, 1 deletions
diff --git a/jsmond.1 b/jsmond.1
index a68c8e7..e496a3b 100644
--- a/jsmond.1
+++ b/jsmond.1
@@ -58,7 +58,7 @@ doesn\(aqt do the right thing for you. In this case, only these devices
will be monitored (no search is done).
.sp
jsmond should be started from your \fB\&.xinitrc\fP 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\(aqs no PID file: use "pkill jsmond"
if you need to kill the daemon.
.SH OPTIONS
@@ -139,6 +139,10 @@ device name that doesn\(aqt happen to exist yet because its device hasn\(aqt
been plugged in yet. Try to avoid typos, if you really have to use device
names (better to autodetect).
.sp
+Normally once daemonized, jsmond is very robust. However, if something
+does go wrong, there\(aqs no way to find out what. Probably there should
+be a log file, or use syslog.
+.sp
jsmond isn\(aqt portable. It only works on Linux, at least for now, for
three reasons:
.INDENT 0.0