[Bug 334206] New: Yast NTP configuration doesn't handle refclocks correctly
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.
https://bugzilla.novell.com/show_bug.cgi?id=334206#c1 --- Comment #1 from Martin Burnicki <martin.burnicki@meinberg.de> 2007-10-16 04:55:19 MST --- Oops, I just saw that the fudge parameter can be entered on another page which shows up if I click on the "calibration" button. This is misleading since ntpd also supports a special "calibration" mode which is useful for debugging only. Anyway, in my opinion this neither doesn't work correctly since it adds all fudge parameters, even those for which no values have been entered, and thus might unintentionally override some default settings. For example, I have just entered for my parse refclock: stratum 0 # makes more sense than 3, which is shown by default refid GPSi time1 0.0 All other fields left empty, but the resulting line in ntp.conf is: fudge 127.127.8.0 flag1 0 flag2 0 flag3 0 flag4 0 refid GPSi \ stratum 0 time1 0.0 However, parameters for which no values have been entered should not appear in the fudge line, and if there are no parameters at all then the fudge line should not at all appear in ntp.conf. 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.
https://bugzilla.novell.com/show_bug.cgi?id=334206#c2 --- Comment #2 from Martin Burnicki <martin.burnicki@meinberg.de> 2007-10-16 05:04:27 MST --- Unlike assumed in my initial comment a symbolic link for the device to be used by the parse driver is not created. Appearently it hat been there just because I had created it before by myself. I've now even entered the parameters in /etc/sysconfig/ntp manually: NTP_PARSE_LINK="/dev/refclock-0" NTP_PARSE_DEVICE="/dev/mbgntp" and have expected the link to be created when running SuSEconfig. However, this does not seem to happen. 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.
https://bugzilla.novell.com/show_bug.cgi?id=334206#c3 --- Comment #3 from Martin Burnicki <martin.burnicki@meinberg.de> 2007-10-16 05:13:00 MST --- Hm, I wonder where the fudge parameters for a refclock are saved by yast. They don't appear in /etc/sysconfig/ntp. However, if I re-run yast I can see the values I have entered before. Are they read back directly from ntp.conf? 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.
https://bugzilla.novell.com/show_bug.cgi?id=334206 Matej Horvath <mhorvath@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team-screening@forge.provo.novell.com |kmachalkova@novell.com -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=334206 User kmachalkova@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=334206#c4 Katarina Machalkova <kmachalkova@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|kmachalkova@novell.com |mvidner@novell.com --- Comment #4 from Katarina Machalkova <kmachalkova@novell.com> 2008-04-04 09:10:48 MST --- new maintainer -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=334206 Martin Vidner <mvidner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |463470 -- 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.
https://bugzilla.novell.com/show_bug.cgi?id=334206 User mvidner@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=334206#c5 Martin Vidner <mvidner@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P3 - Medium Summary|Yast NTP configuration |[yast2-ntp-client] doesn't |doesn't handle refclocks |handle refclocks correctly |correctly | --- Comment #5 from Martin Vidner <mvidner@novell.com> 2009-03-17 08:03:39 MST --- (Adjusting summary to start with the RPM name.) -- 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.
participants (1)
-
bugzilla_noreply＠novell.com