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