Now that this file is taking on the nature of a help file, I've
attempted to improve its readability, with:
1. Minor layout changes (whitespace between sections)
2. Spell check, inc. s/backend/back end (standardization)
3. General copy-edit
Pretty trivial stuff.
--
David O'Brien
Senior Technic
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2010 09:27 AM, David O'Brien wrote:
> Now that this file is taking on the nature of a help file, I've
> attempted to improve its readability, with:
>
> 1. Minor layout changes (whitespace between sections)
> 2. Spell check, inc. s/backend/bac
Jakub Hrozek wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2010 09:27 AM, David O'Brien wrote:
Now that this file is taking on the nature of a help file, I've
attempted to improve its readability, with:
1. Minor layout changes (whitespace between sections)
2. Spell check, inc.
Hi,
the ldap_access_filter patch introduces a check if the LDAP id provider
is already initialized so that the LDAP access provider can use the same
global connection as the id provider. This worked in tests because two
errors (missing '==0' and wrong case) were canceling each other. But it
would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2010 10:15 AM, Sumit Bose wrote:
> Hi,
>
> the ldap_access_filter patch introduces a check if the LDAP id provider
> is already initialized so that the LDAP access provider can use the same
> global connection as the id provider. This worked
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 05/19/2010 01:04 AM, David O'Brien wrote:
> Recently it was recommended that I not include the LOCAL domain, nested
> groups, and related functionality in the end-user doc (limiting it to
> the man pages). This raises the following issue:
>
> The
On May 19, 2010, at 3:46 AM, Jakub Hrozek wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/19/2010 09:27 AM, David O'Brien wrote:
>> Now that this file is taking on the nature of a help file, I've
>> attempted to improve its readability, with:
>>
>> 1. Minor layout changes (whit
Great catch. I also ack.
On May 19, 2010, at 4:15 AM, Sumit Bose wrote:
> Hi,
>
> the ldap_access_filter patch introduces a check if the LDAP id
> provider
> is already initialized so that the LDAP access provider can use the
> same
> global connection as the id provider. This worked in tests be
On May 19, 2010, at 4:51 AM, Jakub Hrozek wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> On 05/19/2010 01:04 AM, David O'Brien wrote:
>> Recently it was recommended that I not include the LOCAL domain,
>> nested
>> groups, and related functionality in the end-user doc (limiting it t
Stephen Gallagher wrote:
> On May 19, 2010, at 4:51 AM, Jakub Hrozek wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 05/19/2010 01:04 AM, David O'Brien wrote:
>>> Recently it was recommended that I not include the LOCAL domain,
>>> nested
>>> groups, and related functionalit
Stephen Gallagher wrote:
> On May 19, 2010, at 3:46 AM, Jakub Hrozek wrote:
>
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 05/19/2010 09:27 AM, David O'Brien wrote:
>>> Now that this file is taking on the nature of a help file, I've
>>> attempted to improve its readability, with:
1. In the option "ldap_opt_timeout", where does the "opt" come from? Is
it just short for "option"?
2. A question arose today about how to determine which options are
mandatory and which are not in any given SSSD config. I've since found a
few cases where "optional" is included as part of the d
On 05/19/2010 08:24 AM, David O'Brien wrote:
> Stephen Gallagher wrote:
>> On May 19, 2010, at 4:51 AM, Jakub Hrozek wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 05/19/2010 01:04 AM, David O'Brien wrote:
Recently it was recommended that I not include the LOCAL do
On 05/19/2010 08:33 AM, David O'Brien wrote:
> 1. In the option "ldap_opt_timeout", where does the "opt" come from? Is
> it just short for "option"?
It comes from the LDAP API call to set options. I'm not sure we
necessarily want to document this, as it's pretty low-level. Really all
it does is
On 05/19/2010 08:30 AM, David O'Brien wrote:
> Stephen Gallagher wrote:
>> On May 19, 2010, at 3:46 AM, Jakub Hrozek wrote:
>>
>>> -BEGIN PGP SIGNED MESSAGE-
>>> Hash: SHA1
>>>
>>> On 05/19/2010 09:27 AM, David O'Brien wrote:
Now that this file is taking on the nature of a help file,
On 05/19/2010 03:58 AM, David O'Brien wrote:
> Jakub Hrozek wrote:
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> On 05/19/2010 09:27 AM, David O'Brien wrote:
>>> Now that this file is taking on the nature of a help file, I've
>>> attempted to improve its readability, with:
>>>
>>> 1. Mi
Addresses https://fedorahosted.org/sssd/ticket/476
--
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
From b9b5a76bb26acfd537c6438124349e2110103c82 Mon Sep 17 00:00:00 2001
From: Stephe
Hi,
the patch adds a small delay to sbus_dispatch() to avoid log flooding.
bye,
Sumit
From 25c3ada18e44032cd6a2416914bac628a7034c55 Mon Sep 17 00:00:00 2001
From: Sumit Bose
Date: Wed, 19 May 2010 17:49:45 +0200
Subject: [PATCH] Defer sbus_dispatch() for 30ms during reconnect
---
src/sbus/sssd
On 05/19/2010 12:04 PM, Sumit Bose wrote:
> Hi,
>
> the patch adds a small delay to sbus_dispatch() to avoid log flooding.
>
Ack.
--
Stephen Gallagher
RHCE 804006346421761
Delivering value year after year.
Red Hat ranks #1 in value among software vendors.
http://www.redhat.com/promo/vendor/
___
Stephen Gallagher wrote:
> Addresses https://fedorahosted.org/sssd/ticket/476
>
>
>
>
> ___
> sssd-devel mailing list
> sssd-devel@lists.fedorahosted.org
> https://fedorahosted.or
Stephen Gallagher wrote:
> On 05/19/2010 08:33 AM, David O'Brien wrote:
>> 1. In the option "ldap_opt_timeout", where does the "opt" come from? Is
>> it just short for "option"?
>
> It comes from the LDAP API call to set options. I'm not sure we
> necessarily want to document this, as it's pretty
21 matches
Mail list logo
