Date: Mon, 20 Nov 2000 15:23:43 -0800 (PST)
From: Greg Thomas
Date: Mon, 20 Nov 2000 18:35:44 -0500
From: Landy Roman
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script <p> -- Rolando Roman SuSe 7.0 Linux virtuoso 2.2.16 #1 Wed Aug 2 20:22:26 GMT 2000 i586 unknown
Date: Wed, 22 Nov 2000 09:43:13 -0800 (PST)
From: Greg Thomas
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script
I'm still having this problem. To recap my hardware clock is set to localtime, I'm in Pacific Standard Time, and in yast I have set the timezone and that my hardware clock is set to localtime. Any more ideas? Thanks, Greg
Date: Wed, 22 Nov 2000 13:55:21 -0500 (EST)
From: "Christopher W. Aiken"
Date: Wed, 22 Nov 2000 10:45:19 -0800 (PST)
From: Greg Thomas
Eight hours? Isn't Pacific time equal to GMT-8 ? Try setting your hardware clock to GMT, i.e local time +8. If your hardware clock is set to GMT and you have the correct TZ set, Linux should automatically get the right time and correct for time changes such as daylight savings time.
I'm kind of confused with this. On SuSE 5.3 through 6.4 I always set my hardware clock to localtime and set my timezone to PST and I haven't had this problem. 7.0 is the first release where this has shown up for me. Why does it change only once a day? The machine isn't being rebooted and I don't see any cron jobs that run hwclock or date. Greg
Message-ID: <002801c054c6$79b2e980$0200a8c0@sk.sympatico.ca>
From: "Doug Roberts"
-|On Mon, 20 Nov 2000, Landy Roman wrote: -| -|> > Every once in awhile my clock jumps backwards 8 hours. I recall
seeing
-|> > similar problems mentioned before but could not find them in the e-mail -|> > archives. -|> > -|> > Where do I start looking to troubleshoot this problem? -|> > -|> you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script -|> -| -|I'm still having this problem. To recap my hardware clock is set to -|localtime, I'm in Pacific Standard Time, and in yast I have set the -|timezone and that my hardware clock is set to localtime. -| -|Any more ideas? -| -|Thanks, Greg
Eight hours? Isn't Pacific time equal to GMT-8 ? Try setting your hardware clock to GMT, i.e local time +8. If your hardware clock is set to GMT and you have the correct TZ set, Linux should automatically get the right time and correct for time changes such as daylight savings time.
--- Christopher W. Aiken, Scenery Hill, Pa, USA chris at cwaiken dot com, www.cwaiken.com Current O/S: SuSE 7.0 Professional Linux
I have a problem with this, what is this daylight saving garbage,,<vbg>/sarcasm off. I live in the only jurisdiction in North America that never changes its clocks. SuSE doesn't recognize this fact, yet Winblows does. Yes, on October 31 this year the clock on my Linux box set itself back an hour, when it should have not done this. I would like to see somebody recognize this fact and correct it in some version. I know it is a small matter, but it does bug me when I have to reset my clock and the OS I use doesn't recognize the time zone I live in. Doug Roberts dgr@sk.sympatico.ca ----------------------------------------------------------------- "A battle of wits?" inquired the dragon. "To whose death, Sir knight?"
Date: Wed, 22 Nov 2000 12:17:23 -0800 (PST)
From: Greg Thomas
I have a problem with this, what is this daylight saving garbage,,<vbg>/sarcasm off. I live in the only jurisdiction in North America that never changes its clocks. SuSE doesn't recognize this fact, yet Winblows does. Yes, on October
It doesn't look like you live in Arizona (not in the Navajo or Hopi nations, they follow daylight saving time but they're physically located within Arizona) or the east side of Indiana in the USA? Greg
Message-ID: <004401c054c9$99fb0b20$0200a8c0@sk.sympatico.ca>
From: "Doug Roberts"
I have a problem with this, what is this daylight saving garbage,,<vbg>/sarcasm off. I live in the only jurisdiction in North America that never changes its clocks. SuSE doesn't recognize this fact, yet Winblows does. Yes, on
October
It doesn't look like you live in Arizona (not in the Navajo or Hopi nations, they follow daylight saving time but they're physically located within Arizona) or the east side of Indiana in the USA?
Greg
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
On Wed, 22 Nov 2000, Greg Thomas wrote:
-|On Mon, 20 Nov 2000, Landy Roman wrote: -| -|> > Every once in awhile my clock jumps backwards 8 hours. I recall seeing -|> > similar problems mentioned before but could not find them in the e-mail -|> > archives. -|> > -|> > Where do I start looking to troubleshoot this problem? -|> > -|> you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script -|> -| -|I'm still having this problem. To recap my hardware clock is set to -|localtime, I'm in Pacific Standard Time, and in yast I have set the -|timezone and that my hardware clock is set to localtime. -| -|Any more ideas? -| -|Thanks, Greg
Eight hours? Isn't Pacific time equal to GMT-8 ? Try setting your hardware clock to GMT, i.e local time +8. If your hardware clock is set to GMT and you have the correct TZ set, Linux should automatically get the right time and correct for time changes such as daylight savings time.
--- Christopher W. Aiken, Scenery Hill, Pa, USA chris at cwaiken dot com, www.cwaiken.com Current O/S: SuSE 7.0 Professional Linux
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq Okay I set the clock to +8 i.e., cmos clock, and that was
Date: Thu, 23 Nov 2000 12:57:20 +0800
From: Robert Sweet
Date: Wed, 22 Nov 2000 12:35:56 -0800
From: Robert Sweet
On Mon, 20 Nov 2000, Landy Roman wrote:
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script
I'm still having this problem. To recap my hardware clock is set to localtime, I'm in Pacific Standard Time, and in yast I have set the timezone and that my hardware clock is set to localtime.
Any more ideas?
Thanks, Greg
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq I too am in the pacific timezone (USA) and have problems with time. I am running xntpd, which loses sync:
22 Nov 09:52:20 xntpd[8766]: signal_no_reset: signal 17 had flags 4000000 22 Nov 10:13:04 xntpd[8758]: time reset 0.629585 s 22 Nov 10:13:04 xntpd[8758]: synchronisation lost 22 Nov 11:29:07 xntpd[8758]: time error 35083 over 1000 seconds; set clock manually I set everything manually...get the time correct, and baboom, by the evening or next day it is screwed up. -- rsweet@socal.rr.com | Oh, well, I guess this is just -o) | going to be one of those Linux, the Choice /\ | lifetimes. of a GNU generation _\_v | |
On Wed, Nov 22, 2000 at 09:43:13AM -0800, Greg Thomas wrote:
On Mon, 20 Nov 2000, Landy Roman wrote:
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script
I'm still having this problem. To recap my hardware clock is set to localtime, I'm in Pacific Standard Time, and in yast I have set the timezone and that my hardware clock is set to localtime.
Any more ideas?
Thanks, Greg
People are adressing the problem of how to keep your clock synchronised, but
From: Cliff Sarginson
Date: Fri, 24 Nov 2000 01:12:58 +0800
From: Robert Sweet
On Wed, Nov 22, 2000 at 09:43:13AM -0800, Greg Thomas wrote:
On Mon, 20 Nov 2000, Landy Roman wrote:
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script
I'm still having this problem. To recap my hardware clock is set to localtime, I'm in Pacific Standard Time, and in yast I have set the timezone and that my hardware clock is set to localtime.
Any more ideas?
Thanks, Greg
People are adressing the problem of how to keep your clock synchronised, but
On Wednesday 22 November 2000 21:35, you wrote: that is assuming your clock is sort of ok in the first place...
Does it only happen when you reboot or just at random.
I have had some problems with time, it is much more complicated than it may appear, since the kernel may also be ticking a clock for you.. and it will be if you use xntpd..but may not be if you don't ..
I would suggest setting your BIOS clock to GMT and the timezone to PST or whatever. Make sure the setting for this is correct in rc.config. I have dialup connection and every time I connect I get the time from the ISP time server and use hwclock to set my hardware time from it. This works well.
I will post the little script I use if you want to see it..
Cliff Hwclock holds time:
c-24-130-150-58:/home/rsweet # hwclock --show Fri Nov 24 10:02:25 2000 -0.367565 seconds ystem time progressively worsens: c-24-130-150-58:/home/rsweet # date Fri Nov 24 00:59:31 GMT-8 2000 When I reboot, time is perfect. The longer the machine is up, the worse time gets. I have run ntpdate to set the clock manually and then started xntpd. Xntpd though cannot keep up, because the clock gets to out of whack. The cmos clock is -8 to local time, and the timezone for the system is set to GMT-8 for California/USA. Any help in fixing this would greatly be appreciated. I have been trying to fix this for over a year now. Thanks. rsweet@socal.rr.com
Date: Fri, 24 Nov 2000 22:08:35 +0200
From: Des Aubery
On Thu, Nov 23, 2000 at 11:22:43PM +0100, Cliff Sarginson wrote:
On Wed, Nov 22, 2000 at 09:43:13AM -0800, Greg Thomas wrote:
On Mon, 20 Nov 2000, Landy Roman wrote:
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script
I'm still having this problem. To recap my hardware clock is set to localtime, I'm in Pacific Standard Time, and in yast I have set the timezone and that my hardware clock is set to localtime.
Any more ideas?
Thanks, Greg
People are adressing the problem of how to keep your clock synchronised, but
On Wednesday 22 November 2000 21:35, you wrote: that is assuming your clock is sort of ok in the first place...
Does it only happen when you reboot or just at random.
I have had some problems with time, it is much more complicated than it may appear, since the kernel may also be ticking a clock for you.. and it will be if you use xntpd..but may not be if you don't ..
I would suggest setting your BIOS clock to GMT and the timezone to PST or whatever. Make sure the setting for this is correct in rc.config. I have dialup connection and every time I connect I get the time from the ISP time server and use hwclock to set my hardware time from it. This works well.
I will post the little script I use if you want to see it..
Cliff Hwclock holds time:
sc-24-130-150-58:/home/rsweet # hwclock --show Fri Nov 24 10:02:25 2000 -0.367565 seconds
system time progressively worsens:
sc-24-130-150-58:/home/rsweet # date Fri Nov 24 00:59:31 GMT-8 2000
When I reboot, time is perfect. The longer the machine is up, the worse time gets. I have run ntpdate to set the clock manually and then started xntpd. Xntpd though cannot keep up, because the clock gets to out of whack. The cmos clock is -8 to local time, and the timezone for the system is set to GMT-8 for California/USA. Any help in fixing this would greatly be appreciated. I have been trying to fix this for over a year now.
Thanks.
rsweet@socal.rr.com
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
-- Best regards, Des Aubery... _________________________ ^^^^^ ---> East London ^^^^^ ---> Advanced Automotive... E.Cape, 5257 ^^^^^ ---> Heat-Transfer South Africa ^^^^^ ---> CFD email: daubery@mweb.co.za ^^^^^ ---> FEA ______________________________^^^^^ --->
Date: Sat, 25 Nov 2000 00:14:42 +0100
From: Cliff Sarginson
Date: Thu, 23 Nov 2000 21:51:27 -0800
From: Michael Perry
On Wed, Nov 22, 2000 at 09:43:13AM -0800, Greg Thomas wrote:
On Mon, 20 Nov 2000, Landy Roman wrote:
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script
I'm still having this problem. To recap my hardware clock is set to localtime, I'm in Pacific Standard Time, and in yast I have set the timezone and that my hardware clock is set to localtime.
Any more ideas?
Thanks, Greg
People are adressing the problem of how to keep your clock synchronised, but
On Wednesday 22 November 2000 21:35, you wrote: that is assuming your clock is sort of ok in the first place...
Does it only happen when you reboot or just at random.
I have had some problems with time, it is much more complicated than it may appear, since the kernel may also be ticking a clock for you.. and it will be if you use xntpd..but may not be if you don't ..
I would suggest setting your BIOS clock to GMT and the timezone to PST or whatever. Make sure the setting for this is correct in rc.config. I have dialup connection and every time I connect I get the time from the ISP time server and use hwclock to set my hardware time from it. This works well.
I will post the little script I use if you want to see it..
Cliff
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq
The man ntp and ntpdate pages tell a lot about how to use the available utilities to manage time. I use ntp against a known timeserver and then synch all the systems on my home network. My systems account for changes in pst/pdt and I have not been concerned about issues regarding time or changes since I implemented a ntp server here. My NAT/firewall box running debian works quite well at syncing to a known time server here; clock.via.net. The ntpdate man page points out a few facts about using ntpdate and ntp at the same time. I don't recall the last time I had a system lose the correct time because of the pdt shift. Another good source of information is to read the hwclock man pages throughout. In the absence of a ntp server, those pages talk a lot about setting the bios clock to UTC and then running the local clock at the local time. This also has worked for me. Running a local time server has its advantages though. I know how I do it. It works for me. It also appears to work for a great many other people. If you search on deja news you can see that a great many people use ntp services on fulltime dsl or cable networks. Then its only a matter of how you get the time served to individual systems on your home network. Lots of ways depending on the OS. -- Michael Perry mperry@tsoft.com ------------------
Quoting Cliff Sarginson on Thu, Nov 23, 2000 at 11:22:43PM +0100:
On Wednesday 22 November 2000 21:35, you wrote:
On Wed, Nov 22, 2000 at 09:43:13AM -0800, Greg Thomas wrote:
On Mon, 20 Nov 2000, Landy Roman wrote:
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
The man ntp and ntpdate pages tell a lot about how to use the available utilities to manage time. I use ntp against a known timeserver and then synch all the systems on my home network. <snip> I believe there are issues surrounding xntpd/ntpdate if the time difference is huge between the time servers and the client...it may refuse to synchronise since I believe it has some logic in it to detect if
Date: Fri, 24 Nov 2000 07:06:26 +0100
From: Cliff Sarginson
Date: Thu, 23 Nov 2000 22:20:57 -0800 (PST)
From: Greg Thomas
Quoting Cliff Sarginson on Thu, Nov 23, 2000 at 11:22:43PM +0100:
On Wed, Nov 22, 2000 at 09:43:13AM -0800, Greg Thomas wrote:
On Mon, 20 Nov 2000, Landy Roman wrote:
Every once in awhile my clock jumps backwards 8 hours. I recall seeing similar problems mentioned before but could not find them in the e-mail archives.
Where do I start looking to troubleshoot this problem?
you hardware clock might be incorrect find 2 pgms netdate and hwclock and run this script
I'm still having this problem. To recap my hardware clock is set to localtime, I'm in Pacific Standard Time, and in yast I have set the timezone and that my hardware clock is set to localtime.
Any more ideas?
Thanks, Greg
People are adressing the problem of how to keep your clock synchronised, but
On Wednesday 22 November 2000 21:35, you wrote: that is assuming your clock is sort of ok in the first place...
Does it only happen when you reboot or just at random.
It definitely happens at reboot. But it also happens randomly which I don't understand. If I just run hwclock --hctosys it corrects the problem so I could schedule that periodically. I would really like to understand why this is happening, though, the change is exactly 8 hours so it appears to be related to not running my hardware clock at GMT.
The man ntp and ntpdate pages tell a lot about how to use the available utilities to manage time.
The thing is I have never had a problem running my hardware clock at localtime. ntpdate and such are fine, but I'd still like to figure out why I'm having this problem. Greg
From: kastus@tsoft.com Date: Fri, 24 Nov 2000 13:38:41 -0800 Message-ID: <20001124133841.A958@fizia.local> Subject: Re: [SLE] Clock problem
I too am in the pacific timezone (USA) and have problems with time. I am running xntpd, which loses sync:
22 Nov 09:52:20 xntpd[8766]: signal_no_reset: signal 17 had flags 4000000 22 Nov 10:13:04 xntpd[8758]: time reset 0.629585 s 22 Nov 10:13:04 xntpd[8758]: synchronisation lost 22 Nov 11:29:07 xntpd[8758]: time error 35083 over 1000 seconds; set clock manually
I set everything manually...get the time correct, and baboom, by the evening or next day it is screwed up. -- rsweet@socal.rr.com | Oh, well, I guess this is just -o) | going to be one of those Linux, the Choice /\ | lifetimes. of a GNU generation _\_v | |
I am in PST zone too, I use xntpd, and no problems. Hardware clock is set to GMT. I sync to 63.192.96.2 and 165.227.1.1. What servers do you sync to? -Kastus
participants (9)
-
cliff＠raggedclown.net -
cwaiken＠telerama.com -
daubery＠mweb.co.za -
dgr＠sk.sympatico.ca -
ethant＠pacificnet.net -
kastus＠tsoft.com -
landie＠concentric.net -
mperry＠tsoft.com -
rsweet＠socal.rr.com