Parse two LDIF exports, one only with users and the other only
with group information, and check the associations between both.
Generates an output LDIF file with the proper operations to add
the missing associations. After that importing the destination
LDIF file should fix missing user/group associations.

Usage (running it without parameters or with the wrong parameters will print the message below):

#########################################################################
Group and User Association Check Utility


SYNOPSIS

grpusrfix.pl -u <path to the LDIF file with the exported users>
  -g <path to the LDIF file with the exported groups>
  -o <path to create the LDIF output file>


DESCRIPTION

grpusrfix.pl Reads both an LDIF export with all the users on an eDirectory
tree, and an LDIF export with all groups in the same eDirectory tree, then
check the associations between users and groups. Those associations involve
four attributes, two on the user side and two on the group side. It then 
creates an output LDIF file with the proper operations to add any missing
associations in the exported files.

After generating the destination LDIF file, this file should be imported 
back in the eDirectory tree from which the user and group exports were 
generated.


SWITCHES

-u <path to the LDIF file with the exported users>
   Set the path to the LDIF file with the exported users. This file should
   have ONLY user objects, and it has to have at the very minimum the 
   following user attributes: SecurityEquals and GroupMembership
   
-g <path to the LDIF file with the exported groups>
   Set the path to the LDIF file with the exported groups.This file should
   have ONLY group objects, and it has to have at the very minimum the
   following group attributes: EquivalentToMe and Member

-o <path to create the LDIF output file>
   Set the path were the output LDIF file will be created, as well as its
   filename. This file will contain any LDIF operations necessary to add 
   back missing associations between users and groups in the eDirectory 
   tree, if any
#########################################################################