On Wed, 2009-06-17 at 09:53 -0700, Daniel L. Miller wrote: > Scott James Remnant wrote: > >> There as probably much more required methods "on_start on_event > >> on_starting on_failed_dependency ..." > >> > >> > > "Failed dependency" is an interesting one; Upstart doesn't really > > process jobs in that way - a job simply stays dormant all the time its > > while condition isn't satisfied. > > > > The only time you'd get a "failed to start due to a while condition" is > > if, as a sysadmin, you ran "start JOB" manually -- this is communicated > > back as an error to the start command, other jobs on the system don't > > need to know about it. > > > Perhaps I'm missing something (probably). I'm basing the following on > the assumption that jobs like "starting the mailserver", which happen > "upon startup after networking initialized" magically happen by Upstart > parsing the configs. > > As a syadmin, if a machine is rebooted, and various processes that are > supposed to startup DON'T - that's important information! My particular > example is a bad one - cuz without mail services or networking its kind > of hard to e-mail the sysadmin - but do you follow where I'm going? > 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 -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
-- upstart-devel mailing list upstart-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
