I tried that as well.. Whatever I put in ntp.conf is in the end overwritten by what dhcp configuration obtains from the network. It has become really annoying!
I also find it to be a great security hole/threat for two reasons:
1. Things coming from the network should not be overwritting a .conf file
2. Ntp reconfigures the iptables LOKKIT rules to open in/out ntp traffic for whatever address it has in its conf file. It should only need to open outbound traffic only.
Rgds
NOTE: I am using RH9
on 29/01/2004 20:22, L. Christopher Luther at CLuther@xxxxxxxxxxxxx wrote:
My RH 8.0 box is moved between subnets, and I've manually edited my /etc/ntp.conf file to include multiple time servers:
[/etc/ntp.conf snip...]
# --- OUR TIMESERVERS -----
# or remove the default restrict line
# Permit time synchronization with our time source, but do not
# permit the source to query or modify the service on this system.
# restrict mytrustedtimeserverip mask 255.255.255.255 nomodify notrap noquery
# server mytrustedtimeserverip
server 129.6.15.28
server 129.6.15.29
server 192.43.244.18
[...snip]
When my dhclient renews/changes it's lease, it doesn't seem to change the /etc/ntp.conf file at all.
What exactly is happening to your ntp configuration? Is it possible that your DHCP server's scope is populating the NTP time source settings?
