diff options
| -rw-r--r-- | jsmond.1 | 6 | ||||
| -rw-r--r-- | jsmond.html | 5 | ||||
| -rw-r--r-- | jsmond.rst | 6 |
3 files changed, 14 insertions, 3 deletions
@@ -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 diff --git a/jsmond.html b/jsmond.html index 29a9bdf..20608d9 100644 --- a/jsmond.html +++ b/jsmond.html @@ -401,7 +401,7 @@ you can pass one or more device names (or just numbers) if the default doesn't do the right thing for you. In this case, only these devices will be monitored (no search is done).</p> <p>jsmond should be started from your <strong>.xinitrc</strong> 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.</p> </div> @@ -487,6 +487,9 @@ or else fork() failed. No daemon will be running in this case.</p> 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).</p> +<p>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.</p> <p>jsmond isn't portable. It only works on Linux, at least for now, for three reasons:</p> <ul class="simple"> @@ -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: |