[Date Prev][Date Next] [Chronological] [Thread] [Top]

Raising a INT signal to stop the slapd daemon causes an infinite loop (ITS#1614)

Full_Name: Benoît Gilon
Version: 2.0.23
OS: Windows 2000 Professional SP2 - Cygwin 1.3.9-1
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (


The Open LDAP deployment uses the Berkeley DB 4 as recommended.
The executables were built from the sources with the sequence below:

env "CPPFLAGS=-I/usr/local/BerkeleyDB.4.0/include"
"LDFLAGS=-L/usr/local/BerkeleyDB.4.0/lib" ./configure
make depend
make install

The slapd daemon was started using the command line below
cd /usr/local/libexec; ./slapd.exe -u Administrator -g None -d 255

as I submit the command below in another bash window:
$ kill -INT `cat /usr/local/var/slapd.pid`
The line below is displayed in the first terminal window (from which I started
the server) in an infinite loop.

daemon: select: listen=5 active_hreads=0 tvp=NULL\n

I have to submit a kill -KILL to the slapd process in order to kill the process
which I understand might lead to database consistency problems upon next

I understand that many components might interfere (W2000 network layer, Cygwin
emulation, Threads support, GNU compiler release).
Thus I am ready to provide you with more info per our request.

I found no bug already registered which perfectly match the symptom I describe.
I submitted queries as described in the Quick start guide using the ldapsearch
client tool and it works great so that it's more an annoyance than a real pain
to me (the deplyment is only a test environment).

Thank you for reading,
Benoît Gilon