Hi there, and thanks for the taking the time to write the mail. From
what I can tell, there's no actual bug you are reporting here, but
merely asking about the mechanism by which Upstart can determine that a
daemon is "ready". I'll mark this report out as "Invalid" for lack of a
better status to put it into
This varies from daemon to daemon, the most common is through use of
"expect fork" as with e.g. /etc/init/dbus.conf or "expect daemon" as
with e.g. /etc/init/mountall.conf - but these do assume that the daemon
is ready when it forks - while common this isn't always true. For
example this doesn't work for Plymouth, and bug #530779 covers that
particular case.
Other mechanisms for determining readiness are certainly on the "To do"
list for Upstart - if there are particular cases you're aware of, it
would certainly help to know about them.
Also if there are particular problems with daemons that have already
been converted, please do open bugs on those.
Thanks
** Package changed: ureadahead (Ubuntu) => upstart (Ubuntu)
** Changed in: upstart (Ubuntu)
Status: New => Won't Fix
** Changed in: upstart (Ubuntu)
Status: Won't Fix => Invalid
--
Problems with startup order when using upstart-job and ureadahead
https://bugs.launchpad.net/bugs/503334
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
