LinuxQuestions.org - /etc/ntp.conf got cleared a couple of months ago.

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - /etc/ntp.conf got cleared a couple of months ago. (https://www.linuxquestions.org/questions/slackware-14/etc-ntp-conf-got-cleared-a-couple-of-months-ago-4175701603/)

/etc/ntp.conf got cleared a couple of months ago.

I run current and just now discovered that I had an empty /etc/ntp.conf file with an August 15 timestamp. I copied the .orig version into place and restarted the daemon to solve the problem. Anyone else see this?

EDIT: I checked my other current machine and that one has an intact /etc/ntp.conf but an empty /etc/ntp.conf.orig, both timestamped January.

I just looked. Mine is intact.

Code:

eford@dimholt:~$ ls -l /etc/ntp.conf*

-rw-r--r-- 1 root root 2576 Aug 11 15:48 /etc/ntp.conf

-rw-r--r-- 1 root root 2579 May 21 15:02 /etc/ntp.conf.dist

eford@dimholt:~$ diff /etc/ntp.conf /etc/ntp.conf.dist

21,23c21,23

< server 1.pool.ntp.org iburst

< server 2.pool.ntp.org iburst

< server 3.pool.ntp.org iburst

---

> #server 1.pool.ntp.org iburst

> #server 2.pool.ntp.org iburst

> #server 3.pool.ntp.org iburst

I installed slackware64-current on Aug 10th, and configured ntp the next day, saving the default conf file via cp -p, so the May 21 timestamp is from the distribution.

The default config, by the way, looks to me like it does nothing other than run off the clock in the local computer. Here it is with the comments stripped out:

Code:

eford@dimholt:~$ grep -v '^#' /etc/ntp.conf.dist 



server  127.127.1.0    # local clock

fudge  127.127.1.0 stratum 10





statsdir /var/lib/ntp/stats



logfile /var/log/ntp



driftfile /var/lib/ntp/drift



pidfile /var/run/ntpd.pid







restrict default limited kod nomodify notrap nopeer noquery

restrict -6 default limited kod nomodify notrap nopeer noquery





restrict 127.0.0.1

restrict ::1

Quote:

Originally Posted by Zexuo (Post 6289651)

I have a vague memory of this happening to me as well some time back. I seem to recall it was clobbered by dhcpcd, or seeing comments about how the file was managed by dhcpcd. But I have since fixed it, and don't have a trace of it. It hasn't happened since.

Quote:

Originally Posted by emmet (Post 6289746)

The default config, by the way, looks to me like it does nothing other than run off the clock in the local computer. Here it is with the comments stripped out:

Yeah, I think you're right. I usually just uncomment the default *.pool.ntp.org server lines and then start the service.

Their website says, "The NTP Pool DNS system automatically picks time servers which are geographically close for you," and it seems to work well enough.

Mine is good, nothing changed.