I’m new here, sorry if this post is in wrong place…
First of all, I readed a lot of threads about configuration about localtime or utc.
I have this problem in a Server (only one SO in the machine) with OpenSuse 12.2 (Generated by Kiwi JeOS) and the configuration was apointed to UTC.
/etc/localtime
/etc/sysconfig/clock
Please, see the sequence of command below and you can look the problem…
# sntp -s a.ntp.br
31 Jan 16:19:00 sntp[2248]: Started sntp
2013-01-31 16:19:00.085036 (+0000) +0.00025 +/- 0.002762 secs
# hwclock -s
# date ; date -u ; hwclock -r --localtime ; hwclock -r --utc
Thu Jan 31 16:19:33 UTC 2013
Thu Jan 31 16:19:33 UTC 2013
Thu Jan 31 16:19:34 2013 -0.740107 seconds
Thu Jan 31 16:19:35 2013 -1.001539 seconds
Up to here is all ok!!!
# TZ=America/Sao_Paulo
# export TZ
# date ; date -u ; hwclock -r --localtime ; hwclock -r --utc
Thu Jan 31 14:20:53 BRST 2013
Thu Jan 31 16:20:53 UTC 2013
Thu Jan 31 16:20:54 2013 -0.912976 seconds
Thu Jan 31 14:20:55 2013 -0.986086 seconds
If you tell it that RTC time is in local clock, it is displayed “as is” (no conversion). If you tell it that RTC time is in UTC, it is converted to local clock. So again - where is the problem?
dab213 wrote:
> arvidjaar;2523532 Wrote:
>> man hwclock:
>
> For sure I readed it and this help cant help me…
> Please, If you cannout help dont answer my posts. Thank you.
Well arvidjaar didn’t know you had already read it, because you didn’t
tell him. So don’t blame him for making the suggestion. And the man page
does contain the answer but you have to be prepared to understand it.
Again, you can’t blame him for your lack of effort to understand it.
hwclock -r does not affect the contents of the hardware clock. It only
reads the data from the clock. The --utc and --localtime simply tell
hwclock how to interpret the data. --utc tells it that the hardware
clock data is in UTC. hwclock then works out the difference between UTC
and the localtime so it can show you the result in localtime.
–localtime tells hwclock that the data is in localtime and it displays
it directly.
It looks like you have stored the time in your hardware clock in
localtime. It is generally regarded as better practice to store the time
in UTC on a server, and on any workstation that doesn’t dual boot with
an old version of Windows.
> arvidjaar;2523532 Wrote:
>> man hwclock:
>
> For sure I readed it and this help cant help me…
> Please, If you cannout help dont answer my posts. Thank you.
As Dave said, we have no way of knowing what you did and didn’t do before
asking a question unless you tell us.
Arvidjaar was trying to help you. If you find that it wasn’t helpful,
well, that’s the way things go. You may not tell him not to try to help
that’s not how volunteer support works.
By doing that, you leave everyone wondering “gee, if I try to help, is
this user going to get angry at me if I get it wrong?” - and that’ll lead
to fewer people being willing to even try to help you.
On 2013-01-31 18:46, Jim Henderson wrote:
> By doing that, you leave everyone wondering “gee, if I try to help, is
> this user going to get angry at me if I get it wrong?” - and that’ll lead
> to fewer people being willing to even try to help you.
Absolutely.
I was about to compare on my system, but I will not.
–
Cheers / Saludos,
Carlos E. R.
(from 12.1 x86_64 “Asparagus” at Telcontar)
arvidjaar wrote:
> djh-novell;2523551 Wrote:
>> It looks like you have stored the time in your hardware clock in
>> localtime.
>
> Actually according to the original post, it is stored in UTC.
Apologies. You’re quite right. I’m not sure how I misinterpreted it
yesterday. Sorry.
I so this post.
I made an ISO using the KIWI.
It’s a JeOS (minimal text terminal)
I beleave that I applyed this configuration directly in the configurations files.