Dear Maintainer,
*** Reporter, please consider answering these questions, where appropriate ***
* What exactly did you do (or not do) that was effective (or
ineffective)?
from console start nslcd , doesn't matter if nslcd -h, nslcd -d or nslcd is used.
* What was the outcome of this action?
The nslcd program starts using maximum available processor for a couple of minutes and then starts responding.
* What outcome did you expect instead?
The nslcd command should respond instantly to nslcd -h and nslcd -d and to basically and start method.
* Quick fix of issue
write ulimit -n 1024 before staring app (or add in startup script)
* Details about the error
I looked into the code and compiled it and found the latest daemonizer.c file has not been updated in three years
in the latest by the maintainers. In this file there is the function "closefrom" that solves the startup issues
which is not present in the shipped debian version.
In the shipped debian version sysconf(_SC_OPEN_MAX) returns a very large number running in Docker for some reason
that has the effect of making startup take minutes for this application. This can be fixed by using ulimit command
from shell to reduce the number of maximum open files. Similar issues exist in LDAP packages in debian resulting in
slow start and large resource usage (memory CPU), while it may be possible to fix using Docker settings having a
high max file limit should not cause issues for code to run.