Tom Barrett wrote: > 2009/12/14 Chris McDonough <[email protected] <mailto:[email protected]>> > > Please try running supervisor like so: > > supervisord -n -edebug > > This will run it in the foreground with the debug log printing to > stdout, including child process output, which might give you a clue. > > > How should I simulate the php-cgi process dying? I don't know what > constitues an 'unexpected quit'. A simple 'kill <pid>' appears to be an > 'expected quit'.
Nobody could know. I'd just let it run for a while. Note that you can run supervisord in the background but still log at debug level via: supervisord -edebug The log message will end up in supervisord.log - C _______________________________________________ Supervisor-users mailing list [email protected] http://lists.supervisord.org/mailman/listinfo/supervisor-users
