On Sun, Dec 21, 2014 at 09:51:41AM +0100, Ian Hinder wrote: > I thought the entire purpose of xargs was to split up the command invocations > so that each one did not exceed the maximum length? It's also using "-n 1", > so only one file should be processed at a time. Also, doesn't the for loop > suffer from the same problem?
Here, the shell expanded to a potentially quite long command. I imagine the new code circumvents this problem by only partially evaluating the arguments, "finding" the files bit by bit. And yes: xargs splits up the arguments, but it is the input to xargs that is already too large. I wonder if there would be a way to increase that limit on AIX, which I would prefer to complicating our code. Frank
signature.asc
Description: Digital signature
_______________________________________________ Users mailing list [email protected] http://cactuscode.org/mailman/listinfo/users
