You could also test a value of "0":
RE: man xargs
Code:
-P max-procs, --max-procs=max-procs
Run up to max-procs processes at a time; the default is 1. If max-procs is 0, xargs will run as
many processes as possible at a time. Use the -n option or the -L option with -P; otherwise chances
are that only one exec will be done. While xargs is running, you can send its process a SIGUSR1
signal to increase the number of commands to run simultaneously, or a SIGUSR2 to decrease the num‐
ber. You cannot increase it above an implementation-defined limit (which is shown with --show-lim‐
its). You cannot decrease it below 1. xargs never terminates its commands; when asked to decrease,
it merely waits for more than one existing command to terminate before starting another.
Please note that it is up to the called processes to properly manage parallel access to shared re‐
sources. For example, if more than one of them tries to print to stdout, the output will be pro‐
duced in an indeterminate order (and very likely mixed up) unless the processes collaborate in some
way to prevent this. Using some kind of locking scheme is one way to prevent such problems. In
general, using a locking scheme will help ensure correct output but reduce performance. If you
don't want to tolerate the performance difference, simply arrange for each process to produce a sep‐
arate output file (or otherwise use separate resources).
Also a good read: https://blog.tratif.com/2023/01/30/b...m-using-xargs/
