Weird, given that it does say it is exiting in the log file. The mixed times is a bit hard to go through, but you can see:
[12908] 2012-01-05 15:55:14.492 INFO: Listening on socket: /tmp/tmp-lp-service-4yBbLy.sock
1.249 ... some stuff about getting a for request
...
[12908] 2012-01-05 15:55:14.526 INFO: Shutting down. Waiting up to 1s for 0 child processes
[12908] 2012-01-05 15:55:14.527 INFO: Exiting
So it started listening at 55:14.492 and shut down at 55:14.527 or about 35ms after it started it sees that it needed to shut down.
Weird, given that it does say it is exiting in the log file. The mixed times is a bit hard to go through, but you can see:
[12908] 2012-01-05 15:55:14.492 INFO: Listening on socket: /tmp/tmp- lp-service- 4yBbLy. sock
1.249 ... some stuff about getting a for request
...
[12908] 2012-01-05 15:55:14.526 INFO: Shutting down. Waiting up to 1s for 0 child processes
[12908] 2012-01-05 15:55:14.527 INFO: Exiting
So it started listening at 55:14.492 and shut down at 55:14.527 or about 35ms after it started it sees that it needed to shut down.
Is there something about buffering going on ?