> "Nikola Milutinovic" <[EMAIL PROTECTED]> wrote:
> > I'm not subscribed to the list, so please CC to me.
> >
> > I believe I have located a problem with "csplit". I'm running as a part
of a pipe and it bombs my script with "pipe memory exhausted". This is the
script:
>
> Thanks for the report.
> A
The symptoms were a little vague, but if his data is larger than 2 GB,
and especially if it has any lines larger than 2 GB, then there are a
lot of bugs in csplit. I took an hour or so to start hacking away at
them, but it's a big job.
I'm a bit surprised that it happened only with a pipe, but ma
Thanks again for the report.
I was able to reproduce it consistently with this:
(while :; do echo =; yes jj|head -n1; done) \
| csplit - '/=$/' '{*}'
I got output like this:
0
270002
253910
csplit: memory exhausted
Here's the patch:
Don't exhaus
"Nikola Milutinovic" <[EMAIL PROTECTED]> wrote:
> I'm not subscribed to the list, so please CC to me.
>
> I believe I have located a problem with "csplit". I'm running as a part of a pipe
> and it bombs my script with "pipe memory exhausted". This is the script:
Thanks for the report.
A little mo
Hi all.
I'm not subscribed to the list, so please CC to me.
I believe I have located a problem with "csplit". I'm running as a part of a pipe and
it bombs my script with "pipe memory exhausted". This is the script:
#!/usr/bin/bash
DEF_SIZE=4000
DEF_INPUT="txt/input"
TMP_DIR="/usr/tmp"
output=
