Groups > linux.debian.user > #193520

Re: Open socket not connected to any real process

From	Sven Hartge <sven@svenhartge.de>
Newsgroups	linux.debian.user
Subject	Re: Open socket not connected to any real process
Date	2018-03-08 13:30 +0100
Message-ID	<vr2Qi-6Q3-3@gated-at.bofh.it> (permalink)
References	<vqODE-5Fx-7@gated-at.bofh.it> <vqP6F-5P2-11@gated-at.bofh.it> <vqPq1-6e6-3@gated-at.bofh.it> <vqTah-Eg-1@gated-at.bofh.it>
Organization	Newsfeed am Wurmloch

Show all headers | View raw

Roberto C. Sánchez <roberto@debian.org> wrote:
> On Wed, Mar 07, 2018 at 11:08:05PM +0100, Sven Hartge wrote:
 
>> This is why you use libpam-ldapd (instead of libpam-ldap) in
>> combination with libnss-ldapd (instead of libnss-ldap).
>> 
>> Its design with a separate daemon (nslcd) doing the actual LDAP
>> connection is far superior compared to the original lib*-ldap code.
>> 
>> It also means that libldap itself is only mapped into the central
>> server process and not into every process on the system. 
 
> Personally, I found sssd (along with libpam-sss and libnss-sss) to be
> much better behaved.

Yes, also a very valid alternative, much more so, if Active Directory is
involved.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

Back to linux.debian.user | Previous | Next — Previous in thread | Find similar | Unroll thread

Thread

Open socket not connected to any real process David Parker <dparker@utica.edu> - 2018-03-07 22:20 +0100
  Re: Open socket not connected to any real process David Parker <dparker@utica.edu> - 2018-03-07 22:50 +0100
    Re: Open socket not connected to any real process Sven Hartge <sven@svenhartge.de> - 2018-03-07 23:10 +0100
      Re: Open socket not connected to any real process Roberto C. Sánchez <roberto@debian.org> - 2018-03-08 03:10 +0100
        Re: Open socket not connected to any real process Sven Hartge <sven@svenhartge.de> - 2018-03-08 13:30 +0100

csiph-web