Print this page
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1m/zonecfg.1m
+++ new/usr/src/man/man1m/zonecfg.1m
1 1 '\" te
2 2 .\" Copyright (c) 2004, 2009 Sun Microsystems, Inc. All Rights Reserved.
|
↓ open down ↓ |
2 lines elided |
↑ open up ↑ |
3 3 .\" Copyright 2015 Joyent, Inc.
4 4 .\" 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. You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE or http://www.opensolaris.org/os/licensing.
5 5 .\" See the License for the specific language governing permissions and limitations under the License. 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
6 6 .\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 7 .TH ZONECFG 1M "Nov 4, 2015"
8 8 .SH NAME
9 9 zonecfg \- set up zone configuration
10 10 .SH SYNOPSIS
11 11 .LP
12 12 .nf
13 -\fBzonecfg\fR {\fB-z\fR \fIzonename\fR | \fB-u\fR \fIuuid\fR}
13 +\fBzonecfg\fR \fB-z\fR \fIzonename\fR
14 14 .fi
15 15
16 16 .LP
17 17 .nf
18 -\fBzonecfg\fR {\fB-z\fR \fIzonename\fR | \fB-u\fR \fIuuid\fR} \fIsubcommand\fR
18 +\fBzonecfg\fR \fB-z\fR \fIzonename\fR \fIsubcommand\fR
19 19 .fi
20 20
21 21 .LP
22 22 .nf
23 -\fBzonecfg\fR {\fB-z\fR \fIzonename\fR | \fB-u\fR \fIuuid\fR} \fB-f\fR \fIcommand_file\fR
23 +\fBzonecfg\fR \fB-z\fR \fIzonename\fR \fB-f\fR \fIcommand_file\fR
24 24 .fi
25 25
26 26 .LP
27 27 .nf
28 28 \fBzonecfg\fR help
29 29 .fi
30 30
31 31 .SH DESCRIPTION
32 32 .LP
33 33 The \fBzonecfg\fR utility creates and modifies the configuration of a zone.
34 34 Zone configuration consists of a number of resources and properties.
|
↓ open down ↓ |
1 lines elided |
↑ open up ↑ |
35 35 .sp
36 36 .LP
37 37 To simplify the user interface, \fBzonecfg\fR uses the concept of a scope. The
38 38 default scope is global.
39 39 .sp
40 40 .LP
41 41 The following synopsis of the \fBzonecfg\fR command is for interactive usage:
42 42 .sp
43 43 .in +2
44 44 .nf
45 -{\fB-z\fR \fIzonename\fR | \fB-u\fR \fIuuid\fR}
46 -zonecfg {\fB-z\fR \fIzonename | \fB-u\fR \fIuuid} subcommand\fR
45 +zonecfg \fB-z\fR \fIzonename subcommand\fR
47 46 .fi
48 47 .in -2
49 48 .sp
50 49
51 50 .sp
52 51 .LP
53 52 Parameters changed through \fBzonecfg\fR do not affect a running zone. The zone
54 53 must be rebooted for the changes to take effect.
55 54 .sp
56 55 .LP
57 56 In addition to creating and modifying a zone, the \fBzonecfg\fR utility can
58 57 also be used to persistently specify the resource management settings for the
59 58 global zone.
60 59 .sp
61 60 .LP
62 61 In the following text, "rctl" is used as an abbreviation for "resource
63 62 control". See \fBresource_controls\fR(5).
64 63 .sp
65 64 .LP
66 65 Every zone is configured with an associated brand. The brand determines the
67 66 user-level environment used within the zone, as well as various behaviors for
68 67 the zone when it is installed, boots, or is shutdown. Once a zone has been
69 68 installed the brand cannot be changed. The default brand is determined by the
70 69 installed distribution in the global zone. Some brands do not support all of
71 70 the \fBzonecfg\fR properties and resources. See the brand-specific man page for
72 71 more details on each brand. For an overview of brands, see the \fBbrands\fR(5)
73 72 man page.
74 73 .SS "Resources"
75 74 .LP
76 75 The following resource types are supported:
77 76 .sp
78 77 .ne 2
79 78 .na
80 79 \fB\fBattr\fR\fR
81 80 .ad
82 81 .sp .6
83 82 .RS 4n
84 83 Generic attribute.
85 84 .RE
86 85
87 86 .sp
88 87 .ne 2
89 88 .na
90 89 \fB\fBcapped-cpu\fR\fR
91 90 .ad
92 91 .sp .6
93 92 .RS 4n
94 93 Limits for CPU usage.
95 94 .RE
96 95
97 96 .sp
98 97 .ne 2
99 98 .na
100 99 \fB\fBcapped-memory\fR\fR
101 100 .ad
102 101 .sp .6
103 102 .RS 4n
104 103 Limits for physical, swap, and locked memory.
105 104 .RE
106 105
107 106 .sp
108 107 .ne 2
109 108 .na
110 109 \fB\fBdataset\fR\fR
111 110 .ad
112 111 .sp .6
113 112 .RS 4n
114 113 \fBZFS\fR dataset.
115 114 .RE
116 115
117 116 .sp
118 117 .ne 2
119 118 .na
120 119 \fB\fBdedicated-cpu\fR\fR
121 120 .ad
122 121 .sp .6
123 122 .RS 4n
124 123 Subset of the system's processors dedicated to this zone while it is running.
125 124 .RE
126 125
127 126 .sp
128 127 .ne 2
129 128 .na
130 129 \fB\fBdevice\fR\fR
131 130 .ad
132 131 .sp .6
133 132 .RS 4n
134 133 Device.
135 134 .RE
136 135
137 136 .sp
138 137 .ne 2
139 138 .na
140 139 \fB\fBfs\fR\fR
141 140 .ad
142 141 .sp .6
143 142 .RS 4n
144 143 file-system
145 144 .RE
146 145
147 146 .sp
148 147 .ne 2
149 148 .na
150 149 \fB\fBnet\fR\fR
151 150 .ad
152 151 .sp .6
153 152 .RS 4n
154 153 Network interface.
155 154 .RE
156 155
157 156 .sp
158 157 .ne 2
159 158 .na
160 159 \fB\fBrctl\fR\fR
161 160 .ad
162 161 .sp .6
163 162 .RS 4n
164 163 Resource control.
165 164 .RE
166 165
167 166 .SS "Properties"
168 167 .LP
169 168 Each resource type has one or more properties. There are also some global
170 169 properties, that is, properties of the configuration as a whole, rather than of
171 170 some particular resource.
172 171 .sp
173 172 .LP
174 173 The following properties are supported:
175 174 .sp
176 175 .ne 2
177 176 .na
178 177 \fB(global)\fR
179 178 .ad
180 179 .sp .6
181 180 .RS 4n
182 181 \fBzonename\fR
183 182 .RE
184 183
185 184 .sp
186 185 .ne 2
187 186 .na
188 187 \fB(global)\fR
189 188 .ad
190 189 .sp .6
191 190 .RS 4n
192 191 \fBzonepath\fR
193 192 .RE
194 193
195 194 .sp
196 195 .ne 2
197 196 .na
198 197 \fB(global)\fR
199 198 .ad
200 199 .sp .6
201 200 .RS 4n
202 201 \fBautoboot\fR
203 202 .RE
204 203
205 204 .sp
206 205 .ne 2
207 206 .na
208 207 \fB(global)\fR
209 208 .ad
210 209 .sp .6
211 210 .RS 4n
212 211 \fBbootargs\fR
213 212 .RE
214 213
215 214 .sp
216 215 .ne 2
217 216 .na
218 217 \fB(global)\fR
219 218 .ad
220 219 .sp .6
221 220 .RS 4n
222 221 \fBpool\fR
223 222 .RE
224 223
225 224 .sp
226 225 .ne 2
227 226 .na
228 227 \fB(global)\fR
229 228 .ad
230 229 .sp .6
231 230 .RS 4n
232 231 \fBlimitpriv\fR
233 232 .RE
234 233
235 234 .sp
236 235 .ne 2
237 236 .na
238 237 \fB(global)\fR
239 238 .ad
240 239 .sp .6
241 240 .RS 4n
242 241 \fBbrand\fR
243 242 .RE
244 243
245 244 .sp
246 245 .ne 2
247 246 .na
248 247 \fB(global)\fR
249 248 .ad
250 249 .sp .6
251 250 .RS 4n
252 251 \fBcpu-shares\fR
253 252 .RE
254 253
255 254 .sp
256 255 .ne 2
257 256 .na
258 257 \fB(global)\fR
259 258 .ad
260 259 .sp .6
261 260 .RS 4n
262 261 \fBhostid\fR
263 262 .RE
264 263
265 264 .sp
266 265 .ne 2
267 266 .na
268 267 \fB(global)\fR
269 268 .ad
270 269 .sp .6
271 270 .RS 4n
272 271 \fBmax-lwps\fR
273 272 .RE
274 273
275 274 .sp
276 275 .ne 2
277 276 .na
278 277 \fB(global)\fR
279 278 .ad
280 279 .sp .6
281 280 .RS 4n
282 281 \fBmax-msg-ids\fR
283 282 .RE
284 283
285 284 .sp
286 285 .ne 2
287 286 .na
288 287 \fB(global)\fR
289 288 .ad
290 289 .sp .6
291 290 .RS 4n
292 291 \fBmax-sem-ids\fR
293 292 .RE
294 293
295 294 .sp
296 295 .ne 2
297 296 .na
298 297 \fB(global)\fR
299 298 .ad
300 299 .sp .6
301 300 .RS 4n
302 301 \fBmax-shm-ids\fR
303 302 .RE
304 303
305 304 .sp
306 305 .ne 2
307 306 .na
308 307 \fB(global)\fR
309 308 .ad
310 309 .sp .6
311 310 .RS 4n
312 311 \fBmax-shm-memory\fR
313 312 .RE
314 313
315 314 .sp
316 315 .ne 2
317 316 .na
318 317 \fB(global)\fR
319 318 .ad
320 319 .sp .6
321 320 .RS 4n
322 321 \fBscheduling-class\fR
323 322 .RE
324 323
325 324 .sp
326 325 .ne 2
327 326 .na
|
↓ open down ↓ |
271 lines elided |
↑ open up ↑ |
328 327 .B (global)
329 328 .ad
330 329 .sp .6
331 330 .RS 4n
332 331 .B fs-allowed
333 332 .RE
334 333
335 334 .sp
336 335 .ne 2
337 336 .na
338 -\fB(global)\fR
339 -.ad
340 -.sp .6
341 -.RS 4n
342 -\fBzfs-io-priority\fR
343 -.RE
344 -
345 -.sp
346 -.ne 2
347 -.na
348 337 \fB\fBfs\fR\fR
349 338 .ad
350 339 .sp .6
351 340 .RS 4n
352 341 \fBdir\fR, \fBspecial\fR, \fBraw\fR, \fBtype\fR, \fBoptions\fR
353 342 .RE
354 343
355 344 .sp
356 345 .ne 2
357 346 .na
358 347 \fB\fBnet\fR\fR
359 348 .ad
360 349 .sp .6
361 350 .RS 4n
362 -\fBaddress\fR, \fBallowed-address\fR, \fBdefrouter\fR, \fBglobal-nic\fR, \fBmac-addr\fR, \fBphysical\fR, \fBproperty\fR, \fBvlan-id\fR
351 +\fBaddress\fR, \fBphysical\fR, \fBdefrouter\fR
363 352 .RE
364 353
365 354 .sp
366 355 .ne 2
367 356 .na
368 357 \fB\fBdevice\fR\fR
369 358 .ad
370 359 .sp .6
371 360 .RS 4n
372 361 \fBmatch\fR
373 362 .RE
374 363
375 364 .sp
376 365 .ne 2
377 366 .na
378 367 \fB\fBrctl\fR\fR
379 368 .ad
380 369 .sp .6
381 370 .RS 4n
382 371 \fBname\fR, \fBvalue\fR
383 372 .RE
384 373
385 374 .sp
386 375 .ne 2
387 376 .na
388 377 \fB\fBattr\fR\fR
389 378 .ad
390 379 .sp .6
391 380 .RS 4n
392 381 \fBname\fR, \fBtype\fR, \fBvalue\fR
393 382 .RE
394 383
395 384 .sp
396 385 .ne 2
397 386 .na
398 387 \fB\fBdataset\fR\fR
399 388 .ad
400 389 .sp .6
401 390 .RS 4n
402 391 \fBname\fR
403 392 .RE
404 393
405 394 .sp
406 395 .ne 2
407 396 .na
408 397 \fB\fBdedicated-cpu\fR\fR
409 398 .ad
410 399 .sp .6
411 400 .RS 4n
412 401 \fBncpus\fR, \fBimportance\fR
413 402 .RE
414 403
415 404 .sp
416 405 .ne 2
417 406 .na
418 407 \fB\fBcapped-memory\fR\fR
419 408 .ad
420 409 .sp .6
421 410 .RS 4n
422 411 \fBphysical\fR, \fBswap\fR, \fBlocked\fR
423 412 .RE
424 413
425 414 .sp
426 415 .ne 2
427 416 .na
428 417 \fB\fBcapped-cpu\fR\fR
429 418 .ad
430 419 .sp .6
431 420 .RS 4n
432 421 \fBncpus\fR
433 422 .RE
434 423
435 424 .sp
436 425 .LP
437 426 As for the property values which are paired with these names, they are either
438 427 simple, complex, or lists. The type allowed is property-specific. Simple values
439 428 are strings, optionally enclosed within quotation marks. Complex values have
440 429 the syntax:
441 430 .sp
442 431 .in +2
443 432 .nf
444 433 (<\fIname\fR>=<\fIvalue\fR>,<\fIname\fR>=<\fIvalue\fR>,...)
445 434 .fi
446 435 .in -2
447 436 .sp
448 437
449 438 .sp
450 439 .LP
451 440 where each <\fIvalue\fR> is simple, and the <\fIname\fR> strings are unique
452 441 within a given property. Lists have the syntax:
453 442 .sp
454 443 .in +2
455 444 .nf
456 445 [<\fIvalue\fR>,...]
457 446 .fi
458 447 .in -2
459 448 .sp
460 449
461 450 .sp
462 451 .LP
463 452 where each <\fIvalue\fR> is either simple or complex. A list of a single value
464 453 (either simple or complex) is equivalent to specifying that value without the
465 454 list syntax. That is, "foo" is equivalent to "[foo]". A list can be empty
466 455 (denoted by "[]").
467 456 .sp
468 457 .LP
469 458 In interpreting property values, \fBzonecfg\fR accepts regular expressions as
470 459 specified in \fBfnmatch\fR(5). See \fBEXAMPLES\fR.
471 460 .sp
472 461 .LP
473 462 The property types are described as follows:
474 463 .sp
475 464 .ne 2
476 465 .na
477 466 \fBglobal: \fBzonename\fR\fR
478 467 .ad
479 468 .sp .6
480 469 .RS 4n
481 470 The name of the zone.
482 471 .RE
483 472
484 473 .sp
485 474 .ne 2
486 475 .na
487 476 \fBglobal: \fBzonepath\fR\fR
488 477 .ad
489 478 .sp .6
490 479 .RS 4n
491 480 Path to zone's file system.
492 481 .RE
493 482
494 483 .sp
495 484 .ne 2
496 485 .na
497 486 \fBglobal: \fBautoboot\fR\fR
498 487 .ad
499 488 .sp .6
500 489 .RS 4n
501 490 Boolean indicating that a zone should be booted automatically at system boot.
502 491 Note that if the zones service is disabled, the zone will not autoboot,
503 492 regardless of the setting of this property. You enable the zones service with a
504 493 \fBsvcadm\fR command, such as:
505 494 .sp
506 495 .in +2
507 496 .nf
508 497 # \fBsvcadm enable svc:/system/zones:default\fR
509 498 .fi
510 499 .in -2
511 500 .sp
512 501
513 502 Replace \fBenable\fR with \fBdisable\fR to disable the zones service. See
514 503 \fBsvcadm\fR(1M).
515 504 .RE
516 505
517 506 .sp
518 507 .ne 2
519 508 .na
520 509 \fBglobal: \fBbootargs\fR\fR
521 510 .ad
522 511 .sp .6
523 512 .RS 4n
524 513 Arguments (options) to be passed to the zone bootup, unless options are
525 514 supplied to the "\fBzoneadm boot\fR" command, in which case those take
526 515 precedence. The valid arguments are described in \fBzoneadm\fR(1M).
527 516 .RE
528 517
529 518 .sp
530 519 .ne 2
531 520 .na
532 521 \fBglobal: \fBpool\fR\fR
533 522 .ad
534 523 .sp .6
535 524 .RS 4n
536 525 Name of the resource pool that this zone must be bound to when booted. This
537 526 property is incompatible with the \fBdedicated-cpu\fR resource.
538 527 .RE
539 528
540 529 .sp
541 530 .ne 2
542 531 .na
543 532 \fBglobal: \fBlimitpriv\fR\fR
544 533 .ad
545 534 .sp .6
546 535 .RS 4n
547 536 The maximum set of privileges any process in this zone can obtain. The property
548 537 should consist of a comma-separated privilege set specification as described in
549 538 \fBpriv_str_to_set\fR(3C). Privileges can be excluded from the resulting set by
550 539 preceding their names with a dash (-) or an exclamation point (!). The special
551 540 privilege string "zone" is not supported in this context. If the special string
552 541 "default" occurs as the first token in the property, it expands into a safe set
553 542 of privileges that preserve the resource and security isolation described in
554 543 \fBzones\fR(5). A missing or empty property is equivalent to this same set of
555 544 safe privileges.
556 545 .sp
557 546 The system administrator must take extreme care when configuring privileges for
558 547 a zone. Some privileges cannot be excluded through this mechanism as they are
559 548 required in order to boot a zone. In addition, there are certain privileges
560 549 which cannot be given to a zone as doing so would allow processes inside a zone
561 550 to unduly affect processes in other zones. \fBzoneadm\fR(1M) indicates when an
562 551 invalid privilege has been added or removed from a zone's privilege set when an
563 552 attempt is made to either "boot" or "ready" the zone.
564 553 .sp
565 554 See \fBprivileges\fR(5) for a description of privileges. The command "\fBppriv
566 555 -l\fR" (see \fBppriv\fR(1)) produces a list of all Solaris privileges. You can
567 556 specify privileges as they are displayed by \fBppriv\fR. In
568 557 \fBprivileges\fR(5), privileges are listed in the form
569 558 PRIV_\fIprivilege_name\fR. For example, the privilege \fIsys_time\fR, as you
570 559 would specify it in this property, is listed in \fBprivileges\fR(5) as
571 560 \fBPRIV_SYS_TIME\fR.
572 561 .RE
573 562
574 563 .sp
575 564 .ne 2
576 565 .na
577 566 \fBglobal: \fBbrand\fR\fR
578 567 .ad
579 568 .sp .6
580 569 .RS 4n
581 570 The zone's brand type.
582 571 .RE
583 572
584 573 .sp
585 574 .ne 2
586 575 .na
587 576 \fBglobal: \fBip-type\fR\fR
588 577 .ad
589 578 .sp .6
590 579 .RS 4n
591 580 A zone can either share the IP instance with the global zone, which is the
592 581 default, or have its own exclusive instance of IP.
593 582 .sp
594 583 This property takes the values \fBshared\fR and \fBexclusive\fR.
595 584 .RE
596 585
597 586 .sp
598 587 .ne 2
599 588 .na
600 589 \fBglobal: \fBhostid\fR\fR
601 590 .ad
602 591 .sp .6
603 592 .RS 4n
604 593 A zone can emulate a 32-bit host identifier to ease system consolidation. A
605 594 zone's \fBhostid\fR property is empty by default, meaning that the zone does
606 595 not emulate a host identifier. Zone host identifiers must be hexadecimal values
607 596 between 0 and FFFFFFFE. A \fB0x\fR or \fB0X\fR prefix is optional. Both
608 597 uppercase and lowercase hexadecimal digits are acceptable.
609 598 .RE
610 599
611 600 .sp
612 601 .ne 2
613 602 .na
614 603 \fB\fBfs\fR: dir, special, raw, type, options\fR
|
↓ open down ↓ |
242 lines elided |
↑ open up ↑ |
615 604 .ad
616 605 .sp .6
617 606 .RS 4n
618 607 Values needed to determine how, where, and so forth to mount file systems. See
619 608 \fBmount\fR(1M), \fBmount\fR(2), \fBfsck\fR(1M), and \fBvfstab\fR(4).
620 609 .RE
621 610
622 611 .sp
623 612 .ne 2
624 613 .na
625 -\fB\fBinherit-pkg-dir\fR: dir\fR
614 +\fB\fBnet\fR: address, physical, defrouter\fR
626 615 .ad
627 616 .sp .6
628 617 .RS 4n
629 -The directory path.
630 -.RE
631 -
632 -.sp
633 -.ne 2
634 -.na
635 -\fB\fBnet\fR: address, allowed-address, defrouter, global-nic, mac-addr, physical, property, vlan-id\fR
636 -.ad
637 -.sp .6
638 -.RS 4n
639 618 The network address and physical interface name of the network interface. The
640 619 network address is one of:
641 620 .RS +4
642 621 .TP
643 622 .ie t \(bu
644 623 .el o
645 624 a valid IPv4 address, optionally followed by "\fB/\fR" and a prefix length;
646 625 .RE
647 626 .RS +4
648 627 .TP
649 628 .ie t \(bu
650 629 .el o
651 630 a valid IPv6 address, which must be followed by "\fB/\fR" and a prefix length;
652 631 .RE
653 632 .RS +4
654 633 .TP
655 634 .ie t \(bu
656 635 .el o
657 636 a host name which resolves to an IPv4 address.
658 637 .RE
659 638 Note that host names that resolve to IPv6 addresses are not supported.
660 639 .sp
661 640 The physical interface name is the network interface name.
662 641 .sp
663 642 The default router is specified similarly to the network address except that it
|
↓ open down ↓ |
15 lines elided |
↑ open up ↑ |
664 643 must not be followed by a \fB/\fR (slash) and a network prefix length.
665 644 .sp
666 645 A zone can be configured to be either exclusive-IP or shared-IP. For a
667 646 shared-IP zone, you must set both the physical and address properties; setting
668 647 the default router is optional. The interface specified in the physical
669 648 property must be plumbed in the global zone prior to booting the non-global
670 649 zone. However, if the interface is not used by the global zone, it should be
671 650 configured \fBdown\fR in the global zone, and the default router for the
672 651 interface should be specified here.
673 652 .sp
674 -The global-nic is used for exclusive stack zones which will use a VNIC on-demand. When the zone boots, a VNIC named using the physical property will be created on the global NIC. If provided, the mac-addr and vlan-id will be set on this VNIC.
675 -.sp
676 -The \fBproperty\fR setting is a resource which can be used to set arbitrary name/value pairs on the network. These name/value pairs are made available to the zone's brand, which can use them as needed to set up the network interface.
677 -.sp
678 653 For an exclusive-IP zone, the physical property must be set and the address and
679 654 default router properties cannot be set.
680 655 .RE
681 656
682 657 .sp
683 658 .ne 2
684 659 .na
685 660 \fB\fBdevice\fR: match\fR
686 661 .ad
687 662 .sp .6
688 663 .RS 4n
689 664 Device name to match.
690 665 .RE
691 666
692 667 .sp
693 668 .ne 2
694 669 .na
695 670 \fB\fBrctl\fR: name, value\fR
696 671 .ad
697 672 .sp .6
698 673 .RS 4n
699 674 The name and \fIpriv\fR/\fIlimit\fR/\fIaction\fR triple of a resource control.
700 675 See \fBprctl\fR(1) and \fBrctladm\fR(1M). The preferred way to set rctl values
701 676 is to use the global property name associated with a specific rctl.
702 677 .RE
703 678
704 679 .sp
705 680 .ne 2
706 681 .na
707 682 \fB\fBattr\fR: name, type, value\fR
708 683 .ad
709 684 .sp .6
710 685 .RS 4n
711 686 The name, type and value of a generic attribute. The \fBtype\fR must be one of
712 687 \fBint\fR, \fBuint\fR, \fBboolean\fR or \fBstring\fR, and the value must be of
713 688 that type. \fBuint\fR means unsigned , that is, a non-negative integer.
714 689 .RE
715 690
716 691 .sp
717 692 .ne 2
718 693 .na
719 694 \fB\fBdataset\fR: name\fR
720 695 .ad
721 696 .sp .6
722 697 .RS 4n
723 698 The name of a \fBZFS\fR dataset to be accessed from within the zone. See
724 699 \fBzfs\fR(1M).
725 700 .RE
726 701
727 702 .sp
728 703 .ne 2
729 704 .na
730 705 \fBglobal: \fBcpu-shares\fR\fR
731 706 .ad
732 707 .sp .6
733 708 .RS 4n
734 709 The number of Fair Share Scheduler (FSS) shares to allocate to this zone. This
735 710 property is incompatible with the \fBdedicated-cpu\fR resource. This property
736 711 is the preferred way to set the \fBzone.cpu-shares\fR rctl.
737 712 .RE
738 713
739 714 .sp
740 715 .ne 2
741 716 .na
742 717 \fBglobal: \fBmax-lwps\fR\fR
743 718 .ad
744 719 .sp .6
745 720 .RS 4n
746 721 The maximum number of LWPs simultaneously available to this zone. This property
747 722 is the preferred way to set the \fBzone.max-lwps\fR rctl.
748 723 .RE
749 724
750 725 .sp
751 726 .ne 2
752 727 .na
753 728 \fBglobal: \fBmax-msg-ids\fR\fR
754 729 .ad
755 730 .sp .6
756 731 .RS 4n
757 732 The maximum number of message queue IDs allowed for this zone. This property is
758 733 the preferred way to set the \fBzone.max-msg-ids\fR rctl.
759 734 .RE
760 735
761 736 .sp
762 737 .ne 2
763 738 .na
764 739 \fBglobal: \fBmax-sem-ids\fR\fR
765 740 .ad
766 741 .sp .6
767 742 .RS 4n
768 743 The maximum number of semaphore IDs allowed for this zone. This property is the
769 744 preferred way to set the \fBzone.max-sem-ids\fR rctl.
770 745 .RE
771 746
772 747 .sp
773 748 .ne 2
774 749 .na
775 750 \fBglobal: \fBmax-shm-ids\fR\fR
776 751 .ad
777 752 .sp .6
778 753 .RS 4n
779 754 The maximum number of shared memory IDs allowed for this zone. This property is
780 755 the preferred way to set the \fBzone.max-shm-ids\fR rctl.
781 756 .RE
782 757
783 758 .sp
784 759 .ne 2
785 760 .na
786 761 \fBglobal: \fBmax-shm-memory\fR\fR
787 762 .ad
788 763 .sp .6
789 764 .RS 4n
790 765 The maximum amount of shared memory allowed for this zone. This property is the
791 766 preferred way to set the \fBzone.max-shm-memory\fR rctl. A scale (K, M, G, T)
792 767 can be applied to the value for this number (for example, 1M is one megabyte).
793 768 .RE
794 769
795 770 .sp
796 771 .ne 2
797 772 .na
798 773 \fBglobal: \fBscheduling-class\fR\fR
799 774 .ad
800 775 .sp .6
801 776 .RS 4n
802 777 Specifies the scheduling class used for processes running in a zone. When this
803 778 property is not specified, the scheduling class is established as follows:
804 779 .RS +4
805 780 .TP
806 781 .ie t \(bu
807 782 .el o
808 783 If the \fBcpu-shares\fR property or equivalent rctl is set, the scheduling
809 784 class \fBFSS\fR is used.
810 785 .RE
811 786 .RS +4
812 787 .TP
813 788 .ie t \(bu
814 789 .el o
815 790 If neither \fBcpu-shares\fR nor the equivalent rctl is set and the zone's pool
816 791 property references a pool that has a default scheduling class, that class is
817 792 used.
818 793 .RE
819 794 .RS +4
820 795 .TP
821 796 .ie t \(bu
822 797 .el o
823 798 Under any other conditions, the system default scheduling class is used.
824 799 .RE
825 800 .sp
826 801 If the \fBFX\fR scheduling class is specified, then the optional
827 802 \fBfixed-hi-pri\fR attribute can be set to \fBtrue\fR. This causes all of the
828 803 processes in the zone to run at the highest \fBFX\fR priority. By default
829 804 processes under \fBFX\fR run at the lowest priority. See \fBpriocntl\fR(2)
830 805 for details on each scheduling class.
831 806 .RE
832 807
833 808
834 809 .sp
835 810 .ne 2
836 811 .na
837 812 \fB\fBdedicated-cpu\fR: ncpus, importance\fR
838 813 .ad
839 814 .sp .6
840 815 .RS 4n
841 816 The number of CPUs that should be assigned for this zone's exclusive use. The
842 817 zone will create a pool and processor set when it boots. See \fBpooladm\fR(1M)
843 818 and \fBpoolcfg\fR(1M) for more information on resource pools. The \fBncpu\fR
844 819 property can specify a single value or a range (for example, 1-4) of
845 820 processors. The \fBimportance\fR property is optional; if set, it will specify
846 821 the \fBpset.importance\fR value for use by \fBpoold\fR(1M). If this resource is
847 822 used, there must be enough free processors to allocate to this zone when it
848 823 boots or the zone will not boot. The processors assigned to this zone will not
849 824 be available for the use of the global zone or other zones. This resource is
850 825 incompatible with both the \fBpool\fR and \fBcpu-shares\fR properties. Only a
851 826 single instance of this resource can be added to the zone.
852 827 .RE
853 828
854 829 .sp
855 830 .ne 2
856 831 .na
857 832 \fB\fBcapped-memory\fR: physical, swap, locked\fR
858 833 .ad
859 834 .sp .6
860 835 .RS 4n
861 836 The caps on the memory that can be used by this zone. A scale (K, M, G, T) can
862 837 be applied to the value for each of these numbers (for example, 1M is one
863 838 megabyte). Each of these properties is optional but at least one property must
864 839 be set when adding this resource. Only a single instance of this resource can
865 840 be added to the zone. The \fBphysical\fR property sets the \fBmax-rss\fR for
866 841 this zone. This will be enforced by \fBrcapd\fR(1M) running in the global zone.
867 842 The \fBswap\fR property is the preferred way to set the \fBzone.max-swap\fR
868 843 rctl. The \fBlocked\fR property is the preferred way to set the
869 844 \fBzone.max-locked-memory\fR rctl.
870 845 .RE
871 846
872 847 .sp
873 848 .ne 2
874 849 .na
875 850 \fB\fBcapped-cpu\fR: ncpus\fR
876 851 .ad
877 852 .sp .6
878 853 .RS 4n
879 854 Sets a limit on the amount of CPU time that can be used by a zone. The unit
880 855 used translates to the percentage of a single CPU that can be used by all user
881 856 threads in a zone, expressed as a fraction (for example, \fB\&.75\fR) or a
882 857 mixed number (whole number and fraction, for example, \fB1.25\fR). An
883 858 \fBncpu\fR value of \fB1\fR means 100% of a CPU, a value of \fB1.25\fR means
884 859 125%, \fB\&.75\fR mean 75%, and so forth. When projects within a capped zone
885 860 have their own caps, the minimum value takes precedence.
886 861 .sp
887 862 The \fBcapped-cpu\fR property is an alias for \fBzone.cpu-cap\fR resource
888 863 control and is related to the \fBzone.cpu-cap\fR resource control. See
889 864 \fBresource_controls\fR(5).
890 865 .RE
891 866
892 867 .sp
893 868 .ne 2
894 869 .na
895 870 \fBglobal: \fBfs-allowed\fR\fR
896 871 .ad
897 872 .sp .6
898 873 .RS 4n
899 874 A comma-separated list of additional filesystems that may be mounted within
900 875 the zone; for example "ufs,pcfs". By default, only hsfs(7fs) and network
901 876 filesystems can be mounted. If the first entry in the list is "-" then
902 877 that disables all of the default filesystems. If any filesystems are listed
903 878 after "-" then only those filesystems can be mounted.
|
↓ open down ↓ |
216 lines elided |
↑ open up ↑ |
904 879
905 880 This property does not apply to filesystems mounted into the zone via "add fs"
906 881 or "add dataset".
907 882
908 883 WARNING: allowing filesystem mounts other than the default may allow the zone
909 884 administrator to compromise the system with a malicious filesystem image, and
910 885 is not supported.
911 886 .RE
912 887
913 888 .sp
914 -.ne 2
915 -.na
916 -\fBglobal: \fBzfs-io-priority\fR\fR
917 -.ad
918 -.sp .6
919 -.RS 4n
920 -Specifies a priority for this zone's ZFS I/O. The priority is used by the ZFS I/O scheduler as in input to determine how to schedule I/O across zones. By default all zones have a priority of 1. The value can be increased for zones whose I/O is more critical. This property is the preferred way to set the \fBzone.zfs-io-priority\fR rctl.
921 -.RE
922 -
923 -.sp
924 889 .LP
925 890 The following table summarizes resources, property-names, and types:
926 891 .sp
927 892 .in +2
928 893 .nf
929 894 resource property-name type
930 895 (global) zonename simple
931 896 (global) zonepath simple
932 897 (global) autoboot simple
933 898 (global) bootargs simple
934 899 (global) pool simple
935 900 (global) limitpriv simple
|
↓ open down ↓ |
2 lines elided |
↑ open up ↑ |
936 901 (global) brand simple
937 902 (global) ip-type simple
938 903 (global) hostid simple
939 904 (global) cpu-shares simple
940 905 (global) max-lwps simple
941 906 (global) max-msg-ids simple
942 907 (global) max-sem-ids simple
943 908 (global) max-shm-ids simple
944 909 (global) max-shm-memory simple
945 910 (global) scheduling-class simple
946 -(global) zfs-io-priority simple
947 911 fs dir simple
948 912 special simple
949 913 raw simple
950 914 type simple
951 915 options list of simple
952 916 net address simple
953 - allowed-address simple
954 - defrouter simple
955 - global-nic simple
956 - mac-addr simple
957 917 physical simple
958 - property list of complex
959 - name simple
960 - value simple
961 - vlan-id simple
962 918 device match simple
963 919 rctl name simple
964 920 value list of complex
965 921 attr name simple
966 922 type simple
967 923 value simple
968 924 dataset name simple
969 925 dedicated-cpu ncpus simple or range
970 926 importance simple
971 927
972 928 capped-memory physical simple with scale
973 929 swap simple with scale
974 930 locked simple with scale
975 931
976 932 capped-cpu ncpus simple
977 933 .fi
978 934 .in -2
979 935 .sp
980 936
981 937 .sp
982 938 .LP
983 939 To further specify things, the breakdown of the complex property "value" of the
984 940 "rctl" resource type, it consists of three name/value pairs, the names being
985 941 "priv", "limit" and "action", each of which takes a simple value. The "name"
986 942 property of an "attr" resource is syntactically restricted in a fashion similar
987 943 but not identical to zone names: it must begin with an alphanumeric, and can
988 944 contain alphanumerics plus the hyphen (\fB-\fR), underscore (\fB_\fR), and dot
989 945 (\fB\&.\fR) characters. Attribute names beginning with "zone" are reserved for
990 946 use by the system. Finally, the "autoboot" global property must have a value of
991 947 "true" or "false".
992 948 .SS "Using Kernel Statistics to Monitor CPU Caps"
993 949 .LP
994 950 Using the kernel statistics (\fBkstat\fR(3KSTAT)) module \fBcaps\fR, the system
995 951 maintains information for all capped projects and zones. You can access this
996 952 information by reading kernel statistics (\fBkstat\fR(3KSTAT)), specifying
997 953 \fBcaps\fR as the \fBkstat\fR module name. The following command displays
998 954 kernel statistics for all active CPU caps:
999 955 .sp
1000 956 .in +2
1001 957 .nf
1002 958 # \fBkstat caps::'/cpucaps/'\fR
1003 959 .fi
1004 960 .in -2
1005 961 .sp
1006 962
1007 963 .sp
1008 964 .LP
1009 965 A \fBkstat\fR(1M) command running in a zone displays only CPU caps relevant for
1010 966 that zone and for projects in that zone. See \fBEXAMPLES\fR.
1011 967 .sp
1012 968 .LP
1013 969 The following are cap-related arguments for use with \fBkstat\fR(1M):
1014 970 .sp
1015 971 .ne 2
1016 972 .na
1017 973 \fB\fBcaps\fR\fR
1018 974 .ad
1019 975 .sp .6
1020 976 .RS 4n
1021 977 The \fBkstat\fR module.
1022 978 .RE
1023 979
1024 980 .sp
1025 981 .ne 2
1026 982 .na
1027 983 \fB\fBproject_caps\fR or \fBzone_caps\fR\fR
1028 984 .ad
1029 985 .sp .6
1030 986 .RS 4n
1031 987 \fBkstat\fR class, for use with the \fBkstat\fR \fB-c\fR option.
1032 988 .RE
1033 989
1034 990 .sp
1035 991 .ne 2
1036 992 .na
1037 993 \fB\fBcpucaps_project_\fR\fIid\fR or \fBcpucaps_zone_\fR\fIid\fR\fR
1038 994 .ad
1039 995 .sp .6
1040 996 .RS 4n
1041 997 \fBkstat\fR name, for use with the \fBkstat\fR \fB-n\fR option. \fIid\fR is the
1042 998 project or zone identifier.
1043 999 .RE
1044 1000
1045 1001 .sp
1046 1002 .LP
1047 1003 The following fields are displayed in response to a \fBkstat\fR(1M) command
1048 1004 requesting statistics for all CPU caps.
1049 1005 .sp
1050 1006 .ne 2
1051 1007 .na
1052 1008 \fB\fBmodule\fR\fR
1053 1009 .ad
1054 1010 .sp .6
1055 1011 .RS 4n
1056 1012 In this usage of \fBkstat\fR, this field will have the value \fBcaps\fR.
1057 1013 .RE
1058 1014
1059 1015 .sp
1060 1016 .ne 2
1061 1017 .na
1062 1018 \fB\fBname\fR\fR
1063 1019 .ad
1064 1020 .sp .6
1065 1021 .RS 4n
1066 1022 As described above, \fBcpucaps_project_\fR\fIid\fR or
1067 1023 \fBcpucaps_zone_\fR\fIid\fR
1068 1024 .RE
1069 1025
1070 1026 .sp
1071 1027 .ne 2
1072 1028 .na
1073 1029 \fB\fBabove_sec\fR\fR
1074 1030 .ad
1075 1031 .sp .6
1076 1032 .RS 4n
1077 1033 Total time, in seconds, spent above the cap.
1078 1034 .RE
1079 1035
1080 1036 .sp
1081 1037 .ne 2
1082 1038 .na
1083 1039 \fB\fBbelow_sec\fR\fR
1084 1040 .ad
1085 1041 .sp .6
1086 1042 .RS 4n
1087 1043 Total time, in seconds, spent below the cap.
1088 1044 .RE
1089 1045
1090 1046 .sp
1091 1047 .ne 2
1092 1048 .na
1093 1049 \fB\fBmaxusage\fR\fR
1094 1050 .ad
1095 1051 .sp .6
1096 1052 .RS 4n
1097 1053 Maximum observed CPU usage.
1098 1054 .RE
1099 1055
1100 1056 .sp
1101 1057 .ne 2
1102 1058 .na
1103 1059 \fB\fBnwait\fR\fR
1104 1060 .ad
1105 1061 .sp .6
1106 1062 .RS 4n
1107 1063 Number of threads on cap wait queue.
1108 1064 .RE
1109 1065
1110 1066 .sp
1111 1067 .ne 2
1112 1068 .na
1113 1069 \fB\fBusage\fR\fR
1114 1070 .ad
1115 1071 .sp .6
1116 1072 .RS 4n
1117 1073 Current aggregated CPU usage for all threads belonging to a capped project or
1118 1074 zone, in terms of a percentage of a single CPU.
1119 1075 .RE
1120 1076
1121 1077 .sp
1122 1078 .ne 2
1123 1079 .na
1124 1080 \fB\fBvalue\fR\fR
1125 1081 .ad
1126 1082 .sp .6
1127 1083 .RS 4n
1128 1084 The cap value, in terms of a percentage of a single CPU.
1129 1085 .RE
1130 1086
1131 1087 .sp
1132 1088 .ne 2
1133 1089 .na
1134 1090 \fB\fBzonename\fR\fR
1135 1091 .ad
1136 1092 .sp .6
1137 1093 .RS 4n
1138 1094 Name of the zone for which statistics are displayed.
1139 1095 .RE
1140 1096
1141 1097 .sp
1142 1098 .LP
1143 1099 See \fBEXAMPLES\fR for sample output from a \fBkstat\fR command.
1144 1100 .SH OPTIONS
1145 1101 .LP
1146 1102 The following options are supported:
1147 1103 .sp
1148 1104 .ne 2
1149 1105 .na
1150 1106 \fB\fB-f\fR \fIcommand_file\fR\fR
1151 1107 .ad
1152 1108 .sp .6
1153 1109 .RS 4n
1154 1110 Specify the name of \fBzonecfg\fR command file. \fIcommand_file\fR is a text
1155 1111 file of \fBzonecfg\fR subcommands, one per line.
1156 1112 .RE
1157 1113
1158 1114 .sp
1159 1115 .ne 2
1160 1116 .na
1161 1117 \fB\fB-z\fR \fIzonename\fR\fR
|
↓ open down ↓ |
190 lines elided |
↑ open up ↑ |
1162 1118 .ad
1163 1119 .sp .6
1164 1120 .RS 4n
1165 1121 Specify the name of a zone. Zone names are case sensitive. Zone names must
1166 1122 begin with an alphanumeric character and can contain alphanumeric characters,
1167 1123 the underscore (\fB_\fR) the hyphen (\fB-\fR), and the dot (\fB\&.\fR). The
1168 1124 name \fBglobal\fR and all names beginning with \fBSUNW\fR are reserved and
1169 1125 cannot be used.
1170 1126 .RE
1171 1127
1172 -.sp
1173 -.ne 2
1174 -.na
1175 -\fB\fB-u\fR \fIuuid\fR\fR
1176 -.ad
1177 -.sp .6
1178 -.RS 4n
1179 -Specify the uuid of a zone instead of the Zone name.
1180 -.RE
1181 -
1182 1128 .SH SUBCOMMANDS
1183 1129 .LP
1184 1130 You can use the \fBadd\fR and \fBselect\fR subcommands to select a specific
1185 1131 resource, at which point the scope changes to that resource. The \fBend\fR and
1186 1132 \fBcancel\fR subcommands are used to complete the resource specification, at
1187 1133 which time the scope is reverted back to global. Certain subcommands, such as
1188 1134 \fBadd\fR, \fBremove\fR and \fBset\fR, have different semantics in each scope.
1189 1135 .sp
1190 1136 .LP
1191 1137 \fBzonecfg\fR supports a semicolon-separated list of subcommands. For example:
1192 1138 .sp
1193 1139 .in +2
1194 1140 .nf
1195 1141 # \fBzonecfg -z myzone "add net; set physical=myvnic; end"\fR
1196 1142 .fi
1197 1143 .in -2
1198 1144 .sp
1199 1145
1200 1146 .sp
1201 1147 .LP
1202 1148 Subcommands which can result in destructive actions or loss of work have an
1203 1149 \fB-F\fR option to force the action. If input is from a terminal device, the
1204 1150 user is prompted when appropriate if such a command is given without the
1205 1151 \fB-F\fR option otherwise, if such a command is given without the \fB-F\fR
1206 1152 option, the action is disallowed, with a diagnostic message written to standard
1207 1153 error.
1208 1154 .sp
1209 1155 .LP
1210 1156 The following subcommands are supported:
1211 1157 .sp
1212 1158 .ne 2
1213 1159 .na
1214 1160 \fB\fBadd\fR \fIresource-type\fR (global scope)\fR
1215 1161 .ad
1216 1162 .br
1217 1163 .na
1218 1164 \fB\fBadd\fR \fIproperty-name property-value\fR (resource scope)\fR
1219 1165 .ad
1220 1166 .sp .6
1221 1167 .RS 4n
1222 1168 In the global scope, begin the specification for a given resource type. The
1223 1169 scope is changed to that resource type.
1224 1170 .sp
1225 1171 In the resource scope, add a property of the given name with the given value.
1226 1172 The syntax for property values varies with different property types. In
1227 1173 general, it is a simple value or a list of simple values enclosed in square
1228 1174 brackets, separated by commas (\fB[foo,bar,baz]\fR). See \fBPROPERTIES\fR.
1229 1175 .RE
1230 1176
1231 1177 .sp
1232 1178 .ne 2
1233 1179 .na
1234 1180 \fB\fBcancel\fR\fR
1235 1181 .ad
1236 1182 .sp .6
1237 1183 .RS 4n
1238 1184 End the resource specification and reset scope to global. Abandons any
1239 1185 partially specified resources. \fBcancel\fR is only applicable in the resource
1240 1186 scope.
1241 1187 .RE
1242 1188
1243 1189 .sp
1244 1190 .ne 2
1245 1191 .na
1246 1192 \fB\fBclear\fR \fIproperty-name\fR\fR
1247 1193 .ad
1248 1194 .sp .6
1249 1195 .RS 4n
1250 1196 Clear the value for the property.
1251 1197 .RE
1252 1198
1253 1199 .sp
1254 1200 .ne 2
1255 1201 .na
1256 1202 \fB\fBcommit\fR\fR
1257 1203 .ad
1258 1204 .sp .6
1259 1205 .RS 4n
1260 1206 Commit the current configuration from memory to stable storage. The
|
↓ open down ↓ |
69 lines elided |
↑ open up ↑ |
1261 1207 configuration must be committed to be used by \fBzoneadm\fR. Until the
1262 1208 in-memory configuration is committed, you can remove changes with the
1263 1209 \fBrevert\fR subcommand. The \fBcommit\fR operation is attempted automatically
1264 1210 upon completion of a \fBzonecfg\fR session. Since a configuration must be
1265 1211 correct to be committed, this operation automatically does a verify.
1266 1212 .RE
1267 1213
1268 1214 .sp
1269 1215 .ne 2
1270 1216 .na
1271 -\fB\fBcreate [\fR\fB-F\fR\fB] [\fR \fB-a\fR \fIpath\fR |\fB-b\fR \fB|\fR \fB-t\fR \fItemplate\fR\fB] [\fR\fB-X\fR\fB]\fR\fR
1217 +\fB\fBcreate [\fR\fB-F\fR\fB] [\fR \fB-a\fR \fIpath\fR |\fB-b\fR \fB|\fR
1218 +\fB-t\fR \fItemplate\fR\fB]\fR\fR
1272 1219 .ad
1273 1220 .sp .6
1274 1221 .RS 4n
1275 1222 Create an in-memory configuration for the specified zone. Use \fBcreate\fR to
1276 1223 begin to configure a new zone. See \fBcommit\fR for saving this to stable
1277 1224 storage.
1278 1225 .sp
1279 1226 If you are overwriting an existing configuration, specify the \fB-F\fR option
1280 1227 to force the action. Specify the \fB-t\fR \fItemplate\fR option to create a
1281 1228 configuration identical to \fItemplate\fR, where \fItemplate\fR is the name of
1282 1229 a configured zone.
|
↓ open down ↓ |
1 lines elided |
↑ open up ↑ |
1283 1230 .sp
1284 1231 Use the \fB-a\fR \fIpath\fR option to facilitate configuring a detached zone on
1285 1232 a new host. The \fIpath\fR parameter is the zonepath location of a detached
1286 1233 zone that has been moved on to this new host. Once the detached zone is
1287 1234 configured, it should be installed using the "\fBzoneadm attach\fR" command
1288 1235 (see \fBzoneadm\fR(1M)). All validation of the new zone happens during the
1289 1236 \fBattach\fR process, not during zone configuration.
1290 1237 .sp
1291 1238 Use the \fB-b\fR option to create a blank configuration. Without arguments,
1292 1239 \fBcreate\fR applies the Sun default settings.
1293 -.sp
1294 -Use the \fB-X\fR option to facilitate creating a zone whose XML definition already exists on the host. The zone will be atomically added to the zone index file.
1295 1240 .RE
1296 1241
1297 1242 .sp
1298 1243 .ne 2
1299 1244 .na
1300 1245 \fB\fBdelete [\fR\fB-F\fR\fB]\fR\fR
1301 1246 .ad
1302 1247 .sp .6
1303 1248 .RS 4n
1304 1249 Delete the specified configuration from memory and stable storage. This action
1305 1250 is instantaneous, no commit is necessary. A deleted configuration cannot be
1306 1251 reverted.
1307 1252 .sp
1308 1253 Specify the \fB-F\fR option to force the action.
1309 1254 .RE
1310 1255
1311 1256 .sp
1312 1257 .ne 2
1313 1258 .na
1314 1259 \fB\fBend\fR\fR
1315 1260 .ad
1316 1261 .sp .6
1317 1262 .RS 4n
1318 1263 End the resource specification. This subcommand is only applicable in the
1319 1264 resource scope. \fBzonecfg\fR checks to make sure the current resource is
1320 1265 completely specified. If so, it is added to the in-memory configuration (see
1321 1266 \fBcommit\fR for saving this to stable storage) and the scope reverts to
1322 1267 global. If the specification is incomplete, it issues an appropriate error
1323 1268 message.
1324 1269 .RE
1325 1270
1326 1271 .sp
1327 1272 .ne 2
1328 1273 .na
1329 1274 \fB\fBexport [\fR\fB-f\fR \fIoutput-file\fR\fB]\fR\fR
1330 1275 .ad
1331 1276 .sp .6
1332 1277 .RS 4n
1333 1278 Print configuration to standard output. Use the \fB-f\fR option to print the
1334 1279 configuration to \fIoutput-file\fR. This option produces output in a form
1335 1280 suitable for use in a command file.
1336 1281 .RE
1337 1282
1338 1283 .sp
1339 1284 .ne 2
1340 1285 .na
1341 1286 \fB\fBhelp [usage] [\fIsubcommand\fR] [syntax] [\fR\fIcommand-name\fR\fB]\fR\fR
1342 1287 .ad
1343 1288 .sp .6
1344 1289 .RS 4n
1345 1290 Print general help or help about given topic.
1346 1291 .RE
1347 1292
1348 1293 .sp
1349 1294 .ne 2
1350 1295 .na
1351 1296 \fB\fBinfo zonename | zonepath | autoboot | brand | pool | limitpriv\fR\fR
1352 1297 .ad
1353 1298 .br
1354 1299 .na
1355 1300 \fB\fBinfo [\fR\fIresource-type\fR
1356 1301 \fB[\fR\fIproperty-name\fR\fB=\fR\fIproperty-value\fR\fB]*]\fR\fR
1357 1302 .ad
1358 1303 .sp .6
1359 1304 .RS 4n
1360 1305 Display information about the current configuration. If \fIresource-type\fR is
|
↓ open down ↓ |
56 lines elided |
↑ open up ↑ |
1361 1306 specified, displays only information about resources of the relevant type. If
1362 1307 any \fIproperty-name\fR value pairs are specified, displays only information
1363 1308 about resources meeting the given criteria. In the resource scope, any
1364 1309 arguments are ignored, and \fBinfo\fR displays information about the resource
1365 1310 which is currently being added or modified.
1366 1311 .RE
1367 1312
1368 1313 .sp
1369 1314 .ne 2
1370 1315 .na
1371 -\fB\fBremove\fR [\fR\fB-F\fR\fB] \fIresource-type\fR\fB [\fR\fIproperty-name\fR\fB=\fR\fIproperty-value\fR\fB]* \fR(global scope)\fR
1372 -.br
1373 -\fB\fBremove\fR \fR\fIproperty-name\fR\fB \fR\fIproperty-value\fR\fB \fR(resource scope)\fR
1316 +\fB\fBremove\fR \fIresource-type\fR\fB{\fR\fIproperty-name\fR\fB=\fR\fIproperty
1317 +-value\fR\fB}\fR(global scope)\fR
1374 1318 .ad
1375 1319 .sp .6
1376 1320 .RS 4n
1377 1321 In the global scope, removes the specified resource. The \fB[]\fR syntax means
1378 -0 or more property name-value pairs. If you want to only remove a
1322 +0 or more of whatever is inside the square braces. If you want only to remove a
1379 1323 single instance of the resource, you must specify enough property name-value
1380 1324 pairs for the resource to be uniquely identified. If no property name-value
1381 1325 pairs are specified, all instances will be removed. If there is more than one
1382 -pair specified, a confirmation is required, unless you use the \fB-F\fR
1383 -option. Likewise, the \fB-F\fR option can be used to remove a resource that
1384 -does not exist (that is, no error will occur). In the resource scope, remove
1385 -the specified name-value pair.
1326 +pair is specified, a confirmation is required, unless you use the \fB-F\fR
1327 +option.
1386 1328 .RE
1387 1329
1388 1330 .sp
1389 1331 .ne 2
1390 1332 .na
1391 1333 \fB\fBselect\fR \fIresource-type\fR
1392 1334 \fB{\fR\fIproperty-name\fR\fB=\fR\fIproperty-value\fR\fB}\fR\fR
1393 1335 .ad
1394 1336 .sp .6
1395 1337 .RS 4n
1396 1338 Select the resource of the given type which matches the given
1397 1339 \fIproperty-name\fR \fIproperty-value\fR pair criteria, for modification. This
1398 1340 subcommand is applicable only in the global scope. The scope is changed to that
1399 1341 resource type. The \fB{}\fR syntax means 1 or more of whatever is inside the
1400 1342 curly braces. You must specify enough \fIproperty -name property-value\fR pairs
1401 1343 for the resource to be uniquely identified.
1402 1344 .RE
1403 1345
1404 1346 .sp
1405 1347 .ne 2
1406 1348 .na
1407 1349 \fB\fBset\fR \fIproperty-name\fR\fB=\fR\fIproperty\fR\fB-\fR\fIvalue\fR\fR
1408 1350 .ad
1409 1351 .sp .6
1410 1352 .RS 4n
1411 1353 Set a given property name to the given value. Some properties (for example,
1412 1354 \fBzonename\fR and \fBzonepath\fR) are global while others are
1413 1355 resource-specific. This subcommand is applicable in both the global and
1414 1356 resource scopes.
1415 1357 .RE
1416 1358
1417 1359 .sp
1418 1360 .ne 2
1419 1361 .na
1420 1362 \fB\fBverify\fR\fR
1421 1363 .ad
1422 1364 .sp .6
1423 1365 .RS 4n
1424 1366 Verify the current configuration for correctness:
1425 1367 .RS +4
1426 1368 .TP
1427 1369 .ie t \(bu
1428 1370 .el o
1429 1371 All resources have all of their required properties specified.
1430 1372 .RE
1431 1373 .RS +4
1432 1374 .TP
1433 1375 .ie t \(bu
1434 1376 .el o
1435 1377 A \fBzonepath\fR is specified.
1436 1378 .RE
1437 1379 .RE
1438 1380
1439 1381 .sp
1440 1382 .ne 2
1441 1383 .na
1442 1384 \fB\fBrevert\fR \fB[\fR\fB-F\fR\fB]\fR\fR
1443 1385 .ad
1444 1386 .sp .6
1445 1387 .RS 4n
1446 1388 Revert the configuration back to the last committed state. The \fB-F\fR option
1447 1389 can be used to force the action.
1448 1390 .RE
1449 1391
1450 1392 .sp
1451 1393 .ne 2
1452 1394 .na
1453 1395 \fB\fBexit [\fR\fB-F\fR\fB]\fR\fR
1454 1396 .ad
1455 1397 .sp .6
1456 1398 .RS 4n
1457 1399 Exit the \fBzonecfg\fR session. A commit is automatically attempted if needed.
1458 1400 You can also use an \fBEOF\fR character to exit \fBzonecfg\fR. The \fB-F\fR
1459 1401 option can be used to force the action.
1460 1402 .RE
1461 1403
1462 1404 .SH EXAMPLES
1463 1405 .LP
1464 1406 \fBExample 1 \fRCreating the Environment for a New Zone
1465 1407 .sp
1466 1408 .LP
1467 1409 In the following example, \fBzonecfg\fR creates the environment for a new zone.
1468 1410 \fB/usr/local\fR is loopback mounted from the global zone into
1469 1411 \fB/opt/local\fR. \fB/opt/sfw\fR is loopback mounted from the global zone,
1470 1412 three logical network interfaces are added, and a limit on the number of
1471 1413 fair-share scheduler (FSS) CPU shares for a zone is set using the \fBrctl\fR
1472 1414 resource type. The example also shows how to select a given resource for
1473 1415 modification.
1474 1416
1475 1417 .sp
1476 1418 .in +2
1477 1419 .nf
1478 1420 example# \fBzonecfg -z myzone3\fR
1479 1421 my-zone3: No such zone configured
1480 1422 Use 'create' to begin configuring a new zone.
1481 1423 zonecfg:myzone3> \fBcreate\fR
1482 1424 zonecfg:myzone3> \fBset zonepath=/export/home/my-zone3\fR
1483 1425 zonecfg:myzone3> \fBset autoboot=true\fR
1484 1426 zonecfg:myzone3> \fBadd fs\fR
1485 1427 zonecfg:myzone3:fs> \fBset dir=/usr/local\fR
1486 1428 zonecfg:myzone3:fs> \fBset special=/opt/local\fR
1487 1429 zonecfg:myzone3:fs> \fBset type=lofs\fR
1488 1430 zonecfg:myzone3:fs> \fBadd options [ro,nodevices]\fR
1489 1431 zonecfg:myzone3:fs> \fBend\fR
1490 1432 zonecfg:myzone3> \fBadd fs\fR
1491 1433 zonecfg:myzone3:fs> \fBset dir=/mnt\fR
1492 1434 zonecfg:myzone3:fs> \fBset special=/dev/dsk/c0t0d0s7\fR
1493 1435 zonecfg:myzone3:fs> \fBset raw=/dev/rdsk/c0t0d0s7\fR
1494 1436 zonecfg:myzone3:fs> \fBset type=ufs\fR
1495 1437 zonecfg:myzone3:fs> \fBend\fR
1496 1438 zonecfg:myzone3> \fBadd net\fR
1497 1439 zonecfg:myzone3:net> \fBset address=192.168.0.1/24\fR
1498 1440 zonecfg:myzone3:net> \fBset physical=eri0\fR
1499 1441 zonecfg:myzone3:net> \fBend\fR
1500 1442 zonecfg:myzone3> \fBadd net\fR
1501 1443 zonecfg:myzone3:net> \fBset address=192.168.1.2/24\fR
1502 1444 zonecfg:myzone3:net> \fBset physical=eri0\fR
1503 1445 zonecfg:myzone3:net> \fBend\fR
1504 1446 zonecfg:myzone3> \fBadd net\fR
1505 1447 zonecfg:myzone3:net> \fBset address=192.168.2.3/24\fR
1506 1448 zonecfg:myzone3:net> \fBset physical=eri0\fR
1507 1449 zonecfg:myzone3:net> \fBend\fR
1508 1450 zonecfg:my-zone3> \fBset cpu-shares=5\fR
1509 1451 zonecfg:my-zone3> \fBadd capped-memory\fR
1510 1452 zonecfg:my-zone3:capped-memory> \fBset physical=50m\fR
1511 1453 zonecfg:my-zone3:capped-memory> \fBset swap=100m\fR
1512 1454 zonecfg:my-zone3:capped-memory> \fBend\fR
1513 1455 zonecfg:myzone3> \fBexit\fR
1514 1456 .fi
1515 1457 .in -2
1516 1458 .sp
1517 1459
1518 1460 .LP
1519 1461 \fBExample 2 \fRCreating a Non-Native Zone
1520 1462 .sp
1521 1463 .LP
1522 1464 The following example creates a new Linux zone:
1523 1465
1524 1466 .sp
1525 1467 .in +2
1526 1468 .nf
1527 1469 example# \fBzonecfg -z lxzone\fR
1528 1470 lxzone: No such zone configured
1529 1471 Use 'create' to begin configuring a new zone
1530 1472 zonecfg:lxzone> \fBcreate -t SUNWlx\fR
1531 1473 zonecfg:lxzone> \fBset zonepath=/export/zones/lxzone\fR
1532 1474 zonecfg:lxzone> \fBset autoboot=true\fR
1533 1475 zonecfg:lxzone> \fBexit\fR
1534 1476 .fi
1535 1477 .in -2
1536 1478 .sp
1537 1479
1538 1480 .LP
1539 1481 \fBExample 3 \fRCreating an Exclusive-IP Zone
1540 1482 .sp
1541 1483 .LP
1542 1484 The following example creates a zone that is granted exclusive access to
1543 1485 \fBbge1\fR and \fBbge33000\fR and that is isolated at the IP layer from the
1544 1486 other zones configured on the system.
1545 1487
1546 1488 .sp
1547 1489 .LP
1548 1490 The IP addresses and routing is configured inside the new zone using
1549 1491 \fBsysidtool\fR(1M).
1550 1492
1551 1493 .sp
1552 1494 .in +2
1553 1495 .nf
1554 1496 example# \fBzonecfg -z excl\fR
1555 1497 excl: No such zone configured
1556 1498 Use 'create' to begin configuring a new zone
1557 1499 zonecfg:excl> \fBcreate\fR
1558 1500 zonecfg:excl> \fBset zonepath=/export/zones/excl\fR
1559 1501 zonecfg:excl> \fBset ip-type=exclusive\fR
1560 1502 zonecfg:excl> \fBadd net\fR
1561 1503 zonecfg:excl:net> \fBset physical=bge1\fR
1562 1504 zonecfg:excl:net> \fBend\fR
1563 1505 zonecfg:excl> \fBadd net\fR
1564 1506 zonecfg:excl:net> \fBset physical=bge33000\fR
1565 1507 zonecfg:excl:net> \fBend\fR
1566 1508 zonecfg:excl> \fBexit\fR
1567 1509 .fi
1568 1510 .in -2
1569 1511 .sp
1570 1512
1571 1513 .LP
1572 1514 \fBExample 4 \fRAssociating a Zone with a Resource Pool
1573 1515 .sp
1574 1516 .LP
1575 1517 The following example shows how to associate an existing zone with an existing
1576 1518 resource pool:
1577 1519
1578 1520 .sp
1579 1521 .in +2
1580 1522 .nf
1581 1523 example# \fBzonecfg -z myzone\fR
1582 1524 zonecfg:myzone> \fBset pool=mypool\fR
1583 1525 zonecfg:myzone> \fBexit\fR
1584 1526 .fi
1585 1527 .in -2
1586 1528 .sp
1587 1529
1588 1530 .sp
1589 1531 .LP
1590 1532 For more information about resource pools, see \fBpooladm\fR(1M) and
1591 1533 \fBpoolcfg\fR(1M).
1592 1534
1593 1535 .LP
1594 1536 \fBExample 5 \fRChanging the Name of a Zone
1595 1537 .sp
1596 1538 .LP
1597 1539 The following example shows how to change the name of an existing zone:
1598 1540
1599 1541 .sp
1600 1542 .in +2
1601 1543 .nf
1602 1544 example# \fBzonecfg -z myzone\fR
1603 1545 zonecfg:myzone> \fBset zonename=myzone2\fR
1604 1546 zonecfg:myzone2> \fBexit\fR
1605 1547 .fi
1606 1548 .in -2
1607 1549 .sp
1608 1550
1609 1551 .LP
1610 1552 \fBExample 6 \fRChanging the Privilege Set of a Zone
1611 1553 .sp
1612 1554 .LP
1613 1555 The following example shows how to change the set of privileges an existing
1614 1556 zone's processes will be limited to the next time the zone is booted. In this
1615 1557 particular case, the privilege set will be the standard safe set of privileges
1616 1558 a zone normally has along with the privilege to change the system date and
1617 1559 time:
1618 1560
1619 1561 .sp
1620 1562 .in +2
1621 1563 .nf
1622 1564 example# \fBzonecfg -z myzone\fR
1623 1565 zonecfg:myzone> \fBset limitpriv="default,sys_time"\fR
1624 1566 zonecfg:myzone2> \fBexit\fR
1625 1567 .fi
1626 1568 .in -2
1627 1569 .sp
1628 1570
1629 1571 .LP
1630 1572 \fBExample 7 \fRSetting the \fBzone.cpu-shares\fR Property for the Global Zone
1631 1573 .sp
1632 1574 .LP
1633 1575 The following command sets the \fBzone.cpu-shares\fR property for the global
1634 1576 zone:
1635 1577
1636 1578 .sp
1637 1579 .in +2
1638 1580 .nf
1639 1581 example# \fBzonecfg -z global\fR
1640 1582 zonecfg:global> \fBset cpu-shares=5\fR
1641 1583 zonecfg:global> \fBexit\fR
1642 1584 .fi
1643 1585 .in -2
1644 1586 .sp
1645 1587
1646 1588 .LP
1647 1589 \fBExample 8 \fRUsing Pattern Matching
1648 1590 .sp
1649 1591 .LP
1650 1592 The following commands illustrate \fBzonecfg\fR support for pattern matching.
1651 1593 In the zone \fBflexlm\fR, enter:
1652 1594
1653 1595 .sp
1654 1596 .in +2
1655 1597 .nf
1656 1598 zonecfg:flexlm> \fBadd device\fR
1657 1599 zonecfg:flexlm:device> \fBset match="/dev/cua/a00[2-5]"\fR
1658 1600 zonecfg:flexlm:device> \fBend\fR
1659 1601 .fi
1660 1602 .in -2
1661 1603 .sp
1662 1604
1663 1605 .sp
1664 1606 .LP
1665 1607 In the global zone, enter:
1666 1608
1667 1609 .sp
1668 1610 .in +2
1669 1611 .nf
1670 1612 global# \fBls /dev/cua\fR
1671 1613 a a000 a001 a002 a003 a004 a005 a006 a007 b
1672 1614 .fi
1673 1615 .in -2
1674 1616 .sp
1675 1617
1676 1618 .sp
1677 1619 .LP
1678 1620 In the zone \fBflexlm\fR, enter:
1679 1621
1680 1622 .sp
1681 1623 .in +2
1682 1624 .nf
1683 1625 flexlm# \fBls /dev/cua\fR
1684 1626 a002 a003 a004 a005
1685 1627 .fi
1686 1628 .in -2
1687 1629 .sp
1688 1630
1689 1631 .LP
1690 1632 \fBExample 9 \fRSetting a Cap for a Zone to Three CPUs
1691 1633 .sp
1692 1634 .LP
1693 1635 The following sequence uses the \fBzonecfg\fR command to set the CPU cap for a
1694 1636 zone to three CPUs.
1695 1637
1696 1638 .sp
1697 1639 .in +2
1698 1640 .nf
1699 1641 zonecfg:myzone> \fBadd capped-cpu\fR
1700 1642 zonecfg:myzone>capped-cpu> \fBset ncpus=3\fR
1701 1643 zonecfg:myzone>capped-cpu>capped-cpu> \fBend\fR
1702 1644 .fi
1703 1645 .in -2
1704 1646 .sp
1705 1647
1706 1648 .sp
1707 1649 .LP
1708 1650 The preceding sequence, which uses the capped-cpu property, is equivalent to
1709 1651 the following sequence, which makes use of the \fBzone.cpu-cap\fR resource
1710 1652 control.
1711 1653
1712 1654 .sp
1713 1655 .in +2
1714 1656 .nf
1715 1657 zonecfg:myzone> \fBadd rctl\fR
1716 1658 zonecfg:myzone:rctl> \fBset name=zone.cpu-cap\fR
1717 1659 zonecfg:myzone:rctl> \fBadd value (priv=privileged,limit=300,action=none)\fR
1718 1660 zonecfg:myzone:rctl> \fBend\fR
1719 1661 .fi
1720 1662 .in -2
1721 1663 .sp
1722 1664
1723 1665 .LP
1724 1666 \fBExample 10 \fRUsing \fBkstat\fR to Monitor CPU Caps
1725 1667 .sp
1726 1668 .LP
1727 1669 The following command displays information about all CPU caps.
1728 1670
1729 1671 .sp
1730 1672 .in +2
1731 1673 .nf
1732 1674 # \fBkstat -n /cpucaps/\fR
1733 1675 module: caps instance: 0
1734 1676 name: cpucaps_project_0 class: project_caps
1735 1677 above_sec 0
1736 1678 below_sec 2157
1737 1679 crtime 821.048183159
1738 1680 maxusage 2
1739 1681 nwait 0
1740 1682 snaptime 235885.637253027
1741 1683 usage 0
1742 1684 value 18446743151372347932
1743 1685 zonename global
1744 1686
1745 1687 module: caps instance: 0
1746 1688 name: cpucaps_project_1 class: project_caps
1747 1689 above_sec 0
1748 1690 below_sec 0
1749 1691 crtime 225339.192787265
1750 1692 maxusage 5
1751 1693 nwait 0
1752 1694 snaptime 235885.637591677
1753 1695 usage 5
1754 1696 value 18446743151372347932
1755 1697 zonename global
1756 1698
1757 1699 module: caps instance: 0
1758 1700 name: cpucaps_project_201 class: project_caps
1759 1701 above_sec 0
1760 1702 below_sec 235105
1761 1703 crtime 780.37961782
1762 1704 maxusage 100
1763 1705 nwait 0
1764 1706 snaptime 235885.637789687
1765 1707 usage 43
1766 1708 value 100
1767 1709 zonename global
1768 1710
1769 1711 module: caps instance: 0
1770 1712 name: cpucaps_project_202 class: project_caps
1771 1713 above_sec 0
1772 1714 below_sec 235094
1773 1715 crtime 791.72983782
1774 1716 maxusage 100
1775 1717 nwait 0
1776 1718 snaptime 235885.637967512
1777 1719 usage 48
1778 1720 value 100
1779 1721 zonename global
1780 1722
1781 1723 module: caps instance: 0
1782 1724 name: cpucaps_project_203 class: project_caps
1783 1725 above_sec 0
1784 1726 below_sec 235034
1785 1727 crtime 852.104401481
1786 1728 maxusage 75
1787 1729 nwait 0
1788 1730 snaptime 235885.638144304
1789 1731 usage 47
1790 1732 value 100
1791 1733 zonename global
1792 1734
1793 1735 module: caps instance: 0
1794 1736 name: cpucaps_project_86710 class: project_caps
1795 1737 above_sec 22
1796 1738 below_sec 235166
1797 1739 crtime 698.441717859
1798 1740 maxusage 101
1799 1741 nwait 0
1800 1742 snaptime 235885.638319871
1801 1743 usage 54
1802 1744 value 100
1803 1745 zonename global
1804 1746
1805 1747 module: caps instance: 0
1806 1748 name: cpucaps_zone_0 class: zone_caps
1807 1749 above_sec 100733
1808 1750 below_sec 134332
1809 1751 crtime 821.048177123
1810 1752 maxusage 207
1811 1753 nwait 2
1812 1754 snaptime 235885.638497731
1813 1755 usage 199
1814 1756 value 200
1815 1757 zonename global
1816 1758
1817 1759 module: caps instance: 1
1818 1760 name: cpucaps_project_0 class: project_caps
1819 1761 above_sec 0
1820 1762 below_sec 0
1821 1763 crtime 225360.256448422
1822 1764 maxusage 7
1823 1765 nwait 0
1824 1766 snaptime 235885.638714404
1825 1767 usage 7
1826 1768 value 18446743151372347932
1827 1769 zonename test_001
1828 1770
1829 1771 module: caps instance: 1
1830 1772 name: cpucaps_zone_1 class: zone_caps
1831 1773 above_sec 2
1832 1774 below_sec 10524
1833 1775 crtime 225360.256440278
1834 1776 maxusage 106
1835 1777 nwait 0
1836 1778 snaptime 235885.638896443
1837 1779 usage 7
1838 1780 value 100
1839 1781 zonename test_001
1840 1782 .fi
1841 1783 .in -2
1842 1784 .sp
1843 1785
1844 1786 .LP
1845 1787 \fBExample 11 \fRDisplaying CPU Caps for a Specific Zone or Project
1846 1788 .sp
1847 1789 .LP
1848 1790 Using the \fBkstat\fR \fB-c\fR and \fB-i\fR options, you can display CPU caps
1849 1791 for a specific zone or project, as below. The first command produces a display
1850 1792 for a specific project, the second for the same project within zone 1.
1851 1793
1852 1794 .sp
1853 1795 .in +2
1854 1796 .nf
1855 1797 # \fBkstat -c project_caps\fR
1856 1798
1857 1799 # \fBkstat -c project_caps -i 1\fR
1858 1800 .fi
1859 1801 .in -2
1860 1802 .sp
1861 1803
1862 1804 .SH EXIT STATUS
1863 1805 .LP
1864 1806 The following exit values are returned:
1865 1807 .sp
1866 1808 .ne 2
1867 1809 .na
1868 1810 \fB\fB0\fR\fR
1869 1811 .ad
1870 1812 .sp .6
1871 1813 .RS 4n
1872 1814 Successful completion.
1873 1815 .RE
1874 1816
1875 1817 .sp
1876 1818 .ne 2
1877 1819 .na
1878 1820 \fB\fB1\fR\fR
1879 1821 .ad
1880 1822 .sp .6
1881 1823 .RS 4n
1882 1824 An error occurred.
1883 1825 .RE
1884 1826
1885 1827 .sp
1886 1828 .ne 2
1887 1829 .na
1888 1830 \fB\fB2\fR\fR
1889 1831 .ad
1890 1832 .sp .6
1891 1833 .RS 4n
1892 1834 Invalid usage.
1893 1835 .RE
1894 1836
1895 1837 .SH ATTRIBUTES
1896 1838 .LP
1897 1839 See \fBattributes\fR(5) for descriptions of the following attributes:
1898 1840 .sp
1899 1841
1900 1842 .sp
1901 1843 .TS
1902 1844 box;
1903 1845 c | c
1904 1846 l | l .
1905 1847 ATTRIBUTE TYPE ATTRIBUTE VALUE
1906 1848 _
1907 1849 Interface Stability Volatile
1908 1850 .TE
1909 1851
1910 1852 .SH SEE ALSO
1911 1853 .LP
1912 1854 \fBppriv\fR(1), \fBprctl\fR(1), \fBzlogin\fR(1), \fBkstat\fR(1M),
1913 1855 \fBmount\fR(1M), \fBpooladm\fR(1M), \fBpoolcfg\fR(1M), \fBpoold\fR(1M),
1914 1856 \fBrcapd\fR(1M), \fBrctladm\fR(1M), \fBsvcadm\fR(1M), \fBsysidtool\fR(1M),
1915 1857 \fBzfs\fR(1M), \fBzoneadm\fR(1M), \fBpriocntl\fR(2), \fBpriv_str_to_set\fR(3C),
1916 1858 \fBkstat\fR(3KSTAT), \fBvfstab\fR(4), \fBattributes\fR(5), \fBbrands\fR(5),
1917 1859 \fBfnmatch\fR(5), \fBlx\fR(5), \fBprivileges\fR(5), \fBresource_controls\fR(5),
1918 1860 \fBzones\fR(5)
1919 1861 .sp
1920 1862 .LP
1921 1863 \fISystem Administration Guide: Solaris Containers-Resource Management, and
1922 1864 Solaris Zones\fR
1923 1865 .SH NOTES
1924 1866 .LP
1925 1867 All character data used by \fBzonecfg\fR must be in US-ASCII encoding.
|
↓ open down ↓ |
530 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX