Closed schloett closed 1 year ago
The downside is that you can't use the fully-qualified name anymore. I'm not against that, but we'll need to adapt other parts of the documentation, e.g. instead of
ssh -v $USERNAME@login.ikim.uk-essen.de
it's just
ssh -v $USERNAME@ikim
Could you do a text search for .ikim.uk-essen.de
across the docs?
Ah right, hadn't thought of that. Not being able to use the fully qualified name anymore would probably cause only more confusion... What about keeping both Host directives and duplicate the options? Could that cause another issue that I'm missing?
I don't mind if we delete the section with the fully qualified name. Since this is just a recommended setup to get started, there's merit in keeping it simple, so I would avoid duplication. I don't see any significant disadvantages in keeping short names only.
I adapted the rest of the page to short names only and checked all other pages for occurrences of fully qualified names (found none).
It seems that on some systems/version, the options for
Host g1-*.ikim.uk-essen.de c*.ikim.uk-essen.de slurmq.ikim.uk-essen.de
aren't applied after resolving the hostname viaHost g1-? c? c?? slurmq
. Hence I moved the insideHost g1-? c? c?? slurmq
and removed the rest => shorter config and advanced users will adapt it to their needs anyway.