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