If you need to fix a randomly failing test (race condition), you need to run it until you get that hard-to-reproduce failure. Show Sample Output
Run this within a steady screen session. You can get the approximate time when the remote server went down or other abnormal behavior.
This will, for an application that has already been removed but had its configuration left behind, purge that configuration from the system. To test it out first, you can remove the last -y, and it will show you what it will purge without actually doing it. I mean it never hurts to check first, "just in case." ;)
Are the two strings anagrams of one another? sed splits up the strings into one character per line the result is sorted cmp compares the results Note: This is not pretty. I just wanted to see if I could do it in bash. Note: It uses fewer characters than the perl version :-)
for small output only example usage: jobs -l |col1 72
Found this one little more for me. This one removes the perl dependency (from command 2535). Source for command : http://www.earthinfo.org/linux-disk-usage-sorted-by-size-and-human-readable/ Show Sample Output
Terminal is part of XFCE Desktop. This will open a tab for every node that we pass in the command line. In a single line we'll connect to nodes of our server farm.
tail would be considered dull, but pair this with being able to push out unix commands over ARD, and life gets easier. (Same can be said for my TimeMachine scrape command, http://xrl.us/begrzb) Show Sample Output
find . -maxdepth 1 -iname ".*" | awk 'NR >= 2' Can be used to list only dotfiles without . nor .. Show Sample Output
Very similar but no use of `tr` for function liner() { local num_lines=${1:-42} local line=$(printf %${num_lines}s) echo ${line// /#} }
You can use this in shell scripts to show which commands are actually run. Just prepend every "critical line" with "v˽". $TMP=/tmp echo "Let me create a directory for you" v mkdir $TMP/new In scripts this can be more useful than "set -x", because that can be very verbose with variable assignments etc. Another nice use is if you prepend every "critical" command with "v", then you can test your script by commenting out the actual execution. Show Sample Output
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: