Hopefully this is an easy fix for someone here.
I've installed ntpd on a remote server running CentOS 5.5 but, after copying /usr/share/zoneinfo/Europe/London to /etc/localtime and performing an ntpd -q I am getting a system date which _is_ in BST but is 8 hours fast.
Someone suggested I set the date and time manually but this is quickly going to be overwritten as ntpd is running.
Here were the steps performed as root,
yum -y install ntp
chkconfig --levels 2345 ntp on
cp /usr/share/zoneinfo/Europe/London /etc/localtime
ntpd -q uk.pool.ntp.org
I have not modified /etc/ntp.conf so I believe that following a reboot the CentOS time severs are now being queried.
Can anyone spot a glaring omission on my part?
I've installed ntpd on a remote server running CentOS 5.5 but, after copying /usr/share/zoneinfo/Europe/London to /etc/localtime and performing an ntpd -q I am getting a system date which _is_ in BST but is 8 hours fast.
Someone suggested I set the date and time manually but this is quickly going to be overwritten as ntpd is running.
Here were the steps performed as root,
yum -y install ntp
chkconfig --levels 2345 ntp on
cp /usr/share/zoneinfo/Europe/London /etc/localtime
ntpd -q uk.pool.ntp.org
I have not modified /etc/ntp.conf so I believe that following a reboot the CentOS time severs are now being queried.
Can anyone spot a glaring omission on my part?