System File Modifications
Privilege Management for Unix and Linux does not replace any Unix and Linux files or binaries during installation, but it does modify the following system files:
- /etc/inetd.conf (or xinetd.conf, launchd, systemd or SMF configuration file)
These files are automatically backed up as files with the same name and the extension .sybak.####.
The changes made to these files depend on whether a policy server host, run host, GUI host, log synchronization host, or log host is being installed. Depending on the selected installation options, each file has lines removed, added, or both.
For /etc/inetd.conf (or your xinetd.conf, launchd, or SMF configuration), the installer tries to determine the superdaemon configuration file that is used on the active system. Most systems use the superdaemon’s default configuration file name while the rest of the systems use a switch or command line format. This makes it possible to determine the superdaemon's configuration files that need to be configured. xinetd uses /etc/xinetd.conf and any specified includedir file directories.
Privilege Management for Unix and Linux used xinetd for the MacOS X 10.4 operating system. Starting with version 6.0, Privilege Management for Unix and Linux uses launchd for MacOS X 10.4. Privilege Management for Unix and Linux has always used launchd for MacOS X 10.5. For MacOS X 10.4, if Privilege Management for Unix and Linux is upgraded from an earlier release to version 6.0, its xinetd configuration is removed and replaced with the Privilege Management for Unix and Linux launchd configuration.
Removal of earlier releases of Privilege Management for Unix and Linux with version 6.0 checks for and removes the its xinetd configuration.
For MacOS X 10.4.7+, starting launchd jobs with launchctl can result in the following error message "Workaround Bonjour: Unknown error: 0." This message can be ignored. The problem has been resolved in MacOS X 10.5.
SMF is used on Solaris 10+ and uses a configuration database.
Starting with version 7.1.0, if the system Privilege Management for Unix and Linux is being installed on is IPv6-capable and the configuration of inetd, xinetd, SMF (Solaris), is being performed, the super daemon configuration is set for IPv6 rather than IPv4.