[opensuse] Time problems after upgrade to openSUSe 10.2
After upgrade to 10.2, I cannot seem to get the time settings right in Evolution, the clock applet and system time. I cannot find a bug, so I am assuming it is something I have done. FYI I am in US Eastern time, same as New York. I have my system clock set with ntpdate in cron (this is a laptop that spends a lot of time off net). This has been set up this way for a long time and has worked smoothly. Right now, it is actually 1:36 pm local time. the system clock is
date Wed Dec 20 18:36:43 UTC 2006
The clock applet shows 6:36 pm starting YAST and looking at the time admin panel, I see that the region is set to USA, the Time Zone is set to Eastern, Hardware clock is set to "UTC" and actual time and date is set to 13:36. I save (without changing anything) and now the applet correctly reads 1:36 (well, 1:41 now). All is well until --- -- ntpdate runs and the clock applet rolls back to 6:56 pm (I am a slow writer, ignore the minutes) In the meantime, Evolution seems to be time stamping emails in UTC but the Evolution calendars "current time" indicator (that red line that is supposed to tell when you are NOW is showing 8:45 am if the clock applet is right and the right time if the clock applet is 6+pm. FYI, Evolution "calender and task" timezone is set to America/New York. I am confused. I know I am going to be embarrassed by the answer, but can someone help??? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 20 December 2006 12:55, Jim McKean wrote:
starting YAST and looking at the time admin panel, I see that the region is set to USA, the Time Zone is set to Eastern, Hardware clock is set to "UTC" and actual time and date is set to 13:36.
Easiest from my perspective would be to change the hardware clock in YaST to localtime instead of UTC. That has kept my time settings correct and agreeing with each in all the apps I use since SUSE 7.3 through openSUSE 10.2. YMMV, Stan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2006-12-20 at 13:22 -0600, S Glasoe wrote:
On Wednesday 20 December 2006 12:55, Jim McKean wrote:
starting YAST and looking at the time admin panel, I see that the region is set to USA, the Time Zone is set to Eastern, Hardware clock is set to "UTC" and actual time and date is set to 13:36.
Easiest from my perspective would be to change the hardware clock in YaST to localtime instead of UTC. That has kept my time settings correct and agreeing with each in all the apps I use since SUSE 7.3 through openSUSE 10.2.
I think this is the embarrassing part. Changing to local time fixes things briefly, but when ntpdate runs again, it updates the internal clock to UTC, not local. So then the Gnome clock applet is off again. Evolution message stamps are off, but Evolutions calendar time indicator line is OK. How do I tell ntpdate to update to LOCAL time, not UTC? I used to have a link from /etc/localtime to some timezone file somewhere. The system set that up, so I am a little vague on the details. The upgrade removed that link -- I assume there is some other timezone mechanism that I just don't understand. If I could fix that, it would fix all but the Evo calendar time indicator, and that's just an annoyance. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-12-21 at 13:45 -0000, Jim McKean wrote:
How do I tell ntpdate to update to LOCAL time, not UTC?
You can not. ntpdate uses UTC time, and any linux system also uses UTC internally (this is not entirely correct, but it doesn't matter for us now). Only when displaying the time programs in Linux do the conversion from the internal time to the local time.
I used to have a link from /etc/localtime to some timezone file somewhere. The system set that up, so I am a little vague on the details. The upgrade removed that link -- I assume there is some other timezone mechanism that I just don't understand.
I don't think so. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFiqYftTMYHG2NR9URAjX9AJ4qHqBfKDDwZuBuFnXg7t9O/pu74wCfc9S8 TOV1+PXeNp3PcZDv9QYBiZU= =n1ts -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2006-12-21 at 16:19 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2006-12-21 at 13:45 -0000, Jim McKean wrote:
How do I tell ntpdate to update to LOCAL time, not UTC?
You can not.
ntpdate uses UTC time, and any linux system also uses UTC internally (this is not entirely correct, but it doesn't matter for us now). Only when displaying the time programs in Linux do the conversion from the internal time to the local time.
thanks, that save me a lot of time (no pun intended)
I used to have a link from /etc/localtime to some timezone file somewhere. The system set that up, so I am a little vague on the details. The upgrade removed that link -- I assume there is some other timezone mechanism that I just don't understand.
I don't think so.
Yeah, I think this is what is broke. I am trying to figure out how to fix.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFiqYftTMYHG2NR9URAjX9AJ4qHqBfKDDwZuBuFnXg7t9O/pu74wCfc9S8 TOV1+PXeNp3PcZDv9QYBiZU= =n1ts -----END PGP SIGNATURE-----
-- Jim McKean Director of Information Services Pratt Corporation Smart Retail Graphics (R) Indianapolis - Chicago - Los Angeles W: 317-524-3334 jmckean@prattcorp.com www.prattcorp.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 2006-12-20 12:55, Jim McKean wrote:
Right now, it is actually 1:36 pm local time.
the system clock is
date
Wed Dec 20 18:36:43 UTC 2006
The clock applet shows 6:36 pm
Which desktop? If KDE, right click on the clock, then left on "show timezone" and make sure local time is selected. Given what follows, I think it probably is, but just make sure. If Gnome, I can't help you with this selection, but I can't imagine it would be much different.
starting YAST and looking at the time admin panel, I see that the region is set to USA, the Time Zone is set to Eastern, Hardware clock is set to "UTC" and actual time and date is set to 13:36.
I save (without changing anything) and now the applet correctly reads 1:36 (well, 1:41 now). All is well until ---
-- ntpdate runs and the clock applet rolls back to 6:56 pm (I am a slow writer, ignore the minutes)
In the Yast sysconfig editor, verify directly that system/environment/clock/HWCLOCK is set to -u. If not, change it, click "finish" and exit Yast, which should correct the problem. -- The best way to accelerate a computer running Windows is at 9.81 m/s² -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2006-12-20 at 14:20 -0600, Darryl Gregorash wrote:
On 2006-12-20 12:55, Jim McKean wrote:
Which desktop? If KDE, right click on the clock, then left on "show
Sorry. Gnome.
If Gnome, I can't help you with this selection, but I can't imagine it would be much different.
Its not, but it does not solve the problem. If I leave the internal clock set to UTC, the Evo message times and the Clock applet are off, but the Evo calendar time indicator is OK. If I change internal to local, Evo messages nad the clock are OK, butthe Evo calendar time indeicator are off -- and ntpdate changtees everything back to UTC when it runs -- 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 2006-12-20 at 18:55 -0000, Jim McKean wrote:
FYI I am in US Eastern time, same as New York.
I have my system clock set with ntpdate in cron (this is a laptop that spends a lot of time off net). This has been set up this way for a long time and has worked smoothly.
Right now, it is actually 1:36 pm local time.
the system clock is
date Wed Dec 20 18:36:43 UTC 2006
That means that the locale setting for that user (or system wide) is UTC. The system setting would be stored in "/etc/localtime", a binary file copied by Yast from somewhere else (doesn't matter). It may be wrong/bad. The user setting would be the variable TZ: cer@nimrodel:~> date ; TZ=EST date ; TZ=UTC date Wed Dec 20 21:52:20 CET 2006 Wed Dec 20 15:52:20 EST 2006 Wed Dec 20 20:52:20 UTC 2006
The clock applet shows 6:36 pm
Matches.
starting YAST and looking at the time admin panel, I see that the region is set to USA, the Time Zone is set to Eastern, Hardware clock is set to "UTC" and actual time and date is set to 13:36.
13:36 local time, I assume.
I save (without changing anything) and now the applet correctly reads 1:36 (well, 1:41 now). All is well until ---
-- ntpdate runs and the clock applet rolls back to 6:56 pm (I am a slow writer, ignore the minutes)
I guess it does that because your clock shows local time but says it is UTC time. Check settings in "/etc/sysconfig/clock". Or do the procedure in Yast you did, but do change something, then enter again and change back. Having the HW clock in UTC is the recommended thing in linux, unless you double boot to windows, by the way. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFiaKntTMYHG2NR9URAmc3AJ4hULTPelBUDRmeyfV5snDH4oIPwgCeMI3d tn2ugYYBPmTjaNNYhFeZ+SQ= =qZMS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2006-12-20 at 21:52 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Wednesday 2006-12-20 at 18:55 -0000, Jim McKean wrote:
FYI I am in US Eastern time, same as New York.
I have my system clock set with ntpdate in cron (this is a laptop that spends a lot of time off net). This has been set up this way for a long time and has worked smoothly.
Right now, it is actually 1:36 pm local time.
the system clock is
date Wed Dec 20 18:36:43 UTC 2006
That means that the locale setting for that user (or system wide) is UTC. The system setting would be stored in "/etc/localtime", a binary file copied by Yast from somewhere else (doesn't matter). It may be wrong/bad.
The user setting would be the variable TZ:
cer@nimrodel:~> date ; TZ=EST date ; TZ=UTC date Wed Dec 20 21:52:20 CET 2006 Wed Dec 20 15:52:20 EST 2006 Wed Dec 20 20:52:20 UTC 2006
The clock applet shows 6:36 pm
Matches.
starting YAST and looking at the time admin panel, I see that the region is set to USA, the Time Zone is set to Eastern, Hardware clock is set to "UTC" and actual time and date is set to 13:36.
13:36 local time, I assume.
I save (without changing anything) and now the applet correctly reads 1:36 (well, 1:41 now). All is well until ---
-- ntpdate runs and the clock applet rolls back to 6:56 pm (I am a slow writer, ignore the minutes)
I guess it does that because your clock shows local time but says it is UTC time.
Check settings in "/etc/sysconfig/clock".
Or do the procedure in Yast you did, but do change something, then enter again and change back.
Having the HW clock in UTC is the recommended thing in linux, unless you double boot to windows, by the way.
If someone could correct me here I would appreciate it. If the clock is set to UTC does that mean the time needs to be set to the actual UTC time which for USA/Eastern would be +5 hours? As the OP seems to be off by 5 hours doesn't this explain why? -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998 -- 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 2006-12-20 at 18:59 -0500, Kenneth Schneider wrote:
If someone could correct me here I would appreciate it. If the clock is set to UTC does that mean the time needs to be set to the actual UTC time which for USA/Eastern would be +5 hours? As the OP seems to be off by 5 hours doesn't this explain why?
If the command "date" shows UTC time, then the time has to be set also using UTC. But that command allows displaying and setting the time in any standard. If, as for the OP, it shows UTC and you set it to local time, as is, the display will seem correct at first glance, ie the "number" will be correct, but the computer says it is still UTC. I mean, if it 18:00 local, and it displays: "18:00 UTC", the time is incorrect, even being the number correct. Thus, when ntpdate runs it displays "wrong" - being in fact correct, but with the wrong timezone. Ie, the OP problem is only the TZ. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFidwZtTMYHG2NR9URAgfPAJ9KyMiMtC/rFEFy5aznLP247TZQJgCbB0b3 6ZueorncNMtXxN34mgWpiQ0= =IQDg -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
That means that the locale setting for that user (or system wide) is UTC. The system setting would be stored in "/etc/localtime", a binary file copied by Yast from somewhere else (doesn't matter). It may be wrong/bad.
Ah ha! /etc/localtime was a symbolic link before upgrade. The upgrade removed that link but did not replace it. I assumed (incorrectly, it seems) that that mechanism had been replaced.
The user setting would be the variable TZ:
The TZ variable is empty
cer@nimrodel:~> date ; TZ=EST date ; TZ=UTC date Wed Dec 20 21:52:20 CET 2006 Wed Dec 20 15:52:20 EST 2006 Wed Dec 20 20:52:20 UTC 2006
I am not following this. Are these commands I need to execute?
I guess it does that because your clock shows local time but says it is UTC time.
Yeah, I think. Right now, I have YAST set the clock to local time, but ntpdate screws that up when it runs.
Check settings in "/etc/sysconfig/clock".
# cat clock ## Path: System/Environment/Clock ## Description: Information about your timezone and time ## Type: string ## ServiceRestart: boot.clock # # Set to "-u" if your system clock is set to UTC, and to "--localtime" # if your clock runs that way. # HWCLOCK="--localtime" ## Type: string(Europe/Berlin,Europe/London,Europe/Paris) ## ServiceRestart: boot.clock # # Timezone (e.g. CET) # (this will set /usr/lib/zoneinfo/localtime) # TIMEZONE="US/Eastern" DEFAULT_TIMEZONE="US/Eastern" ## Description: Write back system time to the hardware clock ## Type: yesno ## Default: yes # # Is set to "yes" write back the system time to the hardware # clock at reboot or shutdown. Usefull if hardware clock is # much more inaccurate than system clock. Set to "no" if # system time does it wrong due e.g. missed timer interrupts. # If set to "no" the hardware clock adjust feature is also # skipped because it is rather useless without writing back # the system time to the hardware clock. # SYSTOHC="yes"
Or do the procedure in Yast you did, but do change something, then enter again and change back.
Having the HW clock in UTC is the recommended thing in linux, unless you double boot to windows, by the way.
I do but not often enough to bother. I do run win4lin pro. I have not checked to see what it is doing.
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFiaKntTMYHG2NR9URAmc3AJ4hULTPelBUDRmeyfV5snDH4oIPwgCeMI3d tn2ugYYBPmTjaNNYhFeZ+SQ= =qZMS -----END PGP SIGNATURE-----
-- Jim McKean Director of Information Services Pratt Corporation Smart Retail Graphics (R) Indianapolis - Chicago - Los Angeles W: 317-524-3334 jmckean@prattcorp.com www.prattcorp.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-12-21 at 14:00 -0000, Jim McKean wrote:
The system setting would be stored in "/etc/localtime", a binary file copied by Yast from somewhere else (doesn't matter). It may be wrong/bad.
Ah ha! /etc/localtime was a symbolic link before upgrade. The upgrade removed that link but did not replace it. I assumed (incorrectly, it seems) that that mechanism had been replaced.
Ah? I do not know and I can't check at this moment. I'd be surprised if the method has changed, though. Hold, yes, I can. The timezone-2.5-25.i586.rpm on the install dvd contains a 56 bytes locatime file, set for UTC. I believe you should have that file.
The user setting would be the variable TZ:
The TZ variable is empty
That's correct.
cer@nimrodel:~> date ; TZ=EST date ; TZ=UTC date Wed Dec 20 21:52:20 CET 2006 Wed Dec 20 15:52:20 EST 2006 Wed Dec 20 20:52:20 UTC 2006
I am not following this. Are these commands I need to execute?
It's what I got executing "date ; TZ=EST date ; TZ=UTC date", which is three commands in a single line. Notice that that two of them set the TZ variable for the following command only, so that its behavior is different. Run "tzselect", it will show you the correct TZ setting for you - but don't set it. Just run Yast, change the timezone to something (any place), then change it back to your setting. See if the "/etc/localtime" exists now.
I guess it does that because your clock shows local time but says it is UTC time.
Yeah, I think. Right now, I have YAST set the clock to local time, but ntpdate screws that up when it runs.
Actually, ntpdate is doing it correctly - it is the timezone for your system that is incorrect.
# Set to "-u" if your system clock is set to UTC, and to "--localtime" # if your clock runs that way. # HWCLOCK="--localtime"
TIMEZONE="US/Eastern" DEFAULT_TIMEZONE="US/Eastern"
But if /etc/localtime is missing... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFiqUTtTMYHG2NR9URAtWPAJ9wpj6XrISLc9OcyKyDqWLK6N+0eQCfTrj0 aEW7OFFsc6Tlp0lVOF4w8jg= =xt12 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2006-12-21 at 16:15 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2006-12-21 at 14:00 -0000, Jim McKean wrote:
The system setting would be stored in "/etc/localtime", a binary file copied by Yast from somewhere else (doesn't matter). It may be wrong/bad.
Ah ha! /etc/localtime was a symbolic link before upgrade. The upgrade removed that link but did not replace it. I assumed (incorrectly, it seems) that that mechanism had been replaced.
Ah? I do not know and I can't check at this moment. I'd be surprised if the method has changed, though.
Hold, yes, I can. The timezone-2.5-25.i586.rpm on the install dvd contains a 56 bytes locatime file, set for UTC. I believe you should have that file.
The user setting would be the variable TZ:
The TZ variable is empty
That's correct.
cer@nimrodel:~> date ; TZ=EST date ; TZ=UTC date Wed Dec 20 21:52:20 CET 2006 Wed Dec 20 15:52:20 EST 2006 Wed Dec 20 20:52:20 UTC 2006
I am not following this. Are these commands I need to execute?
It's what I got executing "date ; TZ=EST date ; TZ=UTC date", which is three commands in a single line. Notice that that two of them set the TZ variable for the following command only, so that its behavior is different.
ah
Run "tzselect", it will show you the correct TZ setting for you - but don't set it. Just run Yast, change the timezone to something (any place), then change it back to your setting. See if the "/etc/localtime" exists now.
I have a man file for tzselect, but no executable. Looks like a upgrade SNAFU. OK, timezone-2.5-25.i586.rpm was not installed. I have installed it and now have tzselect. OK! That did it -- everything seems to be back in coordination again. Thanks!
I guess it does that because your clock shows local time but says it is UTC time.
Yeah, I think. Right now, I have YAST set the clock to local time, but ntpdate screws that up when it runs.
Actually, ntpdate is doing it correctly - it is the timezone for your system that is incorrect.
# Set to "-u" if your system clock is set to UTC, and to "--localtime" # if your clock runs that way. # HWCLOCK="--localtime"
TIMEZONE="US/Eastern" DEFAULT_TIMEZONE="US/Eastern"
But if /etc/localtime is missing...
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFiqUTtTMYHG2NR9URAtWPAJ9wpj6XrISLc9OcyKyDqWLK6N+0eQCfTrj0 aEW7OFFsc6Tlp0lVOF4w8jg= =xt12 -----END PGP SIGNATURE-----
-- Jim McKean Director of Information Services Pratt Corporation Smart Retail Graphics (R) Indianapolis - Chicago - Los Angeles W: 317-524-3334 jmckean@prattcorp.com www.prattcorp.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2006-12-21 at 11:00 -0500, Jim McKean wrote: ...
I have a man file for tzselect, but no executable. Looks like a upgrade SNAFU.
OK, timezone-2.5-25.i586.rpm was not installed.
Curious.
I have installed it and now have tzselect.
OK! That did it -- everything seems to be back in coordination again.
Thanks!
Welcome! - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFivKTtTMYHG2NR9URAsW2AJwJ33TbdipvVtUzt1+PYLHYwNFeGgCfTnBm k/XIElGAxbwYG1JoEJHw/jM= =ZcMm -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2006-12-21 at 16:15 +0100, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
The Thursday 2006-12-21 at 14:00 -0000, Jim McKean wrote:
The system setting would be stored in "/etc/localtime", a binary file copied by Yast from somewhere else (doesn't matter). It may be wrong/bad.
Ah ha! /etc/localtime was a symbolic link before upgrade. The upgrade removed that link but did not replace it. I assumed (incorrectly, it seems) that that mechanism had been replaced.
Ah? I do not know and I can't check at this moment. I'd be surprised if the method has changed, though.
Hold, yes, I can. The timezone-2.5-25.i586.rpm on the install dvd contains a 56 bytes locatime file, set for UTC. I believe you should have that file.
The user setting would be the variable TZ:
The TZ variable is empty
That's correct.
cer@nimrodel:~> date ; TZ=EST date ; TZ=UTC date Wed Dec 20 21:52:20 CET 2006 Wed Dec 20 15:52:20 EST 2006 Wed Dec 20 20:52:20 UTC 2006
I am not following this. Are these commands I need to execute?
It's what I got executing "date ; TZ=EST date ; TZ=UTC date", which is three commands in a single line. Notice that that two of them set the TZ variable for the following command only, so that its behavior is different.
ah
Run "tzselect", it will show you the correct TZ setting for you - but don't set it. Just run Yast, change the timezone to something (any place), then change it back to your setting. See if the "/etc/localtime" exists now.
I have a man file for tzselect, but no executable. Looks like a upgrade SNAFU. OK, timezone-2.5-25.i586.rpm was not installed. I have installed it and now have tzselect. OK! That did it -- everything seems to be back in coordination again. Thanks!
I guess it does that because your clock shows local time but says it is UTC time.
Yeah, I think. Right now, I have YAST set the clock to local time, but ntpdate screws that up when it runs.
Actually, ntpdate is doing it correctly - it is the timezone for your system that is incorrect.
# Set to "-u" if your system clock is set to UTC, and to "--localtime" # if your clock runs that way. # HWCLOCK="--localtime"
TIMEZONE="US/Eastern" DEFAULT_TIMEZONE="US/Eastern"
But if /etc/localtime is missing...
- -- Cheers, Carlos E. R.
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76
iD8DBQFFiqUTtTMYHG2NR9URAtWPAJ9wpj6XrISLc9OcyKyDqWLK6N+0eQCfTrj0 aEW7OFFsc6Tlp0lVOF4w8jg= =xt12 -----END PGP SIGNATURE-----
-- Jim McKean Director of Information Services Pratt Corporation Smart Retail Graphics (R) Indianapolis - Chicago - Los Angeles W: 317-524-3334 jmckean@prattcorp.com www.prattcorp.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Carlos E. R. -
Darryl Gregorash -
Jim McKean -
Kenneth Schneider -
S Glasoe