I've done quite a bit with supervisor over the years. The version bundled in distros is often old and sometimes missing init scripts etc. It is however an ace tool.
I'll fire up a centos box and try and post a gist up.
https://gist.github.com/coldclimate/b9a47aa86fb5dcc79ea1I didn't create an actual job but supervisord comes up cleanly.
Hope this helps,
Hi Jason,I use supervisord at work to control almost all server processes including httpd and fpm - it's certainly rock solid.Can't add much to the above, but the -n flag on supervisorctl is pretty useful - can start supervisord in the foreground and watch what it's doing. Most of the errors I had whilst setting it up involved instructing supervisor to stop a process only to find it's still running.So had to tweak the signal via the "stopsignal" directive.Once configured it really can be left alone. As you can see from the example at the URL above, it can manage it's own logs per process too.
Feel free to shout on here if you have any specific issue, chances are I've had to battle around it.(See also http://laravel.com/docs/master/queues#supervisor-configuration - might help structure the command)