[16:22] <cpick> I'm running precise 12.04.2 amd64 with upstart 1.5-0ubuntu7.2 and I'm having trouble debugging the upstart scripts I'm writing.
[16:22] <cpick> http://upstart.ubuntu.com/cookbook indicates that I should be able to set upstart to log-priority debug
[16:23] <cpick> But after doing that I don't see any init trace in /var/log/syslog or any other file I can find.
[16:24] <cpick> I've tried setting it with both `sudo initctl log-priority debug` and by adding --debug to the kernel's boot options, using either method I've verified that it worked by running `sudo initctl log-priority` and seeing it's set to "debug".
[16:59] <xnox> cpick: $ dmesg
[17:00] <xnox> cpick: grep init /var/log/kern.log 
[17:00] <xnox> cpick: is upstart logging visible in one of the above two places?
[17:01] <cpick> Yeah, nothing out of init in /var/log/kern.log eithier.
[17:01] <cpick> No
[17:01] <cpick> I lied
[17:01] <cpick> sorry
[17:01] <cpick> dmesg does include init: trace
[17:01] <cpick> Excellent, thank you.
[17:02] <cpick> I thought upstart was supposed to switch from the kernel buffer to syslog as soon as syslog was up?
[17:03] <xnox> cpick: good point. let me file a bug, to check up on it.
[18:43] <cpick> It turned out the root cause of the problem I was trying to debug was: https://bugs.launchpad.net/upstart/+bug/568288
[18:44] <cpick> A frustrating waste of time.
[20:28] <xnox> cpick: right, sad. I'm confused why that patch was not taken into upstart.