Parallel XZ with progress bar

function xzv() { THREADS=`grep processor /proc/cpuinfo | wc -l`; for file in $*; do pv -s `stat -c%s $file` < $file | pxz -q -T $THREADS > $file.xz ; done; }
You need: pxz for the actual work ( The function could be better with better multifile and stdin/out support.

By: oernii2
2011-12-14 08:22:08

What Others Think

Hmm... pv is a wonderful tool, but I'm not sure about the rest. First of all, pxz works out, for itself, how many processors/threads it can use. Even if you did need to tell it, you don't need "wc -l"; grep has a count option. THREADS=$(grep -c processor /proc/cpuinfo) Finally, quote your arguments to allow whitespace in filenames. "$@" does the right thing. for file in "$@"; do pxz "$file"; done
flatcap · 520 weeks and 3 days ago
I prefer to use:
syngin · 520 weeks and 2 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: