[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: Non working link on the webpage for Busybox.
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2010-06-19 19:43:14
Message-ID: 201006192143.14283.vda.linux () googlemail ! com
[Download RAW message or body]

On Sunday 13 June 2010 10:18, Bernhard Reutner-Fischer wrote:
> On Sun, Jun 13, 2010 at 03:47:16AM +0200, Denys Vlasenko wrote:
> >On Wednesday 09 June 2010 21:26, Bernhard Reutner-Fischer wrote:
> 
> >> xargs-double-size.patch better realloc or worth a config option?
> >
> >I prefer to just fix -s NUM to be able to take arbitrarily big NUM
> >(currently we restrict it) - this way user can not only restrict,
> >but only ENLARGE the max possible comand line, above what
> >system headers say is a safe limit (because headers can be wrong).
> >
> >I did so in git.
> 
> big findutils limit n_max_chars to 128k if no -s was given.

I am bumping it up to 32k for now - 128k *fixed* allocation
by default is a bit much.

# yes | ./busybox xargs echo | head -1 | wc -c
32762
xargs: echo: terminated by signal 13

-s NUM is assepted even with large

# yes | ./busybox xargs -s 1000000 echo | head -1 | wc -c
999994
xargs: echo: terminated by signal 13

# yes | ./busybox xargs -s 2700000 echo | head -1 | wc -c
2699994
xargs: echo: terminated by signal 13

signal 13 is SIGPIPE. echo dies with SIGKILL (?) when I try -s 2800000:

# yes | ./busybox xargs -s 2800000 echo | head -1 | wc -c
xargs: echo: terminated by signal 9
0


Does it look good enough?
-- 
vda

_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]