With the following /etc/tmpfiles.d/clock.conf: f /run/lock/clock - ramana users I get this error (in journalctl) on boot: systemd-tmpfiles: Failed to create file /run/lock/clock: No such file or directory However, manually running systemctl restart systemd-tmpfiles-setup.service after boot up creates the file without an error. The same error if I use this: F /run/lock/clock - ramana users Finally, if I use: d /run/lock f /run/lock/clock - ramana users The file gets created on boot as desired, but I get a different error about conflicting lines for /run/lock. What is the correct configuration? (The man page is unclear about whether f and F create parent directories.) What is the correct behaviour? I expect to be able to use the f configuration and get the file created without any errors.
Hmm, which distro is this? /usr/lib/tmpfiles.d/legacy.conf is usually responsible for creating /run/lock
The distro is Parabola (a derivative of Arch Linux).
It should probably work if you rename clock.conf to something that sorts after legacy.conf. E.g. x-clock.conf should work.
Versions in systemd git will automatically order creation of files by the prefix used. I.e. /a/b/c will always be created after /a/b, even if listed in the opposite order.
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.