From owner-freebsd-hackers Tue Nov 16 4:53:52 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from citadel.cequrux.com (citadel.cdsec.com [192.96.22.18]) by hub.freebsd.org (Postfix) with ESMTP id 8E41E14C93 for ; Tue, 16 Nov 1999 04:53:30 -0800 (PST) (envelope-from gram@cequrux.com) Received: (from nobody@localhost) by citadel.cequrux.com (8.9.3/8.9.3) id OAA29641 for ; Tue, 16 Nov 1999 14:53:27 +0200 (SAST) Received: by citadel.cequrux.com via recvmail id 29573; Tue Nov 16 14:53:06 1999 From: Graham Wheeler To: hackers@freebsd.org Subject: Missing core dumps Date: Tue, 16 Nov 1999 14:45:26 +0200 X-Mailer: KMail [version 1.0.28] Content-Type: text/plain MIME-Version: 1.0 Message-Id: <9911161453040F.23105@cequrux.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Howdy all I have a program that occasionally catches a SEGV signal, but it doesn't dump core. And I really could use that core file, as I can't replicate the problem under controlled conditions. The program is invoked from inetd. It is owned by user nobody and has group mail. When it starts up, it calls setuid and setgid to set the user and group to be nobody and mail respectively. It then chroots to a directory which is owned by bin and has group mail. This directory has owner and group read, write and execute permissions on. The program can create and destroy temporary files in this directory without any problem. It doesn't catch SEGV signals in its own handler, and it has no obvious file size limits. From my reading of Stevens APITUE, there are no reasons why the core file shouldn't be created. Am I missing something? (This is on 2.2.7 and 2.2.8 systems, although I suspect the behaviour will be unchanged under 3.x) TIA gram -- Dr Graham Wheeler E-mail: gram@cequrux.com Cequrux Technologies Phone: +27(21)423-6065/6/7 Firewalls/Virtual Private Networks Fax: +27(21)24-3656 Data/Network Security Specialists WWW: http://www.cequrux.com/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message