diff --git a/man/systemd.system-credentials.xml b/man/systemd.system-credentials.xml
index 5be4ddfe59..62f86d1254 100644
--- a/man/systemd.system-credentials.xml
+++ b/man/systemd.system-credentials.xml
@@ -201,19 +201,13 @@
vmm.notify_socket
- Contains a AF_VSOCK or AF_UNIX address where to
- send a READY=1 notification datagram when the system has finished booting. See
- sd_notify3 for
- more information. Note that in case the hypervisor does not support SOCK_DGRAM
- over AF_VSOCK, SOCK_SEQPACKET will be tried instead. The
- credential payload for AF_VSOCK should be in the form
- vsock:CID:PORT.
-
- This feature is useful for hypervisors/VMMs or other processes on the host to receive a
- notification via VSOCK when a virtual machine has finished booting.
+ Configures an
+ sd_notify3
+ compatible AF_VSOCK socket the service manager will report status information,
+ ready notification and exit status on. For details see
+ systemd1.
-
diff --git a/man/systemd.xml b/man/systemd.xml
index f1e0256e05..3ceac5f919 100644
--- a/man/systemd.xml
+++ b/man/systemd.xml
@@ -1048,6 +1048,30 @@
kernel-command-line7.
+
+ System credentials
+
+ The service manager when run as PID 1 reads the following system credentials:
+
+
+
+ vmm.notify_socket
+
+ Contains a AF_VSOCK or AF_UNIX address where to
+ send a READY=1 notification datagram when the system has finished booting. See
+ sd_notify3 for
+ more information. Note that in case the hypervisor does not support SOCK_DGRAM
+ over AF_VSOCK, SOCK_SEQPACKET will be tried instead. The
+ credential payload for AF_VSOCK should be in the form
+ vsock:CID:PORT.
+
+ This feature is useful for hypervisors/VMMs or other processes on the host to receive a
+ notification via VSOCK when a virtual machine has finished booting.
+
+
+
+
+
Options