Theseus007

Untitled

Feb 13th, 2015
225
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.29 KB | None | 0 0
  1. Master subprocess watcher.
  2.  
  3. Start and watch the configured runners and ensure that they stay alive and
  4. kicking. Each runner is forked and exec'd in turn, with the master waiting on
  5. their process ids. When it detects a child runner has exited, it may restart
  6. it.
  7.  
  8. The runners respond to SIGINT, SIGTERM, SIGUSR1 and SIGHUP. SIGINT, SIGTERM
  9. and SIGUSR1 all cause a runner to exit cleanly. The master will restart
  10. runners that have exited due to a SIGUSR1 or some kind of other exit condition
  11. (say because of an uncaught exception). SIGHUP causes the master and the
  12. runners to close their log files, and reopen then upon the next printed
  13. message.
  14.  
  15. The master also responds to SIGINT, SIGTERM, SIGUSR1 and SIGHUP, which it
  16. simply passes on to the runners. Note that the master will close and reopen
  17. its own log files on receipt of a SIGHUP. The master also leaves its own
  18. process id in the file `data/master.pid` but you normally don't need to use
  19. this pid directly.
  20.  
  21. master: error: The master lock could not be acquired, because it appears as if some process
  22. on some other host may have acquired it. We can't test for stale locks across
  23. host boundaries, so you'll have to clean this up manually.
  24.  
  25. Lock file: /home/cce/repo/mailman/var/locks/master.lck
  26. Lock host: linux-35.local
  27.  
  28. Exiting.
Advertisement
Add Comment
Please, Sign In to add comment