Ok you unlucky ones, here it is: I live in Hawaii. I have spent a lot of time and effort setting my time to "gmt-10"= hawaii time. I realise that the work ethic around here does leave a lot of room to move around in, HOWEVER: as soon as I turned the xntpd daemon on, well, actually about 4-5 hours later, the kde displayed time jumped to California time, 2 hours ahead!!!! That would be too much for most but the real hard core "hawaii time die hards"!! I dutyfully right clicked on the time display, typed in my root pword and prepared myself to reset the time, ALAS, it WAS properly set in Yast!!!!!!! The kde display just added a couple of hours to confuse us haole insurgents!!!! Now the clincher: A "redo" resulted in a time display 3 hours behind the local time, that would be 5 hours behind California time and 3 hours behind "normal" time, ie summertime time diff from Ca (we do not the silly fall back / jump forward one hour bit in the fall and in the Spring)!!!!!!! I mean nothing against California, actually i wish them the best with their problems, BUT I DO NOT WANT TO SEE THEIR TIME AS MINE!!!!! Any ideas? tia, Dimitris
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Sun, 1 Feb 2004 00:36:31 -0800 plain <kanenas@hawaii.rr.com> wrote:
Ok you unlucky ones, here it is: I live in Hawaii. I have spent a lot of time and effort setting my time to "gmt-10"= hawaii time. I realise that the work ethic around here does leave a lot of room to move around in, HOWEVER: as soon as I turned the xntpd daemon on, well, actually about 4-5 hours later, the kde displayed time jumped to California time, 2 hours ahead!!!! That would be too much for most but the real hard core "hawaii time die hards"!!
I dutyfully right clicked on the time display, typed in my root pword and prepared myself to reset the time, ALAS, it WAS properly set in Yast!!!!!!! The kde display just added a couple of hours to confuse us haole insurgents!!!! Now the clincher: A "redo" resulted in a time display 3 hours behind the local time, that would be 5 hours behind California time and 3 hours behind "normal" time, ie summertime time diff from Ca (we do not the silly fall back / jump forward one hour bit in the fall and in the Spring)!!!!!!! I mean nothing against California, actually i wish them the best with their problems, BUT I DO NOT WANT TO SEE THEIR TIME AS MINE!!!!! Is your system set to local time or UTC time? Use YaST, and click on System/Editor for Sysconfig files Then open environment/clock. HWCLOCK should be set to either -u or --localtime. TIMEZONE should be set to US/Hawaii This should set your timezone up correctly. Certainly GMT-10 should be correc.t
The time servers you use in /etc/ntp.conf should not affect your timezone settings. Once you have verified that YaST has this correct, then run the date command with the -u flag. This will display the UTC (eg. GMT) time. In your case, this should show a time 10 hours ahead of yours. Also, use the hwclock command with the --show parameter. That will also show the correct timezone. AFAIK, KDE would be using the time(3), or gettimeofday(2) functions to get the current time. The latter function also optionally gets the time zone information. So, I think that the problem is still with your system and not with KDE per se. If you are a programmer, use the gettimeofday system call and write a short program to check the timezone, but hwclock --show should provide the correct information. - -- Jerry Feldman <gaf@blu.org> Boston Linux and Unix user group http://www.blu.org PGP key id:C5061EA9 PGP Key fingerprint:053C 73EC 3AC1 5C44 3E14 9245 FB00 3ED5 C506 1EA9 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (GNU/Linux) iD8DBQFAHQV2+wA+1cUGHqkRAoYiAJ4lBnyiJ9gmAPyGiETmh45FzkPgFgCfRxhx xgxwoYcIsceRXt+56dkDGO4= =tGjW -----END PGP SIGNATURE-----
The Sunday 2004-02-01 at 00:36 -0800, plain wrote:
Ok you unlucky ones, here it is: I live in Hawaii. I have spent a lot of time and effort setting my time to "gmt-10"= hawaii time. I realise that the work ethic around here does leave a lot of room to move around in, HOWEVER: as soon as I turned the xntpd daemon on, well, actually about 4-5 hours later, the kde displayed time jumped to California time, 2 hours ahead!!!! That would be too much for most but the real hard core "hawaii time die hards"!!
xntp knows nothing about Hawaii or California time: it uses only UTC time. The conversion to local time is done by your system. As a matter of fact, you should check what the command "date" says about the hour you have, not kde. And by the way, you should not tinker with the hour while xntp is running. -- Cheers, Carlos Robinson
On Sunday 01 February 2004 06:31, Carlos E. R. wrote:
The Sunday 2004-02-01 at 00:36 -0800, plain wrote:
Ok you unlucky ones, here it is: I live in Hawaii. I have spent a lot of time and effort setting my time to "gmt-10"= hawaii time. I realise that the work ethic around here does leave a lot of room to move around in, HOWEVER: as soon as I turned the xntpd daemon on, well, actually about 4-5 hours later, the kde displayed time jumped to California time, 2 hours ahead!!!! That would be too much for most but the real hard core "hawaii time die hards"!!
xntp knows nothing about Hawaii or California time: it uses only UTC time. The conversion to local time is done by your system. As a matter of fact, you should check what the command "date" says about the hour you have, not kde.
And by the way, you should not tinker with the hour while xntp is running.
-- Cheers, Carlos Robinson
Thanks Jerry and Carlos. The setup was for the Hawaii time zone, local time. The discrepancy was between displayed time and the time Yast indicated. the date command showed the correct time, just like Yast. What I think might be an obscure problem is that sometimes kde does not pick up the timezone info. I do recall (in 8.2) occasions where changing the timezone in Yast was not reflected on the screen. Sorry Jerry, I am not a programmer and i am not involved in development to hunt this down, but thanks for the gettime pointers. But perhaps the re-re-resetting of TZ's in Yast last night finally worked. Setting it to another tz, getting out of yast, going back in and resetting to the correct tz might have forced the change that could have been missed by just reclicking on the "old" tz. This morning....the display shows the correct time and timezone!!!!!! So far, this has been my greatest problem with the new mobo and upgrade to 9.0, the transition has been absolutely uneventful and trouble free :) i guess i will start adding things here and there, it's been too easy:)) Dimitris
participants (3)
-
Carlos E. R. -
Jerry Feldman -
plain