From owner-freebsd-current  Tue Dec 24 03:46:49 1996
Return-Path: <owner-current>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id DAA19705
          for current-outgoing; Tue, 24 Dec 1996 03:46:49 -0800 (PST)
Received: from sdev.usn.blaze.net.au (sdev.usn.blaze.net.au [203.17.53.19])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id DAA19700
          for <freebsd-current@freebsd.org>; Tue, 24 Dec 1996 03:46:42 -0800 (PST)
Received: from localhost (davidn@localhost) by sdev.usn.blaze.net.au (8.8.4/8.6.9) with SMTP id WAA06759 for <freebsd-current@freebsd.org>; Tue, 24 Dec 1996 22:46:37 +1100 (EST)
Date: Tue, 24 Dec 1996 22:46:37 +1100 (EST)
From: David Nugent <davidn@sdev.usn.blaze.net.au>
Reply-To: davidn@blaze.net.au
To: FreeBSD-current Mailing List <freebsd-current@freebsd.org>
Subject: Re: Problems with sshd and -current
In-Reply-To: <Pine.BSF.3.95.961224221701.5821G-100000@sdev.usn.blaze.net.au>
Message-ID: <Pine.BSF.3.95.961224224239.5821H-100000@sdev.usn.blaze.net.au>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Tue, 24 Dec 1996, David Nugent wrote:

>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.

A quick attach shows that it is in a signal handling loop:

#5  0x80c9490 in fstat ()
#6  0x80ca76f in malloc ()
#7  0x80c8937 in __smakebuf ()
#8  0x80c88c7 in __swsetup ()
#9  0x80c3b53 in vfprintf ()
#10 0x80c3631 in fprintf ()
#11 0x1b1f6 in signal_handler (sig=6) at signals.c:49
#12 0xefbfdfdc in end ()
#13 0x80c9441 in fstat ()
#14 0x80c9490 in fstat ()
#15 0x80ca76f in malloc ()
#16 0x80c8937 in __smakebuf ()
#17 0x80c88c7 in __swsetup ()
#18 0x80c3b53 in vfprintf ()
#19 0x80c3631 in fprintf ()
#20 0x1b1f6 in signal_handler (sig=6) at signals.c:49
#21 0xefbfdfdc in end ()

.. and so on.

Uh, I just noticed that removing /etc/malloc.conf "fixes" the
problem (which answers the question as to why it works elsewhere.
:-)).. Ok, looks like an sshd bug, not -current.

We now return you to your usual program or droll Christmas
classics...


Regards,

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/