#469 unable to specify separate db home dir
Closed: wontfix None Opened 8 years ago by rmeggins.

I'm trying to setup a server which uses /dev/shm as the db home dir. So I have

dn: cn=config,cn=ldbm database,cn=plugins,cn=config
nsslapd-db-home-directory: /dev/shm/dbhome
nsslapd-directory: /home/rich/389srv/var/lib/dirsrv/slapd-1389/db

When you specify this via ConfigFile in setup-ds.pl, the first import stage doesn't work. It uses /dev/shm/dbhome as the data dir root and creates /dev/shm/dbhome/userRoot.


Note that it works fine if you edit nsslapd-db-home-directory after the server has been set up, it just doesn't work if you try to set it up at setup time.

Reading check_and_add_entry in DSUtil.pm.in, it looks you need to have "changetype" in the file as follows:
{{{
$ cat ConfigFile.txt
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-db-home-directory
nsslapd-db-home-directory: /tmp/dbhome

dn: cn=config,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-directory
nsslapd-directory: /tmp/dbdir
}}}

This command line works for me:
{{{
setup-ds.pl slapd.ConfigFile=/path/to/ConfigFile.txt
}}}

One defect is this '-' separated modifies is not supported...
{{{
dn: cn=config,cn=ldbm database,cn=plugins,cn=config
changetype: modify
replace: nsslapd-db-home-directory
nsslapd-db-home-directory: /tmp/dbhome
-
replace: nsslapd-directory
nsslapd-directory: /tmp/dbdir
}}}
Do you think it's acceptable?

Yes, I think that's fine. Thanks for checking it out.

Metadata Update from @rmeggins:
- Issue assigned to nhosoi
- Issue set to the milestone: N/A

4 years ago

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

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 (was: Invalid)

7 months ago

Login to comment on this ticket.

Metadata