From owner-freebsd-current Mon Sep 18 7:21:38 2000 Delivered-To: freebsd-current@freebsd.org Received: from lucifer.ninth-circle.org (lucifer.bart.nl [194.158.168.74]) by hub.freebsd.org (Postfix) with ESMTP id 940C237B422; Mon, 18 Sep 2000 07:21:35 -0700 (PDT) Received: (from asmodai@localhost) by lucifer.ninth-circle.org (8.11.0/8.9.3) id e8IELG407224; Mon, 18 Sep 2000 16:21:16 +0200 (CEST) (envelope-from asmodai) Date: Mon, 18 Sep 2000 16:21:15 +0200 From: Jeroen Ruigrok van der Werven To: Alexander Leidinger Cc: current@FreeBSD.ORG, kris@FreeBSD.ORG Subject: Re: updated OpenSSH & pam_ssh, the old bug is back Message-ID: <20000918162115.A7126@lucifer.bart.nl> References: <20000918155741.K4858@lucifer.bart.nl> <200009181417.e8IEHOV04422@Magelan.Leidinger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <200009181417.e8IEHOV04422@Magelan.Leidinger.net>; from Alexander@leidinger.net on Mon, Sep 18, 2000 at 04:17:22PM +0200 Organisation: VIA Net.Works The Netherlands Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG -On [20000918 16:20], Alexander Leidinger (Alexander@leidinger.net) wrote: >On 18 Sep, Jeroen Ruigrok van der Werven wrote: > >> You mean that bug which you reported and produced a patch and which I >> subsequently committed? The malloc.conf -> AJ resulted coredump one? > >Initially yes, but at the moment I'm under the impression it's another >bug (I don't know where it is and how to fix it), the old one seems to >be fixed. Is it a malloc.conf -> AJ related bug again? =) Anyway, if you find it, don't hesitate to let me know, so I can apply it. Cheers, -- Jeroen Ruigrok van der Werven Network- and systemadministrator VIA Net.Works The Netherlands BSD: Technical excellence at its best http://www.via-net-works.nl Grant me the serenity to accept the things I cannot change, courage to change the things I can, and wisdom to know the difference... To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message