ADIC 4.3 Operating System Requirements, Operating Issues, Patches, YEAR 2000 COMPLIANT CR #237

Operating System Requirements

Patches

NOTE: ADIC recommends that you install all required Y2k patches for your machine.

Make sure you install all the patches that your vendor recommends for your kernel, operating system, network, hardware, media, drive type, and storage devices.

Additionally, ADIC requires the patches, filesets, or packages listed below to successfully operate FileServ. Obtain these patches from the appropriate vendor.

Platform	Patch	Description
IRIX 6.5.8f	SG0004026	Fixes lost read events. Even though the feature release is not officially
		supported, if you choose this release you must have this patch.
Solaris 7	Update	Maintenance update.
	2107022-04
	107587-01	System accounting, (Usr).
	Recommended	Includes nine patches.
	Patch Cluster
	09/02/1999

YEAR 2000 COMPLIANT (CR #237)

When FileServ is running on Year 2000-compliant operating systems, including systems with Y2K-compliant patches, FileServ is Year 2000 Option 1-compliant. Basically, this means that a year is designated as a four-digit number, for example, 2000. (FileServ has been Year 2000-compliant since Version 3.5.)

Operating Issues

fileserv -t -y LEAVES UNWANTED PROCESSES RUNNING (CR #921)

•Running fileserv -t-yunconditionally exits after the number of seconds specified in the sysparm value configured in the $FS_TERMTIMEOUT_VALUE parameter. After FileServ terminates, there may be unwanted processes still running. To check for these processes, type the following:

#ps -elf grep fs_

#ps -elf grep fsadm

Look for processes that should not be running, and determine which ones need to be terminated.

fsloglevel COMMAND (CR #829)

•The fsloglevel command does not affect all log messages. A more reliable method for changing the logging level is to modify the FS_LOG_LEVEL variable in the $FS_HOME/sysparm/fs_sysparm file.

www.adic.com FileServ Version 4.3—600726 Rev A Page 9 of 22