If you use the file type KcsSolarisFile in the KcsLoadProfile() function, you must install profiles where the KCMS framework can locate them. The KCMS framework searches for profiles in the following directories in the order listed below:
Local current directory
Typically a CMM creates profiles in the directory in which it is being run.
Directories specified by the KCMS_PROFILES
environment variable
KCMS_PROFILES
is a colon-separated
list of directory paths to profiles. You can set this variable on a per-user
or work-group basis. You may want to use this variable to set the path to
temporary profiles your CMM creates.
/etc/openwin/devdata/profiles
This directory contains the local or machine-specific copies of configured profiles, for example, X Window System visual profiles.
/usr/openwin/etc/devdata/profiles
This directory always contains read-only files.
All profiles for distribution (whether you create them or they are supplied with the Solaris operating system) should be written as superuser and read only to protect them from being overwritten.
If you use the file type KcsFile in the KcsLoadProfile() function, when the application opens the profile, you can name it anything you want.