sudo easy_install supervisor

它的配置文件使用;做为注释符

另外有点类似于nginx

使用supervisord -c supervisord.conf这样的方式在后台执行

使用supervisorctl进行命令行的控制，这个有点像redis

看了pycon上的视频，发现自已水平好菜，老外好牛，差距大，还没想到什么方法，只有多写代码来着。

以下reference:

http://lincolnloop.com/blog/2010/jun/24/automatically-running-supervisord-startup/

Automatically Running Supervisord on Startup

I really like supervisord for long-running process management. It is Python, so it is easy to install and it is easy to script with tools like Fabric. Lately I’ve been deploying smaller Django/WSGI sites with Green Unicorn behind Nginx proxied over a Unix socket which makes for a nice little setup on shared hosting and RAM starved VPSes.

After installing supervisord with something like sudo easy_install supervisor, you’ll want to make sure it runs after you reboot your machine (and gets restarted in case it crashes). If you are on a Linux system with upstart (and have root access), you can bypass the ugly init scripts and use this simple file placed in /etc/init/supervisord.conf to manage your supervisord process:

description     "supervisord"start on runlevel [2345]
stop on runlevel [!2345]respawnexec /usr/local/bin/supervisord --nodaemon --configuration /etc/supervisord.conf

Now that it is in upstart, you can start it with the command sudo start supervisord.

If you are on shared hosting, you probably won’t have permissions to do this, but if you have access tocron, you can make sure it gets started in case the server reboots by adding this to your cron jobs:

@reboot   /my/path/to/supervisord -c /my/path/to/supervisord.conf 2>&1

In the event supervisord crashes or is killed off by a sysadmin, you’re out of luck. If this happens, you’ll want to look into having a cron job periodically poll the process pid to see if it is still alive and restart it if it is not. I haven’t needed this (yet), so that is left as an exercise for the reader :)

COMMENTS

• June 24, 2010 at 12:56 p.m. #

  Simon Luijk responded:

  I am using daemontools to monitor gunicorn. When I update my code I send gunicorn a SIGHUP to gracefully reload the code. This creates all sorts of problems. As expected gunicorn starts up a new process and then shuts the original process down. At which point daemontools tries to start gunicorn as it thinks gunicorn has died. I have a tempary hack which I’ll spare you from.

  I have been looking for an alternative and supervisord is high on the list but I have not been able to find anything conclusive on sending signals to monitored processes. What is your experience in getting gunicorn to gracefully reload code with your setup?

• June 25, 2010 at 4:48 a.m. #

  ZeissS chimed in with:

  @Simon: You could use the supervisorctl tool to signal supervisord to restart the process.

• June 28, 2010 at 1:57 a.m. #

  Simon Luijk chimed in with:

  @ZeissS That would stop and start the process and not gracefully reload the code.

  I guess my question is does supervisord get its knickers in a twist if I “kill -HUP `cat /tmp/gunicorn.pid`” like daemontools does?

  Seeing that you can’t give supervisord a pid file for a process, I guess the answer is yes.

GOT SOMETHING TO SAY?

以下reference:http://blog.chinaunix.net/u2/87077/showart_2300645.html

supervisor 管理后台进程

文章分类:Python编程

参考这篇文章

加上一些notes:

1 生成默认conf文件: echo_supervisord_conf > ...

2 启动：superviserd -c 配置文件path 
     eg：supervised -c t.ini 
     配置文件ini格式

3 控制：supervisorctrl -i 
     进入交互模式

用 Supervisor 管理后台守护进程

 2009-05-14, Thursday 17:42 PM |  0 comments |  0 pingbacks |  supervisor, virtual host, webfaction, zine

easy_install supervisor --prefix=$HOME

[supervisord]
logfile = %(here)s/supervisord.log
loglevel = warn
pidfile = %(here)s/supervisord.pid
directory = %(here)s/
childlogdir = %(here)s/childlog[unix_http_server]
file = <YOU-HOME-PATH>/deploy/supervisor/supervisord.sock[rpcinterface:supervisor]
; This section is always necessary because supervisor uses RPC internally.
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface[supervisorctl]
; Must match settings in 'unix_http_server'
serverurl = unix:///<YOU-HOME-PATH>/deploy/supervisor/supervisord.sock[program:blog]
command = <YOU-HOME-PATH>/deploy/zine/bin/python /home/yospaly/deploy/zine/scripts/server -a 127.0.0.1 --no-reloader --no-debugger --threaded -p 6666 -I <YOU-HOME-PATH>/deploy/blog/[program:blog2]
command = <YOU-HOME-PATH>/deploy/zine/bin/python /home/yospaly/deploy/zine/scripts/server -a 127.0.0.1 --no-reloader --no-debugger --threaded -p 8888 -I <YOU-HOME-PATH>/deploy/blog2/

supervisorctl start all
supervisorctl stop blog
supervisorctl restart blog2