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
|
Example sets of service definition directories.
demo:
It is a manually constructed set of services, separated
into two stores, meant to be used with the repo commands
of s6-rc, or with the s6-frontend package, so that users
can test the commands in a sandbox.
demo/0 and demo/1 should be the stores, hosting the service definitions.
Uppercase means the service is a longrun. Lowercase means the
service is a oneshot.
Services named E*|e* are essential.
Services named R*|r* are recommended, i.e. they should appear as
"active" rather than "usable" by default.
Services named N*|n* are only "usable" by default.
The number identifies the service.
Foo-log means the service is a logger for Foo.
Services that don't follow the format are bundles.
source-router:
It is a real life example, used for the configuration of
a router with 4 ethernet interfaces and 2 wifi ones, behind
two ISPs (one fiber, one DSL), running a few services such
as a DNS cache and a web server for a local network. Each
interface has one IPv4 and two IPv6.
All the scripts are genuine, only specific values such as
IP addresses are not present (machine-specific data is stored
in /etc, not in the s6-rc source directories).
The scripts use standard POSIX tools, the whole suite of
skarnet.org tools, and some specialized Linux tools such as
iproute2, iw, etc.
default is the entry point, i.e. the default bundle containing
all the services that are to be started at boot time. If
you are using s6-frontend, this bundle should not be defined
manually, it will be automatically computed by s6-frontend
from the enabled and essential services in your set.
Don't look too much into the weird ipv6 stuff, this is a bunch
of workarounds for a very broken ISP-provided device.
|
