[Zope-Checkins] CVS: Zope/doc - SIGNALS.txt:1.1.2.2

[Chris McDonough]

Update of /cvs-repository/Zope/doc
In directory cvs.zope.org:/tmp/cvs-serv31096

Modified Files:
      Tag: Zope-2_6-branch
	SIGNALS.txt 
Log Message:
Minor cleanups and STX-if-ication for inclusion into Zope Book.


=== Zope/doc/SIGNALS.txt 1.1.2.1 => 1.1.2.2 ===
--- Zope/doc/SIGNALS.txt:1.1.2.1	Thu Oct 10 09:38:11 2002
+++ Zope/doc/SIGNALS.txt	Thu Oct 10 10:27:58 2002
@@ -1,37 +1,35 @@
-Signals are a posix inter-process communications mechanism.
-If you are using Windows then this documentation is not
-for you.
-
-Zope responds to signals which are sent to the process id
-written to the file /path/to/var/Z2.pid. 
-
-    SIGHUP  - close open database connections and sockets,
-              then restart the server process. The common
-              idiom for restarting a Zope server is
-              kill -SIGHUP `cat /path/to/var/z2.pid`
-
-    SIGTERM - close open database connections and sockets,
-              then shut down. The default stop script uses
-              kill -SIGTERM `cat /path/to/var/Z2.pid`
-
-    SIGUSR2 - close and re-open all Zope log files (z2.log,
-              event log, detailed log.) The common idiom
-              after rotating Zope log files is
-              kill -SIGUSR2 `cat /path/to/var/z2.pid`
+Signals (POSIX only)
 
-    SIGINT  - same as SIGTERM
+  Signals are a POSIX inter-process communications mechanism.
+  If you are using Windows then this documentation does not apply.
+
+  Zope responds to signals which are sent to the process id
+  specified in the file 'ZOPE_HOME/var/Z2.pid'::
+
+    SIGHUP  - close open database connections, then restart the server
+              process. The common idiom for restarting a Zope server is:
 
+              kill -HUP `cat ZOPE_HOME/var/z2.pid`
 
+    SIGTERM - close open database connections then shut down. The common
+              idiom for shutting down Zope is:
 
-Exactly which process has its pid written to this file 
-depends on whether Zope is run under the management
-process. If using a management process (the default)
-then its pid is recorded here. Relevant signals sent to
-the management process are forwarded on to the server
-process. (Specifically, it forwards all those signals
-listed above, plus SIGQUIT and SIGUSR1)
-
-If not using a management process (-Z0 on the z2.py
-command line) then the server process records its own
-pid here.
+              kill -TERM `cat ZOPE_HOME/var/Z2.pid`
+
+    SIGINT  - same as SIGTERM
 
+    SIGUSR2 - close and re-open all Zope log files (z2.log, event log,
+              detailed log.) The common idiom after rotating Zope log files
+              is:
+
+              kill -USR2 `cat ZOPE_HOME var/z2.pid`
+
+  The process id written to the 'z2.pid' file depends on whether Zope
+  is run under the 'zdaemon' management process. If Zope is run under
+  a management process (as it is by default) then the pid of the
+  management process is recorded here.  Relevant signals sent to the
+  management process are forwarded on to the server process.
+  Specifically, it forwards all those signals listed above, plus
+  SIGQUIT and SIGUSR1.  If Zope is not using a management process (-Z0
+  on the z2.py command line), the server process records its own pid
+  into 'z2.pid', but all signals work the same way.