Re: Enabling monitor backend mucks with slapcat (ITS#2343)

[quanah@stanford.edu]

--On Monday, March 03, 2003 10:56 PM +0100 Pierangelo Masarati 
<ando@sys-net.it> wrote:

>
>> Full_Name: Quanah Gibson-Mount
>> Version: 2.1.14
>> OS: Solaris 8
>> URL: ftp://ftp.openldap.org/incoming/
>> Submission from: (NULL) (171.64.19.82)
>>
>>
>> Hello,
>>
>> After upgrading to OpenLDAP 2.1.14 and enabling the monitor backend,
>> slapcat now complains when run from the command line that the database
>> doesn't support being exported.  I can get around this by doing a
>> slapcat -n 2.  However, why does it even try to export the monitor
>> backend DB if it isn't exportable?
>
> What version did you upgrade from? I went back in source code
> and I couldn't find any trace of changes that could have allowed
> slapcat of monitor backend, nor enabled tools to skip it.
>
> I understand your point, but you may well use -n 2 or move
> the "database monitor" directive to the end of your slapd.conf
>
> I added a fix that selects the first legal database and improves
> database selection checks.  However, I'd suggest to always specify
> what database one is dumping, to avoid nasty misunderstandings.

Thanks for the fix. :)  I did reorder my definitions so our primary DB will 
now always be the first encountered. ;)

--Quanah

--
Quanah Gibson-Mount
Senior Systems Administrator
ITSS/TSS/Computing Systems
Stanford University
GnuPG Public Key: http://www.stanford.edu/~quanah/pgp.html