3830 SIGQUEUE_MAX's limit of 32 is too low
1 '\" te
2 .\" Copyright (c) 2007, Sun Microsystems, Inc. All Rights Reserved.
3 .\" The contents of this file are subject to the terms of the Common Development and Distribution License (the "License"). You may not use this file except in compliance with the License.
4 .\" You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing. See the License for the specific language governing permissions and limitations under the License.
5 .\" When distributing Covered Code, include this CDDL HEADER in each file and include the License file at usr/src/OPENSOLARIS.LICENSE. If applicable, add the following below this CDDL HEADER, with the fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
6 .TH RESOURCE_CONTROLS 5 "Jul 2, 2007"
7 .SH NAME
8 resource_controls \- resource controls available through project database
9 .SH DESCRIPTION
10 .sp
11 .LP
12 The resource controls facility is configured through the project database. See
13 \fBproject\fR(4). You can set and modify resource controls through the
14 following utilities:
15 .RS +4
16 .TP
17 .ie t \(bu
18 .el o
19 \fBprctl\fR(1)
20 .RE
21 .RS +4
22 .TP
23 .ie t \(bu
24 .el o
25 \fBprojadd\fR(1M)
26 .RE
27 .RS +4
28 .TP
29 .ie t \(bu
30 .el o
31 \fBprojmod\fR(1M)
32 .RE
33 .RS +4
34 .TP
35 .ie t \(bu
36 .el o
37 \fBrctladm\fR(1M)
38 .RE
39 .sp
40 .LP
41 In a program, you use \fBsetrctl\fR(2) to set resource control values.
42 .sp
43 .LP
44 In addition to the preceding resource controls, there are resource pools,
45 accessible through the \fBpooladm\fR(1M) and \fBpoolcfg\fR(1M) utilities. In a
46 program, resource pools can be manipulated through the \fBlibpool\fR(3LIB)
47 library.
48 .sp
49 .LP
50 The following are the resource controls are available:
51 .sp
52 .ne 2
53 .na
54 \fB\fBprocess.max-address-space\fR\fR
55 .ad
56 .sp .6
57 .RS 4n
58 Maximum amount of address space, as summed over segment sizes, that is
59 available to this process, expressed as a number of bytes.
60 .RE
61
62 .sp
63 .ne 2
64 .na
65 \fB\fBprocess.max-core-size\fR\fR
66 .ad
67 .sp .6
68 .RS 4n
69 Maximum size of a core file created by this process, expressed as a number of
70 bytes.
71 .RE
72
73 .sp
74 .ne 2
75 .na
76 \fB\fBprocess.max-cpu-time\fR\fR
77 .ad
78 .sp .6
79 .RS 4n
80 Maximum CPU time that is available to this process, expressed as a number of
81 seconds.
82 .RE
83
84 .sp
85 .ne 2
86 .na
87 \fB\fBprocess.max-data-size\fR\fR
88 .ad
89 .sp .6
90 .RS 4n
91 Maximum heap memory available to this process, expressed as a number of bytes.
92 .RE
93
94 .sp
95 .ne 2
96 .na
97 \fB\fBprocess.max-file-descriptor\fR\fR
98 .ad
99 .sp .6
100 .RS 4n
101 Maximum file descriptor index available to this process, expressed as an
102 integer.
103 .RE
104
105 .sp
106 .ne 2
107 .na
108 \fB\fBprocess.max-file-size\fR\fR
109 .ad
110 .sp .6
111 .RS 4n
112 Maximum file offset available for writing by this process, expressed as a
113 number of bytes.
114 .RE
115
116 .sp
117 .ne 2
118 .na
119 \fB\fBprocess.max-msg-messages\fR\fR
120 .ad
121 .sp .6
122 .RS 4n
123 Maximum number of messages on a message queue (value copied from the resource
124 control at \fBmsgget()\fR time), expressed as an integer.
125 .RE
126
127 .sp
128 .ne 2
129 .na
130 \fB\fBprocess.max-msg-qbytes\fR\fR
131 .ad
132 .sp .6
133 .RS 4n
134 Maximum number of bytes of messages on a message queue (value copied from the
135 resource control at \fBmsgget()\fR time), expressed as a number of bytes.
136 .RE
137
138 .sp
139 .ne 2
140 .na
141 \fB\fBprocess.max-port-events\fR\fR
142 .ad
143 .sp .6
144 .RS 4n
145 Maximum allowable number of events per event port, expressed as an integer.
146 .RE
147
148 .sp
149 .ne 2
150 .na
151 \fB\fBprocess.max-sem-nsems\fR\fR
152 .ad
153 .sp .6
154 .RS 4n
155 Maximum number of semaphores allowed per semaphore set, expressed as an
156 integer.
157 .RE
158
159 .sp
160 .ne 2
161 .na
162 \fB\fBprocess.max-sem-ops\fR\fR
163 .ad
164 .sp .6
165 .RS 4n
166 Maximum number of semaphore operations allowed per \fBsemop\fR call (value
167 copied from the resource control at \fBsemget()\fR time). Expressed as an
168 integer, specifying the number of operations.
169 .RE
170
171 .sp
172 .ne 2
173 .na
174 \fB\fBprocess.max-stack-size\fR\fR
175 .ad
176 .sp .6
177 .RS 4n
178 Maximum stack memory segment available to this process, expressed as a number
179 of bytes.
180 .RE
181
182 .sp
183 .ne 2
184 .na
185 \fB\fBproject.cpu-caps\fR\fR
186 .ad
187 .sp .6
188 .RS 4n
189 Maximum amount of CPU resources that a project can use. The unit used is the
190 percentage of a single CPU that can be used by all user threads in a project.
191 Expressed as an integer. The cap does not apply to threads running in real-time
192 scheduling class. This resource control does not support the \fBsyslog\fR
193 action.
194 .RE
195
196 .sp
197 .ne 2
198 .na
199 \fB\fBproject.cpu-shares\fR\fR
200 .ad
201 .sp .6
202 .RS 4n
203 Number of CPU shares granted to a project for use with the fair share scheduler
204 (see \fBFSS\fR(7)). The unit used is the number of shares (an integer). This
205 resource control does not support the \fBsyslog\fR action.
206 .RE
207
208 .sp
209 .ne 2
210 .na
211 \fB\fBproject.max-contracts\fR\fR
212 .ad
213 .sp .6
214 .RS 4n
215 Maximum number of contracts allowed in a project, expressed as an integer.
216 .RE
217
218 .sp
219 .ne 2
220 .na
221 \fB\fBproject.max-crypto-memory\fR\fR
222 .ad
223 .sp .6
224 .RS 4n
225 Maximum amount of kernel memory that can be used for crypto operations.
226 Allocations in the kernel for buffers and session-related structures are
227 charged against this resource control.
228 .RE
229
230 .sp
231 .ne 2
232 .na
233 \fB\fBproject.max-locked-memory\fR\fR
234 .ad
235 .sp .6
236 .RS 4n
237 Total amount of physical memory locked by device drivers and user processes
238 (including D/ISM), expressed as a number of bytes.
239 .RE
240
241 .sp
242 .ne 2
243 .na
244 \fB\fBproject.max-lwps\fR\fR
245 .ad
246 .sp .6
247 .RS 4n
248 Maximum number of LWPs simultaneously available to a project, expressed as an
249 integer.
250 .RE
251
252 .sp
253 .ne 2
254 .na
255 \fB\fBproject.max-msg-ids\fR\fR
256 .ad
257 .sp .6
258 .RS 4n
259 Maximum number of message queue IDs allowed for a project, expressed as an
260 integer.
261 .RE
262
263 .sp
264 .ne 2
265 .na
266 \fB\fBproject.max-port-ids\fR\fR
267 .ad
268 .sp .6
269 .RS 4n
270 Maximum allowable number of event ports, expressed as an integer.
271 .RE
272
273 .sp
274 .ne 2
275 .na
276 \fB\fBproject.max-sem-ids\fR\fR
277 .ad
278 .sp .6
279 .RS 4n
280 Maximum number of semaphore IDs allowed for a project, expressed as an integer.
281 .RE
282
283 .sp
284 .ne 2
285 .na
286 \fB\fBproject.max-shm-ids\fR\fR
287 .ad
288 .sp .6
289 .RS 4n
290 Maximum number of shared memory IDs allowed for a project, expressed as an
291 integer.
292 .RE
293
294 .sp
295 .ne 2
296 .na
297 \fB\fBproject.max-shm-memory\fR\fR
298 .ad
299 .sp .6
300 .RS 4n
301 Total amount of shared memory allowed for a project, expressed as a number of
302 bytes.
303 .RE
304
305 .sp
306 .ne 2
307 .na
308 \fB\fBproject.max-tasks\fR\fR
309 .ad
310 .sp .6
311 .RS 4n
312 Maximum number of tasks allowable in a project, expressed as an integer.
313 .RE
314
315 .sp
316 .ne 2
317 .na
318 \fB\fBproject.pool\fR\fR
319 .ad
320 .sp .6
321 .RS 4n
322 Binds a specified resource pool with a project.
323 .RE
324
325 .sp
326 .ne 2
327 .na
328 \fB\fBrcap.max-rss\fR\fR
329 .ad
330 .sp .6
331 .RS 4n
332 The total amount of physical memory, in bytes, that is available to processes
333 in a project.
334 .RE
335
336 .sp
337 .ne 2
338 .na
339 \fB\fBtask.max-cpu-time\fR\fR
340 .ad
341 .sp .6
342 .RS 4n
343 Maximum CPU time that is available to this task's processes, expressed as a
344 number of seconds.
345 .RE
346
347 .sp
348 .ne 2
349 .na
350 \fB\fBtask.max-lwps\fR\fR
351 .ad
352 .sp .6
353 .RS 4n
354 Maximum number of LWPs simultaneously available to this task's processes,
355 expressed as an integer.
356 .RE
357
358 .sp
359 .LP
360 The following zone-wide resource controls are available:
361 .sp
362 .ne 2
363 .na
364 \fB\fBzone.cpu-cap\fR\fR
365 .ad
366 .sp .6
367 .RS 4n
368 Sets a limit on the amount of CPU time that can be used by a zone. The unit
369 used is the percentage of a single CPU that can be used by all user threads in
370 a zone. Expressed as an integer. When projects within the capped zone have
371 their own caps, the minimum value takes precedence. This resource control does
372 not support the \fBsyslog\fR action.
373 .RE
374
375 .sp
376 .ne 2
377 .na
378 \fB\fBzone.cpu-shares\fR\fR
379 .ad
380 .sp .6
381 .RS 4n
382 Sets a limit on the number of fair share scheduler (FSS) CPU shares for a zone.
383 CPU shares are first allocated to the zone, and then further subdivided among
384 projects within the zone as specified in the \fBproject.cpu-shares\fR entries.
385 Expressed as an integer. This resource control does not support the
386 \fBsyslog\fR action.
387 .RE
388
389 .sp
390 .ne 2
391 .na
392 \fB\fBzone.max-locked-memory\fR\fR
393 .ad
394 .sp .6
395 .RS 4n
396 Total amount of physical locked memory available to a zone.
397 .RE
398
399 .sp
400 .ne 2
401 .na
402 \fB\fBzone.max-lwps\fR\fR
403 .ad
404 .sp .6
405 .RS 4n
406 Enhances resource isolation by preventing too many LWPs in one zone from
407 affecting other zones. A zone's total LWPs can be further subdivided among
408 projects within the zone within the zone by using \fBproject.max-lwps\fR
409 entries. Expressed as an integer.
410 .RE
411
412 .sp
413 .ne 2
414 .na
415 \fB\fBzone.max-msg-ids\fR\fR
416 .ad
417 .sp .6
418 .RS 4n
419 Maximum number of message queue IDs allowed for a zone, expressed as an
420 integer.
421 .RE
422
423 .sp
424 .ne 2
425 .na
426 \fB\fBzone.max-sem-ids\fR\fR
427 .ad
428 .sp .6
429 .RS 4n
430 Maximum number of semaphore IDs allowed for a zone, expressed as an integer.
431 .RE
432
433 .sp
434 .ne 2
435 .na
436 \fB\fBzone.max-shm-ids\fR\fR
437 .ad
438 .sp .6
439 .RS 4n
440 Maximum number of shared memory IDs allowed for a zone, expressed as an
441 integer.
442 .RE
443
444 .sp
445 .ne 2
446 .na
447 \fB\fBzone.max-shm-memory\fR\fR
448 .ad
449 .sp .6
450 .RS 4n
451 Total amount of shared memory allowed for a zone, expressed as a number of
452 bytes.
453 .RE
454
455 .sp
456 .ne 2
457 .na
458 \fB\fBzone.max-swap\fR\fR
459 .ad
460 .sp .6
461 .RS 4n
462 Total amount of swap that can be consumed by user process address space
463 mappings and \fBtmpfs\fR mounts for this zone.
464 .RE
465
466 .sp
467 .LP
468 See \fBzones\fR(5).
469 .SS "Units Used in Resource Controls"
470 .sp
471 .LP
472 Resource controls can be expressed as in units of size (bytes), time (seconds),
473 or as a count (integer). These units use the strings specified below.
474 .sp
475 .in +2
476 .nf
477 Category Res Ctrl Modifier Scale
478 Type String
479 ----------- ----------- -------- -----
480 Size bytes B 1
481 KB 2^10
482 MB 2^20
483 GB 2^30
484 TB 2^40
485 PB 2^50
486 EB 2^60
487
488 Time seconds s 1
489 Ks 10^3
490 Ms 10^6
491 Gs 10^9
492 Ts 10^12
493 Ps 10^15
494 Es 10^18
495
496 Count integer none 1
497 K 10^3
498 M 10^6
499 G 10^9
500 T 10^12
501 P 10^15
502 Es 10^18
503 .fi
504 .in -2
505
506 .sp
507 .LP
508 Scaled values can be used with resource controls. The following example shows a
509 scaled threshold value:
510 .sp
511 .in +2
512 .nf
513 task.max-lwps=(priv,1K,deny)
514 .fi
515 .in -2
516
517 .sp
518 .LP
519 In the \fBproject\fR file, the value \fB1K\fR is expanded to \fB1000\fR:
520 .sp
521 .in +2
522 .nf
523 task.max-lwps=(priv,1000,deny)
524 .fi
525 .in -2
526
527 .sp
528 .LP
529 A second example uses a larger scaled value:
530 .sp
531 .in +2
532 .nf
533 process.max-file-size=(priv,5G,deny)
534 .fi
535 .in -2
536
537 .sp
538 .LP
539 In the \fBproject\fR file, the value \fB5G\fR is expanded to \fB5368709120\fR:
540 .sp
541 .in +2
542 .nf
543 process.max-file-size=(priv,5368709120,deny)
544 .fi
545 .in -2
546
547 .sp
548 .LP
549 The preceding examples use the scaling factors specified in the table above.
550 .sp
551 .LP
552 Note that unit modifiers (for example, \fB5G\fR) are accepted by the
553 \fBprctl\fR(1), \fBprojadd\fR(1M), and \fBprojmod\fR(1M) commands. You cannot
554 use unit modifiers in the project database itself.
555 .SS "Resource Control Values and Privilege Levels"
556 .sp
557 .LP
558 A threshold value on a resource control constitutes a point at which local
559 actions can be triggered or global actions, such as logging, can occur.
560 .sp
561 .LP
562 Each threshold value on a resource control must be associated with a privilege
563 level. The privilege level must be one of the following three types:
564 .sp
565 .ne 2
566 .na
567 \fB\fBbasic\fR\fR
568 .ad
569 .sp .6
570 .RS 4n
571 Can be modified by the owner of the calling process.
572 .RE
573
574 .sp
575 .ne 2
576 .na
577 \fB\fBprivileged\fR\fR
578 .ad
579 .sp .6
580 .RS 4n
581 Can be modified by the current process (requiring \fBsys_resource\fR privilege)
582 or by \fBprctl\fR(1) (requiring \fBproc_owner\fR privilege).
583 .RE
584
585 .sp
586 .ne 2
587 .na
588 \fB\fBsystem\fR\fR
589 .ad
590 .sp .6
591 .RS 4n
592 Fixed for the duration of the operating system instance.
593 .RE
594
595 .sp
596 .LP
597 A resource control is guaranteed to have one \fBsystem\fR value, which is
598 defined by the system, or resource provider. The \fBsystem\fR value represents
599 how much of the resource the current implementation of the operating system is
600 capable of providing.
601 .sp
602 .LP
603 Any number of privileged values can be defined, and only one basic value is
604 allowed. Operations that are performed without specifying a privilege value are
605 assigned a basic privilege by default.
606 .sp
607 .LP
608 The privilege level for a resource control value is defined in the privilege
609 field of the resource control block as \fBRCTL_BASIC\fR, \fBRCTL_PRIVILEGED\fR,
610 or \fBRCTL_SYSTEM\fR. See \fBsetrctl\fR(2) for more information. You can use
611 the \fBprctl\fR command to modify values that are associated with basic and
612 privileged levels.
613 .sp
614 .LP
615 In specifying the privilege level of \fBprivileged\fR, you can use the
616 abbreviation \fBpriv\fR. For example:
617 .sp
618 .in +2
619 .nf
620 task.max-lwps=(priv,1K,deny)
621 .fi
622 .in -2
623
624 .SS "Global and Local Actions on Resource Control Values"
625 .sp
626 .LP
627 There are two categories of actions on resource control values: global and
628 local.
629 .sp
630 .LP
631 Global actions apply to resource control values for every resource control on
632 the system. You can use \fBrctladm\fR(1M) to perform the following actions:
633 .RS +4
634 .TP
635 .ie t \(bu
636 .el o
637 Display the global state of active system resource controls.
638 .RE
639 .RS +4
640 .TP
641 .ie t \(bu
642 .el o
643 Set global logging actions.
644 .RE
645 .sp
646 .LP
647 You can disable or enable the global logging action on resource controls. You
648 can set the \fBsyslog\fR action to a specific degree by assigning a severity
649 level, \fBsyslog=\fR\fIlevel\fR. The possible settings for \fIlevel\fR are as
650 follows:
651 .RS +4
652 .TP
653 .ie t \(bu
654 .el o
655 \fBdebug\fR
656 .RE
657 .RS +4
658 .TP
659 .ie t \(bu
660 .el o
661 \fBinfo\fR
662 .RE
663 .RS +4
664 .TP
665 .ie t \(bu
666 .el o
667 \fBnotice\fR
668 .RE
669 .RS +4
670 .TP
671 .ie t \(bu
672 .el o
673 \fBwarning\fR
674 .RE
675 .RS +4
676 .TP
677 .ie t \(bu
678 .el o
679 \fBerr\fR
680 .RE
681 .RS +4
682 .TP
683 .ie t \(bu
684 .el o
685 \fBcrit\fR
686 .RE
687 .RS +4
688 .TP
689 .ie t \(bu
690 .el o
691 \fBalert\fR
692 .RE
693 .RS +4
694 .TP
695 .ie t \(bu
696 .el o
697 \fBemerg\fR
698 .RE
699 .sp
700 .LP
701 By default, there is no global logging of resource control violations.
702 .sp
703 .LP
704 Local actions are taken on a process that attempts to exceed the control value.
705 For each threshold value that is placed on a resource control, you can
706 associate one or more actions. There are three types of local actions:
707 \fBnone\fR, \fBdeny\fR, and \fBsignal=\fR. These three actions are used as
708 follows:
709 .sp
710 .ne 2
711 .na
712 \fB\fBnone\fR\fR
713 .ad
714 .sp .6
715 .RS 4n
716 No action is taken on resource requests for an amount that is greater than the
717 threshold. This action is useful for monitoring resource usage without
718 affecting the progress of applications. You can also enable a global message
719 that displays when the resource control is exceeded, while, at the same time,
720 the process exceeding the threshhold is not affected.
721 .RE
722
723 .sp
724 .ne 2
725 .na
726 \fB\fBdeny\fR\fR
727 .ad
728 .sp .6
729 .RS 4n
730 You can deny resource requests for an amount that is greater than the
731 threshold. For example, a \fBtask.max-lwps\fR resource control with action deny
732 causes a \fBfork()\fR system call to fail if the new process would exceed the
733 control value. See the \fBfork\fR(2).
734 .RE
735
736 .sp
737 .ne 2
738 .na
739 \fB\fBsignal=\fR\fR
740 .ad
741 .sp .6
742 .RS 4n
743 You can enable a global signal message action when the resource control is
744 exceeded. A signal is sent to the process when the threshold value is exceeded.
745 Additional signals are not sent if the process consumes additional resources.
746 Available signals are listed below.
747 .RE
748
749 .sp
750 .LP
751 Not all of the actions can be applied to every resource control. For example, a
752 process cannot exceed the number of CPU shares assigned to the project of which
753 it is a member. Therefore, a deny action is not allowed on the
754 \fBproject.cpu-shares\fR resource control.
755 .sp
756 .LP
757 Due to implementation restrictions, the global properties of each control can
758 restrict the range of available actions that can be set on the threshold value.
759 (See \fBrctladm\fR(1M).) A list of available signal actions is presented in the
760 following list. For additional information about signals, see
761 \fBsignal\fR(3HEAD).
762 .sp
763 .LP
764 The following are the signals available to resource control values:
765 .sp
766 .ne 2
767 .na
768 \fB\fBSIGABRT\fR\fR
769 .ad
770 .sp .6
771 .RS 4n
772 Terminate the process.
773 .RE
774
775 .sp
776 .ne 2
777 .na
778 \fB\fBSIGHUP\fR\fR
779 .ad
780 .sp .6
781 .RS 4n
782 Send a hangup signal. Occurs when carrier drops on an open line. Signal sent to
783 the process group that controls the terminal.
784 .RE
785
786 .sp
787 .ne 2
788 .na
789 \fB\fBSIGTERM\fR\fR
790 .ad
791 .sp .6
792 .RS 4n
793 Terminate the process. Termination signal sent by software.
794 .RE
795
796 .sp
797 .ne 2
798 .na
799 \fB\fBSIGKILL\fR\fR
800 .ad
801 .sp .6
802 .RS 4n
803 Terminate the process and kill the program.
804 .RE
805
806 .sp
807 .ne 2
808 .na
809 \fB\fBSIGSTOP\fR\fR
810 .ad
811 .sp .6
812 .RS 4n
813 Stop the process. Job control signal.
814 .RE
815
816 .sp
817 .ne 2
818 .na
819 \fB\fBSIGXRES\fR\fR
820 .ad
821 .sp .6
822 .RS 4n
823 Resource control limit exceeded. Generated by resource control facility.
824 .RE
825
826 .sp
827 .ne 2
828 .na
829 \fB\fBSIGXFSZ\fR\fR
830 .ad
831 .sp .6
832 .RS 4n
833 Terminate the process. File size limit exceeded. Available only to resource
834 controls with the \fBRCTL_GLOBAL_FILE_SIZE\fR property
835 (\fBprocess.max-file-size\fR). See \fBrctlblk_set_value\fR(3C).
836 .RE
837
838 .sp
839 .ne 2
840 .na
841 \fB\fBSIGXCPU\fR\fR
842 .ad
843 .sp .6
844 .RS 4n
845 Terminate the process. CPU time limit exceeded. Available only to resource
846 controls with the \fBRCTL_GLOBAL_CPUTIME\fR property
847 (\fBprocess.max-cpu-time\fR). See \fBrctlblk_set_value\fR(3C).
848 .RE
849
850 .SS "Resource Control Flags and Properties"
851 .sp
852 .LP
853 Each resource control on the system has a certain set of associated properties.
854 This set of properties is defined as a set of flags, which are associated with
855 all controlled instances of that resource. Global flags cannot be modified, but
856 the flags can be retrieved by using either \fBrctladm\fR(1M) or the
857 \fBsetrctl\fR(2) system call.
858 .sp
859 .LP
860 Local flags define the default behavior and configuration for a specific
861 threshold value of that resource control on a specific process or process
862 collective. The local flags for one threshold value do not affect the behavior
863 of other defined threshold values for the same resource control. However, the
864 global flags affect the behavior for every value associated with a particular
865 control. Local flags can be modified, within the constraints supplied by their
866 corresponding global flags, by the \fBprctl\fR command or the \fBsetrctl\fR
867 system call. See \fBsetrctl\fR(2).
868 .sp
869 .LP
870 For the complete list of local flags, global flags, and their definitions, see
871 \fBrctlblk_set_value\fR(3C).
872 .sp
873 .LP
874 To determine system behavior when a threshold value for a particular resource
875 control is reached, use \fBrctladm\fR to display the global flags for the
876 resource control . For example, to display the values for
877 \fBprocess.max-cpu-time\fR, enter:
878 .sp
879 .in +2
880 .nf
881 $ rctladm process.max-cpu-time
882 process.max-cpu-time syslog=off [ lowerable no-deny cpu-time inf seconds ]
883 .fi
884 .in -2
885
886 .sp
887 .LP
888 The global flags indicate the following:
889 .sp
890 .ne 2
891 .na
892 \fB\fBlowerable\fR\fR
893 .ad
894 .sp .6
895 .RS 4n
896 Superuser privileges are not required to lower the privileged values for this
897 control.
898 .RE
899
900 .sp
901 .ne 2
902 .na
903 \fB\fBno-deny\fR\fR
904 .ad
905 .sp .6
906 .RS 4n
907 Even when threshold values are exceeded, access to the resource is never
908 denied.
909 .RE
910
911 .sp
912 .ne 2
913 .na
914 \fB\fBcpu-time\fR\fR
915 .ad
916 .sp .6
917 .RS 4n
918 \fBSIGXCPU\fR is available to be sent when threshold values of this resource
919 are reached.
920 .RE
921
922 .sp
923 .ne 2
924 .na
925 \fB\fBseconds\fR\fR
926 .ad
927 .sp .6
928 .RS 4n
929 The time value for the resource control.
930 .RE
931
932 .sp
933 .LP
934 Use the \fBprctl\fR command to display local values and actions for the
935 resource control. For example:
936 .sp
937 .in +2
938 .nf
939 $ prctl -n process.max-cpu-time $$
940 process 353939: -ksh
941 NAME PRIVILEGE VALUE FLAG ACTION RECIPIENT
942 process.max-cpu-time
943 privileged 18.4Es inf signal=XCPU -
944 system 18.4Es inf none
945 .fi
946 .in -2
947
948 .sp
949 .LP
950 The \fBmax\fR (\fBRCTL_LOCAL_MAXIMAL\fR) flag is set for both threshold values,
951 and the \fBinf\fR (\fBRCTL_GLOBAL_INFINITE\fR) flag is defined for this
952 resource control. An \fBinf\fR value has an infinite quantity. The value is
953 never enforced. Hence, as configured, both threshold quantities represent
954 infinite values that are never exceeded.
955 .SS "Resource Control Enforcement"
956 .sp
957 .LP
958 More than one resource control can exist on a resource. A resource control can
959 exist at each containment level in the process model. If resource controls are
960 active on the same resource at different container levels, the smallest
961 container's control is enforced first. Thus, action is taken on
962 \fBprocess.max-cpu-time\fR before \fBtask.max-cpu-time\fR if both controls are
963 encountered simultaneously.
964 .SH ATTRIBUTES
965 .sp
966 .LP
967 See \fBattributes\fR(5) for a description of the following attributes:
968 .sp
969
970 .sp
971 .TS
972 box;
973 c | c
974 l | l .
975 ATTRIBUTE TYPE ATTRIBUTE VALUE
976 _
977 Interface Stability Evolving
978 .TE
979
980 .SH SEE ALSO
981 .sp
982 .LP
983 \fBprctl\fR(1), \fBpooladm\fR(1M), \fBpoolcfg\fR(1M), \fBprojadd\fR(1M),
984 \fBprojmod\fR(1M), \fBrctladm\fR(1M), \fBsetrctl\fR(2),
985 \fBrctlblk_set_value\fR(3C), \fBlibpool\fR(3LIB), \fBproject\fR(4),
986 \fBattributes\fR(5), \fBFSS\fR(7)
987 .sp
988 .LP
989 \fISystem Administration Guide: Virtualization Using the Solaris Operating
990 System\fR
--- EOF ---