After administering Unix or Unix-like servers, what tools (command-line preferably) do you feel you cannot live without?
Questions on Server Fault are expected to relate to server, networking, or related infrastructure administration within the scope defined by the community. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope. Read more about reopening questions here. If this question can be reworded to fit the rules in the help center, please edit the question.
locked by HopelessN00b Dec 5 '14 at 6:14
This question exists because it has historical significance, but it is not considered a good, on-topic question for this site so please do not use it as evidence that you can ask similar questions here. This question and its answers are frozen and cannot be changed. See the help center for guidance on writing a good question.
Read more about locked posts here.
GNU screen - essential when you're managing large numbers of systems and don't want to have a dozen terminal windows open.
Some I know that I cannot live without...
tee - allows simultaneous writing to STDOUT (standard output) and a file. Great for viewing information and logging it for later.
top - the task manager of UNIX, gives a great overview of the system.
tail -f - allows you to view appended data as a file grows, great for monitoring log files on a server.
grep - Global Regular Expression Print, great for searching the system for data in files.
df - reports disk usage of current filesystems.
du - reports disk usage of a certain file/directory.
less - needed to view man pages! also useful for viewing output of commands in an easily seekable manner.
vim/Emacs/nano/pico/ed - whatever your text editor of choice may be, self explanatory of why it's needed.
lsof to determine which processes are using a file or directory (useful when trying to figure out what is preventing a device from being umount'd)
netstat to determine which processes are using network connections (especially useful when trying to figure out which daemon is bound to a certain port)
Learn all the basic tools, but learn Perl.
Perl is ideal for manipulating text, and since un*x operators live on text files, pipes, input and output, Perl is a great fit.
The added bonus is Perl is cross platform and if you have to do some work on a windows box you have an easily installable (just drop a Perl directory on the server) language that you already know.
And on that train of thought, get Cygwin as well. If you are a un*x admin and have to work on a windows box (even your desktop) having ls, rm, grep, sed, tail etc save you a lot of time when switching OS's.
The forgotten grandfathers of modern systems scripting. I know Perl gets most of the love (along with Bash scripting, Python, Ruby, and [insert your favorite scripting language here]), and don't get me wrong, I love Perl. I make use of it almost daily.
But sed and awk should not be forgotten, overlooked, or ignored. For a lot of cases, sed and awk are the best tools for the job. Quick examples are command line filtering with sed, and quick and dirty log processing with awk. Both could be done in Perl, but will require more work and development time.
rsync, especially in concert with ssh. It allows simple efficient copying of files from host to host. How did we ever cope without ssh and rsync? :-)
- Test if TCP services are listening.
- Perform transactions against plaintext protocols such as SMTP.
- Quick insecure data transfers between machines.
- Telnet client emulation.
The network swiss army knife, as they say.
For quick scripts, automation, etc:
To connect to your *NIX server:
- Open SSH (Linux client)
- Putty (Windows client)
I use most of the tools already listed, but here's one no one has touched on yet:
Puppet - system for automating system administration tasks
A couple of handy tools I haven't seen mentioned yet:
ClusterSSH controls a number of xterm windows via a single graphical console window to allow commands to be interactively run on multiple servers over an ssh connection.
Gives you a great overview of system behaviour.
pv: Displays the progress of long operations that can be redirected. http://www.ivarch.com/programs/pv.shtml
Useful then you want to monitor something that is going to take ages, like copying/compressing a raw block device over the network (which is how I take paranoia backups of my 8Gb netbook before tinkering with anything major like tweaking with file system settings).
Also: I'll second votes for ssh, rsync, screen, htop and netcat as mentioned by people above - all of which are more important than pv but pv had not been mentioned yet. In fact pv is often a useful addition when piping stuff to or from to netcat.
ssh, Vim, htop, su, Python, ls, cd, screen, du, tar :)
tail -f is useful.
Some that haven't been mentioned before:
piping the output of tar to another utility, to tar running on the same box, or to tar running over SSH is my favorite old-school Unix move for moving files from one place to another.
This also gives you the Windows-style option of copying one folder to another and ending up with all of the files in the source and destination directory.
zsh as a shell
It is especially efficient with grml.org's extensions/setup.
iotop, is a top-like program to monitor I/O accesses to your disks.
Most of these tools are made much more powerful using Bash "programmable completion" - so you can tab-complete things like commandline options, or say the name of a package with "apt-get install". It will also limit what you tab-complete for relevant files - for example, "unzip" will only complete supported archive files.
It really is the mutts - if you have never tried it you probably just need to fiddle your .bashrc:
if [ -f /etc/bash_completion ]; then . /etc/bash_completion fi
Certainly this is true on Ubuntu and Debian. You may need to get the package on some Linux distributions.
Some additional answers can be found in this similar question
A few things overlooked I wanted to mention.
- vim -d split screen console diff that makes it very easy to see the differences in a file
- pdsh allows you to easily run a command over as many systems as you want either serial or parallel(I am a cluster admin. I can't function without it.)
- nmon is like top on crack. It gives you a great idea of what is going on on a system on a single screen. You can see disk I/O, network I/O CPU usage, and memory usage real time. At the very least a real fun thing to play with when profiling a system.
Oh, and I forgot to mention, when scripting, I believe you should always use Korn. I hate Korn(Not the band. I love the band:-P) but it's literally everywhere. You can take a script and move it between Solaris, AIX and Linux and not have to worry about whether or not the admin had the decency to install Bash.
One tool sometimes very handy is nohup. I use it to run scripts that last for a long time using remote SSH clients.
man - to read the man pages.
elinks - to check google, cause I sure as hell cant remember everything.
And attention to detail & tenacity, because without them I just waste time.
screen is a must, especially with a good .screenrc file. I have it configured to display visually which window I'm in and can move between them with Ctrl+Arrow. For a single ssh session and multiple shells, it is a life saver.
I love AWK as well as "for" on the command line.
Especially to build up a list of commands I want to run and then execute them all at once.