Top Unix Command Line Utilities

Post by cynwoody » Sun, Dec 30, 2012, 7:03 PM UTC

aidos wrote: post #27

imglorp wrote: post #11

Earlier quoted context omitted.

That whole "find -ls | awk" is wicked slow anyway; try wc and xargs... $ time find -ls | awk '{s += $7} END {print s}' 15970582120 real 0m27.721s user 0m1.256s sys 0m1.780s $ time find | xargs wc -c 2> /dev/null | tail -1 604260969 total real 0m0.332s user 0m0.068s sys 0m0.204s

You sure that's not because of memory swapping? Once warmed up the awk command is much faster for me. Also, the results are different - though I'm too lazy to figure out why right now :)

    find -type f -ls|awk '{s += $7} END {print s}'
    find -type f -print0 | xargs -0 wc -c | tail -1
    find -type f -exec wc -c {} + | tail -1

Post by akurilin » Sun, Dec 30, 2012, 8:48 PM UTC

Post by prostoalex » Sun, Dec 30, 2012, 10:27 PM UTC

niggler wrote: post #10

Where's the love for awk? It has been tucked away in a sub item but doesn't deserve first class status?

Post by kps » Sun, Dec 30, 2012, 11:19 PM UTC

stiff wrote: post #38

decklin wrote: post #36

Earlier quoted context omitted.

The for loop works fine. Performing word splitting/wildcard expansion/etc on a variable will, well, split it into words/expand wildcards/etc, whether it was introduced by a for loop or not.

I am not sure I understand what you mean. Word-splitting is performed by the "for x in y" construct, using the IFS variable, so by default if you have a file called "foo bar.mp4" the command line from the article: for i in *.mp4; do ffmpeg -i "$i" "${i%.mp4}.mp3"; done will result in executing: ffmpeg -i foo foo.mp3 ffmpeg -i bar.mp4 bar.mp3 Which is obviously not what was meant. So it's a good habit to learn to loop…

  $ function echon { echo $# $*; }                    
  $ >'foo bar.mp4'
  $ for i in *.mp4; do echon "$i" "${i%mp4}mp3"; done 
  2 foo bar.mp4 foo bar.mp3

Post by kps » Sun, Dec 30, 2012, 11:22 PM UTC

helper wrote: post #42

FuzzyDunlop wrote: post #5

You can also use Ctrl+T to get the status of a running command, instead of faffing about with pids and kill.

That doesn't work for me, but sending USR1 does.