=== nikias_ is now known as nikias
[05:33] <SpamapS> slangasek: note I just pinged you in #debian-devel, but I'll ask here in case you ignore that one
[05:33] <SpamapS> vorlon: Hey, say I was totally insane and wanted to have a Debian box that used upstart.. 
[05:33] <SpamapS> slangasek: Hey, say I was totally insane and wanted to have a Debian box that used upstart.. 
[05:33] <SpamapS> slangasek: specifically a VM... how might I get that upstart to be verbose and spray things to the console?
[18:00] <SpamapS> slangasek: have you experienced any issues with startpar and upstart on sid?
[18:01] <SpamapS> slangasek: for me, rc RUNLEVEL=2 never returns when using startpar
[19:29] <slangasek> SpamapS: not specifically, though certainly there have been scattered reports of broken init scripts preventing startpar from doing the right thing
[19:29] <SpamapS> What seems to happen..
[19:29] <SpamapS> is startpar never returns
[19:29] <SpamapS> so rc RUNLEVEL=2 never finishes.. and tty1 never starts
[19:30] <SpamapS> slangasek: I have a really minimal set of software installed
[19:30] <SpamapS> slangasek: anyway, I'm filing a bug against sysvinit-utils .. upstart seems to be doing the right thing.. /etc/init.d/rc or startpar seems more likely as the problem.
[19:34] <slangasek> SpamapS: ok, well, I can't reproduce that in a basic sid VM here
[19:38] <SpamapS> slangasek: I'm building the VM myself using debootstrap and diskimage-builder (OpenStack image builder)
[19:38] <SpamapS> slangasek: so perhaps we're missing a dep somewhere?
[19:38] <slangasek> SpamapS: I don't see how a missing dep would cause any upstart-specific problems
[19:39] <slangasek> SpamapS: have you turned up the debugging on startpar, to see where it gets stuck?
[19:39] <slangasek> er... or does startpar have any debugging
[19:40] <SpamapS> I don't know how to do that :(
[19:40] <SpamapS> yeah I don't see anything in the manpage
[19:41] <SpamapS> slangasek: I can work around it by just diverting startpar...
[19:41] <SpamapS> slangasek: I'm using upstart specifically because I want upstarty things to keep working.. don't care much about speed of /etc/rc2.d/* :)
[19:42] <slangasek> SpamapS: hah - so I just dist-upgraded my vm, pulling in new versions of udev and ifupdown, and the VM hasn't come back up
[19:42] <SpamapS> slangasek: could it be a bug in the cloud-init packages? I see that cloud-init ships /etc/init/cloud-config.conf _and_ I have /etc/rc2.d/S03cloud-config
[19:43] <slangasek> SpamapS: diverting startpar doesn't work, upstart relies on startpar integration to force skipping of init scripts that duplicate upstart jobs
[19:43] <SpamapS> slangasek: mine dies after cron says it started
[19:45] <SpamapS> slangasek: so it 'works' but not really :)
[19:45] <slangasek> SpamapS: it 'works' except that it doesn't work after I update, so something changed in sid recently
[19:46] <SpamapS> slangasek: ok so it is normal to have an S03cloud-config and /etc/init/cloud-config.conf ?
[19:46] <slangasek> SpamapS: yep
[19:50] <slangasek> SpamapS: ah, my boot failure is unrelated, EC2 console shows that the kernel config explodeded :P
[19:56] <SpamapS> slangasek: one other problem I'm having is that I"m not able to just add --verbose to kernel command line and get lots of init: stuff on console
[20:18] <SpamapS> slangasek: startpar appears to only have debugging printing stuff if you compile with -DDEBUG