[08:35] <xnox> pfak: with .override files you can change particular stanza, e.g. override just the exec stanza to add more parameters and the rest (pre-/post- start/stop) will be kept.
[08:35] <xnox> pfak: or make a new different job "start on started foo" to have things execute straight after.
[08:36] <xnox> pfak: what job do you want to append to? and what do you want to append?
[13:02] <Trevinho> Hey... Since the upgrade to kernel 3.10 in saucy. I can't boot anymore using the normal mode... (see bug #1195687), is that somewhat known?
[13:03] <Trevinho> Using the recovery mode works instead...
[13:30] <jodh> Trevinho: please see the latest comment on the bug.
[13:33] <Trevinho> jodh: I think I'm unable to boot... All I get it's a black screen (i didn't check withot quiet yet  but it seems like a problem in initializing plymouth), checking that though, thanks
[13:34] <Trevinho> jodh: what's the best way for you to make me get the console log?
[13:35] <jodh> Trevinho: I don't know what hardware, etc you have - can you just confirm whether there is a crash shown onscreen when you remove 'quiet' and 'splash'? if so, a photo attachment is good enough.
[13:35] <Trevinho> jodh: ok
[13:41] <Trevinho> jodh: unfortunately I'm getting a black screen...
[13:41] <Trevinho> jodh: also removing splash and quiet I'm getting a fast log, then the screen gets blank
[13:43] <Trevinho> (and nothing in /var/crash this time)
[13:50] <jodh> Trevinho: can you ctrl-alt-f1/f2? do the caps-lock/num-lock lights still work? is the system accessible via ssh? please could you add those details to the bug.
[13:50] <axyelp> how do i add a random number to my exec script? using env VARIABLE=$((RANDOM%100) doesn't work
[13:54] <Trevinho> jodh: mh, ok, I'll check that... 
[13:55] <Trevinho> jodh: however I've found what's blocking init
[13:55] <Trevinho> jodh: I'm using the custom cmd line for linux radeon.audio=1
[13:55] <Trevinho> jodh: removing that it boots with normal boot profile..
[13:55] <Trevinho> jodh: that's weird btw... as it seems to work in recovery
[13:58] <axyelp> any way to use random values in upstart?
[14:01] <jodh> axyelp: 'env' doesn't pass the variable value through a shell for expansion, but you can obviously set variables in a script section. If this is a Session Init job however, you *can* do what you want though by having your job call "initctl set-env VARIABLE=$((RANDOM%100))" in say the pre-start section, and that would then be available to all other sections.
[14:02] <Trevinho> jodh: just checked... not using hdmi audio in recovery mode so it seems mostly a kernel issue.. mh
[14:07] <axyelp> jodh: thanks? is there anything specific to import before using it? adding the line breaks the script
[14:09] <jodh> axyelp: before using initctl? no. breaks how?
[14:10] <axyelp> jodh: by printing 'start: Job failed to start'
[14:10] <jodh> axyelp: run init-checkconf /etc/init/your-job.conf
[14:12] <axyelp> jodh: it does say syntax ok!  here's the script - http://pastebin.com/dKb2thLM
[14:15] <jodh> axyelp: RANDOM is a bash-ism. see http://upstart.ubuntu.com/cookbook/#changing-the-default-shell
[14:15] <axyelp> i'm trying with $(od -An -N2 -i /dev/random). sigh!
[14:15] <axyelp> jodh: alright! will try that too!
[14:25] <axyelp> jodh: well! /dev/random did the trick! thanks! :)
[14:25] <jodh> axyelp: np.
[16:31] <pfak> xnox: libvirt-bin, i actually wanted to prepend ..
[16:34] <xnox> pfak: prepend to exec line should be easy..... inside script doable.... pre-start/pre-stop - well hard
[16:34] <xnox> pfak: best edit it inline imho.
[16:34] <pfak> ah
[16:34] <pfak> I just copypasted the stanza
[16:35] <pfak> http://paste.pfak.org/6ea4QJXb
[16:35] <pfak> that look proper?
[16:36] <xnox> pfak: yes.
[16:36] <pfak> sweet!
[16:38] <jodh> pfak: you might want to add "|| :" to the end of that ovs-vsctl line in case grep fails say.
[16:38] <pfak> ovs-vsctl show | grep 'Port \"vnet.\"' | awk -F\" {'print $2'} | xargs -I {} ovs-vsctl del-port {} || :
[16:38] <pfak> ?
[16:40] <jodh> pfak: if any of those commands fails, the pre-start will fail, and your job will fail since upstart runs all scripts with "sh -e". See http://upstart.ubuntu.com/cookbook/#debugging-a-script-which-appears-to-be-behaving-oddly
[16:41] <pfak> sexy
[16:41] <pfak> (you'll have to pardon me for not rtfmin'g the WHOLE upstart guidebook)
[16:44] <pfak> well, hopefully that fixes my problem
[19:45] <JoeJulian> I created this conf expecting that as a "task" it would finish before prefdm tries to start. I'd like prefdm to block until this script is finished, otherwise it starts with system defaults instead of the preset user config I want for my users.  http://ur1.ca/ei0a7
[19:46] <JoeJulian> It seems to work most of the time, but not reliably.
[19:46] <JoeJulian> I also don't want to modify the packaged prefdm.conf 
[19:47] <JoeJulian> Oh, and this is the centos rpm, upstart-0.6.5-12.el6_4.1.x86_64
[19:48] <pfak> Can't you just use an override?
[19:49] <JoeJulian> searching...
[19:50] <JoeJulian> Looks like no. Apparenly that comes with 1.3
[19:52] <JoeJulian> Hmm, maybe I'll try it anyway. There is a ".override" string in /sbin/init
[19:52] <pfak> :\ too bad
[19:52] <pfak> Ah!
[19:53] <JoeJulian> And if I'm reading this correctly, I can just put the stanza that I want overriden in the .override and the rest will run from the original?
[19:54] <pfak> yes
[20:02] <JoeJulian> perfect. Thanks pfak. That was the bit I needed.
[20:02] <pfak> It worked? Great.
[20:21] <xnox> JoeJulian: hmm... to block a job foo with your own task, you make your job "start on starting foo"
[23:21] <JoeJulian> xnox: that's the way it was set, but it wasn't always consistent. (yes, it's been hours... Too many channels open and it was scrolled below the window.)