[05:55] <Grivvel> Hello! I'm having an issue where upstart seems to be respawning my process if it shuts down during the pre-stop script. As far as I can tell from the documentation, that isn't intended. Does anyone know what might be causing it?
[06:08] <Grivvel> Aha, nevermind. It looks like this is already a documented bug https://bugs.launchpad.net/upstart/+bug/568288 . But it looks like there are workarounds :)
[06:18] <Sargun> Is there a good way to manipulate user upstart jobs from system upstart jobs?
[07:04] <xnox> Sargun: no, not really, you could drop/edit new jobs in one of the "user upstart job" locations - e.g. /etc/xdg/upstart/
[07:05] <xnox> Sargun: and system jobs can send events that user upstart jobs notice.
[07:05] <xnox> Sargun: but you wouldn't be able to start/stop/status user upstart jobs from within system one.
[07:34] <Sargun> Hm
[07:49] <xnox> Sargun: what do you want to do & why? =)
[07:49] <xnox> Sargun: sudo -u foo start bar
[07:50] <xnox> should work.
[07:50] <xnox> ;-)
[13:18]  * trapni waves
[13:28] <trapni> Hey. As of 6.13.2, I'm having a worker.init upstart file that spawnes a worker with a given $ID, then I have a generic workers.init that spawns all workers with their given ID, just like in the cookbook. Now, however, I want to globally restart them without writing the loop everytime again, just by `initctl restart workers` - but that doesn't seem possible, is it ?