🚀 go-pugleaf

In <1994Feb14.181931.12695@beaver.cs.washington.edu> drupp@cs.washington.edu (Douglas Rupp) writes:

>I installed bash (Bourne Again SHell) on my ODT 3.0 (Sco Unix 3.2v4.2) system
>on the suggestion that it would get rid of my "arg list too long" errors
>when doing simple commands like ls, mv, cp, rm, etc.  However it didn't.
>Where is this coming from?  Is there some parameter I can increase when
>building bash?  Is it the command itself that has the limitation?  Is it
>the system exec call?  Any helpful suggestions would be appreciated.

I have access to both a UnixWare and a SCO system.

I know that under UnixWare, there is a kernel parameter named ARG_MAX
that is the size of the total parameter area (argv+envp in c terms) for
new proceses.  This is the parameter that controls the maximum argument
list/environment list for exec system calls.

I have looked in the SCO kernel parameters, but I have not been able to
find a similar parameter.  Looks like you (and I) are out of luck

JC

ps: please let me know if you do get a more positive answer!
--
___  __  ____________________________________________________________________
   |/  \   Jan Christiaan van Winkel                        jc@sci.kun.nl
   |       Alternative e-mail addresses: jc@oreo.atcmp.nl and jc@atcmp.nl
__/ \__/ ____________________________________________________________________

gnu-bash-bug@cs.washington.edu wrote:
> I installed bash (Bourne Again SHell) on my ODT 3.0 (Sco Unix 3.2v4.2)
> system on the suggestion that it would get rid of my "arg list too long"
> errors when doing simple commands like ls, mv, cp, rm, etc.  However it
> didn't.  Where is this coming from?  Is there some parameter I can increase
> when building bash?  Is it the command itself that has the limitation?  Is
> it the system exec call?  Any helpful suggestions would be appreciated.

I'm no wizard, but this ain't no shell problem.  When you run a command
like "ls *.*" or "mv * <some directory>" all the shell does is expand the
wildcard into a list of filenames.  It is the program itself (/bin/ls,
/bin/mv) that's choking.  Adding memory or tweeking kernel parameters may
help, but the "usual" way around this is to wrap your command in a shell
script:

for file in $*
do
(command) $file (whatever...)
done

If you're into Perl, try using that too.  It's usually a little smarter
about memory.

Hope this helps.
--
+------------------------------------------------------------------------+
| Richard S. Smith  | PROGRESS(tm) 4GL Developer | Monrovia, California  |
| rsmith@netcom.com | "Holding my breath for V7" | Voice: (818) 303-7346 |
+------------------------------------------------------------------------+

rsmith@netcom.com (Richard Smith) writes:

>gnu-bash-bug@cs.washington.edu wrote:
>> I installed bash (Bourne Again SHell) on my ODT 3.0 (Sco Unix 3.2v4.2)
>> system on the suggestion that it would get rid of my "arg list too long"
>> errors when doing simple commands like ls, mv, cp, rm, etc.  However it
>> didn't.  Where is this coming from?  Is there some parameter I can increase
>> when building bash?  Is it the command itself that has the limitation?  Is
>> it the system exec call?  Any helpful suggestions would be appreciated.

>I'm no wizard, but this ain't no shell problem.  When you run a command
>like "ls *.*" or "mv * <some directory>" all the shell does is expand the
>wildcard into a list of filenames.  It is the program itself (/bin/ls,
>/bin/mv) that's choking.  Adding memory or tweeking kernel parameters may
>help, but the "usual" way around this is to wrap your command in a shell
>script:

>for file in $*
>do
>(command) $file (whatever...)
>done

>If you're into Perl, try using that too.  It's usually a little smarter
>about memory.

>Hope this helps.
>--
>+------------------------------------------------------------------------+
>| Richard S. Smith  | PROGRESS(tm) 4GL Developer | Monrovia, California  |
>| rsmith@netcom.com | "Holding my breath for V7" | Voice: (818) 303-7346 |
>+------------------------------------------------------------------------+

Try using the xargs(C) command. This should allow you to clear up you
problem.

BTW this is exactly a shell problem. Running the following will
demonstrate it on your system.

|# strings /bin/sh |grep 'too long'
|arg list too long
|sh error: pwd too long
|# strings /bin/ksh |grep 'too long'
|arg list too long
|name too long
|# strings /bin/csh |grep 'too long'
|Word too long
|Arguments too long
|Pathname too long
|Word too long
|Word too long
|Rhs too long
|Arg list too long
|Filename too long

Note that sh, ksh, and csh all contain the message text 'Arg list too long'
although the 'A' isn't capitalized in sh and ksh.
-- 
Jim Maddox (703)827-3298
maddoxj@hfsi.com

gnu-bash-bug@nl.net wrote:
: In <1994Feb14.181931.12695@beaver.cs.washington.edu> drupp@cs.washington.edu (Douglas Rupp) writes:

: >I installed bash (Bourne Again SHell) on my ODT 3.0 (Sco Unix 3.2v4.2) system
: >on the suggestion that it would get rid of my "arg list too long" errors
: >when doing simple commands like ls, mv, cp, rm, etc.  However it didn't.
: >Where is this coming from?  Is there some parameter I can increase when
: >building bash?  Is it the command itself that has the limitation?  Is it
: >the system exec call?  Any helpful suggestions would be appreciated.

For any gnu package that gives you this error, try the make from a non-ODT
window, and also try:

$ env - PATH=$PATH make ...

to clear out the environment first.  This is what did it for me.

R. Day