[10:24] <judu> Hi
[10:25] <judu> How do I add my custom job to startup? I just put my .conf in /etc/init, then I tried to update-rc.d and I get an error saying that /etc/init.d/myjob does not exist…
[10:47] <jodh> judu: sounds like you need to use dh_installinit if you are packaging a new service for debian/ubuntu. If you are doing this "by hand", you'll need to manually create a link from /lib/init/upstart-job to /etc/init.d/$job (where $job is actually /etc/init/${job}.conf).
[11:00] <judu> Ok, thanks
[11:02] <judu> So, I did that, and ln -s /lib/init/upstart-job /etc/init.d/testjob, then update-rc.d testjob enable, and I get System start/stop links for /etc/init.d/testjob do not exist.
[11:02] <judu> Hum my bad.
[11:02] <judu> Why did I forget the start on startup?
[11:04] <judu> Hmm… I added the start on startup and stop on runlevel [06], but still the same message
[12:20] <xnox> jodh: there is no need for update-rc.d for upstart jobs.
[12:20] <xnox> =)
[12:20] <xnox> jodh: and in debian wheezy and ubuntu saucy and up, no need for symlink to upstart-job =)
[17:48] <crankharder> is there a way to stop all processes of a given config regardless of instance variables?
[23:17] <xnox> crankharder: you could itterate via dbus api, not sure if there is easy command line way to do so.
[23:18] <xnox> crankharder: you can see all instances in $ sudo initctl list, and iterrate and stop them via that with xargs -L 1 or something like that.
[23:40] <joshu> hi
[23:42] <joshu> I'm writing my third upstart script and this one is giving me a headache https://gist.github.com/anonymous/13679e11d60c86a2aff6
[23:43] <joshu> I can't get it to work properly and write the file to the user directory /home/test/brscan. If I replace setuid and chdir with exec su -c "/usr/bin/brscan-skey" test it work fine. However, with su -c the respawning doesn't work correctly.