| === evand is now known as ev | ||
| === ev is now known as evand | ||
| === evand is now known as ev | ||
| === ev is now known as evand | ||
| wanderer_ | hi. Ubuntu9.10 question: anyone can explain why symbolic link in /etc/init/ is not recognized by upstart as valid job? | 14:13 |
|---|---|---|
| wanderer_ | evand:did not really help | 14:25 |
| twiinz | hi there, is it possible to have a single upstart .conf file that exec multiple scripts (basically the same script but with different parameters) and also set the respawn setting on each of them ? | 16:12 |
| wasabi | twiinz, there is an instance thing. | 17:21 |
| wasabi | not sure if that's what you're thinking of | 17:21 |
| twiinz | wasabi: instance? that sounds interesting | 17:22 |
| wasabi | man 5 init | 17:22 |
| wasabi | Keybuk, it's really awesome to see all this stuff we talked about live. | 17:23 |
| wasabi | congrats | 17:23 |
| twiinz | wow wasabi this looks very promising, reading about it | 17:24 |
| wasabi | Hmm. DKMS needs to run before GDM. | 17:38 |
| wasabi | Sucks rebooting into a new kernel without nvidia built. :0 | 17:39 |
| mbiebl | Keybuk: bzr branch lp:upstart | 17:51 |
| mbiebl | bzr: ERROR: Not a branch: "http://bazaar.launchpad.net/~scott/upstart/trunk/". | 17:51 |
| Keybuk | mbiebl: what version of bzr? | 17:54 |
| Keybuk | bah, regression/change with automake 1.11 | 18:06 |
| Keybuk | make dist doesn't work anymore | 18:06 |
| === highvolt1ge is now known as highvoltage | ||
| mbiebl | Keybuk: 2.0.2-1 | 18:31 |
| mbiebl | hm, now magically fixed again :-) | 18:38 |
| Keybuk | mbiebl: probably caught LP at a bad Time | 19:28 |
| adurity | I'd like to run a script based on the presence of certain hardware at boot. Can upstart help me do this today? | 22:36 |
| mbiebl | adurity: yes | 22:41 |
| adurity | mbiebl, how? | 22:41 |
| mbiebl | If you use ubuntu 9.10, there is a already a tool called upstart-udev-bridge | 22:42 |
| mbiebl | which generates upstart events based on information from udev | 22:42 |
| mbiebl | If you don't have that tool, you can write your own udev rules | 22:42 |
| mbiebl | and emit events use initctl emit | 22:43 |
| mbiebl | and start your upstart based on those events | 22:43 |
| adurity | i have upstart-udev-bridge | 22:44 |
| adurity | how do I know which events to listen to for specific hardware? | 22:45 |
| mbiebl | my best answer to this is, read the source | 22:46 |
| mbiebl | apt-get source upstart | 22:46 |
| mbiebl | -> udev/upstart-udev-bridge.c | 22:46 |
| mbiebl | there you can read, how the events are named | 22:47 |
| adurity | alright, thanks, I'll go source diving | 22:47 |
| Keybuk | $SUBSYSTEM-device-$ACTIONed | 23:44 |
| Keybuk | :) | 23:44 |
| Keybuk | it's a hack though, and will change in backwardly incompatible ways | 23:44 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!