Hi Daniel, could you please give more hints as to how you experienced this error?
A fresh 26.04 resolute install of the slapd package doesn't show the error. Furthermore, systemd documentation[1] allows for executables without a full path, as there is a search mechanism, which by default includes /usr/bin: $ systemd-path search-binaries-default /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin I also didn't find, after a few non-exhaustive greps, who is emitting the "The SystemD ExecXY ..." error message. I checked systemd source code. The fix doesn't look wrong (give it a full path), but I'd like to understand better how you came across this, to have an idea of which scenario causes the problem, and determine it's impact. 1. https://manpages.ubuntu.com/manpages/stonking/man5/systemd.service.5.html#:~:text=If%20the%20command%20is%20not%20a%20full%20(absolute)%20path -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2152633 Title: slapd.service won't restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/2152633/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
