The problem is ldirectord's systemd service script; it tries to touch
/var/lock/subsys/ldirectord but it appears /var/lock/subsys dir doesn't
exist.  I believe /var/lock/subsys is a sysv service thing, and isn't
needed with systemd, but i only briefly investigated.

Most likely the service file should just have its touch/rm removed.  If
there is a reason to touch/remove the /var/lock/subsys lockfile, the
service needs to mkdir /var/lock/subsys first or at least ignore touch
errors.

This could potentially actually break ldirectord package installation or
upgrade, so I think it's more serious than just a failing autopkgtest.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1828258

Title:
  ldirectord systemd service fails if no /var/lock/subsys dir

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resource-agents/+bug/1828258/+subscriptions

-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to