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