Installation Instructions for Hot Fix B57007
64-bit Enabled Solaris
Hot fix B57007 addresses the issue(s) in Scalable Performance Data Server 4.52 on 64-bit Enabled Solaris as documented
in the Issue(s) Addressed section of the hot fix download page:
http://ftp.sas.com/techsup/download/hotfix/HF2/B57.html#B57006
IMPORTANT NOTES
-
You must have Scalable Performance Data Server 4.52 installed on your system before applying this hot fix.
Refer to SN-35968 for instructions on how to determine which product releases you have installed.
-
Files delivered in this hot fix will be backed up during the installation process.
However, it is good general practice to back up your system before applying updates
to software.
-
You must have Administrator Privileges on your CLIENT or SERVER machine.
-
All currently active SAS sessions, daemons, spawners and servers must be terminated
before applying this hot fix.
- This hot fix should be installed using the same userid who performed the initial
software installation.
INSTALLATION
1. The installer downloaded is B57007s6.bin. Verify that the installation binary
has execute permission. If it does not, use the chmod command to make
it executable.
$> chmod 755 B57007s6.bin
2. Set your $DISPLAY environment variable
export DISPLAY=<your_node_name>:0
3. Execute B57007s6.bin
<path_to_downloaded_file>/B57007s6.bin
For example:
./B57007s6.bin
This will initiate the installation wizard, which will guide you through the hot fix
installation process. During the installation you will be prompted for the
SASHOME location to be updated. You should provide the path to the
top level SAS directory where the deploymntreg directory exists.
See the Maintenance Installation Tool
(MIT) documentation for more details on the installation of hot fixes.
The content of this hot fix is listed in the hot fix manifest.
POST-INSTALLATION INSTRUCTIONS
Activate Password Database Audit Logging
To activate this feature
- Create a file called /etc/spds.rc on the SPD Server host containing the line
SYSLOG=YES
- The user creating /etc/spds.rc should not be the same as the user installing and administrating SPDS.
- /etc/spds.rc must be readable by the SPD Server (the uid who started up the server).
- An entry must be made to the /etc/syslog.conf file to indicate where
the user.notice messages will be sent. For example the following entry in /etc/syslog.conf will
send the user.notice messages to file /var/adm/messages:
user.notice /var/adm/messages
Adding SYSLOG=YES will enable logging changes to the psmgr database by the psmgr utility and
by the SPDS SMC Password Manager panel. The changes will be logged to the system log as
user.notice messages.
Messages are logged when the SPD Server password database is updated by
- an SMC operator connected to a running SPD Server
- an SPD Server administrator who started the SPD Server
- an SPD Server administrator running the password manager utility
opuser is the userid of:
- the SPD Server admin who started the SPD Server
- the SPD Server admin who started the password database utility
opuser is SPDSSMC if the change was made by the SPDS SMC
Messages sent to the syslog are:
"SPDS AUDIT opuser ADD userid "
"SPDS AUDIT opuser GROUPDEF newgroupname"
"SPDS AUDIT opuser AUTHORIZE username"
"SPDS AUDIT opuser DELETE username"
"SPDS AUDIT opuser GROUPDEL groupname"
"SPDS AUDIT opuser RESET username"
"SPDS AUDIT opuser CHGPASS username"
"SPDS AUDIT opuser GROUPMEM group1 ... group5"
"SPDS AUDIT opuser CHGAUTH userid"
"SPDS AUDIT opuser CHGEXPIRE userid"
"SPDS AUDIT opuser CHGTIMEOUT userid"
"SPDS AUDIT opuser CHGFAIL userid"
"SPDS AUDIT opuser CHGPERFCLASS userid"
"SPDS AUDIT opuser EXPORT"
This completes the installation of hot fix B57007 on 64-bit Enabled Solaris.