From: jared <demottjar@yahoo.com>
To: linux-kernel@vger.kernel.org
Subject: Why doesn't my system have the core_setuid_ok key?
Date: Fri, 30 Dec 2005 09:19:26 -0500 [thread overview]
Message-ID: <dp3fot$6df$1@sea.gmane.org> (raw)
Hello all:
I'm running the postfix mailing system and made a few modifications.
It's dieing with signal 11 but not dumping core -- and I need a core
dump. I asked on the postfix group how to deal with this but they said
I need to come talk to a linux group. They said the reason is because
my system will not let a process that starts life as root (but than
drops privs) to dump core. They said I need to check my
kernel.core_setuid_ok key, but my systems don't have that key. (I have
redhat (2.4.20) and FC (2.6.12))
I've also already modified the /etc/security/limits and /etc/profile to
allow system wide cores.
Can anyone shed some light on my attempts to get cores?
Thanks,
Jared DeMott
reply other threads:[~2005-12-30 14:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='dp3fot$6df$1@sea.gmane.org' \
--to=demottjar@yahoo.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox