DEFAULT client settings applied even when a different rule matches earlier in hobbit-clients.cfg
I'm trying to set up my hobbit-clients.cfg file so that specific hosts have certain settings, and the remaining hosts that do not match pick up the default settings. However, it seems that the default settings are picked up and applied to everything, no matter what. If I understand what I've read in the hobbit-clients.cfg manpage, the first rule match should be applied and the remainder of the config file is ignored for the host. That has not been my experience, though. For example, I have these two entries in my hobbit-clients.cfg:
HOST=%radm.*t.mcclatchyinteractive.com UP 30m LOAD 3.0 5.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97 PROC adm 1
DEFAULT # These are the built-in defaults. UP 30m LOAD 3.0 5.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97 PROC default 1
Right now I have a red procs alert for server radm004t.mcclatchyinteractive.com, because the process "default" is not running.
I feel like I'm just missing something simple, but can't figure out what it is. Any tips?
Tom Georgoulias Systems Engineer McClatchy Interactive
On Fri, Dec 01, 2006 at 03:31:27PM -0500, Tom Georgoulias wrote:
DEFAULT # These are the built-in defaults. UP 30m LOAD 3.0 5.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97 PROC default 1
Bottom line: Dont put PROC settings into the default section.
Regards, Henrik
Henrik Stoerner wrote:
Bottom line: Dont put PROC settings into the default section.
That works--thanks.
Is that the only parameter in DEFAULT that is applied to all hobbit clients?
Tom Georgoulias Systems Engineer McClatchy Interactive
participants (2)
-
henrik@hswn.dk
-
tomg@mcclatchyinteractive.com