[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ldap
Subject:    Re: Can't run ldif2ldbm anymore
From:       Griff Miller II <griff.miller () pgs ! com>
Date:       1998-06-25 3:12:19
[Download RAW message or body]

I wrote:
>
> I believe the only thing that has changed is that I installed
> the crypt patch at http://www3.innosoft.com/ldapworld/patch/crypt.patch.txt .
> 
> Solaris 2.6, gcc 2.7.2 . truss gives a lot of this:
> 
> getpid()                                        = 9250 [9249]
> signotifywait()                                 Err#4 EINTR
> lwp_mutex_lock(0xEF7998A8)                      Err#4 EINTR
> door_return(0x00000004, 0, 0x00000000, 0)       Err#4 EINTR
> getpid()                                        = 9250 [9249]
> signotifywait()                                 Err#4 EINTR
> lwp_mutex_lock(0xEF7998A8)                      Err#4 EINTR
> door_return(0x00000004, 0, 0x00000000, 0)       Err#4 EINTR
> getpid()                                        = 9250 [9249]
> signotifywait()                                 Err#4 EINTR
> lwp_mutex_lock(0xEF7998A8)                      Err#4 EINTR
> door_return(0x00000004, 0, 0x00000000, 0)       Err#4 EINTR
> 
> Help!

Okay, I got around the problem. I used the -d255 flag to
ldif2ldbm and figured out that it didn't like one of the
two following lines in my slapd.conf:

access to dn=".*,o=Acme,c=US" by self write
access to dn=".*,l=Houston,ou=Anvils,o=Acme,c=US" by
dn="uid=bob,l=Houston,ou=Anvils,o=Acme,c=US" write

I think it was the first one it didn't like. In fact, I am 99.9% positive.
When I commented it out, ldif2ldbm ran fine.

What did I do wrong? I have just about all the patches installed
from the Critical Angle site.

-- 
Griff Miller II
Senior Unix/NT Sysadmin
PGS Tensor - Houston, TX           -- Measure twice. Cut once. --
griff.miller@pgs.com

[prev in list] [next in list] [prev in thread] [next in thread]