[20:32] <yaaang> what's the precise connection between upstart and init.d/rc's? if i have an upstart conf in /etc/init/ with "start on runlevel [2345]" do i still need to create a symlink to /lib/init/upstart-job and run update-rc.d on that?
[20:32] <yaaang> i notice a bunch of services have presence in both directories, which is confusing
[22:27] <rgl> hello
[22:28] <rgl> for some reason, service mongrel2 status says "mongrel2 start/killed, process 12548
[22:28] <rgl> " but there is no process 12548 ... doing a service mongrel2 stop does not work either ... how can I "unstuck" upstart?
[23:56] <ashb> rgl: sounds like its forking. 'expect fork' stanza or something along thosel ines in the config
[23:56] <ashb> also check the log to make sure its not just respawning really fast then stopping
[23:57] <ion> Don’t add an ‘expect’ stanza unless you’re *absolutely* certain of the forking behavior of the main process. Otherwise you’ll confuse Upstart. A future release will have a better implementation of following forks.
[23:58] <rgl> ashb, I have respawn like in other upstart files (eg. the cron one). 
[23:58] <ashb> i was just guessing - my upstart knowledge is teeny
[23:58] <rgl> oh w8... respawn does not seem the same as fork!
[23:59] <rgl> err
[23:59] <ashb> yeah respawn says restart if it crashes/stops(?)
[23:59] <rgl> on the previous version ... I was using expect fork too. but it does not work either.