Jonathan Ruano skryf:
> 
> On Mon, Nov 22, 1999 at 06:51:46PM +0200, Dirk Laurie wrote:
> 
> > hardware clock.  I can type "hwclock --hctosys" and then it's OK.
> > So somewhere in the boot-up scripts the GMT must have got hardcoded
> > at installation time.  Any idea where?
> /etc/sysconfig/clock
> 
> UTC=no
> 
No, that one gets fixed by timeconfig.  I've got some extracts from
/var/log/messages that say where things go wrong.  Unfortunately that
doesn't tell me what to fix.

The first set comes from bootup:

Nov 23 05:33:21 collatz atd: atd startup succeeded
Nov 23 07:33:06 collatz rc.sysinit: Loading default keymap succeeded 
Nov 23 07:33:06 collatz rc.sysinit: Setting default font succeeded 
...
Nov 23 07:33:14 collatz fsck: /dev/hda6: clean, 9181/132600 files, 113856/529168
 blocks 
Nov 23 07:33:14 collatz rc.sysinit: Checking filesystems succeeded 
Nov 23 07:33:16 collatz rc.sysinit: Mounting local filesystems succeeded 
Nov 23 07:33:16 collatz rc.sysinit: Turning on user and group quotas for local f
ilesystems succeeded 
Nov 23 05:33:19 collatz date: Tue Nov 23 05:33:19 SAST 1999 
Nov 23 05:33:19 collatz rc.sysinit: Setting clock : Tue Nov 23 05:33:19 SAST 199
9 succeeded 
Nov 23 05:33:19 collatz rc.sysinit: Enabling swap space succeeded 
Nov 23 05:33:19 collatz init: Entering runlevel: 3 

So when atd starts, it gets information that time is GMT and resets system
time.  Then it stays there for a while, until rc.sysinit obviously working
off /etc/sysconfig/clock as it should, sets the clock back to the hardware 
reading.  

The next extract comes from a point when apmd made my screen go blank:

Nov 23 09:37:16 collatz PAM_pwdb[285]: (login) session opened for user dirk by (
uid=0)
Nov 23 12:47:28 collatz apmd[122]: Resume after 02:16:53 (65% unknown)
Nov 23 13:01:19 collatz sudo:     dirk : TTY=pts/0 ; PWD=/home/dirk/kantoor/navo
rs/artikels/gauss-survey ; USER=root ; COMMAND=/sbin/hwclock --hctosys 
Nov 23 11:02:26 collatz sudo:     dirk : TTY=tty1 ; PWD=/home/dirk/kantoor/navor
s/artikels/gauss-survey ; USER=root ; COMMAND=/usr/bin/less /var/log/messages 

I had been working for about an hour and then went for tea.  Coming back,
I reactivated the screen, discovered that GMT had reasserted itself, and
manually reset the system clock.

These two-hour jumps to and fro can't be good for the integrity of the
system.

IMHO the above behaviour is a bug, caused by some old code somewhere
that dates back to the days before we had /etc/sysconfig.  But where
does that code get its information?

Dirk


-- 
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.

Reply via email to