Top Unix Command Line Utilities

Post by 4ad » Mon, Dec 31, 2012, 11:42 AM UTC

coldgrnd wrote: post #56

4ad wrote: post #48

The second #6 example, the one with xargs, is wrong. Xargs(1) doesn't necessarily create a single du process, it might create several.

I was wondering about that, but is it really wrong? From what I found in the "BSD General Commands Manual": Any arguments specified on the command line are given to utility upon each invocation, followed by some number of the arguments read from the standard input of xargs. The utility is repeatedly executed until standard input is exhausted. and -P maxprocs Parallel mode: run at most maxprocs invocations of utility…

Post by niggler » Mon, Dec 31, 2012, 3:23 PM UTC

coldgrnd wrote: post #28

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?

actually there is heaps of love for awk... so much actually that I'd rather spend a whole post on it than to "just" make it one item :)

Post by visarga » Mon, Jan 07, 2013, 7:43 AM UTC

EvilTerran wrote: post #8

visarga wrote: post #6

My 2012 top, in order of usage: joe, ls, cd, time, cdbdump, tail, more, cat, rm, grep, wc, apachectl restart, find, curl, chmod, history, mv, locate, cpan, apt-get, pwd But the most useful one is a command line Perl utility I called "flt" that executes a block of perl code for each in the stdin. cat file.txt | flt ' $line=~ s|\s+| |gsi; print $line."\n"; ' That would compact free spaces find . | flt ' if (-f $line) {…

Are you familiar with perl's -n and -p switches? http://perldoc.perl.org/perlrun.html#*-n* Those "flt" lines could be written perl -lpe 's|\s+| |gsi' file.txt find . | perl -ne 'if (-f) { print -s }' (-l chomps the incoming newlines, and puts them back on the output) Of course, "perl -ne" is longer than "flt", and I appreciate all this implicit use of $_ is not to everyone's tastes.