Tool
Program Input:
LDAP source server IP address
Starting context in target eDirectory tree
Program Actions:
The program will use the IP address and context entered to extract the schema naming attributes and all object RDNs from the context entered and below. The schema naming values are then used with 'regular expressions' (regex) to identify all collisioned objects in the extracted data.
The collisioned object data is then 'context reversed' and sorted to produce all collisioned objects in container order.
The main results output file is called 'sorted_collisions.txt'.
Program Requirements:
The program should run on any Linux/Unix OS that supports ldapsearch, grep, egrep, awk, sed and cut. It has been tested on SLED10, SLES10/OES2 SP1 and SLES11.
Installation:
- Untar the code to a new directory.
- Use chmod to make sure you can execute the perl program and the shell scripts (e.g. chmod 755 *).
- Verify connectivity to the intended LDAP source by pinging the LDAP server.
- Execute the program using: perl getcolls.pl
e.g.
t=MyTree
o=MyCompany
The code will correctly handle white space in any context entered (e.g. 'ou=IT Dept.o=MyCo').
Working files created (these are retained for debug purposes and can be deleted at will):
collisions.txt dnfixed.txt dnlist.txt getdn.pl revcolls.txt schema.pl schema.txt schema2.txt schema3.txt schema4.txt schema5.txt
| Attachment | Size |
|---|---|
| eDir_collisions_v1.0.tar | 20 KB |
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.
Related Articles
User Comments
- Be the first to comment! To leave a comment you need to Login or Register
- 4881 reads


0