50
Chapter 8: General Customization
Overview
Processes to be monitored may be classified into two categories:
1. Processes that remain attached to a terminal when started (e.g. “ping”). These
processes do not fork child processes.
2. Processes that do not remain attached to a terminal when started (e.g.
“squid”). These processes fork other child processes.
The customization steps explained are common for both the categories above,
unless stated otherwise.
The customization involves two major steps:
1. Creating the target resource that starts the process to be monitored
2. Creating the monitoring resource that monitors the target resource. This
monitoring resource attempts to restart target resource in case of termination.
If the target resource terminates more than a set threshold number of times, in
a given time interval, the server is rebooted automatically.
Kommentare zu diesen Handbüchern