Joined May 2011
·
Posted to
How NOT to delete files with the find command
over 1 year
ago
Those using xargs, I suggest you read man xargs and look at the -P parameter:
-P 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 with -P; otherwise chances are
that only one exec will be done.
This is cool, because that means you can spawn >1 instance of rm to do your calls, which should give a minor improvement if you manage to get the kernel batching the underlying rm calls.
Achievements
109 Karma
0 Total ProTip Views
Raven
Have at least one original repo where some form of shell script is the dominant language
Komodo Dragon
Have at least one original repo where Java is the dominant language
Walrus
The walrus is no stranger to variety. Use at least 4 different languages throughout all your repos
Velociraptor 3
Have at least three original repos where Perl is the dominant language
Velociraptor
Have at least one original repo where Perl is the dominant language
Nephila Komaci 3
Have at least three original repos where PHP is the dominant language
Nephila Komaci
Have at least one original repos where PHP is the dominant language
Philanthropist
Truly improve developer quality of life by sharing at least 50 individual open source projects
Altruist
Increase developer well-being by sharing at least 20 open source projects
Forked
Have a project valued enough to be forked by someone else
Charity
Fork and commit to someone's open source project in need
"There is nothing wrong with git pull, as long as you know, what you are doing (ask your coworker ;))."
But it is for that reason I can't recommend 'pull' to novices, it makes them do the wrong thing, and impedes them from understanding the git 'model'.
It is initially more convenient. But convenience at the price of doing the wrong thing is a steep penalty.