From owner-freebsd-security Tue Apr 23 14: 3:18 2002 Delivered-To: freebsd-security@freebsd.org Received: from shark.amis.net (shark.amis.net [212.18.32.14]) by hub.freebsd.org (Postfix) with ESMTP id 1A62437B41D for ; Tue, 23 Apr 2002 14:03:12 -0700 (PDT) Received: from baracuda.amis.net (baracuda.amis.net [212.18.32.4]) by shark.amis.net (Postfix) with ESMTP id 255067C05 for ; Tue, 23 Apr 2002 23:03:11 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by baracuda.amis.net (Postfix) with ESMTP id E48229B12 for ; Tue, 23 Apr 2002 23:03:10 +0200 (CEST) Received: from titanic.medinet.si (titanic.medinet.si [212.18.42.5]) by baracuda.amis.net (Postfix) with ESMTP id 0B8119B11 for ; Tue, 23 Apr 2002 23:03:10 +0200 (CEST) Received: by titanic.medinet.si (Postfix, from userid 1000) id 8474D55411; Tue, 23 Apr 2002 23:03:09 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by titanic.medinet.si (Postfix) with ESMTP id 8262555404 for ; Tue, 23 Apr 2002 23:03:09 +0200 (CEST) Date: Tue, 23 Apr 2002 23:03:09 +0200 (CEST) From: Blaz Zupan X-X-Sender: blaz@titanic.medinet.si To: freebsd-security@freebsd.org Subject: segfault in ftpd Message-ID: <20020423225805.Q93786-100000@titanic.medinet.si> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Virus-Scanned: by AMaViS perl-11 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org For some time now I see messages like this in the logs on our webserver: pid 36861 (ftpd), uid 29987: exited on signal 11 This is with the stock ftpd on 4.5-RELEASE-p3 (users use it to upload their web pages to it). I compiled ftpd with -g and tried to set it up so that I get a coredump. I configured: mkdir /var/coredumps chmod 1777 /var/coredumps sysctl kern.corefile=/var/coredumps/%U.%N.%P.core Now I can create a simple program that crashes and the core will be written to /var/coredumps. But ftpd simply does not want to create a coredump. As far as I can see, /etc/login.conf specifies coredumpsize=unlimited. Is there anything else I need to configure or tune to be able to catch a coredump? I'd really like to catch this one before 4.6-RELEASE ;-) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message