-
Notifications
You must be signed in to change notification settings - Fork 1
/
supervisord.conf.templ
35 lines (29 loc) · 1.53 KB
/
supervisord.conf.templ
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
[unix_http_server]
file=/tmp/supervisor.sock ; path to your socket file
username = ${HTTP_USER}
password = ${HTTP_PASSWORD}
[inet_http_server]
port=9101
username = ${HTTP_USER}
password = ${HTTP_PASSWORD}
[supervisord]
logfile=/data/log/supervisord.log ; supervisord log file
logfile_maxbytes=50MB ; maximum size of logfile before rotation
logfile_backups=10 ; number of backed up logfiles
loglevel=error ; info, debug, warn, trace
pidfile=/var/run/supervisord/supervisord.pid ; pidfile location
nodaemon=false ; run supervisord as a daemon
minfds=1024 ; number of startup file descriptors
minprocs=200 ; number of process descriptors
user=fetchmail ; default user
childlogdir=/data/log/ ; where child log files will live
[rpcinterface:supervisor]
supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface
[supervisorctl]
serverurl=unix:///tmp/supervisor.sock ; use a unix:// URL for a unix socket
; This is where you run individual Tornado instances.
; We run four; one per processor core.
; In development, we ran as many as four per core with no issues.
; If you're looking to minimize cpu load, run fewer processes.
; BTW, Tornado processes are single threaded.
; To take advantage of multiple cores, you'll need multiple processes.