/srv/irclogs.ubuntu.com/2013/07/13/#upstart.txt

cpickI'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
cpickhttp://upstart.ubuntu.com/cookbook indicates that I should be able to set upstart to log-priority debug16:22
cpickBut after doing that I don't see any init trace in /var/log/syslog or any other file I can find.16:23
cpickI'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:24
xnoxcpick: $ dmesg16:59
xnoxcpick: grep init /var/log/kern.log 17:00
xnoxcpick: is upstart logging visible in one of the above two places?17:00
cpickYeah, nothing out of init in /var/log/kern.log eithier.17:01
cpickNo17:01
cpickI lied17:01
cpicksorry17:01
cpickdmesg does include init: trace17:01
cpickExcellent, thank you.17:01
cpickI thought upstart was supposed to switch from the kernel buffer to syslog as soon as syslog was up?17:02
xnoxcpick: good point. let me file a bug, to check up on it.17:03
cpickIt turned out the root cause of the problem I was trying to debug was: https://bugs.launchpad.net/upstart/+bug/56828818:43
cpickA frustrating waste of time.18:44
=== erkules_ is now known as erkules
xnoxcpick: right, sad. I'm confused why that patch was not taken into upstart.20:28

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!