=== cort [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk]  has joined #upstart
=== wasabi [n=wasabi@ubuntu/member/wasabi]  has joined #upstart
=== cort [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk]  has joined #upstart
=== cort [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk]  has joined #upstart
=== AlexExtreme [n=AlexExtr@frugalware/developer/AlexExtreme]  has joined #upstart
=== ion_ finally got around to setting jabberd back up. ion@heh.fi
=== Md [i=md@freenode/staff/md]  has joined #upstart
=== wil_syd [n=chatzill@c211-30-149-97.rivrw4.nsw.optusnet.com.au]  has joined #upstart
=== wil_syd [n=chatzill@c211-30-149-97.rivrw4.nsw.optusnet.com.au]  has joined #upstart
[12:36] <wil_syd> Whats a general purpose shutdown event ? 
[12:37] <AlexExtreme> the shutdown/halt/reboot utils will emit a runlevel event
[12:37] <wil_syd> like the opposite of start on startup
[12:37] <AlexExtreme> 'runlevel 0' for shutdown and 'runlevel 6' for reboot
[12:39] <wil_syd> ok.. I've got mt-daapd starting at startup. Can you have multiple stop ats ?
[12:40] <AlexExtreme> yes
[12:40] <wil_syd> ok.. thanks
[12:42] <wil_syd> oh.. should have been mutiple stop ons :)
[12:42] <AlexExtreme> yes ;)
=== juergbi [n=juerg@80-219-17-127.dclient.hispeed.ch]  has joined #upstart
=== j_ack [n=rudi@p508da888.dip0.t-ipconnect.de]  has joined #upstart
=== crazy [n=crazy@frugalware/developer/crazy]  has joined #upstart
=== Md [i=md@freenode/staff/md]  has joined #upstart
=== sadleder [n=sadleder@p50813DA7.dip0.t-ipconnect.de]  has joined #upstart
=== sadleder [n=sadleder@p50813DA7.dip0.t-ipconnect.de]  has left #upstart [] 
=== Md [i=md@freenode/staff/md]  has joined #upstart
=== mbiebl [n=michael@e180070135.adsl.alicedsl.de]  has joined #upstart
=== int0x0c [n=ben@161.253.47.113]  has joined #upstart
=== j_ack [n=rudi@p508da888.dip0.t-ipconnect.de]  has joined #upstart
=== mbiebl [n=michael@e180070135.adsl.alicedsl.de]  has joined #upstart
=== Md [i=md@freenode/staff/md]  has joined #upstart
=== phlaegel [n=phlaegel@S01060016b619a773.ok.shawcable.net]  has joined #upstart
[10:43] <phlaegel> hi, I'm trying to get upstart to handle my mythfrontend the way I used do it in /etc/inittab (details at http://www.mythtv.org/wiki/index.php/Frontend_Auto_Login), and I'm not sure it's possible yet.
[10:45] <phlaegel> I've got it mostly working (it starts the frontend, and restarts it if it crashes), but on boot it starts too early (before the mythtv-backend startup).
[10:46] <phlaegel> Would adding something like 'initctl emit mythtv-started' to the mythtv-backend init script be a way to get it working?
[10:46] <phlaegel> (and then making the mythfrontend job start on that event...)
[10:46] <AlexExtreme> yes, that would work
[10:49] <phlaegel> ok, I'll give that a shot... just wanted to see if that was a good way, or if there was something better. thanks
=== wasabi [n=wasabi@ubuntu/member/wasabi]  has joined #upstart
=== wasabi_ [n=jhaltom@ubuntu/member/wasabi]  has joined #upstart
=== j_ack [n=rudi@p508DACED.dip0.t-ipconnect.de]  has joined #upstart
=== sadleder [n=sadleder@p50813DA7.dip0.t-ipconnect.de]  has joined #upstart
=== sadleder [n=sadleder@p50813DA7.dip0.t-ipconnect.de]  has left #upstart []