Bug 58467

Summary: Bash seems to now have a smaller limit on the number of arguments that can be passed to programs
Product: [Retired] Red Hat Linux Reporter: Terry Barnaby <terry1>
Component: bashAssignee: Bernhard Rosenkraenzer <bero>
Status: CLOSED NOTABUG QA Contact: Ben Levenson <benl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.2CC: terry1
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2002-01-23 11:30:13 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:
Attachments:
Description Flags
Code demonstrating it's not a bash problem none

Description Terry Barnaby 2002-01-17 14:30:02 UTC
Description of Problem:


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


How Reproducible:
always

Steps to Reproduce:
1. ls */*/*/* in a big tree of files
2. 
3. 

Actual Results:


Expected Results:


Additional Information:

Comment 1 Jakub Jelinek 2002-01-22 17:00:34 UTC
*** Bug 58649 has been marked as a duplicate of this bug. ***

Comment 2 Bernhard Rosenkraenzer 2002-01-23 11:30:08 UTC
Created attachment 43274 [details]
Code demonstrating it's not a bash problem

Comment 3 Bernhard Rosenkraenzer 2002-01-23 11:32:01 UTC
As you can see from the attached C application, the limit is enforced by glibc's
exec functions, not bash.
Call the application with parameter 32767 and it'll work, call it with 32768 and
it'll show the error message.

This limit has always been the same (if you don't believe me, try running the
test application on older releases), so I think it's not a bug.