[12:27] <Coldbyte> Md are you there?
[01:26] <Coldbyte> staff members here?
[01:30] <neuralis> Coldbyte: this is not a support channel.
[01:35] <Coldbyte> i know that but Md is listed as staff member
[01:35] <Coldbyte> and i can't pm him about my registration issues as im not registered
[01:36] <zorglub> you should use the dedicated channels
[01:36] <zorglub> I suppose #help exists
[01:36] <Coldbyte> doesnt
[01:39] <Coldbyte> anyway type /who freenode/staff/*
[01:39] <Coldbyte> and you will see
[01:41] <neuralis> Coldbyte: you can always private message staff members.
[01:42] <Coldbyte> the message i get says smth else
[01:44] <Md> Coldbyte: everybody can send messages to staff, I have no clue why you believe this is not possible. anyway, if somebody is not answering usually insisting will not help much
[07:23] <dem> is there documentation on the job format; i'm trying to write a job to start the mythtv backend server
[07:26] <LarstiQ> dem: http://upstart.ubuntu.com/doc/getting-started.html ?
[07:28] <dem> yeah, but it dosen't really list (all) the events that I can use
[07:28] <LarstiQ> from what I gather, there is no limit
[07:29] <dem> i'm trying to figure out exactly what respawn does
[07:29] <dem> since it's in some jobs but not really documented anywhere
[07:30] <dem> for example can i respawn something as a certain user
[07:32] <dem> basicaly i'm trying to figure out, how to start the mythbackend deamon, and have it respawn in the case it goes down, as the mythtv user
[07:32] <LarstiQ> dem: sorry not to be able of help :/
[07:32] <dem> and a second script to start an Xserver with the mythtv-frontend, also repsawn that in the case it goes down, but only if the mythtv-database up
[07:33] <dem> that's okay, maybe some one knows
[07:34] <dem> i figured, hell there's this new stuff edgy, might as well use/get on the bandwagon
[07:57] <_ion> "respawn" respawns a daemon in case it dies.
[08:49] <dem> _ion: how do you variables in the job?
[08:50] <_ion> Do you mean environment variables?
[09:12] <dem> yeah
[09:13] <dem> well that too, but how would i do a deamon that respawns when it dies and also runs as a particular user?
[09:13] <alp> from a blog entry i saw, "The IPC mechanism used by upstart is not currently D-BUS because of various problems" -- i was wondering if there's a summary of what these problems are?
[09:24] <_ion> dem: env foo=bar
[09:24] <_ion> dem: Seems like there's no support for setting uid in jobs. It wouldn't be difficult to implement, though.
[09:25] <_ion> alp: There is lengthy discussion about that in the mailing list.
[09:28] <alp> _ion: any idea which list/timeframe?
[09:28] <alp> ah, there is an upstart-devel
[09:30] <alp> _ion: i don't see any pertinent threads
[09:34] <alp> i'm working on a dbus-compatible ipc implementation and want to make sure any limitations of libdbus and its daemons aren't carried on to mine
[09:42] <alp> the only discussion i could find (on the dbus list) relates to process activation