# rpm -q openntpd
openntpd-3.9p1-alt12

# grep -v '^#' /etc/ntpd.conf | grep -v '^$'
server 10.1.0.2
# date --set='1 jan 1990'
Mon Jan  1 00:00:00 UTC 1990
# ntpd -d
ntp engine ready
reply from 10.1.0.2: offset 727691985.579069 delay 0.000478, next query 8s
set local clock to Tue Jan 22 08:39:56 UTC 2013 (offset 727691985.579069s)
^Cntp engine exiting
Terminating

При этом, если в ntpd.conf больше одной записи, или время не сбито, все работает нормально.

# grep -v '^#' /etc/ntpd.conf | grep -v '^$'
server 10.1.0.2
server 10.1.0.2
# date --set='1 jan 1990'
Mon Jan  1 00:00:00 UTC 1990
# ntpd -d
ntp engine ready
reply from 10.1.0.2: offset 727692626.531716 delay 0.000508, next query 6s
reply from 10.1.0.2: offset 727692626.531648 delay 0.000590, next query 9s
set local clock to Tue Jan 22 08:50:31 UTC 2013 (offset 727692626.531716s)
reply from 10.1.0.2: offset -0.000241 delay 0.000263, next query 6s
reply from 10.1.0.2: offset -0.000352 delay 0.000260, next query 5s
peer 10.1.0.2 now valid
reply from 10.1.0.2: offset -0.000438 delay 0.000264, next query 9s
^Cntp engine exiting
Terminating

или

# grep -v '^#' /etc/ntpd.conf | grep -v '^$'
server 10.1.0.2
# ntpdate 10.1.0.2
22 Jan 08:51:58 ntpdate[4603]: step time server 10.1.0.2 offset 727692714.553779 sec
# ntpd -d
ntp engine ready
reply from 10.1.0.2: offset -0.000122 delay 0.000250, next query 9s
reply from 10.1.0.2: offset -0.000257 delay 0.000279, next query 8s
reply from 10.1.0.2: offset -0.000405 delay 0.000261, next query 8s
peer 10.1.0.2 now valid
reply from 10.1.0.2: offset -0.000806 delay 0.000729, next query 9s
^Cntp engine exiting
Terminating