Problem
In previous releases of SCO UNIX software, the Sysamdsh(ADM) was used to control which password entity, the protected password database or /etc/password, was considered the "master" file in the event that discrepancies developed between the two files.
However, I do not see this functionality in the SCOAdmin(F) Account Manager utility in SCO OpenServer Release 5.
How do I control which password entity is the master file in the event of password file corruption?
Solution
Setting the master password file is a command line option in
SCO OpenServer Release 5. See the entry for usermod(ADM) for
additional information.The correct command to enable the protected password (tcb) database as the master is:
# usermod -Dx "{tcbDatabaseIsMaster 1}"The correct command to disable this functionality is:
# usermod -Dx "{tcbDatabaseIsMaster 0}"This sets /etc/passwd as the master file, which is system default.
As a final note, the information comes from the file:
/etc/auth/system/defaultHowever, it is strongly recommended that you use the libprot APIs to manipulate this file, or the command line, and not edit the files themselves.
See also
manual page entries for: scoadmin(F), useradd(ADM).