Hi Since we've just changed our clocks over here I thought I'd better change my system time on my workstation so that my e-mail shows the +0100 value. Just now it shows +0000. I've tried to play around with hwclock and YaST2 to no effect. That was since last night. I just can't get either YaST2 or hwclock to have any effect on my system time. I can change it backwards and forwards but that's all. Still can't get the +0100 value to show up in my e-mail application. Also tried the KDE control centre. Can anyone help with this ? SuSE 8.1. -- Richard
Richard Ibbotson wrote:
Hi
Since we've just changed our clocks over here I thought I'd better change my system time on my workstation so that my e-mail shows the +0100 value. Just now it shows +0000. Can anyone help with this ? SuSE 8.1.
Try using YaST and setting the timezone to Europe/London and indicating that the hardware clock is local time. Internally, Linux runs on UTC and doesn't use the hardware clock, except to set the time if you reboot, but these YaST settings should ensure the time is reported as BST. If you want your clock set more accurately, try # /usr/sbin/ntpdate ntp.cis.strath.ac.uk # /sbin/hwclock -w This should set both the time in linux and your hardware clock to the correct time. Use # date to check the time. You should get something like Sun Mar 30 13:04:36 BST 2003 if you've set the system to British Summer time. You can check the headers of this email (Mozilla) to see how it uses BST. I don't know if mail clients should convert times to UTC so they're sorted in the right order. My experience is that it wouldn't make much difference because there are still a lot of people using obsolescent OSs that don't care what time their computer uses. -- JDL
John
Try using YaST and setting the timezone to Europe/London and indicating that the hardware clock is local time. Internally, Linux runs on UTC and doesn't use the hardware clock, except to set the time if you reboot, but these YaST settings should ensure the time is reported as BST.
There isn't a Europe/London setting under YaST. Just a Europe/Ireland setting. Looks like our capital city is now Dublin :) Tried it and it doesn't work. Still comes out as +0000 in the header.
If you want your clock set more accurately, try
# /usr/sbin/ntpdate ntp.cis.strath.ac.uk # /sbin/hwclock -w
I'll have a go at this but I don't suppose that this will change the +0000 value to +0100. Thank you -- Richard
John
I'll have a go at this but I don't suppose that this will change the +0000 value to +0100.
No, doesn't want to play.... sheflug:~ # /usr/sbin/ntpdate ntp.cis.strath.ac.uk 30 Mar 18:06:02 ntpdate[5061]: can't find host ntp.cis.strath.ac.uk 30 Mar 18:06:02 ntpdate[5061]: no servers can be used, exiting sheflug:~ # /usr/sbin/ntpdate ntp.cis.strath.ac.uk 30 Mar 18:06:20 ntpdate[5078]: no server suitable for synchronization found -- Richard
On Sun, 30 Mar 2003 17:07:21 +0000, Richard Ibbotson wrote:
John
I'll have a go at this but I don't suppose that this will change the +0000 value to +0100.
I don't know the details of your locale so I can't really comment on why it isn't working correctly. However, time changes should be automatic.
No, doesn't want to play....
sheflug:~ # /usr/sbin/ntpdate ntp.cis.strath.ac.uk 30 Mar 18:06:02 ntpdate[5061]: can't find host ntp.cis.strath.ac.uk 30 Mar 18:06:02 ntpdate[5061]: no servers can be used, exiting sheflug:~ # /usr/sbin/ntpdate ntp.cis.strath.ac.uk 30 Mar 18:06:20 ntpdate[5078]: no server suitable for synchronization found
There are lots of other ntp hosts available. I'm off line at the moment, but if you find the NTP website, there are other servers available to synchronize with. -- David Benfell, LCP benfell@parts-unknown.org --- Resume available at http://www.parts-unknown.org/resume.html
Richard Ibbotson wrote:
There isn't a Europe/London setting under YaST. Just a Europe/Ireland setting. Looks like our capital city is now Dublin :) Tried it and it doesn't work. Still comes out as +0000 in the header.
Sorry, should be Europe/United_Kingdom. Setting local time is also necessary. For ntpdate, you could try a different server or try pinging to see that it's still reachable. -- JDL
participants (3)
-
David Benfell
-
John Lamb
-
Richard Ibbotson