If you see this message after logging in:
LOGIN: ERROR- Failed to initialize policy manager.(SCO_PM_FATAL) Login session denied.Either the policy manager daemon, /etc/sco, has stopped and not restarted, or some crucial file required by the policy manager to satisfy the login request is missing or corrupted.
Here are possible specific sources of corruption or malfunction:
The policy manager (/etc/sco_pmd) must be present
and running for your system to function.
In the Software Manager, choose
Software Verify Software
and select Broken/missing symbolic links.
This will check and possibly repair
the link from /etc/sco_pmd
to the /opt/K/SCO hierarchy. You can also
perform this operation on the policy manager package alone
by making the following successive selections first:
SCO OpenServer Enterprise System
SCO OpenServer Enterprise System UNIX
SCO OpenServer Enterprise System Core OS
Base Operating System
If the sco_pmd binary is actually missing from the
/opt/K/SCO directory tree, you can use the
command to install a single file from the installation media.
In the case of CD-ROM media and
the CD-ROM device /dev/cd0, the command would be:
customextract -m /dev/cd0 /opt/K/SCO/Unix/*/pmd/sco_pmd
After the restore is complete, you should use the Software Manager to verify the link in /etc.
The directory /pmd and/or its contents, the named streams pipes IPCCT_pipe and IPCST_pipe| and the file sco_pmd.pid, are corrupted or missing.
If /pmd exists, but any of its file contents do not, they may be restored by stopping and restarting /etc/sco_pmd. To do this:
This has been identified as a common reason for policy manager-related failures. Of course, in this case, the policy manager errors would accompany many write failures to /dev/root, with corresponding error messages.
It is usually sufficient to check this by examining the file /etc/default/filesys for nondefault root filesystem settings, such as mountflags=-r, or mntopts="-o ro" If such settings are found, remove them.
First, determine how many users are already logged in to the system with the brand(ADM) command; see ``Displaying login licenses in use''. A user is defined as a distinct physical keyboard or a login over the network. If the system has run out of licenses to check out, the only way to avoid the error message is to add user licenses by purchasing an additional-user license product.
If the login user count has not been exceeded, it is possible that the license database itself has been corrupted. Follow the steps below to re-apply the user licenses on the system. This procedure assumes that user licenses are supplied only through the SCO OpenServer Enterprise System License. If you have already licensed additional users with a separate user-license product, apply the procedure to that product first.
Repeat the grep command to verify that the sco_pmd daemon is now running.
Issue the command:
Note the first line of the output (
streams allocation: config alloc free total max fail streams 292 110 182 337172 126 0 . . .If the
streamsline shows a
failgreater than zero, then run the Hardware/Kernel Manager or the configure(ADM) command and increase the NSTREAM kernel parameter. See ``Tuning STREAMS usage'' for more information.