Am 12.03.2018 um 11:26 schrieb Laurent Bigonville:
> Package: nslcd
> Version: 0.9.9-1
> Severity: normal
> User: firstname.lastname@example.org
> Usertags: systemd-units
> nslcd currently doesn't provides a systemd .service file.
> This is a problem as nslcd should order itself with the
> nss-lookup.target and/or nss-user-lookup.target (see systemd.special(7)
Well, the SysV init has
# Should-Start: $named
So the generated .service file should already have an
After=nss-lookup.target ordering. Are you saying this is incorrect?
If so, is the SysV init script incorrect as well?
> Quickly looking at the initscript, it starts two daemon at once.
> Spliting that in two .service file would be a good idea.
> If it's not possible, adding a .service file doing
> ExecStart/ExecStop=/etc/init.d/nslcd start/stop would be a good
Fwiw, I wouldn't call that a good workaround. A workaround maybe, but
not a good one and we should not recommend doing that.
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
Pkg-systemd-maintainers mailing list