Bug 314471 - tcsh using incorrect block size with limits
tcsh using incorrect block size with limits
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: tcsh (Show other bugs)
7
All Linux
low Severity low
: ---
: ---
Assigned To: Vitezslav Crhonek
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-10-01 14:44 EDT by Daniel Qarras
Modified: 2007-11-30 17:12 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2007-10-01 15:00:12 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Daniel Qarras 2007-10-01 14:44:24 EDT
On a Fedora 7 I have set following limits (only) on /etc/security/limits.conf:

*               soft    core            0
*               hard    core            32768

When I use tcsh I get this:

% limit -h core
coredumpsize 32768 kbytes

But with zsh I get this:

$ ulimit -Hc
65536

Reading the standards below it seems unambiguous that the correct block size
should be 512:

http://www.opengroup.org/onlinepubs/000095399/utilities/ulimit.html
http://www.opengroup.org/onlinepubs/009695399/functions/ulimit.html

FWIW, zsh and ksh are using 512 and bash and tcsh are using 1024. I think tcsh
should be fixed.

A similar bug against Bash is Bug 314461.
Comment 1 Daniel Qarras 2007-10-01 14:57:28 EDT
Actually, when reading /etc/security/limits.conf it says:

#<item> can be one of the following:
#        - core - limits the core file size (KB)

So tcsh is working correctly here, only bash is incorrect here.

Please close this one.

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