Monthly Archives: February 2012

  For system and network administrators or other users who frequently deal with sessions on multiple machines, SSH ends up being one of the most oft-used Unix tools. It usually works so well that until you use it for something slightly more complex than starting a terminal session on a remote machine, you tend to use it fairly automatically. However, the ~/.ssh/config file bears mentioning for a few ways it can make using the ssh a client a little easier. Abbreviating hostnames If you often have to SSH into a machine with a long host and/or network name, it can get irritating to type it every time. For example, consider the following command: $ ssh server42371.some.long.hostname.for.a.server.com If you interact with the server42371 machine a lot, you could include a stanza like this in your ~/.ssh/config: Host server42371 HostName server43271.some.long.
Read More...