On Thu, Jan 16, 2003 at 09:34:30AM -0600, Bret Hughes wrote:
> On Thu, 2003-01-16 at 06:27, fred smith wrote:
> > On Tue, Jan 14, 2003 at 07:34:18PM -0500, fred smith wrote:
> > > I've got a 6.2 box at work (can't update yet because it's used for
> > > development and customers run the result on 6.2).
> > >
> > > today it paniced during shutdown (dunno why either) and after the
> > > massive fsck, some things are, like, broken.
> > >
> > > Like, for example, I can't log in on a text console, type in the
> > > username, hit ENTER and it flashes (so briefly it's nearly invisible)
> > > something like "invalid password" and returns to the login prompt.
> > > using ^J or ^M instead of ENTER makes no difference.
> >
> > The problem was: /etc/pam.d/login got munged. Replaced it and voila!
> Am I the only one that get nervous when files like this get changed /
> corrupted? I have not seen this on any of my boxes but this is at least
> two threads on this list tht have had this issue. What could cause this
> sort of errors?
In this case it was because of a crash and the resulting FSCK which
apparently munged a lot of files.
I ran "rpm -qa | rpm -v" and found a good-sized list of files listed
as missing. So I captured that list, fed it back into RPM to find out
which packages they were from, piped that list thru "sort | uniq"
then fed it back into RPM to reinstall them.
--
---- Fred Smith -- [EMAIL PROTECTED] -----------------------------
The Lord is like a strong tower.
Those who do what is right can run to him for safety.
--------------------------- Proverbs 18:10 (niv) -----------------------------
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]?subject=unsubscribe
https://listman.redhat.com/mailman/listinfo/redhat-list
