Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15228

Re: [PATCH] Fix \H: Use getaddrinfo to get full hostname

From Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups gnu.bash.bug
Subject Re: [PATCH] Fix \H: Use getaddrinfo to get full hostname
Date 2019-07-24 10:46 -0400
Message-ID <mailman.2139.1563979594.2688.bug-bash@gnu.org> (permalink)
References <20190724135835.110473-1-whissi@gentoo.org> <454afb04-c18a-1b82-d869-34539c194b3d@case.edu> <f1f2e8df-5921-b696-686b-de5aec362a25@gentoo.org> <20190724144629.GL1218@eeg.ccf.org>

Show all headers | View raw


On Wed, Jul 24, 2019 at 04:38:06PM +0200, Thomas Deutschmann wrote:
> Can you tell me more about your system and how you (your administrator)
> set up your system so that hostname will return FQDN?

It's common outside the Linux world.

# hostname
minea.eeg.ccf.org
# uname -a
HP-UX minea B.11.11 U 9000/785 4239047153 unlimited-user license

> I hope you are not talking about putting FQDN into a file which is
> expecting hostname only...

Yes, many people do precisely that.  They configure their systems
so the "hostname" command returns an FQDN, as I showed above.  (Not
my design, not my choice.)

This is what bash's \H vs. \h is for.  If your system's hostname
has dots in it, \h shows only the part up to the first dot (because
that's usually what you want in your prompt -- the shorter version),
and \H is available just in case you actually want the full version.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: [PATCH] Fix \H: Use getaddrinfo to get full hostname Greg Wooledge <wooledg@eeg.ccf.org> - 2019-07-24 10:46 -0400

csiph-web