Follow-up Comment #10, bug #18554 (project findutils):
In addition to ARG_MAX (# bytes of args + environ for exec(), according to
linux/limits.h) the Linux kernel has another limit: the number of command
line arguments (including the 0th) cannot exceed 32767. Is this a standard,
too? Is find/xargs aware of this limit? (I can't see a constant defined for
it in linux/limits.h.)
Using the inline shell script wrapper you've just shown, one can hit this
limit. If you pass several options to scp, you may end up the scp command
taking more arguments than sh gets. So even if "find" correctly takes care
not to pass too many arguments to sh, it may eventually try to pass too many
for scp, and there's nothing "find" could do against it.
I still can't understand POSIX people... Slightly breaking backwards
compatibility is okay, but let's not introduce a useful new feature, let's
rather create ugly workarounds for them, because that would break bw
compatibility even a little bit more. Nevermind... :-)
How about allowing this feature only if POSIXLY_CORRECT is unset?
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?18554>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-findutils mailing list
Bug-findutils@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-findutils
