Initscript cleanup #1
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
https://bugzilla.redhat.com/show_bug.cgi?id=786865 In the event that the thin process has died for some reason, service status will report: > # service aeolus-conductor status > is stopped The use of a LOCKFILE corrects the output, in addition to improved handling during system shutdown (/etc/init.d/killall): > # service aeolus-conductor status > aeolus-conductor dead but subsys locked
|
This appears to have been merged already back in Feb, 2012. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Greetings,
Just a small set of fixes to the aeolus-conductor initscript to improve operation during system reboots, and improve status reporting when conductor (thin) has died.
I previously sent this to aeolus-devel@ in October, please disregard that patchset. This pull request applies cleanly to origin.
Thanks,
James