[01:56] <cwillu_at_work> when did upstart start doing it's own permission checks in addition to dbus?
[01:57] <cwillu_at_work> I used to have a dbus rule to permit a specific user to start a job, but that doesn't work anymore
[01:57] <cwillu_at_work> "start: You do not have permission to modify job:  xxx"
[01:57] <cwillu_at_work> as opposed to "start: Rejected send message, 1 matches rules; type =..." that you get if dbus didn't permit the message send
[01:59] <cwillu_at_work> more importantly I guess, how do I turn it off?
[14:47] <jmacdonald> hello
[15:47] <james_woods> (I googled for about 20 minutes without luck) I need to set my $PATH variable so that upstart can execute the right binary, but it keeps ignoring it. Any idea why? https://gist.github.com/james-woods/f5207bcc1ac5b81f69f6
[15:51] <jodh_> james_woods: http://upstart.ubuntu.com/cookbook/#see-the-environment-a-job-runs-in, http://upstart.ubuntu.com/cookbook/#checking-how-a-service-might-react-when-run-as-a-job, http://upstart.ubuntu.com/cookbook/#determining-why-your-service-fails-to-start. At a guess I'd say it might be because you have not set $HOME. Why ipython rather than python? Also, you may be able to remove that sudo call and use the
[15:51] <jodh_> setuid stanza: http://upstart.ubuntu.com/cookbook/#setuid
[16:09] <james_woods> jodh_: thanks
[16:09] <james_woods> :)
[21:18] <niram> hi, i am trying to setup socket activation for php-fpm
[21:18] <niram> but it doesn't seem to work
[21:19] <niram> i have added: start on socket PROTO=unix PATH=/var/path/to/socket
[21:19] <niram> and: env FPM_SOCKETS=/var/path/to/socket
[21:19] <niram> i am getting strange behavior.. sometimes the daemon starts right away
[21:19] <niram> other times it doesn't start at all
[21:20] <niram> never actually starts when the socket is accessed