Interactive commands cause rule failure

In the various Compliance Content component templates, certain rules that check the compliance of environment variables (such as Umask, PATH, or LD_LIBRARY_PATH) fail. An error message in the log reports that a certain interactive command caused the failure. This happens on operating systems that are using the script command (a typescript command) — Linux, AIX, Solaris, and HPUX.

Workaround:

To successfully complete the compliance check of environment variables, temporarily comment out the script command in all OS files. Alternatively, to avoid receiving failure messages, comment out the rules that check for compliance of environment variables.