You should override this method when you subclass Daemon. # Check for a pidfile to see if the daemon already runs Programming in the UNIX Environment" for details (ISBN 0201563177)
Usage: subclass the Daemon class and override the run() methodĭef _init_(self, pidfile, stdin='/dev/null', stdout='/dev/null', stderr='/dev/null'):ĭo the UNIX double-fork magic, see Stevens' "Advanced Here's a nice class that is taken from here: #!/usr/bin/env python While if the script is added as a cron job, it will just trigger again. Unless there are additional reasons why you should make a daemon (in addition to trigger periodically), choose the other approach.Īlso, if you use daemonize with a loop and a crash happens, no one will check the mail after that (as pointed out by Ivan Nevostruev in comments to this answer). The Linux system paradigm is to let multiple simple tools interact and solve your problems. I wouldn't recommend you to choose 2., because you would be, in fact, repeating cron functionality. Yes, it will require a simple event loop (where your events are timer triggering, possibly, provided by sleep function). Use some kind of python approach (a library, for example) for your script to be able to daemonize itself. There is a variety of different cron daemons, but your GNU/Linux system should have it already installed. You add your script into a crontab or place a symlink to it into a special directory and the daemon handles the job of launching it in the background.
Cron is a common name for a GNU/Linux daemon that periodically launches scripts according to a schedule you set. Make a proper cron job that calls your script.
0 kommentar(er)
