Handles the scandir for a given user. Designed to be either root or a branch of the supervision tree(nested scandir).
scandir [ -h ] [ -o owner ] create|start|stop|remove|reload|check|quit|abort|nuke|annihilate|zombies [<command options>]
This program creates, removes or sends a signal to a scandir (directory containing a collection of s6‑supervise processes) for the current owner of the proccess depending on the provided options.
When the start subcommand is invoked, this command launches the s6-svscan, responsible for supervising the s6-supervise program, where s6-supervise monitors a single service.
-h: prints this help.
-o owner: handles the scandir for the given owner. Only the root user can use this option. Note that owner can be any valid user on the system. However, the given user must have sufficient permissions to create the necessary directories at its location. That is /run/66 by default or the resulting path provided by the 66 ‑l option.
Creates a scandir for the owner of the process
66 scandir create
Creates a scandir for the owner owner
66 scandir -o owner create
Creates a scandir for a boot process
66 scandir create -b
Creates a scandir for the boot process using the specific account logaccount for the logger
66 scandir create -b -L logaccount
Creates (if doesn’t exist yet) and starts a scandir for the boot process within a container adding an environment directory
66 scandir start -B -e /etc/66/environment
Stops an already running scandir
66 scandir stop
This subcommand create a scandir.
scandir create [ -h ] [ -b|B ] [ -c ] [ -L log_user ] [ -s skel ]
This command create the necessary directory at /run/66. If the scandir already exist for the given user it will prevent its creation. You must remove it first if you don’t want to keep it.
Various files and directories is created at /run/66. Refers to deeper understanding documentation for futhers information.
-h: print this help.
-b: create scandir for a boot process. Only the root user can use this option. It is not meant to be used directly even with root. 66 boot calls it during the boot process.
-B: create scandir for a boot process inside a container. This option modifies some behaviors:
The ultimate output fallback (i.e. the place where error messages go when nothing catches them, e.g. the error messages from the catch-all logger and the s6-supervise process managing the catch-all logger) is not /dev/console, but the descriptor that was init’s standard error.
Stopping the container with reboot will make the container’s init program report being killed by a SIGHUP. Stopping it with 66 poweroff will make it report being killed by a SIGINT. This is according to the reboot(2) specification.
Stopping the container with 66 halt, however, is different. It will make the container’s pid 1 read a number in the /run/66/container/\<owner\>/halt file which contents the variable EXITCODE, and exit with the code it has read. (Default is 0.) This means that in order to run a command in a container managed by 66 boot and exit the container when the command dies while reporting the exit code to its parent, 66 boot use the /etc/66/rc.init.container file instead of the /etc/66/rc.init file. This file should be modified to launch the command that you want to start inside this container. Then you need to stop that container calling 66 halt.
All the running services will be killed, all the zombies will be reaped, and the container will exit with the required exit code.
-c: do not catch logs. On a non-containerized system, that means that all the logs from the scandir will go to /dev/console, and that /dev/console will also be the default stdout and stderr for services running under the supervision tree: use of this option is discouraged. On a containerized system (when paired with the -B option), it simply means that these outputs go to the default stdout and stderr given to the container’s init - this should generally not be the default, but might be useful in some cases.
-L log_user: run catch-all logger as log_user user. Default is s6log. The default can also be changed at compile-time by passing the ‑‑with‑s6‑log‑user=user option to ./configure.
-s skel: use skel as skeleton directory. Directory containing skeleton files. This option is not meant to be used directly even with root. 66 boot calls it during the boot process. Default is /etc/66.
Creates a scandir for the owner of the process
66 scandir create
Creates a scandir for the boot process using the specific account logaccount for the logger
66 scandir create -b -L logaccount
This subcommand starts a scandir and, if it doesn’t exist yet, it possibly creates it .
scandir start [ -h ] [ -d notif ] [ -s rescan ] [ -e environment ] [ -b|B ]
The scandir is created if it wasn’t made previously, but you don’t a fine-grained control over its creation as you do with the create subcommand.
-h: prints this help.
-d notif: notify readiness on file descriptor notif. When scandir is ready to accept signal, it will write a newline to notif. notif cannot be lesser than 3. By default, no notification is sent. If -b is set, this option have no effects.
-t rescan: perform a scan every rescan milliseconds. If rescan is set to 0 (the default), automatic scans are never performed after the first one and s6‑svscan will only detect new services by issuing either scandir reload or scandir check. It is strongly discouraged to set rescan to a positive value under 500.
-e environment: an absolute path. Merge the current environment variables with variables found in this directory before starting the scandir. Any file in environment not beginning with a dot and not containing the = character will be read and parsed. Each services will inherit of the key=value pair define within environment. The mentioned environment directory can not exceed more than 100 files. Each file can not contain more than 8095 bytes or more than 50 key=value pairs.
Starts a scandir with notify readiness mechanism on file descriptor 3
66 scandir start -d 3
Starts a scandir for the owner owner
66 scandir -o owner start
This command stops a running scandir.
scandir stop [ -h ]
This command stops the scandir sending a SIGTERM to all the s6-supervise processes supervising a service and a SIGHUP to all the s6-supervise processes supervising a logger, then exec into its finish procedure. This means that services will be brought down but loggers will exit naturally on EOF, and s6-svscan will wait for them to exit before exec’ing into .s6-svscan/finish or exiting itself: it’s a clean shutdown with no loss of logs.
Stop an already running scandir
66 scandir stop
Stop an already running scandir for the owner owner
66 scandir -o owner stop
This command remove a scandir from the live directory.
scandir remove [ -h ]
The scandir must first be stopped with scandir stop subcommand or similar subcommand to be able to remove it.
Certain directories within the scandir will not be removed. Specifically, /run/66/log, /run/66/scandir, and /run/66/state remain intact, whereas all UID subdirectories are deleted. Refers to deeper understanding for futhers information.
Removes a scandir
66 scandir remove
Removes a scandir for the owner owner
66 scandir -o owner scandir
This command reload configuration of a running scandir.
scandir reload [ -h ]
s6-svscan will perform a scan, and destroy inactive services.
Reloads a running scandir.
66 scandir reload
Reloads a scandir for the owner owner
66 scandir -o owner reload
This command check the scandir for services.
scandir check [ -h ]
s6-svscan will immediately perform a scan of scandir to check for services.
Checks a scandir
66 scandir check
Checks a scandir for the owner owner
66 scandir -o owner check
Quits a running scandir.
scandir quit [ -h ]
s6-svscan will send all its s6-supervise processes a SIGTERM, then exec into its finish procedure. This is different from stop subcommand in that services and loggers will be forcibly killed, so the quit procedure may be faster but in-flight logs may be lost.
Quits a scandir running scandir.
66 scandir quit
Quits a scandir for the owner owner
66 scandir -o owner quit
This command abort a running scandir.
scandir abort [ -h ]
s6-svscan will exec into its finishing procedure. It will not kill any of the maintained s6-supervise processes.
Aborts a scandir
66 scandir abort
Aborts a scandir for the owner owner
66 scandir -o owner abort
Kill all the s6-supervise processes.
scandir nuke [ -h ]
s6-svscan kill all the s6-supervise processes it has launched but that did not match a service directory last time scandir was scanned, i.e. it prunes the supervision tree so that it matches exactly what was in scandir at the time of the last scan. A SIGTERM is sent to the s6-supervise processes supervising services and a SIGHUP is sent to the s6-supervise processes supervising loggers.
Kill s6-supervise processes from a scandir
66 scandir nuke
Kill s6-supervise processes from a scandir for the owner owner
66 scandir -o owner nuke
Annihilates a running scandir.
scandir annihilate [ -h ]
Does the same thing as nuke, except that SIGTERM is sent to all the relevant s6-supervise processes, even if they are supervising loggers. This is not recommended in a situation where you do not need to tear down the supervision tree.
Annihilates a scandir
66 scandir annihilate
Annihilates a scandir for the owner owner
66 scandir -o owner annihilate
Destroy zombies from a running scandir.
scandir zombies [ -h ]
Immediately triggers s6-svscan’s reaper mechanism.
Removes zombies from a scandir
66 scandir zombies
Removes zombies from a scandir for the owner owner
66 scandir -o owner zombies
The -b, -B, -c and -s option are called by 66 boot. ‑b and -B will create .s6‑svscan control files (see s6‑svscan interface documentation) specifically for stage1 (PID1 process). This special scandir is controlled by 66 halt, 66 poweroff and 66 reboot command. The 66-shutdownd daemon which controls the shutdown request will be created automatically at the correct location. Further this specific task needs to read the skeleton file init.conf containing the live directory location which is the purpose of the ‑s option.
The live directory for the boot process requires writable directories and an executable filesystem. In order to accommodate for read‑only root filesystems there needs to be a tmpfs mounted before s6‑svscan can be run.