openldap-devel

openldap-devel@openldap.org

1418 discussions

Propose to MDB_PICKUP for mdb_dpi_open()
by Леонид Юрьев 30 Apr '15

30 Apr '15

Hi, Howard. I would like to introduce the MDB_PICKUP flag for mdb_dpi_open(). Please see https://github.com/ReOpen/ReOpenLDAP/commit/04f92c952e42ff4c843135c42fdb9aa… At least, this is required for mdb_chk tool, when a DBI should be opened with flags that stored inside LMDB, which while a DBI was created. It is particularly important for DBI_MAIN. Leonid.

2 4

Re: (ITS#8117) Bugs related to key-size in lmdb and backend
by Леонид Юрьев 30 Apr '15

30 Apr '15

Hi, Howard. As you told before, I will write to openldap-devel. So, please take look to MDB_INTEGERDUP in mdb_attr_dbs_open(). I cutout ones and all tests are passing. For my mdb_chk tool this is also solves a problem with checking INTEGER-keys. With MDB_INTEGERDUP removal a logic become spotless: keys must be sizeof(int) or sizeof(size_t) only if MDB_INTEGERDUP or MDB_INTEGERKEY is in a dbi-flags. Would you agree to remove MDB_INTEGERDUP from the mdb_attr_dbs_open()? Leonid. 2015-04-30 4:12 GMT+03:00 Howard Chu <hyc(a)symas.com>: > Leonid Yuriev wrote: > >> OK, but then - what is the purpose of MDB_INTEGERDUP in >> mdb_attr_dbs_open()? >> >> flags = MDB_DUPSORT|MDB_DUPFIXED|MDB_INTEGERDUP; >> if ( !(slapMode & SLAP_TOOL_READONLY) ) >> flags |= MDB_CREATE; >> >> Think it is not necessary, is it? >> > > You really think so? Have you thought about what the actual *values* are > in an index, instead of just the keys? > > Anyway, this ITS is resolved. Thank you for reporting the bug. If you want > to ask further questions about how the indexer works take it to > openldap-devel. > > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/project/ >

2 2

New Committer
by Howard Chu 29 Apr '15

29 Apr '15

The Project is pleased to announce that Ryan Tandy has joined the OpenLDAP Engineering Team. Ryan's recent contributions have been very helpful, in addition to his participation in the community and his coordinating with the Debian project. Welcome, Ryan! -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

2 1

New Committer
by project＠openldap.org 29 Apr '15

29 Apr '15

We are pleased to announce that Ryan Tandy has joined the OpenLDAP Engineering Team. Ryan's recent contributions have been very helpful, particularly his work as a liaison to the Debian project. Welcome, Ryan! -- -- Howard Chu CTO, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: [WIP] WiredTiger Backend
by HAMANO Tsukasa 27 Apr '15

27 Apr '15

Hi, Howard Thanks for your responce! On 月, 27 4月 2015 at 12:46:12 JST, Howard Chu wrote: > > Interesting, thanks for the contribution. Looks like there is no > manpage though, do you have one? > I will write it soon :p > > Some note: > > * slapadd, slapcat, slapindex will works. > > * LDAP BIND, ADD, DELETE, SEARCH will works. > > How well does it work, good enough to run benchmarks now? > I have just tested on virtual machine, back-wt LDAP ADD(with single thread) is 20-30x times faster than back-bdb. I'm looking forward to benchmarking with many thread. I'll publish benchmarks just when I get high spec machine. > > * WiredTiger is not support multiprocess access yet. > > It mean that we can't to do slatcat while running slapd. > > It will be supported in the future. > > You should use alock in the meantime then, to prevent multiprocess access. > WiredTiger is planning to implement RPC for multiprocess access. http://source.wiredtiger.com/2.5.3/group__wt.html#ga9e6adae3fc6964ef837a627… I think it will communicate with unix domain socket. I'm planning to use the feature to avoid multi process locking. Thank you. -- Open Source Solution Technology Corporation HAMANO Tsukasa <hamano(a)osstech.co.jp> fingerprint = 2285 2111 6D34 3816 3C2E A5B9 16BE D101 6069 BE55

1 0

LMDB and gitorious
by Timur Kristóf 22 Apr '15

22 Apr '15

Hi, As you might've heard, Gitorious is shutting down on 15th May. Maybe we start should look for a new home for the projects at https://gitorious.org/mdb - do you guys have a plan for this? Cheers, Timur

2 1

ppolicy: pardon password history
by hercherf＠hrz.uni-marburg.de 21 Apr '15

21 Apr '15

Hi list, I have made a tiny modification to the ppolicy-module. The aim is to go easy on people who forgot their password, or forgot to deploy their recently changed password to all devices (think of laptops, smartphones, etc.). Whenever a login fails due to a invalid password, the ppolicy-module will count this as a failure. After a configurable number of password failures in a given time, ppolicy will take action and - for example - lock the acount. I have tried to tweak this behaviour: When the password is found in the password history, the ppolicy-module will not count this as a password failure. If anyone is interested in this, please find the attached patch which also includes a working example configuration/testcase. Best regards, Florian -- Florian Hercher | Hochschulrechenzentrum | Philipps-Universität Marburg Hans-Meerwein-Str. 6, 35032 Marburg | fon +49-(0)6421-28-21036

3 3

Fwd: [Patch] Allocating sparse files on Windows
by Colin LeMahieu 20 Apr '15

20 Apr '15

Apologies if this arrives twice, I sent it once two days ago before subscribing to the list and it hasn't appeared yet so I'm resending after subscribing. Memory mapping files on Windows requires the file size to match the size of the memory mapped region however in the current implementation this requires creating a file the full size of the environment which may be much larger than the actual amount of data in the database. This patch creates the database as a sparse file on Windows. Windows Explorer will report the file size as the size of the entire memory mapped region but the size on disk will be proportional to the size of committed data in the database. This can be checked by checking the "size on disk" property of the file. Let me know if this is posted incorrectly, otherwise feel free to modify the patch in whatever way is necessary for approval.

2 2

www.openldap.org not mobile-friendly
by Hallvard Breien Furuseth 15 Apr '15

15 Apr '15

It will drop in Google's ratings next week because it fails the <https://www.google.com/webmasters/tools/mobile-friendly/> tests. Maybe someone can fix the web pages up a bit? I'm too busy now. -- Hallvard

4 4

Fwd: Using sendfile with lmdb
by James Rouzier 03 Apr '15

03 Apr '15

Eric thank you I would have never considered that as an issue. I tried out your code and saw the problem. You saved me going down a rabbit hole. Many Thanks On Thu, Apr 2, 2015 at 5:33 PM, Eric Wong <e(a)80x24.org> wrote: > James Rouzier <rouzier(a)gmail.com> wrote: > > Hey Guys, > > > > I am working on a proof of concept of a simple key value store service > > using lmdb as the back end. > > I am using sendfile to avoid an extra copy. > > Be careful if you're overwriting any data in LMDB. > > zero-copy sendfile means any data queued up in the kernel will be > subject to modifications as the underlying file is updated, so your > client may se data it was not intended to see. > > I wanted to do the same thing as you last year but ended up writing a > patch to the sendfile manpage instead: > > > https://git.kernel.org/cgit/docs/man-pages/man-pages.git/patch?id=7b6a32997… >

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-devel