Bug 48518 – ntp upgrade to 4.2.0-r2 can be problematic on existing systems

• Product: Gentoo Linux
• Status: RESOLVED INVALID

[Description Bill Kenworthy 2004-04-20 16:03:43 UTC]

Changes to latest ntp-4.2.0-r2 do not work smoothly on existing systems
/etc/ntp/ntp.drift appears to have moved to /usr/share/something
tries to create a file /etc/ntp.drift.TEMP as user ntp which errors
operation of restrict keyword has changed so that existing, working configs fail
one system of mine has local syncing as stratum 5 to some weird IP number - no idea how/why as its not in the config
Some more on forums and mailing lsit, mostly to do with restrict or dieing because of permissions to do with ntp:ntp


Reproducible: Sometimes
Steps to Reproduce:
1. upgrade ntp on an existing system
2.
3.

Actual Results:  
ntp daemon dies when it hits file permission problems, fails to sync, acts
weirdly depending on existing config/environment

Expected Results:  
should have been a transparent upgrade, or at least some realistic warning messages.
fix permission problems to do with droproot
add config file moves to ewarn
document changes to restrict

[Comment 1 Martin Holzer (RETIRED) 2004-04-21 07:09:53 UTC]

*** Bug 48556 has been marked as a duplicate of this bug. ***

[Comment 2 SpanKY 2004-04-21 16:04:12 UTC]

drift file is stored where ntp.conf says to store it

review /usr/share/ntp/ntp.conf for the default locations

[Comment 3 Bill Kenworthy 2004-04-21 16:26:23 UTC]

drift: yes, I was tricked by the fact that it was root owned, so with ntpd running as ntp:ntp it couldnt be read/written to - also my work laptop (which after the upgrade has the local source running as stratum 5 syncing to some wierd IP) tries to write the file to /usr/share something.  That one might be reading a strange conf file somewhere I will have to track down today - why I dont know as was working right up to the upgrade.  Two other machines work after the restrict clauses were commented out, as either root:root or ntp:ntp if the appropritae files are created (/etc/drift.TEMP) owned by ntp

This has been marked resolved, invalid but I see no mention of /etc/drift.TEMP being addressed.  Also, the restrict keryword still does not work - its either changed or now faulty as previously working configs require it to be removed.  Theres some on both these topics on the forums, but no really acceptable fix (suggestions amount to forcing ntpd to run as root)

[Comment 4 SpanKY 2004-04-21 16:36:34 UTC]

the drift temp file should be created along side the real drift file

on my systems, i use pretty much the stock ntp.conf file and i have the files /var/lib/ntp/ntp.drift and /var/lib/ntp/ntp.drift.TEMP created

thats the reason ntp gets its own subdir ... it needs somewhere to create/delete a TEMP file