openldap-bugs

openldap-bugs@openldap.org

1 participants
20960 discussions

Re: (ITS#4860) Sets' enhancement
by ando＠sys-net.it 13 Sep '07

13 Sep '07

Should be fixed now in HEAD/re24/re23. Please test. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by hyc＠symas.com 13 Sep '07

13 Sep '07

Raphaël Ouazana-Sustowski wrote: > Hi, > > Le Jeu 13 septembre 2007 21:29, hyc(a)symas.com a écrit : >> There is nothing ambiguous here. When slapd.conf is being used, the >> dbconfig >> directive *only* takes effect *if* no DB_CONFIG file exists. If one >> exists, the >> dbconfig directives are ignored. > > So if someone first create its DB_CONFIG by putting dbconfig directives in > slapd.conf, and then modify these directives, the modification has no > effect ? Correct. > Reading the man page, I thought that the directives don't modify > DB_CONFIG, but were applied at slapd's startup. For slapd.conf, the directives can only take effect after they are written to DB_CONFIG. They will only be written to DB_CONFIG at startup time, and only if no such file already existed. The main reason this directive was added was for the benefit of cn=config. Using it in slapd.conf is rather pointless. Once you start managing slapd through cn=config, you are expected to stop editing DB_CONFIG manually. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by ando＠sys-net.it 13 Sep '07

13 Sep '07

Howard Chu wrote: > Pierangelo Masarati wrote: >> hyc(a)symas.com wrote: >> >>> There is nothing ambiguous here. When slapd.conf is being used, the >>> dbconfig directive *only* takes effect *if* no DB_CONFIG file exists. >>> If one exists, the dbconfig directives are ignored. >> >> I insist: I don't see it so clear, and I was pointed to it by other >> people that didn't find it clear as well. I'm not questioning what the >> code does, just this very bit of the man page. > > "If (x) then (y)" is the complete definition of the behavior. You are > looking for explanations for "If (!x)", but it should be well understood > that such cases are irrelevant given this definition. That's actually an if (x) and (!y) then (z). What is missing is if (x) and (y) (which happens to be (!z), but it could be anything...) p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by hyc＠symas.com 13 Sep '07

13 Sep '07

Gavin Henry wrote: > <quote who="Howard Chu"> >> ghenry(a)suretecsystems.com wrote: >>> I would say since dbconfig directives only work on a restart of slapd, >>> and >>> that if a DB_CONFIG is present, the DB_CONFIG should *always* take >>> precedence. If dbconfig changes could make a difference via back-config, >>> which they can't without a restart, then dbconfig stuff should override >>> any DB_CONFIG. >> dbconfig behavior via cn=config is fully dynamic, and thus quite different >> from >> slapd.conf. Changes to dbconfig via cn=config take effect immediately and >> will >> completely rewrite the DB_CONFIG file. > > Understood, but a restart would still be needed to make the db env honour > DB_CONFIG, right? NO. "Fully dynamic" and "take effect immediately" means exactly that. I did not say "the file is written immediately but there's no effect until the server is restarted." Immediate effect means immediate effect. Do we really have to say everything twice or thrice here before people get it? -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by hyc＠symas.com 13 Sep '07

13 Sep '07

Pierangelo Masarati wrote: > hyc(a)symas.com wrote: > >> There is nothing ambiguous here. When slapd.conf is being used, the dbconfig >> directive *only* takes effect *if* no DB_CONFIG file exists. If one exists, the >> dbconfig directives are ignored. > > I insist: I don't see it so clear, and I was pointed to it by other > people that didn't find it clear as well. I'm not questioning what the > code does, just this very bit of the man page. "If (x) then (y)" is the complete definition of the behavior. You are looking for explanations for "If (!x)", but it should be well understood that such cases are irrelevant given this definition. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by raphael.ouazana＠linagora.com 13 Sep '07

13 Sep '07

Hi, Le Jeu 13 septembre 2007 21:29, hyc(a)symas.com a écrit : > There is nothing ambiguous here. When slapd.conf is being used, the > dbconfig > directive *only* takes effect *if* no DB_CONFIG file exists. If one > exists, the > dbconfig directives are ignored. So if someone first create its DB_CONFIG by putting dbconfig directives in slapd.conf, and then modify these directives, the modification has no effect ? Reading the man page, I thought that the directives don't modify DB_CONFIG, but were applied at slapd's startup. (Note that english is not my native language either, if it was not already clear ;). Regards, Raphael Ouazana.

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by ghenry＠suretecsystems.com 13 Sep '07

13 Sep '07

<quote who="Howard Chu"> > ghenry(a)suretecsystems.com wrote: >> I would say since dbconfig directives only work on a restart of slapd, >> and >> that if a DB_CONFIG is present, the DB_CONFIG should *always* take >> precedence. If dbconfig changes could make a difference via back-config, >> which they can't without a restart, then dbconfig stuff should override >> any DB_CONFIG. > > dbconfig behavior via cn=config is fully dynamic, and thus quite different > from > slapd.conf. Changes to dbconfig via cn=config take effect immediately and > will > completely rewrite the DB_CONFIG file. Understood, but a restart would still be needed to make the db env honour DB_CONFIG, right? Gavin.

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by ando＠sys-net.it 13 Sep '07

13 Sep '07

hyc(a)symas.com wrote: > There is nothing ambiguous here. When slapd.conf is being used, the dbconfig > directive *only* takes effect *if* no DB_CONFIG file exists. If one exists, the > dbconfig directives are ignored. I insist: I don't see it so clear, and I was pointed to it by other people that didn't find it clear as well. I'm not questioning what the code does, just this very bit of the man page. p. Ing. Pierangelo Masarati OpenLDAP Core Team SysNet s.r.l. via Dossi, 8 - 27100 Pavia - ITALIA http://www.sys-net.it --------------------------------------- Office: +39 02 23998309 Mobile: +39 333 4963172 Email: pierangelo.masarati(a)sys-net.it ---------------------------------------

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by hyc＠symas.com 13 Sep '07

13 Sep '07

ghenry(a)suretecsystems.com wrote: > I would say since dbconfig directives only work on a restart of slapd, and > that if a DB_CONFIG is present, the DB_CONFIG should *always* take > precedence. If dbconfig changes could make a difference via back-config, > which they can't without a restart, then dbconfig stuff should override > any DB_CONFIG. dbconfig behavior via cn=config is fully dynamic, and thus quite different from slapd.conf. Changes to dbconfig via cn=config take effect immediately and will completely rewrite the DB_CONFIG file. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: (ITS#5134) dbconfig vs. DB_CONFIG
by hyc＠symas.com 13 Sep '07

13 Sep '07

ando(a)sys-net.it wrote: > Full_Name: Pierangelo Masarati > Version: HEAD/re24/re23 > OS: irrelevant > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (193.203.230.29) > Submitted by: ando > > > The slapd-bdb(5) man page seems to me unclear with respect to the dbconfig > directive. In fact, what I gather from the text is that if no DB_CONFIG file > exists, any dbconfig directive will be used to generate one; otherwise, an > existing DB_CONFIG file will not be altered. What is unclear is what happens if > both a DB_CONFIG file and any dbconfig directives exist, and they differ? Who > takes the precedence? What if any dbconfig directive is not present in the > DB_CONFIG file? There is nothing ambiguous here. When slapd.conf is being used, the dbconfig directive *only* takes effect *if* no DB_CONFIG file exists. If one exists, the dbconfig directives are ignored. -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

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-bugs