why not strace sshd and find what it's doing? log into the machine, then run a separate sshd under an alternate port , and under 'strace -f -o <file> ....-tt -T', then see what strace shows you it is doing, and which operations are taking a long time (-tt gives a timestamp for each syscall invocation, -T gives the time a syscall invocation took to complete).
--guy Eli Billauer wrote: > Hi, > > > PAM did indeed cross my mind as a suspect. Unfortunately, I have no > /var/log/auth* logfiles. As a matter of fact, I don't have any log > messages related to authentication. In my very old Redhat 7.3, I had > pam_unix messages in /var/log/messages telling me who has changed user > ID. On Fedora 12, nothing is mentioned about becoming root in > /var/log/messages, and I can't see any directory or file in /var/log > that seems to contain that information. Maybe under the audit directory, > but the files there are not really human readable. > > > Any idea of where my authenticate mechanism keeps its logs? > > > And why a kernel upgrade would have any effect? > > > <rant>In the past, I clearly recall just upgrading my kernel and all was > fine. Where are those days?</rant> > > > Thanks, > > Eli > > > Shachar Shemesh wrote: > >>> >> If both ssh and the graphical logins are slow, I would suspect PAM. >> Try ssh public key authentication and see what happens (I think that >> one bypasses pam). Also, see what /var/log/auth* have to say. >> >> Shachar >> > > _______________________________________________ Haifux mailing list [email protected] http://hamakor.org.il/cgi-bin/mailman/listinfo/haifux
