-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rich,
Thanks for writing back. I opened Ticket #44708. I'm going through
the CLI suggestions now.
Thanks,
ep
On 02/18/2014 06:11 PM, Rich Megginson wrote:
>> Please file a ticket at https://fedorahosted.org/389/newticket
>
>> In the meant
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rich and 389-users,
I followed the directions on the page you had sent,
https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Configuring_Directory_Databases.html#Creating_and_Maintaining_Suf
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Ah, I think I see the error of my ways. I blind copied the
"nsslapd-backend: GroupData" from the webpage, not realizing that this
was the name of the database for the sub suffix.
I'll try it again and give a unique database for each dc I add.
Thanks
On 02/19/2014 12:38 PM, Brian Epstein wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rich and 389-users,
I followed the directions on the page you had sent,
https://access.redhat.com/site/documentation/en-US/Red_Hat_Directory_Server/9.0/html/Administration_Guide/Configuring_Direct
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Rich,
Thanks again for your help. Now that I have created the sub
suffices, I figured out that I also needed to create the databases. I
did this by adding the following.
dn: cn=SNS,cn=ldbm database,cn=plugins,cn=config
changetype: add
objec
Hi all,
We've just set up monster-sized server nodes to run 389 as a replacement to Sun
DS. I've been running my tests and I am pleased to report that the memory
issue seems to be in check with growth only up to double the initial memory
usage after large quantities of ldapmodify calls. We ha
On 02/19/2014 04:56 PM, Russell Beall wrote:
Hi all,
We've just set up monster-sized server nodes to run 389 as a
replacement to Sun DS. I've been running my tests and I am pleased to
report that the memory issue seems to be in check with growth only up
to double the initial memory usage aft
