openldap-bugs

openldap-bugs@openldap.org

1 participants
21001 discussions

Re: (ITS#7417) Why is there no schema add utility?
by jerrac＠gmail.com 17 Oct '12

17 Oct '12

--f46d04447dffae07bd04cc34c745 Content-Type: text/plain; charset=ISO-8859-1 Really? How? Also, the method described by Zytrax is pretty much what all the search results said. Including https://help.ubuntu.com/12.04/serverguide/openldap-server.html And I couldn't find anything different in the Openldap.org documentation. Again, maybe because I didn't search for the right things... With slapadd and ldapadd, can you add a .schema file? Or does it have to be in LDIF syntax? *goes to check the man page* --David Reagan On Tue, Oct 16, 2012 at 1:31 PM, Howard Chu <hyc(a)symas.com> wrote: > jerrac(a)gmail.com wrote: > >> Full_Name: David Reagan >> Version: 2.4 >> OS: Ubuntu 12.04 >> URL: ftp://ftp.openldap.org/**incoming/<ftp://ftp.openldap.org/incoming/> >> Submission from: (NULL) (163.41.112.5) >> >> >> Why is there no simple way to add new schema's to cn=Config? As in, >> something >> like "slapadd --schema newschema.schema". >> > > Eh? New schemas can be added directly using slapadd, or using ldapadd. > > The best explanation I found on how to add a new schema is >> http://www.zytrax.com/books/**ldap/ch6/slapd-config.html#**use-schemas<http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schemas>. >> You have to >> create a conf file, a new directory, run a command, edit a file, and then >> run >> another command. That's a lot of places where user error could break >> things. >> > > Your first mistake is in trusting anything that Zytrax says. Most of their > information is out of date or flat wrong. > > -- > -- Howard Chu > CTO, Symas Corp. http://www.symas.com > Director, Highland Sun http://highlandsun.com/hyc/ > Chief Architect, OpenLDAP http://www.openldap.org/**project/<http://www.openldap.org/project/> > --f46d04447dffae07bd04cc34c745 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Really? How? Also, the method described by Zytrax is pretty much wh= at all the search results said. Including <a href=3D"https://help.ubuntu.co= m/12.04/serverguide/openldap-server.html">https://help.ubuntu.com/12.04/ser= verguide/openldap-server.html</a> And I couldn't find anything different in the Openldap.org document= ation. Again, maybe because I didn't search for the right things... = With slapadd and ldapadd, can you add a .schema file? Or does it have t= o be in LDIF syntax? *goes to check the man page* --David Reagan <div class=3D"gmail_quote">On Tue, Oct 16, 2012 at 1:31 PM, Howard = Chu <<a href=3D"mailto:hyc@symas.com" target=3D"_blank= ">hyc(a)symas.com</a>> wrote: <blockquote class=3D"gmail_quote" = style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> <a href=3D"mailto:jerrac@gmail.com" target=3D"_blank">jerrac(a)gmail.com</a> = wrote: <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> Full_Name: David Reagan Version: 2.4 OS: Ubuntu 12.04 URL: <a href=3D"ftp://ftp.openldap.org/incoming/" target=3D"_blank">ftp://f= tp.openldap.org/incoming/</a> Submission from: (NULL) (163.41.112.5) Why is there no simple way to add new schema's to cn=3DConfig? As in, s= omething like "slapadd --schema newschema.schema". </blockquote> Eh? New schemas can be added directly using slapadd, or using ldapadd. <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p= x #ccc solid;padding-left:1ex"> The best explanation I found on how to add a new schema is <a href=3D"http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schem= as" target=3D"_blank">http://www.zytrax.com/books/ldap/ch6/slapd-con= fig.html#use-schemas</a>. You have to create a conf file, a new directory, run a command, edit a file, and then r= un another command. That's a lot of places where user error could break th= ings. </blockquote> Your first mistake is in trusting anything that Zytrax says. Most of their = information is out of date or flat wrong. -- =A0 -- Howard Chu =A0 CTO, Symas Corp. =A0 =A0 =A0 =A0 =A0 <a href=3D"http://www.symas.com" t= arget=3D"_blank">http://www.symas.com</a> =A0 Director, Highland Sun =A0 =A0 <a href=3D"http://highlandsun.com/hyc/" = target=3D"_blank">http://highlandsun.com/hyc/</a> =A0 Chief Architect, OpenLDAP =A0<a href=3D"http://www.openldap.org/project= /" target=3D"_blank">http://www.openldap.org/project/</a> </blockquote></div> --f46d04447dffae07bd04cc34c745--

1 0

Re: (ITS#7417) Why is there no schema add utility?
by hyc＠symas.com 16 Oct '12

16 Oct '12

jerrac(a)gmail.com wrote: > Full_Name: David Reagan > Version: 2.4 > OS: Ubuntu 12.04 > URL: ftp://ftp.openldap.org/incoming/ > Submission from: (NULL) (163.41.112.5) > > > Why is there no simple way to add new schema's to cn=Config? As in, something > like "slapadd --schema newschema.schema". Eh? New schemas can be added directly using slapadd, or using ldapadd. > The best explanation I found on how to add a new schema is > http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schemas. You have to > create a conf file, a new directory, run a command, edit a file, and then run > another command. That's a lot of places where user error could break things. Your first mistake is in trusting anything that Zytrax says. Most of their information is out of date or flat wrong. -- -- 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

(ITS#7417) Why is there no schema add utility?
by jerrac＠gmail.com 16 Oct '12

16 Oct '12

Full_Name: David Reagan Version: 2.4 OS: Ubuntu 12.04 URL: ftp://ftp.openldap.org/incoming/ Submission from: (NULL) (163.41.112.5) Why is there no simple way to add new schema's to cn=Config? As in, something like "slapadd --schema newschema.schema". The best explanation I found on how to add a new schema is http://www.zytrax.com/books/ldap/ch6/slapd-config.html#use-schemas. You have to create a conf file, a new directory, run a command, edit a file, and then run another command. That's a lot of places where user error could break things. So, is there a utility in the works, or are there other reasons this would be a bad idea? I'm curious. I did search Google, the tickets, and the mailing lists. But either there isn't anything there, or my search terms were bad. If this has already be discussed, I apologize for bringing it up again, and would appreciate a link to the discussion.

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by hyc＠symas.com 12 Oct '12

12 Oct '12

Kurt(a)OpenLDAP.org wrote: > You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. > > For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. > > So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. I think you've already covered the points. I have plenty of checks like this in my local source tree, but I see no reason to embed OS and platform-specific stuff into the distributed source. I believe it would lend a false sense of security, particularly when you're on a platform that ignores these variables, but you aren't aware of the fact. It is always the developers' responsibility to know how their own development environment works, and to tweak it to suit their development efforts. -- -- 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: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 12 Oct '12

12 Oct '12

2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: > > On Oct 12, 2012, at 8:38 AM, Elia Pinto <gitter.spiros(a)gmail.com> wrote: > >> 2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: >>> You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. >> >> It is your own opinion, right? Have experiences in this regard? > > Yes and Yes. I use to run with such environmental variables set in my .login. Not anymore, too many odd crashes. So sometimes I do something like: > env MallocScribble=yes MallocErrorAbort=yes make test > > but I've that crash above and below the run script, but not in OpenLDAP Software itself. So now, because I tend to run stuff I'm working on in a debugger, I now mostly rely on my debugger to turn malloc debugging on. And I tend to use other tools for leak detection (like leaks(1) on MacOS/X). HeHe, i suspect was ONLY a MacOS/X crap. Good to know. > > -- Kurt > > >> I do >> not. I personally run make test on openldap with Ubuntu 4.12, Fedora >> 17 and RHEL6 and my patch without any problem (good for openldap :=) >> ). And many other projects, for example, git hat has a very extensive >> test suite, use MALLOC_CHECK as in my patch, integrated in a test >> suite. >> >> However, I will not insist further on a trivial patch. Also because >> this discussion gave me the opportunity to investigate better the >> issue, and I'll just patch for FreeBSD my software. So, thank you >> anyway for the useful observations. >> >> Regards >>> >>> For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. >>> >>> So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. >>> >>> -- Kurt >>> >

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by Kurt＠OpenLDAP.org 12 Oct '12

12 Oct '12

On Oct 12, 2012, at 8:38 AM, Elia Pinto <gitter.spiros(a)gmail.com> wrote: > 2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: >> You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. > > It is your own opinion, right? Have experiences in this regard? Yes and Yes. I use to run with such environmental variables set in my .login. Not anymore, too many odd crashes. So sometimes I do something like: env MallocScribble=yes MallocErrorAbort=yes make test but I've that crash above and below the run script, but not in OpenLDAP Software itself. So now, because I tend to run stuff I'm working on in a debugger, I now mostly rely on my debugger to turn malloc debugging on. And I tend to use other tools for leak detection (like leaks(1) on MacOS/X). -- Kurt > I do > not. I personally run make test on openldap with Ubuntu 4.12, Fedora > 17 and RHEL6 and my patch without any problem (good for openldap :=) > ). And many other projects, for example, git hat has a very extensive > test suite, use MALLOC_CHECK as in my patch, integrated in a test > suite. > > However, I will not insist further on a trivial patch. Also because > this discussion gave me the opportunity to investigate better the > issue, and I'll just patch for FreeBSD my software. So, thank you > anyway for the useful observations. > > Regards >> >> For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. >> >> So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. >> >> -- Kurt >>

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 12 Oct '12

12 Oct '12

2012/10/12 Kurt Zeilenga <Kurt(a)openldap.org>: > You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. It is your own opinion, right? Have experiences in this regard? I do not. I personally run make test on openldap with Ubuntu 4.12, Fedora 17 and RHEL6 and my patch without any problem (good for openldap :=) ). And many other projects, for example, git hat has a very extensive test suite, use MALLOC_CHECK as in my patch, integrated in a test suite. However, I will not insist further on a trivial patch. Also because this discussion gave me the opportunity to investigate better the issue, and I'll just patch for FreeBSD my software. So, thank you anyway for the useful observations. Regards > > For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. > > So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. > > -- Kurt >

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by Kurt＠OpenLDAP.org 12 Oct '12

12 Oct '12

You miss the fact that we encourage deployers of OpenLDAP Software, who we recommend build OpenLDAP Software from source, run 'make test' before they 'make install'. We don't want these deployers to have false positives, such as would be likely caused if we added such environmental variables. For those doing automated checks, such as those who do construct packages, they can have local patches to their hearts content. Likewise for developers. So, if it was up to me, I would reject your patch as, IMO, it's in appropriate for our source distributions. I suspect Howard will chime in sooner or later. -- Kurt

1 0

Re: (ITS#7415) Add MALLOC_CHECK_ and MALLOC_PERTURB_ libc env to the test suite for detecting heap corruption
by gitter.spiros＠gmail.com 12 Oct '12

12 Oct '12

2012/10/11 Kurt Zeilenga <Kurt(a)openldap.org>: > I note that these environment variables are specific to Linux, and then only certain Linux systems. If we add these, then we should also add similar environment variables for FreeBSD malloc(3), MacOS/X malloc(3), and various alternative malloc(3) libraries. And then we might get into cases where variables for one set of environmental variables conflict with another. As these can be set by the developer as desired in their development environment, there's little reason to get into setting all the malloc(3) environmental variables that might be useful... and we shouldn't play favors and only set variables for Linux. Sorry for the delay, problems to the my $DAYWORK Ok. First of all, elibc (debian/ubuntu recently) and glibc cover probably 95% of the Linux distributions, and they are compatible, in particular for the MALLOC_CHECK http://lwn.net/Articles/333755/ - i have also checked the source. A considerable part of the remaining operating systems are like BSD - FreeBSD for example - and MacOSX, FreeBSD based. In fact, these latter two have different malloc library and it may be necessary to activate different controls for different systems (see the first reference) http://permalink.gmane.org/gmane.network.openvswitch.devel/14838 http://www.unix.com/man-page/freebsd/5/malloc.conf/ But the benefits of automating these tests is to do a better AUTOQA for the buildsystem. It is also not true, as experience shows, that all developers know everything. Beeing expert in LDAP and C programming, for example, does not mean necessarily be an expert in everything: this can certainly be true for the OPENLDAP developers but it is not always the case. Here some examples: http://lists.fedoraproject.org/pipermail/devel/2010-May/135683.html (this check had found many bug that the upstream developer haven't catched) or this, from my mantainer, http://lists.gnupg.org/pipermail/gcrypt-devel/2010-June/001605.html I saw that you have closed the case(WANTFIX i think), however, I have to tell you better my opinion. If, as can happen, you decide that my reasons make sense, i can reroll my patch for Linux, macos and freebsd. Let me know. Thanks anyway for your reply > > -- Kurt >

1 0

Re: (ITS#7414) rwm: ldapmodify, slapd segmentation fault
by jvcelak＠redhat.com 12 Oct '12

12 Oct '12

> > The slapd daemon will crash, here is the full backtrace: > > Thanks for the detailed report. Fixed now in master. > Thank you for the very fast resolution. Jan

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