[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: SOLVED: Erk! Something is *really* wrong here!



In article <[🔎] 3.0.1.32.19970303182911.006c1b68@tower.net.au>,
Karl Ferguson <karl@tower.net.au> wrote:
>>> For some reason now I'm getting bad logging to the wtmp file.  When a
>>> client logs in it puts them in there, and then when another logs in it
>>> wipes the first one out and puts the new one in there.
>>> 
>>> It says rubbish like this:
>>> 
>>> 
>>> P		******y**3	Wed Feb 26 18:50 - 18:54  (00:04)
>
>Well, here's some extra news...  I recently rebooted again after upgrading
>the libc's to 5.4.23 from 5.4.20 and the problem happened again (with the
>28 kernel).  I decided to recompile the kernel with the new libc's etc,
>installed it, rebooted, and now the problem has gone way again - I dare not
>reboot :-)

I think your wtmp file is corrupt. The standard cron.monthly script
rotates it every month - so then you start out with a clean one and
the problem is gone.

Just copy your wtmp file to wtmp.old or so, and truncate (not delete) the
original one using ": > /var/log/wtmp" when this happens again.

Mike.


Reply to: