On Sat, 2011-02-12 at 21:22 +0000, Mike Bianchi wrote:
> > > 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.
>
Ready or not its out there in RHEL and Ubuntu as well as other places.
>
> 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
On Sat, 2011-02-12 at 21:22 +0000, Mike Bianchi wrote:
> > > 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.
>
Ready or not its out there in RHEL and Ubuntu as well as other places.
>
> 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