Yesterday I needed to change the syslog.conf on 96 servers. Offcourse I did write a script but security in our environment is the tightest you can think of so using sudo or su - interactively was not an option. I had to start the script by hand after logging in . Now I had some smart tricks on my sleeve so I finished the job within the hour. Perhaps you know some already, but I'll share them anyway - it could improve your workflow:

• Put putty in your path environment variable: This allows you to do <Windows-Key>-<r> and type 'putty <servername>'
• Copy the password in your windows buffer (you know, <Ctrl>-<c>) and insert it in the session using <Shift>-<Insert>
• Log in with elevated priviledges
• Start the script, which was on NFS in my case like: /vmfs/volumes/nfsdatastore/startscript.sh - BUT USE THE<tab>KEY:/vmf<tab>v<tab>n<tab>s<tab><enter>
• Log out using <Ctrl>-<d>, <Ctrl>-<d>!The first one logs you out from root, the second from the initial connection.
• Start the whole cycle again...

Awesome right? If you would like to know more cool tricks, check out this site . I like using:

• <Ctrl>-<l> to clear the screen
• <Ctrl>-<z> and command 'bg' to put the current job in the background, check status using command 'jobs'
• <Shift>-<PgUp> and <PgDn> to scroll throught the output (works on your ESX console too)
• <Ctrl>-<r> and start typing a part of a previous command, it will autofill
• 'history' to scroll through previous commands, execute one by using '!<number>'
• use !$, like 'cat <very_long_absolute_path_to_a_file_including_the_file>' and now I want to edit the file. Instead of using 'vi <very_long_absolute_path_to_a_file_including_the_file>' I use 'vi !$' where !$ means: use the last argument from the previous command
• Use 'cd ~' to go to your homedir. Use 'cd -' to switch back to your previous dir
• .... Can't think of anymore, but I'll post some more if you like them and I can think

Have fun consolling!