When called with -s, -l, -a, etc. hostname looks up the resulting names
using the resolver (as mentioned in the man page)
Thus if you change the hostname of the system without adding the new
name and IP to /etc/hosts, hostname will fail. This is quite normal.
This is why the installer always ens
Actually, you have quite enough to figure this out. From my
description, and the account of comment #3 you know:
1. hostname expects a specific binding to the local hostname in /etc/hosts
2. it is not in /etc/hosts by default, forcing users to add it manually to
resolve the issue.
3. you prob
We'd like to figure out what's causing this bug for you, but we haven't
heard back from you in a while. Could you please provide the requested
information? Thanks!
--
hostname bug: does not parse command line options properly
https://bugs.launchpad.net/bugs/253100
You received this bug notificati
I have just encounter the same issue.
I resolved it by adding the ip of eth0 to the /etc/hosts file.
so a hosts file of:
127.0.0.1 server-15.neontribe.co.uk localhost
127.0.1.1 debian
caused the described error exactly
and a hosts file of:
127.0.0.1 server-15.neontribe.co.uk lo
Thank you for reporting this bug. Please add your ubuntu version and the
shell you are using. I tried it with bash and dash and cannot reproduce
your bug.
** Changed in: hostname (Ubuntu)
Status: New => Incomplete
--
hostname bug: does not parse command line options properly
https://bugs.
Thank you for taking the time to report this bug and helping to make Ubuntu
better. This bug did not have a package associated with it, which is important
for ensuring that it gets looked at by the proper developers. You can learn
more about finding the right package at [WWW]
https://wiki.ubunt
