[17:10] <marianogg9> hi guys, just a quick question. I need to start a job every time the vm is restarted, I've added "start on startup" to the script but it doesn't start when the vm starts
[17:10] <marianogg9> is there something I'm missing?
[17:13] <xnox> marianogg9: the job is in the VM? And what do you mean restarted - is it rebooted, or suspended/resumed?
[17:14] <xnox> or is the job on the host?
[17:15] <marianogg9> xnox: this upstart script is monitoring a lumberjack service (log shipping service). When the vm where it's located is rebooted or stop/started, it doesn't start automatically
[17:15] <xnox> marianogg9: can you pastebin the job?
[17:15] <marianogg9> sure
[17:16] <xnox> marianogg9: start on startup, might be way too early for it - no filesystems are mounted rw yet potentially.
[17:18] <marianogg9> xnox: https://gist.github.com/marianogg9/10024411
[17:18] <marianogg9> then which stanza is more suitable?
[17:22] <xnox> marianogg9: use : start on runlevel [2345]
[17:23] <marianogg9> instead of startup you mean?
[17:47] <FunnyLookinHat> Is there an event automatically emitted / generated upon completion of any upstart task?  i.e. I want to do something once cups.conf has run it's post-start script 
[17:47] <FunnyLookinHat> all I can think to do is edit cups.conf to emit a special event that I listen for and then try to work with that
[17:47] <FunnyLookinHat> but I don't want to edit that file  :)
[18:26] <FunnyLookinHat> Ah - you can just "start on stopped cups RESULT=ok"
[20:14] <xnox> FunnyLookinHat: yes, that =)
[20:15] <FunnyLookinHat> xnox, :)  I was getting a bit confused - what I really wanted was "start on started cups RESULT=ok" ... but same difference though
[20:15] <xnox> FunnyLookinHat: no need for result=ok in that case. "start on started cups" means cups got successfully started and is running.
[20:16] <xnox> FunnyLookinHat: if it fails to start "started" event is not emitted.
[20:16] <FunnyLookinHat> xnox, slick thx