I just discovered that my clock is showing London, England time. I tried to configure the time zone, but it is already set to Pacific Std Time. Why did this happen? How do I fix it? How do I keep it from happening again? -- John R. Sowden AMERICAN SENTRY SYSTEMS, INC. Residential & Commercial Alarm Service UL Listed Central Station Serving the San Francisco Bay Area Since 1967 mail@americansentry.net www.americansentry.net
** Reply to message from "John R. Sowden" <jsowden@americansentry.net> on Sun, 24 Jul 2005 06:51:17 -0700
I just discovered that my clock is showing London, England time. I tried to configure the time zone, but it is already set to Pacific Std Time. Why did this happen? How do I fix it? How do I keep it from happening again? -- John R. Sowden
John, this happens to me from time to time. Most recently my clock was reading time in Sydney, OZ (but I'm in Florida). In addition to setting to Pacific time zone be sure that you've also set it to "local time" rather than UTC. That should keep it right. Gil
On Sun, 2005-07-24 at 09:56 -0400, Gil Weber wrote:
** Reply to message from "John R. Sowden" <jsowden@americansentry.net> on Sun, 24 Jul 2005 06:51:17 -0700
I just discovered that my clock is showing London, England time. I tried to configure the time zone, but it is already set to Pacific Std Time. Why did this happen? How do I fix it? How do I keep it from happening again? -- John R. Sowden
John, this happens to me from time to time. Most recently my clock was reading time in Sydney, OZ (but I'm in Florida).
In addition to setting to Pacific time zone be sure that you've also set it to "local time" rather than UTC.
That should keep it right. Gil
Move your mouse over the clock and move the wheel, it will change to other timezones that you can setup. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
** Reply to message from Ken Schneider <suse-list@bout-tyme.net> on Sun, 24 Jul 2005 12:35:30 -0400
In addition to setting to Pacific time zone be sure that you've also set it to "local time" rather than UTC.
That should keep it right. Gil
Move your mouse over the clock and move the wheel, it will change to other timezones that you can setup.
Where is the TZ environment variable that governs the seasonal transitions for the selected time zone. The winter > summer transtion here is calculated by the Hebrew calendar, not the Gregorian, and a Gregorian TZ variable won't work right. In OS/2 I had to make a script to compute the transtion dates, and I suppose I will have to do the same thing for SUSE. -- Stan Goodman Qiryat Tiv'on Israel "When your enemy falls, do not rejoice." -- Proverbs 24:17 Q: H'llo, h'llo, h'llo. Why is a computer like an air conditioner? A: It stops working when you open Windows.
On Sunday 24 July 2005 19:11, Stan Goodman wrote:
Where is the TZ environment variable that governs the seasonal transitions for the selected time zone. The winter > summer transtion here is calculated by the Hebrew calendar, not the Gregorian, and a Gregorian TZ variable won't work right. In OS/2 I had to make a script to compute the transtion dates, and I suppose I will have to do the same thing for SUSE.
I don't really know about this, but reading the timezone information in the glibc source code, it looks like the "Israel" timezone takes into account the rule they call 'Zion', and according to the text it's fairly up to date, they include a law from March 2004 passed by the Knesset setting DST rules from 2005 onwards So as far as I can see, you shouldn't have to do it yourself, just set the timezone to Israel in YaST and the rest should take care of itself
** Reply to message from Anders Johansson <andjoh@rydsbo.net> on Sun, 24 Jul 2005 19:48:45 +0200
On Sunday 24 July 2005 19:11, Stan Goodman wrote:
Where is the TZ environment variable that governs the seasonal transitions for the selected time zone. The winter > summer transtion here is calculated by the Hebrew calendar, not the Gregorian, and a Gregorian TZ variable won't work right. In OS/2 I had to make a script to compute the transtion dates, and I suppose I will have to do the same thing for SUSE.
I don't really know about this, but reading the timezone information in the glibc source code, it looks like the "Israel" timezone takes into account the rule they call 'Zion', and according to the text it's fairly up to date, they include a law from March 2004 passed by the Knesset setting DST rules from 2005 onwards.
Yes, that's the rule to which I wrote the script.
So as far as I can see, you shouldn't have to do it yourself, just set the timezone to Israel in YaST and the rest should take care of itself
I've already set the timezone to Israel, as a matter of course. I'm flabbergasted, and impressed by what you say. Also by the fact that I was able to set the clock to display the date according to the Hebrew calendar, albeit only in short format. Arabic and Persian calendars are also available. Thanks... -- Stan Goodman Qiryat Tiv'on Israel "When your enemy falls, do not rejoice." -- Proverbs 24:17 I hate puns. Except synonym puns, which are good with coffee for breakfast.
On Sun, 2005-07-24 at 19:48 +0200, Anders Johansson wrote:
On Sunday 24 July 2005 19:11, Stan Goodman wrote:
Where is the TZ environment variable that governs the seasonal transitions for the selected time zone. The winter > summer transtion here is calculated by the Hebrew calendar, not the Gregorian, and a Gregorian TZ variable won't work right. In OS/2 I had to make a script to compute the transtion dates, and I suppose I will have to do the same thing for SUSE.
I don't really know about this, but reading the timezone information in the glibc source code, it looks like the "Israel" timezone takes into account the rule they call 'Zion', and according to the text it's fairly up to date, they include a law from March 2004 passed by the Knesset setting DST rules from 2005 onwards
So as far as I can see, you shouldn't have to do it yourself, just set the timezone to Israel in YaST and the rest should take care of itself
And wait for the shysters that run our government (in the USA) change the dates for DST by adding three weeks in the spring and one in the fall. Won't that cause a lot of confusion for the programmers. And think about all of the legacy systems that will have to be updated/programs changed. And these are supposed to intelligent people. I hate to think of all of the children that will have more darkness to endure in the morning either walking to school or waiting for the school bus. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 "The day Microsoft makes something that doesn't suck is probably the day they start making vacuum cleaners." -Ernst Jan Plugge
Ken, On Sunday 24 July 2005 14:34, Ken Schneider wrote:
...
And wait for the shysters that run our government (in the USA) change the dates for DST by adding three weeks in the spring and one in the fall. Won't that cause a lot of confusion for the programmers. And think about all of the legacy systems that will have to be updated/programs changed. And these are supposed to intelligent people. ...
If these programmers are worth a whit, they did not hard code DST rules into any code that performs calendric math, because such computations are some of the most special-case-riddled of anything you'll ever have to compute.
-- Ken Schneider
Randall Schulz
On Sunday 24 July 2005 23:34, Ken Schneider wrote:
And wait for the shysters that run our government (in the USA) change the dates for DST by adding three weeks in the spring and one in the fall. Won't that cause a lot of confusion for the programmers. And think about all of the legacy systems that will have to be updated/programs changed. And these are supposed to intelligent people. I hate to think of all of the children that will have more darkness to endure in the morning either walking to school or waiting for the school bus.
The rules for summer time are different in different areas of the world. And in those areas they have changed multiple times. And if I read the timezone stuff right in the glibc source, the calendaring code can handle it. In other words, if you set your computer's date to 1823 or whatever, you'll get the correct summer time info So one more change I don't think will be that hard to handle
Ken Schneider <suse-list@bout-tyme.net> writes:
And wait for the shysters that run our government (in the USA) change the dates for DST by adding three weeks in the spring and one in the fall. Won't that cause a lot of confusion for the programmers. And think about all of the legacy systems that will have to be updated/programs changed. And these are supposed to intelligent people.
glibc uses the timezone package which is actually a database that contains entries like the following to determine when to change the timezone (this is only part of the data): # Rule NAME FROM TO TYPE IN ON AT SAVE LETTER/S Rule US 1918 1919 - Mar lastSun 2:00 1:00 D Rule US 1918 1919 - Oct lastSun 2:00 0 S Rule US 1942 only - Feb 9 2:00 1:00 W # War Rule US 1945 only - Aug 14 23:00u 1:00 P # Peace Rule US 1945 only - Sep 30 2:00 0 S Rule US 1967 max - Oct lastSun 2:00 0 S Rule US 1967 1973 - Apr lastSun 2:00 1:00 D Rule US 1974 only - Jan 6 2:00 1:00 D Rule US 1975 only - Feb 23 2:00 1:00 D Rule US 1976 1986 - Apr lastSun 2:00 1:00 D Rule US 1987 max - Apr Sun>=1 2:00 1:00 D So, anything can be added here and then updated without recompiling glibc or other programs (no other program should use this data!), Andreas -- Andreas Jaeger, aj@suse.de, http://www.suse.de/~aj SUSE Linux Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany GPG fingerprint = 93A3 365E CE47 B889 DF7F FED1 389A 563C C272 A126
On Sunday 24 July 2005 06:56, Gil Weber wrote:
** Reply to message from "John R. Sowden" <jsowden@americansentry.net> on Sun, 24 Jul 2005 06:51:17 -0700
I just discovered that my clock is showing London, England time. I tried to configure the time zone, but it is already set to Pacific Std Time. Why did this happen? How do I fix it? How do I keep it from happening again? -- John R. Sowden
John, this happens to me from time to time. Most recently my clock was reading time in Sydney, OZ (but I'm in Florida).
In addition to setting to Pacific time zone be sure that you've also set it to "local time" rather than UTC.
That should keep it right. Gil Thanks-I yasted the clock from utc to local. -- John R. Sowden AMERICAN SENTRY SYSTEMS, INC. Residential & Commercial Alarm Service UL Listed Central Station Serving the San Francisco Bay Area Since 1967 mail@americansentry.net www.americansentry.net
On Sunday 24 July 2005 23:13, John R. Sowden wrote:
Thanks-I yasted the clock from utc to local.
It's not a good idea in general. The BIOS clock should be set to UTC. ISTR there are things, like summer time changes, that will fail if your hardware clock is set to local time The only time you want to have your BIOS clock set to local time is when you're dual booting with windows
participants (7)
-
Anders Johansson -
Andreas Jaeger -
Gil Weber -
John R. Sowden -
Ken Schneider -
Randall R Schulz -
Stan Goodman