Since these are standard tests, as long as you have the host itself listed in the bb-hosts file, they will re-appear unless you use the "no<test>" tag - noconn noprocs nports, etc - as outlined in the help files. Use those tags at the appropriate level in the bb-hosts file and all will be well.
Dean Casey
From: Benjamin Gagnon [mailto:benjamin.gagnon at yahoo.ca] Sent: Monday, March 19, 2007 6:06 AM To: hobbit at hswn.dk Subject: Re: [hobbit] drop test not sticking...
Thank you very much for your solution. I have dropped both procs and ports so far.
I hacked the hobbit-client-<OS>.sh script on the client, restarted the client then dropped the tests once again from the server. Those 2 tests are now gone.
I'm not sure how to get rid of msgs and files though. Doesn't appear to be any entry for these in the hobbit-client-<OS>.sh script. Anyone? There are no uncommented FILE or LOG entries in the client's localclient.cfg or in the server's hobbit-clients.cfg files.
I'm confused as to why it is so difficult to remove standard client-side tests that I do not wish to perform at this point in time.
Benjamin
----- Original Message ---- From: Buchan Milne <bgmilne at staff.telkomsa.net> To: hobbit at hswn.dk Cc: Benjamin Gagnon <benjamin.gagnon at yahoo.ca> Sent: Monday, March 19, 2007 4:23:55 AM Subject: Re: [hobbit] drop test not sticking...
On Monday 19 March 2007, Benjamin Gagnon wrote:
Hi, I'm having a problem with dropping a host's test.
I perform the following command from the server (there are no output errors or errors in the error log)...
bb 127.0.0.1 "drop opsappsl.lac-bac.gc.ca ports"
Within a couple of minutes the ports column gets dropped and then a couple of minutes later the column reappears. So the drop command works ok but the settings do not stick.
I've RTFM'd and searched the web for answers to no avail. Anyone have any ideas?
To remove a test: 1)Remove the test from the configuration file for the server that is running the test (so that no new data is generated) 2)Drop the test (to prevent the test from going purple now that it receives no data)
However, note that the ports test is not run from the Hobbit server, the ports data is supplied by the client ...
If you were dropping the entire host, this would make sense, but I can't see why you would want to drop the ports test for one host (and ... this is a bit tricky). Maybe you can explain?
You could accomplish this by hacking up the hobbit-client-<OS>.sh script on the client.
Regards, Buchan
-- Buchan Milne ISP Systems Specialist - Monitoring/Authentication Team Leader B.Eng,RHCE(803004789010797),LPIC-2(LPI000074592)
The best gets better. See why everyone is raving about the All-new Yahoo! Mail. <http://us.rd.yahoo.com/evt=40705/*http:/mrd.mail.yahoo.com/try_beta?.in tl=ca>