[07:03] <scathen^C> hey all can you use upstart on debian 7?
[09:08] <vanguarde9> Hey guys I need a hint , i want to use some bash scripting in pre start stanza
[09:08] <vanguarde9> if I put there command which return 1 
[09:09] <vanguarde9> start of upstart service of course fails
[09:09] <vanguarde9> what is the recommended way ? to use bash script in pre start stanza ?
[09:12] <vanguarde9> something like this http://pastebin.com/H1R9pT3u
[09:41] <vanguarde9> ok i have found solution
[09:44] <xnox> vanguarde9: egrep "abc" /etc/hosts && do_some_stuff || true
[09:59] <vanguarde9> yes you have right ,  i have found this article http://superuser.com/questions/597549/grep-fails-in-upstart-script
[10:00] <vanguarde9> It would be great if this info was in FAQ
[10:01] <vanguarde9> however thanks ;)
[10:03] <xnox> vanguarde9: it's in the cookbook.
[10:03] <xnox> vanguarde9: http://upstart.ubuntu.com/cookbook/
[10:04] <xnox> vanguarde9: all scripts are running with equivalent of $ set -e
[19:57] <crankharder> how do I deal with a process that is expected to 1) maintain its own pid file that's always up to date 2) spawns replacements for itself and dies off
[19:57] <crankharder> basically, my process is doing the above, but upstart thinks it's died, since the original process is gone, so it spawns another process
[19:57] <crankharder> that all said, I *do* want upstart to spawn a new process if the PID represented in the pid file isn't running
[20:52] <crankharder> it also doesn't help that I can't set the user a script is run as, instead havint to restort to:  exec su - username -c "..." -- which evidentally counts as one fork
[20:56] <crankharder> pretty sure this could all be solved if I were able to just tell upstart the name of the PID file to check for the current PID.  is that possible?
[21:09] <codygman> Does upstart respect environmental variables set by .bashrc?
[21:12] <codygman> It seems not to, because I can run a Django site which gets settings from environmental variables in an interactive ssh session but it fails because it doesn't respect the environmental variables in upstart.
[21:14] <codygman> I seem to have found my answer at http://upstart.ubuntu.com/cookbook/#id94
[21:14] <codygman> of course my upstart installation doesn't seem to have commands such as initctl get-env
[21:15] <codygman> Running upstart '1.5-0ubuntu7.2' on 'Ubuntu 12.04.2 LTS \n \l'