[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: gnu parallel in the bash manual

From: John Kearney
Subject: Re: gnu parallel in the bash manual
Date: Sun, 03 Mar 2013 16:09:21 +0100
User-agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130215 Thunderbird/17.0.3

Am 03.03.2013 01:40, schrieb Chet Ramey:
>> this is actually more disturbing.
>> ls | parallel mv {} destdir
>> find -type f -print0 | xargs -0 -I{} -P <NumJobs> /bin/mv {} <destdir>
> If we're really going to pick nits here, those two aren't really identical.
> You'd probably want something like
> find . -depth 1 \! -name '.*' -print0
> to start.
> Chet
Sure your right what I showed wasn't a 1 to 1 functional replacement,
but then again most times I see ppl using a ls | syntax they actually
don't intend that functionality, its a side effect of them not knowing
how to use a better syntax.
The example is bad anyway as you normally don't want to parallelize disk
io , due to seek overhead and io bottle neck congestion. This example
will be slower and more likely to damage your disk than simply using mv
on its own. but thats another discussion.

with regards to nit picking, considering how much effort is made on this
mailing list and help-bash to give filename safe examples, its hardly
nitpicking to expect the examples in the bash manual to be written to
the same standard.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]