A bit too late now, but sometimes it's helpful to run 'strace' or 'ltrace' on the program in question. I've had a problem like that long time ago and the only thing I remember about it is that it was some kind of interaction between su and X11 authentication system and it got fixed by unsetting DISPLAY (this was inside a script). I do remember, though, that we found it by running either strace or ltrace and seeing it time out in one of the calls.
On Mon, Jan 26, 2004 at 06:37:02PM +0000, Greg Bolshaw wrote: > On Sun, 2004-01-25 at 04:42, Mike Arrison wrote: > > Run 'top' in one console while su'ing in another. See if anything major > > is taking cycles. > > Nothing at all. It just seemed to idle - no change whatsoever to CPU or > memory usage. > > I've now fixed this by re-emerging sys-libs/pam. Not sure what caused > it. > > Thanks for your suggestion. > > -- > Kind regards > > Greg Bolshaw > Consultant > Linux Technologies > http://www.linuxtechnologies.co.uk/ -- - Andrey ~ In theory, practice and theory are the same, but in practice they are different (Larry McVoy) ~ -- [EMAIL PROTECTED] mailing list
