A System and Service Manager
0a51c274d6
Sadly, this does not work. It seems NM queries resolved for the local IP address and gets "linux" and sets that as the transient hostname. Resolved has a "fallback hostname" (that will now again be "fedora"), but it also has a fallback fallback hostname that is "linux" that it used in reverse dns queries and such. NM gets the "linux" name and tells hostnamed to use that as the transient hostname. I don't think this is an improvement, since "linux" is a problematic as "fedora". So let's revert this for now to avoid pointless churn, until we figure out a real solution. |
||
---|---|---|
tests | ||
.gitignore | ||
20-grubby.install | ||
20-yama-ptrace.conf | ||
0001-test-path-util-do-not-fail-if-the-fd_is_mount_point-.patch | ||
0001-test-path-util-ignore-test-failure.patch | ||
f58b96d3e8d1cb0dd3666bc74fa673918b586612.patch | ||
inittab | ||
libsystemd-shared.abignore | ||
macros.sysusers | ||
purge-nobody-user | ||
sources | ||
split-files.py | ||
sysctl.conf.README | ||
systemd-journal-gatewayd.xml | ||
systemd-journal-remote.xml | ||
systemd-udev-trigger-no-reload.conf | ||
systemd-user | ||
systemd.rpmlintrc | ||
systemd.spec | ||
sysusers.attr | ||
sysusers.generate-pre.sh | ||
sysusers.prov | ||
triggers.systemd | ||
use-bfq-scheduler.patch | ||
yum-protect-systemd.conf |