That looks like your BIOS clock is set to local time.
You stated ‘hwclock --show’ show me correct time’.
That means that your BIOS clock is set to local time, so you OS clock will give you the timestamp data shifted the amount of time corresponding to our local time. It is no surprise you see time in the future.
If that´s the case, and your system is not hosting any other OS (specially if the other is Windows), you should set BIOS clock to UTC.
Then, from the Open Suse system, selecting your local time zone will adjust UTC to you local time automatically.
That used to be a problem on machines that were shipped with Windows installed. That machines had BIOS time settings set to localtime.
So. I have not understood as to resolve this problem? I have updated insserv from repo, nscd for me actual, boot.clock during booting is started and time remains correct, but then it shift +3. (TIMEZONE=“Europe/Kiev”, summer time). I cannot understand what script changes time.
New question.
Why in loadtime of system the script boot.clock produces:
Antosh. Clock is out off script boot.clock [date]: Wed Sep 3 10:43:58 UTC 2008
Antosh. Clock is out off script boot.clock [date-u]: Wed Sep 3 10:43:58 UTC 2008
and if it to start right after loadings that:
#./boot.clock restart
Setting up the hardware clock done
Antosh. Clock is out off script boot.clock [date]: Wed Sep 3 10:47:20 EEST 2008
Antosh. Clock is out off script boot.clock [date-u]: Wed Sep 3 **07:47:20 UTC **2008
Here my data:
/etc/adjtime
-1.843383 1220426307 0.000000
1220426307
LOCAL
For a new question please use a new thread so things don’t get (more)
confusing unnecessarily.
When you get booted up does date show the correct date and time?
Many/Most systems use UTC for their host time (like mine all do) but
then apply an offset for everything you need to see. Is this what you
are seeing or are you actually seeing UTC 24x7 like in the date
command output?
Good luck.
iiantosh wrote:
> New question.
> Why in loadtime of system the script boot.clock produces:
> Antosh. Clock is out off script boot.clock [date]: Wed Sep 3 10:43:58
> UTC 2008
> Antosh. Clock is out off script boot.clock [date-u]: Wed Sep 3
> 10:43:58 UTC 2008
> and if it to start right after loadings that:
> #./boot.clock restart
> Setting up the hardware clock done
> Antosh. Clock is out off script boot.clock [date]: Wed Sep 3 10:47:20
> EEST 2008
> Antosh. Clock is out off script boot.clock [date-u]: Wed Sep 3
> *07:47:20 UTC *2008
>
> Here my data:
> /etc/adjtime
> -1.843383 1220426307 0.000000
> 1220426307
> LOCAL
>
> /etc/sysconfig/clock
> HWCLOCK="–localtime"
> SYSTOHC=“no”
> TIMEZONE=“Europe/Kiev”
> DEFAULT_TIMEZONE=“Europe/Moscow”
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
For a new question please use a new thread so things don’t get (more)
confusing unnecessarily.
It’s not new question. It is a new detail in the given problem.
When you get booted up does date show the correct date and time?
I will show you results of operation of a script boot.clock in loadtime openSuSe 10.3:
Antosh. Clock is out off script boot.clock [date]: Wed Sep 3 23:46:33 EEST 2008
Antosh. Clock is out off script boot.clock [date -u]: Wed Sep 3 20:46:33 UTC 2008
Here it is correct. And in 10,3 the time shows correctly.
Many/Most systems use UTC for their host time (like mine all do) but
then apply an offset for everything you need to see.
Systems can use different time but if I specify to system that HW-time is a local time the system should understand and calculate correctly UTC-time and if HW-time is UTC-time, correctly to calculate local time. As does successfully SuSe 10.3. SuSe 11 it do not do. It would be desirable to know, why?
I was having the same problem with my install of Suse 11.0_64. I went to Yast and selected System and the Date and Time. I set the date and time using a selected NTP and then configured it to run at boot time. That seemed to work just fine. I have rebooted 10 times and it has had the right clock time every time now. Hope this works for you
I’m too starting to think this is related to KDE4.
For a long period, my system clock stay accurate (without any NTP sync.). Last time (4 days ago) it went wrong, I was returning from a KDE4.0 session as root (my main desktop is Gnome2).
I tried to reproduce the problem:
logout
login as root (KDE4)
browse some directories with Dolphin
logout
and login back to Gnome desktop as user
But there was no problem with the system clock.
(I suspect that this jump-in-time only happen once per day.)
My system clock is still accurate since, but I haven’t started KDE4 in the meantime.
First of all, hello to everybody.
I’m a new openSuSE user, but not new at linux, at least as an hobbyst.
I was very interested in the “1-click-installation” feature and so I installed openSuSE 11.0 from the live CD. Then I was really annoyed by this same bug: at each reboot, my system time was delayed by two more hours (4 hours after 2 reboots, 6 hours after 3 reboots …).
My hardware clock is set to local time, since once in a while I have to use WindowsXP … My local time is CEST, so it is GMT+2.
With a working ntp server the system time goes good, but sometimes my ADSL connection is quite slow to start up and so it takes several minutes before the ntp server can connect and synchronize.
I tried some search in the bugzilla and in the forums and I found out other people with this problem but no complete fix (https://bugzilla.novell.com/show_bug.cgi?id=426270).
After some tries I found out that probably the problem is due to the fact that /sbin/hwclock, as called by the boot.clock script, needs access to data stored in the /usr/share/zoneinfo directory. Note that my /usr directory is stored in a different partition and that partiton is not mounted till after the boot.localfs script is called and has completed its procedure. Without parallel booting it is sufficient to call boot.clock just after boot.localfs, but with parallel booting boot.clock is still called before the /usr partition is mounted. As I like parallel booting, as a temporary fix I copied /usr/share/zoneinfo in the / directory.
BTW, I see in the boot.clock script the line “#X-Start-Before: boot.localfs”, so it seems that boot.clock must be called after boot.localfs: can somebody explain why ? And fix the problem that we have found?
P.S. I promise to be less verbose next time, but I’ve been involved for so much time with this bug …
Yes, I’m using KDE 4.1.1, but I don’t think the bug is related to the DE, since the problem happens even when starting with the runlevel set at 3 and working in a console, at least on my system … I
Well, maybe we are referring to 2 different bugs. The one discussed about in the opening message of this thread looks like mine, not KDE related. Your bug seems related to KDE. Anyway, what about your /usr directory? Is it mounted on the same partition as the root directory or not, like mine ?
I have this same problem. Everytime my opensuse 11.0 boots my clock goes back 2 hours.
My BIOS clock is set localtime (since I also use windows). What I dont understand is that all my files are saying the clock is local, but its still applying this 2 hour offset at every boot. I also checked to see if it happened on shutdown but its not. After I turn it off, the BIOS clock is correct, only when opensuse is started the clock is changed.
My /etc/sysconfig/clock file:
## 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"
## 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="no"
## Type: string(Europe/Berlin,Europe/London,Europe/Paris)
## ServiceRestart: boot.clock
#
# Timezone (e.g. CET)
# (this will set /usr/lib/zoneinfo/localtime)
#
TIMEZONE="America/Sao_Paulo"
DEFAULT_TIMEZONE="US/Eastern"
As you can see, the HWCLOCK variable is set to localtime. I still dont understand why suse is doing this clock update. My /etc/adjtime doesnt exist and hwclock fails with the message:
Cannot access the Hardware Clock via any known method.
Use the --debug option to see the details of our search for an access method.
Hi
Can you boot into windows and see if a time server is active, if it is
can you setup ntp on openSUSE. There was a user awhile back who had the
same sort of issue. I don’t know, maybe it writes something to the
BIOS…
–
Cheers Malcolm °¿° (Linux Counter #276890)
openSUSE 11.0 x86 Kernel 2.6.25.18-0.2-default
up 1 day 13:50, 1 user, load average: 0.27, 0.37, 0.35
GPU GeForce 6600 TE/6200 TE - Driver Version: 177.80
I also thought so, but then I realized the problem happens even if I dont boot windows between suse boots. It only adjusts the clock on suse boot, not even at shutdown.
Matheus, have you tried setting SYSTOHC to yes?
also, what is the difference between hwclock, date & date -u ?
There you go…
matheusnbasus:~ # hwclock
Fri Nov 7 12:43:52 2008 -0.238649 seconds
matheusnbasus:~ # date
Fri Nov 7 12:43:54 BRST 2008
matheusnbasus:~ # date -u
Fri Nov 7 14:44:22 UTC 2008
