|
|
This section describes ClearCase functionality specific to the Solaris SPARC (sun5) platform, with references to other places in the documentation set where more information is available.
In the Administrator's Guide, the chapters on administering scheduled jobs (in particular, the chapter that discusses altering scripts that use the find / command) discuss modifying crontab entries or other scripts to prevent recursion. On Solaris systems, the standard cron job for removing old .nfs files is now in the script /usr/lib/fs/nfs/nfsfind, which is called by the root crontab, so you do not need a separate root crontab entry for removing old .nfs files. However, you could use the -prune option with any find commands in the crontab file to prevent recursion into mounted VOBs.
For example, you could replace an entry like this one
|
15 3 * * * find / -name core -mtime +7 |
|
...-exec rm -f {} ';' -o -fstype nfs -prune |
|
15 3 * * * find / -name core -mtime +7 |
|
...-exec rm -f {} ';' -o -fstype nfs -prune |
|
...-o -fstype mvfs -prune |
NOTE: In the previous example, long lines are broken for readability. In actual crontab files, each entry must be contained on a single physical text line.
The chapter Improving Client Host Performance in the Administrator's Guide describes changes you can make to improve performance of ClearCase clients. Use the information in this section in conjunction with the material in that chapter.
The instructions that follow increase the size of the MVFS cache in such a way that the changes are persistent.
Become the root user.
Shut down ClearCase.
# /etc/init.d/atria stop
Edit the file /etc/system. You can make the change in only one of the following ways:
Add this line:
set mvfs:mvfs_largeinit = 1
For one or more of the MVFS cache parameters listed in the chapter Improving Client Host Performance in the Administrator's Guide, create an entry of the form:
set mvfs:parameter = value
For example, you may establish the following parameter settings to increase cache sizes:
set mvfs:mvfs_mnmax=8192
set mvfs:mvfs_vobfreemax=1800
set mvfs:mvfs_cvpfreemax=1800
set mvfs:mvfs_dncdirmax=400
set mvfs:mvfs_dncregmax=1600
set mvfs:mvfs_dncnoentmax=1600
Save the /etc/system file.
Restart the operating system.
On Solaris SPARC, by default, the lp command does not copy a file to the print spooler. Instead, it passes a path specification to link to. When you are set to a view and issue the lp command, the path specification has no view context, so the spooler cannot see the file.
To work around this issue, do one of the following:
Use lp -c to copy the file to the spooler and then print the file from there.
Use a view-extended pathname when issuing the lp command. For example:
For information about installing and configuring SoftBench to work with ClearCase on Solaris SPARC computers, see the online help on ClearCase integrations with third-party products.
On Solaris SPARC hosts, users must include /usr/ucb in their search paths. A user whose search path does not include this directory cannot use clearmake's Sun compatibility mode (-C sun) and may experience problems in other contexts that require access to standard system-supplied programs. For example, if /usr/ucb is not in your search path, whoami is not accessible, and so some scripts run by xclearcase fail.
If you use non-ClearCase access from an NFS V.2 server on a Solaris SPARC 2.6, Solaris 7, or Solaris 8 host, you must add the following line to /etc/system on each Solaris SPARC 2.6, Solaris 7, or Solaris 8 NFS V.2 server:
set nfs:nfs2_limit_inum=0
Starting with Solaris SPARC 2.6, the NFS v2 server code, by default, added a check to ensure that inode numbers have fewer than 31 bits of data. This check is not valid for file systems that use all of the 32-bit unsigned inode, such as the MVFS. Making this proposed change to /etc/system disables this check.
If this check has not been disabled, you see either File too big errors or NFS server not responding when accessing files in a VOB using non-ClearCase access.
CacheFS should only be used for cleartext storage pools. It should be considered as a form of remote NFS storage.
If you are running Solaris in an environment where no X Font Server is running, the default font used by CPF product GUIs may not be to your liking. To specify the font used by CPF product GUIs, use one of the following methods (listed in decreasing order of precedence):
Specify the font when you invoke the application on the command line:
% clearhistory -font value
Add the following lines to your .Xdefaults file (or any other mechanism that loads the font value into the Xserver resource database):
clearhistory*font: -misc-fixed-medium-*-*--15-*-*-*-*-*-*-*
cleardescribe*font: -misc-fixed-medium-*-*--15-*-*-*-*-*-*-*
cleargetlog*font: -misc-fixed-medium-*-*--15-*-*-*-*-*-*-*
clearvobadmin*font: -misc-fixed-medium-*-*--15-*-*-*-*-*-*-*
Specify the font as an environment variable.
% setenv font value
$ export font= "family:lucida sans-face:sans-size:12-encoding:iso88591-foundry:b&h"
On Solaris 7 and later, you must use the Solaris coreadm utility to enable VOB server processes to generate core files if they fail. Core files are often needed when resolving problems that cause server failures. To enable core file generation for these server processes:
Log on to the VOB server host as root.
Run the coreadm command with the -e proc-setid argument.
Verify that the system is now configured to allow core file dumps by running the coreadm command with no arguments. Look for the output line per-process setid core dumps: enabled. (This does not require root privileges).
coreadm global core file pattern :
init core file pattern : core
global core dumps : disabled
per-process core dumps : enabled
global setid core dumps : disabled
per-process setid core dumps: enabled
global core dump logging : disabled
|
|
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |
