On Fri, Oct 26, 2001 at 12:41:31AM +0100, Robin Kearney wrote: > > > > 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. > > > > 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 would recommend using DJB's daemontools for uses such as this. It is both more robust and doesn't mess with your system's init process. http://cr.yp.to/daemontools.html > I`ve now moved to snmpdiskspace.monitor and the host resource mib which doesnt > suffer from the inetd problems. Better anyways. You can extend net-snmp with scripts as well, if you need to go that route. -- Nate Campi <[EMAIL PROTECTED]> www.campin.net GnuPG key: 0xC17AEF79 Key fingerprint = BF12 722F 8799 E614 33CC FAB7 5A90 C464 C17A EF79 Microsoft is a cross between The Borg and the Ferengi. Unfortunately they use Borg to do their marketing and Ferengi to do their programming
