Licensing and registering SCO products

Policy manager has died

If any application reports a license failure and you believe that this is incorrect, it is possible that either the policy manager daemon, /etc/ifor_pmd, has stopped and not restarted, or some crucial file required by the policy manager to satisfy the login request is missing or corrupted.

NOTE: You may be logged out and be unable to log in to troubleshoot the problem. Additional error messages may also appear. If so, simply turn the system off and reboot. If the error messages persist when the system is brought up, follow the procedures described here.

Here are possible specific sources of corruption or malfunction:

The /etc/ifor_pmd binary is corrupted or missing

The policy manager (/etc/ifor_pmd) must be present and running for your system to function. If the /etc/ifor_pmd file is missing, restore it from backups.

Key files or directories are missing

The directory /pmd and/or its contents, the named streams pipes IPCCT_pipe, PMDCT_pipe, LST_pipe, and the file ifor_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/ifor_pmd. In order to do this, perform these steps:

Enter the command:

ps -ef | egrep -e ifor_ -e sco | grep -v egrep
which should return lines similar to this:
```
   root    72    70   TS  80  0   Nov 26 ?        0:00 /etc/sco_cpd
   root    69     1   TS  70  0   Nov 26 ?        0:00 /etc/ifor_pmd
   root    73    70   TS  80  0   Nov 26 ?        0:01 /etc/ifor_sld
   root    70    69   TS  80  0   Nov 26 ?        0:03 /etc/ifor_pmd
```
Any of the numbers shown may vary on your system, with the exception that one of the entries should have ``1'' in the third field (parent process ID). This is the ``parent'' copy of ifor_pmd, and the other entry is the ``child'', whose parent process ID should match the second field (process ID) of the parent entry.
Kill the child ifor_pmd. In the example, the command would be:

kill 70
In a few moments, run the ps command again. You should observe that a new child ifor_pmd is running.
Check the contents of /pmd. You should see four files:

IPCCT_pipe
PMDCT_pipe
LST_pipe
ifor_pmd.pid

If licensing problems persist, kill all of the child daemons shown in the output from step 1 and remove the contents of /pmd, then enter:

/etc/ifor_pmd

The root filesystem is mounted read-only

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 root filesystem, with corresponding error messages.

You can see if the root filesystem is mounted read-only by running the Filesystem Manager. The ``Access Mode'' is listed in the main display. If this is the case, modify the mount configuration to be read-write.

No user licenses exist, or there are no more licenses

First, determine how many users are already logged in to the system. A user is defined as a distinct physical keyboard or a login over the network. If indeed 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 UnixWare 7 Certificate of License Authenticity. If you have already licensed additional users with a separate user-license product, apply the procedure to that product first.

Tell all users to log off the system.
When all users are logged off, invoke the License Manager, select UnixWare 7, and choose License Remove to remove the UnixWare 7 license.
Re-license and register UnixWare 7 choosing the appropriate options in the License Manager.
Run the grep command discussed in ``Key files or directories are missing'' to check whether the policy manager daemon is running. If two instances of the /etc/ifor_pmd process are not running, issue this command to restart the policy manager:

/etc/ifor_pmd
Repeat the grep command to verify that two instances of ifor_pmd are running.
Tell users to log back in to the system.