From owner-freebsd-questions@FreeBSD.ORG Fri Jun 18 19:09:14 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C79B3106566B for ; Fri, 18 Jun 2010 19:09:14 +0000 (UTC) (envelope-from m.seaman@infracaninophile.co.uk) Received: from smtp.infracaninophile.co.uk (gate6.infracaninophile.co.uk [IPv6:2001:8b0:151:1::1]) by mx1.freebsd.org (Postfix) with ESMTP id 350538FC13 for ; Fri, 18 Jun 2010 19:09:14 +0000 (UTC) Received: from seedling.black-earth.co.uk (seedling.black-earth.co.uk [81.187.76.163]) (authenticated bits=0) by smtp.infracaninophile.co.uk (8.14.4/8.14.4) with ESMTP id o5IJ98BI011514 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Fri, 18 Jun 2010 20:09:09 +0100 (BST) (envelope-from m.seaman@infracaninophile.co.uk) Message-ID: <4C1BC454.4060505@infracaninophile.co.uk> Date: Fri, 18 Jun 2010 20:09:08 +0100 From: Matthew Seaman Organization: Infracaninophile User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.1.10) Gecko/20100512 Thunderbird/3.0.5 MIME-Version: 1.0 To: Tim Daneliuk References: <4C1BB9D9.10704@tundraware.com> <4C1BBA99.9010705@gmail.com> <4C1BBB4E.8080907@tundraware.com> <4C1BBC19.8030007@gmail.com> <4C1BC075.4030903@tundraware.com> <4C1BC15A.5020301@tundraware.com> In-Reply-To: <4C1BC15A.5020301@tundraware.com> X-Enigmail-Version: 1.0.1 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.96.1 at lucid-nonsense.infracaninophile.co.uk X-Virus-Status: Clean X-Spam-Status: No, score=1.6 required=5.0 tests=BAYES_50,DKIM_ADSP_ALL, SPF_FAIL autolearn=no version=3.3.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on lucid-nonsense.infracaninophile.co.uk Cc: FreeBSD Mailing List Subject: Re: Followup On Perl Dumping Core X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 18 Jun 2010 19:09:14 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 18/06/2010 19:56:26, Tim Daneliuk wrote: > I should mention that I don't think it is actually "dumping core". > It's just reporting the problem in /var/log/messages... You'll only get a core file if the current working directory of the process is writable by the process. Normally. There are various sysctls you can use to affect core-dumping: kern.corefile: process corefile name format string kern.coredump: Enable/Disable coredumps kern.sugid_coredump: Enable coredumping set user/group ID processes See core(5). It is possible to set kern.corefile to an absolute path -- eg /tmp/%N.core -- to always record corefiles in a writable directory. Also, look at setrlimit values for the maximum size core file permitted. Cheers, Matthew - -- Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard Flat 3 PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate JID: matthew@infracaninophile.co.uk Kent, CT11 9PW -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkwbxFQACgkQ8Mjk52CukIwOFACfWpg3voC/YqPXRWLS6NHyQZxy F0UAn178RJ7+eQvU7kygDSB24fZMsayL =QJmo -----END PGP SIGNATURE-----