Re: (ITS#7072) caseIgnoreMatch equals regular capital I with dotted capital I
by hyc＠symas.com
Frank.Meisschaert(a)UGent.be wrote:
> Full_Name: Frank Meisschaert
> Version: 2.4.26
> OS: linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (157.193.44.200)
>
>
> When I try to add the names "İsmail" (original, with dotted capital I) and
> "Ismail" (transcribed, regular capital I) to an entry using ldapmodify:
>
> dn: ...
> changetype: modify
> replace: givenName
> givenName: Ismail
> givenName:: xLBzbWFpbA==
> -
>
> I get the error:
>
> ldap_modify: Type or value exists (20)
> additional info: givenName: value #0 provided more than once
>
> The lowercase version of dotted and regular capital I is regular i which
> explains this error. However according to unicode case folding the dotted
> capital I should be mapped to 0069 0307 (i, combining dot above) which would
> make Ismail andİsmail different when compared case-insensitively as I
> would expect.
Apparently our liblunicode implementation doesn't use the CaseFolding data. I
believe that means our implementation corresponds to the "Simple" case folding
rules. They're valid, just not doing what you want in this case. So it appears
that this is an enhancement request.
I don't believe this request warrants a very high priority. Looking at the
Unicode charts, I-with-dot-above is the only character where the two case
folding alternatives actually makes a difference.
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
11 years, 7 months
(ITS#7074) back-ldap module compilation issue with gcc 4.6.1
by stephane.paquot＠gmail.com
Full_Name: Stéphane PAQUOT
Version: 2.4.26
OS: Windows (MingW)
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (83.194.186.14)
Hi
I am actually compiling backend modules for openldap 2.4.26 with MingW (gcc
version 4.6.1, GNU make 3.81, GNU libtool 2.4, GNU automake 1.11.1, GNU autoconf
2.68.
An issue occurs when compiling back-ldap module.
The GNU tools used are the following :
host-triplet: i686-pc-mingw32
shell: /bin/sh
compiler: gcc
compiler flags: -O3 -s -mms-bitfields -march=i386 -mtune=i686
linker: c:/mingw/mingw32/bin/ld.exe (gnu? yes)
libtool: (GNU libtool) 2.4
automake: automake (GNU automake) 1.11.1
autoconf: autoconf (GNU Autoconf) 2.68
The command line to compile openldap 2.4.26 is the following
./configure --prefix=/software/openldap \
--enable-slapd \
--enable-modules \
--enable-rewrite \
--enable-bdb=mod \
--enable-hdb=mod \
--enable-ldap=mod \
--enable-sql=mod \
--enable-monitor=mod \
--enable-accesslog=mod \
--enable-auditlog=mod \
--enable-rwm=mod \
--enable-syncprov=mod \
--with-odbc=odbc32 \
--with-tls=openssl \
--without-cyrus-sasl
Here are the compilation flags :
CPPFLAGS="-I/software/openssl/include
-I/software/berkeleydb/berkeleydb-5.2/include"
LDFLAGS="-I/software/openssl/lib -I/software/berkeleydb/berkeleydb-5.2/lib"
LIBS="-lodbc32 -lws2_32"
All backends modules and overlays compile fine but when compiling backend
back-ldap as a module, the following compile error occurs : error: initializer
element is not constant.
$ make
/bin/sh ../../../libtool --tag=disable-static --mode=compile gcc -g -O2
-std=c89
-I../../../include -I../../../include -I.. -I./..
-I/software/openssl/i
nclude -I/software/berkeleydb/berkeleydb-5.2/include -DSLAPD_IMPORT -c
chain.c
gcc -g -O2 -std=c89 -I../../../include -I../../../include -I.. -I./..
-I/softwa
re/openssl/include -I/software/berkeleydb/berkeleydb-5.2/include -DSLAPD_IMPORT
-c chain.c -DDLL_EXPORT -DPIC -o .libs/chain.o
chain.c:1273:3: error: initializer element is not constant
chain.c:1273:3: error: (near initialization for 'chainocs[1].co_table')
make: *** [chain.lo] Error 1
gcc 4.6.1 complains about
static ConfigOCs chainocs[] = {
{ "( OLcfgOvOc:3.1 "
"NAME 'olcChainConfig' "
"DESC 'Chain configuration' "
"SUP olcOverlayConfig "
"MAY ( "
#ifdef LDAP_CONTROL_X_CHAINING_BEHAVIOR
"olcChainingBehavior $ "
#endif /* LDAP_CONTROL_X_CHAINING_BEHAVIOR */
"olcChainCacheURI $ "
"olcChainMaxReferralDepth $ "
"olcChainReturnError "
") )",
Cft_Overlay, chaincfg, NULL, chain_cfadd },
{ "( OLcfgOvOc:3.2 "
"NAME 'olcChainDatabase' "
"DESC 'Chain remote server configuration' "
"AUXILIARY )",
Cft_Misc, olcDatabaseDummy, chain_ldadd
#ifdef SLAP_CONFIG_DELETE
, NULL, chain_lddel
#endif
},
{ NULL, 0, NULL}
};
I try to solve this problem but I'm a little stuck. When back-ldap is not
compiled as a module, no problem, slapd compiles fine with this backend
back-ldap.
Best regards and many thanks to you.
Stéphane PAQUOT
Database Administrator (Sybase, Oracle, MS SQL Server, MySQL).
France, Paris.
11 years, 7 months
Re: (ITS#7010) Deadlock in Producer/Consumer Nodes
by ghola＠rebelbase.com
Here is the data requested from the most recent lock-up.
Default locking region information:
14 Last allocated locker ID
0x7fffffff Current maximum unused locker ID
9 Number of lock modes
1000 Maximum number of locks possible
1000 Maximum number of lockers possible
1000 Maximum number of lock objects possible
160 Number of lock object partitions
27 Number of current locks
682 Maximum number of locks at any one time
5 Maximum number of locks in any one bucket
0 Maximum number of locks stolen by for an empty partition
0 Maximum number of locks stolen for any one partition
63 Number of current lockers
63 Maximum number of lockers at any one time
21 Number of current lock objects
377 Maximum number of lock objects at any one time
3 Maximum number of lock objects in any one bucket
0 Maximum number of objects stolen by for an empty partition
0 Maximum number of objects stolen for any one partition
13M Total number of locks requested (13581842)
13M Total number of locks released (13581804)
0 Total number of locks upgraded
13 Total number of locks downgraded
6 Lock requests not available due to conflicts, for which we waited
1 Lock requests not available due to conflicts, for which we did not wait
0 Number of deadlocks
0 Lock timeout value
0 Number of locks that have timed out
0 Transaction timeout value
0 Number of transactions that have timed out
808KB The size of the lock region
15280 The number of partition locks that required waiting (0%)
10921 The maximum number of times any partition lock was waited for (0%)
0 The number of object queue operations that required waiting (0%)
4742 The number of locker allocations that required waiting (0%)
0 The number of region locks that required waiting (0%)
3 Maximum hash bucket length
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock REGINFO information:
Lock Region type
5 Region ID
__db.005 Region name
0x2aeb3285c000 Region address
0x2aeb3285c138 Region primary address
0 Region maximum allocation
0 Region allocated
Region allocations: 327 allocations, 0 failures, 0 frees, 1 longest
Allocations by power-of-two sizes:
1KB 322
2KB 0
4KB 0
8KB 0
16KB 1
32KB 2
64KB 0
128KB 1
256KB 1
512KB 0
1024KB 0
REGION_JOIN_OK Region flags
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock region parameters:
262177 Lock region region mutex [0/450861 0% 15746/47187942583984]
1031 locker table size
1031 object table size
952 obj_off
122400 locker_off
1 need_dd
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Lock conflict matrix:
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by lockers:
Locker Mode Count Status ----------------- Object ---------------
1 dd=22 locks held 1 write locks 0 pid/thread
7123/47021676422512 priority 100
1 READ 1 HELD id2entry.bdb handle 0
2 dd=21 locks held 1 write locks 0 pid/thread
7123/47021676422512 priority 100
2 READ 1 HELD dn2id.bdb handle 0
3 dd=20 locks held 0 write locks 0 pid/thread
7123/47021676422512 priority 100
4 dd=16 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
4 READ 1 HELD entryUUID.bdb handle 0
5 dd=15 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
5 READ 1 HELD modifyTimestamp.bdb handle 0
6 dd=12 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
6 READ 1 HELD cn.bdb handle 0
7 dd=11 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
7 READ 1 HELD givenName.bdb handle 0
8 dd=10 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
8 READ 1 HELD sn.bdb handle 0
9 dd= 9 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
9 READ 1 HELD objectClass.bdb handle 0
a dd= 6 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
a READ 1 HELD uid.bdb handle 0
b dd= 5 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
b READ 1 HELD uidNumber.bdb handle 0
c dd= 4 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
c READ 1 HELD gidNumber.bdb handle 0
d dd= 3 locks held 1 write locks 0 pid/thread
7123/1121872192 priority 100
d READ 1 HELD sambaSID.bdb handle 0
e dd= 2 locks held 1 write locks 0 pid/thread
7123/1121872192 priority 100
e READ 1 HELD sambaPrimaryGroupSID.bdb handle 0
80000380 dd=14 locks held 0 write locks 0 pid/thread
7123/1121872192 priority 100
80000381 dd=13 locks held 0 write locks 0 pid/thread
7123/1092884800 priority 100
80000003 dd=19 locks held 0 write locks 0 pid/thread
7123/47021676422512 priority 100
80000004 dd=18 locks held 0 write locks 0 pid/thread
7123/47021676422512 priority 100
80000005 dd=17 locks held 1 write locks 0 pid/thread
7123/1113479488 priority 100
80000005 READ 1 HELD 0x3dc78 len: 9 data: a2b007000000000000
80000938 dd= 8 locks held 0 write locks 0 pid/thread
7123/1138657600 priority 100
80000939 dd= 7 locks held 0 write locks 0 pid/thread
7123/1130264896 priority 100
80048a47 dd= 1 locks held 0 write locks 0 pid/thread
7123/1147050304 priority 100
800dc266 dd= 0 locks held 11 write locks 5 pid/thread
7123/1138657600 priority 100
800dc266 WRITE 1 WAIT 0x3dc78 len: 9 data: a2b007000000000000
800dc266 READ 2 HELD dn2id.bdb page 11658
800dc266 WRITE 4 HELD dn2id.bdb page 11658
800dc266 READ 2 HELD objectClass.bdb page 115
800dc266 WRITE 2 HELD objectClass.bdb page 115
800dc266 READ 1 HELD objectClass.bdb page 3
800dc266 READ 1 HELD entryUUID.bdb page 2839
800dc266 WRITE 2 HELD entryUUID.bdb page 2839
800dc266 READ 1 HELD modifyTimestamp.bdb page 3168
800dc266 WRITE 2 HELD modifyTimestamp.bdb page 3168
800dc266 WRITE 3 HELD id2entry.bdb page 14475
800dc266 READ 1 HELD 0x36718 len: 9 data: 9cb007000000000000
800dc268 dd= 0 locks held 0 write locks 0 pid/thread
7123/1163835712 priority 100
800dc269 dd= 0 locks held 0 write locks 0 pid/thread
7123/1155443008 priority 100
800dc26a dd= 0 locks held 0 write locks 0 pid/thread
7123/1172228416 priority 100
800dc26b dd= 0 locks held 0 write locks 0 pid/thread
7123/1180621120 priority 100
800dc26c dd= 0 locks held 0 write locks 0 pid/thread
7123/1189013824 priority 100
800dc26d dd= 0 locks held 0 write locks 0 pid/thread
7123/1197406528 priority 100
800dc26e dd= 0 locks held 0 write locks 0 pid/thread
7123/1205799232 priority 100
800dc26f dd= 0 locks held 0 write locks 0 pid/thread
7123/1214191936 priority 100
800dc270 dd= 0 locks held 0 write locks 0 pid/thread
7123/1222584640 priority 100
800dc271 dd= 0 locks held 0 write locks 0 pid/thread
7123/1230977344 priority 100
800dc272 dd= 0 locks held 0 write locks 0 pid/thread
7123/1239370048 priority 100
800dc273 dd= 0 locks held 0 write locks 0 pid/thread
7123/1247762752 priority 100
800dc274 dd= 0 locks held 0 write locks 0 pid/thread
7123/1256155456 priority 100
800dc275 dd= 0 locks held 0 write locks 0 pid/thread
7123/1264548160 priority 100
800dc276 dd= 0 locks held 0 write locks 0 pid/thread
7123/1272940864 priority 100
800dc277 dd= 0 locks held 0 write locks 0 pid/thread
7123/1289726272 priority 100
800dc278 dd= 0 locks held 0 write locks 0 pid/thread
7123/1281333568 priority 100
800dc279 dd= 0 locks held 0 write locks 0 pid/thread
7123/1298118976 priority 100
800dc27a dd= 0 locks held 0 write locks 0 pid/thread
7123/1306511680 priority 100
800dc27b dd= 0 locks held 0 write locks 0 pid/thread
7123/1314904384 priority 100
800dc27c dd= 0 locks held 0 write locks 0 pid/thread
7123/1331689792 priority 100
800dc27d dd= 0 locks held 0 write locks 0 pid/thread
7123/1340082496 priority 100
800dc27e dd= 0 locks held 0 write locks 0 pid/thread
7123/1348475200 priority 100
800dc27f dd= 0 locks held 0 write locks 0 pid/thread
7123/1356867904 priority 100
800dc280 dd= 0 locks held 0 write locks 0 pid/thread
7123/1365260608 priority 100
800dc281 dd= 0 locks held 0 write locks 0 pid/thread
7123/1373653312 priority 100
800dc282 dd= 0 locks held 0 write locks 0 pid/thread
7123/1382046016 priority 100
800dc283 dd= 0 locks held 0 write locks 0 pid/thread
7123/1390438720 priority 100
800dc284 dd= 0 locks held 0 write locks 0 pid/thread
7123/1407224128 priority 100
800dc285 dd= 0 locks held 0 write locks 0 pid/thread
7123/1398831424 priority 100
800dc286 dd= 0 locks held 0 write locks 0 pid/thread
7123/1415616832 priority 100
800dc287 dd= 0 locks held 0 write locks 0 pid/thread
7123/1424009536 priority 100
800dc288 dd= 0 locks held 0 write locks 0 pid/thread
7123/1432402240 priority 100
800dc289 dd= 0 locks held 0 write locks 0 pid/thread
7123/1440794944 priority 100
800dc28a dd= 0 locks held 0 write locks 0 pid/thread
7123/1449187648 priority 100
800dc28b dd= 0 locks held 0 write locks 0 pid/thread
7123/1457580352 priority 100
800dc28c dd= 0 locks held 0 write locks 0 pid/thread
7123/1474365760 priority 100
800dc28d dd= 0 locks held 0 write locks 0 pid/thread
7123/1465973056 priority 100
800dc28e dd= 0 locks held 0 write locks 0 pid/thread
7123/1482758464 priority 100
800dc28e READ 1 WAIT dn2id.bdb page 11658
800dc28f dd= 0 locks held 0 write locks 0 pid/thread
7123/1491151168 priority 100
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Locks grouped by object:
Locker Mode Count Status ----------------- Object ---------------
800dc266 READ 2 HELD objectClass.bdb page 115
800dc266 WRITE 2 HELD objectClass.bdb page 115
800dc266 WRITE 3 HELD id2entry.bdb page 14475
4 READ 1 HELD entryUUID.bdb handle 0
1 READ 1 HELD id2entry.bdb handle 0
b READ 1 HELD uidNumber.bdb handle 0
80000005 READ 1 HELD 0x3dc78 len: 9 data: a2b007000000000000
800dc266 WRITE 1 WAIT 0x3dc78 len: 9 data: a2b007000000000000
e READ 1 HELD sambaPrimaryGroupSID.bdb handle 0
2 READ 1 HELD dn2id.bdb handle 0
800dc266 READ 1 HELD entryUUID.bdb page 2839
800dc266 WRITE 2 HELD entryUUID.bdb page 2839
a READ 1 HELD uid.bdb handle 0
6 READ 1 HELD cn.bdb handle 0
800dc266 READ 1 HELD 0x36718 len: 9 data: 9cb007000000000000
800dc266 READ 1 HELD modifyTimestamp.bdb page 3168
800dc266 WRITE 2 HELD modifyTimestamp.bdb page 3168
d READ 1 HELD sambaSID.bdb handle 0
c READ 1 HELD gidNumber.bdb handle 0
5 READ 1 HELD modifyTimestamp.bdb handle 0
8 READ 1 HELD sn.bdb handle 0
7 READ 1 HELD givenName.bdb handle 0
800dc266 READ 1 HELD objectClass.bdb page 3
9 READ 1 HELD objectClass.bdb handle 0
800dc266 READ 2 HELD dn2id.bdb page 11658
800dc266 WRITE 4 HELD dn2id.bdb page 11658
800dc28e READ 1 WAIT dn2id.bdb page 11658
11 years, 7 months
(ITS#7073) zero-length entries should be allowed
by hyc＠OpenLDAP.org
Full_Name: Howard Chu
Version: 2.4
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (76.94.188.8)
Submitted by: hyc
entry_header() rejects "entries" that have zero attributes. As it turns out,
overlays like pcache and translucent can create such entries in their normal
operation. With back-bdb/hdb, such entries will work OK while slapd is running,
because they're in the entry cache. But after a restart, such entries can't be
read back from the DB because they're considered invalid by entry_header().
Already fixed in master, entry_header() now allows zero length entries.
11 years, 7 months
(ITS#7072) caseIgnoreMatch equals regular capital I with dotted capital I
by Frank.Meisschaert＠UGent.be
Full_Name: Frank Meisschaert
Version: 2.4.26
OS: linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (157.193.44.200)
When I try to add the names "İsmail" (original, with dotted capital I) and
"Ismail" (transcribed, regular capital I) to an entry using ldapmodify:
dn: ...
changetype: modify
replace: givenName
givenName: Ismail
givenName:: xLBzbWFpbA==
-
I get the error:
ldap_modify: Type or value exists (20)
additional info: givenName: value #0 provided more than once
The lowercase version of dotted and regular capital I is regular i which
explains this error. However according to unicode case folding the dotted
capital I should be mapped to 0069 0307 (i, combining dot above) which would
make Ismail and İsmail different when compared case-insensitively as I
would expect.
11 years, 7 months
Re: (ITS#7067) openldap not properly starting
by masarati＠aero.polimi.it
On 10/24/2011 07:18 AM, sanjiv.singh(a)impetus.co.in wrote:
> --_000_23A2685ED8B30D46A90227113A1ECE0758F47662Mail3impetuscoi_
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: quoted-printable
>
> How can I redirect to openldap-technical mailing list ?
> Not getting any link for this .
Subscribe to openldap-technical
<http://www.openldap.org/lists/mm/listinfo/openldap-technical>; post
your message to <mailto:openldap-technical@openldap.org>
--
Pierangelo Masarati
Associate Professor
Dipartimento di Ingegneria Aerospaziale
Politecnico di Milano
11 years, 7 months
Re: (ITS#7067) openldap not properly starting
by sanjiv.singh＠impetus.co.in
--_000_23A2685ED8B30D46A90227113A1ECE0758F47662Mail3impetuscoi_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
How can I redirect to openldap-technical mailing list ?
Not getting any link for this .
Regards,
Sanjiv Singh
________________________________
New Impetus webcast on-demand 'Big Data Technologies for Social Media Analy=
tics' available at http://bit.ly/nFdet0.
Visit http://www.impetus.com to know more. Follow us on www.twitter.com/imp=
etuscalling
NOTE: This message may contain information that is confidential, proprietar=
y, privileged or otherwise protected by law. The message is intended solely=
for the named addressee. If received in error, please destroy and notify t=
he sender. Any use of this email is prohibited when received in error. Impe=
tus does not represent, warrant and/or guarantee, that the integrity of thi=
s communication has been maintained nor that the communication is free of e=
rrors, virus, interception or interference.
--_000_23A2685ED8B30D46A90227113A1ECE0758F47662Mail3impetuscoi_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style>
<!--
@font-face
{font-family:Calibri}
@font-face
{font-family:Tahoma}
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif"}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline}
pre
{margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New"}
span.EmailStyle17
{font-family:"Calibri","sans-serif";
color:windowtext}
span.HTMLPreformattedChar
{font-family:"Courier New"}
.MsoChpDefault
{font-family:"Calibri","sans-serif"}
@page WordSection1
{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
{}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<pre>How can I redirect to openldap-technical mailing list ?</pre>
<p class=3D"MsoNormal">Not getting any link for this .</p>
<p class=3D"MsoNormal"> </p>
<p class=3D"MsoNormal"><span style=3D"font-size:7.5pt; font-family:"Ta=
homa","sans-serif"; color:gray">Regards,</span></p>
<p class=3D"MsoNormal"><b><span style=3D"font-size:10.0pt; font-family:&quo=
t;Arial","sans-serif"">Sanjiv Singh</span></b><span style=3D=
"font-size:7.5pt; font-family:"Tahoma","sans-serif"; co=
lor:gray">
</span></p>
<p class=3D"MsoNormal"> </p>
<p class=3D"MsoNormal"> </p>
</div>
<br>
<hr>
<font face=3D"Verdana" color=3D"Gray" size=3D"1"><br>
New Impetus webcast on-demand ‘Big Data Technologies for Social Media=
Analytics’ available at http://bit.ly/nFdet0.
<br>
<br>
Visit http://www.impetus.com to know more. Follow us on www.twitter.com/imp=
etuscalling
<br>
<br>
<br>
NOTE: This message may contain information that is confidential, proprietar=
y, privileged or otherwise protected by law. The message is intended solely=
for the named addressee. If received in error, please destroy and notify t=
he sender. Any use of this email
is prohibited when received in error. Impetus does not represent, warrant =
and/or guarantee, that the integrity of this communication has been maintai=
ned nor that the communication is free of errors, virus, interception or in=
terference.<br>
</font>
</body>
</html>
--_000_23A2685ED8B30D46A90227113A1ECE0758F47662Mail3impetuscoi_--
11 years, 7 months
