Re: [Bug 526141] allow empty groups
by Rich Megginson
bugzilla(a)redhat.com wrote:
> Please do not reply directly to this email. All additional
> comments should be made in the comments box of this bug.
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=526141
>
>
> Noriko Hosoi <nhosoi(a)redhat.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |nhosoi(a)redhat.com
> Devel Whiteboard|comment#1.review? |comment#1.review+nhosoi
>
Thanks - pushed to master
14 years, 8 months
Re: [Bug 520921] Config schema not included in core schema
by Rich Megginson
bugzilla(a)redhat.com wrote:
> Please do not reply directly to this email. All additional
> comments should be made in the comments box of this bug.
>
>
> https://bugzilla.redhat.com/show_bug.cgi?id=520921
>
>
> Nathan Kinder <nkinder(a)redhat.com> changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> CC| |nkinder(a)redhat.com
> Devel Whiteboard|comment#5.review? |comment#5.review+nkinder
>
Thanks - pushed to master
14 years, 8 months
Please review: Bug 520921 - Config schema not included in core schema
by Rich Megginson
https://bugzilla.redhat.com/show_bug.cgi?id=520921
Resolves: bug 520921
Bug Description: Config schema not included in core schema
Reviewed by: ???
Fix Description: Just had to move a few schema from 02common and
30ns-common into 01core389.ldif. I also added 01core389.ldif to the
list of schema installed when install_full_schema=0 is specified with
setup-ds.pl. I also added these schema files to the list of schema
files to upgrade.
With these changes, the server starts up fine. The only error is this:
[29/Sep/2009:16:47:53 -0600] - Entry "cn=PAM Pass Through
Auth,cn=plugins,cn
=config" has unknown object class "pamConfig"
This is because the pam pass through plugin is included in the
default config. I'd rather not move that schema file. That plugin can
be removed from the default config during setup by specifying a
slapd.ConfigFile directive with contents like this:
dn: cn=PAM Pass Through Auth,cn=plugins,cn=config
changetype: delete
Platforms tested: RHEL5 x86_64
Flag Day: no
Doc impact: no
https://bugzilla.redhat.com/attachment.cgi?id=363060&action=diff
14 years, 8 months
Please review: Bug 526319 - SASL IO sometimes loops with "error: would block"
by Rich Megginson
https://bugzilla.redhat.com/show_bug.cgi?id=526319
Resolves: bug 526319
Bug Description: SASL IO sometimes loops with "error: would block"
Reviewed by: ???
Fix Description: The semantics for recv() are that it returns -1 for
errors,
0 for connection closed, and non-zero for some bytes received. The
sasl code w
as not using those semantics - it was returning 0 for successful read
and -1 for
error. Although I have not been able to reproduce the exact failure,
what I be
lieve is happening is that the initial read of the packet length in
sasl_io_star
t_packet() works, and the sasl IO is received. At some point, the
connection is
closed by the client, and the PR_Recv return of 0 is not handled
correctly,
and somehow the errno gets set to EWOULDBLOCK. From this point on,
PR_Recv() wi
ll return -1 (since the socket has been closed) and errno is not reset
from EWOU
LDBLOCK.
The fix is to make sure the sasl IO code handles the PR_Recv()
return value
correctly.
Note that with CONNS (8) error log level, you may still occasionally
see "wo
uld block" errors, but as long as they are not endlessly repeating, this
should
be ok.
Platforms tested: RHEL5 x86_64
Flag Day: no
Doc impact: no
https://bugzilla.redhat.com/attachment.cgi?id=363058&action=diff
14 years, 8 months