We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ERROR (already started) is harsh.
This should not be ERROR. We are trying to ensure the state is started! And it turns out its already in that state.
for instance
$ sudo service nginx start * Starting nginx nginx $ sudo service nginx start * Starting nginx nginx $ sudo service networking start start: Job is already running: networking
No errors!
how about started already like:
started already
$ sudo supervisorctl start fedoracommons fedoracommons: started $ sudo supervisorctl start fedoracommons fedoracommons: started already
This is clear and simple to parse/read.
Another issue is the lack of exit codes
nosuchthing: ERROR (no such process) s8weber@c3:~$ echo $? 0
I feel /real/ errors should have an exit code != 0.
linked issue in ansible ansible/ansible#3977 (comment) #296
The text was updated successfully, but these errors were encountered:
There are two issues mentioned here:
I am closing this issue as a duplicate since we have the ones above.
Sorry, something went wrong.
No branches or pull requests
ERROR (already started)
is harsh.
This should not be ERROR. We are trying to ensure the state is started! And it turns out its already in that state.
for instance
No errors!
how about
started already
like:This is clear and simple to parse/read.
Another issue is the lack of exit codes
I feel /real/ errors should have an exit code != 0.
linked issue in ansible
ansible/ansible#3977 (comment)
#296
The text was updated successfully, but these errors were encountered: