  Re: slapadd: which database to open  Hallvard B Furuseth
wrote: Pierangelo Masarati writes: The inexperienced or
incautious user would probably erroneously feel safe when the
wrong ldif happens to load in the right, yet unintended
database.  I don't quite get it. Which unintended database?  You
have "cn=foo" and "cn=bar"; you intend to load "cn=foo"'s LDIF
into "cn=foo", but you actually feed "cn=bar"'s LDIF to slapadd.
Slapadd succeeds, and you believe you loaded "cn=foo" while you
loaded "cn=bar". If an explicit switch must be used, and you
feed the wrong LDIF, slapadd errors out (possibly with some
explanatory message).  There is only one database into which any
entry will go, based on the DN.  Right. However, slapadd does
not behave like that, right now. It always tries to feed
database #1 (possibly skipping "cn=Monitor" and any subordinate
database).  If you just mean the user slapadds an LDIF he
shouldn't have slapadded, well, though.  The user might do lots
of things he didn't intend to, like acciden