Name
vxckuuid -- EDS UUID discrepancy checker
Syntax
vxckuuid [--vxdb database]
[-T limit] -i file [-t
type]
Description
vxckuuid will help find minimal differences between EDS and VXDB users. Such changes are often corrections of user data (i.e. fixing typos) on the EDS side. However, libvxmdsync (used by vxusersync and Steelmill) regards every EDS difference as a old/new user (delete/create). Since it is impossible to say whether an EDS change is just a typo or a new user, manual user intervention is required, usually by utilizing vxfixuuid and/or vxusermod, adjusting the VXDB with the new EDS data, before running vxusersync.
Options
--vxdb database |
Uses the specified database rather than the default one defined in the VXDB configuration file. |
-T limit |
Omit displaying comparisons where the computed distance is larger than limit. Defaults to 1000. |
-i file |
External Data Source input file |
-t type |
External Data Source type |
Description, continued
In External Data Source formats where no external UUID is provided, Vitalnix has to generate one. This generated UUID is based upon the user's real name, so if the real name received a typo fix, the UUID changes and triggers a new-user-discovered event in libvxmdsync. Hence you use vxfixuuid to not cause this event in the first place.
Note about complexity: vxckuuid will take linear time (O(m*n)) to calculate difference between m EDS and n VXDB users.
vxckuuid will display each EDS-VXDB user pair, sorted by
smallest difference, up to the difference limit given by the -T
option. Output will look like:
[ 1]: - EDS_Computed_UUID EDS_User_Realname
0/1/1: + VXDB_Stored_UUID VXDB_User_Realname
The number in square brackets gives the total distance. The
other three numbers denote UUID distance, Name distance and weighthing factor.
The exact algorithm can be obtained from the ckuuid.c
source
code.
See also
vxfixuuid(8), vxusermod(8), vxusersync(8)