Description of problem: systemd-tmpfiles[1146]: [/etc/tmpfiles.d/legacy.conf:22] Unknown group 'lock'. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. grep "Unknown group" /var/log/messages Possible patch found here. https://qa.mandriva.com/show_bug.cgi?id=63081
Keywords: (none) => PATCHBlocks: (none) => 2120Source RPM: (none) => systemd
I have the same issue on a clean install from Cauldron post-alpha3: from /var/log/daemons/errors.log: Jan 19 11:58:58 localhost systemd-tmpfiles[17159]: [/usr/lib/tmpfiles.d/legacy.conf:22] Unknown group 'lock'. Line 22 of /usr/lib/tmpfiles.d/legacy.conf : d /run/lock/lockdev 0775 root lock -
CC: (none) => curtis.h.news
(In reply to comment #1) > I have the same issue on a clean install from Cauldron post-alpha3: Yep, quick workaround solution is if grep lock /etc/group returns nothing: /usr/sbin/groupadd -r lock
c#2: getent group lock :) On up to date cauldron, after booting to kernel-server-3.2.1-1.mga2-1-1.mga2: # systemctl status systemd-tmpfiles-setup.service systemd-tmpfiles-setup.service - Recreate Volatile Files and Directories Loaded: loaded (/lib/systemd/system/systemd-tmpfiles-setup.service; static) Active: failed since Sat, 21 Jan 2012 12:02:16 +0000; 6min ago Main PID: 946 (code=exited, status=1/FAILURE) CGroup: name=systemd:/system/systemd-tmpfiles-setup.service Jan 21 12:02:14 dvg.homepower systemd-tmpfiles[946]: [/usr/lib/tmpfiles.d/legacy.conf:22] Unknown group 'lock'. # systemctl start systemd-tmpfiles-setup.service Job failed. See system logs and 'systemctl status' for details. # systemctl enable systemd-tmpfiles-setup.service Warning: unit files do not carry install information. No operation executed. I suspect that systemd package scripts should useradd 'lock' if not present.
CC: (none) => dvgevers
(In reply to comment #3) > c#2: getent group lock :) > > I suspect that systemd package scripts should useradd 'lock' if not present. Not useradd, groupadd -r lock
please install lockdev rpm and tell if the pb still exist
CC: (none) => dmorganec
(In reply to comment #5) > please install lockdev rpm > and tell if the pb still exist Sorry, bug 4144, bug 4035, bug 4124 has pretty much shutdown all my testing. All my VirtualBox Mageia guests abort when startx is issued.
closing as now lockdev is required by systemd ( and lockdev created the lock group )
Status: NEW => RESOLVEDResolution: (none) => FIXED