=== Starting logfile irclogs/upstart.log
=== ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog]  has joined #upstart
=== Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo
=== Topic (#upstart): set by Md at Sun May  6 19:59:46 2007
=== crazy [n=crazy@frugalware/developer/crazy]  has joined #upstart
=== AlexExtreme [n=AlexExtr@frugalware/developer/AlexExtreme]  has joined #upstart
=== Md [i=md@freenode/staff/md]  has joined #upstart
=== phoenix24 [i=rsvi@ns37986.ovh.net]  has joined #upstart
=== phoenix24_ [i=htvq@ns37986.ovh.net]  has joined #upstart
=== Keybuk [n=scott@quest.netsplit.com]  has joined #upstart
=== razialx [n=razialx@adsl-70-228-95-46.dsl.akrnoh.ameritech.net]  has joined #upstart
[02:23] <razialx> hello again. I was wondering if someone would help me. I am trying to write a job that will catch the event of a network interface coming up. I am not sure how to get the event to emit, without using initctl. 
[02:24] <Keybuk> razialx: hello
[02:24] <razialx> I suppose I assumed that an event would be emitted automatically 
[02:24] <Keybuk> initctl is the standard method to emit events
[02:24] <razialx> ok, so should i add an initctl command to the eth1_up script ?
[02:24] <Keybuk> if the monitoring software is a daemon, it may prefer to link directly with libupstart rather than fork()/exec()ing initctl, but the effect is the same
[02:24] <Keybuk> yes
[02:24] <razialx> I just want to be sure that I am doing things correctly :)
[02:25] <razialx> thank you keybuk 
[02:25] <Keybuk> the only events Upstart generates itself are for "startup", and for events informing you of a job state change
[02:25] <razialx> ah, ok. 
[02:25] <Keybuk> events for things like network cards, interfaces, devices, etc. are expected to be emitted by other processes using initctl or libupstart
=== Amaranth [n=travis@ubuntu/member/Amaranth]  has joined #upstart
[02:26] <razialx> that is good to know. 
[02:27] <razialx> thank you, i should have what i need now. 
=== razialx [n=razialx@adsl-70-228-95-46.dsl.akrnoh.ameritech.net]  has left #upstart [] 
=== juergbi [n=juerg@80-219-19-183.dclient.hispeed.ch]  has joined #upstart
[02:33] <Keybuk> the dbus service activation threads are amusing me
[02:33] <Keybuk> I hadn't, until now, realised how heavily nih Fedora are
[02:33] <Keybuk> and coming from me, that's a big thing
=== tale [n=tale@207.235.54.1]  has joined #upstart
=== tck [n=tux@78.16.8.120]  has joined #upstart
=== Trevelyan is now known as Trevelyan`
=== AlexExtreme [n=AlexExtr@frugalware/developer/AlexExtreme]  has joined #upstart
=== AlexExtreme [n=AlexExtr@frugalware/developer/AlexExtreme]  has joined #upstart
[05:16] <Nilsy> nih ?
[05:56] <thom> not invented here
=== tck [n=tck@194.125.76.126]  has joined #upstart
=== phoenix24 [i=vervgo@ns37986.ovh.net]  has joined #upstart
=== tck [n=tck@194.125.76.126]  has joined #upstart
[07:13] <Nilsy> oh ok
=== phoenix24_ [i=meqoedu@ns37986.ovh.net]  has joined #upstart
=== phoenix24_ is now known as phoenix24
=== tck [n=tck@194.125.76.126]  has joined #upstart
=== tck_ [n=tck@212.2.175.76]  has joined #upstart
=== phoenix24_ [i=gbp@ns37986.ovh.net]  has joined #upstart
=== tck_ [n=tck@212.2.175.76]  has joined #upstart
[09:56] <Keybuk> start on wibble foo bar or ((foo "frodo baggins"
[09:56] <Keybuk>                              and bar bilbo))
[09:56] <Keybuk> stop on wibble (foo) and
[09:56] <Keybuk>                ^ Expected operator
[09:56] <Keybuk> exec /sbin/daemon
[09:56] <Keybuk> at line 3
[09:56] <Keybuk> \o/
=== phoenix24_ is now known as phoenix24
[10:36] <ion_> Whee
=== phoenix24 [i=npdgqpb@ns37986.ovh.net]  has joined #upstart
=== tck [n=tck@78.16.5.190]  has joined #upstart
=== Md [i=md@freenode/staff/md]  has joined #upstart
=== phoenix24 [i=eblv@ns37986.ovh.net]  has joined #upstart