16.12.2012 Views

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

are given. If the -h flag is given, the hard limits are used instead of the current<br />

limits. The hard limits impose a ceiling on the values of the current limits. All hard<br />

limits can be raised only by a process which has superuser authority but a user<br />

may lower or raise the current limits within the legal range. If a user attempts to<br />

make a soft limit ″unlimited″, and their effective UID is not 0, then limit (or unlimit)<br />

will set the soft limit to the current hard limit value.<br />

Resources currently include:<br />

addressspace<br />

The maximum address space size for the process, measured in kilobytes. If<br />

the limit is exceeded, malloc() and mmap() functions will fail. Also,<br />

automatic stack growth will fail. An attempt to set the address space size<br />

limit lower than the current usage or higher than the existing hard limit will<br />

fail.<br />

coredumpsize<br />

The size of the largest core dump file that will be created. A value of 0<br />

(zero) prevents file creation. Dump file creation will stop at this limit.<br />

cputime<br />

The maximum amount of CPU time, in seconds, to be used by each<br />

process. If the limit is exceeded, a SIGXCPU signal is sent to the process<br />

and the process is granted a small CPU time extension to allow for signal<br />

generation and delivery. If the extension is used up, the process is<br />

terminated with a SIGKILL signal. An attempt to set the CPU limit lower<br />

than that already used will fail.<br />

datasize<br />

The data size limit is the maximum size of the break value for the process,<br />

in units of 1024 bytes. This resource always has unlimited hard and soft<br />

limits.<br />

descriptors<br />

The maximum number of open file descriptors allowed for the process. This<br />

number is one greater than the maximum value that may be assigned to a<br />

newly created descriptor. Any function that attempts to create a new file<br />

descriptor beyond the limit will fail. An attempt to set the open file<br />

descriptors limit lower than that already used will fail.<br />

filesize<br />

tcsh: limit<br />

The largest single file which can be created by a process. A value of 0<br />

(zero) prevents file creation. If the size is exceeded, a SIGXFSZ signal is<br />

sent to the process. If the process is blocking, catching, or ignoring<br />

SIGXFSZ, continued attempts to increase the size of a file beyond the limit<br />

will fail<br />

memlimit<br />

The amount of storage, in megabytes, above the 2 gigabyte bar that a<br />

process is allowed to have allocated and unhidden at any given time. An<br />

attempt to set the storage size limit lower than the current usage or higher<br />

than the existing hard limit will fail.<br />

stacksize<br />

The maximum size of the automatically-extended stack region for a<br />

process. The stack is a per-thread resource that has unlimited hard and soft<br />

limits.<br />

maximum-use may be given as a (floating point or integer) number followed by a<br />

scale factor. For cputime the default scaling is seconds, while m for minutes or h for<br />

Chapter 2. Shell command descriptions 683

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!