[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
Top Document: comp.unix.aix Frequently Asked Questions (Part 2 of 5)
Previous Document: 1.515: Why doesn't Netscape work?
Next Document: 1.601: How do I trace ethernet packets on an AIX system?
-
Search the FAQ Archives
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
Top Document: comp.unix.aix Frequently Asked Questions (Part 2 of 5)
Previous Document: 1.515: Why doesn't Netscape work?
Next Document: 1.601: How do I trace ethernet packets on an AIX system?
1.600: My named dies frequently, why?
Running on 3.2, named dies frequently on network's primary name server.
Try the following:
stopsrc -s named # stop running named
setenv MALLOCTYPE 3.1 # use 3.1 memory allocation algorithm
/etc/named ... # don't use smit to start named
You might be able to use startsrc/smit after setting MALLOCTYPE and get
the same effect, but I'm not sure.
[According to John, the problem is malloc() in the named code. He
also suggests using Berkeley's bind, which he has ported and can be
ftp'ed from ftp://ftp.egr.duke.edu/archives/bind-4.8.3.tar.gz. -ed]
Two ptfs should fix this problem. Get U412332 and U414752.
Christophe Wolfhugel <Christophe.Wolfhugel@grasp.insa-lyon.fr> reports
that bind 4.9 works fine on AIX 3.2 and without MALLOCTYPE=3.1.
Top Document: comp.unix.aix Frequently Asked Questions (Part 2 of 5)
Previous Document: 1.515: Why doesn't Netscape work?
Next Document: 1.601: How do I trace ethernet packets on an AIX system?
Part1 - Part2 - Part3 - Part4 - Part5 - Single Page
[ Usenet FAQs | Web FAQs | Documents | RFC Index ]
Send corrections/additions to the FAQ Maintainer:
bofh@mail.teleweb.pt (Jose Pina Coelho)
Last Update October 22 2009 @ 05:22 AM