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

Error messages and exit codes #295

Closed
steverweber opened this issue Oct 10, 2013 · 1 comment
Closed

Error messages and exit codes #295

steverweber opened this issue Oct 10, 2013 · 1 comment

Comments

@steverweber
Copy link

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:

$ 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

@mnaberez
Copy link
Member

mnaberez commented Nov 7, 2013

There are two issues mentioned here:

I am closing this issue as a duplicate since we have the ones above.

@mnaberez mnaberez closed this as completed Nov 7, 2013
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