The executable, created locally on each node, which starts the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and are separated by spaces. For applications running in Solaris 10 zones, use the path as seen from the zone that is running the application—its relative path. Type and dimension: string-scalar
Example in global and non-global zones for Solaris 10:
Example in global and non-global zones for Solaris 10: | |
The executable, created locally on each node, that stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and are separated by spaces. For applications running in Solaris 10 zones, use the path as seen from the zone that is running the application—its relative path. Type and dimension: string-scalar
Example in global and non-global zones for Solaris 10:
Example in global and non-global zones for Solaris 10: | |
The executable, created locally on each node, which forcibly stops the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and are separated by spaces. For applications running in Solaris 10 zones, use the path as seen from the zone that is running the application—its relative path. Type and dimension: string-scalar Solaris 8 and 9: /usr/sbin/samba force stop Solaris 8 and 9: "/usr/sbin/samba force stop"
Solaris 10: Example in global and non-global zones:
Solaris 10: Example in global and non-global zones: | |
Non-global zone support for Solaris 10 and above. Defines the name of the non-global zone. | |
A list of processes that you want monitored and cleaned. Each process name is the name of an executable. Qualify the executable name with its complete path if the path starts the executable.
The process name must be the full command line argument displayed by the | |
The executable, created locally on each node, which monitors the application. Specify the complete path of the executable. Applicable command line arguments follow the name of the executable and are separated by spaces. For applications running in Solaris 10 zones, use the path as seen from the zone that is running the application—its relative path. MonitorProgram can return the following VCSAgResState values: offline value is 100; online values range from 101 to 110 (depending on the confidence level); 110 equals confidence level of 100%. Any other value = unknown. Type and dimension: string-scalar
Solaris 8 and 9:
Solaris 8 and 9:
Solaris 10: Example in global and non-global zones:
Solaris 10: Example in global and non-global zones: | |
A list of PID files that contain the process ID (PID) of the processes that you want monitored and cleaned. These are application generated files. Each PID file contains one monitored PID. Specify the complete path of each PID file in the list. For applications running in Solaris 10 non-global zones, include the zone root path in the PID file's path—the global zone's absolute path—see the example below. The process ID can change when the process restarts. If the application takes time to update the PID file, the agent's monitor script may return an incorrect result. If this occurs, increase the ToleranceLimit in the resource definition. Type and dimension: string-vector
Example in a global zone for Solaris 10:
Example in a global zone for Solaris 10:
Example in a non-global zone for Solaris 10:
Example in a non-global zone for Solaris 10: Where the $zoneroot is the root directory of the non-global zone, as seen from the global zone. | |
The user ID for running StartProgram, StopProgram, MonitorProgram, and CleanProgram. The processes specified in the MonitorProcesses list must run in the context of the specified user. Monitor checks the processes to make sure they run in this context. |