Re: [opensuse] Daylight Savings Change
Quite true; FWIW, I did enter a "bug report against an unlisted product" on the bugzilla. It isn't really a bug report in the usual bugzilla sense, and I got the distinct impression that report form is intended for commercial products. Cross your fingers and hope :-)
Darryl, Hopefully they will fix it, if not you can take a working zone file from 10.2 and use it to overwrite /etc/localtime. It worked on our systems. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-02-01 12:33, Coach-X wrote:
Quite true; FWIW, I did enter a "bug report against an unlisted product" on the bugzilla. It isn't really a bug report in the usual bugzilla sense, and I got the distinct impression that report form is intended for commercial products. Cross your fingers and hope :-)
Darryl, Hopefully they will fix it, if not you can take a working zone file from 10.2 and use it to overwrite /etc/localtime. It worked on our systems.
I thought timezone has glibc dependencies. I would be hesitant to stuff a package, or even a single file from a package, from one version into another version, without knowing those dependencies weren't going to be busted at all. -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 01 February 2007 13:36, Darryl Gregorash wrote:
Darryl, Hopefully they will fix it, if not you can take a working zone file from 10.2 and use it to overwrite /etc/localtime. It worked on our systems.
I thought timezone has glibc dependencies. I would be hesitant to stuff a package, or even a single file from a package, from one version into another version, without knowing those dependencies weren't going to be busted at all.
I just tried my /etc/localtime from a 10.2 box on a 9.2 box and it didn't work. Still have the old DST dates. :( I've got an 8.2 box lying around as well :o Custom app that has a dependency on an old verion of Tk. Porting, but still have to use the 8.2 box. Adjusting DST manually for now. -- Brian Jackson Photo Sports ~ People ~ Events http://www.BrianJacksonPhoto.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Brian Jackson wrote:
On Thursday 01 February 2007 13:36, Darryl Gregorash wrote:
Darryl, Hopefully they will fix it, if not you can take a working zone file from 10.2 and use it to overwrite /etc/localtime. It worked on our systems.
I thought timezone has glibc dependencies. I would be hesitant to stuff a package, or even a single file from a package, from one version into another version, without knowing those dependencies weren't going to be busted at all.
I just tried my /etc/localtime from a 10.2 box on a 9.2 box and it didn't work. Still have the old DST dates. :(
How did you test that? By calling zdump with a timezone name? That takes zonefiles from /usr/share/zoneinfo and not /etc/localtime.
I've got an 8.2 box lying around as well :o Custom app that has a dependency on an old verion of Tk. Porting, but still have to use the 8.2 box.
I just tried a 10.0 file on an 8.1 box and it works. Since there are no changes to 10.2, it should work as well. Check that /usr/lib/zoneinfo/localtime is a symlink to /etc/localtime, as it should be. Try the following first: -- Backup (rename) your /usr/share/zoneinfo/ tree. -- Copy that complete tree from the 10.2 system to your older system. -- Check that it works by calling zdump -v PST8PDT | grep 2007 It must output the March date and not the April date. -- If it does so, copy the appropriate zoneinfo file to /etc/localtime. Try again. HTH, Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----Original Message----- From: Brian Jackson [mailto:brian@brianjacksonphoto.com] Sent: Thursday, February 01, 2007 1:42 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Daylight Savings Change
On Thursday 01 February 2007 13:36, Darryl Gregorash wrote:
Darryl, Hopefully they will fix it, if not you can take a working
zone file
from 10.2 and use it to overwrite /etc/localtime. It worked on our systems.
I thought timezone has glibc dependencies. I would be hesitant to stuff a package, or even a single file from a package, from one version into another version, without knowing those dependencies weren't going to be busted at all.
I just tried my /etc/localtime from a 10.2 box on a 9.2 box and it didn't work. Still have the old DST dates. :(
I've got an 8.2 box lying around as well :o Custom app that has a dependency on an old verion of Tk. Porting, but still have to use the 8.2 box.
Adjusting DST manually for now.
So, I adapted the following instructions for Canada to fix DST on 8.2 and 9.x systems on my US systems. https://secure-support.novell.com/KanisaPlatform/Publishing/112/3615274_ f.SAL_Public.html Basically, I did the following: To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007 * Grabbed a copy of tzdata2007a.tar.gz from ftp://elsie.nci.nih.gov/pub. * Extracted the files from it. * zic northamerica To filter out regions that didn't have tzdata info in older distros. * grep US backward > backward.america * zic backward.america To check that it worked: * zdump -v US/Pacific | grep 2007 To relink localtime setting: * zic -l US/Pacific Since I did my testing in VMware, I reset the date to 1:59:55 on 3/11 to watch that it rolled over to 3 am. Also reset it to 1:59:55 on 4/1 to see that it rolled over to 2 am. Anyway, it seemed to work as far as the OS seemed concerned. Hope this helps. -p ~~~~~~~ Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam@fhcrc.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday 09 February 2007 16:46, Hirayama, Pat wrote: <snip>
So, I adapted the following instructions for Canada to fix DST on 8.2 and 9.x systems on my US systems.
https://secure-support.novell.com/KanisaPlatform/Publishing/112/3615274_ f.SAL_Public.html
Basically, I did the following:
To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007
What's all that stuff mean after one does the above command (mine I did with US/Central)? How do I know if I have to fix DST in my 9.3 system? Here's the result of the above command: US/Central Sun Apr 1 07:59:59 2007 UTC = Sun Apr 1 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Apr 1 08:00:00 2007 UTC = Sun Apr 1 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Oct 28 06:59:59 2007 UTC = Sun Oct 28 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Oct 28 07:00:00 2007 UTC = Sun Oct 28 01:00:00 2007 CST isdst=0 gmtoff=-21600 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote:
<snip>
So, I adapted the following instructions for Canada to fix DST on 8.2 and 9.x systems on my US systems.
https://secure-support.novell.com/KanisaPlatform/Publishing/112/3615274_ f.SAL_Public.html
Basically, I did the following:
To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007
What's all that stuff mean after one does the above command (mine I did with US/Central)? How do I know if I have to fix DST in my 9.3 system? Here's the result of the above command:
US/Central Sun Apr 1 07:59:59 2007 UTC = Sun Apr 1 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Apr 1 08:00:00 2007 UTC = Sun Apr 1 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Oct 28 06:59:59 2007 UTC = Sun Oct 28 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Oct 28 07:00:00 2007 UTC = Sun Oct 28 01:00:00 2007 CST isdst=0 gmtoff=-21600
I was wondering what it all meant also. I don't think you have the patch. I assume the first two are start dates and next two end dates. Not sure why there is a couple minutes difference in the times. I also use the NTP service so I assume it will automatically correct the time. Here's mine: US/Pacific Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0 gmtoff=-28800 US/Pacific Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0 gmtoff=-28800 And I know DST starts in March this year and goes past Halloween.I am on OpenSUSE 10.2 -- Russ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
russbucket wrote:
I was wondering what it all meant also. I don't think you have the patch. I assume the first two are start dates and next two end dates. Not sure why there is a couple minutes difference in the times. I also use the NTP service so I assume it will automatically correct the time. Here's mine: US/Pacific Sun Mar 11 09:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 PST isdst=0 gmtoff=-28800 US/Pacific Sun Mar 11 10:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Nov 4 08:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 PDT isdst=1 gmtoff=-25200 US/Pacific Sun Nov 4 09:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 PST isdst=0 gmtoff=-28800 And I know DST starts in March this year and goes past Halloween.I am on OpenSUSE 10.2
ntp deals only with UTC. timezone and DST translations are the responsibility of the ntp client, not the server. Your output above is correct. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Friday 2007-02-09 at 19:54 -0800, J Sloan wrote: ...
ntp deals only with UTC. timezone and DST translations are the responsibility of the ntp client, not the server. Your output above is correct.
Rather of the operating system, not even the ntp client. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFzbICtTMYHG2NR9URAtfuAJ9IDQvcn1UklJKElgHMCqrN0D0AJQCcD2b/ kenkzWNF6DOw9yMK3VnrS58= =lB7N -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Honestly, this is why we switched all our timezones to UTC/GMT in the past, headaches like this one and now we are all on the same page. On 2/10/07, Carlos E. R. <robin.listas@telefonica.net> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Friday 2007-02-09 at 19:54 -0800, J Sloan wrote:
...
ntp deals only with UTC. timezone and DST translations are the responsibility of the ntp client, not the server. Your output above is correct.
Rather of the operating system, not even the ntp client.
- -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFzbICtTMYHG2NR9URAtfuAJ9IDQvcn1UklJKElgHMCqrN0D0AJQCcD2b/ kenkzWNF6DOw9yMK3VnrS58= =lB7N -----END PGP SIGNATURE-----
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-02-10 at 10:23 -0500, Rami Michael wrote:
Honestly, this is why we switched all our timezones to UTC/GMT in the past, headaches like this one and now we are all on the same page.
Linux doesn't use local time internally. Local time is calculated for display only. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFzenwtTMYHG2NR9URAvosAKCRJShZ5Sd1XBTj5mYrNh19TTvxqACgmMuz ejqFHZe7LUZ5XxjGAHCIz2Y= =wxAg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Rami Michael wrote:
Honestly, this is why we switched all our timezones to UTC/GMT in the past, headaches like this one and now we are all on the same page.
On 2/10/07, Carlos E. R. <robin.listas@telefonica.net> wrote:
The Friday 2007-02-09 at 19:54 -0800, J Sloan wrote:
...
ntp deals only with UTC. timezone and DST translations are the responsibility of the ntp client, not the server. Your output above is correct.
Rather of the operating system, not even the ntp client.
Indeed, that is how I meant it - client as in "the client sytem", not the "ntp client program". Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----Original Message----- From: russbucket [mailto:russbucket@nwi.net] Sent: Friday, February 09, 2007 7:48 PM To: opensuse@opensuse.org Subject: Re: [opensuse] Daylight Savings Change
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote:
<snip>
To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007
What's all that stuff mean after one does the above command (mine I did with US/Central)? How do I know if I have to fix DST in my 9.3 system? Here's the result of the above command:
US/Central Sun Apr 1 07:59:59 2007 UTC = Sun Apr 1 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Apr 1 08:00:00 2007 UTC = Sun Apr 1 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Oct 28 06:59:59 2007 UTC = Sun Oct 28 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Oct 28 07:00:00 2007 UTC = Sun Oct 28 01:00:00 2007 CST isdst=0 gmtoff=-21600
OK, these are the times/dates that Standard Time / Daylight Savings Time are set to start/end in 2007 for the Central time zone in the US. These numbers indicate that your system is not patched ... It is still following the old rules. In other words, Sun Apr 1 1:59:59 will be followed by Sun Apr 1 3:00:00. Once your system has been corrected, you should get the following output: US/Central Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmtoff=-21600 Thanks, -p -- Pat Hirayama IT / Server Operations Fred Hutchinson Cancer Research Center phirayam@fhcrc.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 February 2007 10:38, Hirayama, Pat wrote:
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote:
<snip>
To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007
What's all that stuff mean after one does the above command (mine
I did
with US/Central)? How do I know if I have to fix DST in my 9.3
system?
Here's the result of the above command:
US/Central Sun Apr 1 07:59:59 2007 UTC = Sun Apr 1 01:59:59 2007
CST isdst=0 gmtoff=-21600
US/Central Sun Apr 1 08:00:00 2007 UTC = Sun Apr 1 03:00:00 2007
CDT isdst=1 gmtoff=-18000
US/Central Sun Oct 28 06:59:59 2007 UTC = Sun Oct 28 01:59:59 2007
CDT isdst=1 gmtoff=-18000
US/Central Sun Oct 28 07:00:00 2007 UTC = Sun Oct 28 01:00:00 2007
CST isdst=0 gmtoff=-21600
OK, these are the times/dates that Standard Time / Daylight Savings Time are set to start/end in 2007 for the Central time zone in the US. These numbers indicate that your system is not patched ... It is still following the old rules. In other words, Sun Apr 1 1:59:59 will be followed by Sun Apr 1 3:00:00. Once your system has been corrected, you should get the following output:
US/Central Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST isdst=0 gmtoff=-21600 US/Central Sun Mar 11 08:00:00 2007 UTC = Sun Mar 11 03:00:00 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 06:59:59 2007 UTC = Sun Nov 4 01:59:59 2007 CDT isdst=1 gmtoff=-18000 US/Central Sun Nov 4 07:00:00 2007 UTC = Sun Nov 4 01:00:00 2007 CST isdst=0 gmtoff=-21600
Thanks, Pat. I did the instructions you put up on this list, and it seems to have worked. Good job, bud. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 February 2007 17:39, JB wrote:
On Thursday 15 February 2007 10:38, Hirayama, Pat wrote:
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote:
<snip>
To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007
What's all that stuff mean after one does the above command (mine /snip/ and so on. . .
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something? --doug -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doug McGarrett wrote:
On Thursday 15 February 2007 17:39, JB wrote:
On Thursday 15 February 2007 10:38, Hirayama, Pat wrote:
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote: <snip>
To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007 What's all that stuff mean after one does the above command (mine /snip/ and so on. . .
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something?
Hmm, ntp service is free, and the software ships with suse. Why would any linux user settle for having the wrong time on their system? In any case, whenever I'm looking at the logs, I find it pretty important to know what time something happened. Not approximately. Exactly. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 15 February 2007 20:40, J Sloan wrote:
Doug McGarrett wrote:
On Thursday 15 February 2007 17:39, JB wrote:
On Thursday 15 February 2007 10:38, Hirayama, Pat wrote:
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote:
<snip>
> To verify that I had to fix DST: > * zdump -v US/Pacific | grep 2007
What's all that stuff mean after one does the above command (mine
/snip/ and so on. . .
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something?
Hmm, ntp service is free, and the software ships with suse. Why would any linux user settle for having the wrong time on their system?
In any case, whenever I'm looking at the logs, I find it pretty important to know what time something happened. Not approximately. Exactly.
Joe
Why don't you just change the time manually post new DST changes? -- Ben Kevan SLED 10 - Kmail 1.9.1 "How much can you know about yourself if you've never been in a fight" - Fight Club -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-02-15 at 20:40 -0800, J Sloan wrote:
Doug McGarrett wrote:
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something?
Hmm, ntp service is free, and the software ships with suse. Why would any linux user settle for having the wrong time on their system?
In any case, whenever I'm looking at the logs, I find it pretty important to know what time something happened. Not approximately. Exactly.
The ntp service is not affected by the daylight time saving adjustement, nor by it being correct or incorrect, because ntp uses UTC, which does not vary summer or winter. Nor will using an ntp client correct the daylight time saving adjustement when the time comes. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF19T/tTMYHG2NR9URAluOAJ98UWCOcDwChCZEQKt3FhrPIEPA6gCfRkpf slbr4Iq7no9nxT4Kkj/f6vQ= =oJ/o -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Thursday 2007-02-15 at 20:40 -0800, J Sloan wrote:
Doug McGarrett wrote:
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something? Hmm, ntp service is free, and the software ships with suse. Why would any linux user settle for having the wrong time on their system?
In any case, whenever I'm looking at the logs, I find it pretty important to know what time something happened. Not approximately. Exactly.
The ntp service is not affected by the daylight time saving adjustement, nor by it being correct or incorrect, because ntp uses UTC, which does not vary summer or winter.
Nor will using an ntp client correct the daylight time saving adjustement when the time comes.
But it would correct the OP's condition, that of his system time being "a few minutes off". Nothing more was implied. Joe -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-02-17 at 20:37 -0800, J Sloan wrote: ...
Nor will using an ntp client correct the daylight time saving adjustement when the time comes.
But it would correct the OP's condition, that of his system time being "a few minutes off". Nothing more was implied.
I think the OP was "aragonx" and he worried about «the change in daylight savings in the United States» for 9.3 ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF2IcQtTMYHG2NR9URAm94AKCF6jEtghVUlJS8LCFBxQbk19GJfwCaAlM4 cgOrQaWyOXku3zmUMBQITLU= =kdxy -----END PGP SIGNATURE-----
J Sloan wrote:
Doug McGarrett wrote:
On Thursday 15 February 2007 17:39, JB wrote:
On Thursday 15 February 2007 10:38, Hirayama, Pat wrote:
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote: <snip>
> To verify that I had to fix DST: > * zdump -v US/Pacific | grep 2007 What's all that stuff mean after one does the above command (mine /snip/ and so on. . .
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something?
Hmm, ntp service is free, and the software ships with suse. Why would any linux user settle for having the wrong time on their system?
Hmm, ntp is not relevant -- it has nothing to do with DST, the system clock runs on UTC. You are right about timestamps in logs, though; they use local time, and here the correct zoneinfo for you US folks is of interest. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Doug McGarrett wrote:
On Thursday 15 February 2007 17:39, JB wrote:
On Thursday 15 February 2007 10:38, Hirayama, Pat wrote:
On Friday February 9 2007 16:21, JB wrote:
On Friday 09 February 2007 16:46, Hirayama, Pat wrote:
<snip>
To verify that I had to fix DST: * zdump -v US/Pacific | grep 2007
What's all that stuff mean after one does the above command (mine
/snip/ and so on. . .
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something?
Ever notice how some mail list replies appear before the question was asked? It's usually because someone's clock is mis-configured. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-02-17 at 21:17 -0500, James Knott wrote:
if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something?
Ever notice how some mail list replies appear before the question was asked? It's usually because someone's clock is mis-configured.
Nonononono. X-) If you get a replay earlier that the question, it is because it got stuck on some server, but not because of our clock problems. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF19PKtTMYHG2NR9URAnjaAJ9P7YK93moY25aPzuySjxRUU0wCeACfVHma f1FcTpy5o0QccwQzvlgw7JM= =ytJg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Saturday 17 February 2007 20:19, Carlos E. R. wrote:
The Saturday 2007-02-17 at 21:17 -0500, James Knott wrote:
...
Ever notice how some mail list replies appear before the question was asked? It's usually because someone's clock is mis-configured.
Nonononono. X-)
If you get a replay earlier that the question, it is because it got stuck on some server, but not because of our clock problems.
Both can (appear to) be true. If the mail client sorts incoming mail / mailboxes by date, then James' observation can be valid. If the mail client shows messages in the order received, then Carlos' point is correct.
Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2007-02-17 at 20:41 -0800, Randall R Schulz wrote:
Ever notice how some mail list replies appear before the question was asked? It's usually because someone's clock is mis-configured.
Nonononono. X-)
If you get a replay earlier that the question, it is because it got stuck on some server, but not because of our clock problems.
Both can (appear to) be true. If the mail client sorts incoming mail / mailboxes by date, then James' observation can be valid. If the mail client shows messages in the order received, then Carlos' point is correct.
Absolutely :-) I tend to forget that, as Pine can sort by thread, sorted by arrival date instead of the header date. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF2Id6tTMYHG2NR9URAn2oAJ0fWapa9LVjCetfcoP7t3La62mw7wCfZhRE qGTPIS48h5B1GPfL/pofALQ= =6Gqd -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Randall R Schulz wrote:
On Saturday 17 February 2007 20:19, Carlos E. R. wrote:
The Saturday 2007-02-17 at 21:17 -0500, James Knott wrote:
...
Ever notice how some mail list replies appear before the question was asked? It's usually because someone's clock is mis-configured.
Nonononono. X-)
If you get a replay earlier that the question, it is because it got stuck on some server, but not because of our clock problems.
Both can (appear to) be true. If the mail client sorts incoming mail / mailboxes by date, then James' observation can be valid. If the mail client shows messages in the order received, then Carlos' point is correct.
The other possibility, as I mentioned in another note, is a temporal anomaly. My trip took me to Edmonton, which is beyond the Delta Quadrant. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
The Saturday 2007-02-17 at 21:17 -0500, James Knott wrote:
if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something? Ever notice how some mail list replies appear before the question was asked? It's usually because someone's clock is mis-configured.
Nonononono. X-)
If you get a replay earlier that the question, it is because it got stuck on some server, but not because of our clock problems.
I'm referring to the date as displayed on the message, not when actually received on my computer. For example, yesterday after returning home from a business trip, I had new mail going back a few days. In that mail there were a couple of examples where the original message appeared after the replies. Currently, there is another message further down the inbox that was apparently posted tomorrow! Then again, while on my trip, I may have passed through a temporal anomaly. ;-) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-02-18 at 12:03 -0500, James Knott wrote:
Nonononono. X-)
If you get a replay earlier that the question, it is because it got stuck on some server, but not because of our clock problems.
I'm referring to the date as displayed on the message, not when actually received on my computer. For example, yesterday after returning home from a business trip, I had new mail going back a few days. In that mail there were a couple of examples where the original message appeared after the replies. Currently, there is another message further down the inbox that was apparently posted tomorrow!
Those do not trouble me much, as I tell Pine to sort by thread by arrival date. It is a sort method I sorely miss when using Kmail or Thunderbird.
Then again, while on my trip, I may have passed through a temporal anomaly. ;-)
Hum! Would that be Voyager or the 1st Enterprise? ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF2OUmtTMYHG2NR9URAslEAJ0d2Tash6mv3p/D0V1nf3pggxecNgCfVja/ RduOZhmNFE0EyBJxY8S/S3I= =QbRo -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos, On Sunday 18 February 2007 15:45, Carlos E. R. wrote:
...
Those do not trouble me much, as I tell Pine to sort by thread by arrival date. It is a sort method I sorely miss when using Kmail or Thunderbird.
KMail has both by-message-date and by-arrival-order mailbox sorting.
Carlos E. R.
Randall Schulz -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2007-02-18 at 16:04 -0800, Randall R Schulz wrote:
Those do not trouble me much, as I tell Pine to sort by thread by arrival date. It is a sort method I sorely miss when using Kmail or Thunderbird.
KMail has both by-message-date and by-arrival-order mailbox sorting.
And threaded? I mean, thread sort, and the threads sorted by arrival date? - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF2O+gtTMYHG2NR9URAopgAJ4ofNgUmPwW/vyZLvbHkJarVlnf4QCfVcCT KHYKsKt9M9MdH4baZnsM2Jg= =Gttl -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Sunday 18 February 2007, Carlos E. R. wrote:
The Sunday 2007-02-18 at 16:04 -0800, Randall R Schulz wrote:
Those do not trouble me much, as I tell Pine to sort by thread by arrival date. It is a sort method I sorely miss when using Kmail or Thunderbird.
KMail has both by-message-date and by-arrival-order mailbox sorting.
And threaded? I mean, thread sort, and the threads sorted by arrival date?
Yes, And Threaded. If you check the Threaded view checkbox messages will be properly threaded (by message ids) and then within threads sorted to Date/Arrival/Subject/Sender/etc order. So when you sort by arrival order with threaded on the first sort is by threads, and the threads are sorted to arrival order by the uppermost thread entry, then within threads they are sorted by the threading, and by arrival order when more than one poster replies to the same thread member. Its the best I've seen. The only problem is it tends to make me really irritated when users reply with non-threading mailers which causes thread splintering and fives you 5 or 8 threads for the same subject. A peek at the headers of such posts usually reveals Outlook. sigh... -- _____________________________________ John Andersen
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2007-02-15 at 23:36 -0500, Doug McGarrett wrote:
Unless you are in a business, where time of messages is important, what difference does it make if the time change is out of sync? I'd fix mine, if someone would say "YaST this" for 9.3 So somebody tell me, Yast (timefix). But i really don't care if it's fixed. The clock is a few minutes off now, who cares if it's off an hour? Am I missing something?
But it will be off during days! correct: US/Central Sun Mar 11 07:59:59 2007 UTC = Sun Mar 11 01:59:59 2007 CST incorrect: US/Central Sun Apr 1 07:59:59 2007 UTC = Sun Apr 1 01:59:59 2007 CST If I understand it correctly, the time was to be changed on April 1, and now it will have to be changed on Mar 11 (US politicians change of mind). Ie, the local displayed time on an incorrect, not patched system will be off one hour from March 11th till April 1st. It is not only logs and mail messages that will be incorrect. It is the hour displayed by your computer that will be off by one hour. If you correct it, and you use ntp, it will go back to the "legally incorrect" time. You might be late for work or lunch! :-P - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFF19iZtTMYHG2NR9URAhK8AJ4kqxubZg/aFeh0wVKzTEetQobTNQCcDi2+ UT2Vu4+q/vnGEWFIuH8n8BQ= =jix7 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Darryl Gregorash wrote:
On 2007-02-01 12:33, Coach-X wrote:
Quite true; FWIW, I did enter a "bug report against an unlisted product" on the bugzilla. It isn't really a bug report in the usual bugzilla sense, and I got the distinct impression that report form is intended for commercial products. Cross your fingers and hope :-)
Darryl, Hopefully they will fix it, if not you can take a working zone file from 10.2 and use it to overwrite /etc/localtime. It worked on our systems.
I thought timezone has glibc dependencies.
/etc/localtime is just a data file, and thus does not use any shared libraries. I just tried to copy the PST8PDT zonefile to an old SUSE 8.1 that I have still running in an VMware -- and it works. Since the format is compatible so long back, it will work with all other intermediate releases as well. Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2007-02-01 16:10, Joachim Schrod wrote:
Darryl Gregorash wrote:
<snip>
I thought timezone has glibc dependencies.
/etc/localtime is just a data file, and thus does not use any shared libraries.
I wasn't certain, since "rpm -q --requires timezone" indicates the following glibc dependencies: libc.so.6 libc.so.6(GLIBC_2.0) libc.so.6(GLIBC_2.1) libc.so.6(GLIBC_2.3) -- Moral indignation is jealousy with a halo. -- HG Wells -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (15)
-
Ben Kevan -
Brian Jackson -
Carlos E. R. -
Coach-X -
Darryl Gregorash -
Doug McGarrett -
Hirayama, Pat -
J Sloan -
James Knott -
JB -
Joachim Schrod -
John Andersen -
Rami Michael -
Randall R Schulz -
russbucket