Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!usc!ucsd!nic.cerf.net!pushp
From: pushp@nic.cerf.net (Pushpendra Mohta)
Newsgroups: comp.protocols.tcp-ip.domains
Subject: Re: Monitoring your nameserver
Message-ID: <147@nic.cerf.net>
Date: 18 Aug 90 05:10:37 GMT
References: <9008141525.AA27754@sci.ccny.cuny.edu> <7769@gollum.twg.com> <EMV.90Aug17083504@urania.math.lsa.umich.edu>
Organization: CERFnet, La Jolla, CA
Lines: 14

In article <EMV.90Aug17083504@urania.math.lsa.umich.edu> emv@math.lsa.umich.edu (Edward Vielmetti) writes:
>Ummmm....
>I would think that the right way of managing these things would be to
>embed into them some piece of SNMP (the Simple Network Management Protocol),
>and then have them all watched over by a network management station
>which could get traps when the daemons die, arrange to have things
>restarted, etc etc.  This would have the advantage of letting you watch
>--Ed

Good idea, however SNMP daemons have been known to die too :-)
I have a cron process which checks whether my SNMPD is alive.

--pushpendra
CERFNet