<html>
    <head>
      <base href="https://bugs.freedesktop.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - RFE: WatchdogUnit= program"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=88192">88192</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>RFE: WatchdogUnit= program
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>systemd
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>unspecified
          </td>
        </tr>

        <tr>
          <th>Hardware</th>
          <td>Other
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>All
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>medium
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>general
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>rektide@voodoowarez.com
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>systemd-bugs@lists.freedesktop.org
          </td>
        </tr></table>
      <p>
        <div>
        <pre>The current watchdog mechanism requires modifying an existing application to
add in a new watchdog liveness signalling mechanism, and it leaves it to the
application to bake in any deliberate failure mechanisms it might needs (signal
to itself to stop sending "alive" beacons).

I'd like to see a mechanism introduced to enable health-monitor checks via
external units. In a decoupled form, an application doesn't necessarily have to
bake in custom systemd functionality. A webserver might reply as normal to a
/ping on loopback, and the healthcheck is just a curl -f unit test. A slightly
more sophisticated monitor unit might go 'curl -f -m 0.3 localhost/ping', and
so on to higher levels.

I'd love to see systemd better able to mechanize autonomous reflexes for the
processes under it's controls, and making more general purpose check systems
(fire watchdog when X fails) is the #1 thing I think of.

(I have an existing suggestion for inter-unit linkages in another form in,
<a href="https://www.libreoffice.org/bugzilla/show_bug.cgi?id=85709">https://www.libreoffice.org/bugzilla/show_bug.cgi?id=85709</a>
which suggests EnvironmentUnit=, a directive using one task's stdout to
supplements a starting unit's existing static Environment/EnvironmentFile/&c
values)</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are the QA Contact for the bug.</li>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>