FS#73171 - [systemd] 250-1 removal of /usr/lib/tmpfiles.d/legacy.conf causes problems
Attached to Project:
Arch Linux
Opened by Thomas Eberhardt (ed209) - Monday, 27 December 2021, 14:14 GMT
Last edited by Christian Hesse (eworm) - Monday, 27 December 2021, 23:02 GMT
Opened by Thomas Eberhardt (ed209) - Monday, 27 December 2021, 14:14 GMT
Last edited by Christian Hesse (eworm) - Monday, 27 December 2021, 23:02 GMT
|
Details
Description:
The removal of /usr/lib/tmpfiles.d/legacy.conf which creates /run/lock, /var/lock (symlink to /run/lock) and /run/lock/subsys is causing at least one problem on my system. The following error is now reported during boot (i have libvirt-guests.service from libvirt enabled): libvirt-guests.sh[1461]: touch: cannot touch '/var/lock/subsys/libvirt-guests': No such file or directory Also there seems to be a lot of other stuff that uses /run/lock. On my system there are, for example, /run/lock/asound.state.lock, /run/lock/dmraid and /run/lock/lvm. |
This task depends upon
Closed by Christian Hesse (eworm)
Monday, 27 December 2021, 23:02 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 250-3
Monday, 27 December 2021, 23:02 GMT
Reason for closing: Fixed
Additional comments about closing: systemd 250-3
I guess other packages have to care the paths exist on their own now.
https://github.com/systemd/systemd/blob/v250/tmpfiles.d/legacy.conf.in
Well, ok.. As we do not set 'sysvinit-path' and 'sysvrcnd-path' the file is not generated for us...
Upstream systemd thinks these directories should be created on systems with support for SysV init scripts. We do not have this support.
Services started from unit files should care to create the directories themselves. (This can be done inside service if permissions are sufficient, but also with a specific tmpfiles file).
So probably not including this file and opening (upstream) issues for failing services is the correct way.