grep -roh aaa . | wc -w Grep recursively all files and directories in the current dir searching for aaa, and output only the matches, not the entire line. Then, just use wc to count how many words are there.
It would be: cp `ls -SF | grep -v / | head -5` Directory assuming that the pipeline is correct. The backticks substitute in the line the output of the commands inside it. You can also make your tests: cp `echo a b c` Directory will copy all a, b, and c into Directory.
yet another solution uses tr: echo $testVar | tr -d ‘\r’ cat myscript | tr -d ‘\r’ the option -d stands for delete.
File sutest #!/bin/bash echo “uid is ${UID}” echo “user is ${USER}” echo “username is ${USERNAME}” run it: `./sutest’ gives me uid is 500 user is stephenp username is stephenp but using sudo: sudo ./sutest gives uid is 0 user is root username is stephenp So you retain the original user name in $USERNAME when running …
cron is the general name for the service that runs scheduled actions. crond is the name of the daemon that runs in the background and reads crontab files. A crontab is a file containing jobs in the format minute hour day-of-month month day-of-week command crontabs are normally stored by the system in /var/spool/<username>/crontab. These files …
From: http://zch051383471952.blogspot.com/2010/01/different-of-real-user-sys-time.html Real refers to actual elapsed time; User and Sys refer to CPU time used only by the process. Real is wall clock time – time from start to finish of the call. This is all elapsed time including time slices used by other processes and time the process spends blocked (for example if …
find . -size +10000k -exec ls -sd {} + If your version of find won’t accept the + notation (which acts rather like xargs does), then you might use (GNU find and xargs, so find probably supports + anyway): find . -size +10000k -print0 | xargs -0 ls -sd or you might replace the + …
It’s because in your first case, your current shell expands the $HELLO variable before running the commands. And there’s no HELLO variable set in your current shell. env HELLO=’Hello World’ echo $HELLO will do this: expand any variables given, in this case $HELLO run env with the 3 arguments ‘HELLO=Hello World’, ‘echo’ and ” (an …
The messages you are receiving is due to a lack of permission on those files, i.e., those are error messages. All you have to do is to redirect the stderr (standard error output) to /dev/null, like this: grep -irl “foo” 2> /dev/null To lear more about redirection (on bash), read this article: Bash Reference Manual …
Using exit 0 will cleanly terminate the script. Whether Terminal window stays open is user-configurable. The default is to always stay open. To change this: Terminal.app > Preferences > Profiles > Shell – “When the shell exists:” > Close if the shell exited cleanly – “Ask before closing:” (•) Never — OR — (•) Only …