NTP issues with 5.4

[Ted Mittelstaedt]

> -----Original Message-----
> From: owner-freebsd-questions at freebsd.org
> [mailto:owner-freebsd-questions at freebsd.org]On Behalf Of Michal Mertl
> Sent: Wednesday, May 11, 2005 3:59 PM
> To: Ted Mittelstaedt
> Cc: freebsd-questions at freebsd.org
> Subject: RE: NTP issues with 5.4
>
>
> Ted Mittelstaedt wrote:
> > Did you do an in-place update or a nuke-and-repave update?
> >
> > if it's an in-place update, then do a nuke-and-repave on your
> > test system and see if the problem still happens.  If not then
> > there's a library or something somewhere that the updater
> forgot about.
>
> It update with buildworld and mergemaster. I doubt the issue can be
> cause by something in my config or installation. By 'nuke-and-repave'
> you mean fresh install? I can't do that on the machines in
> question, one
> of them is acting as a router.
>

Then go to Goodwill and buy a $10 PC and load 5.4 on it.  Your making
excuses.  If you have that many production systems that you just can't
turn off, then you damn well better have a test system.

You updated with buildworld and mergemaster - these programs are only
as good as the developers make them, and their configs.  Maybe someone
made a mistake and it wasn't caught in the beta cycle, because all the
beta testers did nuke and repaves, not buildworlds.

I have never once done a buildworld and mergemaster to go to a updated
version of FreeBSD on any of my servers, and I have dozens that I run
in production with FreeBSD.  I always do nuke and repaves.  And during
the
last few versions I even stopped installing the precompiled X and started
building X from scratch, after my fresh installs - this avoided dozens of
Firefox bugs that others have wasted days chasing.

I am NOT advising YOU to stop your buildworlds as a means of upgrading.
I AM advising you that when you have a problem like this that the FIRST
thing you need to do is a comparison between an upgraded system and a
system that is a fresh install.

Ted