Wednesday, March 29, 2017

10 Tips on working fast in UNIX or Linux

10 UNIX Productivity tips
Have you ever amazed to see someone working very fast in UNIX, firing commands and doing things in mille seconds? Yes I have seen and I have always inspired to learn from those gems of guys. This article or tutorial or whatever you call it I have dedicated to share UNIX command practices I follow to work fast, quick or efficiently in UNIX. I work for financial services industry and my work involves development and support of online stock and futures trading application in Electronic trading, Derivatives etc. all our services runs of UNIX servers so its very important for me to work efficiently and quickly in Linux machine.

This article is in continuation of my earlier article Top 10 basic networking Commands in Unix and Top 10 most useful CVS command in Unix . If you have not read those you can see if you find them interesting and useful. In this UNIX command tutorial I am going to share my experience on how to work quick, fast and efficiently in UNIX.

10 UNIX and Linux Productivity Tips

UNIX and Linux Productivity TipsIf your server also resides in UNIX machine and your day 2 day work involves lots of searching and playing around UNIX commands. Below tips are of my years of experience in UNIX which I have summarized as 10 tips to work fast in UNIX :) What I am looking forward is to get some more tips from you guys to enhance my arsenal so please share how you work in UNIX, how you make most of powerful commands and shell utilities provided by UNIX?

Please share your experience by posting comments to make this post useful and get most of it and benefit from each others experience.

1) Use ! For executing last command

This has saved my 30% time on average. It always happens that you fire same UNIX command multiple times within a fraction of seconds, before knowing this trick I used to use up and down arrow for finding my command and then executing them which takes some of my time but after

Knowing this trick I just have to remember command name e.g. !ls will execute your last "ls -lrt" , !vim will open your last file without

Typing full commands. Use it and experience it , It definitely save loads of time and its also useful on shell other than bash where up and down arrow generally doesn't give you previous commands.

For example After doing ls –l stocks.txt if you want to open stocks.txt you can use vi !$ (last argument)

2) Use !! for executing last command

This is an extension of previous tip which is used to execute the very last command you have executed. Since it just involves two keystrokes and that too for same key it’s amazingly fast. This will also works on the shells in which up and down arrow don’t work.This is extremely useful if you are stopping or starting your trading application for debug purpose frequently

3) Use "CRTL+R" for repeating the last matching command

Best out of lot if you remember your last command executed sometime back and just want to find that command with same argument and execute. This is the tip you need to remember. just press "CRTL+R" and type words that you had in your last command and UNIX will find that command for you then just press enter.

All above three tips will save lot of your time if you execute commands frequently and percentage of repetition is quite high. for me

I have saved almost 50-60% time by following above three tips. let me know how it works for you guys.

4) Using history command for getting some of the most frequently used UNIX command

This is the first thing I learn when I started working on UNIX :) This is your most helpful command in UNIX or shell. In most of the

Cases there are certain command like starting, stopping, checking log files, making build or doing release. Which we need to execute very frequently and if you don't remember exact command no need to worry, just do history | grep "keyword" and you will get that command from

UNIX history. There are certain environment variable e.g. HISTSIZE which defines how many command UNIX history can store, so have it big

Enough to save your time and avoid referencing your command booklet now and then.

5) Using regular expression in grep and find.

grep and find is two best tools UNIX provide to us. almost everybody needs to search something in UNIX e.g. a file , a directory , certain words in file e.g. ERROR or Exception and if you know how to use grep and find with regular expression you will save lot of your time by typing less commands.

For example by knowing about egrep you can fire egrep "ERROR|Exception" *.xml instead of firing two grep command for finding ERROR and Exception individually.

6) Using pipe instead of firing two commands

Just shown above this nice and little tip I guess everybody knows :)

7) Using aliases and defining them in bash profile or bashrc file.

Have you seen some strange commands working in someone's machine and not yours, which might be aliases he would have setup in either his .bashrc or .profile file. Always do such kind of setup for commonly used command. There are lots of usage of .bashrc and .profile file but

One of the most important one is setting up aliases e.g. "l." which finds all hidden files. "ls" which includes all useful option e.g. -lrtH to show all relevant information.

8) Using pushd, popd , cd - , ~ for moving across directory.

Based on my experience navigation in UNIX shell takes almost 50% times of people and if you are going to write directory path every now and then just forget about working fast. so instead of typing full name use all above tips and make best use of pushd, popd, cd - and cd ~ command. cd - is best if your switching between two directory location in UNIX.

9) Minimize the key strokes or increase the speed of typing.

That I guess you know isn't it the less you type the more fast you work so make use of your last typed command, make use of tab in bash so that let the UNIX bash shell complete your command, use Ctrl+R if the last command you have typed is very long and you want to change just few lines.

10) Try to learn more commands and their options and usage this will reduce thinking time for a particular task and use ctrl+z and fg and bg to suspend a process. it saves almost 10% time if you are viewing multiple files or log files so instead of every now and then executing vim commands just do Ctrl+Z to suspend it and fg 1 or fg 2 to bring it on foreground.

I hope these examples, tips on UNIX command will help you to do more in less time and enhance your productivity and experience while working in UNIX. This list is by no means complete so please share how you working in UNIX and of course how fast are you working in UNIX?

Further Learning
Linux Command Line Basics
Linux Command Line Interface (CLI) Fundamentals
Learn Linux in 5 Days and Level Up Your Career

Related UNIX Command Tutorials
  • 10 examples of find command in UNIX (examples)
  • 10 examples of grep command in UNIX (examples)
  • 10 examples of date command in Linux (examples)
  • How to get IP address from hostname and vice-versa in Linux (command)
  • 10 examples of xargs command in Linux (examples)
  • 10 examples of tar command in UNIX (examples)
  • 10 examples of Vim in UNIX (examples)
  • How to create, update and delete soft link in UNIX (command)
  • 5 examples of sort command in Linux (examples)
  • 5 examples of kill command in Linux (examples)
  • 10 examples of chmod command in UNIX (examples)

Thanks for reading this article so far. If you like this article then please share with your friends and colleagues. If you have any questions or feedback then please drop a note.


arapidhs said...

$hexdump -C imagen2.jpg | grep " ff d9" :)))

Anonymous said...

good article. I learned some quick ways to increase my efficiency in unix. thanks Javin.

Javin @ Sort Command in Unix said...

Thanks Anonymous, good to know that you find this Unix command tips useful for increasing productivity.

ashok said...

also we have alias command for storing cmd which we are using usaully. try with alias command that is more fun

Javin @ grep command in unix said...

Completely agree ashok, alias is another way of working fast in Unix, Even I have lots of alias in my .bashrc file for frequent commands, or changing directory or location etc.

Suresh Mekala said...

Very useful tips Javin. One more tip I would like to add:

While working in UNIX/LINUX environment some times you need to investigate an issue while server/application is writing log statements into log file. In that situation I found "less" command is very useful.


Above command opens the file in read only mode and good thing is all search command(All egrep command options work here) which work in vim editor/egrep options are also available in 'less'. But one advantage of using less over vim is as I mentioned while we investigate the issue, application might have written some more statements into log file. so to see those new statements just press ctrl + f will open the same file as if you are tailing the log so you can see most recent statments in log file. Again pressing ctrl + f will bring back us to less mode where we can continue our further investigation.

In summary:



ctrl + f


'ctrl+ f' will bring back us to less mode.

Another variation of less is "less -I " will open the file in case insensitive mode where you can search not bothering about case while searching for words in you don't remember exact word.

I use this tip almost everyday at my job and hope its useful for others too.


Anonymous said...

another tips to working fast in Unix is use a bash script file to create shortcuts of frequently used unix command, directories and options.

Anonymous said...

Linux has lot of commands which makes easy for working on linux...
typing vimtutor in terminal will show us lot of commands.

Anonymous said...

You are a star............


Anonymous said...

One tips, which really helps me working with lots of UNIX boxes are storing logging information in Putty Connection Manager, it offers login macros, which can be really handy for storing username and password, especially if you have lot of servers to work on. From there, it just need one click to login and start working in UNIX shell.

Gaurav Khurana said...

I think you gave some of the best tricks that a person should utitlise and i am glad that i am doing most of them

Priya Chaney said...

It is wonderful article.. and very helpful!

Javin Paul said...

@Priya, thanks you like this UNIX tips. Please share with your friends. Cheers ..

vidya said...

Very useful article.
Just wanted to know, what does cd ~ do ?

Unknown said...

cd - moves backwards and forwards (toggles) between two directories

Javin Paul said...

@vidya, cd ~ takes you to home directory e.g /home/user , @unknown, yes cd - is a nice way to move between two directories, I use it a lot.

Jeff Pohlmeyer said...

cd with no arguments does the same thing as cd ~

never147 said...

Something that I find very useful is shortcuts to move the cursor on the command line. For example, Ctrl+e moves to the end of the line, Ctrl+a moves to the start of the line. You can also cut the command line to the start of the prompt with Ctrl+u or just cut the last word with Ctrl+was. The best thing then is you can paste the cut text back with Ctrl+y. So you construct parts of commands into new ones very quickly.

luca formaggia said...

Fine hints. Other great commends are find and locate, when you need to find where you have put that file...

Anyway, I do not agree much about aliasing commands on a permanent basis (i.e. by setting the alias in .bashrc) . It may be dangerous because eventually it let you wrongly believe that a command has a certain standard behaviour. And make mistakes when do you log into another computer. In particular, never ever alias 'rm' to 'rm -i' !

Manu said...

Thank u very much for share these tips :D its good to remind some of them.

Anonymous said...

Don't forget the tab key to auto complete directory, command or service names. Example: service php[tab] restart (service php-fpm restart, or could be php5-fpm, etc), cat /var/lo[tab]/au[tab]/au[tab] (cat /var/log/auth/auth.log) - saves tons of tim

Swapnil M said...

Great tios

I use this often as well to know if server or process is running and to know it's details

ps -elf | grep process

Post a Comment