Hi all,
I seem to have a bit of a problem with ntp and am hoping someone here
can steer me in the direction of a fix.
I have one of your typical home setups, linux server doing firewall,
samba, ntp, etc etc. with a couple of M$ workstations/laptops as
clients. On boot on the M$ machines I have a small utility, abouttime,
that queries the linux server for the time and subsequenly sets it. Now
this is where my problem lays. The linux box is returning the 32 bit
epoch, the time in 2036 when the time is going to roll over due to the
timer being a 32 bit int. The M$ machines regard this as rubbish and
ignore it and subsequently poll the next ntp server, which is my ISP's.
The ISP returns a proper time and the local machines time gets set. From
this I can deduce that the M$ machines, for once, are not playing up.
Does anyone have any ideas as to why the linux box has recently started
doing this? It has worked fine in the past. If I do a "date" on the
linux box, I get a time that is about right, so the linux box's clock
isn't stuffed.
I'm stumped, any thoughts greatly appreciated.
Regards,
Andrew Lowe
--
gentoo-user@gentoo.org mailing list
