summaryrefslogtreecommitdiff
path: root/sysusers.d
Commit message (Collapse)AuthorAge
* sysusers: realign sysusers snippetsLennart Poettering2014-08-19
|
* sysusers: set home directory for root to /rootLennart Poettering2014-08-19
|
* sysusers: split users for remote into separate fileZbigniew Jędrzejewski-Szmek2014-07-31
| | | | This mirrors the setup for tmpfiles.d done in ad95fd1d2b9.
* journal: add systemd-journal-remote to sysusersKay Sievers2014-07-16
|
* sysusers: split up default sysusers snippetLennart Poettering2014-06-29
| | | | | This ways, distributions have an easier way to replace the OS specific generic groups/users while keeping systemd's own.
* sysusers.d - fix typo in user definition fileJonathan Boulle2014-06-20
|
* sysusers: hide generate .conf fileLennart Poettering2014-06-13
|
* sysuser: generate default snippet incorporating TTY_GID properlyLennart Poettering2014-06-12
| | | | | When the user specifies --with-tty-gid= then we should honour that and write it to the snippet, too.
* sysusers: add new input group to default snippetLennart Poettering2014-06-12
|
* sysusers: add minimal tool to reconstruct /etc/passwd and /etc/group from ↵Lennart Poettering2014-06-12
static files systemd-sysusers is a tool to reconstruct /etc/passwd and /etc/group from static definition files that take a lot of inspiration from tmpfiles snippets. These snippets should carry information about system users only. To make sure it is not misused for normal users these snippets only allow configuring UID and gecos field for each user, but do not allow configuration of the home directory or shell, which is necessary for real login users. The purpose of this tool is to enable state-less systems that can populate /etc with the minimal files necessary, solely from static data in /usr. systemd-sysuser is additive only, and will never override existing users. This tool will create these files directly, and not via some user database abtsraction layer. This is appropriate as this tool is supposed to run really early at boot, and is only useful for creating system users, and system users cannot be stored in remote databases anyway. The tool is also useful to be invoked from RPM scriptlets, instead of useradd. This allows moving from imperative user descriptions in RPM to declarative descriptions. The UID/GID for a user/group to be created can either be chosen dynamic, or fixed, or be read from the owner of a file in the file system, in order to support reconstructing the correct IDs for files that shall be owned by them. This also adds a minimal user definition file, that should be sufficient for most basic systems. Distributions are expected to patch these files and augment the contents, for example with fixed UIDs for the users where that's necessary.