[389-users] Re: disk i/o: very high write rates

2018-08-09 Thread Ludwig Krispenz
On 08/09/2018 01:53 AM, William Brown wrote: In the audit-log there is nothing what would explain this. But in iotop I see a lot of threads like: The audit log itself (and search log) will generate IO themself :) 1621 be/4 dirsrv 0.00 B/s3.95 K/s 0.00 % 0.46 % ns-slapd -D /etc/di

[389-users] Re: Attempting to make memberUID searches case insensitive

2018-08-09 Thread Ludwig Krispenz
On 08/09/2018 02:04 AM, William Brown wrote: On Wed, 2018-08-08 at 07:23 -0500, Patrick Landry wrote: Here is the index definition: # memberuid, index, userRoot, ldbm database, plugins, config dn: cn=memberuid,cn=index,cn=userRoot,cn=ldbm database,cn=plugins,cn=config objectClass: top objectCl

[389-users] users ldap managment tool

2018-08-09 Thread Maria Tsiolakki
Hello We run ldap 389, here in a computer science department We need to have an easy management tool for setup and manage ldap accounts. Required functionalities among others are: *query users based on criteria i.e, select all users that belong to the same group, and  easily update their gid

[389-users] Re: Attempting to make memberUID searches case insensitive

2018-08-09 Thread Patrick Landry
So what is the point of adding the matching rule when defining the index? Is that simply so that the index is built with the *capability* of supporting searches using that matching rule explicitly? - Original Message - > From: "Ludwig Krispenz" > To: 389-users@lists.fedoraproject.or

[389-users] Re: users ldap managment tool

2018-08-09 Thread William Brown
On Thu, 2018-08-09 at 14:52 +0300, Maria Tsiolakki wrote: > Hello > We run ldap 389, here in a computer science department > We need to have an easy management tool for setup and manage ldap > accounts. Required functionalities among others are: > *query users based on criteria i.e, select all user

[389-users] Re: Attempting to make memberUID searches case insensitive

2018-08-09 Thread William Brown
On Thu, 2018-08-09 at 08:23 -0500, Patrick Landry wrote: > So what is the point of adding the matching rule when defining the > index? Is that > simply so that the index is built with the *capability* of supporting > searches using > that matching rule explicitly? I think it would be worth trying

[389-users] Re: Attempting to make memberUID searches case insensitive

2018-08-09 Thread Patrick Landry
Sorry. I did not answer your db2index question. I have two servers using multimaster replication and I did run db2index.pl on both servers after adding the index. As to Ludwig's suggestion, I can run the queries using ":caseIgnoreIA5Match:" in an extensible match search filter (memberuid:caseI

[389-users] Re: disk i/o: very high write rates

2018-08-09 Thread David Boreham
On 8/9/2018 2:44 AM, Ludwig Krispenz wrote: Sadly this doesn't tell us much :( we could get a pstack along with iotop to see which threads do teh IO, regular mods or the BDB regulars like trickle, checkpointing Also : strace ___ 389-users mail