Bug 314461

Summary:	bash using incorrect block size with limits
Product:	[Fedora] Fedora	Reporter:	Daniel Qarras <dqarras>
Component:	bash	Assignee:	Roman Rakus <rrakus>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	8	CC:	tsmetana, twaugh
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-06-25 12:29:36 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daniel Qarras 2007-10-01 18:41:31 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 bash I get this:

$ ulimit -Hc
32768

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

However, http://ftp.gnu.org/gnu/bash/bash-3.2.tar.gz has the following in
bash-3.2/builtins/ulimit.def:

static RESOURCE_LIMITS limits[] = {
#ifdef RLIMIT_CORE
  { 'c',        RLIMIT_CORE,  1024,     "core file size",      
"blocks" },
#endif

Same goes for several other limits.

FWIW, zsh and ksh are using 512 and bash and tcsh are using 1024. I think bash
should be fixed. I'll open another case against tcsh.

Comment 1 Daniel Qarras 2007-10-01 18:44:44 UTC

The bug against tcsh is Bug 314471.

Comment 2 Daniel Qarras 2007-10-01 18:58:04 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.

Comment 3 Pete Graner 2007-10-01 19:06:03 UTC

Looks like a bug, however to be sure I've sent a query to the upstream
maintainers to get their take on it. More once I have it.

Comment 4 Daniel Qarras 2007-10-12 20:53:12 UTC

Thanks for the info. Would be nice to get this fixed for F8.

Comment 5 Daniel Qarras 2007-12-29 16:15:37 UTC

Still exists in Fedora 8. Upstream will be probably fixed in the next version
according to mailing list discussions.

Comment 6 Roman Rakus 2008-06-25 12:29:36 UTC

Yep. As in Comment #5 -> close upstream