| === AStorm [n=astralst@host-81-190-179-124.gorzow.mm.pl] has joined #upstart | ||
| === wasabi__ [n=wasabi@cpe-76-184-96-5.tx.res.rr.com] has joined #upstart | ||
| === woodwizzle [n=corey@user-0c6sclg.cable.mindspring.com] has joined #upstart | ||
| === Andrew__ [n=chatzill@client-82-3-94-213.manc.adsl.virgin.net] has joined #upstart | ||
| === Andrew__ is now known as space-m0nkey | ||
| === space-m0nkey is now known as space-m0nkey_ | ||
| === space-m0nkey [n=chatzill@client-82-3-94-213.manc.adsl.virgin.net] has joined #upstart | ||
| === Md [i=md@freenode/staff/md] has joined #upstart | ||
| === AStorm [n=astralst@host-81-190-179-124.gorzow.mm.pl] has joined #upstart | ||
| === j_ack [n=rudi@p508D9040.dip0.t-ipconnect.de] has joined #upstart | ||
| === wasabi [n=jhaltom@ubuntu/member/wasabi] has joined #upstart | ||
| === repp [n=repp@151.57.226.5] has joined #upstart | ||
| repp | hi, is "complex event configurations" supported in 0.3.5 ? | 05:07 |
|---|---|---|
| repp | i mean: | 05:08 |
| repp | from fhs-filesystem-mounted until fhs-filesystem-unmounted | 05:08 |
| repp | and from network-up until network-down | 05:08 |
| repp | do i need http://people.ubuntu.com/~scott/complex-event-config.patch ? | 05:23 |
| AlexExtreme | repp, use this bazaar branch: https://code.launchpad.net/~keybuk/+branch/upstart/complex-event-config | 05:25 |
| repp | AlexExtreme: do you know if there is a complete description of job scripts? | 05:33 |
| AlexExtreme | no | 05:34 |
| repp | http://upstart.ubuntu.com/wiki/ComplexEventConfig this seems to describe at least the complex event stuff | 05:36 |
| repp | i'm integrating this with getting-started | 05:36 |
| === mbiebl [n=michael@e180126203.adsl.alicedsl.de] has joined #upstart | ||
| === space-m0nkey [n=chatzill@client-82-3-94-213.manc.adsl.virgin.net] has joined #upstart | ||
| _ion | The page doesn't describe the final syntax | 06:39 |
| _ion | The one used in the complex-event-config implementation might not be 100% final, but it's close. And it's different than the wiki page describes. | 06:39 |
| repp | _ion: is there a description of it? | 06:40 |
| _ion | I think this describes the current form (but i haven't actually checked) just substitute 'FOO' to 'on'. https://lists.ubuntu.com/archives/upstart-devel/2006-December/000200.html | 06:42 |
| repp | thanks _ion | 06:42 |
| === jonib1 [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has joined #upstart | ||
| === jonib1 [n=jonas@ua-83-227-144-18.cust.bredbandsbolaget.se] has left #upstart [] | ||
| === juergbi [n=juerg@80-219-17-102.dclient.hispeed.ch] has joined #upstart | ||
| === lyam [n=zAi@88.118.60.248] has joined #upstart | ||
| lyam | is where an utility what manages daemons on Edgy? | 09:37 |
| _ion | services-admin? | 09:41 |
| _ion | (Not really related to upstart, as all services but gettys are still started by the old sysvrc scripts in edgy) | 09:41 |
| lyam | does upstart have something like inittab file like in older distros? | 09:43 |
| _ion | Depends on what you want to do with said inittab file. | 09:45 |
| _ion | The general answer is /etc/event.d | 09:45 |
| lyam | when booting Edgy by default, what is runlevel? | 10:05 |
| mbiebl | lyam: Read /usr/share/doc/upstart/README.Debian | 10:15 |
| === space-m0nkey [n=chatzill@client-82-3-94-213.manc.adsl.virgin.net] has joined #upstart | ||
| === j_ack [n=rudi@p508DB835.dip0.t-ipconnect.de] has joined #upstart | ||
| === space-m0nkey_ [n=chatzill@client-82-3-73-143.manc.adsl.virgin.net] has joined #upstart | ||
| === Md [i=md@freenode/staff/md] has joined #upstart | ||
| === space-m0nkey_ is now known as space-m0nkey | ||
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!