Bug 31258 - ntp 4.1.2 does not have IPv6 support -- can you provide ntp 4.2.0?
|
Bug#:
31258
|
Product: Gentoo Linux
|
Version: unspecified
|
Platform: All
|
|
OS/Version: Linux
|
Status: RESOLVED
|
Severity: enhancement
|
Priority: P2
|
|
Resolution: FIXED
|
Assigned To: vapier@gentoo.org
|
Reported By: christian.strauf@gmx.de
|
|
Component: Applications
|
|
|
URL:
|
|
Summary: ntp 4.1.2 does not have IPv6 support -- can you provide ntp 4.2.0?
|
|
Keywords:
|
|
Status Whiteboard:
|
|
Opened: 2003-10-16 03:42 0000
|
I really love Gentoo's IPv6 support. What I'm missing is ntp with IPv6 support.
Unfortunately, ntp version 4.1.2 that is currently the stable ntp version in
portage is not IPv6 capable (4.1.78 and up is). The new ntp version 4.2.0 is out
and I would really love to see this in Gentoo's portage. TNX in advance for your
help!
Christian
Reproducible: Always
Steps to Reproduce:
*** Bug 31438 has been marked as a duplicate of this bug. ***
4.2.0 is not in cvs because i havent added it yet
*** Bug 33922 has been marked as a duplicate of this bug. ***
*** Bug 38454 has been marked as a duplicate of this bug. ***
sorry for the delay all, but 4.2.0 can now be found in portage
Works, the only "problem" left is a
chown -R go-w /usr/share/ntp
in line 101 of the ebuild which should probably be a chmod :-)
BTW, whoever wants to test a stratum-1 enabled ntp appliance by Meinberg can test time.join.uni-muenster.de. More detailed information http://www.join.uni-muenster.de
ah, i'm a tool ... sorry about that :)
got it right in the 4.1.2 ebuild
And another one... both 4.1.2 and 4.2.0 support dropping root priviledges, but
while ntp-4.1.2 uses needs "-U ntp" in /etc/conf.d/ntp 4.2.0 has "-u ntp"
(lowercase u).
The ebuild for 4.2.0 currently installs the same conf.d-file as 4.1.2 breaking
startup right after installation. Not that hard to find, but should be fixed
netherless, either by installing another version of the configuration file or
by patching the droproot-patch to use -U instead of -u.
*** Bug 41610 has been marked as a duplicate of this bug. ***