The AccuRev Server is designed to handle multiple client commands concurrently: any number of requests that “read” data, along with one command that “writes” data. Accomplishing such concurrency typically requires that the AccuRev Server have many files open at the same time. Each operating system imposes limits on how many files can be open simultaneously. There may be an “open file descriptor” limit for each user process, or an overall limit for all user processes, or both. If the AccuRev Server hits the open file descriptor limit, additional client requests will be queued until file descriptors become available. (No client command is cancelled, and no data is lost. Hitting the open file descriptor limit just slows AccuRev Server performance.)
• (UNIX/Linux) Create a file (anyname.xml) containing the following line:
• (Windows) Use Microsoft’s Handle utility on the AccuRev Server machine to monitor the open file handles. (See the “Process Utilities” link at http:/www.sysinternals.com.)The table below indicates the default open file descriptor limits for the various AccuRev-supported operating systems. Following the table are instructions for increasing these limits.
Default Limit on Open Filehandles /usr/bin/ulimit -n <number>/usr/bin/ulimit -Hn <number> Note: if you are performing a pre-purchase evaluation of AccuRev in an environment with a limited number of users and a limited amount of data, there is no need to make any changes. The default limits will be more than adequate.The procedure for increasing a process’s maximum number of open files varies from operating system to operating system.Note: in all cases, be sure to remove file acserver.handle.limit, located in the AccuRev site_slice directory, before restarting the AccuRev Server or rebooting the operating system. This file caches the current value of the open-files limit.You must be the root user to perform the following procedure.
1. > /sbin/sysctl –w fs.file-max=10000The number you specify is stored in file /proc/sys/fs/file-max.
2. Add this line to file /etc/pam.d/login:session required pam_limits.so
3. Change the capabilities of the Bash shell command ulimit, by creating or editing the “nofile” (number of open files) lines in file /etc/security/limits.conf. Example:* soft nofile 1024
* hard nofile 10000
• A Bash shell can execute the command ulimit –n number, with 65535 as the maximum value of number. This enables that particular shell (and its subprocesses) to have up to number open files. (The person executing the ulimit command doesn’t need to know what the “hard limit” specified in /etc/security/limits.conf is — he can just enter the command as ulimit –n unlimited to get the maximum value.)
4. Test your change by entering a ulimit command in a Bash shell, setting the limit somewhere in between the soft and hard specifications you made in Step 3. For example:> /bin/bash$ ulimit -n 5000You must be the root user to perform the following procedure.> sam
2.
3. Select the maxusers parameter.
5. Invoke the Actions > Process New Kernel command, to create a new HP-UX kernel.
AccuRev, Inc. |
Phone: 781-861-8700 |
Fax: 781-861-8704 |
support@accurev.com |