On Tue, Feb 23, 2010 at 11:23 AM, Anthony Howe <ach...@snert.com> wrote: > Without the call to setuid, then the daemon will create a core file in /tmp. > > What I would like to know is how to get a core file when the daemon > program uses setuid/seteuid family of functions, which appears to make > it subject to kern.nosuidcoredump? I've tried all 3 possible values
Not sure. I added the 2 setting just for scenarios like this, but it was several years ago. Looks like it doesn't work. Maybe it never did. :(
