@pmatilai commented on this pull request.
> +invoke the *%\_\_systemd_sysusers* binary (typically *systemd-sysusers*(8))
> with
+the correct arguments in order to create the user and/or group accounts when
the
+package is installed. This is the recommended method on systemd native
platforms
+and requires no intervention from the package beyond shipping those files.
+
+RPM also allows for declaring sysusers.d entries explicitly in the spec file
+with the *%add_sysuser* macro. This macro takes a sysusers.d line with its
+fields passed as separate arguments and must be declared in the (sub-)package
+context. This method is primarily intended for platforms without systemd where
+it is typically also coupled with a custom *%\_\_systemd_sysusers* binary (see
+*DECODING* for details).
+
+Note that for certain types of systemd services (for example, transient or
+socket activated), it may be possible to avoid package level user and group
+allocation altogether by using Dynamic Users (see *DynamicUser=* in
+*systemd.exec*(5) and the URL in *SEE ALSO* for details).
This is a useful pointer 👍 - I vaguely knew of DynamicUser but it never even
crossed my mind to mention. It also explains the SEE ALSO section that I saw
before this bit here, and was wondering about some of the references 😄
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/4126#pullrequestreview-3866779696
You are receiving this because you are subscribed to this thread.
Message ID: <rpm-software-management/rpm/pull/4126/review/[email protected]>
_______________________________________________
Rpm-maint mailing list
[email protected]
https://lists.rpm.org/mailman/listinfo/rpm-maint
