=== administrator [i=administ@nat/cisco/x-a4cfccb527852c5b] has joined #upstart === sanityx [n=sanityx@pool-71-249-101-16.nycmny.east.verizon.net] has joined #upstart [03:08] Anybody here? [03:08] How do I control what services run at boot with upstart? [03:37] This channel is ALIVE with activity. === j_ack [n=rudi@p508daa58.dip0.t-ipconnect.de] has joined #upstart === administrator [i=administ@nat/cisco/x-926c5bfaad8d99ef] has joined #upstart === juergbi [n=juerg@80-219-17-102.dclient.hispeed.ch] has joined #upstart === mbiebl [n=michael@e180076086.adsl.alicedsl.de] has joined #upstart === mbiebl [n=michael@e180076086.adsl.alicedsl.de] has joined #upstart === mbiebl [n=michael@e180076086.adsl.alicedsl.de] has joined #upstart === Keybuk [n=scott@wing-commander.netsplit.com] has joined #upstart [12:57] hmm... if i have a job with, for example, both 'stop on foobar 0' and 'stop on foobar 1', i know I can get the actual event name, foobar, in the scripts with the UPSTART_EVENT variable, but how can I get the arguments to the foobar event, in this case 0 or 1? === AlexExtreme hopes that made sense [12:59] $1, $2, $3 [01:00] ah [01:00] ok [01:00] thanks [01:00] this works for exec too, through an evil trick [01:01] yeah [01:06] I have yet to work out the pattern by which the scrap van comes around our street [01:06] SETI could analyse the periods between visits and discover new and unhidden depths in the complexity of the universe [01:07] :p [01:07] <_ion> They're sending you secret messages through the periods between visits. [01:08] <_ion> You're not schizophrenic if they're really sending messages to you. [01:09] that's paranoid [01:10] schizophrenic is when you send messages to yourself [01:24] <_ion> I was finally able to order a decent monitor to replace these blussy CRTs. [01:24] <_ion> blurry [01:28] _ion, LCD? or another CRT? [01:31] <_ion> Samsung 226BW, a 22" widescreen flat monitor. [01:31] nice [01:31] this LCD has managed to get the outline of my top gnome panel etched into the screen... [01:31] <_ion> :-) [01:32] shows how much I use it :p [01:42] btw [01:42] if I do this in my job for system-tools-backends: [01:42] exec STB_NO_DAEMON="y" /usr/bin/system-tools-backends [01:43] will upstart interpret that correctly by passing it to a shell and behave as you'd expect it to? [01:45] <_ion> exec env STB_NO_DAEMON="y" /usr/bin/system-tools-backends [01:46] <_ion> Even better: [01:47] <_ion> env STB_NO_DAEMON=y [01:47] <_ion> exec /usr/bin/system-tools-backends [01:47] ah [01:47] cool === mbiebl [n=michael@e180076086.adsl.alicedsl.de] has joined #upstart === mbiebl [n=michael@e180076086.adsl.alicedsl.de] has joined #upstart [03:13] Keybuk: I think upstarts sysv compat utils are not compatible enough ;-) [03:13] I noticed that while adopting upstart for Gentoo. [03:15] When in runlevel 0 or 6, reboot/halt/poweroff when called without -f, should *not* call shutdown. [03:16] Other distros I checked do not have a "-f" in the final halt/reboot call. === AlexExtreme noticed that about 5 minutes ago ;) [03:17] I think it would also be nice, if the links would be the same as with sysvinit [03:18] poweroff -> halt, reboot -> halt [03:18] and not halt->reboot, poweroff -> reboot [03:18] But that's just nitpicking. [03:19] Besides that it was astonishingly painless to get upstart running on Gentoo ;-) [03:20] Yeah, but then it'll be astonishingly painful to actually write upstart-native jobs for it ;) [03:22] yeah, that is a different kettle of fish === j_ack [n=rudi@p508DB904.dip0.t-ipconnect.de] has joined #upstart [03:22] btw, i've got some new upstart-native jobs for frugalware here: http://ftp.frugalware.org/pub/other/upstart-jobs/upstart-jobs/etc/event.d/ [03:23] i haven't actually tested them yet though, i'm setting up a virtual machine because i don't want to kill my main machine :) [03:23] hehe [03:23] they're kinda ugly atm, i'm sure some stuff could be done better, and there's no event based networking or mounting yet [03:25] when do you expect the first frugalware release with a fully upstart-native boot? [03:26] 0.7 stable will definitely have it, it won't get into 0.6 because that's gonna be released in 4 days [03:26] i'll try to get it into the development repo quite early in 0.7's development [03:27] cool. what is your strategy for frugalware: will you dump sysvinit completely and go upstart only? [03:27] Or will you ship both? [03:27] just upstart [03:27] Yeah, that makes it easier... [03:27] but we'll leave the sysv compat stuff there for proprietry apps which provide their own init script like vmware === wasabi [n=wasabi@ubuntu/member/wasabi] has joined #upstart [03:32] Keybuk: about the "-f" behaviour of the compat tools [03:32] Should I file a bug report? [03:32] probably a good idea, then there's no reason for him to forget it ;) [03:33] I just wanted to get his opinion first, but then it seems he is not around atm. [03:36] AlexExtreme: Have you also written the udev rules already? [03:36] http://ftp.frugalware.org/pub/other/upstart-jobs/upstart-jobs/etc/udev/rules.d/85-upstart.rules [03:36] that's a base set of rules, maybe more could be added later [03:36] Yep, he's not around ;) [03:37] *grin* === Md [i=md@freenode/staff/md] has joined #upstart === AlexExtreme prays and types reboot into the VM [03:56] it seems my prayers have been answered. it works :) [03:56] way cool! === AlexUpstart [n=alex@88-105-163-121.dynamic.dsl.as9105.com] has joined #upstart [03:59] nothing seems to have gone wrong so far, although hald is being a little more verbose than I would like ;) [04:02] http://frugalware.org/paste/955 === AlexExtreme hopes shutting down will work now [04:05] awesome... it worked :) [04:18] nice === j_ack [n=rudi@p508DB904.dip0.t-ipconnect.de] has joined #upstart === administrator [i=administ@nat/cisco/x-caa28f48ce02a298] has joined #upstart