Gentoo Archives: gentoo-amd64

From: "Hemmann
To: gentoo-amd64@l.g.o
Subject: Re: [gentoo-amd64] [SOLVED] Recent clock problems
Date: Sat, 11 Feb 2006 22:58:55
Message-Id: 200602112357.00015.volker.armin.hemmann@tu-clausthal.de
In Reply to: [gentoo-amd64] [SOLVED] Recent clock problems by Mark Knecht
1 On Saturday 11 February 2006 23:14, Mark Knecht wrote:
2 >
3 >
4 > I think the only thing I'm not clear about here is what is actually in
5 > the hardware clock? If I keep time in UTC then when date tells me 4PM
6 > is the hardware clock holding midnight? (I'm in CA - offset is 8
7 > hours.)
8
9 the hardware clock is what you set in your bios.
10
11 >
12 > Can I check this somehow, like going into BIOS?
13
14 yes, that is exactly where it is sitting.
15
16 >
17 > Right now I've set the clock back to UTC and rebooted. This is what I
18 > see now. It has the 8 hour offset:
19
20 please don't forget to remove /etc/adjtime if you change settings.
21 In fact, it does not hurt to remove it regularly, especially if you add
22 ntp-client to your default runlevel.
23
24 >
25 > OK, for now anyway this seems to be the solution. I have never run
26 > ntp-client. For whatever reason I've never required it. It seems that
27 > some set of recent updates - ntp or whatever - have now started
28 > requirign that I run it. With this turned on my AMD64 machine is
29 > within a second (the speed at twhich I can hit enter in two
30 > terminals...) of my wife's Gentoo 32-bit machine.
31
32 some time ago, you installed ntp, and you run it and it was ok.
33 today ntpd is the server daemon, for syncronizing several machines of a
34 network, ntp-client the part, that sets your clock.
35 please run ntp-client and forget ntpd.
36
37 >
38 > Thanks Duncan! As usual your answers are very through and well
39 > written
40
41 and sometimes he is wrong, but his postings are so long that most people don't
42 bother to search for the errors.
43
44 --
45 gentoo-amd64@g.o mailing list

Replies

Subject Author
[gentoo-amd64] Re: [SOLVED] Recent clock problems Duncan <1i5t5.duncan@×××.net>