389-ds-base

#50086 allow only one slapd process at any time
Closed: wontfix by spichugi. Opened by lkrispen.

Closed: wontfix
Reopen Issue

Issue Description

The database environment for BDB can be shared by multiple processes, so it is possible to run a slapd process and one or more offline processes in parallel, eg an normal slapd process serving client requests and a db2ldif export.

There have been many problems with this concept, especially if a secondary process crashed or was killed and did hold locks in the shared environment.
So, by and by, the processes allowed to run in parallel were limited, but there still can be problems.

The request in this ticket is to eliminate all options for parallel slapd processes

Metadata Update from @mreynolds:
- Custom field component adjusted to None
- Custom field origin adjusted to None
- Custom field reviewstatus adjusted to None
- Custom field type adjusted to None
- Custom field version adjusted to None
- Issue set to the milestone: 1.4.0

Metadata Update from @mreynolds:
- Issue priority set to: minor
- Issue set to the milestone: FUTURE (was: 1.4.0)

Metadata Update from @mreynolds:
- Issue set to the milestone: 1.4.5 (was: FUTURE)

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/3145

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.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)
Metadata
None
None
None
None
Highest
None
None
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.