User`s guide

Reference 98
--othersockbuf bar:lim
Total size in bytes of UNIX-domain socket buffers,
UDP and other datagram protocol send buffers.
--dgramrcvbuf bar:lim
Total size in bytes of receive buffers of UDP and other
datagram protocols.
--oomguarpages bar:lim
Out-of-memory guarantee, in 4 Kb pages. Any VPS
process will not be killed even in case of heavy memory
shortage if the current memory consumption (including
both physical memory and swap) does not reach the
oomguarpages barrier. In this version of OpenVZ,
the limit shall be set to the same value as the barrier.
--lockedpages bar:lim
Memory not allowed to be swapped out (locked with
the mlock() system call), in 4-Kb pages.
--shmpages bar:lim
Total size of shared memory (including IPC, shared
anonymous mappings and tmpfs objects), allocated by
processes of particular VPS, in 4 Kb pages.
--privvmpages bar:lim
Size in 4 Kb pages of private (or potentially private)
memory, allocated by Virtual Private Server
applications. Memory that is always shared among
different applications is not included in this resource
parameter.
--numfile bar:lim
Number of files opened by all VPS processes. In this
version of OpenVZ, the limit shall be set to the same
value as the barrier.
--numflock bar:lim
Number of file locks created by all VPS processes.
--numpty bar:lim
Number of pseudo-terminals. For example, ssh
session, screen, xterm application consumes
pseudo-terminal resource. In this version of OpenVZ,
the limit shall be set to the same value as the barrier.
--numsiginfo bar:lim
Number of siginfo structures (essentially this
parameter limits size of signal delivery queue). In this
version of OpenVZ, the limit shall be set to the same
value as the barrier.
--dcache bar:lim
Total size in bytes of dentry and inode structures
locked in memory. Exists as a separate parameter to
impose a limit causing file operations to sense memory
shortage and return an error to applications,
protecting from excessive consumption of memory due
to intensive file system operations.
--cpuunits units
Allowed CPU power. This is a positive integer number,
which determines the minimal guaranteed share of the
CPU the Virtual Private Server will receive. You may
estimate this share as ((VPS CPUUNITS)/(Sum of CPU
UNITS across all busy Virtual Private Servers))*100%.
The total CPU power depends on CPU and OpenVZ
reporting tools consider one 1 GHz PIII Intel processor
to be equivalent to 50,000 CPU units.
--cpulimit percent
This is a positive number indicating the CPU time in per
cent the corresponding VPS is not allowed to exceed.