Posts

Showing posts from June, 2013

How to find out which process is listening upon a port?

To discover the process name, ID (pid), and other details you need to run: lsof -i : port So to see which process is listening upon port 80 we can run: root@mystery:~# lsof -i :80 This gives us the following output: COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME apache2 10437 root 3u IPv6 22890556 TCP *:www (LISTEN) apache2 10438 www-data 3u IPv6 22890556 TCP *:www (LISTEN) apache2 10439 www-data 3u IPv6 22890556 TCP *:www (LISTEN) apache2 10440 www-data 3u IPv6 22890556 TCP *:www (LISTEN) apache2 10441 www-data 3u IPv6 22890556 TCP *:www (LISTEN) apache2 10442 www-data 3u IPv6 22890556 TCP *:www (LISTEN) apache2 25966 www-data 3u IPv6 22890556 TCP *:www (LISTEN) apache2 25968 www-data 3u IPv6 22890556 TCP *:www (LISTEN) Here you can see the command running ( apache2 ), the username it is running as www-data , and some other details. Similarly we can see which process is bound to

How To Autocomplete Commands Preceded By 'sudo'

When writing a command in the terminal, you can autocomplete it by pressing the TAB key. Example: type "nau" in the terminal and press TAB -> "nautilus" should show up (if you have Nautilus installed, obviously). However, the autocomplete doesn't work if you are trying to run a command with "sudo". For example, typing "sudo nau" and then pressing the TAB key will not autocomplete the command to "sudo nautilus". Here is how to get autocomplete to work in the Terminal while using "sudo". Simply open the ".bashrc" hidden file from your home folder. If you use GNOME, paste this in a terminal to open it: sudo gedit ~/.bashrc Then paste this at the bottom of the file: if [ "$PS1" ]; then complete -cf sudo fi Then type this in a terminal to reload: bash Now try the example in the beginning of the file "sudo nau" and press TAB. It should now work. found at  http://www.webupd8.org/20

How do I change bash history completion to complete what's already on the line?

edit:   # ~/.inputrc "\e[A": history-search-backward "\e[B": history-search-forward or equivalently,   # ~/.bashrc bind '"\e[A": history-search-backward' bind '"\e[B": history-search-forward'   Normally, Up and Down are bound to the Readline functions previous-history and next-history respectively. I prefer to bind PgUp/PgDn to these functions, instead of displacing the normal operation of Up/Down.   # ~/.inputrc "\e[5~": history-search-backward "\e[6~": history-search-forward After you modify ~/.inputrc , restart your shell or use Ctrl + X , Ctrl + R to tell it to re-read ~/.inputrc . found at  http://stackoverflow.com/questions/1030182/how-do-i-change-bash-history-completion-to-complete-whats-already-on-the-line