[00:54] <mase_wk> can upstart be used to monitor a file event ( like a file being modified) ?
[01:02] <ion> mase_wk: Not yet, but that’s in TODO.
[01:03] <mase_wk> ion: thanks 
[05:15] <wasabi_> So. I just had a problem where I booted up my server, and init stopped starting proceses before I had a usable console.
[05:15] <wasabi_> Looks like it got hung up trying to contact dbus.
[05:16] <wasabi_> single mode was in a similar shape. break=mount got me in, and I just removed dbus
[05:16] <wasabi_> And now it boots.
[05:16] <wasabi_> Guess if I install dbus while the system is running, init will get -USR1 and attempt to connect... and maybe freeze in the same way
[05:16] <wasabi_> But I should still have a system usable enough to debug it. ;)
[05:23] <wasabi_> init: Unable to connect to the system bus: Connection ":1.0" is not allowed to own the service "com.ubuntu.Upstart" due to security policies in the configuration file
[05:25] <wasabi_> imaginging there is supposed to be some sort of system.d/upstart.conf
[22:13] <echa> hi there
[22:13] <echa> i'd like to add a job in my ubuntu 9.10 startup to run an ethtool setting
[22:13] <echa> is there a new way to do this?
[22:14] <mtd> can/should I use upstart to communicate between non-root processes (source daemon fires event IM_HOME, which causes upstart to start a few daemons, for example), or is that better a D-Bus thing?
[22:14] <echa> in debian i guess i would make a init.d script
[22:15] <mtd> echa: sure, make an /etc/event.d script that runs on runlevels 2-5
[22:18] <echa> ok
[22:18] <echa> thanks
[22:19] <mtd> echa: echo -e "start on stopped rcS\nconsole output\n/run/my/job/here" > /etc/event.d/my-startup-job-config
[22:20]  * mtd supposed rcS is a bit more precisely "startup"
[22:23] <JanC> upstart in Ubuntu 9.10 doesn't use /etc/event.d/
[22:24] <echa> ?
[22:28] <JanC> it uses /etc/init/
[22:28] <JanC> read the manpages  ;)
[22:31] <echa> so i just use /etc/init.d/myscript and link to it in rc5.d/?
[22:32] <echa> that's the old way to do it
[22:32] <echa> i thought upstart had changed all that, i'm confused
[22:32] <ion> /etc/init ≠ /etc/init.d
[22:35] <echa> ok, i see, so why are there still init.d scripts - is it just that not everthing has been migrated
[22:36] <echa> ?
[22:37] <ion> Basically, yes. Also, everything doesn’t *need* to be migrated. There are benefits from migration, of course, but $randomsoftware that used to work with sysvinit will not be broken by upstart.
[22:37] <echa> and i still don't know where to put my ethtool script. i'd like to know where to put the setting
[22:38] <ion> What does the script to?
[22:38] <echa> ethtool -s eth0 wol g
[22:38] <echa> just enables wake on lan for my ethernet adaptor
[22:39] <ion> Something like
[22:39] <ion> start on net-device-added INTERFACE=eth0
[22:39] <ion> task
[22:39] <echa> hm
[22:39] <ion> exec ethtool -s "$INTERFACE" wol g
[22:39] <ion> in /etc/init/ethtool-wol.conf
[22:40] <echa> right
[22:40] <ion> My personal preference would be /etc/init/local/ethtool-wol.conf for easy access to my personal jobs.
[22:40] <echa> right
[22:40] <echa> keep them separate
[22:41] <echa> where can i find a reference for the device triggers?
[22:41] <ion> upstart-udev-bridge listens to udev events and emits upstart events with the format $SUBSYSTEM-device-{added,removed}
[22:41] <echa> oh i see
[22:41] <echa> ok
[22:41] <ion> Its documentation could use some help.
[22:42] <echa> hm
[22:44] <echa> i'll try
[22:52] <mtd> JanC: thanks, I was reading the Fedora manpages since I didn't have non-google access to the ubuntu ones (yeah I know echa asked about ubuntu...)
[22:53] <JanC> what do you mean by non-google access ?
[22:54] <mtd> JanC: presumably the ubuntu man pages are indexed by google a few times.
[22:54] <JanC> they are at http://manpages.ubuntu.com/
[22:55]  * mtd nods.