[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#8707) slapd: Add systemd service notification support

michael@stroeder.com wrote:
> ryan@nardis.ca wrote:
>> An explicit design goal of systemd is that unit files should be
>> uniform enough that it's reasonable for upstream projects to
>> ship them,
> Yes, systemd has many admirable goals.

And not enough competent developers to achieve any of them.

> On the other hands Linux distributions differ a lot especially
> regarding file system layout, not to speak of their systemd
> back-port patches.

My experience so far with Arch/Debian/Ubuntu/Centos mirrors this - they'r=
e all=20
different in FS layouts (/var/run vs /run, etc etc etc) and the situation=
no better than it was in SysV init. I see no reason for us to change our=20
policy regarding system-specific dependencies.

re: providing an example in OpenLDAP documentation - this is an only slig=
less-bad suggestion. The onus is on systemd to provide adequate documenta=
on how to write unit files, and adequate examples of working files. Our o=
responsibility is to document the parameters for correctly running the co=
it's up to distro packagers to encapsulate a correct invocation into what=
their launch mechanism is.

If no one has any other reasons to offer, I'm inclined to reject and clos=
this ITS.
> Ciao, Michael.
> P.S.:
> Right at this moment I'm trying to figure out the appropriate
> Requires and After lines in systemd unit file template in =C3=83=E2=80=A0=
> ansible role. And the ansible role has only support for three (and
> a half) different Linux distributions [1].
> [1] https://www.ae-dir.com/install.html#prereq

   -- Howard Chu
   CTO, Symas Corp.           http://www.symas.com
   Director, Highland Sun     http://highlandsun.com/hyc/
   Chief Architect, OpenLDAP  http://www.openldap.org/project/