=== Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === GodEater_ [n=bryan@rockbox/staff/GodEater] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === mbiebl [n=michael@e180071094.adsl.alicedsl.de] has joined #upstart === Keybuk [n=scott@wing-commander.netsplit.com] has joined #upstart [11:42] Keybuk: hi, how's work going on upstart? [11:42] I guess you are pretty busy atm with the upcoming release [11:51] mbiebl: still blocking on working out what direction to tak eit [11:52] Why not implement some non-controversial stuff first. [11:52] such as? [11:52] I'd love to see pid file monitoring e.g. [11:54] but you wouldn't get to see it for a while [11:54] since the rest of the code is in an intermediate state [11:56] what about branching off from 0.3.8 for that? [11:56] IIRC also stuff like umask, chroot etc. is not implemented yet. [11:56] that stuff's always been implemented [11:57] ah sorry, I mixed it up with an option to run the job as a different user... [11:57] that's never going to be implemented :p [11:58] lol [11:58] the closest to that planned is having users other than root own jobs [11:58] (and having them listen in on that user's and root's events) [12:01] the problem at the moment for me is until I've decided what to do with Upstart, I don't really have much motivation to work on it [12:01] So an option like start-stop-daemons --chuid won't be in upstart. Would have been handy because some sysv init scripts seems to use that functionality [12:01] mbiebl: exec su user -c ... [12:03] yeah, but a separate chuid stanza for that would be "nicer". [12:05] reimplementing all of su in upstart is "nicer" ? [12:06] mbiebl: what are your thoughts on the mail I sent to upstart-devel? [12:06] I'll have to read it again first. [12:09] I can't promise though, that I can contribute something useful to the discussion which will help you :-) [12:12] Another area, upstart is currently lacking imho, is a flexible output/logging system. === Md [i=md@freenode/staff/md] has joined #upstart [12:20] Might be worth looking at. What was the outcome of the logd issue? [12:20] Is something like syslog-ng an valuable alternative for that? [12:25] maybe [12:25] I haven't looked into it === juergbi [n=juerg@80-219-16-19.dclient.hispeed.ch] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === juergbi [n=juerg@80-219-16-19.dclient.hispeed.ch] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === juergbi [n=juerg@80-219-21-79.dclient.hispeed.ch] has joined #upstart === mbiebl [n=michael@e180071094.adsl.alicedsl.de] has joined #upstart === mbiebl [n=michael@e180071094.adsl.alicedsl.de] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === mbiebl [n=michael@e180071094.adsl.alicedsl.de] has joined #upstart