Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unexpected behavior with supervisorctl #759

Closed
Cobraeti opened this issue May 24, 2016 · 1 comment
Closed

Unexpected behavior with supervisorctl #759

Cobraeti opened this issue May 24, 2016 · 1 comment

Comments

@Cobraeti
Copy link

Hi,
I am facing a strange behavior when running supervisorctl status.
Imagine you have at least one process named azertyuiop. I don't have any azertyuiop group and after some test it seems that I can't have a group named like a single process (which is a logical behavior).
When I run supervisorctl azertyuiop azertyuiop:* I get this output:

azertyuiop RUNNING pid...
azertyuiop RUNNING pid...

This strange behavior is really interesting for what I am trying to do as I don't always know if I execute that command for a single process or for a group of processes. This output shows that this information doesn't matter, so I could always run supervisorctl status azertyuiop:* whithout knowing if azertyuiop is a group or a single process.
I would like to know if it was written so or if you might change this in future releases? As I would like to be able to shorten my code thanks to that behavior ^^
Thanks

@mnaberez
Copy link
Member

I would like to know if it was written so or if you might change this in future releases? As I would like to be able to shorten my code thanks to that behavior

There are no current plans to change how supervisorctl works. If we do make a breaking change sometime in the future, we will bump the major version and note it in the changelog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants