Re: getting sysclock to match hwclock
On Mon, 25 Oct, 1999 à 09:52:51PM +0200, Laurent PICOULEAU wrote: On Mon, 25 Oct, 1999 à 08:26:09PM +0200, Patrik Magnusson wrote: I was under the impression (I still am) that it's a bad thing to just set the system clock back. Instead you should get it to run slower (or faster - I don't see how it could be harmful to set the system clock ahead though -) until it matches the hardware clock, and then get it to run at 'normal' speed again. Is this correct? If it is, is there some switch that makes adjtimex do this, or some other tool? And yes, I have read the man page for adjtimex, it's just that most of it is undecipherable to me. I wrote a document (in French) on this topic. You can found it on http://www.linux-france.org/article/sys/heure.html. The SGML source can be found in the same directory. Translators are welcomed. A little mistake in the URL, I should have written : http://www.linux-france.org/article/sys/heure/index.html -- ( - Laurent PICOULEAU - ) /~\ [EMAIL PROTECTED] /~\ | \)Linux : mettez un pingouin dans votre ordinateur !(/ | \_|_Seuls ceux qui ne l'utilisent pas en disent du mal. _|_/
getting sysclock to match hwclock
My system clock has been keeping time rather poorly. The hardware-clock on the other hand hasn't lost a second in over two months. I tried to use adjtimex to get the system clock to match the hardware clock, unsuccessfully. First i tried adjtimex --adjust resulting in the system clock losing more than five minutes in a day. Then I tried adjtimex -u --adjust, resulting in the system clock losing 20 minutes a day. I just want the system clock to match the hardware clock. Please help. /Patrik.
Re: getting sysclock to match hwclock
On Mon, 25 Oct 1999, Patrik Magnusson wrote: My system clock has been keeping time rather poorly. The hardware-clock on the other hand hasn't lost a second in over two months. I tried to use adjtimex to get the system clock to match the hardware clock, unsuccessfully. First i tried adjtimex --adjust resulting in the system clock losing more than five minutes in a day. Then I tried adjtimex -u --adjust, resulting in the system clock losing 20 minutes a day. I just want the system clock to match the hardware clock. Please help. All I can offer in this matter is that, despite of many hours of trying and reading manuals, I have never ever managed to figure out the system / hardware clock interrelationships with Linux. I have an old computer whose hw clock loses several minutes a day, and with hwclock and friends this should be fixable (since the deviation is known, the real time can be computed from the faulty BIOS clock on power up). I never got it to work and I now live with the fact that I'm days behind. My new computer's hw clock is set to GMT and runs fine. My timezone is set one hour off GMT (Central European), but date shows a time that's five hours late. I just stopped caring. --Daniel
Re: getting sysclock to match hwclock
On 25 Oct 1999, Patrik Magnusson wrote: My system clock has been keeping time rather poorly. The hardware-clock on the other hand hasn't lost a second in over two months. I tried to use adjtimex to get the system clock to match the hardware clock, unsuccessfully. First i tried adjtimex --adjust resulting in the system clock losing more than five minutes in a day. Then I tried adjtimex -u --adjust, resulting in the system clock losing 20 minutes a day. I just want the system clock to match the hardware clock. Please help. hwclock --hctosys or, if you're on UTC: hwclock --utc --hctosys. However, the error will come back unless you use adjtimex to correct it. You can do this in /etc/rc.boot/adjtimex. See the man pages for hwclock and adjtimex for details of all this. (Thank you A. Campbell) I see now that I was unclear in my original message. I do know about hwclock --hctosys. I was under the impression (I still am) that it's a bad thing to just set the system clock back. Instead you should get it to run slower (or faster - I don't see how it could be harmful to set the system clock ahead though -) until it matches the hardware clock, and then get it to run at 'normal' speed again. Is this correct? If it is, is there some switch that makes adjtimex do this, or some other tool? And yes, I have read the man page for adjtimex, it's just that most of it is undecipherable to me. /Patrik.
Re: getting sysclock to match hwclock
On Mon, 25 Oct, 1999 à 03:37:28PM +0200, Patrik Magnusson wrote: My system clock has been keeping time rather poorly. The hardware-clock on the other hand hasn't lost a second in over two months. I tried to use adjtimex to get the system clock to match the hardware clock, unsuccessfully. First i tried adjtimex --adjust resulting in the system clock losing more than five minutes in a day. Then I tried adjtimex -u --adjust, resulting in the system clock losing 20 minutes a day. What does /etc/adjtime contain ? You can copy hardware clock to system with hwclock --hctosys but you should have a coherent /etc/adjtime if you want that the two clock stay on sync. -- ( - Laurent PICOULEAU - ) /~\ [EMAIL PROTECTED] /~\ | \)Linux : mettez un pingouin dans votre ordinateur !(/ | \_|_Seuls ceux qui ne l'utilisent pas en disent du mal. _|_/
Re: getting sysclock to match hwclock
On 10/25/99, Patrik Magnusson scribbled about getting sysclock to match hwclock: My system clock has been keeping time rather poorly. The hardware-clock on the other hand hasn't lost a second in over two months. I just want the system clock to match the hardware clock. Please help. Try the program hwclock, in the package util-linux. Documentation in `man hwclock` -- Jesse Jacobsen, Pastor [EMAIL PROTECTED] Grace Lutheran Church (ELS) http://www.jvlnet.com/~jjacobsen/ Madison, Wisconsin GnuPG public key ID: 2E3EBF13 pgptp6FSobXDO.pgp Description: PGP signature
Re: getting sysclock to match hwclock
On Mon, 25 Oct, 1999 à 08:26:09PM +0200, Patrik Magnusson wrote: On 25 Oct 1999, Patrik Magnusson wrote: My system clock has been keeping time rather poorly. The hardware-clock on the other hand hasn't lost a second in over two months. hwclock --hctosys or, if you're on UTC: hwclock --utc --hctosys. However, the error will come back unless you use adjtimex to correct it. You can do this in /etc/rc.boot/adjtimex. See the man pages for hwclock and adjtimex for details of all this. (Thank you A. Campbell) I see now that I was unclear in my original message. I do know about hwclock --hctosys. I was under the impression (I still am) that it's a bad thing to just set the system clock back. Instead you should get it to run slower (or faster - I don't see how it could be harmful to set the system clock ahead though -) until it matches the hardware clock, and then get it to run at 'normal' speed again. Is this correct? If it is, is there some switch that makes adjtimex do this, or some other tool? And yes, I have read the man page for adjtimex, it's just that most of it is undecipherable to me. I wrote a document (in French) on this topic. You can found it on http://www.linux-france.org/article/sys/heure.html. The SGML source can be found in the same directory. Translators are welcomed. -- ( - Laurent PICOULEAU - ) /~\ [EMAIL PROTECTED] /~\ | \)Linux : mettez un pingouin dans votre ordinateur !(/ | \_|_Seuls ceux qui ne l'utilisent pas en disent du mal. _|_/
