Skip to content

Commit 8b67c82

Browse files
hodgesdsfiorix
authored andcommitted
docs: update man page to reflect Type=notify unit template
Document the notify service type, startup timeout, and exit code 133 handling in the DESCRIPTION and FILES sections of sdme(1).
1 parent 90c6d20 commit 8b67c82

File tree

1 file changed

+12
-0
lines changed

1 file changed

+12
-0
lines changed

docs/sdme.1

Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,13 @@ per\-container upper layer.
1717
.PP
1818
Containers are managed as systemd template units
1919
.RB ( sdme@.service )
20+
with
21+
.B Type=notify
2022
and controlled via D\-Bus.
23+
The unit is considered active only after
24+
.BR systemd\-nspawn (1)
25+
sends its readiness notification, and a 2\-minute startup timeout
26+
catches hung boots.
2127
Interactive access uses
2228
.BR machinectl (1).
2329
.PP
@@ -662,6 +668,12 @@ after reboot when a container referencing the pod is started).
662668
.TP
663669
.I /etc/systemd/system/sdme@.service
664670
Systemd template unit (auto\-installed and auto\-updated).
671+
Uses
672+
.B Type=notify
673+
so the service is considered started only after
674+
.BR systemd\-nspawn (1)
675+
signals readiness.
676+
Exit code 133 is treated as a successful clean shutdown.
665677
.TP
666678
.I /etc/systemd/system/sdme@\fIname\fR.service.d/limits.conf
667679
Per\-container resource limits drop\-in (created when limits are set,

0 commit comments

Comments
 (0)