why not use systemd to manage the daemon? On Wed, May 03, 2017 at 07:21:24PM -0400, jonathan vanasco wrote:
We have a few twisted daemons running on a linux machine under Supervisord as the process manager. Unfortunately, Supervisord is missing a feature that is pretty critical to our needs, so must be replaced with something that supports it -- the feature is the ability to persist state across reboots.
We've run into a situation more than once where we "stop" a Twisted service that caused issues, begun to triage it, and then the machine hits a reboot which causes the broken service to start up again and re-corrupts the data. The only way to maintain a "stop" across reboots in Supervisor is to "stop", then edit the config files so it doesn't start up again. If someone remembers to shut things off this way, they often forget to turn them back on again. We're at the point where using supervisor in our stack has caused more problems than conveniences.
Is anyone deploying their twisted services with something other than Supervisor? If so, I'd love to know.
_______________________________________________ Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python