[00:47] <greylurk> So, i'm trying to write an upstart script for a process, and it appears to fork 56 times before settling in to a single PID.  Is there any hope of writing an "expect" statement to deal with it?
[00:56] <ion> Can you tell it not to do that? :-P
[00:56] <greylurk> I'm not sure… I'm trying.
[00:56] <JanC> seems like that process is somewhat insane  ;)
[00:56] <greylurk> It's actually "clone"ing not "fork"ing, so it might just be a bunch of threads to read configurations and such.
[00:57] <greylurk> I'm investigating.
[00:59] <JanC> there are always tricks with pre/post start/stop & script you can use (see the cookbook for some ideas)
[04:04] <swine_> hey, what would cause a pre-run section of an upstart config file not to ever run ?
[07:25] <roderick__> hi, is there a way to give an instance a default value in the upstart script, so it's optional for "start myapp ..."?
[10:49] <qzio> I'm trying to get nginx to use upstart, not sure what I've done but doing start nginx or stop nginx just sits there doing nothing.
[10:49] <qzio> can't find anything in syslog either, or the nginx log.
[10:49] <qzio> I've installed nginx using the passenger gem, so it sits in /opt/nginx.
[10:50] <qzio> I'm using the upstart script described in http://wiki.nginx.org/Upstart with the modification of DAEMON=/opt/nginx/sbin/nginx
[11:56] <JanC> qzio: *s*bin?
[11:56] <JanC> are you sure it's not in /opt/nginx/bin/ instead?
[12:22] <qzio> yes I'm sure.
[12:22] <qzio> I can get nginx to start. but not to stop.