Bug 180896 - xargs fails with large environment
Summary: xargs fails with large environment
Keywords:
Status: CLOSED DUPLICATE of bug 135129
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: findutils
Version: 3.0
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Miloslav Trmač
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2006-02-10 12:19 UTC by Göran Uddeborg
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-13 17:11:34 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Script triggering the bug (23.32 KB, text/plain)
2006-02-10 12:19 UTC, Göran Uddeborg
no flags Details

Description Göran Uddeborg 2006-02-10 12:19:35 UTC
Description of problem:
If the environment is very large, xargs fails immediately on startup.

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

How reproducible:
Every time

Steps to Reproduce:
1.Run the attached script

Actual results:
Output of "xargs: environment is too large for exec" and exit status 1.

Expected results:
No output and exit status 0.

Additional info:
This problem is fixed in later upstreams version.  The version in RHEL 4 (rpm -q
-f `which xargs`) is also not affected.  But RHEL 3 does fail.

Comment 1 Göran Uddeborg 2006-02-10 12:19:35 UTC
Created attachment 124486 [details]
Script triggering the bug

Comment 2 Göran Uddeborg 2006-02-10 15:59:09 UTC
Sorry about the silly reference to RHEL 4 findutils in comment 0.  It should say
findutils-4.1.20-7, of course.

Comment 3 Miloslav Trmač 2006-02-13 17:11:34 UTC
Thanks for your report.  This is already tracked for RHEL 3, although probably
not easy to find.

*** This bug has been marked as a duplicate of 135129 ***

Comment 4 Göran Uddeborg 2006-02-13 17:39:36 UTC
So it was the same!  I searched and found that one, but I was not sure it was
the same problem.  I wasn't sure if ARG_MAX was just for arguments, or actually
included the environment.  And the error message I saw wasn't mentioned there.

But if it indeed is about the same thing, than fine! :-)


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