=== mjg59_ [n=mjg59@cavan.codon.org.uk] has joined #upstart === Amaranth_ [n=travis@ubuntu/member/amaranth] has joined #upstart === Amaranth [n=travis@ubuntu/member/amaranth] has joined #upstart === yondalf [n=jonathan@219.94.58.74] has joined #upstart === j_ack [n=rudi@p508D8DDE.dip0.t-ipconnect.de] has joined #upstart === juergbi [n=juerg@80-219-26-249.dclient.hispeed.ch] has joined #upstart === mjg59_ is now known as mjg59 === SaintN [n=b@202-161-3-146.dyn.iinet.net.au] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === SaintN [n=b@202-161-3-146.dyn.iinet.net.au] has left #upstart [] === nibil [n=bil@adsl-static-3-105.uklinux.net] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === Amaranth [n=travis@ubuntu/member/amaranth] has joined #upstart === j_ack [n=rudi@p508D8DDE.dip0.t-ipconnect.de] has joined #upstart === mbiebl [n=michael@dslb-084-056-210-048.pools.arcor-ip.net] has joined #upstart === wasabi_ [n=wasabi@ubuntu/member/wasabi] has joined #upstart === j_ack [n=rudi@p508D8DDE.dip0.t-ipconnect.de] has joined #upstart === Md [i=md@freenode/staff/md] has joined #upstart === maro_ [n=mark@0x55511dab.adsl.cybercity.dk] has joined #upstart [06:00] Keybuk: regarding the script syntax, have you considered using a make-like syntax instead? [06:00] oh please no [06:03] maro_: I think I share thom's response here ;) [06:03] DEPENDENCIES := foo [06:03] DEPENDENCIES += bar [06:03] start:: [06:03] some script [06:03] i couldn't imagine anything more hideous, personally. but you could have some fun [06:03] .EXEC: /sbin/some --daemon [06:04] actually, that'd be illegal, you'd need \t before "some script" :) [06:04] thom: X. M. L. [06:05] vpath %.event \ /etc/event.d/ ; %.event: ... [06:05] Keybuk: true [06:06] Keybuk: no, that wasn't what I meant :) [06:06] it was only for the "start script"/"end script" stanza [06:06] maro_: elaborate [06:07] I was initially confused with the "start script" wording since I thought it meant "start of script" (versus "before running the command") [06:08] Keybuk: http://borkware.net/~mark/upstart-service.txt [06:12] (refresh) [06:12] the trouble there is the requirement for indentation and physical tabs [06:14] python fans will love it, though ;) [06:16] my guess is that most distros/users will be consistent in their indentation anyway, and enforcing it will make 3rd party supplied event scripts more consistent [06:17] anyway, that's just my POV, you're the code monkey :) [06:19] btw, the 'while' thing is mainly to avoid "start on this-up", "stop on this-down" [06:20] <_ion> I'm not very fond of the pythonish way of indentation. [06:21] can we please not have a pointless indentation debate [06:21] yeah :) [06:21] the problem with make like indentation is that some poor user will always cock it up and then get really, _really_ confused [06:24] my main liking about it is that it's more human/language-friendly to use a colon, and it saves a line for each script - screw the indentation :) [06:25] (the only argument I can see for that is that the people who edit event scripts are likely to already be familiar with make syntax) [06:27] maro_: i don't think that's particularly likely; think about the poor sysadmin who needs to knock up an event script quickly [06:30] what about the poor sysadmin that though "start script" was the syntax for beginning any script block since it's stopped with "end script"? (e.g. me ;)) [06:31] there's a more interesting problem that "start script" implies the script should start the daemon [06:31] anyway, screw the make syntax part, what do you think about "while"/"when"? [06:31] it's planned to be renamed to pre-start and post-start anyway, which should make things clearer [06:32] Keybuk: true :) [06:32] while/when ? [06:32] Keybuk: the first non-commented line in the file [06:35] also allowing "functions" to be either script blocks or binaries ("run" in that file) [06:35] "while X is Y" doesn't make sense ... events are one-shot occurrences [06:36] Keybuk: hal would run "while dbus is running" [06:37] i.e. respawn if it dies, and stop when dbus is no longer running [06:37] what is "dbus" in this context? [06:37] system bus is available :) [06:38] but what is that? [06:38] it's not an event [06:38] the start/stop of it is, but yeah, point taken [06:39] start on job-started dbus [06:39] stop on job-stopped dbus [06:39] start on job-failed self [06:39] accomplishes much the same thing [06:40] though not quite, interestingly [06:40] and which one is nicer to read/understand? :) [06:40] maro_: I'd say yours is easier to read, but mine is easier to understand [06:41] I really like the "start on job-failed self" thing instead of exec/respawn :) === x4NothinKx [n=stefan@p57A2E0DD.dip.t-dialin.net] has joined #upstart [06:42] hi [06:42] is mahangu there? [06:43] how does "when storage is added" look like? [06:43] "on storage-added"? [06:43] define "added" [06:43] you have block-device-added, or path-mounted, etc. [06:44] depending what you name those events [06:44] that's set by the storage event (and could be anything) [06:44] are all those files in /etc/event.d? :/ [06:46] <_ion> Huh? [06:46] no, those are events [06:48] ah, right, "arbitrary strings" - I need coffee :) [06:48] could someone tell me when mahangu is regular in the channel? [06:48] also see https://wiki.ubuntu.com/UpstartDesignChanges [06:48] that details where we're thinking of going with them [06:49] i want to do the documentation and german translation for upstart [06:50] looking at it, thanks :) [06:51] x4NothinKx: https://launchpad.net/products/upstart/main/+pots/upstart/de/+translate [07:03] Keybuk: btw, I noticed that initctl list doesn't remove moved files [07:03] (in current upstart, obviously) [07:04] s/moved/re&/ [07:05] right [07:05] known bug [07:05] ok, as long as it's considered a bug :) [07:05] or moved files, actually ;) [07:06] or both :) [07:06] yup, it's actually just a lack of implementation [07:06] e.g. should a job be stopped if you remove its file? :) [07:06] hmm, good question [07:07] I'll avoid thinking about that, might get a headache [07:07] <_ion> IMO definitely yes (unless it's only renamed) [07:07] _ion: in which case... should it be restarted? [07:08] <_ion> I don't see a reason to restart it. [07:08] nah, true, initctl should just list the new name [07:08] <_ion> Just change the job's name in memory. [07:08] they're not restarted when modified [07:09] so in theory they probably shouldn't be when renamed [07:09] <_ion> Yep. [07:09] agree completely [07:10] I'd hate to upgrade initscripts if they were ;) [07:12] Keybuk: I also get a ton of hal noise on my console even when using "console null" - I guess hal's helpers are to blame? [07:14] yes [07:19] heh, hal just had pid 666, wonder why [07:23] <_ion> Because it's an integer between 2 and kernel.pid_max [07:23] heh [07:37] i do the translation now [07:37] but i think rosetta is not good [07:38] its very difficult to find matching vocabulary [07:38] because the most words are without a context [07:38] thats a puzzle [07:39] I'm afraid I know little about translation, or the difficulty involved [07:44] some words should be kept in german, like "killed" or so. But some should'nt. I need to test the translation intensively. === pike__ [n=helpdesk@adsl-068-222-206-252.sip.bgk.bellsouth.net] has joined #upstart === j_ack [n=rudi@p508D8DDE.dip0.t-ipconnect.de] has joined #upstart === Amaranth [n=travis@ubuntu/member/amaranth] has joined #upstart === Amaranth [n=travis@ubuntu/member/amaranth] has joined #upstart === pike__ [n=helpdesk@adsl-068-222-206-252.sip.bgk.bellsouth.net] has joined #upstart === Keybuk [n=scott@quest.netsplit.com] has joined #upstart === Amaranth [n=travis@ubuntu/member/amaranth] has joined #upstart === mbiebl [n=michael@dslb-084-056-210-048.pools.arcor-ip.net] has joined #upstart === j_ack [n=rudi@p508D8DDE.dip0.t-ipconnect.de] has joined #upstart === x4Nothin1x [n=stefan@p57A2DC27.dip.t-dialin.net] has joined #upstart === x4NothinKx [n=stefan@p57A2CAC6.dip.t-dialin.net] has joined #upstart === pike__ [n=helpdesk@adsl-068-222-206-252.sip.bgk.bellsouth.net] has left #upstart []