Your message dated Tue, 14 Jul 2020 19:24:03 -0500
with message-id <[email protected]>
and subject line Re: Bug#965045: REFCLOCK: refclock_newpeer: clock type 46
invalid
has caused the Debian Bug report #965045,
regarding REFCLOCK: refclock_newpeer: clock type 46 invalid
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
965045: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=965045
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ntpsec
Version: 1.1.8+dfsg1-6
Severity: important
Dear Maintainer,
Is the refclock driver 46 (GSPD NG) included during the build process?
I have the error "REFCLOCK: refclock_newpeer: clock type 46 invalid" when
trying to uses it.
Thanks
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'stable-updates'), (500,
'oldstable-updates'), (500, 'unstable'), (400, 'stable'), (200, 'oldstable'),
(50, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 5.7.0-1-amd64 (SMP w/16 CPU cores)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE,
TAINT_UNSIGNED_MODULE
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages ntpsec depends on:
ii adduser 3.118
ii init-system-helpers 1.58
ii libc6 2.30-8
ii libcap2 1:2.36-1
ii libssl1.1 1.1.1g-1
ii lsb-base 11.1.0
ii netbase 6.1
ii python3 3.8.2-3
ii python3-ntp 1.1.8+dfsg1-6
ii tzdata 2020a-1
Versions of packages ntpsec recommends:
ii cron [cron-daemon] 3.0pl1-136
ii systemd 245.6-2
Versions of packages ntpsec suggests:
ii apparmor 2.13.4-3
ii certbot 1.6.0-1
pn ntpsec-doc <none>
pn ntpsec-ntpviz <none>
-- Configuration Files:
/etc/apparmor.d/usr.sbin.ntpd changed [not included]
/etc/ntpsec/ntp.conf changed [not included]
-- no debconf information
--- End Message ---
--- Begin Message ---
tags 965045 wontfix
In debian/rules, I have this bit about the gpsd driver:
# gpsd is a tough call. It's not deprecated upstream, and it still can
# work. However, upstream recommends the use of SHM, as does every
# example HOWTO I found with a quick search. Furthermore, it is buggy:
# https://lists.ntpsec.org/pipermail/devel/2016-October/002392.html
# Also, it "makes all sorts of non-standard assumptions about how gpsd
# is configured. A configuration that is contorted and non-obvious":
# https://lists.ntpsec.org/pipermail/devel/2016-October/002422.html
# Most importantly, it is an attractive nuisance. If someone is told
# that the best practice is to use "gpsd", they might logically think
# they should use the gpsd driver.
Note that the first linked comment is from ESR, the NTPsec tech lead and
gpsd maintainer. The second linked comment is from Gary Miller, ntpsec's
"GPS and PPS guy" and a gpsd developer. If the two of them are
recommending against, I don't think anyone should use it.
Use the SHM driver instead. On one of my production NTP servers, I use
gpsd and have this in ntpd.conf:
server 127.127.28.1 minpoll 1 maxpoll 1 prefer
fudge 127.127.28.1 refid GPS
--
Richard
signature.asc
Description: OpenPGP digital signature
--- End Message ---
