Comment 296 for bug 554172

> > On Sat, Feb 12, 2011 at 02:15:20PM -0000, Brian J. Murrell wrote:
> > Any news on this bug? Is anyone trying to fix it?
> On Sat, 2011-02-12 at 12:11 +0000, Jens Schødt wrote:
> Yeah, IMHO, upstart was waaaaayyyy rushed into Ubuntu. ...

I agree.

The evidence strongly suggests that Upstart still is not ready for prime time.

So may I suggest, at the very least, /bin/init be give an detailed logging
function that announces _everything_ it does, and _why_, into syslog
with the _option_ of quieting it if someone sees the need to save the file
space. By "_everything_ it does" I mean not only starting and stopping.
I mean announcing that it is waiting on some event for some /etc/init/*.conf
stanza. Announcing every event that arrives and (if it can) from where.

As I see it the problem is that nobody can present clear evidence of why
their favorite start-up script is not performing as expected because you
have to go in and instrument (read "put print statements into") everything
that upstart touches. Then, if it doesn't touch something you have to
guess a probable cause, hack, and reboot.

This problem has a long history that looks like inattention out here in
user land.

The evidence is that it IS NOT FIXED .

And don't put it off as a kernel or somewhere else.
When Ubuntu does not work, it is Ubuntu that is not working.

And, if a fix still eludes you, put back an old fashioned /bin/init with the
old fashioned /etc/init.d/S??<startupscript> sequence,
at least as an option.

I am still on 8.04 because this is not fixed.

I also am looking to go straight Debian or elsewhere.