From 524f3e5c9d1eb2fba3d0b65d1790018163ba0b20 Mon Sep 17 00:00:00 2001 From: =?utf8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= Date: Mon, 25 Jan 2016 17:56:42 -0500 Subject: [PATCH] man: fix references to a few external man pages Noticed in pull request #2067. --- man/resolved.conf.xml | 2 +- man/systemd-ask-password.xml | 4 ++-- man/systemd.nspawn.xml | 2 +- man/udev_device_new_from_syspath.xml | 4 ++-- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/man/resolved.conf.xml b/man/resolved.conf.xml index 3ab7fc4..09a192c 100644 --- a/man/resolved.conf.xml +++ b/man/resolved.conf.xml @@ -210,7 +210,7 @@ systemd-resolved.service8, systemd-networkd.service8, dnssec-trust-anchors.d5, - resolv.conf4 + resolv.conf4 diff --git a/man/systemd-ask-password.xml b/man/systemd-ask-password.xml index 6fb322e..2a4d243 100644 --- a/man/systemd-ask-password.xml +++ b/man/systemd-ask-password.xml @@ -149,7 +149,7 @@ possible to cache multiple passwords under the same keyname, in which case they will be stored as NUL-separated list of passwords. Use - keyctl1 + keyctl1 to access the cached key via the kernel keyring directly. Example: --keyname=cryptsetup @@ -209,7 +209,7 @@ systemd1, systemctl1, - keyctl1, + keyctl1, plymouth8, wall1 diff --git a/man/systemd.nspawn.xml b/man/systemd.nspawn.xml index e952688..f39e1ad 100644 --- a/man/systemd.nspawn.xml +++ b/man/systemd.nspawn.xml @@ -192,7 +192,7 @@ Takes a space-separated list of Linux process capabilities (see - capabilities7 + capabilities7 for details). The Capability= setting specifies additional capabilities to pass on top of the default set of capabilities. The diff --git a/man/udev_device_new_from_syspath.xml b/man/udev_device_new_from_syspath.xml index 11db1a0..c71356a 100644 --- a/man/udev_device_new_from_syspath.xml +++ b/man/udev_device_new_from_syspath.xml @@ -134,7 +134,7 @@ a uevent file. udev_device_new_from_devnum takes a device type, which can be b for block devices or c for character devices, as well as a devnum (see - makedev3). + makedev3). udev_device_new_from_subsystem_sysname looks up devices based on the provided subsystem and sysname (see udev_device_get_subsystem3 @@ -171,7 +171,7 @@ udev_device_new_from_environment creates a device from the current environment (see - environ7). + environ7). Each key-value pair is interpreted in the same way as if it was received in an uevent (see udev_monitor_receive_device3). -- 2.7.4