summaryrefslogtreecommitdiff
path: root/doc/s6-nuke.html
blob: 10395063ea8274943e06f94303a24c817caeca6b (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
<html>
  <head>
    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
    <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
    <meta http-equiv="Content-Language" content="en" />
    <title>s6-portable-utils: the s6-nuke program</title>
    <meta name="Description" content="s6-portable-utils: the s6-nuke program" />
    <meta name="Keywords" content="s6-portable-utils command s6-nuke signal kill" />
    <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
  </head>
<body>

<p>
<a href="index.html">s6-portable-utils</a><br />
<a href="//skarnet.org/software/">Software</a><br />
<a href="//skarnet.org/">skarnet.org</a>
</p>

<h1> The <tt>s6-nuke</tt> program </h1>

<p>
 s6-nuke sends signals to every process it is allowed to send.
</p>

<h2> Interface </h2>

<pre>
     s6-nuke [ -h | -t | -k ]
</pre>

<ul>
 <li> Depending on the options it is given, s6-nuke sends signals to
all processes; depending on s6-nuke's rights, not all processes may
receive them. </li>
 <li> s6-nuke protects itself against the signals it sends (which
doesn't do much good against SIGKILL). If it survives the blast,
it exits 0. </li>
</ul>

<h2> Options </h2>

<ul>
 <li> <tt>-h</tt>&nbsp;: send a SIGHUP </li>
 <li> <tt>-t</tt>&nbsp;: send a SIGTERM then a SIGCONT </li>
 <li> <tt>-k</tt>&nbsp;: send a SIGKILL </li>
</ul>

<h2> Usage notes </h2>

<p>
 s6-nuke can be used during the shutdown procedure of a system, which is
described
<a href="//skarnet.org/software/s6/s6-svscan-1.html#stage3">here</a>.
</p>

</body>
</html>