Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

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

I'm trying to get it supervisord running on my Mac. The instructions call for using a $BINDIR path variable and I can't figure out what that should be. I tried using the directory I got from $ which python, which = /Library/Frameworks/Python.framework/Versions/2.7/bin/, but when I use that I get an error:

$ /Library/Frameworks/Python.framework/Versions/2.7/bin/supervisord: No such file or directory

From the docs:

This section makes reference to a BINDIR when explaining how to run the supervisord and supervisorctl commands. This is the “bindir” directory that your Python installation has been configured with. For example, for an installation of Python installed via ./configure --prefix=/usr/local/py; make; make install, BINDIR would be /usr/local/py/bin. Python interpreters on different platforms use a different BINDIR. Look at the output of install if you can’t figure out where yours is.

share|improve this question
up vote 4 down vote accepted

Have you installed supervisord yet? If not, it would be a good idea to create a virtual environment and then install into that. With a virtual environment, it doesn't matter so much where you put tools (especially when you are trying them out) and you don't get piles of conflicting libraries all installed in the same place.

If you haven't installed anything at all yet, I would suggest:

  • Homebrew to provide the base tools
  • virtualenv via brew virtualenv
  • Create a virtual environment for supervisord: virtualenv supe
  • Activate it: cd supe; . bin/activate ##note the dot, it matters
  • Install supervisord using pip: pip install supervisord
share|improve this answer
khoxsey- Thanks- I ended up finding supervisord in /usr/local/bin/ - but prob good advice on virtualenv. Though why would I need to install supervisord into a virtualenv? Can't virtualenvs be created anytime, unrelated to where things are installed? – Yarin Aug 15 '12 at 11:28
The best reason to install supervisord into a virtualenv rather than in the system python is to control the runtime environment. In your case, you have no control over what Apple does with the OSX system python, so a venv allows you to control what is in, and what is out. But you're right, it is a personal preference. – khoxsey Aug 15 '12 at 16:22
supervisor is installed without the d in the pip install command – repalviglator May 27 '14 at 18:18

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.