summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorLaurent Bercot <ska-skaware@skarnet.org>2021-04-19 11:26:23 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2021-04-19 11:26:23 +0000
commit9969d7437fa6786782e6c780fbadd6561220ccfe (patch)
tree0be0d73689929500cab25d32695d6074d41c9c90 /doc
parenteaeee8195f3347b3fa762a7ddbb0c7eb0ef15133 (diff)
downloads6-linux-init-9969d7437fa6786782e6c780fbadd6561220ccfe.tar.xz
Clean up the wtmp mess
Diffstat (limited to 'doc')
-rw-r--r--doc/overview.html4
-rw-r--r--doc/s6-linux-init-maker.html25
2 files changed, 19 insertions, 10 deletions
diff --git a/doc/overview.html b/doc/overview.html
index 71b852d..ef01e1e 100644
--- a/doc/overview.html
+++ b/doc/overview.html
@@ -129,8 +129,8 @@ command is executed. </li>
utmp record cleanup duty for patched <tt>login</tt> programs. </li>
<li> <tt>s6-linux-init-early-getty</tt>: the early getty,
allowing the user to login even if <em>rc.init</em> fails early. </li>
- <li> <tt>utmpd</tt> and <tt>wtmpd</tt>: the services performing
-utmp and wtmp access when <a href="//skarnet.org/software/utmps/">utmps</a> is
+ <li> <tt>utmpd</tt>: a service performing
+utmp access when <a href="//skarnet.org/software/utmps/">utmps</a> is
used. </li>
</ul> </li>
</ul>
diff --git a/doc/s6-linux-init-maker.html b/doc/s6-linux-init-maker.html
index f8ef940..9bf44ac 100644
--- a/doc/s6-linux-init-maker.html
+++ b/doc/s6-linux-init-maker.html
@@ -320,9 +320,15 @@ files in a staging directory. </li> <br />
available when the s6-linux-init package has been built with the
<tt>--enable-utmps</tt> configure option, that enables support for the
<a href="//skarnet.org/software/utmps/">utmps</a> package. The option
-defines the user that the <tt>utmpd</tt> and <tt>wtmpd</tt> services
-will run as, and activates these services. Default is <strong>no
-utmpd or wtmpd services</strong>. </li> <br />
+defines the user that the <tt>utmpd</tt> service
+will run as, and activates this service. (Note that you will still
+have to create a <tt>wtmpd</tt> service yourself and activate it
+later in the boot sequence, after a writable filesystem is mounted,
+because the wtmp database is supposed to be persistent and should live
+on a real filesystem.
+s6-linux-init cannot do that for you, because it only handles the
+early part of the boot sequence, before filesystems are mounted.)
+Default is <strong>no utmpd service</strong>. </li> <br />
<li> <tt>-C</tt>&nbsp;: create a set of scripts that is suitable
for running <em>in a container</em>. This modifies some behaviours:
@@ -457,11 +463,14 @@ directories may exist:
<ul>
<li> A directory somewhere under <tt>run-image</tt>, by default <tt>utmps</tt>,
-that is the location where the utmp and wtmp files will be created. </li>
- <li> Two additional early services named <tt>utmpd</tt> and <tt>wtmpd</tt>,
-that are the <a href="//skarnet.org/software/utmps/">utmps</a> way of
-providing secure utmp functionality. </li>
-</ul>
+that is the location where the utmp files will be created. </li>
+ <li> An additional early service named <tt>utmpd</tt>, which is
+a part of the <a href="//skarnet.org/software/utmps/">utmps</a> way of
+providing secure utmp functionality. A similar <tt>wtmpd</tt> service
+should also be created and run later in the boot sequence by the
+service manager; it is not s6-linux-init's job to do it because
+<tt>wtmp</tt> requires a real, writable filesystem. </li>
+</ul>1
<h2> Notes </h2>