Hallvard B Furuseth wrote:
> hyc(a)symas.com writes:
> I suppose there could be a flag to _not_ start the indexing task when
> you add an index via cn=config, so you always must slapindex.
I'd rather not.
>> I suppose we should save the last entryID that was indexed at shutdown time,
>> so that the indexer task can resume at the next startup. We'd also need some
>> coordination with slapindex, so that if you ran slapindex after shutdown, it
>> would erase the saved status. Rather than add any fields to the DB index
>> files, it would probably be OK to write the status in the cn=config tree.
>
> Or a status file in the database directory.
>
> A cn=config attribute would make it messy to swap database directories
> around, since one must also modify cn=config when doing so.
OK, a status file. It would record the old and new index masks for the
attributes being reindexed, and the entryID where it stopped.
If slapindex is run without a specific list of attributes, (reindex
everything) it should remove and ignore the status file.
If slapindex is run with a specific list of attributes, and those attributes
are in the status file, it should use the saved status and remove the
specified attributes from the status file. (Deleting the file if there are no
other attributes remaining.)
Otherwise, when slapd starts, it should read the status file and resume the
indexing task.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
jwm(a)horde.net wrote:
> Full_Name: John Morrissey
> Version: 2.4.16
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (2001:4978:194:0:21f:5bff:fee9:da92)
>
> Looking back through the call chain, do_syncrepl() sets op->o_tmpmemctx to
> NULL:
>
> /* use global malloc for now */
> op->o_tmpmemctx = NULL;
> op->o_tmpmfuncs =&ch_mfuncs;
This should be removed.
> so generalizedTimeIndexer()'s call to slap_sl_malloc() falls back to
> ber_memalloc_x() due to the null ctx. If malloc() fails there, NULL is
> eventually returned to the original caller of slap_sl_malloc(), likely resulting
> in a segfault.
And slap_sl_malloc() should be changed in this case to assert() just like
ch_malloc() does.
> All of the indexing routines seem to ignore slap_sl_malloc()'s return value,
> opening them up to this problem, too. Someone else will need to step in with a
> proper fix since I don't know much about slapd internals, but it seems that if
> these routines are being called with a deliberate null ctx, they should be
> checking for malloc failure. A cursory glance around back-bdb indicates that
> indexing function callers already handle failure return codes gracefully.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: John Morrissey
Version: 2.4.16
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (2001:4978:194:0:21f:5bff:fee9:da92)
tlsg_ctx_init() doesn't initialize the gnutls_x509_privkey_t structure before
passing it to gnutls_x509_privkey_import. This yields:
main: TLS init def ctx failed: -50
on slapd startup. gnutls error -50 is GNUTLS_E_INVALID_REQUEST. Initializing the
structure with gnutls_x509_privkey_init() allows slapd startup to succeed.
[jwm@coral.lab.isis:pts/1 ~> dpkg -l libgnutls26
[...]
ii libgnutls26 2.6.4-2 the GNU TLS library - runtime library
--- openldap-2.4.16.orig/libraries/libldap/tls_g.c
+++ openldap-2.4.16/libraries/libldap/tls_g.c
@@ -354,6 +354,9 @@
gnutls_x509_crt_t certs[VERIFY_DEPTH];
unsigned int max = VERIFY_DEPTH;
+ rc = gnutls_x509_privkey_init(&key);
+ if ( rc < 0 ) return -1;
+
/* OpenSSL builds the cert chain for us, but GnuTLS
* expects it to be present in the certfile. If it's
* not, we have to build it ourselves. So we have to
luca.scamoni(a)sys-net.it ha scritto:
> luca.scamoni(a)sys-net.it ha scritto:
New update
The problem is still there. Same call in bdb_rdn_cmp.
strncmp fails because one of the berval passed to the function has
inconsistent values between bv_len and bv_val
Ing. Luca Scamoni
Responsabile Ricerca e Sviluppo
SysNet s.r.l.
via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
-----------------------------------
Office: +39 0382 573859 (137)
Fax: +39 0382 476497
Email: luca.scamoni(a)sys-net.it
-----------------------------------
Full_Name: Kostas Kalevras
Version: 2.4
OS: FreeBSD
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (147.102.247.75)
In OpenLDAP 2.4 Administration Guide, chapter 15 (Using SASL) in
15.3.3.1. Notes on Proxy Authorization Rules
the documentation states that the administrator can use regular expression
matching like:
authzTo: dn.regex=^uid=[^,]*,dc=example,dc=com$
I believe the correct form should be:
authzTo: dn.regex:"^uid=[^,]*,dc=example,dc=com$"
Notice the : instead of = and the quotes around the regular expression.
Full_Name: Hendrik Saly
Version: JLDAP 4.3
OS: Linux 2.6, Sun JDK 1.5
URL: http://svn.muleforge.org/mule-transport-ldap/trunk/src/main/java/com/novell…
Submission from: (NULL) (78.43.136.21)
While trying to use SASL with JLDAP i encounter a potential minor bug in
$OpenLDAP: pkg/jldap/com/novell/ldap/LDAPConnection.java,v 1.154 2006/02/09
08:43:45 sunilk Exp $
Seems the bind method on line 1730 fails to release the bind semaphore properly
under some circumstances. I tried to use more than the wit JLDAP provided SASL
mechanisms DIGESTMD5 and EXTERNAL by wrapping the novell sasl client with a Java
1.5 sasl client. All works very well but CRAM login for example fails. I have a
workaround http://svn.muleforge.org/mule-transport-ldap/trunk/src/main/java/com/novell…
but i thinks there are some problems with the bind semaphore.
The wrapping code is here
http://svn.muleforge.org/mule-transport-ldap/trunk/src/main/java/org/mule/t…
If neccessary i can provide a test suite for this.
Thanks
Hendrik
tmackey(a)zetta.net wrote:
> Full_Name: Theral Mackey
> Version: 2.4.16
> OS: Linux/Debian
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (216.200.8.2)
>
>
> Running make install leaves an existing slapd.conf alone, but happily nukes and
> replaces the existing schema directory, taking with it any additional or custom
> schema, leaving you with only the ones installed by default (hooray for svn and
> backups!).
No, it doesn't.
> For consistency, it should probably either nuke slapd.conf as well, or leave an
> existing schema dir alone (I vote for option 2).
> fix should be as simple as an 'if [ ! -d $base/schema ] ; then (mkdir, cp
> schemas, etc) ; fi' around where it drops the schemas in place in the Makefile
Since you're already looking in the Makefile, you should see this for the
install-schema: rule...
###
install-schema: FORCE
@if test -d $(DESTDIR)$(schemadir) ; then \
echo "MOVING EXISTING SCHEMA DIR to $(DESTDIR)$(schemadir).$$$$" ; \
mv $(DESTDIR)$(schemadir) $(DESTDIR)$(schemadir).$$$$ ; \
fi
$(MKDIR) $(DESTDIR)$(schemadir)
###
The existing schema directory is simply renamed / moved out of the way. If you
had any custom schema files stored there, they are still there.
This ITS will be closed.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
Full_Name: Theral Mackey
Version: 2.4.16
OS: Linux/Debian
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (216.200.8.2)
Running make install leaves an existing slapd.conf alone, but happily nukes and
replaces the existing schema directory, taking with it any additional or custom
schema, leaving you with only the ones installed by default (hooray for svn and
backups!).
For consistency, it should probably either nuke slapd.conf as well, or leave an
existing schema dir alone (I vote for option 2).
fix should be as simple as an 'if [ ! -d $base/schema ] ; then (mkdir, cp
schemas, etc) ; fi' around where it drops the schemas in place in the Makefile