Re: Solved: Erk! Something is *really* wrong here!
At 04:31 PM 3/2/97 +1100, Herbert Xu wrote:
>I'm a bit late in the discussion but this is very unlikely to be the
>kernel for the kernel has absolutely nothing to do with wtmp or utmp.
>They are managed by programs like init, telnetd, rlogind, etc. BTW, I'm
>running 2.0.29 on one of machines and I haven't seen anything like it.
Well, I'm completely unsure what it could be and I really don't have a way
of finding out since I've reinstalled the stable distribution.
Basically, the problem has appeared on two seperate machines compiled on
that machine. If I compil;e 2.0.28 on each machine the problem goes away.
If I re-compile 2.0.29 on either machine the problem re-appears.
I realise that the kernel really has nothing to do with utmp/wtmp logging,
but if this is the only change on both systems and I can make it happen by
booting 2.0.29 100% of the time, what else could it possibly be?
Baffling. I'm pretty sure I saw a message in one of the lists about a
month ago with a sort of the same problem of corruption - However, I can't
find it anywhere - can anyone tell me how that came about and what was the
result?
Regards
--
___________________________________________________________________
Karl Ferguson,
Tower Networking Pty Ltd karl@tower.net.au
t/a STAR Online Services karl@debian.org
Tel: +61-9-455-3446 Fax: +61-9-455-2776 http://www.star.net.au
___________________________________________________________________
Reply to: