Bug 58467 - Bash seems to now have a smaller limit on the number of arguments that can be passed to programs
Summary: Bash seems to now have a smaller limit on the number of arguments that can be...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: bash
Version: 7.2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bernhard Rosenkraenzer
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-01-17 14:30 UTC by Terry Barnaby
Modified: 2007-04-18 16:39 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-01-23 11:30:13 UTC
Embargoed:

Attachments (Terms of Use)
Code demonstrating it's not a bash problem (433 bytes, text/plain)
2002-01-23 11:30 UTC, Bernhard Rosenkraenzer 		no flags Details
View All

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.
Note You need to log in before you can comment on or make changes to this bug.