>
> Setting up inetd.conf entries is a one-time shot. Using ssh is considerably
> more overhead, especially if you call the monitors frequently, and have more
> than a couple of them in inetd.conf. The inetd method is very efficient in
> comparison to repeated ssh calls.
>
I used to use the df running from inet method, but I found that with a disk
that is constantly over the page level, mon would seemingly ignore the
alertevery paramter and mail me every 20 mins or so (alertafter was set to
6 hours).
After some trouble shooting I discovered that checking the disks every minute
or so would cause inetd to stop accepting connections after a few tries.
This seems to be inetd`s method of stopping a inbound flood. Although in this
situation it was not the desired behaviour. I would recomend anybody using this
metod for retrieving remote data watches for this.
I`ve now moved to snmpdiskspace.monitor and the host resource mib which doesnt
suffer from the inetd problems.
--
info.name("Robin Kearney"); info.mobile("07973 818 354");
info.email("[EMAIL PROTECTED]"); info.web("http://riviera.org.uk/";);
---------------------------------------------------------------------------
"What color is a choking smurf?"
