From: <ps...@us...> - 2009-11-20 16:42:55
|
Revision: 1667 http://znc.svn.sourceforge.net/znc/?rev=1667&view=rev Author: psychon Date: 2009-11-20 16:42:44 +0000 (Fri, 20 Nov 2009) Log Message: ----------- Document the signals This adds the new SIGUSR1 handling to README and adds a section on SIGINT, SIGHUP and SIGUSR1 to znc's man page. Modified Paths: -------------- trunk/README trunk/man/znc.1 Modified: trunk/README =================================================================== --- trunk/README 2009-11-20 15:38:21 UTC (rev 1666) +++ trunk/README 2009-11-20 16:42:44 UTC (rev 1667) @@ -119,6 +119,11 @@ or you can login to znc and use /msg *status rehash +If you changed some settings while znc is running, a simple + pkill -SIGUSR1 znc +will make ZNC rewrite its config file. Alternatively you can use this: + /msg *status saveconfig + Writing own modules ------------------- Modified: trunk/man/znc.1 =================================================================== --- trunk/man/znc.1 2009-11-20 15:38:21 UTC (rev 1666) +++ trunk/man/znc.1 2009-11-20 16:42:44 UTC (rev 1667) @@ -79,6 +79,22 @@ .B znc uses. You need this for SSL. +.SH SIGNALS +This section explains how +.B znc +reacts to different signals: +.TP +.B SIGINT +Exit ZNC. This is equivalent to +.I /znc shutdown +.TP +.B SIGHUP +Reload znc.conf. This is equivalent to +.I /znc rehash +.TP +.B SIGUSR1 +Rewrite znc.conf. This is equivalent to +.I /znc saveconfig .SH FILES .TP .I /usr/local/share/znc/ This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site. |