Thanks. The missing command was "update" which resolved the question!
E.
On Nov 9, 2011, at 7:02 AM, David Birdsong wrote:
> program foo looks like it will work, not sure about test. nfcapd might
> need to be a fully qualified path, also will it just exit?
>
> regardless, i think you need to run 'add'.
>
> a shortcut for this case, but not always safe to run is 'update', it
> will add and start anything available (as long as the default program
> setting autostart=true is not set to false.)
>
> On Tue, Nov 8, 2011 at 9:34 PM, Emanuele Paolini
> <emanuele.paol...@gmail.com> wrote:
>> I don't understand how to start using supervisor.
>>
>> I added two testing programs, one in supervisor.conf and one in conf.d. Here
>> is my session with supervisorctl:
>>
>> $ sudo supervisorctl
>> supervisor> avail
>> foo avail auto 999:999
>> test avail auto 999:999
>> supervisor> start foo
>> foo: ERROR (no such process)
>> supervisor> start test
>> test: ERROR (no such process)
>> supervisor>
>>
>> here is my configuration (which is the default in ubuntu with few lines
>> added):
>>
>> [unix_http_server]
>> file=/var/run//supervisor.sock ; (the path to the socket file)
>> chmod=0700 ; sockef file mode (default 0700)
>>
>> [supervisord]
>> logfile=/var/log/supervisor/supervisord.log ; (main log file;default
>> $CWD/supervisord.log)
>> pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default
>> supervisord.pid)
>> childlogdir=/var/log/supervisor ; ('AUTO' child log dir, default
>> $TEMP)
>>
>> ; the below section must remain in the config file for RPC
>> ; (supervisorctl/web interface) to work, additional interfaces may be
>> ; added by defining them in separate rpcinterface: sections
>> [rpcinterface:supervisor]
>> supervisor.rpcinterface_factory =
>> supervisor.rpcinterface:make_main_rpcinterface
>>
>> [supervisorctl]
>> serverurl=unix:///var/run//supervisor.sock ; use a unix:// URL for a unix
>> socket
>>
>> ; The [include] section can just contain the "files" setting. This
>> ; setting can list multiple files (separated by whitespace or
>> ; newlines). It can also contain wildcards. The filenames are
>> ; interpreted as relative to this file. Included files *cannot*
>> ; include files themselves.
>>
>> [include]
>> files = /etc/supervisor/conf.d/*.conf
>>
>> [program:foo]
>> command=/bin/cat
>>
>> ;; the following in conf.d/test.conf:
>>
>> [program:test]
>> command = nfcapd -p 9999 -l /tmp -x "echo ugh"
>> autostart=true
>> autorestart=true
>>
>> _______________________________________________
>> Supervisor-users mailing list
>> Supervisor-users@lists.supervisord.org
>> http://lists.supervisord.org/mailman/listinfo/supervisor-users
>>
_______________________________________________
Supervisor-users mailing list
Supervisor-users@lists.supervisord.org
http://lists.supervisord.org/mailman/listinfo/supervisor-users
