The following reply was made to PR bin/31580; it has been noted by GNATS.

From: Miles Nordin <carton@Ivy.NET>
To: gnats-bugs@netbsd.org
Cc: 
Subject: Re: bin/31580: 'ntptime' no longer reports ERROR and UNSYNC when ntpd isn't synchronized (ntpd bug #506)
Date: Sun, 16 Oct 2005 00:42:34 -0400

 The other thing from their bug report is, you can use 
 
  ntpq -c "rv 0 status"
 
 to see sync status on both 4.0.99 and 4.2.0.  Even in 4.0.99, when
 ntpd is killed 'ntptime' will still report (OK), so 'ntptime' is not a
 good way to check for sync even back then.  meh.
 
 from the ntpd bug report.
  ------- Additional Comment #11 From mills@udel.edu  2005-10-16 03:49   -------
 
 Subject: Re:  'ntptime' no longer reports ERROR and UNSYNC when ntpd
  isn't synchronized
 
 Miles,
 
 If you can verify what I asked you to do, I am off the planet and the 
 ball lands in NetBSD. Nothing like this happens in Solaris, Tru64, 
 Ultrix, SunOS, FreeBSD or even Linux. I wish the kernelmonger would just 
 leave things alone. Linux is a horrible example and I would be saddened 
 if FreeBSD fell down that rabbit hole.
 
 Dave