| mbiebl | similar to the system and session bus concept from d-bus? | 12:23 |
|---|---|---|
| wasabi_ | Yeah. | 12:23 |
| wasabi_ | Basically, just using upstart as a process for managing parallel starts based on event emission. | 12:23 |
| wasabi_ | Which is all it is. | 12:23 |
| wasabi_ | One code base which is efficient at managing child processes and stuff, instead of many. | 12:24 |
| mbiebl | Well, imo there are more important issues than that atm though. | 12:24 |
| wasabi_ | dbus could use it to do activation. | 12:24 |
| wasabi_ | the system bus could do activation on the system upstart, the session bus could do activation on the session upstart. | 12:25 |
| mbiebl | complex-event-config being one ;-) | 12:25 |
| wasabi_ | yeah. | 12:25 |
| mbiebl | pid file support is another. | 12:25 |
| mbiebl | There are still daemons out there which can't be run in the fg. | 12:26 |
| === wasabi [n=wasabi@ubuntu/member/wasabi] has joined #upstart | ||
| === Keybuk [n=scott@12.145.6.2] has joined #upstart | ||
| === mbiebl [n=michael@e180073128.adsl.alicedsl.de] has joined #upstart | ||
| === mbiebl [n=michael@e180073128.adsl.alicedsl.de] has joined #upstart | ||
| === juergbi [n=juerg@80-219-18-22.dclient.hispeed.ch] has joined #upstart | ||
| === cortana [n=sam@62-31-146-25.cable.ubr12.azte.blueyonder.co.uk] has joined #upstart | ||
| === mbiebl [n=michael@e180070009.adsl.alicedsl.de] has joined #upstart | ||
| === tale [n=tale@207.235.54.1] has joined #upstart | ||
| === sadleder [n=sadleder@p50811dab.dip0.t-ipconnect.de] has joined #upstart | ||
| === sadleder [n=sadleder@p50811dab.dip0.t-ipconnect.de] has left #upstart [] | ||
| === liquidat [n=liquidat@4560-02bg04.stw-wh.uni-jena.de] has joined #upstart | ||
| === mbiebl [n=michael@e180070009.adsl.alicedsl.de] has joined #upstart | ||
| === Md [i=md@freenode/staff/md] has joined #upstart | ||
| === int0x0c [n=ben@161.253.46.169] has joined #upstart | ||
| === aguaithefreak [n=aguai@125-225-108-104.dynamic.hinet.net] has joined #upstart | ||
| === aguaithefreak [n=aguai@125-225-108-104.dynamic.hinet.net] has left #upstart [] | ||
| === cyberix [n=cyberix@hoasb-ff02dd00-192.dhcp.inet.fi] has joined #upstart | ||
| cyberix | Does upstart automagically react to changes in inittab? | 08:33 |
| AlexExtreme | no | 08:34 |
| cyberix | How can I tell it to react? | 08:38 |
| wasabi_ | upstart doesn't use inittab, does it? heh | 08:38 |
| wasabi_ | So that would be a "you can't." | 08:38 |
| cyberix | It has a similar configuration file? | 08:39 |
| wasabi_ | /etc/event.d | 08:39 |
| wasabi_ | It's quite different, so no. | 08:39 |
| cyberix | ok | 08:41 |
| cyberix | Thanks | 08:41 |
| mbiebl | wasabi_: The sysv compat layer in Debian/Ubuntu reads /etc/inittab (if existent) to determine the default runlevel. | 08:42 |
| mbiebl | Otherwise /etc/inittab is not used. | 08:43 |
| wasabi_ | Ahh, but that's not upstart itself as much as one of the job files | 08:43 |
| mbiebl | Right, It's the rc-default job file. | 08:43 |
| === Alfonso [n=alfonso_@201.250.206.233] has joined #upstart | ||
| === Alfonso [n=alfonso_@201.250.206.233] has left #upstart [] | ||
| === mbiebl [n=michael@e180070009.adsl.alicedsl.de] has joined #upstart | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!