[01:23] <ion> (offtopic) A Monkey Island game for free: http://www.telltalegames.com/playlikeapirate
[20:08] <mgoetze> hi ... from the manpage, i can't figure out what effect specifying "respawn" for a service actually has, since that is, supposedly, the default...
[20:25] <Esmil> mgoetze: Which version of upstart are you using? At least with 0.6.3 jobs behave differently with and without respawn
[20:28] <mgoetze> Esmil: hm yes 0.6.3, and it seems they indeed don't respawn without respawn, which means the manpage is rather confusing
[20:29] <mgoetze> does upstart have any events for ac power plugged in etc. ?
[20:32] <Esmil> mgoetze: I don't think it has, but I haven't tested it. It shouldn't be too hard to add a udev rule firing 'initctl emit' or something similar though
[20:47] <mgoetze> i guess cron functionality such as "start every hour" isn't implemented yet?
[20:48] <Esmil> No, but its planned
[20:50] <Esmil> Btw. I just remembered I have an udev rule to fire an event everytime I swith on/off my wireless, its definately possible to do it for ac power too
[20:54] <mgoetze> eh... has my /etc/udev/rules.d always been so empty? *scratches head*
[21:46] <mgoetze> hm, how does one autmatically start multiinstanced jobs? i tried the following:
[21:46] <mgoetze> start on runlevel [23] TTY=tty2
[21:46] <mgoetze> but it doesn't seem to have worked :(
[21:53] <Esmil> mgoetze: I don't think thats possible at the moment. You can, however make another job, eg. tty2.conf, just start on runlevel [23], pre-start exec start getty TTY=tty2, post-stop exec stop getty TTY=tty2
[21:56] <mgoetze> oh... that sucks :(
[22:08] <Esmil> Yes, it does. In order to fix it you'd have to figure out some new syntax of job files since events can have key/value pairs too. Probably something like "start TTY=tty2 on some-event KEY=value"
[22:34]  * mgoetze reports his first ever launchpad bug
[22:35] <mgoetze> am i not allowed to set the severity to wishlist myself?