|
Bugzilla – Full Text Bug Listing |
| Summary: | Consider making pool.ntp.org the default ntp server | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE LINUX 10.0 | Reporter: | Michael Wolf <maw> |
| Component: | Network | Assignee: | Hendrik Vogelsang <hvogel> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | All | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Michael Wolf
2005-08-17 18:33:22 UTC
erm we have no default ntp server. Could you elaborate that a bit? Right - currently there is no default. I think making pool.ntp.org be the default would be a useful enhancement. I think using some random servers (three at least, please) is better than nothing, but you have no guaranteed "service level": The server may be a PC that can die any time, or maybe serve the wrong time, or whatever. From my very short experiments I saw that nslookup returns a different address every query, and not every hour (as documented). Also every query returns multiple addresses. It would well be worth a try, but the default should be in YaST rather than in /etc/ntp.conf. I'd suggest to use the description "use a random set of NTP servers" to activate the feature, because that is what your get. BTW: The initial description is really quite verbose ;-) |