Search in all html files and remove the lines that 'String' is found.

Find and kill multiple instances of a process with one simple command.

Loads your CPU, run a instance for each CPU/CORE.

use manpages, they give you "ultimate commands"

"ls -SshF --color" list by filesize (biggest at the top)

"ls -SshFr --color" list by filesize in reverse order (biggest at the bottom)

If curl isn't available, use lynx.

use xdg-open without looking at error messages

examples msg:

(nautilus:3955): Gtk-WARNING **: Theme parsing error: Notebook.css:21:15: Junk at end of value

Replace D drive with mounted ISO virtual drive and Replace E with your USB drive letter.

avoid rm to be recursive until you complete the command: put the -rf at the end!

Useful for situations where you have word lists or dictionaries that range from hundreds of megabytes to several gigabytes in size. Replace file.lst with your wordlist, replace 50000 with however many lines you want the resulting list to be in total. The result will be redirected to output.txt in the current working directory. It may be helpful to run wc -l file.lst to find out how many lines the word list is first, then divide that in half to figure out what value to put for the head -n part of the command.

Good for finding outdated timthumb.php scripts which need to be updated, anything over 2.0 should be secure, below that timthimb is vulnerable and can be used to compromise your website.

"play" is part of "SoX"

SoX - Sound eXchange, the Swiss Army knife of audio manipulation.

For details, see: man sox

biggest->small directories, then biggest->smallest files

Taken from http://www.earthinfo.org/linux-disk-usage-sorted-by-size-and-human-readable/

It's useful mostly for your custom scripts, which running on specific host and tired on ssh'ing every time when you need one simple command (i use it for update remote apt repository, when new package have to be downloaded from another host).

Don't forget to set up authorization by keys, for maximum comfort.

If you need to fix a randomly failing test (race condition), you need to run it until you get that hard-to-reproduce failure.

Run this within a steady screen session.

You can get the approximate time when the remote server went down or other abnormal behavior.