The sysv init script does some funky parsing of configuration files that
might give us some trouble in an independent service file. I'll check if
we can't work around that and do away with the sysv init script
altogether, otherwise we might as well go with the drop-in override
since the new
> Do you need a whole service file for this? I thought you could achieve
> the same with a drop-in that just overrides the required keys
why would we do a SRU to hack in an override when it's just as easy to
do a SRU to actually create a correct service file so no override hack
is needed?
--
Hello Hector,
On Fri, Mar 22, 2019 at 12:36:57PM -, Heitor R. Alves de Siqueira wrote:
>The slapd package for OpenLDAP is shipped with a SysV-style init script
>(/etc/init.d/slapd). Systemd automatically converts this to a systemd
>service by generating the unit file using the
The attachment "debdiff for disco" seems to be a debdiff. The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff. If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if
You have been subscribed to a public bug by Heitor R. Alves de Siqueira
(halves):
[Impact]
Systemd service reports slapd as active, even though it may have failed
[Description]
The slapd package for OpenLDAP is shipped with a SysV-style init script
(/etc/init.d/slapd). Systemd automatically
5 matches
Mail list logo
