Differences between reread, reload, restart, update?

[flaugher]

Perhaps I missed it but is there a good explanation anywhere as to the differences between these four commands? I didn't see them discussed in the supervisord online documentation. I've noticed on ServerFault and Stackoverflow that other users don't understand their differences either.

For example, if I change the configuration in one program section, I know I must do "supervisorctl reread" to have those changes made available. But how do you restart just that one program? supervisorctl restart doesn't work. Instead if appears that you must either run "supervisorctl update" or restart the supervisor daemon itself. However, this seems to have the unintended effect of restarting all programs, not just the one that changed.

Thanks.

[mnaberez]

Perhaps I missed it but is there a good explanation anywhere as to the differences between these four commands?

No, this should be added to the documentation. I've added the docs label and will leave this issue open so we do that.

[bfleming-ciena]

Still find the current docs confusing.

[pawelad]

What helped me - http://www.onurguzel.com/supervisord-restarting-and-reloading/

[bfleming-ciena]

Thank you, friend.

…

On Tue, Dec 13, 2016 at 7:35 AM, Paweł Adamczak ***@***.***> wrote: What helped me - http://www.onurguzel.com/supervisord-restarting-and- reloading/ — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#720 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEgNpM6R9BMwE03q_DejU96qUOef8zCtks5rHrtMgaJpZM4HZsaj> .

[pawelad]

@flaugher I still think it's worth keeping this issue open, as the docs still don't have the relevant information.

I was actually planning to look into making a PR on the weekend.

[flaugher]

If you want to re-open it, go ahead. I didn’t see anything new and have moved beyond the issue and didn’t want to keep getting notifications. I couldn’t figure out how to mute it so I just closed it.

…

On Dec 13, 2016, at 4:03 PM, Paweł Adamczak ***@***.***> wrote: @flaugher I still think it's worth keeping this issue open, as the docs still don't have the information. I was actually planning to look into making a PR on the weekend. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.

[pawelad]

As a non project member or issue creator I can't open it, but I do get your point completely.

BTW - As far as I know you can unsubscribe from the notifications on the right side menu in issue view

Lastly - sorry for the spam : -)

[ivanleoncz]

Hi everyone.

IMHO, I agree with the re-opening of this issue.

Although the doc bellow can shed a light on the issue, it seems a little bit vague regarding the definitions.

Regarding the "update" action, I believe that there are more things to be described or better described, for example.

Here is the scenario: when you create a configuration for a process to be managed by "supervisord", you run "supervisorctl update" and then comes the message "your_configured_process: added process group". Is there any kind of group controlled by "supervisord", which must contain a record that specifies that your process is now managed by "supervidord"?

• http://www.onurguzel.com/supervisord-restarting-and-reloading/

In my last searches on Google, I also found this man page at Ubuntu website, and it doesn't seem to have explanations for supervisorctl actions..

• http://manpages.ubuntu.com/manpages/xenial/man1/supervisorctl.1.html

Can anyone (member of the project) reopen this issue? Seems like that I'm not the only one who believes that this must be done.

Thanks
@ivanleoncz