bug#7357: csplit: memory exhausted when using stdout / pipe instead of a
From:
Bob Proulx
Subject:
bug#7357: csplit: memory exhausted when using stdout / pipe instead of a file
Date:
Wed, 10 Nov 2010 18:10:05 -0700
User-agent:
Mutt/1.5.20 (2009-06-14)
Jim Meyering wrote:
>http://git.sv.gnu.org/cgit/coreutils.git/commit/?id=cf0fa2d930de1609
>
> Use seq, not `yes' to generate link target.
> Otherwise, on systems (DJGPP) that emulate pipes using files,
> this test would never complete, waiting for `yes' to terminate.
>
> diff --git a/tests/du/slink b/tests/du/slink
> - name=`yes|tr '\n' y|head -c$len`
> + name=`seq 1 $len|tr -c x y |head -c$len`
>
> Is DJGPP still relevant?
> The last update of http://www.delorie.com/djgpp/ was in 2003.
> Now, I'm tempted to leave your seq|head pipe there,
> just to see if anyone notices.
Is using files to emulate pipes even a valid operating model? I
wouldn't have thought so. In which case any system like that is just
insufficient to the task. Avoiding pipes just for such systems
doesn't seem very productive to me.
I would be inclined to have a test not for the program but for the
operating system to ensure that the OS is sufficiently capable.
Just my two cents...
Bob