On Mon, 2003-02-03 at 02:31, Stephen Kuhn wrote: > On Mon, 2003-02-03 at 21:07, Michael Schwendt wrote: > > > Why? Surely you can reboot the machine and get past the passwd > > check. > > > Tried that, no go. Did the exact same thing - and I reckon it has > something to do with using "KUSER" - I used KUSER before the first hose > up; second installation, did the same right after the 45 minutes to > install everything I needed; used "KUSER" then it all went south. > Rebooted and all the passwords for all the accounts I created don't > work. So, it has to be file system corruption - something - something > has to have hosed up the /etc/passwd beyond usage. > > > It's too late to analyze the problem when all evidence has been > > removed. > > > > Twice in the same day, and the physical drive passes all tests. Going to > blow it out and try it with RH 7.3 instead. Getting close to a deadline > for me so I'm in a rush to get some things done and this is really > freaking me out. <ridiculously long signature chopped>
I would have to say you jumped the gun. Linux != Windows (problems almost never require a re-install). Why did you bother posting? a. You don't say what you're installing b. You already took action. c. You can recover password w/o this much trouble. I took a look at Kuser, all it did was set passwords to: '!!' in shadow, effectively disabling login for every user that it touched. I don't know if that was the desired effect, but it certainly would make login's fail. My advice would be use RedHat 8, but don't user KUser. One previous poster mentioned using 'init=/bin/sh' on your boot line, you also might try booting off the RedHat disk 1, going to rescue, and after your root filesystem is mounted, switch to console 2 [alt+f2], then type: chroot /mnt/sysimage then passwd root enter new password: re-enter new password: OK, all done. type 'exit' then go back to console 1 [alt + f1], and you are done. I don't remember the steps, but you practically could just do a: 'sync;sync' on console 2, then hit reset. On another note, your second message indicates that you tracked it down to kuser. Here is another Idea. If you were troubleshooting, and didn't know what to do, maybe you should have backed up /etc/passwd, and /etc/shadow, then run kuser, or whatever else, and then diff the files after it breaks: [that is what I did.] diff -u /etc/shadow.prek /etc/shadow 40c40 > shylok:*K*:12043:0:32767:7::: --- < shylok:!!:12043:0:99999:7::: 43c43 < foo.bar:!!:12060:0:99999:7::: --- > foo.bar:!!:12060:0:32767:7::: FYI: that is the actual output, it shows me that is removed the *K* [indicating Kerberos authentication] and replaced it with '!!' indicating login disabled. I sent a message to the maintainer of kuser, but I bet he has already fixed this bug, or he will say: 'Redhat broke it'. good luck, and patience. js p.s. get a shorter .sig =) -- VB programmers ask why no one takes them seriously, it's somewhat akin to a McDonalds manager asking employees why they don't take their 'career' seriously.
signature.asc
Description: This is a digitally signed message part
