[01:15] <niteowl> Hi. I'm using ubuntu 9.10 and just trying to add an upstart service which runs after all of the legacy init scripts. It doesn't seem to be executing though and there doesn't appear to be a way to enable boot logging for upstart.
[01:15] <niteowl> 'start on stopped rc[2345]' should do what I want, right?
[01:17] <niteowl> I have a description line, followed by start on stopped rc[2345] and then exec /usr/local/bin/myscript
[01:44] <JanC> are you sure you don't want "start on started rc[2345]" instead?
[01:47] <niteowl> I'm pretty sure I've tried that but I'll try it again now
[01:47] <niteowl> I just did a sanity check and 'start on startup' works.
[01:49] <niteowl> start on started didn't work either
[01:49] <niteowl> initctl list shows rc stop/waiting
[01:49] <niteowl> Is there any way to get boot logging?
[01:50] <niteowl> From some googling I did it doesn't look like it's supported right now
[01:50] <niteowl> I'm finding upstart incredibly irritating to deal with.
[01:51] <JanC> it's new (and is still worked on)
[01:53] <niteowl> I'm aware of that but if it's still so new why is it the default?
[01:54] <ion> There’s no rc2 job. There are events such as ‘runlevel 2’, which may be what you want.
[01:54] <ion> Look at the other jobs under /etc/init.
[02:04] <JanC> start on runlevel would start the job parallel with the legacy init scripts
[02:10] <JanC> I guess there should be an init.d script that runs after all other init.d scripts and then emits an event to signal that to upsatrt
[02:10] <niteowl> Hmmm. Well I tried start on stopped rc RUNLEVEL=[2345]
[02:10] <JanC> which is what a "task" does
[02:12] <JanC> hm, rc is a task, so it should be "started" after all init.d scripts are run?
[02:14] <niteowl> The description at the top of the rc task is: This task runs the old System V-style rc script when changing between runlevels
[02:14] <niteowl> Wouldn't that imply that it runs the /etc/init.d scripts
[02:14] <niteowl> so when it's finished doing that it's stopped
[02:14] <niteowl> which should be an event I can use in another task?
[02:15] <JanC> yeah, probably (the documentation could be more clear there  ;)
[02:17] <niteowl> I just wish I had some output to explain why it's not running
[02:17] <niteowl> (any output)
[02:18] <niteowl> Even a log of events and tasks being run
=== ev1 is now known as ev
=== Keybuk_ is now known as Keybuk
=== pocek_ is now known as pocek