https://bugzilla.novell.com/show_bug.cgi?id=334206 Summary: Yast NTP configuration doesn't handle refclocks correctly Product: openSUSE 10.3 Version: Final Platform: All OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: YaST2 AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: martin.burnicki@meinberg.de QAContact: jsrain@novell.com Found By: --- I've tried to configure a parse refclock using yast2 and found 2 points where yast doesn't work correctly. 1.) If I select "Generic Reference driver" then there is an "Options" field where I can add additional parameters. A correct configuration for the parse driver requires a "mode" parameter which specifies the type of refclock to use, e.g. "mode 2" has to be added to let the parse driver expect the Meinberg standard time string. Obviously the text entered in the "Options" field is appended to the server line, so if I enter "mode 2" here the result in ntp.conf is correct: server 127.127.8.0 mode 2 However, there is also a line generated in ntp.conf which can be used to set up additional configuration options for that device: fudge 127.127.8.0 This line is empty, though, i.e. it does not contain any parameters. Commonly uses parameters here would be the refid, a constant time bias, the trust time, .., so the line could look like this: fudge 127.127.8.0 time1 0.0 refid GPSi So there should be an additional field in the yast dialog where you could enter those fudge commands for that device, and the descriptive text should tell where the parameters of each field would be added in ntp.conf. 2.) If I mark the checkbox labelled "create symlink" and enter the device name to which the link should be created, this might work if I finish yast. However, if I run yast the next time the checkbox is not marked anymore and the device name for the symlink is grayed out. A quick look into /etc/sysconfig/ntp shows that the existing parameters are still NTP_PARSE_LINK="" NTP_PARSE_DEVICE="" so they are obviously not updated correctly when yast saves the configuration. By the way, the NTP package should finally be renamed from xntp-* to ntp-*. xntp is outdated for many years now, and if users refer to that package e.g. in the NTP newsgroup comp.protocols.time.ntp they are everytime told their package was outdated and they should upgrade, hust because it is still called xntp-* while it contains ntpd etc. rather than the old xntpd. AFAIK this should be handled fine by RPM which could have an entry saying the ntp-* package obsoletes the xntp-* package. Martin -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.