PR - Issue 49731 - set and use db_home_directory by default

[389-ds-bot]

Cloned from Pagure Pull-Request: https://pagure.io/389-ds-base/pull-request/50959

• Created at 2020-03-16 17:47:25 by mreynolds (@mreynolds389)
• Merged at 2020-03-25 19:32:11

---

Description:

New instances will automatically create and use db_home_dir /dev/shm/dirsrv/slapd-INSTANCE.

relates: Resolves: #2790

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2020-03-16 18:16:52

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 ?

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-03-16 19:14:38

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?

[389-ds-bot]

Comment from firstyear (@Firstyear) at 2020-03-17 00:18:55

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. :)

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-03-18 17:10:19

rebased onto b097eadfffda2be904ff9ca8cda1f6f38398d32c

[389-ds-bot]

Comment from tbordaz (@tbordaz) at 2020-03-25 18:11:46

The patch looks good to me. Ack

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-03-25 19:23:39

rebased onto 96c8abb

[389-ds-bot]

Comment from mreynolds (@mreynolds389) at 2020-03-25 19:32:12

Pull-Request has been merged by mreynolds389

[389-ds-bot]

Patch
50959.patch