From: Tod A. Sandman (sandmant@is.rice.edu)
Date: Thu Jul 07 2005 - 14:31:28 EDT
Thanks to Darren Dunham with the simple answer.
I was using coreadm to enable setuid coredumps, but I was not
setting a global pattern for core files. Setting a pattern
with this did the trick:
coreadm -g /core
Additionally, as Darren stated, directory permissions don't
matter since setuid cores will be written by root.
On Fri, Jun 24, 2005 at 01:33:27PM -0500, Tod A. Sandman wrote:
> I have a SUID daemon, "dspam", that I fire up as root, and it
> suid's to user "dspam". It segfaults after some time, and I
> need to get a core file (but cannot get it to leave one).
>
> I've tried
> ulimit -c unlimited
> as root before I fire up the daemon. I have tried
> coreadm -e global -e process -e global-setid -e proc-setid
> The dspam user owns the directory where the daemon resides
> and from where I fire it up.
>
> When it segfaults, no core file is left.
> When I run gcore on it as user dspam, I get
> gcore: cannot grab 18158: permission denied
> ....................
Tod Sandman
Sr. Systems Administrator
Middleware Development & Integration
Rice University
Voice: 713.348.5816
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers
This archive was generated by hypermail 2.1.7 : Wed Apr 09 2008 - 23:31:03 EDT