Here’s a cool trick for you folks…<\/p>\n
If you regularly I’m sure you already know that you can type a part of a filename on the command line, and have …and the tab key completes the word “ So now let’s apply this capability to So, if you happen to have all your servers\u00a0 in your local …and be very careful there to note the back-ticks and double-quotes.\u00a0 In case you are wondering, what this is doing is to take the second column of your hosts file and put them into a list for completion of any …then the rest of the long servername will be completed there on the line.\u00a0 Is that cool or what?<\/p>\n Alternately, if you happen to have the servernames listed in a textfile, or if you need to prefix your …and so on.\u00a0 This way, the tab completion will include your username prefix. And to utilize this particular file, you would enter something like this (of course, pointing to your particular server list, not mine):<\/p>\n …and again, be careful with the quotes and back-ticks.<\/p>\n I hope this makes your life easier folks, it sure has helped me… And if you haven’t figured it out already, this process applies to just about any program you want.\u00a0 And, you can actually use more precise functions instead of the command method I describe here, but that’s a lot more complex than I wanted to get into in this post.\u00a0 Make sure to check out the already-existing function files at Enjoy!<\/p>\n \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"ssh<\/code> to a set of servers in your server farm, but don’t like having to type out the full hostname on the command line (or can’t remember all the ip addresses), I’ve got a tip for you.<\/p>\nbash<\/code> complete the name.\u00a0 For instance, you would type:<\/p>\nvi \/etc\/hos[tab]<\/code><\/p>\nhost<\/code>” (pressing tab twice shows the remaining matching options that start with \/etc\/hosts<\/code>, including \/etc\/hosts<\/code>).\u00a0 But did you know that bash<\/code> completion can work for more things that just the filesystem?\u00a0 Well, you do now.<\/p>\nssh<\/code>, since this is something many of us commonly use.\u00a0 Normally if you are trying to ssh<\/code> to a server, you probably type something like this:<\/p>\nssh longservernamethatyoudontwanttotype<\/code><\/p>\n\/etc\/hosts<\/code> file, we can add them to the bash<\/code> shell’s tab completion capability with the following command:<\/p>\ncomplete -W \"`awk '{ print $2 }' \/etc\/hosts`\" ssh<\/code><\/p>\nssh<\/code> command.\u00a0 Of course, you could add this to a startup script or some such, but I’m not going into that here for the sake of brevity.\u00a0 Anyway, now if you type:<\/p>\nssh long[tab]<\/code><\/p>\nssh<\/code> connections with a username, you could create that server list file like this (with or without the username prefix, depending on how you wish to connect):<\/p>\njpavlov@abrams
\njpavlov@backus
\njpavlov@crowell<\/code><\/p>\ncomplete -W \"`cat \/home\/jpavlov\/serverlist.txt`\" ssh<\/code><\/p>\n\/etc\/bash_completion<\/code> and check out complete --help<\/code> for more details…<\/p>\n