Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!ddsw1!news.mcs.net!bug.rahul.net!a2i!rahul.net!a2i!dhesi.a2i!dhesi From: Rahul Dhesi <dhesi@rahul.net> Newsgroups: comp.unix.bsd.bsdi.misc,comp.protocols.tcp-ip.domains Subject: Re: named running out of memory and aborting? Date: 14 Nov 1995 00:54:31 GMT Organization: a2i network Lines: 22 Message-ID: <488pc7$2qq@hustle.rahul.net> References: <487p7f$7ia@ionews.io.org> NNTP-Posting-Host: foxtrot.rahul.net NNTP-Posting-User: dhesi Xref: euryale.cc.adfa.oz.au comp.unix.bsd.bsdi.misc:1461 comp.protocols.tcp-ip.domains:8356 In <487p7f$7ia@ionews.io.org> taob@ionews.io.org (Brian Tao) writes: >Once or twice a week, named dies... >Any ideas on what I can do to track down this problem? Not sure what the problem is, or the solution is, but here is the workaround in crontab that has served me well for some years: 10,20,30,40,50 * * * * \ /bin/kill -0 `/bin/cat /etc/named.pid` || /usr/etc/in.named My suggestion to you is to find and fix the real problem,BUT also add a cron job like mine. It will save you much worrying the next time your OS version or BIND version is updated or the next time the nameserver is reconfigured with less swap space. BTW, I have a similar cron job that restarts cron if it dies. How this is done is proprietary information, because many people will tell you it's impossible. I will let you guess whether I'm joking or not. -- Rahul Dhesi <dhesi@rahul.net> "please ignore Dhesi" -- Mark Crispin <mrc@CAC.Washington.EDU>