-
Notifications
You must be signed in to change notification settings - Fork 445
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
Wrong debian systemv init script exit codes #552
Comments
Thanks for pointing out. Is this not the case for the current |
Just received from a customer:
|
...that's using 1.0.0 |
@mahe-ymc so pull request on any branch are welcome :) |
kardapoltsev
added a commit
to kardapoltsev/sbt-native-packager
that referenced
this issue
Apr 26, 2015
kardapoltsev
added a commit
to kardapoltsev/sbt-native-packager
that referenced
this issue
Apr 26, 2015
muuki88
added a commit
that referenced
this issue
Apr 26, 2015
Fix debian systemV init script status command #552
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This affects sbt-native-packager in version 0.7.4
The init script when run with argument 'status' always returns an exit code 0, no matter in what state the program is in. This is bad, as a caller (e.g. puppet) cannot determine the state of the application. One should change this to exit codes specified by LSB (http://refspecs.linuxbase.org/LSB_3.1.0/LSB-Core-generic/LSB-Core-generic/iniscrptact.html).
Fixing this can easily be done by remembering the status code of "start-stop-daemon --status" and by exiting using the value of that status code and not by the one resulted from "echo". Unfortunately "$?" is not referential transparent :(
I can do a pull request for this by myself if you like.
Thanks, Matthias
The text was updated successfully, but these errors were encountered: