s6

Mirror/fork of https://skarnet.org/software/s6/
git clone https://ccx.te2000.cz/git/s6
Log | Files | Refs | README | LICENSE

s6-svdt-clear.html (1753B)


      1 <html>
      2   <head>
      3     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
      4     <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
      5     <meta http-equiv="Content-Language" content="en" />
      6     <title>s6: the s6-svdt-clear program</title>
      7     <meta name="Description" content="s6: the s6-svdt-clear program" />
      8     <meta name="Keywords" content="s6 command s6-svdt-clear servicedir death tally clearing process supervision s6-supervise" />
      9     <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
     10   </head>
     11 <body>
     12 
     13 <p>
     14 <a href="index.html">s6</a><br />
     15 <a href="//skarnet.org/software/">Software</a><br />
     16 <a href="//skarnet.org/">skarnet.org</a>
     17 </p>
     18 
     19 <h1> The <tt>s6-svdt-clear</tt> program </h1>
     20 
     21 <p>
     22 <tt>s6-svdt-clear</tt> clears the recorded death tally of a service.
     23 </p>
     24 
     25 <h2> Interface </h2>
     26 
     27 <pre>
     28      s6-svdt-clear <em>servicedir</em>
     29 </pre>
     30 
     31 <p>
     32  s6-svdt-clear clears the recorded death tally of the service being
     33 currently supervised at the <em>servicedir</em>
     34 <a href="servicedir.html">service directory</a>.
     35 </p>
     36 
     37 <ul>
     38  <li> 0: success </li>
     39  <li> 100: wrong usage </li>
     40  <li> 111: system call failed </li>
     41 </ul>
     42 
     43 <h2> Notes </h2>
     44 
     45 <ul>
     46  <li> Use of <tt>s6-svdt-clear</tt> impacts the listings obtained
     47 by the <a href="s6-svdt.html">s6-svdt</a> command. </li>
     48  <li> It also impacts the behaviour of the
     49 <a href="s6-permafailon.html">s6-permafailon</a> command. This is
     50 the main reason to use <tt>s6-svdt-clear</tt>: once a service has
     51 failed permanently due to an excessive number of deaths in a given
     52 time, it can be useful to erase that record of deaths before
     53 starting the service again, in order to avoid permanently failing
     54 again too fast. </li>
     55 </ul>
     56 
     57 </body>
     58 </html>