Bug 88567 - RFE: systemd-sysusers: Allow overriding dynamic ('-') field values with static values without warnings
Summary: RFE: systemd-sysusers: Allow overriding dynamic ('-') field values with stati...
Status: NEW
Alias: None
Product: systemd
Classification: Unclassified
Component: general (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium enhancement
Assignee: systemd-bugs
QA Contact: systemd-bugs
Depends on:
Reported: 2015-01-18 22:48 UTC by Alain Kalker
Modified: 2015-01-25 02:14 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Alain Kalker 2015-01-18 22:48:59 UTC
Using Arch Linux x86_64, systemd 218.

When I try overriding the unspecified (dynamic) GID of group 'disk' with a static value, for example:

g disk    -     -            -

g disk    6     -            -

systemd-sysusers logs the following warning: "Two or more conflicting lines for disk configured, ignoring."
In this particular case, the desired gid gets assigned, but in general it isn't clear from the message which line gets ignored.

I think it is very useful to be able to override the dynamic or default field values for a user or group as specified in one configuration file with static values specified for that same user or group in a different configuration file without warnings.
This way there is no need to customize the configuration files which ship with systemd (and keep those changes in sync with future updates).
Comment 1 Alain Kalker 2015-01-18 22:55:28 UTC
To be clear, this isn't about being able to override a config file entirely (I know that I can do this by placing a file with the same name in /etc/sysusers.d), this is about enabling a vendor (Arch Linux) to apply its historical UID/GID numbering scheme without touching files shipped with systemd like basic.conf.
Comment 2 Zbigniew Jedrzejewski-Szmek 2015-01-25 02:14:10 UTC
Sounds reasonable. Pathes welcome :)

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.