[ntp:bugs] [Bug 591] NTPDATE fails to update with error: poll(): nfound = 0, error: Success

bugzilla at ntp.isc.org bugzilla at ntp.isc.org
Fri Apr 7 02:08:08 UTC 2006


http://bugs.ntp.isc.org/show_bug.cgi?id=591


stenn at ntp.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WORKSFORME


----------------------------------------------------------------------------
Additional Comments From stenn at ntp.org (Harlan Stenn)
Submitted on 2006-04-07 02:08
Jesse,

I see from your postings that you think you are running one of the
ntpdate commands I mentioned.

That does not explain how, by my read of the code, the message you are
seeing is appearing.  As I read the code, one CANNOT get that message if
errno is 0 (success).

Also, we are deprecating ntpdate.

Please visit http://ntp.isc.org/bin/view/Dev/DeprecatingNtpdate and see if
using appropriate options to either ntpd or sntp will solve this problem.

With all this in mind, I'm marking this bug as WORKSFORME.  If you have a
problem with any of the solutions recommended in DeprecatingNtpdate, please
open an issue for either ntpd or sntp, as appropriate.

If you can clearly demonstrate a problem with ntpdate (hopefully showing how
it is executing code that apparently cannot be executed) you can mark this
bug as REOPENED.  Please also note that I expect ntpdate will be gone from
the distribution within the next 6 months' time or so, in any event.

Finally, please trim any quoted replies or comments you make, and if you 
want to submit log files or program output of more than a few lines please
use the 'attachment' feature of bugzilla.

Finally, it is better to run ntpd and use 'restrict' options to avoid
answering requests that it is to run any cron job to keep system time correct.

Thanks...

H

-- 
Harlan Stenn <stenn at ntp.org>



------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.


More information about the bugs mailing list