Re: [PATCH v2] settings: Resolve path if hostname is a sym-link
- From: Joel Holdsworth <joel holdsworth vcatechnology com>
- To: Thomas Haller <thaller redhat com>, networkmanager-list gnome org
- Subject: Re: [PATCH v2] settings: Resolve path if hostname is a sym-link
- Date: Wed, 27 Jan 2016 16:16:13 +0000
Thereby, it would also be interesting how you run NetworkManager with a
read-only /etc. Do you set keyfile.path configuration option?
Is the hostname thing your only remaining issue, or do you have other
issues NM and a read-only /etc? How does it work with handling
resolv.conf?
So at the moment we have the following setup:
- keyfile - not needed; at the moment we don't support any medium that
needs a keyfile
- /etc/resolv.conf - NetworkManager writes to
/run/NetworkManager/resolv.conf , and the onus has always been on the
integrator to create a sym-link from /etc/resolv.conf to /run
- /etc/NetworkManager/NetworkManager.conf - fixed file
- /etc/NetworkManager/system-connections/ - sym-linked to
/var/lib/NetworkManager/system-connections/
- /etc/hostname - sym-linked to /var/lib/hostname
...and that all works fine; apart from writing the hostname back through
the sym-link.
Like I say, I think this patch is fixing something real. If I did this...
# echo myhost > /etc/hostname
...with a sym-link, that would write through to the target of the
sym-link, rather than replacing it with a file. That's the behavior I
would expect.
Joel
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]