@mreynolds This could just be an issue in the suse spec file now I think about it, because we set this in the spec to --with-tmpfiles-d="%{_tmpfilesdir}" in configure, which yields tmpfiles_d = /usr/lib/tmpfiles.d in the defaults.inf. On fedora/rhel what is this value for you?

https://build.opensuse.org/request/show/753852

Change in question, could be worth checking the fedora/rhel packages for this @mreynolds then we can close it.

The macros seem to expand the very same on Fedora as on SUSE. However, our upstream spec and also Fedora spec already use the %{_sysconfdir}/tmpfiles.d value.

A bit OT: Why we even bother creating the tmpfiles config for each instance? Usually there is this inside:

d /run/dirsrv 0770 dirsrv dirsrv
d /run/lock/dirsrv 0770 dirsrv dirsrv
d /run/lock/dirsrv/slapd-localhost 0770 dirsrv dirsrv

... where we can just replace the localhost with a glob * and ship this in /usr/lib/tmpfiles.d as a generic. The user/group name could be templated build-time if necessary.

Uhhhh, how does a glob work or help here? Linux can't create folders on first read like this, so this wouldn't work. We need to specify the folder name.

We also do need to ensure the full path is built because /run is a tmpfs IIRC.

@firstyear You are right. The first two lines could be generalized but the last one couldn't as it is instance-specific.

Anyway, I'll close this as the original issues reported was already found to be a non-issue within the upstream/Fedora spec file.

Cool cool, thanks @mhonek

389-ds-base is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in 389-ds-base's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/389ds/389-ds-base/issues/3819

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.