=== erkules_ is now known as erkules [16:02] jodh, xnox: hi, so I assume you've seen these build failures on trunk and that someone's working on sorting them out? [16:04] slangasek: that one needs a fix in lp:ubuntu/upstart [16:04] yeah, it was fixed for distcheck target, but not in the ubuntu-branch compile. [16:05] ok - so is that something we wait to fix until we're released and ready to upload to saucy? [16:07] the test_libupstart failure looks like it's a no-dbus-in-chroot issue. [16:07] slangasek: pushed a fix, and requested a new ppa build. [16:08] xnox: cool, thanks [16:09] slangasek: well at the moment I think everything is ready for 1.9 upstream release, but then further work will be needed to merge up 1.9 into lp:ubuntu/upstart. [16:09] ack [16:09] that later will also require additional patches from mdsleur [16:11] xnox: your fix is for the abi-check right? we may as well resolve the dbus/chroot issue before putting a release out tomorrow I think. [16:12] jodh: what's the issue around dbus/chroot? [16:12] jodh: if something needs dbus, simply wrap the whole command/environment with "dbus-launch -- " and that's it. [16:12] xnox: I thought we were all taking about: https://launchpadlibrarian.net/143474336/buildlog_ubuntu-raring-amd64.upstart_1.8%2Bdaily%2B1489%2B1444%2B201306261447~raring1_FAILEDTOBUILD.txt.gz but seemingly not :) [16:14] xnox: no - that won't work as dbus isn't configured in the chroots. [16:15] xnox: see in_chroot() and dbus_configured() in test_initctl.c. [16:16] so, really, we need to fix test_libupstart() to handle being run from within a chroot. Technically, that test is flawed as it assumes it's already running on a system with upstart - it should really spawn its own instance. [16:46] I have /etc/init/aolserver.conf http://bpaste.net/show/fDLGOSF3dfG7X6RTyGkk/ but, because there's nothing running in the foreground, I can't stop/restart it. What's a better approach to starting multiple services? [16:52] magmatt: I think you should be looking at 'instance': http://upstart.ubuntu.com/cookbook/#instance [16:52] magmatt: the examples in the cookbook are a little basic, but this example might be more useful... [16:53] magmatt: worker.conf: http://paste.ubuntu.com/5802034/ [16:53] magmatt: workers.conf: http://paste.ubuntu.com/5802036/ [16:54] okay, thank you jodh. I'll have a go at that [16:56] jodh: if one of the stop worker commands fails (in workers.conf) will it not continue to the others? [16:57] magmatt: if you want it to: change 'stop worker id=$inst' to 'stop worker id=$inst || :'. [17:27] jodh: how do I get `initctl status workers` to work? Here's what I'm seeing: http://paste.ubuntu.com/5802108/ [17:30] would it be silly to do: script while true; do done; end script? [17:31] or maybe with a long sleep in there [17:57] magmatt: maybe just do "initctl list|grep aol" :) === crank_ is now known as crank === crank is now known as crank_ === crank_ is now known as crank === crank is now known as crank_ === crank_ is now known as crank