Added docs for new signal handling functions.

Jeremy.
(This used to be commit 24fb57e7507338845c2075dbd6d86922b3f028ed)

diff --git a/docs/manpages/nmbd.8 b/docs/manpages/nmbd.8
index ce530eb62094f2b2abf31e75594e5360a3931547..639b4472f07eb93face543540009cfa7a6279fb1 100644 (file)
--- a/docs/manpages/nmbd.8
+++ b/docs/manpages/nmbd.8
@@ -216,6 +216,17 @@ See
 .BR smb.conf (5)
 for more information.
 .RE
+.SH SIGNALS
+
+In version 1.9.18 and above, nmbd will accept SIGHUP, which will cause it to dump out
+it's namelists into the file namelist.debug in the SAMBA/var/locks directory. This
+will also cause nmbd to dump out it's server database in the log.nmb file.
+Also new in version 1.9.18 and above is the ability to raise the debug log
+level of nmbd by sending it a SIGUSR1 (kill -USR1 <nmbd-pid>) and to lower
+the nmbd log level by sending it a SIGUSR2 (kill -USR2 <nmbd-pid>). This
+is to allow transient problems to be diagnosed, whilst still running at
+a normally low log level.
+
 .SH VERSION
 
 This man page is (mostly) correct for version 1.9.16 of the Samba

diff --git a/docs/manpages/smbd.8 b/docs/manpages/smbd.8
index f7ef71bd2fff48705977c687a7b9ef9319ec7707..3e5ecc35232d2ddcfd00d36099fef404f6031114 100644 (file)
--- a/docs/manpages/smbd.8
+++ b/docs/manpages/smbd.8
@@ -414,6 +414,21 @@ creation of this man page the source code is still too fluid to warrant
 describing each and every diagnostic. At this stage your best bet is still
 to grep the source code and inspect the conditions that gave rise to the 
 diagnostics you are seeing.
+
+.SH SIGNALS
+
+In version 1.9.18 and above the debug log level of smbd may be raised 
+by sending it a SIGUSR1 (kill -USR1 <smbd-pid>) and lowered by sending 
+it a SIGUSR2 (kill -USR2 <smbd-pid>). This is to allow transient problems
+to be diagnosed, whilst still running at a normally low log level.
+
+Note that as the signal handlers send a debug write, they are not
+re-entrant in smbd. This you should wait until smbd is in a state of
+waiting for an incoming smb before issuing them. It is possible to
+make the signal handlers safe by un-blocking the signals before the
+select call and re-blocking them after, however this would affect
+performance.
+
 .SH BUGS
 None known.
 .SH CREDITS