LDAP-UX Client Services B.04.00 with Microsoft Windows 2000/2003 Active Directory Administrator's Guide

Command, Tool, and Migration Script Reference
Client Management Tools
Appendix C 163
where infile is a binary profile file,
/etc/opt/ldapux/ldapux_profile.bin by default, and outfile is the
output file, stdout by default.
The binary profile contains mappings for all backend commands (even
those that are unused or unsupported by LDAP-UX Client Services with
Active Directory); all of which are displayed by
display_profile_cache. The actual client configuration can be
reviewed in the configuration profile LDIF file
/etc/opt/ldapux/ldapux_profile.ldif.
Examples
The following command displays the profile in the binary profile file
/etc/opt/ldapux/ldapux_profile.bin to stdout:
display_profile_cache
The following command displays the profile in the binary profile file
my_profile.bin and writes the output to the file profile:
display_profile_cache -i my_profile.bin -o profile
get_profile_entry
This tool, found in /opt/ldapux/config downloads a profile from an
LDAP directory into an LDIF file and calls create_profile_cache to
create a binary profile file, thereby activating it on the client. This tool
looks in the local client configuration file
/etc/opt/ldapux/ldapux_client.conf for the profile DN.
Syntax
get_profile_entry -s service [-o outfile ] [-D bindDN -w passwd]
[-p
profile_id ]
where service is the name of a supported service, typically NSS,
outfile is the name of a file to contain the LDIF output, by default
/etc/opt/ldapux_profile.ldif, and profile_id is <remote domain
name> or gc for PROFILE_ID field in
/etc/opt/ldapux/ldapux_client.conf. The -p option only applies if
you want to configure multiple domains.