=== phoenix24 [i=yonbfvz@ns38066.ovh.net] has joined #upstart === phoenix24_ [i=qntk@ns38066.ovh.net] has joined #upstart === phoenix24 [i=tjizpjd@ns38066.ovh.net] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === phoenix24 [i=nzttkgi@ns38066.ovh.net] has joined #upstart === phoenix24 [i=raxjfbz@ns38066.ovh.net] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === phoenix24 [i=prpgeic@ns37986.ovh.net] has joined #upstart === asdaf [n=Ack@213-140-11-128.fastres.net] has joined #upstart === Rusant [i=Rusty4@host34-35-dynamic.8-79-r.retail.telecomitalia.it] has joined #upstart [01:25] wasabi: so let me try and explain :) [01:25] you have a job for a web server [01:25] in this job, you define the configuration for the web server itself; what needs to be run, how to prepare the machine and clean up afterwards, etc. [01:25] any chroot/chdir/resource limits/etc. [01:25] this is the "job" [01:25] you also define the machine state in which the web server should be running [01:26] these are events and pairs of cancelling events [01:26] or references to other job/states [01:26] e.g. the web server is running while there is at least one non-local network interface up and the filesystem has been assembled [01:26] this is "the state in which the web server can be run" [01:27] and the web server job state is nominally coupled to this state [01:27] any changes to this state change the goal of the web server job [01:27] however this is not "the state in which the web server IS running" [01:27] because the web server could fail to start, and stop again, without the underlying state being changed [01:27] or the web server could be started and stopped manually [01:27] or the web server could be a member of a disabled profile [01:27] etc. [01:28] jobs that reference "when a web server is running" are NOT referencing the state in which the server could be running, but the state in which it IS running [01:28] so there's a second state here [01:28] one state is defined in the job configuration and is tied to the goal of the job [01:28] the other state is implicit and is tied to the state of the job [01:29] so "with apache" means the state of the apache job [01:29] not the state in which the apache job can be running === phoenix24 [i=jgxfkw@ns37986.ovh.net] has joined #upstart === Rusant [i=Rusty4@host34-35-dynamic.8-79-r.retail.telecomitalia.it] has left #upstart [] [02:22] i see [02:33] does that make sense? === tale [n=tale@207.235.54.1] has joined #upstart === Keybuk has issues with blocking [04:05] does this # have logs? [04:06] yeah [04:06] people.ubuntu.com/~fabbione/irclogs/upstart-devel-.... [04:06] err [04:06] upstart-... :p [04:26] http://upstart.ubuntu.com/wiki/States === thom [n=thom@amnesiac.heapspace.net] has joined #upstart === phoenix24 [i=viqpsc@ns37986.ovh.net] has joined #upstart === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart === juergbi [n=juerg@80-219-16-162.dclient.hispeed.ch] has joined #upstart === phoenix24 [i=zwdchfz@ns37986.ovh.net] has joined #upstart [06:13] heh, the implementation of profiles i did before was purely lazy [06:14] hmm? [06:15] well, it had absolutely no support for changing profile at runtime, in fact it was quite easy to do that [06:15] it used multiple variables to store info about the current profile rather than a struct [06:16] so i've had to do a fair bit of work to get it working with the new config code, rather than changing a few lines [06:16] laziness != good ;) [06:27] oops, sorry [06:36] \o/ [06:36] parse_profile.c written === AlexExtreme adds the necessary parts to conf.c [06:37] never read code you wrote when you were 18 [06:38] it's very disturbing [06:38] heh [06:38] i have code here that i wrote when I was 9 [06:38] it's *very* disturbing ;) [06:38] not to mention that it's written in VB [06:39] Anything VB is disturbing. [06:39] true [06:40] Speaking of disturbing and VB, http://johan.kiviniemi.name/blag/2006/12/26/excellence/ (in you havent been spammed with this URL yet). [06:41] interesting [06:47] blah. this new server will not run mdrun and vgchange properly in the initramfs [06:47] these packages are constantly pissing me off heh [06:48] wasabi: which release? [06:48] feisty [06:48] heh, yeah, that was pretty bustef [06:48] My desktop on gutsy is busted too. [06:48] yeah, gutsy is more busted righ tnow [06:48] ... my desktop is weird. It looks like udev spawns a ton of mdadm processes. [06:48] infinitly. [06:48] evms installed? [06:49] Nope, I've removed EVMS from teh picture. [06:49] oh right [06:49] dunno then [06:49] You win.=) [06:49] I do? [06:49] Yup. No more evms for me. heh [06:50] lol === Keybuk starts on the next project [06:50] "make wasabi use ext3" [06:50] Are you still familiar with the local-top/mdadm|run scripts, or is somebody else doing them now? [06:50] Oh, you won that too. [06:50] I'm trying to understand what they do/are for [06:50] I just reformatted to ext3. [06:51] Mostly because half of my files because mysteriously truncated. [06:51] heh, it's interesting how most people abandon XFS after an "event" [06:51] mine was when a bunch of files had \0 through them for no readily apparent reason [06:52] ldconfig: file /usr/lib/libwine.so.1 is truncated [06:52] at least ldconfig is very clear about the problem. heh [06:52] RUN+="watershed -i udev-mdadm /scripts/local-top/mdadm from-udev" [06:52] keybuk: Ditto. [06:52] yeah [06:52] That's an odd one. What's the 'udev-mdadm' in there refer to? [06:52] I don't understand why ian runs that [06:53] since in the real filesystem, we just run mdadm itself [06:53] You mean mdrun? [06:53] err, mdadm I think [06:53] I don't really understand what the difference between the two mdadm related initramfs scripts is [06:53] and what the difference between mdrun and mdadm is [06:53] once I understand, mdadm shall be fixed [06:53] Looks like mdrun does auto detection. It's a single shot line that probes all drives. [06:54] Probably not what you need with udev feeding events. [06:56] Hmm. Yeah, looks like mdadm has the work mdrun does duplicated... just in a harder fashion. [06:56] ... builds a config file on the fly from --scan, and then uses that. [06:59] interesting [06:59] neither seems right though, since we need to run something repeatedly until it sticks? [06:59] Yeah. I think what mdrun does is technically rigth... probes all devices. [06:59] Just watershed it on any device event. [07:00] Oh except mdrun is deprecated. [07:01] well that cinches that. *deletes the file* [07:04] lol [07:10] welcome to my world [07:10] "ah, this looks exactly right ... wait, what'd'ya mean deprecated?" [07:11] :-) [07:16] :) === Keybuk scowls at the weather [07:18] you rained yesterday, so flying was cancelled [07:18] you're raining again today [07:18] you better not rain on Saturday [07:22] heh. sometimes I wonder whether this really is summer... [07:22] i think we had summer here in april ;) [07:23] yeah [07:25] Not very summer-ish here either, but thats to be expected, this is Finland after all. :-) === phoenix24 [i=mxs@ns37986.ovh.net] has joined #upstart [07:59] well, that's a start [07:59] it segfaulted [07:59] :p [08:07] bah [08:07] honest question. how do you know what is "supported" and not "supported" on ubuntu. md, for instance. How can it be that it is knowingly busted in feisty? [08:07] Heh. [08:07] it helps to call nih_list_init on a NihList before using it [08:08] In fact who specifically should be tarred and feathered for this? [08:09] i'm not sure about md in feisty, i used it once it it was broken, kinda. [08:09] can't remember what happened exactly [08:10] brb, testing again [08:11] Or perhaps it's my fault for thinking feisty would work at all the same things dapper did. Perhaps the lack of the LTS. [08:12] neat [08:12] it worked [08:16] hmm. wonder if mdadm and vgchange could somehow deadlock on each other. === mbiebl [n=michael@e180074083.adsl.alicedsl.de] has joined #upstart === phoenix24 [i=ffjubj@ns37986.ovh.net] has joined #upstart === Starting logfile irclogs/upstart.log === ubuntulog [i=ubuntulo@ubuntu/bot/ubuntulog] has joined #upstart === Topic for #upstart: Upstart 0.3.8 | http://upstart.ubuntu.com/ | http://upstart.ubuntu.com/wiki/UpstartOnGentoo === Topic (#upstart): set by Md at Sun May 6 19:59:46 2007 === Amaranth [n=travis@ubuntu/member/Amaranth] has joined #upstart