[Erp5-report] r14210 - /erp5/trunk/utils/oood/start.py

[nobody at svn.erp5.org]

Author: bartek
Date: Wed Apr 25 02:12:42 2007
New Revision: 14210

URL: http://svn.erp5.org?rev=14210&view=rev
Log:
description shown on status screens (about threads and about pool status)

Modified:
    erp5/trunk/utils/oood/start.py

Modified: erp5/trunk/utils/oood/start.py
URL: http://svn.erp5.org/erp5/trunk/utils/oood/start.py?rev=14210&r1=14209&r2=14210&view=diff
==============================================================================
--- erp5/trunk/utils/oood/start.py (original)
+++ erp5/trunk/utils/oood/start.py Wed Apr 25 02:12:42 2007
@@ -309,9 +309,38 @@
       sys.exit(0)
     elif o in ("-s", "--status", "--stat"):
       showPoolStatus()
+      print """
+      This screen tells you about status and statistics of the oood server:
+      - how long has it been running
+      - how many times it was restarted ("emergency restart")
+      - how long has it been running since the last restart
+      - how many requests has it processed
+      Also, there is a list of workers in the pool, and some information about every worker:
+      - its index in the pool
+      - how long has it been running
+      - how many requests has it processed
+      - how long (in seconds) has it been processing the current file (if this value reaches
+        the instance_timeout set in config, the worker is killed and restarted)
+      - the (stripped) name of the file it is now processing
+      Sometimes the whole row is filled with "xxxx" marks - it means that this worker has died and this slot
+      in the pool is empty, so the server is running a smaller pool. If the pool size goes to zero, the whole
+      server is restarted.
+      """
       sys.exit(0)
     elif o in ("-r", "--threads", "--th"):
       showThreadingStatus()
+      print """
+      What you should see above is a list of currently running threads:
+      MainThread is the main server thread.
+      There is a number of threads which have no function or args, and which do not change;
+      their number should be equal to the number of OOo instances running, they are waiting for
+      OOo instances to terminate (die, crash, be killed) so that they do not become zombies.
+      There is also a threads whose id increases every two seconds - these are created
+      in response to the script you are currently looking at.
+      Other threads are being launched, started, stopped and terminated by dispatcher to wait for 
+      certain operations to complete, and to launch instance restart of emergency restart of the whole
+      server if these operations time out.
+      """
       sys.exit(0)
 
   # Exit on general error