Bug 314471 - tcsh using incorrect block size with limits
Summary: tcsh using incorrect block size with limits
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: tcsh
Version: 7
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-01 18:44 UTC by Daniel Qarras
Modified: 2007-11-30 22:12 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2007-10-01 19:00:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Daniel Qarras 2007-10-01 18:44:24 UTC
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 18:57:28 UTC
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.