Port-arm archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: ntpdate issue ....

On 04/04/15 19:01, Greg Troxel wrote:
"William A. Mahaffey III" <wam%hiwaay.net@localhost> writes:

I like my LAN boxen to reflect time slightly fast, i.e. slightly ahead
of local time (just like I have all my clocks set), so I munge around
w/ ntpdate & adjtime to effect that. I do in fact run ntpd, as a
server for the rest of the LAN, serving up my locally adjusted
(slightly fast) time. I have been doing this w/ the incumbent LAN-time
server for several years now w/ no issues, although that box has
gotten a bit unreliable lately, hence my interest in moving to a newer
box for LAN-time service.
As much as I really don't want to help you set the wrong time, another
option is to add code in ntpd to maintain custom offset.  I did this in
1998 to test for Y2K bugs; timestamps from outside were increased by
2y.  Either that or the local clock was reduced by 2y.   It wasn't that
hard to do, and then my machine ran exactly 2 years fast, to the second.
(I am pretty sure I no longer have the code.)

I completely understand your position on the wrong time, no problema :-). The NTP people are (*very* justifiably) that way as well, that's why I do it 'outside of' ntpd proper, w/ ntpdate & a small, custom written program to apply my offset & call adjtime. My solution, while quite crufty, isolates my messing aroung 'outside of' any official, well crafted & maintained code like the ntpd code. I'm just puzzled why ntpdate seems to be returning a bad offset from my ISP when my old box (apparently) does it right ....


	William A. Mahaffey III


	"The M1 Garand is without doubt the finest implement of war
	 ever devised by man."
                           -- Gen. George S. Patton Jr.

Home | Main Index | Thread Index | Old Index