1 .\" Copyright (c) 1996 David Nugent <davidn@blaze.net.au>
2 .\" All rights reserved.
4 .\" Redistribution and use in source and binary forms, with or without
5 .\" modification, is permitted provided that the following conditions
7 .\" 1. Redistributions of source code must retain the above copyright
8 .\" notice immediately at the beginning of the file, without modification,
9 .\" this list of conditions, and the following disclaimer.
10 .\" 2. Redistributions in binary form must reproduce the above copyright
11 .\" notice, this list of conditions and the following disclaimer in the
12 .\" documentation and/or other materials provided with the distribution.
13 .\" 3. This work was done expressly for inclusion into FreeBSD. Other use
14 .\" is permitted provided this notation is included.
15 .\" 4. Absolutely no warranty of function or purpose is made by the author
17 .\" 5. Modifications may be freely made to this file providing the above
18 .\" conditions are met.
20 .\" $FreeBSD: src/usr.bin/limits/limits.1,v 1.14.2.10 2003/02/25 20:31:18 trhodes Exp $
27 .Nd set or display process resource limits
33 .Op Fl cdfklmnstuv Op val
37 .Op Fl cdfklmnstuv Op val
39 .Op Ar name Ns = Ns Ar value ...
45 .Op Fl cdflmnstuv Op val
49 .Op Fl cdflmnstuv Op val
51 .Op Ar name Ns = Ns Ar value ...
56 utility either prints or sets kernel resource limits, and may optionally set
57 environment variables like
59 and run a program with the selected resources.
63 .Bl -tag -width indent
67 .Op Ar name Ns = Ns Ar value
70 This usage sets limits according to
72 optionally sets environment variables given as
73 .Ar name Ns = Ns Ar value
74 pairs, and then runs the specified command.
79 This usage determines values of resource settings according to
81 does not attempt to set them and outputs these values to
83 By default, this will output the current kernel resource settings
84 active for the calling process.
89 flags, you may also display the current resource settings modified
90 by the appropriate login class resource limit entries from
93 login capabilities database.
96 .Fl e Op Ar limitflags
98 This usage determines values of resource settings according to
100 but does not set them itself.
101 Like the previous usage it outputs these values to standard
102 output, except that it will emit them in
104 format, suitable for the calling shell.
105 The calling shell is determined by examining the entries in the
107 filesystem for the parent process.
108 If the shell is known (i.e. it is one of sh, csh, bash, tcsh, ksh,
111 emits 'limit' or 'ulimit' commands in the format understood by
113 If the name of the shell cannot be determined, then the 'ulimit'
118 This is very useful for setting limits used by scripts, or prior
119 launching of daemons and other background tasks with specific
120 resource limit settings, and provides the benefit of allowing
121 global configuration of maximum resource usage by maintaining a
122 central database of settings in the login class database.
124 Within a shell script,
126 will normally be used with eval within backticks as follows:
128 .Dl eval `limits -e -C daemon`
130 which causes the output of
132 to be evaluated and set by the current shell.
137 specified in the above contains one or more of the following options:
138 .Bl -tag -width "-d [limit]"
140 Use current resource values, modified by the resource entries applicable
141 for the login class "class".
143 Use current resource values, modified by the resource entries applicable
144 to the login class which "user" belongs to.
145 If the user does not belong to a class, then the resource capabilities
146 for the "default" class are used, if it exists, or the "root" class if
147 the user is a superuser account.
149 Select display or setting of "soft" (or current) resource limits.
150 If specific limits settings follow this switch, only soft limits are
151 affected unless overridden later with either the
157 Select display or setting of "hard" (or maximum) resource limits.
158 If specific limits settings follow this switch, only hard limits are
159 affected until overridden later with either the
165 Select display or setting of both "soft" (current) or "hard" (maximum)
167 If specific limits settings follow this switch, both soft and hard
168 limits are affected until overridden later with either the
174 Select "eval mode" formatting for output.
175 This is valid only on display mode and cannot be used when running a
177 The exact syntax used for output depends upon the type of shell from
186 Select or set (if 'limit' is specified) the
189 A value of 0 disables core dumps.
191 Select or set (if 'limit' is specified) the
213 resource limit. The system-wide limit on the maximum number of
214 open files per process can be viewed using the 'sysctl kern.maxfilesperproc'
215 command. The total number of simultaneously open files in the entire
216 system is limited to the value displayed by the 'sysctl kern.maxfiles'
229 resource limit. The system-wide limit on the maximum number of processes
230 allowed per UID can be viewed using the 'sysctl kern.maxprocperuid' command.
231 The maximum number of processes that can be running simultaneously
232 in the entire system is limited to the value given by
233 the 'sysctl kern.maxproc' command.
238 This limit encompasses the entire VM space for the user process
239 and is inclusive of text, data, bss, stack,
249 in the above set of options consist of either the
256 for an infinite (or kernel-defined maximum)
257 limit, or a numeric value optionally followed by a suffix.
258 Values which relate to size default to a value in bytes, or one of the
259 following suffixes may be used as a multiplier:
261 .Bl -tag -offset indent -width 4n -compact
265 kilobytes (1024 bytes).
267 megabytes (1024*1024 bytes).
276 resource defaults to a number of seconds, but a multiplier may be
277 used, and as with size values, multiple values separated by a valid
278 suffix are added together:
280 .Bl -tag -offset indent -width 4n -compact
294 .Bl -tag -width ".Fl C Ar class"
298 to completely ignore the environment it inherits.
300 Force all resource settings to be displayed even if
301 other specific resource settings have been specified.
302 For example, if you wish to disable core dumps when starting up
303 the Usenet News system, but wish to set all other resource settings
304 as well that apply to the
306 account, you might use:
308 .Dl "eval `limits -U news -aBec 0`"
312 call, only the superuser may raise process
315 Non-root users may, however, lower them or change
318 within to any value below the hard limit.
319 When invoked to execute a program, the failure of
321 to raise a hard limit is considered a fatal error.
327 exits with EXIT_FAILURE if usage is incorrect in any way; i.e. an invalid
328 option, or set/display options are selected in the same invocation,
330 is used when running a program, etc.
331 When run in display or eval mode,
333 exits with a status of EXIT_SUCCESS.
334 When run in command mode and execution of the command succeeds, the exit status
335 will be whatever the executed program returns.
350 utility does not handle commands with equal (``='') signs in their
351 names, for obvious reasons.
353 When eval output is selected, the
355 filesystem must be installed
356 and mounted for the shell to be correctly determined, and therefore
357 output syntax correct for the running shell.
358 The default output is valid for
360 so this means that any
363 in eval mode prior mounting
365 may only occur in standard bourne
370 utility makes no effort to ensure that resource settings emitted or displayed
371 are valid and settable by the current user.
372 Only a superuser account may raise hard limits, and when doing so
375 kernel will silently lower limits to values less than
376 specified if the values given are too high.