Hi
On Sat, Aug 14, 2010 at 8:06 AM, <[email protected]> wrote:
> Hello,
>
> First off, thanks to all who have answered my questions in the past.
>
> I don't quite understand the differences between supervisorctl restart and
> supervisorctl reload. Intuitively, I would say that reload means reloading
> the configuration file without restarting the various commands, while
> restarting allows to reload the configuration file and restart specific or
> all the commands. Is that right?
>
No. Reload means shutting down everything and completely restarting
supervisord. Restart does not re-parse the config file. It just stops and
starts whatever you already have configured to run.
If you want to pick up changes to the config file with minimal disruption,
you need the "reread" and "update" commands. BTW, you can always run
supervisorctl help or supervisorctl help <command> to get help.
> In the context of the section
> [fcgi-program:backend]
> command: /app.fcgi
> numprocs:5
>
> If I change numprocs to 10, do I only need a "supervisorctl reload"?
>
No you need to do.
supervisorctl reread
supervisorctl update
>
> If I install a new version of app.fcgi, still named app.fcgi, do I only
> need a "supervisorctl restart backend:*"?
>
yes
>
> When I run the above commands from an apache user, for instance through a
> php script exec("supervisorctl restart backend"), failures occur because
> the sockets are for the user root; Is there a better strategy then
> changing the permissions on the sockets.
>
You could configure supervisord to run as user 'apache'. Or you can set the
permissions on the socket explicitly using the chown and chmod options in
the unix_http_server section.
>
> Thank you
>
> _______________________________________________
> Supervisor-users mailing list
> [email protected]
> http://lists.supervisord.org/mailman/listinfo/supervisor-users
>
_______________________________________________
Supervisor-users mailing list
[email protected]
http://lists.supervisord.org/mailman/listinfo/supervisor-users
