[00:02] how can i force upstart to forget about a PID and think it's truly stopped? (the actual process is long gone but upstart just won't give it up) [00:03] so far, rebooting seems to be the only way... and even then, it hangs during shutdown on the process and requires a power cycle [01:19] Hi, I am using upstart with the rails Foreman gem - https://gist.github.com/2582347 here is the error. Permission denied - /etc/init/my-app.conf (Errno::EACCES) === rioderel` is now known as rioderelfte [12:13] hey [12:13] jodh: there ? How could I make sure if there is no upstart job running, then "stop" does not terminate my post install script ? Shall I just check for the return value of "stop" ? [12:54] djszapi: I don't understand your question fully, but does this help: http://upstart.ubuntu.com/cookbook/#creating-a-systemv-service-that-communicates-with-upstart-ubuntu-specific [15:53] jodh: was talking about this: http://paste.kde.org/468068/ [15:56] djszapi: packages should generally call 'invoke-rc.d restart' which calls /lib/init/upstart-job and that "does the right thing" - only calls stop if the job is actually running. [15:58] jodh: I am currently achieving this: http://paste.kde.org/468074/ [16:00] jodh: why can that postinst script fail ? [16:13] jodh: what should I write instead ? [16:47] djszapi: it will immediately exit if 'stop' fails due to the '-e'. See your shells man page. [16:48] jodh: so what is the recommended way of doing this ? [17:04] djszapi: http://upstart.ubuntu.com/cookbook/#debugging-a-script-which-appears-to-be-behaving-oddly [17:05] jodh: I should not use -e ? [17:10] djszapi: upstart uses "sh -e", nothing you can do about that [17:11] but that paragraph explains how to suppress errors === alienth_ is now known as alienth