Problem with hint file?
Kevin Darcy
kcd at daimlerchrysler.com
Wed Dec 22 22:59:45 UTC 1999
Another thing you could try is posting to an AIX newsgroup. Apparently no-one on this
newsgroup has seen your problem, but maybe there are other AIX administrators who have,
and maybe someone there knows how to fix it.
- Kevin
P.S. How did my email address get munged to Kevin_Darcy at daimlerchrysler.com in your last
message?
andlil at towerrecords.com wrote:
> I just got done recompiling with tons of free space on all my file systems.
> There were no complaints on the console, and no complaints from any of the
> "make" commands. However, the named binary still exhibits the same
> symptoms. Namely, if I try to start it with a "type hint" entry in my
> named.conf file, named immediately coredumps and dies. If I delete the
> hint entry, then named starts. So, I guess I'll report it as a bug and
> give up for now.
>
> Thanks to all for their suggestions (and of course if anyone has any
> others, I'd be willing to entertain them, though I'm really frustrated with
> the whole thing by now).
>
> -Andrew
>
>
> Joseph S D
> Yao To: andlil at towerrecords.com,
> <jsdy at cospo.o bind-users at isc.org
> sis.gov> cc: Kevin Darcy <kcd at daimlerchrysler.com>
> Subject: Re: Problem with hint file?
> 12/21/99
> 05:57 PM
>
>
>
> On Tue, Dec 21, 1999 at 02:31:27PM -0800, andlil at towerrecords.com wrote:
> > Hmm. OK, I can submit the bug report, but before I do, let me just
> explain
> > the compile to make sure you feel that its not just something in my
> > compiling:
> > I used gcc 2.7.0 and gnu make 3.77 (as reccommended). However, when I
> did
> > "make install", named failed to be placed into /usr/sbin because the /usr
> > file system had run out of space. So, the binary I've been starting is
> the
> > named that ended up my src path as "src/bin/named/named". Then I cleared
> > up some room on my /usr filesystem and placed the named binary there.
> >
> > That should be ok, correct? (For the record: named-bootconf and
> named-xfer
> > were installed correctly during "make install").
>
> QUITE possible that your binary got corrupted because of the lack of
> space in /usr? Try re-compiling the whole thing [with much more free
> space in all file systems]. Watch for any "out of space" console
> messages. Compare the result with the binaries that you have right now.
>
> --
> Joe Yao jsdy at cospo.osis.gov - Joseph
> S. D. Yao
> COSPO/OSIS Computer Support
> EMT-B
> -----------------------------------------------------------------------
> This message is not an official statement of COSPO policies.
More information about the bind-users
mailing list