Re: [SLE] Daylight Saving time change?
Found this subject in the archives, haven't received any of the messages yet. But I noticed this problem too. The explanations confused me, can someone please clarify? On install, I set up the time the same way I had done it when I installed 10.0, EST. The older system always changed automatically. -- ED --
On 30/10/06 08:07, Ed McCanless wrote:
Found this subject in the archives, haven't received any of the messages yet. But I noticed this problem too. The explanations confused me, can someone please clarify? On install, I set up the time the same way I had done it when I installed 10.0, EST. The older system always changed automatically.
( I am sure glad all this talk of what is the hardware clock, and what does or does not run in UTC, is helping people like Ed and Simon to solve their basic problem -- <insert tongue-in-cheek smiley here, I haven't got one>.) I've just spent a bit of time comparing file sizes in the timezone files, /usr/share/zoneinfo/*. Although these files are in a binary format, their sizes alone seem to be sufficiently informative of which files do, and do not, involve DST adjustments. If you set your timezone to just "EST" (which you can check by running 'grep TIMEZONE /etc/sysconfig/clock', without the quotes of course), then I believe your clock has been set to plain EST, not daylight time involved. Similarly, Simon should check for a timezone set to just "MST" in the same place. Ed's timezone should probably be EST5EDT or US/Eastern, while Simon's should be MST7MDT or US/Mountain. These changes can be made directly into /etc/sysconfig/clock (after which the clock should be restarted, "/etc/init.d/boot.clock restart"), or in the Yast Sysconfig Editor, System/environment/clock/timezone, or in Yast/System/Date and time (Yast will restart the clock automatically).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-30 at 17:49 -0600, Darryl Gregorash wrote: ...
These changes can be made directly into /etc/sysconfig/clock
Mmmm... I would rather recomend using Yast for this. If you insert the wrong string, the results will be, er... confusing. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFRpUDtTMYHG2NR9URAqP6AJ0eUvPagsccCLNHfHD2ByHsf6m9aQCeKw7j gVbReqRGlfCSAbk0WPLWjhg= =QPla -----END PGP SIGNATURE-----
On 30/10/06 18:12, Carlos E. R. wrote:
The Monday 2006-10-30 at 17:49 -0600, Darryl Gregorash wrote:
...
These changes can be made directly into /etc/sysconfig/clock
Mmmm... I would rather recomend using Yast for this. If you insert the wrong string, the results will be, er... confusing.
That, my friend, is why the good lord invented copy'n'paste :-) Anyone not feeling comfortable hacking away at the sysconfig files in a text editor should, of course, use the configuration tool(s) at his disposal. At the same time, anyone who uses the Yast sysconfig editor with any degree of confidence probably shouldn't have to worry about getting things wrong editing the files directly, so long as he reads the commentaries accompanying each variable (which seem always to state which service(s) need to be restarted).
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-30 at 19:00 -0600, Darryl Gregorash wrote:
These changes can be made directly into /etc/sysconfig/clock
Mmmm... I would rather recomend using Yast for this. If you insert the wrong string, the results will be, er... confusing.
That, my friend, is why the good lord invented copy'n'paste :-)
In this case, it is not so simple. You have to look at the directory "/usr/share/zoneinfo/", and choose one - and not all are valid. For example you may chose "Europe", so you have to look further at "/usr/share/zoneinfo/Europe/" and choose your capital city, like for instance, "Madrid". Therefore, I'd had to enter "Europe/Madrid" in the sysconfig/clock file. This is one of the cases when Yast is so much easier and safer ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFRrjrtTMYHG2NR9URAgbDAJ9cSj8oE0BAzmTDUAlGvkpeMkogugCeMgEJ SxaN0RDF0hMELpzJpbt0OrQ= =PeQy -----END PGP SIGNATURE-----
On 30/10/06 20:46, Carlos E. R. wrote:
The Monday 2006-10-30 at 19:00 -0600, Darryl Gregorash wrote:
These changes can be made directly into /etc/sysconfig/clock Mmmm... I would rather recomend using Yast for this. If you insert the wrong string, the results will be, er... confusing.
That, my friend, is why the good lord invented copy'n'paste :-)
In this case, it is not so simple. You have to look at the directory "/usr/share/zoneinfo/", and choose one - and not all are valid. For example you may chose "Europe", so you have to look further at "/usr/share/zoneinfo/Europe/" and choose your capital city, like for instance, "Madrid". Therefore, I'd had to enter "Europe/Madrid" in the sysconfig/clock file.
This is one of the cases when Yast is so much easier and safer ;-)
In this case, it actually is so simple. I already did the legwork for both Ed and Simon -- all they have to do is copy and paste. They don't have to worry about how the /usr/share/zoneinfo/ tree is set up, don't have to worry about "where is that *#@$*&(*& MST7MDT thingy anyway" when they use the Date and Time panel in Yast (but for the record, it is under "Global", which is merely yast-ese for "it is in /usr/share/zoninfo/ and not in any subdirectory of that), and certainly don't have to wonder what that "etc" thingy is at the bottom of the zone column in the Yast Date and Time panel. I don't know how much more simple it could be, and I really don't know why people always have to argue about what is/should be/could be/might be, without actually directly answering the OP's question(s), when someone else has actually gone out and found a safe, complete, solution for the OP. Next will you be suggesting that using the Yast sysconfig editor is equally evil? (That is surely how Ed entered his timezone information.)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2006-10-30 at 21:02 -0600, Darryl Gregorash wrote:
In this case, it actually is so simple. I already did the legwork for both Ed and Simon -- all they have to do is copy and paste. They don't have to worry about how the /usr/share/zoneinfo/ tree is set up, don't have to worry about "where is that *#@$*&(*& MST7MDT thingy anyway" when they use the Date and Time panel in Yast (but for the record, it is under "Global", which is merely yast-ese for "it is in /usr/share/zoninfo/ and not in any subdirectory of that), and certainly don't have to wonder what that "etc" thingy is at the bottom of the zone column in the Yast Date and Time panel.
I don't know how much more simple it could be, and I really don't know why people always have to argue about what is/should be/could be/might be, without actually directly answering the OP's question(s), when someone else has actually gone out and found a safe, complete, solution for the OP. Next will you be suggesting that using the Yast sysconfig editor is equally evil? (That is surely how Ed entered his timezone information.)
Sigh.... No comment. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFRr6vtTMYHG2NR9URAqnBAJ4g04Wasc2Oz3zBTWtBveJfYzpMRgCfWS32 wxyp9v7OCLOqixr0uiDQngw= =W6QP -----END PGP SIGNATURE-----
Darryl Gregorash wrote:
In this case, it actually is so simple. I already did the legwork for both Ed and Simon -- all they have to do is copy and paste. They don't have to worry about how the /usr/share/zoneinfo/ tree is set up, don't have to worry about "where is that *#@$*&(*& MST7MDT thingy anyway" when they use the Date and Time panel in Yast (but for the record, it is under "Global", which is merely yast-ese for "it is in /usr/share/zoninfo/ and not in any subdirectory of that), and certainly don't have to wonder what that "etc" thingy is at the bottom of the zone column in the Yast Date and Time panel.
I don't know how much more simple it could be, and I really don't know why people always have to argue about what is/should be/could be/might be, without actually directly answering the OP's question(s), when someone else has actually gone out and found a safe, complete, solution for the OP. Next will you be suggesting that using the Yast sysconfig editor is equally evil? (That is surely how Ed entered his timezone information.)
In Carl's defense, let me say that it is good to have input from several different sources, on several different methods. It' true that I still depend on the YaST tool a lot, but I am trying to learn scripting, so all the info I've seen in this discussion will be a help to me in one way or another. Even when two people say the same thing, I will understand one better, so please don't discourage anyone from telling what they know. Thanks All, -- ED --
On 31/10/06 20:30, Ed McCanless wrote:
In Carl's defense, let me say that it is good to have input from several different sources, on several different methods.
True, and I apologize to Carlos for trying to take his head off. He is simply rather more reluctant than I am to send someone off digging in a config file with a text editor, and his reasons for thinking that way are as valid as mine. You didn't say if you did manage to correct the problem :-)
Darryl Gregorash wrote:
On 31/10/06 20:30, Ed McCanless wrote:
<CUT> You didn't say if you did manage to correct the problem :-)
Sorry about that. I figured it would be six months before I can check if it's fixed, so I have procrastinated. I am saving all the suggestions, though. -- ED --
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-11-01 at 16:10 -0500, Ed McCanless wrote: On Wed, 1 Nov 2006, Ed McCanless wrote:
Darryl Gregorash wrote:
You didn't say if you did manage to correct the problem :-)
Sorry about that. I figured it would be six months before I can check if it's fixed, so I have procrastinated. I am saving all the suggestions, though.
If I were you, I would be unable to wait: I'd change the clock to some minutes before the time shift and watch what happens. I'm that impatient ;-) The snag is that you'd get what you expected and quite some things you probably don't. And a few more when you adjust back the clock :-P (I did it once) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFSSe0tTMYHG2NR9URAr+IAKCO5kUi+uZZHQxNONrRPQXtPnsLvwCffafx 6PHnTuhCP8n0WGRkLdfiCek= =FQZ8 -----END PGP SIGNATURE-----
Carlos E. R. wrote:
I have procrastinated. I am saving all the >suggestions, though.
If I were you, I would be unable to wait: I'd change the clock to some minutes before the time shift and watch what happens. I'm that impatient ;-)
The snag is that you'd get what you expected and quite some things you probably don't. And a few more when you adjust back the clock :-P
(I did it once)
Actually, I've been too busy to be impatient. My list mail has been coming in normally now for 2 days, and I'm trying not to miss anything while getting my real work done. Also those unexpected things worry me a little. -- ED --
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-11-01 at 22:42 -0500, Ed McCanless wrote:
The snag is that you'd get what you expected and quite some things you probably don't. And a few more when you adjust back the clock :-P
(I did it once)
Actually, I've been too busy to be impatient. My list mail has been coming in normally now for 2 days, and I'm trying not to miss anything while getting my real work done. Also those unexpected things worry me a little.
They should - but it's part of the learning experience :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFSe8gtTMYHG2NR9URAn3AAJoCSMU43wRka4oiXN+tqiFv9CxZawCfbi68 NLqXC8aGtZtDRNyKwmtnj0Q= =8WqD -----END PGP SIGNATURE-----
participants (3)
-
Carlos E. R. -
Darryl Gregorash -
Ed McCanless