NAME
systemd-sysusers, systemd-sysusers.service - Allocate system users and groups
SYNOPSIS
systemd-sysusers [OPTIONS...] [CONFIGFILE...]
systemd-sysusers.service
DESCRIPTION
systemd-sysusers creates system users and groups, based on files in the format described in sysusers.d(5).
If invoked with no arguments, directives from the configuration files found in the directories specified by sysusers.d(5) are executed. When invoked with positional arguments, if option --replace=PATH is specified, arguments specified on the command line are used instead of the configuration file PATH. Otherwise, just the configuration specified by the command line arguments is executed. If the string "-" is specified instead of a filename, the configuration is read from standard input. If the argument is a file name (without any slashes), all configuration directories are searched for a matching file and the file found that has the highest priority is executed. If the argument is a path, that file is used directly without searching the configuration directories for any other matching file.
OPTIONS
The following options are understood:
--root=root
Added in version 215.
--image=image
Added in version 247.
--image-policy=policy
--replace=PATH
This option is intended to be used when package installation scripts are running and files belonging to that package are not yet available on disk, so their contents must be given on the command line, but the admin configuration might already exist and should be given higher priority.
Example 1. RPM installation script for radvd
echo 'u radvd - "radvd daemon"' | \
\n
systemd-sysusers --replace=/usr/lib/sysusers.d/radvd.conf -This will create the radvd user as if /usr/lib/sysusers.d/radvd.conf was already on disk. An admin might override the configuration specified on the command line by placing /etc/sysusers.d/radvd.conf or even /etc/sysusers.d/00-overrides.conf.
Note that this is the expanded form, and when used in a package, this would be written using a macro with "radvd" and a file containing the configuration line as arguments.
Added in version 238.
--dry-run
Added in version 250.
--inline
Added in version 238.
--cat-config
--tldr
--no-pager
-h, --help
--version
CREDENTIALS
systemd-sysusers supports the service credentials logic as implemented by ImportCredential=/LoadCredential=/SetCredential= (see systemd.exec(5) for details). The following credentials are used when passed in:
passwd.hashed-password.user
Added in version 249.
passwd.plaintext-password.user
Added in version 249.
passwd.shell.user
Added in version 249.
sysusers.extra
Added in version 252.
Note that by default the systemd-sysusers.service unit file is set up to inherit the "passwd.hashed-password.root", "passwd.plaintext-password.root", "passwd.shell.root" and "sysusers.extra" credentials from the service manager. Thus, when invoking a container with an unpopulated /etc/ for the first time it is possible to configure the root user's password to be "systemd" like this:
# systemd-nspawn --image=... --set-credential=passwd.hashed-password.root:'$y$j9T$yAuRJu1o5HioZAGDYPU5d.$F64ni6J2y2nNQve90M/p0ZP0ECP/qqzipNyaY9fjGpC' ...Note again that the data specified in this credential is consulted only when creating an account for the first time, it may not be used for changing the password or shell of an account that already exists.
Use mkpasswd(1) for generating UNIX password hashes from the command line.
EXIT STATUS
On success, 0 is returned, a non-zero failure code otherwise.
SEE ALSO
systemd(1), sysusers.d(5), Users, Groups, UIDs and GIDs on systemd systems[2], systemd.exec(5), mkpasswd(1)
NOTES
- 1.
Discoverable Partitions Specification
- 2.
Users, Groups, UIDs and GIDs on systemd systems