On 06/17/2009 03:13 PM, Scott James Remnant wrote: > Yes, I do follow. > > This kind of "boot essential" job has been speculated for a while, but > no design for it has come forwards. > > Upstart's design does inherently mean that services may simply not be > started, and that's not considered an error condition. > > Scott >
The right way IMHO is to have a service/state called "system_normal" or what have you, which depends on everything that should be running every day. When that service is not running, there's a problem. If we have cron functionality and inverted dependencies, we have everything we need: task 1m after startup when not system_normal exec /usr/local/bin/do_email_sysadmin.sh -- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
