[10:36] <muh-die-kuh> hi
[10:37] <muh-die-kuh> is it possible to use upstart as a wrapper around a script which provides "$foobar start" "$foobar status" and "$foobar stop"? if so, do you got any hint on what to google for?
[10:45] <xnox> muh-die-kuh: not really no. just use normal init.d script instead - one can mix & match those under upstart.
[11:03] <muh-die-kuh> xnox: okay, thanks
[11:04] <muh-die-kuh> xnox: but there's no layer that provides access to init.d scripts using upstarts "start" & "stop" commands, right?
[11:06] <xnox> muh-die-kuh: $ sudo service NAME [start|stop|status|restart]
[11:06] <xnox> muh-die-kuh: works for all - upstart jobs and init.d scripts alike
[11:07] <muh-die-kuh> xnox: awesome, thanks :)
[11:07] <xnox> muh-die-kuh: but you are correct, upstart native commands (start / stop / initctl ....) only work against upstart job files.
[17:26] <SpamapS> hm, is there a known bug in upstart where if you have   console=tty0 console=ttyS0 it does not fall back to tty0 if ttyS0 is unavailable?
[17:27] <SpamapS> Getting problems in a 13.04 VM that has no serial device.. some programs have no valid console.
[17:27] <SpamapS> (like, cloud-init)
[17:37] <xnox> SpamapS: i think only one of those values is used, not both / no priority.
[17:37] <xnox> i think jodh was looking into that, but it looks like he is EOD.
[18:14] <SpamapS> I'll file a bug with my findings, which are shallow but maybe they can help
[18:19] <SpamapS> hrm, upstart just consumes /dev/console ... 
[18:20] <SpamapS> ok, upstart is off the hook I think