Jack Snodgrass <jacks_temp_id_blue62@verizon.net> writes:


>I can't figure ntpd out.

>I've got it configured ( using the defaults ) on a fedora 8 box.

>It starts and runs... it just doesn't keep my non-stable-clock system up
>to date. If I let my vmware guest run for 24 hours, the time on the
>vmware guest gets off by about 2 hours.

>Currently, I have ntpd disabled and I have a cron job that runs every
>minute and runs ntpdate to keep the time accurate...

>I thought that ntpd was supposed to be able to do this....

>If ntpd can't keep the time on the local box accurate... what's the
>purpose of it? I've had this issue with ntpd for years... I've always
>had to resort to disableing it and running ntpdate from cron.

ntp has limitations. If your boxes clock has a huge drift ( above 500PPM)
it cannot fix it. You have a drift of 100000PPM. ntp cannot fix it. You
need new hardware. You simply have very very bad hardware.
I have no idea what you mean "my vmware guest". ntp disciplines the harware
clock on your physical system. It cannot do anything about a virtual
system. The virtual system has no clock. You must run ntp on your physical
system.



>Thanks - jack


>--
>D.A.M. - Mothers Against Dyslexia

>see http://www.jacksnodgrass.com for my contact info.

>jack - Grapevine/Richardson