From c29368d9e34fee0e2fe0fae2fdf2865580be4ae0 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 28 Aug 2017 08:12:20 +0000 Subject: Add namespaces support, prepare for 0.3.1.0 --- doc/s6-linux-init-maker.html | 11 +++++++++++ 1 file changed, 11 insertions(+) (limited to 'doc/s6-linux-init-maker.html') diff --git a/doc/s6-linux-init-maker.html b/doc/s6-linux-init-maker.html index b7648ed..41d8372 100644 --- a/doc/s6-linux-init-maker.html +++ b/doc/s6-linux-init-maker.html @@ -63,6 +63,7 @@ machine - else the scripts will crash. [ -d dev_style ] \ [ -s env_store ] \ [ -e initial_envvar ] ... \ + [ -n ] \ dir @@ -374,6 +375,14 @@ environment, or of the form VAR=VALUE, to add an environment variable VAR with the value VALUE. The TZ variable, for instance, is a good candidate to be set in the global environment.

+ +

  • -n : tells s6-linux-init-maker that the init script +is going to run in a container, as pid 1 in a non-root namespace. +This modifies the .s6-svscan/finish, .s6-svscan/SIGHUP +and .s6-svscan/SIGINT scripts slightly, in order to provide +adequate functionality when the containerized system is asked to +shutdown. Do not add this option if the init script is going to run +in the root pid namespace.
  • Notes

    @@ -407,6 +416,8 @@ you could probably invoke s6-svscan directly as your process 1, or build a script by hand, which would result in a simpler init with less dependencies. +Nevertheless, if you prefer using s6-linux-init-maker, it +supports this case via the -n option.

    -- cgit v1.3.1