Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Monitoring\s+systems\s+reloading\.\.\.\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*Monitoring\s+systems\s+reloading\.\.\.\s*$/: 3 ]

Total 3 documents matching your query.

1. Monitoring systems reloading... (score: 1): Author: Steve Francis <steve.francis AT COMMSERV.UCSB DOT EDU>; Date: Fri, 17 Dec 1999 15:44:10 -0800; To expand on my ealier question... How is everyone else monitoring whether systems reload? I think this is an inportant thing to monitor (I sure want to know if my router reloads due to a ROM error,; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-12/msg00400.html (11,263 bytes)
2. Re: Monitoring systems reloading... (score: 1): Author: Ray Schafer <schafer AT tkg DOT com>; Date: Fri, 17 Dec 1999 23:27:18 -0600; Have you thought about editing /etc/mibExpr.conf and create an expression that divides (100 * polling interval) by the system uptime. The data collection thresholding can be done looking for this num; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-12/msg00402.html (10,947 bytes)
3. Re: Monitoring systems reloading... (score: 1): Author: Steve Francis <steve.francis AT COMMSERV.UCSB DOT EDU>; Date: Mon, 20 Dec 1999 15:04:43 -0800; Good idea. That works. Thanks a lot. (Although now I've run into MLM no longer allowing monitoring of the default route instance of the nexthopentry in the route table mib for "changes", which I was; /usr/local/webapp/mharc-adsm.org/html/nv-l/1999-12/msg00419.html (11,563 bytes)

Current List: 1 - 3
Page: [1]