Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the '(Rewrite) Another way to create quick-access SSH shortcuts' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
(Rewrite) Another way to create quick-access SSH shortcuts
Authored by: Skurfer on Oct 19, '06 07:47:43AM

That might be useful for a larger audience, so thanks for the additions. In my particular case, I had my reasons for the way it was.

  1. I realize that the $access parameter seems misused in the stripped down version of the script I published. In my version of the script, the "type of access" is more than just a different username. It tells me "How do I get root access to this machine?" Some machines I access using ssh -l root, some using pbrun (PowerBroker), and some using pmrun (UPM).
  2. As for access under another username (or port), I think ~/.ssh/config is a more appropriate location for that. Specifying alternate settings in the .term file will only work if you open that .term file. By putting it in your ssh config, it will work with ssh from the command line and when you open a .term file. Of course, this doesn't account for situations where you have more than one (non-root) account on a machine. I should also mention that I have an account with the same name on almost every machine, so the usernames specified in ~/.ssh/config are rare (2 machines out of 45).
  3. I considered adding other metadata to the format of .hosts, but I wanted to keep it simple because its "real" purpose (or at least it's original purpose) was to enable tab completion on the command-line and I've had it in that format for years. And an even bigger factor in my decision to keep the format simple: I realized that most or all of the metadata I would have added is already available in an LDAP database we use in my office. Obviously, that won't be the case for most people.


[ Reply to This | # ]