| |||||||||||||
|
| |||||||||||||
upstart as cron replacementupstart as cron replacementPosted Sep 1, 2006 1:27 UTC (Fri) by kh (subscriber, #19413)In reply to: upstart as cron replacement by smurf Parent article: What's happening at Ubuntu: from X.org updates to upstart
?? The decision which jobs to run would lie with the author of the job, not with upstart: you decide on the rules for your script, not cron or anybody else. You did not understand what I was trying to say, I am not comfortable with the idea of moving the logic for tests (such as "is the database server running?") from the sync (or whatever) script, where is currently resides, to the cron replacement (i.e. the update config (crontab?) file). And I do not understand how it is possible to do so with a terse language for the config file, and yet have update be aware of every different possible daemon, their states, the system states, & etc. That seems like a LOT of new features for cron.
(Log in to post comments)
No service-specific tests Posted Sep 1, 2006 7:28 UTC (Fri) by smurf (subscriber, #17840) [Link] The test upstart will do, using the mysql example, is not "can I connect to port 3306 and get a sensible reply", but "I have forked off/usr/sbin/mysqld and it hasn't died yet".
Testing for actual services isn't upstart's job; I agree that that makes no sense whatsoever. NB: I don't know how upstart is going to decide that a service has finished starting up. I assume it'll be something along the lines of "the startup script has exited but some of its children are still running" by default, but I haven't checked.
|
|
||||||||||||