You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my service setup, I have one name with multiple id's.
I'm missing a way to check the status of all services under a particular name.
I think it would make be helpful and logical if initctl status <name> shows not just one service status, but all of the status's relating to that name.
So if I was to write in bash it would be:
for ID in $(initctl ident $MYNAME); do
initctl status "$ID"
done
Specific status can still be checked with initctl status <name>:<id> ofcourse, so hopefully it wouldn't be breaking anything.
I guess at the moment initctl status <name> just shows the first service defined in the config file which just depends on the order it's read.
What do you think?
The text was updated successfully, but these errors were encountered:
Or here's another idea this might be tidier, perhaps initctl status <name> could just show the same as initctl status but only specifically based on the name. Then if you want to drill down you can do initctl status <name>:<id> as now.
I would imagine that initctl -q status <name> would show as 0 only if all ids have success, otherwise 1, this is related to #273
Interesting, turns out we had something similar to this which was changed in e51587c. I'll make sure to honor that change by splitting on :. Original implementation was in #197 ... kinda similar to this one :-/
A test will be added to protect against future regressions.
In my service setup, I have one name with multiple id's.
I'm missing a way to check the status of all services under a particular name.
I think it would make be helpful and logical if
initctl status <name>
shows not just one service status, but all of the status's relating to that name.So if I was to write in bash it would be:
Specific status can still be checked with
initctl status <name>:<id>
ofcourse, so hopefully it wouldn't be breaking anything.I guess at the moment
initctl status <name>
just shows the first service defined in the config file which just depends on the order it's read.What do you think?
The text was updated successfully, but these errors were encountered: