It looks like your bios (hardware) clock was set to local time but
you told the debian installer that it was set to UTC (or maybe vice
versa) then for some reason the bios clock drifted about a half-hour
off (not sure what would cause that).
Rather than ntpdate, I'd use ntp. Ntpdate
Ed Curtis wrote:
It's not a dual-boot. I'm not sure but I think the bios date/time had
something to do with it because I haven't had a problem with it since
resetting it and updateing with ntpdate.
I'm unsure about modern hardware, but older machines often suffered from
the reboot it said 1:04 am with the correct date. I used ntpdate to update
and everything is running normally.
Can anyone shed some light on to why the system/bios time would differ
like that or why running ntpdate and setting the correct time would
affect the server as mentioned above?
Thanks,
Ed
and rebooted. When I checked the server time after
the reboot it said 1:04 am with the correct date. I used ntpdate to update
and everything is running normally.
Can anyone shed some light on to why the system/bios time would differ
like that or why running ntpdate and setting the correct time would
was 10:04. I set it to the
correct time of 5:31 and rebooted. When I checked the server time after
the reboot it said 1:04 am with the correct date. I used ntpdate to update
and everything is running normally.
Can anyone shed some light on to why the system/bios time would differ
like
on to why the system/bios time would differ
like that or why running ntpdate and setting the correct time would
affect the server as mentioned above?
Have you run tzconfig to check if your time zone is set correctly?
Yes. It is correctly set for America/New York.
I've only seen
On Mon, 23 Oct 2006, Clive Menzies wrote:
Yes. It is correctly set for America/New York.
I've only seen this problem on dual boot machines where on installation
you set the time to the hardware clock but switching between systems
does strange things. This doesn't apply here but you
Ed Curtis wrote:
It's not a dual-boot. I'm not sure but I think the bios date/time had
something to do with it because I haven't had a problem with it since
resetting it and updateing with ntpdate.
I'm unsure about modern hardware, but older machines often suffered from
clock-drift, and
On Monday, 23.10.2006 at 09:02 -0500, Kent West wrote:
Ed Curtis wrote:
It's not a dual-boot. I'm not sure but I think the bios date/time had
something to do with it because I haven't had a problem with it since
resetting it and updateing with ntpdate.
I'm unsure about modern
9 matches
Mail list logo
