Your message dated Sun, 20 Sep 2015 17:05:26 +0200
with message-id <[email protected]>
and subject line Re: Bug#766182: systemd: incorrect dmesg message about missing
nss-myhostname
has caused the Debian Bug report #766182,
regarding systemd: incorrect dmesg message about missing nss-myhostname
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
766182: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766182
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: systemd
Version: 215-5+b1
Severity: minor
dmesg output gives:
systemd-hostnamed[3013]: Warning: nss-myhostname is not installed.
Changing the local hostname might make it unresolveable. Please
install nss-myhostname!
This is incorrect: nss-myhostname is not needed when there is a
/etc/hosts file. If installed, it makes some software, such as exim4,
fails to work correctly because of a clash between nss-myhostname
and usual /etc/hosts configuration (FQDN set up for IPv4 only).
See bug 756224, and in particular
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756224#114
for the explanation (in short, nss-myhostname adds IPv6 resolution,
but doesn't return the FQDN, while IPv4 resolution returns the FQDN
via /etc/hosts as expected).
This message should not be displayed when a /etc/hosts file is
present.
-- Package-specific info:
-- System Information:
Debian Release: jessie/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable'), (1,
'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=POSIX, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages systemd depends on:
ii acl 2.2.52-2
ii adduser 3.113+nmu3
ii initscripts 2.88dsf-53.4
ii libacl1 2.2.52-2
ii libaudit1 1:2.4-1
ii libblkid1 2.25.1-5
ii libc6 2.19-11
ii libcap2 1:2.24-6
ii libcap2-bin 1:2.24-6
ii libcryptsetup4 2:1.6.6-2
ii libgcrypt20 1.6.2-4
ii libkmod2 18-3
ii liblzma5 5.1.1alpha+20120614-2
ii libpam0g 1.1.8-3.1
ii libselinux1 2.3-2
ii libsystemd0 215-5+b1
ii sysv-rc 2.88dsf-53.4
ii udev 215-5+b1
ii util-linux 2.25.1-5
Versions of packages systemd recommends:
ii dbus 1.8.8-2
ii libpam-systemd 215-5+b1
Versions of packages systemd suggests:
pn systemd-ui <none>
-- Configuration Files:
/etc/pam.d/systemd-user [Errno 2] No such file or directory:
u'/etc/pam.d/systemd-user'
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 217-1
Hello Vincent,
Vincent Lefevre [2015-09-11 9:37 +0200]:
> On 2015-09-11 08:32:41 +0200, Michael Biebl wrote:
> > The presence of /etc/hosts does not mean that your local hostname is
> > configured there. It can easily get out of sync from what's configured
> > in /etc/hostname.
>
> I disagree: you could also check whether the local hostname is
> configured there. Anyway, I no longer get this warning message
> (though libnss-myhostname is still not installed on this machine),
> so everything is now OK. The disappearance of the warning message
> occurred between 2015-05-12 and 2015-06-28.
Indeed, it was dropped upstream in commit 1e5b1aaa (Fri Jul 11
15:38:17 2014), thus this warning does not exist any more with systemd
216 and newer.
Martin
--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
--- End Message ---
