One thing which seems to be missing from the current back-shell/back-sock
interface (and back-perl too for that matter) is access to state associated
with the request. The most important thing for me is the bind DN of the user
making the request. For example, a particular user might only be
On Sat, Oct 15, 2005 at 09:01:59AM -0700, Kurt D. Zeilenga wrote:
Passing the combined (TLS+SASL) SSF would be better.
Is that conn-c_ssf (= conn-c_authz.sai_ssf)?
At the moment I have
if( conn-c_dn.bv_len ) {
fprintf( fp, binddn: %s\n, conn-c_dn.bv_val);
}
The terminal escape sequences from 'make test outfile' can be a bit
annoying. It's not hard to say 'TERM=dumb make test outfile', but
I forget it now and then.
I'd like to wrap the code to find terminal escape sequences in configure
and 'make test' in 'if test -t 1', which checks if file
Hallvard B Furuseth wrote:
[EMAIL PROTECTED] writes:
Log Message:
ITS#4089 use slapcat -n XX to specify just the superior of a glued tree
It'll be a bit confusing that different ways to select a database gives
different result. I think a separate option would be better, with the
Howard Chu writes:
OK, suppose we add a -g option that disables glue completely?
Fine. Or possibly -G, since I have a vague feeling that uppercase
is more common for options that negate what they are named for.
--
Hallvard
At 12:28 PM 10/15/2005, Howard Chu wrote:
Hallvard B Furuseth wrote:
[EMAIL PROTECTED] writes:
Log Message:
ITS#4089 use slapcat -n XX to specify just the superior of a glued tree
It'll be a bit confusing that different ways to select a database gives
different result. I think a separate
Kurt D. Zeilenga wrote:
I've committed a revised lightweight dispatcher.
Aside from various cleanups (no suspend flags),
the main difference is writers are now spun out
into separate threads. Also, readers now spawn
operation threads instead of performing the
operation itself. This is to
At 12:55 PM 10/15/2005, Howard Chu wrote:
My perspective is the opposite
As long as both behaviors are possible, I don't care all
that much which is the default. Just stating a preference.
Kurt
Howard Chu wrote:
Yes. But that's still too messy; currently only the frontend de-queues
CSNs but there are several places that en-queue them (passwd.c,
sasl.c, various overlays) which means right now those places cause a
CSN memory leak. The cleanest solution now appears to be invoking the
At 09:34 AM 10/15/2005, Brian Candler wrote:
On Sat, Oct 15, 2005 at 09:01:59AM -0700, Kurt D. Zeilenga wrote:
Passing the combined (TLS+SASL) SSF would be better.
Is that conn-c_ssf (= conn-c_authz.sai_ssf)?
Yes, but you should values in the Operation structure
(likewise for other
10 matches
Mail list logo
