[02:17] <twb> When translating an LSB init script, does "Required-Start:    mountkernfs $local_fs" equate to "start on local-filesystems"?
[02:22] <twb> Hmm, ufw seems to use "start on (starting network-interface
[02:22] <twb>           or starting network-manager
[02:22] <twb>           or starting networking)"
[02:23] <twb> The comment says "# Make sure we start before an interface receives traffic", but I don't see how "starting" GUARANTEES that the ufw job will complete before any interface is up
[17:53] <yml> Hello I am trying to write an upstart script to start/stop my uwsgi instance : http://dpaste.de/jdNF/
[17:54] <yml> For some reason the it does not start. I have copied that file in /etc/init/
[17:54] <yml> yml@toulouse:~$ start -v usgi_emperor
[17:54] <yml> start: Unknown job: usgi_emperor
[17:55] <yml> is there a way to get more verbose error about the error
[18:55] <ion> You’ll probably find a parse error message in syslog. Btw, you’ll most likely confuse Upstart by using ‘expect fork’ and having a main process that doesn’t behave as the expect stanza claims.
[18:56] <yml> I see
[19:00] <yml> ion: what is the log file that i need to look at ?
[19:00] <ion> Try /var/log/syslog
[21:11] <nfearnley> I'm trying to write an upstart conf file, but I don't understand what happens when I tell a service to stop. When I tell it to start, it runs the pre-start script, then runs exec line, then runs the post-start script. When I tell it to stop, it runs the pre-stop script, does ???? to halt the service, then runs the post-stop script. Can someone fill in the blank?
[21:29] <JanC> nfearnley: it kills the process
[21:32] <JanC> well, first a TERM signal, then if that didn't work a KILL signal IIRC
[21:34] <JanC> you can set the timeout before KILL with the "kill timeout" stanza (see init(5) for that)
[22:14] <nfearnley> Thank you.