=== wasabi [n=wasabi@ubuntu/member/wasabi] has joined #upstart === tck [n=tck@213-202-166-184.bas503.dsl.esat.net] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === twb [n=twb@CPE-144-133-82-155.vic.bigpond.net.au] has joined #upstart [07:53] Does anyone know the status of upstart on Sid? [07:54] Rather, what is the status of upstart on Sid? === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === JK456 [n=laugeai@fe2adsl-2.wyplay.net] has joined #upstart [10:54] hi upstarters :) [10:54] i dont get how i can use the respawn system : [10:55] when i use it on a soft who forks, upstart dont see the son [10:55] and think the soft is dead, and respawn it [10:56] I am not a regular here, but I believe the upstart position is that daemons that fork into the background are broken. [10:56] What package are you having problems with? [10:56] some soft we wrote ourself [10:56] its a quite personalized system [10:57] but for exemple portmap daemon [10:57] it forks after launch [10:57] Are you sure about that? [10:57] well i am gona check again [10:58] I think upstart would say that portmap should be run with -d to prevent it disconnecting. [10:59] portmap forks, or if it doesn't it is restarted for no reason [11:00] -d ? [11:00] is it an upstart option ? [11:00] Oh sorry, -f is more appropriate. [11:00] See the portmap manual. [11:00] "-f (foreground) prevents portmap from running as a daemon, and causes log messages to be printed to the standard error output." [11:01] ok, its an option of portmap [11:01] As I said, I am not associated with upstart. [11:01] But I think they would advise you to add such an option to your program, too. [11:01] but it implies to modifie the code of all daemon in our system :s ^^ [11:02] but your informations are very usefull :) [11:02] thanks a lot [11:02] One needs to add the daemon stanza to the job definition, but handling forking daemons isnt completely implemented yet. [11:02] I'm afraid I can't help more; if you wait long enough a regular will stop by. [11:02] yep, i had the chance to talk them sometimes, freenode is great for that [11:04] The sole reason why Upstart needs to be pid 1 is that it can support forking daemons. Theres no upstart position that forking daemons are broken AFAIK. [11:04] I apologize, I was clearly mistaken. [11:05] Perhaps I am thinking of the cinit people [11:05] ion_ : oh ? how does it work ? [11:06] twb : no prob [11:06] Does upstart on ubuntu still just call out to sysvinit compat for just about everything except inittab? === twb remembers to check https://launchpad.net/distros/ubuntu/+spec/replacement-initscripts [11:07] Pid 1 receives the SIGCHLD for parentless processes. But handling it isnt implemented yet AFAIK. [11:07] twb: The sysvinit scripts havent been replaced with upstart jobs yet. [11:08] Doesn't that mostly take away the real benefit of using upstart for regular users? [11:09] ion_ : if i understand well, i will be possible to restart forking daemon, but it is not yet possible ? [11:10] jk456: Yes, thats the current situation as far as i know. [11:11] twb: I dont see what you mean. The scripts will be converted to upstart gradually. [11:12] I mean that the real appeal of upstart (at least to me) is reduced boot time as a result of aynchronous service startup. If upstart currently just uses run-parts to launch everything in rcS.d and rcN.d, then none of those scripts will be launched asynchronously. [11:12] ok, and i guess it is not possible to use inittab respawn because there is only one process (the 1) receiving sigchild [11:15] twb: I think the major point of upstart is a flexible bootup process that Just Works where sysvinit scripts would fail unless horrible kluges are added to them. Reduced boot time is just a bonus. === Md [i=md@freenode/staff/md] has joined #upstart [11:17] In what way does it "Just Work" more than sysvinit? [11:17] I mean, *right now* as opposed to after sysvinit scripts have been completely replaced [11:18] twb : if you seek for speed, you can test initng [11:18] That's the gentoo thing? [11:18] initng ? [11:19] Right now the system is booted by the sysvinit scripts. [11:19] initng : no i dont think i is for a specific distrib [11:19] But it's pioneered on gentoo, in the same way that upstart is on Ubuntu? [11:20] dont knwo, there is rpm and packages for lots of distrib [11:21] ion_ : in my case, we builded a personalized init, we had 23 seconds at boot, we are at 5 [11:21] "built" [11:21] ion_: I like their icon better than upstarts :P [11:22] (in init phase, there is also 15 seconds for hardware loading) [11:22] twb : but there is less features in initng [11:23] _ion : so thanks to upstart we won 18 seconds [11:23] (its linux embedded soft) === Amaranth_ [n=travis@ubuntu/member/Amaranth] has joined #upstart [11:25] twb : why dont you write your own scripts ? [11:26] it is not so so hard to do [11:26] `-- rcS [11:26] |-- S02mountvirtfs [11:26] |-- S10checkroot.sh [11:26] |-- S30checkfs.sh [11:26] |-- S39ifupdown [11:26] | `-- S40networking [11:26] |-- S40hostname.sh [11:26] Yes, it is. [11:26] `-- S55urandom [11:27] It is hard because I don't have millions of other Debian users helping me debug them. [11:27] on mountvirtfs, you launch the runlevel you want [11:27] |-- rc3 [11:27] | |-- S00set-date [11:27] | |-- S02engine [11:27] | |-- S05sysfs [11:27] | | `-- S06udev [11:27] | |-- S11messagebus [11:27] | |-- S65xinetd [11:27] | `-- S70lircd [11:28] thats the init profile we use (i removed the confidential parts) [11:28] twb : you just have to call the scripts in rcS.d and rcX.d [11:29] this scipts will do the job [11:31] so all your files in event.d will look like to this : [11:31] description "test" [11:31] author "jerry" [11:31] start on stopped mountvfs [11:31] console output [11:31] script [11:31] echo "portmap" [11:31] exec /etc/rc.d/rcS.d/S41portmap start [11:31] echo "done" [11:31] end script [11:31] Please stop flooding. [11:32] ^^ k [11:32] hope it helps [12:00] Ew, bootchart-view is written in Java. [12:06] ion_: have you looked at using LSB headers to programmatically convert sysv init scripts to upstart scripts? [12:08] Is there a LSB header for things like start when network is available, start when all partitions are mounted and writable, start when a sound card has been connected? If not, doing the conversion manually will yield much better results. [12:09] Yes. [12:10] i agree too [12:10] I concede that it won't be perfect, but I wonder if it can save you a lot of grunt work, allowing you to focus on the second 90% [12:11] twb : we wrote it in a day [12:11] the main part is to kwow the dependencies [12:11] after that you just call the sys scripts [12:12] or you copy them [12:12] http://user.skolelinux.no/~pere/mypapers/200706-bootseq/200706-bootseq.html [12:12] Upstart doesnt exactly deal with dependencies, its the other way around. === julo [n=julien@AToulouse-156-1-45-176.w90-16.abo.wanadoo.fr] has joined #upstart [01:38] hi [01:39] I have created an upstart script and it fails to start automatically: "unable to read: Invalid argument", but if I manually start it, it works well. [01:39] Any idea ? [02:10] salut [02:10] j'ai un problme avec upstart: j'ai cr un script, et l'amorage du j'obtiens l'erreur "unable to read: Invalid argument" au lancement du script. Par contre, si je lance ce script la main, a marche. === julo [n=julien@AToulouse-156-1-45-176.w90-16.abo.wanadoo.fr] has left #upstart ["Ex-Chat"] === crazy [n=crazy@frugalware/developer/crazy] has joined #upstart === benmur [n=benmur@friends.sukria.net] has joined #upstart === tale [n=tale@207.235.54.1] has joined #upstart === tck [n=tck@213-202-166-184.bas503.dsl.esat.net] has joined #upstart === mbiebl [n=michael@p5B1333FD.dip0.t-ipconnect.de] has joined #upstart === mbiebl [n=michael@85.180.65.162] has joined #upstart === tck [n=tck@213-202-166-184.bas503.dsl.esat.net] has joined #upstart === tck_ [n=tck@213-202-166-184.bas503.dsl.esat.net] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart