=== robbiew-afk is now known as robbiew === Keybuk_ is now known as Keybuk [15:39] hi, what would be the best option to start an interactive script at boot with upstart? [15:40] ie something similar to 'su -c "/usr/bin/ascript" -l' ? [15:41] lcapriotti: you would need to run it with the console output stanza [15:42] ... any online examples ? [15:42] tks btw [15:43] start on startup [15:43] console output [15:43] exec /usr/bin/ascript [15:43] ^^there's an example :) [15:59] cool, it works :) tks a lot [16:02] now for a more advanced one: what if I need to stop usplash before the script? [16:03] lcapriotti: you would add: [16:03] pre-start exec /whatever/thing/controls/usplash --stop [16:03] or something to that effect [16:03] not an Ubuntu guy ;) [16:04] nice, seems easy once you know what you are doing ;) [16:06] or add "on starting your-script" to /etc/init/usplash.conf ;) [16:06] pre-start exec stop usplash [16:06] would work too [16:08] I prefer not to modify a system script, I'll go for "pre-start exec stop usplash" [16:09] tks a million to both of you! [16:09] np === Md is now known as Guest82827 === Guest82827 is now known as Md [20:29] Keybuk: Hi again! [20:30] I've finally come to working on upstart support in the stb without having had the occasion to talk with you about it :-) [20:32] ...and sadly it doesn't seem we share the same availability hours [20:37] stb? [20:39] system-tools-backends -;) [20:39] ah right [20:39] have you seen bug 435935? [20:40] no, I haven't seen that bug [20:41] that's basically about implementing a rough upstart support, so that services-admin can be shipped in Karmic without breaking things [20:42] I have a patch that works with init.d scripts in Karmic (not upstart jobs yet) [20:42] I'd need some feedback to know if that's good enough that I can release the stb 2.8.2, so that it can go into Karmic [20:47] Karmic is almost past Beta [20:49] yeah, but that one kind of problematic [20:49] we can't break services-admin more than it is now :-) [20:51] sorry, my network connection is really bad [20:51] (public WiFi, not even allowed to use IRC directly) [20:51] did you say something since 21:48? [21:34] Hi Keybuk :-) [21:40] hi [22:18] Is there a way to subscribe to all current and future Upstart blueprints in Launchpad? [22:21] probably not [22:21] blueprint is very underdeveloped [22:21] I don't even use it now === robbiew is now known as robbiew-afk [23:42] Any interesting decisions/news/something from LPC? :-) [23:43] The most recent news at the linuxplumbersconf.org: LPC Registration opens 7:30AM PT Wednesday (come early!) [23:44] haha [23:44] no, it wasn't a great conf this time [23:44] casey and I hung out a bit [23:44] bounced a few ideas [23:45] Has anyone came up with a good name for the ‘like while, but start on starting and stop on stopped’ stanza for upstart+1 yet? :-) [23:45] nope [23:45] but I am going to get rid of pre-start, post-stop, etc. from the state machine :p [23:46] Why? [23:46] because we don't need them anymore [23:46] the blocking stuff added to events really gets rid of the need [23:47] so, let's say we simplify a job down to just a process, and events [23:47] we have [23:47] [ pre-start event ] [ post-start event ] [ pre-stop event ] [ post-stop event ] [23:47] [ process being run here ] [23:47] how would we do a pre-start script? [23:47] easy! [23:47] on job pre-start [23:48] task [23:48] exec ... [23:48] that would block the pre-start event, so block the process being run ;) [23:48] which is exactly what we want [23:49] In that case, it would be nice to be able to put multiple job definitions to a single file, so you’d have the stuff that e.g. does mkdir -p /var/run/dbus in the same file as the stuff that runs dbus. [23:50] Ah, i might have misunderstood. It would still be possible to have pre-start, post-stop stuff in the job definition, it would be just an abstraction that works based on those events? [23:50] exactly! [23:51] even better, it'd be possible to put *any* custom sub-job in the definition [23:51] if we make that really easy, and work well [23:51] Keybuk: the only downside is the hideous things I know people will do with this :) [23:51] sadmac: they can do them already [23:51] Keybuk: on started pre-start job [23:51] just in separate job files ;) [23:51] sadmac: I kinda like that [23:51] while apache pre-start [23:52] (while the apache pre-start script is running) [23:52] :-) [23:52] that one's ok [23:52] actually there'd be no started pre-start, since that would imply a started started, which would imply a started started started... [23:53] or pre-start implies pre-start pre-start implies pre-start pre-start pre-start [23:53] on portmap pre-start pre-start pre-start pre-start [23:53] we should rename that to "turtle" [23:54] ‘while’ for ‘start on started, stop on stopping’; the Old English word ‘hwile’ for ‘start on starting, stop on stopped’ [23:55] Keybuk: rename which? [23:55] on portmap turtle turtle turtle turtle turtle turtle turtle turtle [23:55] turtles all the way! [23:55] gdb.fail++ [23:56] Keybuk: ah [23:56] ‘surrounding’? [23:56] ion: you mean as a name for "before"? [23:57] I’m not sure i like ‘before’. It only means, well, before, which is only the starting point. [23:57] ion: me neither, we've been trying to rename it for months :) [23:58] Keybuk: actually, we may not need before anymore with the new model [23:58] Keybuk: while dbus / while dbus running [23:59] something like that yeah