From 610158048a03f25be88a36cb7c81d11177a2c559 Mon Sep 17 00:00:00 2001

From: =?UTF-8?q?Zbigniew=20J=C4=99drzejewski-Szmek?= <zbyszek@in.waw.pl>

Date: Fri, 3 Oct 2014 17:44:23 -0400

Subject: [PATCH] man: use more markup in daemon(7)

---

 man/daemon.xml | 9 +++++----

 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/man/daemon.xml b/man/daemon.xml

index a23a04794b..99c75a7a18 100644

--- a/man/daemon.xml

+++ b/man/daemon.xml

@@ -85,13 +85,14 @@

                                 with a fallback of iterating from file

                                 descriptor 3 to the value returned by

                                 <function>getrlimit()</function> for

-                                RLIMIT_NOFILE.</para></listitem>

+                                <constant>RLIMIT_NOFILE</constant>.

+                                </para></listitem>

                                 <listitem><para>Reset all signal

                                 handlers to their default. This is

                                 best done by iterating through the

                                 available signals up to the limit of

-                                _NSIG and resetting them to

+                                <constant>_NSIG</constant> and resetting them to

                                 <constant>SIG_DFL</constant>.</para></listitem>

                                 <listitem><para>Reset the signal mask

@@ -330,7 +331,7 @@

                                 init system. If log priorities are

                                 necessary, these can be encoded by

                                 prefixing individual log lines with

-                                strings like "<4>" (for log

+                                strings like <literal><4></literal> (for log

                                 priority 4 "WARNING" in the syslog

                                 priority scheme), following a similar

                                 style as the Linux kernel's

@@ -610,7 +611,7 @@

                         on a network interface, because network

                         sockets shall be bound to the

                         address. However, an alternative to implement

-                        this is by utilizing the Linux IP_FREEBIND

+                        this is by utilizing the Linux <constant>IP_FREEBIND</constant>

                         socket option, as accessible via

                         <varname>FreeBind=yes</varname> in systemd

                         socket files (see