shaba/systemd
1
0
Fork 0
mirror of https://github.com/systemd/systemd.git synced 2025-03-21 02:50:18 +03:00
Code

man: beef up soft-reboot example unit

Browse Source 
Note that journal sockets have to be mounted for softreboot surviving units,
as per thread on the ML, otherwise logging does not work afterwards:

https://lists.freedesktop.org/archives/systemd-devel/2024-June/050382.html

Remove the oneshot, as it didn't actually make sense for a sleep infinity.
And run in a separate image, to showcase that the unit should really be
disconnected from the rootfs.
This commit is contained in:
Luca Boccassi 2024-06-07 13:49:20 +01:00
parent 953c60e2f1
commit db50a2b55c
1 changed files with 7 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
man/systemd-soft-reboot.service.xml
View File

@ -106,7 +106,10 @@
normal shutdown, reboot and maintenance mode. Finally, they have to be ordered after
<constant>basic.target</constant> to ensure correct ordering on boot. Note that in case any new or
custom units are used to isolate to, or that implement an equivalent shutdown functionality, they will
also have to be configured manually for correct ordering and conflicting. For example:</para>
also have to be configured manually for correct ordering and conflicting. In addition, to ensure the
service is disconnected from the rootfs resources (see next paragraph), it should run from a separate
image, but with the journal sockets mounted so that it is still allowed to log to the system journal.
For example:</para>
<programlisting>[Unit]
Description=My Surviving Service
@ -118,7 +121,9 @@ Conflicts=reboot.target kexec.target poweroff.target halt.target rescue.target e
Before=shutdown.target rescue.target emergency.target
[Service]
Type=oneshot
RootImage=/var/lib/root.raw
TemporaryFileSystem=/run
BindReadOnlyPaths=/run/systemd/journal/socket /run/systemd/journal/stdout
ExecStart=sleep infinity</programlisting>
</listitem>