-
Notifications
You must be signed in to change notification settings - Fork 86
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
The exit code for the 'info' command always returns 0 #68
Comments
Not understand what you mean, eye already return different exit codes (from 0.6), maybe you use old version? |
Interesting. I didn't realize that upstart doesn't follow that convention anymore. I just verified that I'm using 0.6.2 from rubygems. I was expecting to see here https://github.com/kostya/eye/blob/master/lib/eye/cli.rb#L22 something like: When I run |
still not understand:
|
if you want to get 0 or 1 if process up or down, there is no such method. |
I think it would be useful for compatibility. Would you like me to put something together and submit a pull request or do you want to tackle it? |
can you test it? i am used correct statuses? |
Yes. Looks good. Thanks for the quick response 👍 |
In the Linux Standard Base, the exit codes are different if the service is running or not running. It would be nice to be able to check the exit code in wrapper scripts. http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html
The text was updated successfully, but these errors were encountered: