Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Perhaps I'm misunderstanding with Supervisor does, but perhaps me asking this question will help clear that up. Basically, I have a Supervisor program in my /etc/supervisord.conf file that executes a bash script which simply executes a PHP script. I've been able to successfully get that bash script to run from supervisor only upon launch of supervisor. However, isn't the point of something like supervisor that it runs that tasks in the background at set intervals or something so that I can know it's always running and handling any tasks it might need to according to the script it runs?

Here is the program in my conf file:

share|improve this question

It sounds to me like what your actually looking for is closer to cron. I'm not familiar with supervisor but from the description provided here, it sounds it is trying to be a userspace replacement for certain aspects of init. By this I mean that it focuses in providing:

  • start/stop/restart of services(programs)
  • Automatic program crash detection and restart
  • Controlling the start order of various programs at boot.
  • Delegating management of services to the people who work with them (aka giving web server reboot-rights to the web devs).
share|improve this answer
That's right. joshholat is mistaking supervisor as a cron-replacement. Supervisor knows how to do such things but they're intended to support process control (e.g. have a look at the superlance plugin suite). – Theuni Dec 7 '12 at 18:19

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.