Kai Gro�johann writes:
 > Joe Stoy <[EMAIL PROTECTED]> writes:
 > 
 > > OK -- I can reproduce the problem without involving tramp at all.
 > > It turns out that for this particular directory (at least) the
 > > command
 > >    /bin/ls -d .*/ */ 2>/dev/null | cat
 > > causes the /bin/ksh on the server (Solaris) to hang with no
 > > output.  I've asked the server's sysadmins to tell my why.
 > 
 > Sigh.  I think a few shells have problems with very long command
 > lines, and globbing in directories with many entries is likely to
 > produce very long command lines.

It's not the shell but the exec that has this limitation.  The size of
command line arguments plus environment strings has to be less than
ARG_MAX.  This can be queried with sysconf (a standard C function and
sometimes also a command).  It may be set as a kernel tunable.
-- 
Pete Forman              | Disclaimer: This posting is originated by
Western Geophysical      | myself and does not represent the opinion
[EMAIL PROTECTED]  | of Baker Hughes or its divisions.

Reply via email to