RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 852045 - ulimit -c got Operation not permitted
Summary: ulimit -c got Operation not permitted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: sudo
Version: 6.3
Hardware: Unspecified
OS: Linux
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Daniel Kopeček
QA Contact: Aleš Mareček
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-08-27 12:32 UTC by Peter Svensson
Modified: 2018-12-01 18:09 UTC (History)
4 users (show)

Fixed In Version: sudo-1.8.6p3-1.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-02-21 09:44:45 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:0363 0 normal SHIPPED_LIVE sudo bug fix and enhancement update 2013-02-20 20:52:59 UTC

Description Peter Svensson 2012-08-27 12:32:47 UTC
Description of problem:

When using sudo to change ulmit for a user, we get Operation not permitted after sudo version 1.7.4p5-9


Version-Release number of selected component (if applicable): 1.7.4p5


How reproducible:

rpm --queryformat "%{VERSION}-%{RELEASE}\n" -q sudo 
1.7.4p5-13.el6_3
sudo /bin/su frodo.u -c "bash -c 'ulimit -c unlimited;exit'"
bash: line 0: ulimit: core file size: cannot modify limit: Operation not permitted

rpm --queryformat "%{VERSION}-%{RELEASE}\n" -q sudo 
1.7.4p5-12.el6_3
sudo /bin/su frodo.u -c "bash -c 'ulimit -c unlimited;exit'"
bash: line 0: ulimit: core file size: cannot modify limit: Operation not permitted

rpm --queryformat "%{VERSION}-%{RELEASE}\n" -q sudo 
1.7.4p5-11.el6
sudo /bin/su frodo.u -c "bash -c 'ulimit -c unlimited;exit'"
bash: line 0: ulimit: core file size: cannot modify limit: Operation not permitted

rpm --queryformat "%{VERSION}-%{RELEASE}\n" -q sudo 
1.7.4p5-9.el6_2
sudo /bin/su frodo.u -c "bash -c 'ulimit -c unlimited;exit'"
This works!!! 

  
Actual results:
cannot modify limit: Operation not permitted

Expected results:
The ulimit is changed 

Additional info:
-

Comment 6 Karel Srot 2012-10-17 07:31:27 UTC
I believe this is a duplicate to bug 836242.

Comment 7 Daniel Kopeček 2012-10-17 08:20:33 UTC
(In reply to comment #6)
> I believe this is a duplicate to bug 836242.

True... don't know why I didn't mark it as such.

Comment 11 errata-xmlrpc 2013-02-21 09:44:45 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0363.html


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