From 5e95d487982b9362b544139b98d1da55fa6ef78c Mon Sep 17 00:00:00 2001 From: PS Date: Sat, 7 Feb 2026 10:20:30 +0100 Subject: Add doc --- doc/bin/compile-db.html | 98 +++++++++++++++++++++++++ doc/bin/longrun-make.html | 141 ++++++++++++++++++++++++++++++++++++ doc/bin/oneshot-make.html | 101 ++++++++++++++++++++++++++ doc/bin/prepare-svscan.html | 120 ++++++++++++++++++++++++++++++ doc/bin/system-db.html | 67 +++++++++++++++++ doc/bin/system-ml.html | 96 ++++++++++++++++++++++++ doc/bin/system-rc.html | 63 ++++++++++++++++ doc/bin/system-run.html | 67 +++++++++++++++++ doc/bin/system-shutdown-daemon.html | 123 +++++++++++++++++++++++++++++++ doc/bin/user-db.html | 82 +++++++++++++++++++++ doc/bin/user-init.html | 128 ++++++++++++++++++++++++++++++++ doc/bin/user-ml.html | 104 ++++++++++++++++++++++++++ doc/bin/user-rc.html | 74 +++++++++++++++++++ doc/bin/user-run.html | 78 ++++++++++++++++++++ doc/bin/user-shutdown.html | 68 +++++++++++++++++ doc/bin/user-tmpfs.html | 104 ++++++++++++++++++++++++++ 16 files changed, 1514 insertions(+) create mode 100644 doc/bin/compile-db.html create mode 100644 doc/bin/longrun-make.html create mode 100644 doc/bin/oneshot-make.html create mode 100644 doc/bin/prepare-svscan.html create mode 100644 doc/bin/system-db.html create mode 100644 doc/bin/system-ml.html create mode 100644 doc/bin/system-rc.html create mode 100644 doc/bin/system-run.html create mode 100644 doc/bin/system-shutdown-daemon.html create mode 100644 doc/bin/user-db.html create mode 100644 doc/bin/user-init.html create mode 100644 doc/bin/user-ml.html create mode 100644 doc/bin/user-rc.html create mode 100644 doc/bin/user-run.html create mode 100644 doc/bin/user-shutdown.html create mode 100644 doc/bin/user-tmpfs.html (limited to 'doc/bin') diff --git a/doc/bin/compile-db.html b/doc/bin/compile-db.html new file mode 100644 index 0000000..c0ed957 --- /dev/null +++ b/doc/bin/compile-db.html @@ -0,0 +1,98 @@ + + + + + + + compile-db + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The compile-db program

+ compile-db is a helper script for use by other software + that compiles a general confdir + tries to use the result to update a general + livedir. +

Interface

     compile-db confdir livedir

+ compile-db runs + s6-rc-compile + on confdir/src/*. +
+ This creates a new confdir/@xyz@_db + file with @xyz@ based on the current UNIX time. +
+ If livedir exists, that is, + a goetia based supervision tree is running, + compile-db the tries to update the live state at livedir + to @xyz@_db using + s6-rc-update. +
+ If it succeeds, it updates the symlink + confdir/compiled + to point to + confdir/@xyz@_db + and deletes the old database + confdir/@abc@_db. +
+ If it does not succeed, + it runs s6-rc-update to switch back to + confdir/compiled + which points to + confdir/@abc@_db. + Followed by deleting + confdir/@xyz@_db. +

Exit codes

+ 0: success +
+ Since compile-db is an + execline + script, it exits with an approximation + of employed program that failed. +
+ compile-db mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no otions to compile-db. +

+ + diff --git a/doc/bin/longrun-make.html b/doc/bin/longrun-make.html new file mode 100644 index 0000000..0c5d8c4 --- /dev/null +++ b/doc/bin/longrun-make.html @@ -0,0 +1,141 @@ + + + + + + + longrun-make + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The longrun-make program

+ longrun-make contains boilerplate code + required to create the + source directory + of a longrun service + based on strings. +

Interface

     longrun-make workingdir name type script dependencies

+ type can only be one of log | srv. +
+ dependencies can only be one of "dependency1 dependency2 ..." | none. +
+ longrun-make creates the directory workingdir/name-type. +
+ It creates the file workingdir/name-type/type + (literal "type") and writes the line longrun to it. +
+ It creates the file workingdir/name-type/notification-fd + and writes the line 3 to it. +
+ It creates the file workingdir/name-type/run + and writes script to it. +
+ If type is log and the file + workingdir/name-type/consumer-for + does not contain the string name: +
- + longrun-make aquires a lock on the file + workingdir/name-type/consumer-for + using + s6-setlock. +
- + It appends the string name-srv to the file + workingdir/name-type/consumer-for + creating it if it does not exist. +
- + It creates a file workingdir/name-type/pipeline-name, + truncating it if it does exist and adds the string name. +
+
+ If type is srv: +
- + The file + workingdir/name-type/producer-for + is created, truncated and the string name-log is added. +
+
+ If dependencies is not none: +
- + The directory + workingdir/name-type/dependencies.d + is created. +
- + For each word "dependency1 dependency2 ..." in + dependencies separated by spaces, + a file + workingdir/name-type/dependencies.d/dependency + is created. +
+

+ longrun-make is, by means of locking and checking for duplicates, + specifically designed to allow parallel creation of logging + source directories. +

Exit codes

+ 0: success +
+ Since longrun-make is an + execline + script, it exits with an approximation + of employed program that failed. +
+ longrun-make mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no otions to longrun-make. +

+ + diff --git a/doc/bin/oneshot-make.html b/doc/bin/oneshot-make.html new file mode 100644 index 0000000..1b285c6 --- /dev/null +++ b/doc/bin/oneshot-make.html @@ -0,0 +1,101 @@ + + + + + + + oneshot-make + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The oneshot-make program

+ oneshot-make contains boilerplate code + required to create the + source directory + of a oneshot service + based on strings. +

Interface

     oneshot-make workingdir name upscript downscript dependencies

+ dependencies can only be one of "dependency1 dependency2 ..." | none. +
+ oneshot-make creates the directory workingdir/name +
+ it creates the file workingdir/name/type + and writes the line oneshot to it. +
+ it creates the file workingdir/name/up + and writes upscript to it. +
+ it creates the file workingdir/name/down + and writes downscript to it. +
+ If dependencies is not none: +
- + The directory + workingdir/name/dependencies.d + is created. +
- + For each word "dependency1 dependency2 ..." in + dependencies separated by spaces, + a file + workingdir/name/dependencies.d/dependency + is created. +
+

Exit codes

+ 0: success +
+ Since oneshot-make is an + execline + script, it exits with an approximation + of employed program that failed. +
+ oneshot-make mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no otions to oneshot-make. +

+ + diff --git a/doc/bin/prepare-svscan.html b/doc/bin/prepare-svscan.html new file mode 100644 index 0000000..6b82bd5 --- /dev/null +++ b/doc/bin/prepare-svscan.html @@ -0,0 +1,120 @@ + + + + + + + prepare-svscan + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The prepare-svscan program

+ prepare-svscan does generic preparation of the + supervision tree. + It is also used in system-init and + user-init. +

Interface

     prepare-svscan workingdir rundir bundle prog...

+ prepare-svscan sets its standard input to /dev/null. +
+ It sets the umask to 0022. +
+ It creates the directory rundir. +
+ It copies all contents of workingdir/run-image/. + to rundir/. +
+ It changes its standard output to rundir/service/s6-svscan-log/fifo. +
+ prepare-svscan then forks a background process that: +
- + waits for a reading end at rundir/service/s6-svscan-log/fifo. +
- + Once the above is given, if rundir/s6-rc does not exist, +
- + it initiates s6-rc on + rundir/service using + s6-rc-init + and starts the bundle bundle using s6-rc. +
+
+ It copies stderr to stdout. +
+ If available, the directory workingdir/env is sourced using + s6-env. +
+ prepare-svscan executest into prog..., + which is usually directly or indirectly + s6-svscan. +

+ Once s6-svscan is launched it will start an + s6-supervise + process on rundir/service/s6-svscan-log which starts + s6-log reading + from rundir/service/s6-svscan-log/fifo. + This in turn triggers the forked background process to continue with its second step. +

Exit codes

+ prepare-svscan usually executes into + s6-svscan + which exits according to its page. +
+ Since prepare-svscan is an + execline + script, it exits with an approximation + of employed program that failed. +
+ prepare-svscan mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no otions to prepare-svscan. +

+ + diff --git a/doc/bin/system-db.html b/doc/bin/system-db.html new file mode 100644 index 0000000..056f5b7 --- /dev/null +++ b/doc/bin/system-db.html @@ -0,0 +1,67 @@ + + + + + + + system-db + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The system-db program

+ system-db compiles the + source directories + of the + system configuration directory + into the compiled format. + This format can then be used by init and + system-rc + to set up and control a + system supervision tree. +

+ system-db is a wrapper around the more general + compile-db + making it target the system supervision tree. +

Interface

     system-db

+ system-db takes no arguments. +
+ It runs compile-db supplementing it with the + system configuration directory + and + system runtime directory. +

Exit codes

+ Since system-db is a wrapper around compile-db, it + behaves exactly like it. +

Options

+ There are no options to system-db. +

+ + diff --git a/doc/bin/system-ml.html b/doc/bin/system-ml.html new file mode 100644 index 0000000..bc487a9 --- /dev/null +++ b/doc/bin/system-ml.html @@ -0,0 +1,96 @@ + + + + + + + system-ml + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The system-ml program

+ system-ml automatically creates logging service + source directories + for longrun services in the + system configuration directory. + To create the logging service source directories, + system-ml uses + longrun-make internally. +

Interface

     system-ml

+ system-ml takes no arguments. +
+ It deletes the src/generated-logger subdirectory of the + system configuration directory. +
+ It scans the src subdirecotry of the + system configuration directory + for longrun services. +
+ It checks for each longrun it detects, + whether its source directory contains a file no-ml. + If this file exits, this longrun is skipped in the subsequent logger generation. +
+ It generates a logging service source directory at + src/generated-logger/@longrun@-log + in the system configuration directory. + It does so in parallel for each longrun @longrun@-srv it found. +

Exit codes

+ Since system-ml is an + execline + script, it exits with an approximation + of employed program that failed. +
+ system-ml mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no options to system-ml. +

Notes

+ The logger services created by this script + will drop privileges to + @loguser@, + which must exist at runtime. + (see log directory). +

+ + diff --git a/doc/bin/system-rc.html b/doc/bin/system-rc.html new file mode 100644 index 0000000..f6e48db --- /dev/null +++ b/doc/bin/system-rc.html @@ -0,0 +1,63 @@ + + + + + + + system-rc + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The system-rc program

+ system-rc is a thin convenience wrapper around + s6-rc + doing nothing more then pointing it to the right livedir. +

+ Read the page of + s6-rc + to understand what this utility does. +

Interface

     system-rc ... see s6-rc ...

+ It runs + s6-rc + with the appropriate livedir option. +

Exit codes

+ Since system-rc is a thin wrapper around + s6-rc + it behaves almost exactly like it. +
+ See also: + execline exit code handling. +

Options

+ system-rc takes exactly the same options as + s6-rc. +

+ + diff --git a/doc/bin/system-run.html b/doc/bin/system-run.html new file mode 100644 index 0000000..465cee4 --- /dev/null +++ b/doc/bin/system-run.html @@ -0,0 +1,67 @@ + + + + + + + system-run + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The system-run program

+ system-run allows + to hand over the execution of commands to the + system supervision tree. +

Interface

     system-run prog...

+ Internally, system-run invokes + s6-sudo + to connect to an + s6-sudod + instance provided by the system + goetia-runner. +
+ prog... is then transferred + to and executed by goetia-runner. +
+ See + s6-sudo + and + s6-sudod + for configuration options and detailed information. +

Exit codes

+ system-run behaves exactly as + s6-sudo. +

Options

+ system-run takes the exact same options as + s6-sudoc. +

+ + diff --git a/doc/bin/system-shutdown-daemon.html b/doc/bin/system-shutdown-daemon.html new file mode 100644 index 0000000..82493b6 --- /dev/null +++ b/doc/bin/system-shutdown-daemon.html @@ -0,0 +1,123 @@ + + + + + + + system-shutdown-daemon + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The system-shutdown-daemon program

+ system-shutdown-daemon contains the Kernel independent + part of the shutdown sequence. + It is invoked by the Kernel specifict goetia-shutdown service, + e.g. + goetia-shutdown service for Linux + or + goetia-shutdown service for FreeBSD. + system-shutdown-daemon is a long lived program that waits for instruction by the system-shutdown command + The latter is part of the Kernel specific packages, e.g. + goetia-linux + or + goetia-freebsd. +

Interface

     system-shutdown-daemon

+ system-shutdown-daemon takes no arguments. +
+ It tries to execute ./stage3b, + which is by default not executable. + If it can not execute ./stage3b, + and only in this case, + it continues with the following. +
+ All services managed by + s6-rc + are stopped. + This means, all services defined in + source directories + at the src subdirectory of the + system configuration directory. +
+ Next, all leftover services except + s6-svscan-log, goetia-shutdown and goetia-rescue, are stopped. +
+ The file stage3b, expected to exist in the current working directory + is made executable. + This file is part of the Kernel secific service directories. + (see e.g. goetia-shutdown) +
+ all uncaught system logs are copied from the + log/uncaught-logs + subdirectory of the + system runtime directory. + to the + uncaught-logs + subdirectory of the + system log directory. +
+ SIGTERM is sent to all processes but PID 1. +
+ This also stops the system-shutdown-daemon process. + It is automatically restarted by the system supervision tree, + but this time, the file ./stage3b is executable + and executed instead of what is described above. + What happens in ./stage3b is Kernel specific, + and documented on + goetia-shutdown service for Linux, + goetia-shutdown service for FreeBSD, + etc. +

Exit codes

+ Since system-shutdown-daemon is an + execline + script, it exits with an approximation + of employed program that failed. +
+ system-shutdown-daemon mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no options to system-shutdown-daemon. +

+ + diff --git a/doc/bin/user-db.html b/doc/bin/user-db.html new file mode 100644 index 0000000..26ef310 --- /dev/null +++ b/doc/bin/user-db.html @@ -0,0 +1,82 @@ + + + + + + + user-db + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The user-db program

+ user-db compiles the + source directories + of the + user configuration directory + into the compiled format. + This format can then be used by init and + user-rc + to set up and control a + user supervision tree. +

+ user-db is a wrapper around the more general + compile-db + making it target the user supervision tree. +

Interface

     user-db

+ user-db takes no arguments. +
+ It reads the USER environment variable, + if it is empty it exits 100. +
+ It reads the USERTREE environment variable, + if it is empty it exits 100. +
+ It reads the HOME environment variable, + if it is empty it exits 100. +
+ It runs compile-db supplementing it the correct + user configuration directory + and + user runtime directory. +

Exit codes

+ 100 if a critical environment variable is missing. +
+ Since user-db is a wrapper around compile-db, it + behaves exactly like it. +

Options

+ There are no options to user-db. +

+ + diff --git a/doc/bin/user-init.html b/doc/bin/user-init.html new file mode 100644 index 0000000..c96c3ae --- /dev/null +++ b/doc/bin/user-init.html @@ -0,0 +1,128 @@ + + + + + + + user-init + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The user-init program

+ user-init starts a user supervision tree for + the user defined in the USER + environment variable. +

Interface

     user-init

+ user-init takes no arguments. +
+ It reads the USER environment variable, + if it is empty it exits 100. +
+ It reads the USERTREE environment variable, + if it is empty it exits 100. +
+ It reads the BUNDLE environment variable, + defaulting to default if empty. +
+ It reads the PATH environment variable, + defaulting to + /command:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/libexec:/usr/local/libexec + if empty. +
+ if ${USER}/${USERTREE} subdirectory of the + runtime directory + olready existis, it exits 100. +
+ It sets the HOME environment variable based on the result of + homeof. +
+ It prepends ${HOME}/.local/bin: to the PATH + environment variable. +
+ It sets the UID, GID and GIDLIST + environment variables using + s6-envuidgid. +
+ It runs + prepare-svscan + with the proper arguments. +
+ Finally, it executes into + s6-svscan + on the scandir represented by the + ${USER}/${USERTREE}/service + subdirectory of the + user runtime directory. +

Exit codes

+ 100 if a critical environment variable is missing. +
+ user-init usually executes into + s6-svscan + which exits according to its documentation. +
+ Since user-init is an + execline + script, it exits with an approximation + of employed program that failed. +
+ user-init mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective documentation. +
+ See also: + execline exit code handling. +

Options

+ There are no otions to user-init. +

Notes

+ More information about user supervision trees + themselves can be found on the + user supervision tree + page. +

+ + diff --git a/doc/bin/user-ml.html b/doc/bin/user-ml.html new file mode 100644 index 0000000..d6d7e2e --- /dev/null +++ b/doc/bin/user-ml.html @@ -0,0 +1,104 @@ + + + + + + + user-ml + + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The user-ml program

+ user-ml automatically creates logging service + source directories + for longrun services of the + user configuration directory. + To create the logging service source directories, + user-ml uses + longrun-make internally. +

Interface

     user-ml

+ user-ml takes no arguments. +
+ It reads the USER environment variable, + if it is empty it exits 100. +
+ It reads the USERTREE environment variable, + if it is empty it exits 100. +
+ It reads the HOME environment variable, + if it is empty it exits 100. +
+ It deletes the ${USERTREE}/src/generated-logger subdirectory + of the user configuration subdirectory. +
+ It scans the ${USERTREE}/src subdirectory + of the user configuration subdirectory + for longrun services. +
+ It checks for each longrun it detects, + whether its source directory contains a file no-ml. + If this file exits, this longrun is skipped in the subsequent logger generation. +
+ It generates a logging service source directory + ${USERTREE}/src/generated-logger/@longrun@-log + in parallel for each longrun @longrun@-srv it found + in the user configuration subdirectory. +

Exit codes

+ 100 if a critical environment variable is missing. +
+ Since user-ml is an + execline + script, it exits with an approximation + of employed program that failed. +
+ user-ml mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no options to user-ml. +

+ + diff --git a/doc/bin/user-rc.html b/doc/bin/user-rc.html new file mode 100644 index 0000000..3bad0c5 --- /dev/null +++ b/doc/bin/user-rc.html @@ -0,0 +1,74 @@ + + + + + + + user-rc + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The user-rc program

+ The user-rc program is a thin convenience wrapper around + s6-rc + doing nothing more then pointing it to the right livedir. +

+ Read the page of + s6-rc + to understand what this utility does. +

Interface

     user-rc ... see s6-rc ...

+ user-rc reads the USER environment variable, + if it is empty it exits 100. +
+ It reads the USERTREE environment variable, + if it is empty it exits 100. +
+ It runs + s6-rc + with the appropriate livedir option. +

Exit codes

+ 100 if a critical environment variable is missing. +
+ Since user-rc is a thin wrapper around + s6-rc + it behaves almost exactly like it. +
+ See also: + execline exit code handling. +

Options

+ user-rc takes exactly the same options as + s6-rc. +

+ + diff --git a/doc/bin/user-run.html b/doc/bin/user-run.html new file mode 100644 index 0000000..924849c --- /dev/null +++ b/doc/bin/user-run.html @@ -0,0 +1,78 @@ + + + + + + + user-run + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The user-run program

+ The user-run program allows + to hand over the execution of commands to the + user supervision tree. +

Interface

     user-run prog...

+ user-rc reads the USER environment variable, + if it is empty it exits 100. +
+ It reads the USERTREE environment variable, + if it is empty it exits 100. +
+ Internally, user-run invokes + s6-sudo + to connect to an + s6-sudod + instance provided by the user + goetia-runner. +
+ prog... is then transferred + to and executed by goetia-runner. +
+ See + s6-sudo + and + s6-sudod + for configuration options and detailed information. +

Exit codes

+ 100 if a critical environment variable is missing. +
+ user-run behaves exactly as + s6-sudo. +

Options

+ user-run takes the exact same options as + s6-sudoc. +

+ + diff --git a/doc/bin/user-shutdown.html b/doc/bin/user-shutdown.html new file mode 100644 index 0000000..6a52db8 --- /dev/null +++ b/doc/bin/user-shutdown.html @@ -0,0 +1,68 @@ + + + + + + + user-shutdown + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The user-shutdown program

+ The user-shutdown program is used to tear down + user supervision trees. +

Interface

     user-shutdown

+ user-shutdown takes no arguments. +
+ It starts the user + goetia-shutdown + service. +

Exit codes

+ Since user-shutdown is an + execline + script, it exits with an approximation + of employed program that failed. +
+ user-shutdown mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective pages. +
+ See also: + execline exit code handling. +

Options

+ There are no options to user-shutdown. +

+ + diff --git a/doc/bin/user-tmpfs.html b/doc/bin/user-tmpfs.html new file mode 100644 index 0000000..3c22c57 --- /dev/null +++ b/doc/bin/user-tmpfs.html @@ -0,0 +1,104 @@ + + + + + + + user-tmpfs + + + +

+ goetia-base +
+ goetia +
+ Software +
+ 0x53.net +

+ +

The user-tmpfs program

+ The user-tmpfs program prepares + a user owned tmpfs for + the user defined in the USER + environment variable. + The user owned tmpfs is created at + @tmpfsdir@/@usrrundir@/${USER}. +

Interface

     user-tmpfs

+ user-tmpfs takes no arguments. +
+ It reads the USER environment variable, + if it is empty it exits 100. +
+ It reads the USER_TMPFSDIR_SIZE environment variable, + defaulting to 64m if undefined. +
+ It creates the directory + @tmpfsdir@/@usrrundir@/${USER}. +
+ It mounts a tmpfs + of size USER_TMPFSDIR_SIZE + with its root owned bi USER + and mode 0755 + at @tmpfsdir@/@usrrundir@/${USER}. +

Exit codes

+ 100 if a critical environment variable is missing. +
+ Since user-tmpfs is an + execline + script, it exits with an approximation + of employed program that failed. +
+ user-tmpfs mostly uses + execline + and + s6 + software, the exit behaviour of which can be looked up on + their respective documentation. +
+ See also: + execline exit code handling. +

Options

+ There are no otions to user-tmpfs. +

Notes

+ user-tmpfs is intended to be used in a boot time + system supervision tree + oneshot service to prepare the + user runtime directory + of a user. + For each user who should have a user runtime directory, + there should be a distinct oneshot running user-tmpfs. +

+ Alternatively, user-tmpfs could be run by a login manager + after login, but befor initiating the first + user supervision tree. +

+ + -- cgit v1.2.3