Bug 10650 - non-privileged users can't set core dump size to non-zero
non-privileged users can't set core dump size to non-zero
Product: Red Hat Linux
Classification: Retired
Component: kernel (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Michael K. Johnson
Depends On:
  Show dependency treegraph
Reported: 2000-04-07 16:52 EDT by glenn
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2000-04-09 18:40:00 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description glenn 2000-04-07 16:52:57 EDT
New to 6.1 is the inability of the ordinary user to get a core file.
Somehow, unless you have super user privileges, the ordinary user can't
execute 'setrlimit(RLIMIT_CORE, ..)'.  So in bash, 'ulimit -c' and in tcsh,
'limit coredumpsize' result in privilege violations.

This is bordering on catastrophe for us poor developers.   There's nothing
like a core file to find out why a program crapped out, especially if
it happened off site, in front of a naive user.

Please put it back!
Comment 1 glenn 2000-04-09 18:40:59 EDT
Please delete/ignore this report pending further investigation.

Note You need to log in before you can comment on or make changes to this bug.