summaryrefslogtreecommitdiff
path: root/libnm-core/nm-setting-hostname.c
diff options
context:
space:
mode:
authorBeniamino Galvani <bgalvani@redhat.com>2021-01-15 09:50:36 +0100
committerBeniamino Galvani <bgalvani@redhat.com>2021-01-18 16:29:55 +0100
commit92c494f2904c981842192d3eea7b74501c1fda0a (patch)
treeed1845809b1471a956fab62d2add130fae434114 /libnm-core/nm-setting-hostname.c
parentaf55a86a821e5f433099d3647147d7e49b68352c (diff)
downloadNetworkManager-bg/hostname-from-any.tar.gz
all: change default value of hostname.only-from-default to falsebg/hostname-from-any
Currently, is retrieved by default only from the device with the default route. This is done so that in presence of multiple connections the choice is deterministic. However, this limitation seems confusing for users, that expect to get an hostname even for non-default devices. Change the default and allow any device to obtain the hostname. Note that when there is a default route, NM still prefers that device and so the behavior doesn't change. The only change in behavior is that when there is no default route and the machine doesn't have a static hostname, NM will try to get hostname from DHCP or reverse DNS. https://bugzilla.redhat.com/show_bug.cgi?id=1766944
Diffstat (limited to 'libnm-core/nm-setting-hostname.c')
-rw-r--r--libnm-core/nm-setting-hostname.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/libnm-core/nm-setting-hostname.c b/libnm-core/nm-setting-hostname.c
index f3ed1cafac..fa781b1fbb 100644
--- a/libnm-core/nm-setting-hostname.c
+++ b/libnm-core/nm-setting-hostname.c
@@ -312,7 +312,7 @@ nm_setting_hostname_class_init(NMSettingHostnameClass *klass)
*
* When set to %NM_TERNARY_DEFAULT, the value from global configuration
* is used. If the property doesn't have a value in the global
- * configuration, NetworkManager assumes the value to be %NM_TERNARY_TRUE.
+ * configuration, NetworkManager assumes the value to be %NM_TERNARY_FALSE.
*
* Since: 1.30
**/