3.7.0 HP StorageWorks HP Scalable NAS File Serving Software administration guide - HP Scalable NAS 3.7 for Linux (AG513-96002, October 2009)

nodes configured for the monitor to ensure that the service is not active on those
nodes.
Start scripts must be robust enough to run when the service is already started, without
considering this to be an error. Similarly, Stop scripts must be robust enough to run
when the service is already stopped, without considering this to be an error. In both
of these cases, the script should exit with a zero exit status.
This behavior is necessary because the Start and Stop scripts are run to establish the
desired start/stop activity, even though the service may actually have been started
by something other than FS Option .
The Start and Stop scripts must also handle recovery from events that may cause them
to run unsuccessfully. For example, if the system encounters a problem, the script will
fail and exit non-zero. The service could then become active on another node, causing
the Stop script to run on the original node even though the Start script did not complete
successfully.
To configure scripts from the command line, use these options:
--recoveryScript <script>
--recoveryTimeout <seconds>
--startScript <script>
--startTimeout <seconds>
--stopScript <script>
--stopTimeout <seconds>
Event severity
By default, FS Option treats the failure or timeout of a Start or Stop script as a failure
of the associated service and may initiate failover of the associated Virtual NFS
Services. Configuration errors can also cause this behavior.
Such a failure or timeout creates an event associated with the monitor on the node
where the failure or timeout occurred. You can view these events on the Management
Console and clear them after you have fixed the problems that caused them.
You can configure the failover behavior with the Event Severity attribute. There are
two settings:
CONSIDER. This is the default value. Events are considered during failover decisions.
Configure FS Option for Linux180