Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

The following is the NTP configuration.
My server is a physical system, not a virtual machine.
The following ntp-4.2.2p1-15.el5.centos rpm I am using.

tinker panic 0
restrict default kod nomodify notrap nopeer noquery
#server     # local clock
#fudge stratum 10
driftfile /var/lib/ntp/drift
keys /etc/ntp/keys

The intention of this configuration is to have a common /etc/ntp.conf for my physical machine and for Virtual Machine.

My server act as a NTP client not as a NTP server. Is there any disadvantage for not using the undisciplined Local Clock on physical machine?

share|improve this question

migrated from Feb 7 '13 at 7:04

This question came from our site for professional and enthusiast programmers.

Let me simplify my question: Is it must to have a local clock as a server in the ntp.conf when we are acting as a NTP client? what is the disadvantage if we don't configure the local clock config? – Sampath Chunduri Feb 6 '13 at 3:54
You should have more than one server. – Martin Schröder Feb 7 '13 at 15:10

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.