-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Bob Proulx on 9/5/2005 3:33 PM:
>
> (export TIMEFORMAT='real %3lR user %3lU sys %3lS'
> for i in 1024 2048 4096 8192 16384 20480; do
> printf "timing $i: "
> yes | head --bytes=10m | bash -c "time xargs -s$i /bin/echo > /dev
Eric Blake wrote:
> But even if cygwin 1.5.19 were to define ARG_MAX and changes
> sysconf(_SC_ARG_MAX) to 32k instead of 1 meg, this would unfairly
> penalize cygexec mounts, which can handle much bigger command lines.
I know this sounds like it would unfairly limit all uses because some
uses are
Jens Schleusener wrote:
> Oh, just I found in /usr/include/fcntl.h the lines
>
> /* Redefine open and creat for large file enabled programming environment.
> */
> #ifdef _LARGE_FILES
> #define open open64
> #define creat creat64
> #endif
>
> just a line as you suspected in your previous
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Cygwin has an interesting situation affecting xargs 4.2.25, where the
maximum command-line length of a command is determined by the command
being executed. If the command lives on a cygwin-executable mount, the
command line is passed using cygwin inte
On Sun, 4 Sep 2005, James Youngman wrote:
On Sun, Sep 04, 2005 at 06:52:15PM +0100, James Youngman wrote:
The problem is fairly easily worked around by
[...]
More explicitly, you could apply this patch:-
Index: find/defs.h
===
