Re: (ITS#8827) lmdb from master fails to build with Visual Studio 2015.
by rion4ik＠gmail.com
--000000000000ac244b056892dafb
Content-Type: text/plain; charset="UTF-8"
logs:
c:\src\lmdb\libraries\liblmdb\mdb.c(55): error C2059: syntax error: '('
1>c:\src\lmdb\libraries\liblmdb\mdb.c(61): error C2143: syntax error:
missing '{' before '*'
1>c:\src\lmdb\libraries\liblmdb\mdb.c(68): error C2059: syntax error: '('
1>c:\src\lmdb\libraries\liblmdb\mdb.c(75): error C2143: syntax error:
missing '{' before '*'
1>c:\src\lmdb\libraries\liblmdb\mdb.c(77): error C2059: syntax error: '('
1>c:\src\lmdb\libraries\liblmdb\mdb.c(79): error C2143: syntax error:
missing '{' before '*'
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4339): error C2063:
'NtCreateSection': not a function
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4346): error C2063:
'NtMapViewOfSection': not a function
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4350): error C2063: 'NtClose': not a
function
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4704): error C2065: 'NtCloseFunc':
undeclared identifier
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4704): error C2059: syntax error: ')'
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4707): error C2065:
'NtMapViewOfSectionFunc': undeclared identifier
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4707): error C2059: syntax error: ')'
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4710): error C2065:
'NtCreateSectionFunc': undeclared identifier
1>c:\src\lmdb\libraries\liblmdb\mdb.c(4710): error C2059: syntax error: ')'
1>c:\src\lmdb\libraries\liblmdb\mdb.c(8314): warning C4333: '>>': right
shift by too large amount, data los
PS github's bug tracker is much more user-friendly, it even has command
line interface for old-school guys. Why do you use this mail-based crap?
Best Regards,
Sergey
--000000000000ac244b056892dafb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">logs:<div><br></div><div><div>c:\src\lmdb\libraries\liblmd=
b\mdb.c(55): error C2059: syntax error: '('</div><div>1>c:\src\l=
mdb\libraries\liblmdb\mdb.c(61): error C2143: syntax error: missing '{&=
#39; before '*'</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c(=
68): error C2059: syntax error: '('</div><div>1>c:\src\lmdb\libr=
aries\liblmdb\mdb.c(75): error C2143: syntax error: missing '{' bef=
ore '*'</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c(77): err=
or C2059: syntax error: '('</div><div>1>c:\src\lmdb\libraries\li=
blmdb\mdb.c(79): error C2143: syntax error: missing '{' before '=
;*'</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c(4339): error C20=
63: 'NtCreateSection': not a function</div><div>1>c:\src\lmdb\li=
braries\liblmdb\mdb.c(4346): error C2063: 'NtMapViewOfSection': not=
a function</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c(4350): error=
C2063: 'NtClose': not a function</div><div>1>c:\src\lmdb\librar=
ies\liblmdb\mdb.c(4704): error C2065: 'NtCloseFunc': undeclared ide=
ntifier</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c(4704): error C20=
59: syntax error: ')'</div><div>1>c:\src\lmdb\libraries\liblmdb\=
mdb.c(4707): error C2065: 'NtMapViewOfSectionFunc': undeclared iden=
tifier</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c(4707): error C205=
9: syntax error: ')'</div><div>1>c:\src\lmdb\libraries\liblmdb\m=
db.c(4710): error C2065: 'NtCreateSectionFunc': undeclared identifi=
er</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c(4710): error C2059: s=
yntax error: ')'</div><div>1>c:\src\lmdb\libraries\liblmdb\mdb.c=
(8314): warning C4333: '>>': right shift by too large amount,=
data los</div></div><div class=3D"gmail_extra"><br></div><div class=3D"gma=
il_extra">PS github's bug tracker is much more user-friendly, it even h=
as command line interface for old-school guys. Why do you use this mail-bas=
ed crap?</div><div class=3D"gmail_extra"><br clear=3D"all"><div><div class=
=3D"gmail_signature" data-smartmail=3D"gmail_signature"><div dir=3D"ltr">Be=
st Regards,<div>Sergey</div></div></div></div><br></div></div>
--000000000000ac244b056892dafb--
5 years, 8 months
Re: (ITS#8825) slapo-memberof: memberof-memberof-ad doesn't work correctly
by quanah＠symas.com
--On Wednesday, March 28, 2018 1:14 AM +0100 Howard Chu <hyc(a)symas.com>
wrote:
> That's because memberOf is an operational attribute, so objectclass
> requirements don't apply. If you want to use some other attribute, make
> sure the schema allows it in the relevant entries, or use an operational
> attribute.
>
> Not a bug. Closing this ITS.
For historical purposes, it is a bit more complex than this.
It is not possible to include an operational attribute via the normal
schema methods. This depends on the "dsaschema" contrib overlay. That
contrib overlay requires development to support cn=config.
The alternative to using an operational attribute is to have a custom
objectClass where the custom attribute desired is defined as an optional
("MAY") attribute.
--Quanah
--
Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
<http://www.symas.com>
5 years, 8 months
Re: (ITS#8825) slapo-memberof: memberof-memberof-ad doesn't work correctly
by hyc＠symas.com
quanah(a)openldap.org wrote:
> Full_Name: Quanah Gibson-Mount
> Version: 2.4.45
> OS: Linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (47.208.148.239)
>
>
> Per the slapo-memberof man page, you can define a different attribute than
> "memberOf" to hold the group membership information for an entry.
>
> However, this fails due to the fact that when a different attribute is used,
> slapd applies objectClass rule requirements to the entry. slapd does *not* do
> this when the default value of "memberOf" is used.
That's because memberOf is an operational attribute, so objectclass
requirements don't apply. If you want to use some other attribute, make sure
the schema allows it in the relevant entries, or use an operational attribute.
Not a bug. Closing this ITS.
>
> Example config:
>
> overlay memberof
> memberof-group-oc groupofuniquenames
> memberof-member-ad uniquemember
> memberof-memberof-ad ismemberof
>
> Example schema:
>
> attributetype ( 2.15.930.3.234225.3.1
> NAME 'isMemberOf'
> DESC 'Sun defined attribute type'
> EQUALITY distinguishedNameMatch
> SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
> X-ORIGIN 'Sun Directory Server' )
>
> Create a group:
>
> dn: cn=mygroup,dc=example,dc=com
> objectClass: top
> objectClass: groupOfUniqueNames
> cn: mygroup
> uniqueMember: cn=La Valko,ou=Peons,dc=example,dc=com
>
> Group creates OK, but:
>
> slapd[5149]: Entry (cn=La Valko,ou=Peons,dc=example,dc=com), attribute
> 'isMemberOf' not allowed
> slapd[5149]: entry failed schema check: attribute 'isMemberOf' not allowed
> slapd[5149]: conn=1000 op=19: memberof_value_modify DN="cn=la
> valko,ou=peons,dc=example,dc=com" add isMemberOf="cn=mygroup,dc=example,dc=com"
> failed err=65
>
>
>
>
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
5 years, 8 months
(ITS#8825) slapo-memberof: memberof-memberof-ad doesn't work correctly
by quanah＠openldap.org
Full_Name: Quanah Gibson-Mount
Version: 2.4.45
OS: Linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (47.208.148.239)
Per the slapo-memberof man page, you can define a different attribute than
"memberOf" to hold the group membership information for an entry.
However, this fails due to the fact that when a different attribute is used,
slapd applies objectClass rule requirements to the entry. slapd does *not* do
this when the default value of "memberOf" is used.
Example config:
overlay memberof
memberof-group-oc groupofuniquenames
memberof-member-ad uniquemember
memberof-memberof-ad ismemberof
Example schema:
attributetype ( 2.15.930.3.234225.3.1
NAME 'isMemberOf'
DESC 'Sun defined attribute type'
EQUALITY distinguishedNameMatch
SYNTAX 1.3.6.1.4.1.1466.115.121.1.12
X-ORIGIN 'Sun Directory Server' )
Create a group:
dn: cn=mygroup,dc=example,dc=com
objectClass: top
objectClass: groupOfUniqueNames
cn: mygroup
uniqueMember: cn=La Valko,ou=Peons,dc=example,dc=com
Group creates OK, but:
slapd[5149]: Entry (cn=La Valko,ou=Peons,dc=example,dc=com), attribute
'isMemberOf' not allowed
slapd[5149]: entry failed schema check: attribute 'isMemberOf' not allowed
slapd[5149]: conn=1000 op=19: memberof_value_modify DN="cn=la
valko,ou=peons,dc=example,dc=com" add isMemberOf="cn=mygroup,dc=example,dc=com"
failed err=65
5 years, 8 months
Re: (ITS#8823) LMDB on ramdisk
by hyc＠symas.com
luca.foppiano(a)inria.fr wrote:
> Full_Name: Luca Foppiano
> Version: 2.4
> OS: linux
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (37.169.254.52)
>
>
> Dear OpenLDAP team,
> I'm using one of your component (LMDB) via a java JNDI bindings
> implementation (https://github.com/deephacks/lmdbjni) and I'm having an issue
> when I deploy my LMDB file on a tempfs filesystem in RAM.
The ITS is for bug reports, not for help requests. Use the -technical mailing
list. Closing this ITS.
>
> The issue do not occur when the LMDB files are stored on a "normal" filesystem.
> When the data is in the tempfs ramdisk all the allocated memory ends up being in
> the Dirty area (it has not been written back to the Filesytem).
>
> Here an example using the ramdisk:
>
> 7ce320000000-7cfc20000000 r--s 00000000 00:26 2459
> /ramfs/nerd/data/db/db-en/entityEmbeddings/data.mdb
> Size: 104857600 kB
> Rss: 1255680 kB
> Pss: 1255680 kB
> Shared_Clean: 0 kB
> Shared_Dirty: 0 kB
> Private_Clean: 0 kB
> Private_Dirty: 1255680 kB <---
> Referenced: 1255680 kB
> Anonymous: 0 kB
> AnonHugePages: 0 kB
> Shared_Hugetlb: 0 kB
> Private_Hugetlb: 0 kB
> Swap: 0 kB
> SwapPss: 0 kB
> KernelPageSize: 4 kB
> MMUPageSize: 4 kB
> Locked: 0 kB
> VmFlags: rd sh mr mw me ms sd
>
> and here an example without:
>
> 7ca4fc000000-7cbdfc000000 r--s 00000000 fd:00 11154951
> /data/workspace/shared/nerd-data/db/db-en/entityEmbeddings/data.mdb
> Size: 104857600 kB
> Rss: 838124 kB
> Pss: 838124 kB
> Shared_Clean: 0 kB
> Shared_Dirty: 0 kB
> Private_Clean: 838124 kB <----
> Private_Dirty: 0 kB
> Referenced: 764872 kB
> Anonymous: 0 kB
> AnonHugePages: 0 kB
> ShmemPmdMapped: 0 kB
> Shared_Hugetlb: 0 kB
> Private_Hugetlb: 0 kB
> Swap: 0 kB
> SwapPss: 0 kB
> KernelPageSize: 4 kB
> MMUPageSize: 4 kB
> Locked: 0 kB
> VmFlags: rd sh mr mw me ms sd
>
>
> According to my understanding the memory is dirty when 1)there are open
> transactions, 2) the data has not been written back to the filesystem
>
> What I don't understand is why there is a difference between filesystem and
> ramdisk?
> Is there any reason? The application (listed above) is not writing on the lmdb,
> but just reading (using reading transaction).
>
> Thank you
> Luca
>
>
--
-- Howard Chu
CTO, Symas Corp. http://www.symas.com
Director, Highland Sun http://highlandsun.com/hyc/
Chief Architect, OpenLDAP http://www.openldap.org/project/
5 years, 8 months
(ITS#8823) LMDB on ramdisk
by luca.foppiano＠inria.fr
Full_Name: Luca Foppiano
Version: 2.4
OS: linux
URL: ftp://ftp.openldap.org/incoming/
Submission from: (NULL) (37.169.254.52)
Dear OpenLDAP team,
I'm using one of your component (LMDB) via a java JNDI bindings
implementation (https://github.com/deephacks/lmdbjni) and I'm having an issue
when I deploy my LMDB file on a tempfs filesystem in RAM.
The issue do not occur when the LMDB files are stored on a "normal" filesystem.
When the data is in the tempfs ramdisk all the allocated memory ends up being in
the Dirty area (it has not been written back to the Filesytem).
Here an example using the ramdisk:
7ce320000000-7cfc20000000 r--s 00000000 00:26 2459
/ramfs/nerd/data/db/db-en/entityEmbeddings/data.mdb
Size: 104857600 kB
Rss: 1255680 kB
Pss: 1255680 kB
Shared_Clean: 0 kB
Shared_Dirty: 0 kB
Private_Clean: 0 kB
Private_Dirty: 1255680 kB <---
Referenced: 1255680 kB
Anonymous: 0 kB
AnonHugePages: 0 kB
Shared_Hugetlb: 0 kB
Private_Hugetlb: 0 kB
Swap: 0 kB
SwapPss: 0 kB
KernelPageSize: 4 kB
MMUPageSize: 4 kB
Locked: 0 kB
VmFlags: rd sh mr mw me ms sd
and here an example without:
7ca4fc000000-7cbdfc000000 r--s 00000000 fd:00 11154951
/data/workspace/shared/nerd-data/db/db-en/entityEmbeddings/data.mdb
Size: 104857600 kB
Rss: 838124 kB
Pss: 838124 kB
Shared_Clean: 0 kB
Shared_Dirty: 0 kB
Private_Clean: 838124 kB <----
Private_Dirty: 0 kB
Referenced: 764872 kB
Anonymous: 0 kB
AnonHugePages: 0 kB
ShmemPmdMapped: 0 kB
Shared_Hugetlb: 0 kB
Private_Hugetlb: 0 kB
Swap: 0 kB
SwapPss: 0 kB
KernelPageSize: 4 kB
MMUPageSize: 4 kB
Locked: 0 kB
VmFlags: rd sh mr mw me ms sd
According to my understanding the memory is dirty when 1)there are open
transactions, 2) the data has not been written back to the filesystem
What I don't understand is why there is a difference between filesystem and
ramdisk?
Is there any reason? The application (listed above) is not writing on the lmdb,
but just reading (using reading transaction).
Thank you
Luca
5 years, 8 months
