=== zz_Kiall is now known as Kiall
[12:59] <six86> hi
[13:00] <six86> one question to upstart: i want a job that starts other jobs for convenience, but it doesnts work. Can someone help?
[13:07] <SpamapS> six86: perhaps you could share the job as you have it now?
[13:09] <six86> i have around 5 jobs, all part of the whole system. to start this jobs i want one that starts them all
[13:10] <six86> http://pastebin.com/LshrGktj
[13:14] <six86> it seems as if the jobs are executed, but i cannot check status nor stop them bz name
[13:14] <six86> by name
[13:18] <SpamapS> six86: start on startup is wrong, btw
[13:18] <SpamapS> six86: that event is emitted before filesystems are mounted, before networking is up..
[13:23] <six86> the start on is currentlz not important and will be changed later. The interesting question is, if i can start multiple services in one job and the track them individually with start/stop/status 
[13:38] <SpamapS> six86: ok, you're kind of doing it backwards
[13:39] <SpamapS> six86: instead of putting a bunch of starts in that job...
[13:39] <SpamapS> six86: (which should work)
[13:39] <SpamapS> six86: how about changing the other jobs to 'start on starting meta-aggregate-job-name'
[13:39] <SpamapS> six86: and then 'stop on stopping meta-aggregate-job-name'
[13:39] <SpamapS> six86: then you don't even need a script section
[13:40] <SpamapS> six86: it just becomes a job to help start/stop them together
=== Kiall is now known as zz_Kiall
=== zz_Kiall is now known as Kiall
[13:57] <six86> thats a good idea, thx. I will try that tomorrow
[17:26] <cubicool> Is there a way in upstart to run a curses-based application before lightdm ever starts? I realize I need to make my curses app be a dependency of lightdm, but I can't actually get my upstart job to "grab the foreground", so to speak.
[17:27] <cubicool> I know everyone will say "why", but I need to accomplish this in a corporate setting; a few pre-X functions must be executed on the employees first boot.
=== Kiall is now known as zz_Kiall
[17:45] <benzittlau> hey, I'm trying to get the PID of the current process inside a pre-stop block
[17:45] <benzittlau> i
[17:45] <benzittlau> is there a straightforward way to get that without having to write the PID to a file?
[17:48] <SpamapS> benzittlau: status
[17:48] <SpamapS> benzittlau: it is every easy to parse
[17:49] <SpamapS> cubicool: if you want it to grab the actual console, you need to make it 'console owner'
[17:49] <SpamapS> cubicool: and you have to make *sure* it is the *only* console owner
[17:50] <benzittlau> SpamapS: happen to know of any snippet for parsing out the PID?  I'm sure I could figure it out, but it would save me some time
[17:50] <SpamapS> cubicool: 'start on starting lightdm' should be enough, but you may have to also add in some stuff about plymouth to make sure you get the console
[17:53] <SpamapS> benzittlau: x=$(status); pid=${x##*, process}
[17:53] <benzittlau> thanks!
=== zz_Kiall is now known as Kiall
=== Kiall is now known as zz_Kiall