[opensuse] WARNING about Beta 2 and date/time setting
The last msg I posted here was only about 20 minutes ago but if you look at the date/time stamp of that msg it is dated 1 day and many hours in the FUTURE (ie, tomorrow, 8 May; today it is 7 May 1520 hours my time, Aust Eastern Standard Time). Beta 2 cannot handle date/time correctly so if you are using it (like I just did) to post a message then bear this in mind. The problem really comes up if you try and do something like 'make cloneconfig' where you will get a WARNING stating that something-or-another is "in the future". If you try and make the system adjust the time to some time server using the NTP option in Yast Control Centre then forget it: NTP option doesn't even 'fire up'. One way out is to use the CLI 'ntpdate -u <IP-of-timeserver>' to get the date/time set correctly. Ciao. -- If you want to know what a man is like, take a look at how he treats his inferiors not his equals. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
The last msg I posted here was only about 20 minutes ago but if you look at the date/time stamp of that msg it is dated 1 day and many hours in the FUTURE (ie, tomorrow, 8 May; today it is 7 May 1520 hours my time, Aust Eastern Standard Time).
Beta 2 cannot handle date/time correctly so if you are using it (like I just did) to post a message then bear this in mind.
The problem really comes up if you try and do something like 'make cloneconfig' where you will get a WARNING stating that something-or-another is "in the future".
If you try and make the system adjust the time to some time server using the NTP option in Yast Control Centre then forget it: NTP option doesn't even 'fire up'. One way out is to use the CLI 'ntpdate -u <IP-of-timeserver>' to get the date/time set correctly.
I don't have a machine I can afford to install it on now and play with it....that's why I ran the Live CD. Fred -- MickySoft Aims to Lasso Everything With Live Mesh. What will get "lassoed" is your private data as hackers, virus and trojan writers have a field day! -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-05-07 at 15:26 +1000, Basil Chupin wrote: This is more a question for the factory list than here.
The last msg I posted here was only about 20 minutes ago but if you look at the date/time stamp of that msg it is dated 1 day and many hours in the FUTURE (ie, tomorrow, 8 May; today it is 7 May 1520 hours my time, Aust Eastern Standard Time).
Your locale seems to be set to +1000, not Aust Eastern Standard Time - your mail says so. Did you set it correctly in Yast? Can you do it now? After setting the default time locale in yast, and login in again, set up the clock if necessary using the command line "date" as root. The do the sequence: date <<-- if the time is correct (time and time zone), continue. Else, repeat setting the clock hwclock --systohc rm /etc/adjtime rcntp ntptimeset The last line requires you have configured some servers in /etc/ntp.conf If it works, now finally try "rcntp start".
Beta 2 cannot handle date/time correctly so if you are using it (like I just did) to post a message then bear this in mind.
I think it can, or more people would have noticed. I haven't tried B2 yet, but previous versions did work. Probably something happened while you were setting it up. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIIYAltTMYHG2NR9URAmh6AJ9qrS6A8+Slbb4+38jjVV0r5J71OQCeIz7k g6Bi1fAZicvr+YH9UVm7yfU= =d0YW -----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 last msg I posted here was only about 20 minutes ago but if you look at the date/time stamp of that msg it is dated 1 day and many hours in the FUTURE (ie, tomorrow, 8 May; today it is 7 May 1520 hours my time, Aust Eastern Standard Time).
Your locale seems to be set to +1000, not Aust Eastern Standard Time - your mail says so.
AEST is UTC+1000, I believe. /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-05-07 at 15:29 +0200, Per Jessen wrote:
Your locale seems to be set to +1000, not Aust Eastern Standard Time - your mail says so.
AEST is UTC+1000, I believe.
Oops! I though Aust was Australia. O:-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIIbyQtTMYHG2NR9URAo9rAJ4s5EsUP2nVldn7jOhI4K1BuRtNUgCfR02X 6lk/OJe+Nyrzw1J5sJz9ahE= =PtqD -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2008-05-07 at 15:29 +0200, Per Jessen wrote:
Your locale seems to be set to +1000, not Aust Eastern Standard Time - your mail says so.
AEST is UTC+1000, I believe.
Oops! I though Aust was Australia. O:-)
Yes, I think it is - AEST = Australian Eastern Standard Time. Carlos, you need more sleep :-) /Per Jessen, Zürich -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2008-05-07 at 16:45 +0200, Per Jessen wrote:
AEST is UTC+1000, I believe.
Oops! I though Aust was Australia. O:-)
Yes, I think it is - AEST = Australian Eastern Standard Time.
Carlos, you need more sleep :-)
That's for sure, I'm off to a siesta right now, but I'm certainly bewildered. cer@nimrodel:~> date ; TZ=UTC date ; TZ=AEST date Wed May 7 16:59:19 CEST 2008 Wed May 7 14:59:19 UTC 2008 Wed May 7 14:59:19 AEST 2008 ???? The above is wrong, dunno why. That's not AEST, can't be. But now I see what you mean: he is at +1000, not +0100. Siesta time! O:-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIIcZptTMYHG2NR9URAnSnAJ0SdM4CESf6I1Y2sXjS7E3bFbSTNQCfUEL+ GYHwrCL3AIoGZhi3uOVQWBQ= =NsaS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
If you try and make the system adjust the time to some time server using the NTP option in Yast Control Centre then forget it: NTP option doesn't even 'fire up'. One way out is to use the CLI 'ntpdate -u <IP-of-timeserver>' to get the date/time set correctly.
Ciao.
Hi, I just updated yast2-ntp and I can confirm it no longer starts and something had stopped my ntp daemon. I restarted it using the yast runlevel editor and it seems to be fine. Are you using yast2-ntp direct from the beta2 dvd/cd or have you updated since installation? Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Dave Plater wrote:
Basil Chupin wrote:
If you try and make the system adjust the time to some time server using the NTP option in Yast Control Centre then forget it: NTP option doesn't even 'fire up'. One way out is to use the CLI 'ntpdate -u <IP-of-timeserver>' to get the date/time set correctly.
Ciao.
Hi, I just updated yast2-ntp and I can confirm it no longer starts and something had stopped my ntp daemon. I restarted it using the yast runlevel editor and it seems to be fine. Are you using yast2-ntp direct from the beta2 dvd/cd or have you updated since installation? Regards Dave P No idea at this point in time - I would need to put in the other HDs with 11.0 on them to see which version of xntp is being used. But I can say that some 398 packages got upgraded (?)a couple of days ago.
Ciao. -- If you want to know what a man is like, take a look at how he treats his inferiors not his equals. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
Dave Plater wrote:
Basil Chupin wrote:
If you try and make the system adjust the time to some time server using the NTP option in Yast Control Centre then forget it: NTP option doesn't even 'fire up'. One way out is to use the CLI 'ntpdate -u <IP-of-timeserver>' to get the date/time set correctly.
Ciao.
Hi, I just updated yast2-ntp and I can confirm it no longer starts and something had stopped my ntp daemon. I restarted it using the yast runlevel editor and it seems to be fine. Are you using yast2-ntp direct from the beta2 dvd/cd or have you updated since installation? Regards Dave P No idea at this point in time - I would need to put in the other HDs with 11.0 on them to see which version of xntp is being used. But I can say that some 398 packages got upgraded (?)a couple of days ago.
Ciao.
I filed a bug about yast2-ntp-client-2.16.8-3, when I downgraded to yast2-ntp-client-2.16.7-9 it worked again so if you want to have yast ntp to work try the package from the dvd.it's Bug #387717. Regards Dave P -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Basil Chupin wrote:
Dave Plater wrote:
Basil Chupin wrote:
If you try and make the system adjust the time to some time server using the NTP option in Yast Control Centre then forget it: NTP option doesn't even 'fire up'. One way out is to use the CLI 'ntpdate -u <IP-of-timeserver>' to get the date/time set correctly.
Ciao.
Hi, I just updated yast2-ntp and I can confirm it no longer starts and something had stopped my ntp daemon. I restarted it using the yast runlevel editor and it seems to be fine. Are you using yast2-ntp direct from the beta2 dvd/cd or have you updated since installation? Regards Dave P No idea at this point in time - I would need to put in the other HDs with 11.0 on them to see which version of xntp is being used. But I can say that some 398 packages got upgraded (?)a couple of days ago.
Ciao.
I filed a bug about yast2-ntp-client-2.16.8-3, when I downgraded to yast2-ntp-client-2.16.7-9 it worked again so if you want to have yast ntp to work try the package from the dvd.it's Bug #387717. Regards Dave P Thanks for this. I found 2.16.7-6 (not -9) on the Beta1 DVD so installed
Dave Plater wrote: that and ntp now works. (Of course, the file manager now keeps wanting to upgrade this to the non-working 2.16.8-3 :-) .) Ciao. -- If you want to know what a man is like, take a look at how he treats his inferiors not his equals. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Basil Chupin
-
Carlos E. R.
-
Dave Plater
-
Fred A. Miller
-
Per Jessen