Bug 131042 - NTP enhancement
Summary: NTP enhancement
Status: RESOLVED WONTFIX
Alias: None
Product: SUSE Linux 10.1
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: unspecified
Hardware: i586 SuSE Linux 10.0
: P5 - None : Enhancement (vote)
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-10-27 15:40 UTC by Jonathon Robison
Modified: 2006-01-09 09:18 UTC (History)
0 users

See Also:
Found By: Other
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jonathon Robison 2005-10-27 15:40:12 UTC 
For situations where the dhcp server does not provide ntp information, but the default gateway does do ntp, perhaps we should add an option to YaST-ntp such as a checkbox which says "use default route as ntp server".
Comment 1 Michael Gross 2005-10-28 13:42:23 UTC 
I think this would be confusing that way... but the maintainer should decide here.
Comment 2 Lukas Ocilka 2005-10-31 08:59:47 UTC 
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.
Comment 3 Lukas Ocilka 2006-01-09 09:18:40 UTC 
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.