documentation: add description for watchdog device path
authorEdward A. James <eajames@us.ibm.com>
Fri, 8 Dec 2017 17:27:01 +0000 (11:27 -0600)
committerEdward A. James <eajames@us.ibm.com>
Fri, 8 Dec 2017 17:27:01 +0000 (11:27 -0600)
Document the command line parameter and the system configuration file
setting.

man/kernel-command-line.xml
man/systemd-system.conf.xml

index 1864895..422c060 100644 (file)
       </varlistentry>
 
       <varlistentry>
+        <term><varname>systemd.watchdog_device=</varname></term>
+
+        <listitem>
+          <para>Overwrites the watchdog device path <varname>WatchdogDevice=</varname>. For details, see
+          <citerefentry><refentrytitle>systemd-system.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>.</para>
+        </listitem>
+      </varlistentry>
+
+      <varlistentry>
         <term><varname>modules_load=</varname></term>
         <term><varname>rd.modules_load=</varname></term>
 
index 4371581..08f6c91 100644 (file)
         <literal>d</literal>, <literal>w</literal>). If
         <varname>RuntimeWatchdogSec=</varname> is set to a non-zero
         value, the watchdog hardware
-        (<filename>/dev/watchdog</filename>) will be programmed to
-        automatically reboot the system if it is not contacted within
+        (<filename>/dev/watchdog</filename> or the path specified with
+        <varname>WatchdogDevice=</varname> or the kernel option
+        <varname>systemd.watchdog-device=</varname>) will be programmed
+        to automatically reboot the system if it is not contacted within
         the specified timeout interval. The system manager will ensure
         to contact it at least once in half the specified timeout
         interval. This feature requires a hardware watchdog device to
       </varlistentry>
 
       <varlistentry>
+        <term><varname>WatchdogDevice=</varname></term>
+
+        <listitem><para>Configure the hardware watchdog device that the
+        runtime and shutdown watchdog timers will open and use. Defaults
+        to <filename>/dev/watchdog</filename>. This setting has no
+        effect if a hardware watchdog is not available.</para></listitem>
+      </varlistentry>
+
+      <varlistentry>
         <term><varname>CapabilityBoundingSet=</varname></term>
 
         <listitem><para>Controls which capabilities to include in the