-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
initctl: add JSON status output support #273
Comments
Hmm yeah there would be definite value in that, this is clear. Just a clarification, it returns 0 if the run/task/sysv has started and executed successfully in the current runlevel. I'll see what I can come up with, this in combination with |
Carrying over from #276, and with a cup of fresh coffee in hand. In systemd land they have |
Back on this now. Turns out the exit code from So I'm leaning towards your original proposal, @hongkongkiwi, with the following "twist" to
I believe this should meet your requirements, @hongkongkiwi, please let me know otherwise. |
Not much feedback in this thread, so after some deliberation with my colleague @wkz, we decided the best course of action for this (and #276) is to instead add JSON output support to (With |
Here's an example of how to query the exit code of a service. (If it died because of a signal the output is slightly different.)
|
I would like a way to know if a task is in ready state.
Right now initctl -q will show errorcode for failure and 0 for anything else.
I propose that it should show 0 only for done and a different error code depending on if it's ready or failed.
The text was updated successfully, but these errors were encountered: