Upstart config file generation

Scott James Remnant scott at netsplit.com
Wed May 4 00:26:12 UTC 2011


On Sun, May 1, 2011 at 12:17 PM, Clint Byrum <clint at ubuntu.com> wrote:

> > If the backend starts before mysql is available then it will fail, and
> > upstart does have an opportunity to retry. No harm done then. Not ideal
> > either, because this attempt will have needlessly slowed the boot
> > procedure down. So why not put the dependency in the default (and
> > static) upstart configuration file? Because in the general case the
> > database need not reside on the same server as the backend (e.g. in the
> > case of a slave backend).
>
> I'm working on a new wait-for-state.conf (which I hope to upload this
> coming week to Oneiric, and will submit upstream for inclusion) which
> will make it this easy:
>
> if [ -x /usr/sbin/mysqld ] && [ -f /etc/init/mysql.conf ] ; then
>  start wait-for-state WAIT_FOR=mysql WAIT_STATE=started WAITER=mythtv
> WAIT_FOREVER=1
> fi
>
> I'm not sure how this is different from a flexible "on" ?

Scott
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/upstart-devel/attachments/20110503/088909ba/attachment.html>


More information about the upstart-devel mailing list