openldap-bugs September 2007

openldap-bugs@openldap.org

33 participants
179 discussions

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

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

13 Sep '07

<quote who="ando(a)sys-net.it"> > ghenry(a)suretecsystems.com wrote: > >> I read that as if there is no DB_CONFIG, one gets created from the >> dbconfig directives. If there is one, dbconfig stuff gets ignored and >> the >> DB_CONFIG file is used. >> >> But yes, it's not clear what happens in that situation. So, I go back to >> you ;-) What does the code actually do? If it does indeed ignore >> dbconfig >> and honour DB_CONFIG then we say that. >> >> As I read your comments, you sound like you don't know what the code >> does > > Exactly. Oh, well excuse me for presuming! > >> (I don't as I haven't looked, but I'd be very surprised if you actually >> don't know). So this brings me back to my first point; we make it say >> what >> the code actually does do in the situation that there is a DB_CONFIG >> file >> and dbconfig directives in slapd.conf or slapd.d/ > > After reading the code, it seems that if reading from slapd.conf and the > DB_CONFIG is in place, any slapd.conf dbconfig directive is ignored. OK, sorry. I should have taken the time to read it myself. So we just amend the man page to say that. Good. > > 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 ando＠sys-net.it 13 Sep '07

13 Sep '07

ghenry(a)suretecsystems.com wrote: > I read that as if there is no DB_CONFIG, one gets created from the > dbconfig directives. If there is one, dbconfig stuff gets ignored and the > DB_CONFIG file is used. > > But yes, it's not clear what happens in that situation. So, I go back to > you ;-) What does the code actually do? If it does indeed ignore dbconfig > and honour DB_CONFIG then we say that. > > As I read your comments, you sound like you don't know what the code does Exactly. > (I don't as I haven't looked, but I'd be very surprised if you actually > don't know). So this brings me back to my first point; we make it say what > the code actually does do in the situation that there is a DB_CONFIG file > and dbconfig directives in slapd.conf or slapd.d/ After reading the code, it seems that if reading from slapd.conf and the DB_CONFIG is in place, any slapd.conf dbconfig directive is ignored. 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 ghenry＠suretecsystems.com 13 Sep '07

13 Sep '07

<quote who="Pierangelo Masarati"> > ghenry(a)suretecsystems.com wrote: > >>> I think the point is not what the code should (or should not) do, or >>> whether its current behavior is correct or not; it's rather that the >>> man >>> page, as far as I understand it, is not clear about what the code >>> currently does. >> >> Ok, well the text should reflect what the code does. I think I'm missing >> the point of your question. If the text doesn't currently match what is >> actually happening in the code, then we fix the man page so it does. > > My point is that from that text I don't understand what the code does. > Either it's my English (could well be), or it needs to be reworded. I'm > quoting here the original text: > > snip... > > dbconfig <Berkeley-DB-setting> > Specify a configuration directive to be placed in the DB_CONFIG > file of the database directory. The dbconfig directive is just > a convenience to allow all necessary configuration to be set in > the slapd.conf file. The options set using this directive will > only be written to the DB_CONFIG file if no such file existed > at server startup time. This allows one to set initial values > without overwriting/destroying a DB_CONFIG file that was > already customized through other means. > > snip... > > So it seems to be quite clear about what's going to happen if no > DB_CONFIG exists, but not as clear about what happens if DB_CONFIG > already exists, apart from not getting overwritten or otherwise modified. I read that as if there is no DB_CONFIG, one gets created from the dbconfig directives. If there is one, dbconfig stuff gets ignored and the DB_CONFIG file is used. But yes, it's not clear what happens in that situation. So, I go back to you ;-) What does the code actually do? If it does indeed ignore dbconfig and honour DB_CONFIG then we say that. As I read your comments, you sound like you don't know what the code does (I don't as I haven't looked, but I'd be very surprised if you actually don't know). So this brings me back to my first point; we make it say what the code actually does do in the situation that there is a DB_CONFIG file and dbconfig directives in slapd.conf or slapd.d/ Or am I being extremely stupid here? Thanks, Gavin.

1 0

← Newer
1
...
7
8
9
10
11
12
13
...
18
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-bugs September 2007