[15:12] Hi! Specs on wiki looks "mixed" with implemented and to be implemented things. Am I right? Then any other documentation? [15:37] The man pages [15:45] Well I was looking for something like Remnant's blog posts. [16:45] which blog posts? [16:46] for the current version, the manpages should document the "implemented things" [17:22] JanC: e.g. http://www.netsplit.com/2006/12/14/upstart-0-3/ [17:22] It's good to read about upstart in common. [17:23] But you're right, I missed man pages and they're really good. [17:27] hiho [17:28] eivanov: Upstart 0.3 is very old [17:28] I am currently trying to add a custom script to execute when switching to runlevel 0 [17:28] JanC: yeah, but I have to work with it, at least now. [17:28] eivanov: :-( [17:29] i can't seem to find an /etc/event.d , but rc?.d/ misses services, so i think i do have upstart installed, but where the heck? ubuntu 10.04 LTS [17:29] phil: upstart uses /etc/init/ now [17:31] as is documented in the manpage... [17:32] sorry, i see now [17:32] i'm familiar with the old style but didn't dig into linux that much since [17:33] if you need to change/add services, see 'man 5 init' for the new syntax [17:36] is there something like pre-stop? [17:36] Yes, pre-stop. [17:36] nice [17:45] is a change to a script in effect instantly? [18:22] 0.3.5 man pages are really poor :( [19:19] how can i make sure a script is executed very early in the shutdown process? [19:24] Why? [19:25] i asked first :P [19:26] i want to execute a custom script before a service shuts down [19:26] added it to the service in pre-stop but that does not seem to do the trick, probably because dependencies are not met any more [19:27] so if i could just do it first in a shutdown sequence it is solved [19:27] now you :P [19:28] pre-stop should be the right thing. What do you mean by dependencies not being met? [19:28] it's a python script, uses mysql db i.e. [19:29] so if mysql is shut down you know what happens [19:29] The job should have “stop on stopping mysql“ or however the mysql job is named. [19:34] thanks [19:36] “stop on foo” causes the stopping of your job to block the foo event.