|
Bugzilla – Full Text Bug Listing |
| Summary: | NTP enhancement | ||
|---|---|---|---|
| Product: | [openSUSE] SUSE Linux 10.1 | Reporter: | Jonathon Robison <jrobiso2> |
| Component: | YaST2 | Assignee: | Lukas Ocilka <locilka> |
| Status: | RESOLVED WONTFIX | QA Contact: | Klaus Kämpf <kkaempf> |
| Severity: | Enhancement | ||
| Priority: | P5 - None | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | SuSE Linux 10.0 | ||
| Whiteboard: | |||
| Found By: | Other | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Jonathon Robison
2005-10-27 15:40:12 UTC
I think this would be confusing that way... but the maintainer should decide here. I'm afraid that if I added a checkbox: [x] Use Default Gateway as the NTP Server Other users could want: [x] Use Primary DNS Server as the NTP Server [x] Use Secondary DNS Server as the NTP Server That's why there is the [Lookup] button when selecting the NTP server. I'll keep this enhancement open for 10.1 and my idea is to pre-select the default-route server as the [default] one from all servers found if the IP matches the default route. The second default could be the primary DNS Server, the third one the secondary DNS Server. I'm sorry but this cannot be done in YaST NTP Client. Author of the YaST Network whose libraries I would have to use did not recommend me to do it. By his opinion admins should fix it by using right DHCP values. |