Date: Fri, 18 Jun 2010 20:09:08 +0100 From: Matthew Seaman <m.seaman@infracaninophile.co.uk> To: Tim Daneliuk <tundra@tundraware.com> Cc: FreeBSD Mailing List <freebsd-questions@freebsd.org> Subject: Re: Followup On Perl Dumping Core Message-ID: <4C1BC454.4060505@infracaninophile.co.uk> In-Reply-To: <4C1BC15A.5020301@tundraware.com> 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>
next in thread | previous in thread | raw e-mail | index | archive | help
-----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-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C1BC454.4060505>