Note: Due to technical difficulties, the Archives are currently not up to date.
GMANE provides an alternative service for most mailing lists. c.f. bug 424647
List Archive: gentoo-amd64
On Saturday 11 February 2006 23:14, Mark Knecht wrote:
>
>
> I think the only thing I'm not clear about here is what is actually in
> the hardware clock? If I keep time in UTC then when date tells me 4PM
> is the hardware clock holding midnight? (I'm in CA - offset is 8
> hours.)
the hardware clock is what you set in your bios.
>
> Can I check this somehow, like going into BIOS?
yes, that is exactly where it is sitting.
>
> Right now I've set the clock back to UTC and rebooted. This is what I
> see now. It has the 8 hour offset:
please don't forget to remove /etc/adjtime if you change settings.
In fact, it does not hurt to remove it regularly, especially if you add
ntp-client to your default runlevel.
>
> OK, for now anyway this seems to be the solution. I have never run
> ntp-client. For whatever reason I've never required it. It seems that
> some set of recent updates - ntp or whatever - have now started
> requirign that I run it. With this turned on my AMD64 machine is
> within a second (the speed at twhich I can hit enter in two
> terminals...) of my wife's Gentoo 32-bit machine.
some time ago, you installed ntp, and you run it and it was ok.
today ntpd is the server daemon, for syncronizing several machines of a
network, ntp-client the part, that sets your clock.
please run ntp-client and forget ntpd.
>
> Thanks Duncan! As usual your answers are very through and well
> written
and sometimes he is wrong, but his postings are so long that most people don't
bother to search for the errors.
--
gentoo-amd64@g.o mailing list
|
|