I'm using perl-ldap-0.22 and I've notice something strange in my logs when I
modify an entry. I'm using MessagingDirect LDAP/X500 product for my directory
server.
$ldap->modify($dn, replace => { 'generationQualifier' => 'JR' });
If the 'generationQualifier' attribute doesn't exist, the logs show a successful
modify to this entry. Not a problem.
$ldap->modify($dn, replace => { 'generationQualifier' => [] });
If the 'generationQualifier' attribute exists, the logs show a successful modify
to this entry. Again, not a problem.
$ldap->modify($dn, replace => { 'generationQualifier' => 'SR' });
If the 'generationQualifier' attribute exists, the log first shows an "Error
sent: Attribute" for the first attempt modify, followed by a successful modify
to the record.
I have not turned on full logging to see exactly what is being attempted twice
and why the first always fails and the second succeeds. I wanted to see if
anyone can tell me what the "ldap->modify replace" option is actually doing
behind the scenes. I don't have a test server running so turning on the full
logging on our production server is my last resort.
Any feedback would be greatly appreciated. Thanks.
Mark Murphy Wayne State University
Lead Applications Technical Analyst Computing & Information Technology (C&IT)
(313) 577-4795 Voice Internet Services (IS)
(313) 577-8787 Fax 5425 Woodward Ave.
Detroit, MI. 48202
Email: aa...@wa...
WWW : http://www.wayne.edu/
------------- End Forwarded Message -------------
Mark Murphy Wayne State University
Lead Applications Technical Analyst Computing & Information Technology (C&IT)
(313) 577-4795 Voice Internet Services (IS)
(313) 577-8787 Fax 5425 Woodward Ave.
Detroit, MI. 48202
Email: aa...@wa...
WWW : http://www.wayne.edu/
|
