2 ms·
> We run both nginx and unicorn through daemontools. Both have options to prevent daemonization. How are you able to do hot-reloads without daemonizing the mas
by otterley 11y ago
> We run both nginx and unicorn through daemontools. Both have options to prevent daemonization.
How are you able to do hot-reloads without daemonizing the master process? Or have you simply chosen to sacrifice this feature?
- scurvy 11y agoHot reload? Like a config reload? Just send the master process a HUP.
- otterley 11y agoThat can't possibly work correctly with runsv, given the way in which Unicorn performs configuration reloads. Eventually the original process that runsv forked will die, and runsv will try to restart it and fail (because the original process launched a new generation that continues to listen to the socket). Then 'sv stop' will fail to work because the new generation of master and workers isn't under runsv's supervision anymore.
- scurvy 11y agonginx doesn't die. It just reloads the config file and applies the changes. I can't remember what Unicorn does because we almost never change its config. Also, we're using daemontools not runit.