On 27/07/14 02:25 PM, Joachim Breitner wrote:
> Hi,
> 
> 
> Am Sonntag, den 27.07.2014, 13:53 -0400 schrieb Daniel Dickinson:
>> Package: libnss-myhostname
>> Version: 0.3-6
>> Severity: serious
>>
>> Takes over names resolution of local host's name and causes apps that
>> need FQDN instead of just
>> hostname to fail (becuase myhostname fails to include a domain).
> 
> Can you explain the problems in more detai:
> What programs are affected?

I don't remember exactly which ones they were; there were a few and it
was a hard to debug problem.  I think one of them may have been amanda.
 I ditched libnss-hostname which I was installing myself sometime ago
because of this issue.

> What precisely do these program look up, what do they expect, and what
> do they get with libnss-myhostname?

They look up a hostname using glibc.  You can get the same result by
doing hostname --fqdn and observing that there is no domain part to
returned hostname. THIS IS BROKEN.  --fqdn should *always* have a domain
part.

> Did they previously work out-of-the box without libnss-myhostname and an
> unmodified /etc/hosts, or did you have to modify /etc/hosts (i.e. add
> the FQDN there)?

They worked out-of-the box without libnss-myhostname, with the DNS setup
I had.

> If so, what happens if you still add them to /etc/hosts?

It is actually the local  hostname that is the issue and I have actually
tried modifying /etc/hosts with <ip-address> <name>.<domain> <name>
however hostname --fqdn *still* returns <name> with NO <domain>.

libnss-hostname is BROKEN WRT to FQDN.

Regards,

Daniel
> 


-- 
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to