Forks and watches multiple instances of a program in the same context (environment + fds) https://redmine.lighttpd.net/projects/multiwatch
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
When the --signal flag was enabled, multiwatch was sending the index of signal in the sig_actions array instead of the correct signal number. So, when multiwatch was told to send a SIGTERM, the application was actually being sent a SIGQUIT, which caused the application to coredump as ordered. The fix is to change the loop to return the signal number stored at the index.
|3 years ago|
|.gitignore||12 years ago|
|CMakeLists.txt||10 years ago|
|COPYING||12 years ago|
|Makefile.am||6 years ago|
|README.rst||8 years ago|
|autogen.sh||12 years ago|
|config.h.cmake||12 years ago|
|configure.ac||10 years ago|
|multiwatch.1||6 years ago|
|multiwatch.c||3 years ago|
Multiwatch forks multiple instance of one application and keeps them running;
it is made to be used with spawn-fcgi, so all forks share the same fastcgi
socket (no webserver restart needed if you increase/decrease the number of
forks), and it is easier than to setup multiple daemontool supervised instances.
Example for spawning two rails instances::
# run script
exec spawn-fcgi -n -s /tmp/fastcgi-rails.sock -u www-rails -U www-data -- /usr/bin/multiwatch -f 2 -- /home/rails/public/dispatch.fcgi
More details in the man page.
* glib >= 2.16.0 (http://www.gtk.org/)
* libev (http://software.schmorp.de/pkg/libev.html)
* cmake or autotools (for snapshots/releases the autotool generated files are included)
* snapshot/release with autotools::
* build from git: git://git.lighttpd.net/multiwatch.git
* with autotools::
* with cmake (should work with snapshots/releases too)::