diff --git a/man/org.freedesktop.hostname1.xml b/man/org.freedesktop.hostname1.xml
index c852bed6de..f707b9080d 100644
--- a/man/org.freedesktop.hostname1.xml
+++ b/man/org.freedesktop.hostname1.xml
@@ -219,10 +219,6 @@ node /org/freedesktop/hostname1 {
it could not be auto-detected. Set this property to the empty string to reenable the automatic detection of
the chassis type from firmware information.
- A client that wants to change the local hostname for DHCP/mDNS should invoke
- SetHostname("newname", false)
as soon as the name is available and afterwards reset it via
- SetHostname("")
.
-
Note that systemd-hostnamed starts only on request and terminates after a
short idle period. This effectively means that PropertyChanged messages are not sent
out for changes made directly on the files (as in: administrator edits the files with vi). This is
@@ -244,33 +240,46 @@ node /org/freedesktop/hostname1 {
machine-info3
for that. For more information on these files and syscalls see the respective man pages.
- The user_interaction boolean parameters can be used to control whether PolicyKit
- should interactively ask the user for authentication credentials if required.
+
+ Security
- The PolicyKit action for SetHostname() is
- org.freedesktop.hostname1.set-hostname. For
- SetStaticHostname() and SetPrettyHostname() it is
- org.freedesktop.hostname1.set-static-hostname. For
- SetIconName() and SetChassis() it is
- org.freedesktop.hostname1.set-machine-info.
+ The interactive boolean parameters can be used to control whether PolicyKit
+ should interactively ask the user for authentication credentials if required.
- Here are three examples show how the pretty hostname and the icon name should be used:
+ The PolicyKit action for SetHostname() is
+ org.freedesktop.hostname1.set-hostname. For
+ SetStaticHostname() and SetPrettyHostname() it is
+ org.freedesktop.hostname1.set-static-hostname. For
+ SetIconName() and SetChassis() it is
+ org.freedesktop.hostname1.set-machine-info.
+
+
+
+
+ Recommendations
+
+ Here are three examples that show how the pretty hostname and the icon name should be used:
- When registering DNS-SD services: use the pretty hostname in the service name, and
- pass the icon name in the TXT data, if there is an icon name. Browsing clients can then show the server
- icon on each service. This is especially useful for WebDAV applications or UPnP media sharing.
+ When registering DNS-SD services: use the pretty hostname in the service name, and pass
+ the icon name in the TXT data, if there is an icon name. Browsing clients can then show the server icon
+ on each service. This is especially useful for WebDAV applications or UPnP media sharing.
Set the bluetooth name to the pretty hostname.
- When your file browser has a "Computer" icon, replace the name with the pretty hostname if set, and the icon with the icon name, if it is set.
+ When your file browser has a "Computer" icon, replace the name with the pretty hostname
+ if set, and the icon with the icon name, if it is set.
To properly handle name lookups with changing local hostnames without having to edit
- /etc/hosts, we recommend using systemd-hostnamed in
- combination with nss-myhostname3.
+ /etc/hosts, we recommend using systemd-hostnamed in combination
+ with nss-myhostname3.
+ A client that wants to change the local hostname for DHCP/mDNS should invoke
+ SetHostname("newname", false)
as soon as the name is available and afterwards reset it via
+ SetHostname("")
.
+
Here are some recommendations to follow when generating a static (internet) hostname from a pretty
name:
@@ -314,7 +323,7 @@ node /org/freedesktop/hostname1 {
Of course, an already valid internet hostname label you enter and pass through this
- conversion should stay unmodified, so that users have direct control of it, if they want -- by simply
+ conversion should stay unmodified, so that users have direct control of it, if they want — by simply
ignoring the fact that the pretty hostname is pretty and just edit it as if it was the normal internet
name.