=== Keybuk_ is now known as Keybuk [22:36] Upstart runs all "start on runlevel 2" scripts in paralel? [22:38] yes [22:40] damjan: you ever get around to toying with those arch upstart scripts? [22:40] Zeqadious: I've made my first successfull boot of Upstart on ArchLinux [22:41] ah [22:41] I'm starting /etc/rc.sysinit and rc.multi now [22:41] i know you were interested in 0.5 versions: http://zeqadious.homelinux.net/junkbin/upstart-0.5.1-jobs/ [22:41] if it helps [22:41] so that I'm compatible with Arch as it is [22:41] again based directly from Arch [22:42] damjan: that's awesome, thank you. [22:42] Zeqadious: I also made a multi-instance agetty script [22:43] damjan: i would interested in seeing that :) [22:43] so basically, instead of having a separate script for each tty [22:43] i tried to write a arch stype stat_busy stat_done stuff for upstart, but its quite flakey [22:43] oh thats cool [22:44] start on stopped sysinit/kernel-logger RESULT=ok <- how does it work? [22:44] I have one, instance $TTY; exec /sbin/agetty -8 38400 $TTY linux [22:45] Zeqadious: and I have another script that starts all of the instances when rc.multi is stopped [22:45] temoto: sysinit/kernel-logger is a job [22:45] damjan: sorry, i mean "RESULT=ok" [22:45] when it's stopped (i.e. successfully run) your other script will run then [22:45] if kernel-logger exits with status=1 it won't [22:46] exitcode? [22:46] temoto: each Unix process has a return value [22:46] aha [22:46] yeah like ecitcode [22:46] thanks, now i get it [22:46] errorlevel on windows [22:46] hi.. i have a upstart job getting started by an application emitting an event.. it is mostly working, except that upstart isnt terminating as I would expect.. i have cut the job down to a single 'exec xinit ' [22:47] RESULT=ok and RESULT=0 is same? [22:47] Zeqadious: http://www.netsplit.com/2008/04/19/upstart-05-job-lifetime/ .. about instances [22:48] My ubuntu 9.04 has upstart 0.3.9 .. wow, i did expect something newer. [22:48] damjan: nice stuff [22:49] damjan: are you developer of upstart? [22:49] temoto: no [22:50] far from it :) [22:50] thats Scott's blog [22:50] Zeqadious: so these jobs you have, this is a port from rc.sysinit right? [22:51] yes [22:51] k [22:51] i have upstart job scripts for dbus, acpid, hal, networkmanager, crond, and syslog-ng too [22:51] so far* [22:51] they are ... problematic [22:52] I have two for memcacheq and mongodb :) [22:53] Zeqadious: what's problematic in crond or syslog? [22:53] temoto: those seem to work 100%, however the others tend to not honor the start on stanza rules [22:54] Zeqadious: you mean tens of "and stopped" ? [22:54] damjan: here is my 'current in use scripts' however they aren't quite compatable with Arch Linux anymore. But please feal to free to steal if you like anything http://zeqadious.homelinux.net/zizzy-linux/i686/abs/core/upstart-jobs/ [22:57] I need to do the shutdown part... couldn't find much documentation about it for Upstart [22:58] i have problems because my data partition is always in use and can't be unmounted [22:58] lol [22:58] the command 'reboot' works 100% [22:58] ctrl+alt+delete 0% [22:59] So on ubuntu using upstart 0.3.9 i can create directories, not only job files? upstart runs like /etc/event.d/*/* ? [22:59] yes [22:59] cool [22:59] start on RESULT=failed now what this mean? [22:59] when exitcode is not 0 [22:59] RESULT of what? [23:00] anything [23:00] uh [23:00] any other upstart job? [23:00] yes [23:00] Zeqadious: it's your jobs.d/sulogin [23:01] temoto: i'm aware [23:02] hm.. if anything fails - sulogin. [23:02] What if /sbin is not mounted - then sulogin job fails and upstart runs another one? [23:03] temoto: if /sbin is not mounted, upstart will not start either [23:03] lol [23:03] right [23:04] But what if /sbin would be unmounted after upstart starts? [23:04] ..and anything fails [23:05] system required boot files reside in /{bin,sbin,lib,etc} per fhs. they are required to be there for boot. [23:05] temoto: upstart (and sysvinit) are /sbin/init, can't be umounted [23:06] fs can't be unmounted while program started from it is running? [23:06] temoto: /usr, /var, and /home are often on other partitions however [23:07] temoto: yes, it can't [23:09] hm.. all this start on stopped this and stopped that.. it's possible (and Zeqadious did) to build a complex dependancy tree. [23:10] But it's very hard to see this dependancies with just browsing files. [23:10] There must be some kind of sysv-rc-conf program to manage jobs via UI. [23:11] yeah it can be hard to debug [23:11] as the dev's of most projects seem fond of saying, "patches welcome" [23:11] :) [23:11] a simple tool showing the dependency tree would be nice [23:11] so not yet? [23:11] temoto: not that i'm aware [23:11] i see [23:12] my scripts certainly aren't 100% yet anyway. closer to 70% and rough. [23:12] the status messages are very* problematic because of the parallel jobs :) [23:13] Zeqadious: btw in one your job file i saw you put \ at the end of lines in 'start on' stanza. In other job i see no \. [23:13] see previous line. [23:14] Zeqadious: so that's syntax error? [23:14] technically yes, but it will still work. [23:15] erh..? [23:15] I think they 100% must not require \, that would make jobs readable. [23:21] damjan: do you happen to know if the environment jobs run in is 100% posix compliant (eg. dash) or the regular 100% posix based (eg. bash)? [23:21] damjan: i get the feeling from working on this for a while that its probably /bin/sh [23:22] I don't know [23:22] oh well [23:22] Zeqadious: > script instead gives shell script code that will be executed using /bin/sh [23:22] I think I've read somewhere about the implementation of script, but that was long time ago [23:22] http://upstart.ubuntu.com/getting-started.html [23:24] at least for version 0.3.9 anyway [23:24] probably still the same however. [23:25] paths.h:#define SHELL "/bin/sh" [23:25] nice