On Tue, 25 Oct 2005, Kunael wrote: > > Could you please point out a way how to reproduce this problem? I don't > > think this is a "bug" in OpenSSH, but rather a hardware or kernel > > problem... ;) > > Yes Christoph you've all the reason... the post title isn't the best. > > The only way to reproduce (the only way I know at present moment) the crash > is > simply use a ssh connection. The ssh-client machine simply lose connection, > but not appear anymore problem and the ssh-server (the machine which runs > under SuSE 10) appears completly freeze. > > Only mechanical reset is able :( > > I've watched in /var dir and I've not found anything interesting. > > ¿Where do I watch to get more info?
First, verify that the software that is installed is not corrupt. Do this in a shell, as root (use "su -" not "su" if you don't login as root): ( rpm -Va 2>&1 ) | tee rpmVa or rpm -Va > rpmVa 2>&1 and then examine the file rpmVa for files that have changed. There will always be some, devices, some files in /etc, and so on, but pay particular attention to *anything* in /sbin, /usr/sbin, /bin, /usr/bin, etc.... However, I'm guessing that you have hardware issues, just based upon experience with this sort of thing. One thing you could tell us is what the output from dmesg is after startup; knowing the hardware could help - it's entirely possible that it's a strange or weird network card and ssh just triggers a bug in the driver. -- Carpe diem - Seize the day. Carp in denim - There's a fish in my pants! Jon Nelson <[EMAIL PROTECTED]>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
