find /usr/share/doc -type f -exec cat {} + > output_file.txt
Then run the watch command.
"watch -d" highlights the changes as they happen
In bash: $! is the process id (pid) of the last command run in the background.
You can change this to $(pidof my_command) to watch something in particular.
Every 2.0s: ls -l /proc/4958/fd Fri Jan 31 23:44:07 2014 total 0 lrwx------. 1 flatcap flatcap 64 Jan 31 23:43 0 -> /dev/pts/3 l-wx------. 1 flatcap flatcap 64 Jan 31 23:43 1 -> /home/flatcap/output_file.txt lrwx------. 1 flatcap flatcap 64 Jan 31 23:43 2 -> /dev/pts/3 lr-x------. 1 flatcap flatcap 64 Jan 31 23:43 3 -> /usr/share/doc/
When running a long `diff -r` over folders, this simulates a "verbose" mode where you can see where diff is in the tree. Replace $file with the first part of the path being compared.
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.
commandlinefu.com 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.
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.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
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: