One of the things I love in Linux is that we can do a simple thing 100 different ways in it, like creating random passwords..

You can direct grep to search through one file or many. You can also pipe in output from some other utility so that you’ll see only the information that you want to see. And, the fact that grep uses regular expressions allows you to perform searches even when you only have an approximate idea of what you’re searching for.

It occurred to me that I was running 3 CPU-bound processes on the same machine and that the processes might be stepping on each other's toes. It's possible that if the server is running on core 4 one second and the producer is running there the next, the level 1 cache of that core could be ruined for the server the next time it ambles over there.

Another week and another top ten one-liners from commandlinefu explained.

Here's a list of 10 commands which may come handy when using the command line in Linux:

In this post I will collect all commands which SHOULD NEVER be executed in Linux. Any of them will cause data loss or corruption, can freeze or hang up running system. NEVER RUN THESE COMMANDS IN LINUX BOX CLI! Even if somebody advises you in forum/im to do it.

A shell is a program that acts as an intermediary between the user and the Linux kernel. The shell receives commands from the user through typed words and passes them into the kernel for processing. The kernel has the ability to communicate with hardware and gather resources like files and memory. The most common shell is bash.

htop - Undoubtedly the most famous of the top-like tools. It implements some extra options to the "top" command, like colors, ability to scroll horizontally and vertically, and a better interaction with the processes listed.

nethogs - network information, but instead of displaying the traffic by protocol, nethogs shows the bandwidth usage by process. Very interesting.