I want to mirror entries from a subtree to another virtual tree.
I tried with rwm-rewrite which works for rewriting but I want to keep the real entries.
Is therefor rwm-rewrite the wrong approach or is that possible?
Thanks in advance,
In the following post:
> However, I will note, the definitions of these attributes are RFC
> defined. They have no ORDERING rule on purpose.
I was not able to find what that purpose was. Does anyone have any
idea why it was decided that something as critical as "name"
attributes shouldn't have an ORDERING rule?
In my case, I have users who have a lower-case first-letter in their
last name, which makes them appear at the bottom of all lists of
people when sorted on the LDAP server. Needless to say, this makes
For most of my purposes, I simply sort the data in my code once it is
retrieved from the LDAP server, but in some cases I don't have control
over the software being used and therefore can't change it, and in
other cases this is terribly inefficient or impractical.
Other than "because the RFC says so", what's the reasoning behind not
defining an ORDERING rule for "name" attributes", preferably one that
is case-insensitive? Could it at least be made a build option to
enable or disable an ORDERING rule on at least that attribute (or
perhaps in a more general configurable way for other attributes as
well), even if it's not truly RFC-compliant?
Baskin Engineering, Room 313A