Package: slapd
Version: 2.2.23-1
Hello,
as you wrote in bug 304738 that all problems should be reported, I'll
report two bugs I hit during upgrading my systems.
During upgrade from 2.1.x to 2.2.23 it dumped out ldap database,
converted slapd.conf to new format - and failed to start slapadd with
new configuration.
Problem is that if you have
access to XXX
<spaces>by dn.exact="...." read
<spaces>by...
<spaces>
access to XXX
<spaces>by dn.exact="...." read
...
then both access lines are merged together, and slapd dies because it
finds 'access to' in the middle of line, not at the beginning. Regexp
should be probably stricter - \n\s+\n sequence matches regexp
\n(?!\n)\s+ you are using. One solution seems to use \n(?!\n)\s and
then allow repeated space occurences (which you must handle anyway,
as 'by dn.exact' is not optimized to 'by dn.exact' by current
parser either).
Actually, what's reason for folding lines together? Nice formatted
configuration I used in 2.1.x still works, and configuration 2.2.x
created is rather unmanageable, as it creates lines over 16KB long
in case of our ACL configuration (even after I split incorrectly
merged lines).
Thanks,
Petr Vandrovec
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
