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