This ticket allows to disable the instance dir. Ticket #47840 - add configure option to disable instance specific scripts
Currently, the instance dir and the instance specific scripts are generated by default. But it may be altered some time.
Date: Thu Apr 7 14:59:06 2016 +1000 Bug Description: During the change, 47840, per instance scripts defaulted to false if not defined in setup.inf. Fix Description: reset the default to true, and allow setting to false if required. This may change in a future release.
Before it occurs, the paths and the options for these scripts need to be adjusted. $ egrep "instdir|instancedir" *.pl 70upgradefromldif.pl: my $instdir = $config_entry->getValues('nsslapd-instancedir'); 70upgradefromldif.pl: @errs = importLDIF($conn, $file, $dbinst, $isrunning, $instdir); 70upgradefromldif.pl: my ($conn, $file, $be, $isrunning, $instdir, $rc) = @_; 70upgradefromldif.pl: if ($rc = system("$instdir/ldif2db -n $be -i $file > /dev/null 2>&1")) { 82targetuniqueidindex.pl: my $instancedir = $config->getValues('nsslapd-instancedir'); 82targetuniqueidindex.pl: my $reindex = $instancedir . "/db2index"; 90subtreerename.pl: my $instdir = $ent0->getValue('nsslapd-instancedir'); 90subtreerename.pl: my $prog = $instdir . "/dn2rdn"; 91reindex.pl: my $instancedir = $config->getValues('nsslapd-instancedir'); 91reindex.pl: my $reindex = $instancedir . "/db2index"; 91subtreereindex.pl: my $instancedir = $config->getValues('nsslapd-instancedir'); 91subtreereindex.pl: my $reindex = $instancedir . "/db2index";
This ticket needs to be evaluated when the instance dir is disabled by default.
Setting the target milestone to 1.4. (See also -- https://fedorahosted.org/389/ticket/47840#comment:19)
Metadata Update from @nhosoi: - Issue set to the milestone: 1.4 backlog
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/1902
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
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)
Login to comment on this ticket.