BIND 8.2.2-P5 problem

[Mark.Andrews at nominum.com]

> 
> Yaning Wang wrote:
> 
> > I am sure someone must have posted this before. But difficult to search the
> > archive. So sorry to post it again.
> >
> > We are running BIND 8.2.2-P5  on Solaris 2.7. But from time to time, it
> > crashes, with error: ns_main.c:537: INSIST(errno == EINTR): Invalid argumen
> t
> > failed. It is a Solaris related error, or 8.2.2-P5 code error ?
> 
> I don't think it is either. I'm running BIND 8.2.2-p5 on my Solaris 7
> workstation here and I've never had it crash. Perhaps your system is missing
> some sort of patch? Or maybe BIND was not built correctly?

	Our current theory is that gettimeofday() sometimes returns
	an out of range tv_usec.  We know this true on some BSD
	based machines and have circumstantial evidence that Solaris
	also has this problem.  The BSD machines in question have
	selectable time keeping mechanisms and by telling the kernel
	to use the alternate machanism the problem disappears.

	BIND 8.2.3 will panic just after the gettimeofday() call if
	gettimeofday() returns a bad time so we should be able to
	positively prove/disprove this theory.

	Mark
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com