[00:08] <jbalonso1> Anyone here know how to increase the available filehandles for upstart itself?
[00:08] <jbalonso1> (I'm running on Ubuntu Raring)
[00:09] <jbalonso1> I have a great number of jobs I'm trying to manage with upstart, and I've found that upstart is losing file handles to (rather useful) log files. When init runs out, /sbin/init spins at 100% and is unresponsive.
[16:11] <jackhill> Hi, I have a service that I am trying to write a configuration for.
[16:16] <jackhill> However, it doesn't behave correctly if I use expect fork or expect daemon. The PID reported by upstart is different than what I observer the service to be running as in ps.
[16:16] <jackhill> Also, a symptom of this is that I can't get upstart to stop the service.
[16:16] <jackhill> It works "correctly" if I tell the service to run in the foreground and omit the expect directive.
[16:17] <jackhill> My question is: is there a tool see if a service forks or double forks or does something else weird?
[16:20] <jackhill> Oh, it seems that, occording to the cookbook, there is no ill effect to just running the service in the foreground, so I'll just do that. :)
[18:58] <dylukes> Hey guys, I'm in a bit of a pickle.
[18:58] <dylukes> I have an upstart conf running `exec gunicorn...` inside a script stanza
[18:58] <dylukes> and a bunch of env variables declared outside
[18:59] <dylukes> I want those variables to be visible inside the exec. Is there any way to do this? Alternatively I can have the same variables in a .env file, but I can't figure out how to exec that file and have those visible to the exec'd gunicorn task
[19:04] <dylukes> hm, now they seem to work
[19:33] <dylukes> ah, no they aren't :p
[21:37] <jbalonso1> dylukes: Did you export your env variables prior to the exec?