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
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
|
<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: the s6-svwait program</title>
<meta name="Description" content="s6: the s6-svwait program" />
<meta name="Keywords" content="s6 command s6-svwait notification service waiting" />
<!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
</head>
<body>
<p>
<a href="index.html">s6</a><br />
<a href="//skarnet.org/software/">Software</a><br />
<a href="//skarnet.org/">skarnet.org</a>
</p>
<h1> The s6-svwait program </h1>
<p>
s6-svwait blocks until a collection of supervised services goes up, or down.
</p>
<p>
s6-svwait only waits for notifications; it never polls.
</p>
<h2> Interface </h2>
<pre>
s6-svwait [ -U | -u | -D | -d ] [ -a | -o ] [ -t <em>timeout</em> ] <em>servicedir...</em>
</pre>
<p>
s6-svwait monitors one or more <a href="servicedir.html">service
directories</a> given as its arguments, waiting for a state (ready, up or down) to
happen.
</p>
<h2> Exit codes </h2>
<ul>
<li> 0: success, the wanted state has been reached </li>
<li> 99: timed out </li>
<li> 100: wrong usage </li>
<li> 102: the <a href="s6-supervise.html">s6-supervise</a> process monitoring the service died </li>
<li> 111: system call failed </li>
<li> <em>n</em>: services were expected to come up, but <em>n</em> of them
reported permanent failure </li>
</ul>
<h2> Options </h2>
<ul>
<li> <tt>-u</tt> : up. s6-svwait will wait until the services are up, as
reported by s6-supervise.
This is the default; it is not reliable, but it does not depend on specific
support in the service programs. See <a href="notifywhenup.html">this page</a>
for details. </li>
<li> <tt>-U</tt> : really up. s6-svwait will wait until the services are
up <em>and</em> ready as reported by the services themselves. This requires
specific support in the service programs, and the use of the
<tt>notification-fd</tt> file in the
<a href="servicedir.html">service directory</a>.
See the explanation on <a href="notifywhenup.html">this page</a>. </li>
<li> <tt>-d</tt> : down. s6-svwait will wait until the services are down. </li>
<li> <tt>-D</tt> : really down. s6-svwait will wait until the
services are down and the cleanup scripts in
<tt><em>servicedir</em>/finish</tt>
for every <em>servicedir</em>
have finished executing (or have timed out and been killed). </li>
<li> <tt>-o</tt> : or. s6-svwait will wait until <em>one</em> of the
given services comes up or down. </li>
<li> <tt>-a</tt> : and. s6-svwait will wait until <em>all</em> of the
given services come up or down. This is the default. </li>
<li> <tt>-t <em>timeout</em></tt> : if the requested events have not
happened after <em>timeout</em> milliseconds, s6-svwait will print a message
to stderr and exit 99. By default, <em>timeout</em> is 0, which means no time
limit. </li>
</ul>
<h2> Notes </h2>
<ul>
<li> s6-svwait should be given one or more <em>service directories</em> as
arguments, not a <em>scan directory</em>. If you need to wait for a whole
scan directory, give all its contents as arguments to s6-svwait. </li>
<li> s6-svwait will only work on service directories that are already
active, i.e. have a <a href="s6-supervise.html">s6-supervise</a> process
running on them. It will not work on a service directory where
s6-supervise has not been started yet. </li>
</ul>
<h2> Internals </h2>
<p>
s6-svwait spawns a <a href="libs6/s6-ftrigrd.html">s6-ftrigrd</a> child to
listen to notifications sent by <a href="s6-supervise.html">s6-supervise</a>.
It also checks <tt>supervise/status</tt> files to get the current service
states, so it is immune to race conditions.
</p>
</body>
</html>
|
