openldap-technical February 2019

openldap-technical@openldap.org

30 participants
22 discussions

[Q] RFC2307bis2 "An Approach for Using LDAP as a Network Information Service"
by Zeus Panchenko 07 Feb '19

07 Feb '19

greetings, We've found RFC2307bis2: "An Approach for Using LDAP as a Network Information Service" and now wondering, what've happened to it finally? Is it just expired and forgotten? Recently we've began to deploy netgroup usage in our network and found it impossible to do search by nisNetgroupTriple attribute due to it's SYNTAX and SUBSTR definition ... We've done "amendments" to nis.schema to fix that and they occured to be the same as the ones offered in RFC2307bis2 :) So, is there any further plans/ideas to do something with RFC2307bis2, please? -- Zeus V. Panchenko jid:zeus@im.ibs.dn.ua IT Dpt., I.B.S. LLC GMT+2 (EET)

2 1

Re: Antw: Re: slapd memory usage
by Howard Chu 07 Feb '19

07 Feb '19

Ulrich Windl wrote: >>>> Howard Chu <hyc(a)symas.com> schrieb am 07.02.2019 um 11:45 in Nachricht > <07438385-b8a5-92c8-3902-9d3084cbef6d(a)symas.com>: >> A. Schulze wrote: >>> >>> Howard Chu: >>> >>>>> Any idea why the memory usage is so different? >>>> >>>> If the only difference is that you set the open file limit to 1024, then it >> sounds >>>> like whatever your default file limit is is much larger. >>> >>> Hello Howard, >>> >>> yes, it's unlimited by default. Tons of other daemon also run without this >> limits here. >>> >>> But in contrast: all other daemons don't let explode the memory usage. >>> Maybe, it worth to find the difference? >> >> That *is* the difference. slapd allocates an array of connection info, one >> slot per >> file descriptor. Running with "unlimited" files is clearly a bad idea here. > > OTOH slapd could also allocate the table in chunks of 100 or 1000 descriptors (if ever needed that much) No. Such strategies invariably lead to failure under heavy load - precisely the time when you want extra resources to be available for use. Preallocating means we always have predictable and consistent runtime behavior. >> In general, running with larger limits than you actually need is a bad idea. > Yes, but allocating a huge table that is most likely never needed is also a bad idea IMHO. It would not be a huge table if you set your resource limits appropriately. >> This >> is elementary system administration. -- -- 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

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical February 2019