Re: NSLCD: Resource temporarily unavailable

[Arthur de Jong <arthur [at] arthurdejong.org>]

On Wed, 2014-01-22 at 14:16 +0100, Alexey Tyurikov wrote:
> nslcd: DEBUG: accept() failed (ignored): Resource temporarily
> unavailable

This message is to be expected and can be safely ignored. It means the
call to accept() was interrupted by a signal and nslcd will retry the
call.

> Furthermore crashes nslcd after few minutes, sometimes few hours.

Can you provide a backtrace of these crashes? To run nslcd under gdb:

  # gdb nslcd
  ...
  (gdb) r -d
  ...
  (gdb) thread apply all bt full

Or perhaps run under valgrind (not sure it is available on FreeBSD):

  valgrind -v --track-origins=yes --leak-check=full nslcd  -d

Are there any special requests that seem to trigger the crash?

Thanks,

-- 
-- arthur - arthur@arthurdejong.org - http://arthurdejong.org/ --

-- 
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/