From 80ec1decc49c72efec2a8b87c06245c92c0ab807 Mon Sep 17 00:00:00 2001 From: Michael Biebl Date: Thu, 11 Feb 2021 18:11:46 +0100 Subject: New upstream version 1.29.90 --- docs/api/html/settings-hostname.html | 89 ++++++++++++++++++++++++++++++++++++ 1 file changed, 89 insertions(+) create mode 100644 docs/api/html/settings-hostname.html (limited to 'docs/api/html/settings-hostname.html') diff --git a/docs/api/html/settings-hostname.html b/docs/api/html/settings-hostname.html new file mode 100644 index 00000000..0a4eddcd --- /dev/null +++ b/docs/api/html/settings-hostname.html @@ -0,0 +1,89 @@ + + + + +hostname: NetworkManager Reference Manual + + + + + + + + + + + + + + + + +
+
+
+ + +
+

hostname

+

hostname — Hostname settings

+
+
+

+ Properties +

+
+

Table 93. 

+
++++++ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
Key NameValue TypeDefault ValueValue Description
from-dhcp
NMTernary (int32)
Whether the system hostname can be determined from DHCP on this connection. When set to NM_TERNARY_DEFAULT (-1), 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 (1).
from-dns-lookup
NMTernary (int32)
Whether the system hostname can be determined from reverse DNS lookup of addresses on this device. When set to NM_TERNARY_DEFAULT (-1), 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 (1).
only-from-default
NMTernary (int32)
If set to NM_TERNARY_TRUE (1), NetworkManager attempts to get the hostname via DHCPv4/DHCPv6 or reverse DNS lookup on this device only when the device has the default route for the given address family (IPv4/IPv6). If set to NM_TERNARY_FALSE (0), the hostname can be set from this device even if it doesn't have the default route. When set to NM_TERNARY_DEFAULT (-1), 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_FALSE (0).
priority
int32
0
The relative priority of this connection to determine the system hostname. A lower numerical value is better (higher priority).  A connection with higher priority is considered before connections with lower priority. If the value is zero, it can be overridden by a global value from NetworkManager configuration. If the property doesn't have a value in the global configuration, the value is assumed to be 100. Negative values have the special effect of excluding other connections with a greater numerical priority value; so in presence of at least one negative priority, only connections with the lowest priority value will be used to determine the hostname.

+

+


+

+

+

+
Generated by GTK-Doc V1.33.1

+
+
\ No newline at end of file
-- 
cgit 1.3.0-6-gf8a5