Hi, On Tue, Jun 10, 2008 at 06:37:22AM -0400, haaseg wrote: > > When we talk system load, are we talking memory, CPU, disk...
It is CPU related and you can see it with uptime. Note that if you're short on memory, the load may get rather high due to increased swapping. There are many different causes of a high load. > On all 3 > counts this box should be fine during the times when the SIGCHILD delays > occurred. Hmm, how do you exactly know that this was the case? > What would the list suggest is a "safe" timeout interval for an IP Address? I'd say at least 15-20 seconds. Note that it has nothing really to do with the type of resource, i.e. running a monitor operation on a resource consists of quite a few operations including forking the shell which nowadays is not so light as it used to be. If the resource type is "heavy" itself or network dependent, then the timeout should of course be still higher. Thanks, Dejan _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
