[17:32] hello. what do I do if upstart thinks a job is running when it's not? I can't restart it, "stop name" just hangs. [19:12] umonkey: if you mean a temporary fix, there is a script somewhere that forks until it has the PID that upstart thinks should exist [19:12] the real fix is to fix the job configuration and reboot, of course [19:23] The real fix is to fix Upstart’s fork tracking code. That’s in the pipeline somewhere. Poke Keybuk. :-P [19:23] ion: right, but that's not something most users can do ;) [19:23] http://heh.fi/tmp/workaround-upstart-snafu [19:23] workaround-upstart-snafu 12345, where 12345 is the pid Upstart thinks the job has. [19:24] and most jobs can be written to work with the current upstart [19:24] yeah