[systemd-bugs] [Bug 53948] New: systemd-tmpfiles-setup.service fails to create file under /run/lock on boot

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=53948

             Bug #: 53948
           Summary: systemd-tmpfiles-setup.service fails to create file
                    under /run/lock on boot
    Classification: Unclassified
           Product: systemd
           Version: unspecified
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
        AssignedTo: systemd-bugs at lists.freedesktop.org
        ReportedBy: ramana at member.fsf.org
         QAContact: systemd-bugs at lists.freedesktop.org


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.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.