[02:17] <blueyed> I have upgraded a Hardy system to Lucid, but now upstart/init fails to boot through: the system is quite borked and I'm currently using the debian testing openvz kernel. this is where it hangs currently: http://i.imgur.com/htTVL.png
[02:18] <blueyed> it was hanging at bridge-network-interfaces before, then I removed this.. http://i.imgur.com/mkBjz.png before
[02:18] <blueyed> s/before$//
[02:30] <blueyed> upstart is in debian, but not essential as with ubuntu - it gets removed now because of the "hostname" package (I am upgrading to testing now, trying to fix the boot failure this way).
[06:36] <synthead> can I use multiple exec lines in an upstart config?
[06:36] <synthead> I need to daemonise two scripts but have upstart manage it
[06:37] <ion> Two daemons, two things to supervise, two jobs.
[06:37] <synthead> okay :)  will write another config
[18:13] <cwb> I'm trying to write a simple upstart job (for puppetd); it starts fine but if I try to stop it I get: "stop: Unknown instance:" That means nothing at all to me -- could anyone give me a hint where I should start looking?
[18:55] <sadmac> cwb: sounds like its already stopped, or you have puppetd set up as a job that can be started multiple times and you didn't say /which/ puppetd you meant.
[21:00] <plautrba> or you need export fork|daemon  if puppetd is deamonized
[21:00] <plautrba> *expect
[22:12] <cwb> plautrba: I think you're right that it's got something to do with that, but upstart still didn't seem to figure out what the pid turned out to be (and pid file .. didn't seem to work); not worth it for me right now, I'm going to stick with init.d I think.