Can I have rgmanager behave differently based on the return code of my init script?
Here are some rules for service script writing: Always return “0” if the status is non-fatal. Rgmanager follows the LSB + OCF RA API draft specifications. That means that 0 is “OK” from running a “status” operation and non-zero is “not OK”. Some scripts do check-restarts of non-critical components from within the “status” check. If you have a “recover” action in a resource agent (resource agent > plain script), rgmanager will try a “recover” operation first (and will fall back to full service restart if recovery fails). A “recover” action is by definition *not allowed* to interfere with other parts of the service. So, if a component X fails, and recovery succeeds, the rest of the service continues running uninterrupted. None of our agents except the nfsclient have recover actions because they’re all considered critical (file systems, IPs, etc.). You could add a “critical” parameter to resource agents and always return 0 if “$OCF_RESKEY_critical” is not set in the script(s), or not allo
