Date: Tue, 24 Dec 1996 22:32:58 +1100 (EST) From: David Nugent <davidn@sdev.usn.blaze.net.au> To: FreeBSD-current Mailing List <freebsd-current@freebsd.org> Subject: Problems with sshd and -current Message-ID: <Pine.BSF.3.95.961224221701.5821G-100000@sdev.usn.blaze.net.au>
next in thread | raw e-mail | index | archive | help
Over the last few days I've noticed an oddity. One time it was a little more than that in that it caused memory/cpu starvation on the system it affected, and subsequently resulted in a crash. :-( Anyway, this is using -current (as of the today). ssh into the box shows: root 16004 0.0 2.4 308 716 ?? Is 10:16PM 0:01.83 /usr/local/sbin/sshd root 16007 0.0 3.1 340 936 ?? S 10:16PM 0:00.33 /usr/local/sbin/sshd Looks reasonable. Logout, ssh back in: root 16007 71.3 29.9 8404 9080 ?? R 10:16PM 0:26.32 /usr/local/sbin/sshd root 16004 0.0 2.3 308 684 ?? Is 10:16PM 0:01.83 /usr/local/sbin/sshd root 16076 0.6 3.0 340 900 ?? S 10:19PM 0:00.33 /usr/local/sbin/sshd Yow, 8 meg! Top shows: PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND 16007 root 92 0 8404K 9080K RUN 1:00 93.16% 93.15% sshd So it has gone into CPU tailspin as well. Does anyone have any ideas before I recompile with debugging info and see what in hell it is doing? ssh to a box running 2.2-ALPHA sitting right alongside works fine, without exhibiting this behaviour, and another remote box I often use running 2.1.5 also works fine (not to mentione freebsd.org's 2.1.6). The version of ssh in all cases is 1.2.17. Merry Christmas or happy holidays to everyone, David Nugent - Unique Computing Pty Ltd - Melbourne, Australia Voice +61-3-9791-9547 Data/BBS +61-3-9792-3507 3:632/348@fidonet davidn@freefall.org davidn@blaze.net.au http://www.blaze.net.au/~davidn/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.3.95.961224221701.5821G-100000>