Mailinglist Archive: opensuse-factory (845 mails)

[Felix Miata <mrmazda@xxxxxx>]

1
/etc/adjtime from my 10.2 server:
0.000101 1204753900 0.000000
1204753900
LOCAL

/etc/adjtime from the Factory box I was using today:
0.000234 1210343800 0.000000
1210343800
LOCAL

Both are multiboot systems with the hardware clock set to local (GMT-0400)
time. Why are they different?

2
I've searched Bugzilla, and don't seem to have found anything open on point,
unless https://bugzilla.novell.com/show_bug.cgi?id=384254 is it, in which
case it needs a much better summary. (No manual entry for nscd).

I have NTP (and NSCD) set to start only in runlevels 3 & 5, since in 1 & 2
there is no network. /etc/sysconfig/clock contains HWCLOCK="--localtime",
SYSTOHC="yes", TIMEZONE="America/New_York", DEFAULT_TIMEZONE="US/Eastern".

When I boot to runlevel 2, the system time has the time zone offset doubled.
When GMT is noon, and localtime is 08:00, the system time booted to Factory
is 04:00, even though hwclock and hwclock --localtime both correctly show
08:00. Only after upping runlevel to 3 or 5, which starts NTP, is the system
time correct. Surely I'm not the only one seeing this. System was last
updated around 00:00 local on 09 May. Anyone know which Bugzilla bug this is,
and how one would tell?

I'm thinking 384254 could be it, because
https://bugzilla.novell.com/show_bug.cgi?id=385296#c5 was duped to it, and
following the instruction there seems to have eliminated the problem of wrong
clock unless NTP  is running. But, 384254 is about as clear as mud regarding
what it is actually about.
-- 
". . . . in everything, do to others what you would
have them do to you . . . ."       Matthew 7:12 NIV

 Team OS/2 ** Reg. Linux User #211409

Felix Miata  ***  http://fm.no-ip.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx