Bug 144733

Summary:	NTP client configuration / checkbox "Use for initial Synchronization" has no effect
Product:	[openSUSE] SUSE LINUX 10.0	Reporter:	Tim Fechtner <timmi>
Component:	YaST2	Assignee:	Lukas Ocilka <locilka>
Status:	RESOLVED FIXED	QA Contact:	Klaus Kämpf <kkaempf>
Severity:	Normal
Priority:	P5 - None
Version:	Final
Target Milestone:	---
Hardware:	Other
OS:	Other
Whiteboard:
Found By:	Other	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	ntp.conf before ntp.conf after yast log new log / 10.1 beta9

Description Tim Fechtner 2006-01-23 09:05:35 UTC

Set up an NTP client the following way:
- start "NTP client" from yast
- set start option to "During boot"
- click "Complex Configuration"
- add a new server (for example ptbtime2.ptb.de)
Leaving the checkbox "Use for initial Synchronization" empty isn't saved. After applying and closing all, the checkbox is checked when I reopen the dialog. When I take of this option another way, close all dialogs and reopen them, the checkbox is another time checked - I can't take this option off.

Comment 1 Michael Gross 2006-01-23 14:37:29 UTC

Please attach the yast logfiles.

Comment 2 Tim Fechtner 2006-01-24 12:22:08 UTC

Well. 

The time server ptbtime2.ptb.de is yet installed. 1-ntp.conf is a copy of /etc/ntp.conf at this time.

Now I start YaST, network services, ntp client. ptbtime2.ptb.de is shown as (server) adress. I choose "complex configuration", there I choose the entry ptbtime2.ptb.de. Button Edit. "use for initial syncronisation" is enabled. I disable it. Ok. Close.

/etc/ntp.conf is rewritten (attached as 2-ntp.conf). Changes are minimal: in the lines 47 and 49 there is a minor difference with the space characters - everything other stays like it is.

The corresponding part of the yast logfile is attached.

Comment 3 Tim Fechtner 2006-01-24 12:24:05 UTC

Created attachment 64711 [details]
ntp.conf before

Comment 4 Tim Fechtner 2006-01-24 12:24:50 UTC

Created attachment 64712 [details]
ntp.conf after

Comment 5 Tim Fechtner 2006-01-24 12:25:11 UTC

Created attachment 64713 [details]
yast log

Comment 6 Lukas Ocilka 2006-02-01 22:41:08 UTC

Thanks for testing and logs. I'm sorry for my response-delay, I still don't have enough to fix it or even test it now.

Comment 7 Lukas Ocilka 2006-03-22 21:16:27 UTC

Sorry, we don't have any time to fix it for 10.0 and has been already fixed in 10.1 (available for free via www.opensuse.org).

You can fix it by yourself in the '/etc/sysconfig/ntp' file by setting correct entry in the NTPD_INITIAL_NTPDATE variable.

Comment 8 Tim Fechtner 2006-04-10 13:44:04 UTC

Created attachment 77547 [details]
new log / 10.1 beta9

Tested in 10.1 beta9. Problem seems to be the same. Log is attached.

Comment 9 Tim Fechtner 2006-04-10 13:45:21 UTC

Reopening.

Comment 10 Lukas Ocilka 2006-04-11 09:48:24 UTC

$["address":"0.pool.ntp.org", "comment":"\n# Random pool server, see http://www.pool.ntp.org/ for more information\n", "initial_sync":false, "options":"", "type":"server"]
$["address":"1.pool.ntp.org", "comment":"\n# Random pool server, see http://www.pool.ntp.org/ for more information\n", "initial_sync":false, "options":"", "type":"server"]
$["address":"2.pool.ntp.org", "comment":"\n# Random pool server, see http://www.pool.ntp.org/ for more information\n", "initial_sync":false, "options":"", "type":"server"]

It seems as a different issue, did you have switched Random Pool Servers option on and off? This option allways sets initial_sync to true because one single checkbox handles all this functionality.

As I can see from you log, you were able to disable the initial_sync for particular server in the Expert configuration.

Comment 11 Tim Fechtner 2006-04-13 12:36:28 UTC

Sorry. It was a quit and dirty test.

It is really a different issue. I've reported him as bug 165852.

Closing.