chiark / gitweb /
man: use more markup in daemon(7)
authorZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Fri, 3 Oct 2014 21:44:23 +0000 (17:44 -0400)
committerZbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl>
Sat, 4 Oct 2014 00:42:09 +0000 (20:42 -0400)
man/daemon.xml

index a23a04794b2a5e1cee35fe46f73cae8682c0704f..99c75a7a18eb9b5d48452b012ef33100c9aae411 100644 (file)
                                 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
                                 init system. If log priorities are
                                 necessary, these can be encoded by
                                 prefixing individual log lines with
-                                strings like "&lt;4&gt;" (for log
+                                strings like <literal>&lt;4&gt;</literal> (for log
                                 priority 4 "WARNING" in the syslog
                                 priority scheme), following a similar
                                 style as the Linux kernel's
                         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