[07:41] arekm: I think upstart has it's own fake implementation of halt/reboot that will send a mesasge to the rest of the system [08:15] keesj: it does that. init receives it but doesn't act properly [08:36] I guess you need to implement some shutdown strategy. I also use upstart on an embedded system [09:12] huh? the upstart should switch to runlevel 0, no "some" strategy required [09:13] but it doesn't do that if it gets _any_ env passed [17:18] arekm: that is only true is you use the backwards compatible scripts, upstart itself has no notion of runlevels , that is something from far awy in the past :p [17:55] Hi, I wanted to convert a few of my custom init scripts to Upstart jobs. Should these jobs go in /etc/event.d/ or /etc/init/jobs.d/ (which doesn't exist). The "getting started" page says the latter, but all my pre-installed jobs are in the former. Is there a difference between putting jobs in event.d vs jobs.d? === ssd71 is now known as ssd7 [18:31] keesj: I use scripts that are still supported by upstart [18:41] if that functionality is to be ignored/left buggy etc then I'll be sad :-/ (wanted to switch to upstart but can't use buggy stuff)