| Summary: | clockspeed-0.62-r3 sntpclock spits annoying warnings and sometimes fails | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Yassen Damyanov <yd> |
| Component: | New packages | Assignee: | No maintainer - Look at https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers if you want to take care of it <maintainer-needed> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | High | ||
| Version: | unspecified | ||
| Hardware: | x86 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
|
Description
Yassen Damyanov
2005-11-16 08:45:14 UTC
good people from the clockspeed list pointed me to the source of those warnings: Toby Betts: "The messages you're seeing: sntpclock: warning: unable to read clock: bad response format sntpclock: fatal: time uncertainty too large have more to do with your network and your choice of NTP server than with the sntpclock software itself. The Network Time Protocol uses UDP, a connectionless data transfer method with no built-in system of congestion control. What this means is that sometimes UDP packets get to their intended destination and sometimes they don't. Under very heavy traffic, sntpclock won't he able to communicate with the NTP server in a timely manner and thus won't have enough information to adjust the system clock correctly. It will warn you and if things don't improve, eventually die. Every time I've seen these messages, it's been because of high traffic or a dodgy NTP server." Stupid me. So, closing this as invalid :-\ |