hostnamed should not print warning about nss-myhostname
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| systemd (Debian) |
New
|
Undecided
|
Unassigned | |
| systemd (Ubuntu) |
Undecided
|
Unassigned |
Bug Description
Currently hostnamed prints the following error in syslog:
systemd-
Since nss-myhostname was rejected as being the right approach in https:/
Can we please patch this warning out to prevent users from thinking something is wrong on their system and leading them to install libnss-myhostname?
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: systemd-services 204-5ubuntu10
ProcVersionSign
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
CurrentDesktop: Unity
Date: Fri Feb 7 12:12:20 2014
InstallationDate: Installed on 2013-11-26 (72 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
SourcePackage: systemd
UpgradeStatus: Upgraded to trusty on 2014-01-17 (20 days ago)
Marc Deslauriers (mdeslaur) wrote : | #1 |
Josh (majik) wrote : | #3 |
Problem continues to exist on 14.10.
Spectrumknight (spectrumknight) wrote : | #4 |
still having this awkward warning...
Marcus (elect-tech) wrote : | #5 |
It is still affecting 14.04LTS. Is this opening any security holes?
Nick Demou (ndemou) wrote : | #6 |
This is _not_ a duplicate of bug #1162475 (titled "Changing hostname doesn't update /etc/hosts")
tags: | added: i386 utopic |
Martin Wildam (mwildam) wrote : | #7 |
Ubuntu 14.04 with latest patchlevel - I still notice that message and indeed thought, something is rotten.
Status changed to 'Confirmed' because the bug affects multiple users.