Just a dummy question regarding containers. Aren't they using the same /dev/shm ?
A risk for several containers running slapd-standalone1 to step on each other ?

Just a dummy question regarding containers. Aren't they using the same /dev/shm ?
A risk for several containers running slapd-standalone1 to step on each other ?

That's a good question. If there are multiple instances with the same name then that would definitely be a problem. I'd hate to have to globally disable this feature if it's "containerised". Is that how customers deploy containers? One system with multiple images? I ask because maybe we could document that caveat?

In containers they each get their own /dev/shm I think, I think they are seperated. So I think that shouldn't be arisk. Certainly we can test this and then roll back if it's a problem. :)

The patch looks good to me. Ack

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 pull request has been cloned to Github as issue and is available here:
- https://github.com/389ds/389-ds-base/issues/4012

If you want to continue to work on the PR, please navigate to the github issue,
download the patch from the attachments and file a new pull request.

Thank you for understanding. We apologize for all inconvenience.