Installation guide

An NFS Version 2 or Version 3 client can mount a maximum of 2048
files or directories.
• Memory mapped file limit
The maximum supported size of a file that can be mapped into memory
without segmenting the file depends on the virtual address space limits, as
documented in the section on memory limits.
• Open files limit
The open-max-soft and open-max-hard attributes control the
maximum number of open file descriptors per process for all processes.
The default value is 4096. When the open-max-soft limit is reached,
a warning message is issued, and when the open-max-hard limit is
reached, the process is stopped. The maximum number of open files per
process is 65,536. If you increase the maximum number of open files per
process, make sure that you adjust the value of the max-vnodes
attribute.
File descriptor entries in the per process file table are dynamically
allocated after the initial 64 entries in the utask structure are used.
• File locking limits
The Tru64 UNIX file record locking service allows applications to lock
any number of bytes in a file in the range of 0 to 2
63
− 1, inclusive. File
locking is supported by UFS, AdvFS, and both NFS Version 2 and
Version 3. Because the NFS Version 2 protocol suite allows ranges to be
specified only with 32-bit numbers, it supports a file locking range of 0 to
2
31
− 1, inclusive.
• Pathname limits
AdvFS, UFS, CDFS, and NFS support a maximum pathname component
of 255 bytes and a maximum file pathname of 1023 bytes.
A.1.8 Networking Limits
The networking limits are as follows:
• Pseudoterminals (ptys)
The maximum number of supported ptys is 8192.
• LAT connections
– The maximum number of incoming LAT connections is 4800.
– The maximum number of outgoing LAT connections is 4000.
• IP alias addresses
Tru64 UNIX allows the use of up to 5,000 IP alias addresses before
System Limits A–7