On 8 Mar 1997, Guy Maor wrote: > Karl Ferguson <[EMAIL PROTECTED]> writes: > > > I agree. I've got login 1.45a-3 installed and the problem hasn't appeared > > - it's definately a problem in the rex-fixed/binary/base and bo/binary/base > > because if I dpkg -i *.deb in either directory the problem re-appears - if > > I then go back to original rex/binary/base it fixes it. > > As far as I know, the only other program that messes with wtmp in base > is init. So could you just try the different versions of it?
Now this IS the answer. I just downgraded one of my systems to sysvinit 2.69-1, rebooted, and the corruption seems to be gone. With sysvinig 2.70 I could produce the wtmp corruption at will just by doing "killall getty". With sysvinit 2.69 this does not cause the corruption. I'll leave it running for a day or so before i'm completely convinced but this definitely looks like it's the answer. BTW, does anyone know of a way to restart init without rebooting? Maybe there should be a 'telinit R' option to force an 'exec /sbin/init'? craig
