Bug 114376 - yast doesn't enter all servers in NTPD_INITIAL_NTPDATE
Summary: yast doesn't enter all servers in NTPD_INITIAL_NTPDATE
Status: RESOLVED INVALID
Alias: None
Product: SUSE LINUX 10.0
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Beta 3
Hardware: i686 All
: P5 - None : Minor
Target Milestone: ---
Assignee: Lukas Ocilka
QA Contact: Klaus Kämpf
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-31 11:36 UTC by Volker Kuhlmann
Modified: 2005-09-02 07:07 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 Volker Kuhlmann 2005-08-31 11:36:43 UTC 
Not all servers which have "use for intial update" ticked in yast's NTP client 
config are entered in /etc/sysconfig/ntp:NTPD_INITIAL_NTPDATE. Only the first 
server I entered earlier shows up.
Comment 1 Lukas Ocilka 2005-09-01 08:55:20 UTC 
Please, attach YaST logs.
http://www.opensuse.org/index.php/Bug_Reporting_FAQ#YaST

Also please check whether you have really selected whether the server should be
used for the initial synchronization. Could you reproduce the bug and write here
a workflow what did you do?

Thanks
Comment 2 Volker Kuhlmann 2005-09-02 07:04:06 UTC 
Start yast->services->NTP client. 
Select auto start NTP during boot. 
Select complex config. 
Open port in firewall. 
Add server time.paradise.net.nz, use for initial sync. 
Ok. 
Finish. 
 
Start yast->services->NTP client. 
Select complex config. 
Add server cantva.canterbury.ac.nz, not for initial. 
Ok. 
Add server nz.pool.ntp.org, use for initial. 
Ok. 
Finish. 
 
And damn, now it works as it should. Sorry can't reproduce now, but if I come 
across it again I'll provide the info.
Comment 3 Lukas Ocilka 2005-09-02 07:07:47 UTC 
OK, so if the bug appears again, reopen it and attach YaST logs, please.
Thanks.