Re: [SSSD] LDAP connection tracking, sharing and fail-over retry framework

2010-07-02 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2010 11:35 AM, Eugene Indenbom wrote: > The complete set of patches for LDAP connection framework is attached: > > 0001-GSSAPI-ticket-expiry-time-is-returned-from-ldap_chil.patch > 0002-Added-an-interface-to-query-number-of-configured

[SSSD] Eliminate delayed sdap_handle destruction after fail-over retry.

2010-07-02 Thread Eugene Indenbom
The patch attached addresses the following issue: Prerequisites: 1. One or more fail-over server is configured; 2. The first server to try can be resolved but LDAP service is down; 3. There is at least one operational LDAP server configured; Synopsis: 1. sdap_async_connection.c tries to connect

Re: [SSSD] [PATCH] Log TLS errors to syslog

2010-07-02 Thread Dmitri Pal
Stephen Gallagher wrote: > On 07/02/2010 09:51 AM, Dmitri Pal wrote: > > Stephen Gallagher wrote: > >> Also adds support for detecting LDAPS errors by adding a check for > >> SDAP_DIAGNOSTIC_MESSAGE after ldap_search_ext() > >> > >> This should make debugging an initial setup easier, as the most co

Re: [SSSD] [PATCH] Add syslog messages for LDAP GSSAPI bind

2010-07-02 Thread Dmitri Pal
Stephen Gallagher wrote: > On 07/02/2010 09:37 AM, Dmitri Pal wrote: > > Nack > > > You are leaking entry in success scenario. > > I suggest a little bit cleaner approach: > > > while((ret = krb5_kt_next_entry(context, keytab, &entry, &cursor)) > > == 0){ > > krb5_unparse_name(context,

Re: [SSSD] [PATCH] Log TLS errors to syslog

2010-07-02 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2010 09:51 AM, Dmitri Pal wrote: > Stephen Gallagher wrote: >> Also adds support for detecting LDAPS errors by adding a check for >> SDAP_DIAGNOSTIC_MESSAGE after ldap_search_ext() >> >> This should make debugging an initial setup easier, as t

Re: [SSSD] [PATCH] Add syslog messages for LDAP GSSAPI bind

2010-07-02 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2010 09:37 AM, Dmitri Pal wrote: > Nack > > You are leaking entry in success scenario. > I suggest a little bit cleaner approach: > > while((ret = krb5_kt_next_entry(context, keytab, &entry, &cursor)) > == 0){ > krb5_unparse_name

Re: [SSSD] [PATCH] Log TLS errors to syslog

2010-07-02 Thread Dmitri Pal
Stephen Gallagher wrote: > Also adds support for detecting LDAPS errors by adding a check for > SDAP_DIAGNOSTIC_MESSAGE after ldap_search_ext() > > This should make debugging an initial setup easier, as the most common > configuration errors will appear in /var/log/messages, instead of > requiring

Re: [SSSD] [PATCH] Add try_inotify option

2010-07-02 Thread Jakub Hrozek
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/30/2010 08:25 PM, Dmitri Pal wrote: > Stephen Gallagher wrote: >> > There are some special cases where inotify cannot be used, even if >> > the host OS claims that it is supported. In these cases, it should >> > be possible to explicitly disable

Re: [SSSD] [PATCH] Add syslog messages for LDAP GSSAPI bind

2010-07-02 Thread Dmitri Pal
Stephen Gallagher wrote: > On 07/02/2010 07:59 AM, Stephen Gallagher wrote: > > On 07/01/2010 02:18 PM, Stephen Gallagher wrote: > >> We will now emit a level 0 debug message on keytab errors, and > >> also write to the syslog (LOG_AUTHPRIV) > >> Resolves: > >> https://bugzilla.redhat.com/show_bug.

Re: [SSSD] [PATCH] Log TLS errors to syslog

2010-07-02 Thread Jeff Schroeder
On Fri, Jul 2, 2010 at 5:52 AM, Stephen Gallagher wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Also adds support for detecting LDAPS errors by adding a check for > SDAP_DIAGNOSTIC_MESSAGE after ldap_search_ext() > > This should make debugging an initial setup easier, as the most co

[SSSD] [PATCH] Log TLS errors to syslog

2010-07-02 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Also adds support for detecting LDAPS errors by adding a check for SDAP_DIAGNOSTIC_MESSAGE after ldap_search_ext() This should make debugging an initial setup easier, as the most common configuration errors will appear in /var/log/messages, instead of

Re: [SSSD] [PATCH] Add syslog messages for LDAP GSSAPI bind

2010-07-02 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/02/2010 07:59 AM, Stephen Gallagher wrote: > On 07/01/2010 02:18 PM, Stephen Gallagher wrote: >> We will now emit a level 0 debug message on keytab errors, and >> also write to the syslog (LOG_AUTHPRIV) > >> Resolves: >> https://bugzilla.redhat.

Re: [SSSD] [PATCH] Add syslog messages for LDAP GSSAPI bind

2010-07-02 Thread Stephen Gallagher
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 07/01/2010 02:18 PM, Stephen Gallagher wrote: > We will now emit a level 0 debug message on keytab errors, and > also write to the syslog (LOG_AUTHPRIV) > > Resolves: > https://bugzilla.redhat.com/show_bug.cgi?id=591677 > https://fedorahosted.org/s