1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
|
.\" Title: limits.conf
.\" Author:
.\" Generator: DocBook XSL Stylesheets v1.72.0 <http://docbook.sf.net/>
.\" Date: 08/30/2007
.\" Manual: Linux-PAM Manual
.\" Source: Linux-PAM Manual
.\"
.TH "LIMITS.CONF" "5" "08/30/2007" "Linux\-PAM Manual" "Linux\-PAM Manual"
.\" disable hyphenation
.nh
.\" disable justification (adjust text to left margin only)
.ad l
.SH "NAME"
limits.conf \- configuration file for the pam_limits module
.SH "DESCRIPTION"
.PP
The syntax of the lines is as follows:
.PP
\fI<domain>\fR
\fI<type>\fR
\fI<item>\fR
\fI<value>\fR
.PP
The fields listed above should be filled as follows:
.PP
\fB<domain>\fR
.RS 4
.RS 4
\h'-04'\(bu\h'+03'a username
.RE
.RS 4
\h'-04'\(bu\h'+03'a groupname, with
\fB@group\fR
syntax. This should not be confused with netgroups.
.RE
.RS 4
\h'-04'\(bu\h'+03'the wildcard
\fB*\fR, for default entry.
.RE
.RS 4
\h'-04'\(bu\h'+03'the wildcard
\fB%\fR, for maxlogins limit only, can also be used with
\fI%group\fR
syntax.
.RE
.RE
.PP
\fB<type>\fR
.RS 4
.RS 4
.PP
\fBhard\fR
.RS 4
for enforcing
\fBhard\fR
resource limits. These limits are set by the superuser and enforced by the Kernel. The user cannot raise his requirement of system resources above such values.
.RE
.PP
\fBsoft\fR
.RS 4
for enforcing
\fBsoft\fR
resource limits. These limits are ones that the user can move up or down within the permitted range by any pre\-exisiting
\fBhard\fR
limits. The values specified with this token can be thought of as
\fIdefault\fR
values, for normal system usage.
.RE
.PP
\fB\-\fR
.RS 4
for enforcing both
\fBsoft\fR
and
\fBhard\fR
resource limits together.
.sp
Note, if you specify a type of '\-' but neglect to supply the item and value fields then the module will never enforce any limits on the specified user/group etc. .
.RE
.RE
.RE
.PP
\fB<item>\fR
.RS 4
.RS 4
.PP
\fBcore\fR
.RS 4
limits the core file size (KB)
.RE
.PP
\fBdata\fR
.RS 4
maximum data size (KB)
.RE
.PP
\fBfsize\fR
.RS 4
maximum filesize (KB)
.RE
.PP
\fBmemlock\fR
.RS 4
maximum locked\-in\-memory address space (KB)
.RE
.PP
\fBnofile\fR
.RS 4
maximum number of open files
.RE
.PP
\fBrss\fR
.RS 4
maximum resident set size (KB)
.RE
.PP
\fBstack\fR
.RS 4
maximum stack size (KB)
.RE
.PP
\fBcpu\fR
.RS 4
maximum CPU time (minutes)
.RE
.PP
\fBnproc\fR
.RS 4
maximum number of processes
.RE
.PP
\fBas\fR
.RS 4
address space limit (KB)
.RE
.PP
\fBmaxlogins\fR
.RS 4
maximum number of logins for this user except for this with
\fIuid=0\fR
.RE
.PP
\fBmaxsyslogins\fR
.RS 4
maximum number of logins on system
.RE
.PP
\fBpriority\fR
.RS 4
the priority to run user process with (negative values boost process priority)
.RE
.PP
\fBlocks\fR
.RS 4
maximum locked files (Linux 2.4 and higher)
.RE
.PP
\fBsigpending\fR
.RS 4
maximum number of pending signals (Linux 2.6 and higher)
.RE
.PP
\fBmsqqueue\fR
.RS 4
maximum memory used by POSIX message queues (bytes) (Linux 2.6 and higher)
.RE
.PP
\fBnice\fR
.RS 4
maximum nice priority allowed to raise to (Linux 2.6.12 and higher)
.RE
.PP
\fBrtprio\fR
.RS 4
maximum realtime priority allowed for non\-privileged processes (Linux 2.6.12 and higher)
.RE
.RE
.RE
.PP
In general, individual limits have priority over group limits, so if you impose no limits for
\fIadmin\fR
group, but one of the members in this group have a limits line, the user will have its limits set according to this line.
.PP
Also, please note that all limit settings are set
\fIper login\fR. They are not global, nor are they permanent; existing only for the duration of the session.
.PP
In the
\fIlimits\fR
configuration file, the '\fB#\fR' character introduces a comment \- after which the rest of the line is ignored.
.PP
The pam_limits module does its best to report configuration problems found in its configuration file via
\fBsyslog\fR(3).
.SH "EXAMPLES"
.PP
These are some example lines which might be specified in
\fI/etc/security/limits.conf\fR.
.sp
.RS 4
.nf
* soft core 0
* hard rss 10000
@student hard nproc 20
@faculty soft nproc 20
@faculty hard nproc 50
ftp hard nproc 0
@student \- maxlogins 4
.fi
.RE
.SH "SEE ALSO"
.PP
\fBpam_limits\fR(8),
\fBpam.d\fR(5),
\fBpam\fR(8)
.SH "AUTHOR"
.PP
pam_limits was initially written by Cristian Gafton <gafton@redhat.com>
|
