Print this page
5432 zoneadm install could fix zonepath permissions automatically
Reviewed by: Jerry Jelinek <jerry.jelinek@joyent.com>
| Split |
Close |
| Expand all |
| Collapse all |
--- old/usr/src/man/man1m/zoneadm.1m
+++ new/usr/src/man/man1m/zoneadm.1m
1 1 '\" te
2 2 .\" Copyright 2014 Nexenta Systems, Inc. All rights reserved.
3 3 .\" Copyright (c) 2009 Sun Microsystems, Inc. All Rights Reserved.
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.
5 5 .\" 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.
6 6 .\" 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]
7 -.TH ZONEADM 1M "Oct 30, 2013"
7 +.TH ZONEADM 1M "Dec 26, 2014"
8 8 .SH NAME
9 9 zoneadm \- administer zones
10 10 .SH SYNOPSIS
11 11 .LP
12 12 .nf
13 13 \fBzoneadm\fR \fB-z\fR \fIzonename\fR [\fB-u\fR \fIuuid-match\fR] \fIsubcommand\fR
14 14 [\fIsubcommand_options\fR]
15 15 .fi
16 16
17 17 .LP
18 18 .nf
|
↓ open down ↓ |
1 lines elided |
↑ open up ↑ |
19 19 \fBzoneadm\fR [\fB-R\fR \fIroot\fR] [\fB-z\fR \fIzonename\fR] [\fB-u\fR \fIuuid-match\fR] list
20 20 [\fIlist_options\fR]
21 21 .fi
22 22
23 23 .LP
24 24 .nf
25 25 \fBzoneadm\fR [\fB-R\fR \fIroot\fR] \fB-z\fR \fIzonename\fR [\fB-u\fR \fIuuid-match\fR] mark incomplete
26 26 .fi
27 27
28 28 .SH DESCRIPTION
29 -.sp
30 29 .LP
31 30 The \fBzoneadm\fR utility is used to administer system zones. A zone is an
32 31 application container that is maintained by the operating system runtime.
33 32 .SH SECURITY
34 -.sp
35 33 .LP
36 34 Once a process has been placed in a zone other than zone \fB0\fR, the process
37 35 or any of its children cannot change zones.
38 36 .SH OPTIONS
39 -.sp
40 37 .LP
41 38 The following options are supported:
42 39 .sp
43 40 .ne 2
44 41 .na
45 42 \fB\fB-R\fR \fIroot\fR\fR
46 43 .ad
47 44 .sp .6
48 45 .RS 4n
49 46 Specify an alternate root (boot environment). This option can only be used in
50 47 conjunction with the "\fBlist\fR" and "\fBmark\fR" subcommands.
51 48 .RE
52 49
53 50 .sp
54 51 .ne 2
55 52 .na
56 53 \fB\fB-u\fR \fIuuid-match\fR\fR
57 54 .ad
58 55 .sp .6
59 56 .RS 4n
60 57 Unique identifier for a zone, as assigned by \fBlibuuid\fR(3LIB). If this
61 58 option is present and the argument is a non-empty string, then the zone
62 59 matching the \fBUUID\fR is selected instead of the one named by the \fB-z\fR
63 60 option, if such a zone is present.
64 61 .RE
65 62
66 63 .sp
|
↓ open down ↓ |
17 lines elided |
↑ open up ↑ |
67 64 .ne 2
68 65 .na
69 66 \fB\fB-z\fR \fIzonename\fR\fR
70 67 .ad
71 68 .sp .6
72 69 .RS 4n
73 70 String identifier for a zone.
74 71 .RE
75 72
76 73 .SH SUBCOMMANDS
77 -.sp
78 74 .LP
79 75 Subcommands which can result in destructive actions or loss of work have a
80 76 \fB-F\fR flag to force the action. If input is from a terminal device, the user
81 77 is prompted if such a command is given without the \fB-F\fR flag; otherwise, if
82 78 such a command is given without the \fB-F\fR flag, the action is disallowed,
83 79 with a diagnostic message written to standard error. If a zone installation or
84 80 uninstallation is interrupted, the zone is left in the incomplete state. Use
85 81 uninstall to reset such a zone back to the configured state.
86 82 .sp
87 83 .LP
88 84 The following subcommands are supported:
89 85 .sp
90 86 .ne 2
91 87 .na
92 88 \fB\fBattach\fR [\fB-F\fR] [\fB-n\fR \fIpath\fR] [\fIbrand-specific
93 89 options\fR]\fR
94 90 .ad
95 91 .sp .6
96 92 .RS 4n
97 93 The \fBattach\fR subcommand takes a zone that has been detached from one system
98 94 and attaches the zone onto a new system. Therefore, it is advised (though not
99 95 required) that the \fBdetach\fR subcommand should be run before the "attach"
100 96 takes place. Once you have the new zone in the configured state, use the
101 97 \fBattach\fR subcommand to set up the zone root instead of installing the zone
102 98 as a new zone.
103 99 .sp
104 100 The \fB-F\fR option can be used to force the zone into the "installed" state
105 101 with no validation. This option should be used with care since it can leave the
106 102 zone in an unsupportable state if it was moved from a source system to a target
107 103 system that is unable to properly host the zone. The \fB-n\fR option can be
108 104 used to run the \fBattach\fR subcommand, without executing the command. It uses
109 105 the output of the "\fBdetach\fR \fB-n\fR" subcommand as input and is useful to
110 106 identify any conflicting issues, such as the network device being incompatible,
111 107 and can also determine whether the host is capable of supporting the zone. The
112 108 path can be "\fB-\fR", to read the input from standard input.
113 109 .sp
114 110 The zone's brand may include additional options that govern how the zone will
115 111 be attached. See \fBbrands\fR(5) for specific brand information.
116 112 .sp
117 113 The zone being attached must first be configured using the \fBzonecfg\fR (see
118 114 \fBzonecfg\fR(1M)) command. This does not apply when running "\fBattach\fR
119 115 \fB-n\fR".
120 116 .sp
121 117 Use the following command to attach a zone:
122 118 .sp
123 119 .in +2
124 120 .nf
125 121 # \fBzoneadm -z my-zone attach\fR
126 122 .fi
127 123 .in -2
128 124 .sp
129 125
130 126 .RE
131 127
132 128 .sp
133 129 .ne 2
134 130 .na
135 131 \fB\fBboot\fR [\fB--\fR \fIboot_options\fR]\fR
136 132 .ad
137 133 .sp .6
138 134 .RS 4n
139 135 Boot (or activate) the specified zones.
140 136 .sp
141 137 The following \fIboot_options\fR are supported:
142 138 .sp
143 139 .ne 2
144 140 .na
145 141 \fB\fB-i\fR \fIaltinit\fR\fR
146 142 .ad
147 143 .sp .6
148 144 .RS 4n
149 145 Select an alternative executable to be the primordial Process. \fIaltinit\fR is
150 146 a valid path to an executable. The default primordial process is
151 147 \fBinit\fR(1M).
152 148 .RE
153 149
154 150 .sp
155 151 .ne 2
156 152 .na
157 153 \fB\fB-m\fR \fIsmf_options\fR\fR
158 154 .ad
159 155 .sp .6
160 156 .RS 4n
161 157 The \fIsmf_options\fR include two categories of options to control booting
162 158 behavior of the service management facility: recovery options and messages
163 159 options.
164 160 .sp
165 161 Message options determine the type and amount of messages that \fBsmf\fR(5)
166 162 displays during boot. Service options determine the services which are used to
167 163 boot the system. See \fBkernel\fR(1M) for a listing of the \fB-m\fR suboptions.
168 164 .RE
169 165
170 166 .sp
171 167 .ne 2
172 168 .na
173 169 \fB\fB-s\fR\fR
174 170 .ad
175 171 .sp .6
176 172 .RS 4n
177 173 Boots only to milestone \fBsvc:/milestone/single-user:default\fR. This
178 174 milestone is equivalent to init level \fBs\fR. See \fBsvc.startd\fR(1M) and
179 175 \fBinit\fR(1M).
180 176 .RE
181 177
182 178 .RE
183 179
184 180 .sp
185 181 .ne 2
186 182 .na
187 183 \fB\fBclone\fR [\fB-m\fR \fIcopy\fR] [\fB-s\fR \fIzfs_snapshot\fR]
188 184 \fIsource_zone\fR\fR
189 185 .ad
190 186 .sp .6
191 187 .RS 4n
192 188 Install a zone by copying an existing installed zone. This subcommand is an
193 189 alternative way to install the zone.
194 190 .sp
195 191 .ne 2
196 192 .na
197 193 \fB\fB-m\fR \fIcopy\fR\fR
198 194 .ad
199 195 .sp .6
200 196 .RS 4n
201 197 Force the clone to be a copy, even if a "\fBZFS\fR clone" is possible.
202 198 .RE
203 199
204 200 .sp
205 201 .ne 2
206 202 .na
207 203 \fB\fB-s\fR \fIzfs_snapshot\fR\fR
208 204 .ad
209 205 .sp .6
210 206 .RS 4n
211 207 Specify the name of a \fBZFS\fR snapshot to use as the source of the clone. The
212 208 \fIsnapshot\fR must be a \fIsnapshot\fR of the source zone taken from a
213 209 previous "\fBzoneadm\fR clone" installation.
214 210 .RE
215 211
216 212 The source zone must be halted before this subcommand can be used.
217 213 .RE
218 214
219 215 .sp
220 216 .ne 2
221 217 .na
222 218 \fB\fBdetach\fR [\fB-n\fR]\fR
223 219 .ad
224 220 .sp .6
225 221 .RS 4n
226 222 Detach the specified zone. Detaching a zone is the first step in moving a zone
227 223 from one system to another. The full procedure to migrate a zone is that the
228 224 zone is detached, the \fIzonepath\fR directory is moved to the new host, and
229 225 then the zone is attached on the new host. Once the zone is detached, it is
230 226 left in the configured state. If you try to install or clone to a configured
231 227 zone that has been detached, you will receive an error message and the
232 228 \fBinstall\fR or \fBclone\fR subcommand will not be allowed to proceed. The
233 229 \fB-n\fR option can be used to run the \fBdetach\fR subcommand, without
234 230 executing the command. This generates the information needed for running the
235 231 "\fBattach\fR \fB-n\fR" subcommand, which is useful to identify any conflicting
236 232 issues, such as the network device being incompatible or if the host is capable
237 233 of supporting the zone. The information is sent to standard output and can be
238 234 saved to a file or piped to the "\fBattach\fR \fB-n\fR" subcommand.
239 235 .sp
240 236 Use the following command to detach a zone:
241 237 .sp
242 238 .in +2
243 239 .nf
244 240 # zoneadm -z my-zone detach
245 241 .fi
246 242 .in -2
247 243 .sp
248 244
249 245 The source zone must be halted before this subcommand can be used.
250 246 .RE
251 247
252 248 .sp
253 249 .ne 2
254 250 .na
255 251 \fB\fBhalt\fR\fR
256 252 .ad
257 253 .sp .6
258 254 .RS 4n
259 255 Halt the specified zones. \fBhalt\fR bypasses running the shutdown scripts
260 256 inside the zone. It also removes run time resources of the zone.
261 257 .RE
262 258
263 259 .sp
264 260 .ne 2
265 261 .na
266 262 \fB\fBhelp\fR [\fIsubcommand\fR]\fR
267 263 .ad
268 264 .sp .6
269 265 .RS 4n
270 266 Display general help. If you specify \fIsubcommand\fR, displays help on
271 267 \fIsubcommand\fR.
|
↓ open down ↓ |
184 lines elided |
↑ open up ↑ |
272 268 .RE
273 269
274 270 .sp
275 271 .ne 2
276 272 .na
277 273 \fB\fBinstall\fR [\fB-x\fR \fInodataset\fR] [\fIbrand-specific options\fR]\fR
278 274 .ad
279 275 .sp .6
280 276 .RS 4n
281 277 Install the specified zone on the system. This subcommand automatically
282 -attempts to verify first. It refuses to install if the verify step fails. See
283 -the \fBverify\fR subcommand.
278 +attempts to verify first, most verification errors are fatal. See the
279 +\fBverify\fR subcommand.
284 280 .sp
285 281 .ne 2
286 282 .na
287 283 \fB\fB-x\fR \fInodataset\fR\fR
288 284 .ad
289 285 .sp .6
290 286 .RS 4n
291 287 Do not create a \fBZFS\fR file system.
292 288 .RE
293 289
294 290 The zone's brand may include additional options that govern how the software
295 291 will be installed in the zone. See \fBbrands\fR(5) for specific brand
296 292 information.
297 293 .RE
298 294
299 295 .sp
300 296 .ne 2
301 297 .na
302 298 \fB\fBlist\fR [\fIlist_options\fR]\fR
303 299 .ad
304 300 .sp .6
305 301 .RS 4n
306 302 Display the name of the current zones, or the specified zone if indicated.
307 303 .sp
308 304 By default, all running zones are listed. If you use this subcommand with the
309 305 \fBzoneadm\fR \fB-z\fR \fIzonename\fR option, it lists only the specified zone,
310 306 regardless of its state. In this case, the \fB-i\fR and \fB-c\fR options are
311 307 disallowed.
312 308 .sp
313 309 If neither the \fB-i\fR or \fB-c\fR options are given, all running zones are
314 310 listed.
315 311 .sp
316 312 The following \fIlist_options\fR are supported:
317 313 .sp
318 314 .ne 2
319 315 .na
320 316 \fB\fB-c\fR\fR
321 317 .ad
322 318 .sp .6
323 319 .RS 4n
324 320 Display all configured zones. This option overides the \fB-i\fR option.
325 321 .RE
326 322
327 323 .sp
328 324 .ne 2
329 325 .na
330 326 \fB\fB-i\fR\fR
331 327 .ad
332 328 .sp .6
333 329 .RS 4n
334 330 Expand the display to all installed zones.
335 331 .RE
336 332
337 333 .sp
338 334 .ne 2
339 335 .na
340 336 \fB\fB-p\fR\fR
341 337 .ad
342 338 .sp .6
343 339 .RS 4n
344 340 Request machine parsable output. The output format is a list of lines, one per
345 341 zone, with colon- delimited fields. These fields are:
346 342 .sp
347 343 .in +2
348 344 .nf
349 345 zoneid:zonename:state:zonepath:uuid:brand:ip-type
350 346 .fi
351 347 .in -2
352 348 .sp
353 349
354 350 If the \fBzonepath\fR contains embedded colons, they can be escaped by a
355 351 backslash ("\:"), which is parsable by using the shell \fBread\fR(1) function
356 352 with the environmental variable \fBIFS\fR. The \fIuuid\fR value is assigned by
357 353 \fBlibuuid\fR(3LIB) when the zone is installed, and is useful for identifying
358 354 the same zone when present (or renamed) on alternate boot environments. Any
359 355 software that parses the output of the "\fBzoneadm list -p\fR" command must be
360 356 able to handle any fields that may be added in the future.
361 357 .sp
362 358 The \fB-v\fR and \fB-p\fR options are mutually exclusive. If neither \fB-v\fR
363 359 nor \fB-p\fR is used, just the zone name is listed.
364 360 .RE
365 361
366 362 .sp
367 363 .ne 2
368 364 .na
369 365 \fB\fB-v\fR\fR
370 366 .ad
371 367 .sp .6
372 368 .RS 4n
373 369 Display verbose information, including zone name, id, current state, root
374 370 directory, brand type, ip-type, and options.
375 371 .sp
376 372 The \fB-v\fR and \fB-p\fR options are mutually exclusive. If neither \fB-v\fR
377 373 nor \fB-p\fR is used, just the zone name is listed.
378 374 .RE
379 375
380 376 .RE
381 377
382 378 .sp
383 379 .ne 2
384 380 .na
385 381 \fB\fBmark incomplete\fR\fR
386 382 .ad
387 383 .sp .6
388 384 .RS 4n
389 385 Change the state of an installed zone to "incomplete." This command may be
390 386 useful in cases where administrative changes on the system have rendered a zone
391 387 unusable or inconsistent. This change cannot be undone (except by uninstalling
392 388 the zone).
393 389 .RE
394 390
395 391 .sp
396 392 .ne 2
397 393 .na
398 394 \fB\fBmove\fR \fInew_zonepath\fR\fR
399 395 .ad
400 396 .sp .6
401 397 .RS 4n
402 398 Move the \fIzonepath\fR to \fInew_zonepath\fR. The zone must be halted before
403 399 this subcommand can be used. The \fInew_zonepath\fR must be a local file system
404 400 and normal restrictions for \fIzonepath\fR apply.
405 401 .RE
406 402
407 403 .sp
408 404 .ne 2
409 405 .na
410 406 \fB\fBready\fR\fR
411 407 .ad
412 408 .sp .6
413 409 .RS 4n
414 410 Prepares a zone for running applications but does not start any user processes
415 411 in the zone.
416 412 .RE
417 413
418 414 .sp
419 415 .ne 2
420 416 .na
421 417 \fB\fBreboot\fR\ [\fB--\fR \fIboot_options\fR]]\fR
422 418 .ad
423 419 .sp .6
424 420 .RS 4n
425 421 Restart the zones. This is equivalent to a \fBhalt\fR \fBboot\fR sequence. This
426 422 subcommand fails if the specified zones are not active. See \fIboot\fR subcommand
427 423 for the boot options.
428 424 .RE
429 425
430 426 .sp
431 427 .ne 2
432 428 .na
433 429 \fB\fBshutdown\fR [\fB-r\fR [\fB--\fR \fIboot_options\fR]]\fR
434 430 .ad
435 431 .sp .6
436 432 .RS 4n
437 433 Gracefully shutdown the specified zone. This subcommand waits for all zone
438 434 processes to finish; the default timeout is SCF_PROPERTY_TIMEOUT value from
439 435 the SMF service system/zones. If the \fB-r\fR option is specified, reboot the
440 436 zone. See \fIboot\fR subcommand for the boot options.
441 437 .RE
442 438
443 439 .sp
444 440 .ne 2
445 441 .na
446 442 \fB\fBuninstall [\fR\fB-F\fR\fB]\fR\fR
447 443 .ad
448 444 .sp .6
449 445 .RS 4n
450 446 Uninstall the specified zone from the system. Use this subcommand with caution.
451 447 It removes all of the files under the \fIzonepath\fR of the zone in question.
452 448 You can use the \fB-F\fR flag to force the action.
453 449 .RE
454 450
455 451 .sp
456 452 .ne 2
457 453 .na
458 454 \fB\fBverify\fR\fR
459 455 .ad
460 456 .sp .6
461 457 .RS 4n
462 458 Check to make sure the configuration of the specified zone can safely be
463 459 installed on the machine. Following is a break-down of the checks by
464 460 \fBresource/property\fR type:
465 461 .sp
466 462 .ne 2
467 463 .na
468 464 \fB\fBzonepath\fR\fR
469 465 .ad
470 466 .sp .6
471 467 .RS 4n
472 468 \fBzonepath\fR and its parent directory exist and are owned by root with
473 469 appropriate modes . The appropriate modes are that \fBzonepath\fR is \fB700\fR,
474 470 its parent is not \fBgroup\fR or \fBworld-writable\fR and so forth.
475 471 \fBzonepath\fR is not over an NFS mount. A sub-directory of the \fBzonepath\fR
476 472 named "root" does not exist.
477 473 .sp
478 474 If \fBzonepath\fR does not exist, the \fBverify\fR does not fail, but merely
479 475 warns that a subsequent install will attempt to create it with proper
480 476 permissions. A \fBverify\fR subsequent to that might fail should anything go
481 477 wrong.
482 478 .sp
483 479 \fBzonepath\fR cannot be a symbolic link.
484 480 .RE
485 481
486 482 .sp
487 483 .ne 2
488 484 .na
489 485 \fB\fBfs\fR\fR
490 486 .ad
491 487 .sp .6
492 488 .RS 4n
493 489 Any \fBfs\fR resources have their \fItype\fR value checked. An error is
494 490 reported if the value is one of \fBproc\fR, \fBmntfs\fR, \fBautofs\fR,
495 491 \fBcachefs\fR, or \fBnfs\fR or the filesystem does not have an associated mount
496 492 binary at \fB/usr/lib/fs/\fI<fstype>\fR/mount\fR.
497 493 .sp
498 494 It is an error for the \fIdirectory\fR to be a relative path.
499 495 .sp
500 496 It is an error for the path specified by \fBraw\fR to be a relative path or if
501 497 there is no \fBfsck\fR binary for a given filesystem type at
502 498 \fB/usr/lib/fs/\fI<fstype>\fR/fsck\fR. It is also an error if a corresponding
503 499 \fBfsck\fR binary exists but a \fBraw\fR path is not specified.
504 500 .RE
505 501
506 502 .sp
507 503 .ne 2
508 504 .na
509 505 \fB\fBnet\fR\fR
510 506 .ad
511 507 .sp .6
512 508 .RS 4n
513 509 All physical network interfaces exist. All network address resources are one
514 510 of:
515 511 .RS +4
516 512 .TP
517 513 .ie t \(bu
518 514 .el o
519 515 a valid IPv4 address, optionally followed by "\fB/\fR" and a prefix length;
520 516 .RE
521 517 .RS +4
522 518 .TP
523 519 .ie t \(bu
524 520 .el o
525 521 a valid IPv6 address, which must be followed by "\fB/\fR" and a prefix length;
526 522 .RE
527 523 .RS +4
528 524 .TP
529 525 .ie t \(bu
530 526 .el o
531 527 a host name which resolves to an IPv4 address.
532 528 .RE
533 529 Note that hostnames that resolve to IPv6 addresses are not supported.
534 530 .sp
535 531 The physical interface name is the network interface name.
536 532 .sp
537 533 A zone can be configured to be either exclusive-IP or shared-IP. For a
538 534 shared-IP zone, both the physical and address properties must be set. For an
539 535 exclusive-IP zone, the physical property must be set and the address property
540 536 cannot be set.
541 537 .RE
542 538
543 539 .sp
544 540 .ne 2
545 541 .na
546 542 \fB\fBrctl\fR\fR
547 543 .ad
548 544 .sp .6
549 545 .RS 4n
550 546 It also verifies that any defined resource control values are valid on the
551 547 current machine. This means that the privilege level is \fBprivileged\fR, the
552 548 limit is lower than the currently defined system value, and that the defined
553 549 action agrees with the actions that are valid for the given resource control.
554 550 .RE
555 551
556 552 .RE
557 553
558 554 .SH EXAMPLES
559 555 .LP
560 556 \fBExample 1 \fRUsing the \fB-m\fR Option
561 557 .sp
562 558 .LP
563 559 The following command illustrates the use of the \fB-m\fR option.
564 560
565 561 .sp
566 562 .in +2
567 563 .nf
568 564 # \fBzoneadm boot -- -m verbose\fR
569 565 .fi
570 566 .in -2
571 567 .sp
572 568
573 569 .LP
574 570 \fBExample 2 \fRUsing the \fB-i\fR Option
575 571 .sp
576 572 .LP
577 573 The following command illustrates the use of the \fB-i\fR option.
578 574
579 575 .sp
580 576 .in +2
581 577 .nf
582 578 # \fBzoneadm boot -- -i /sbin/init\fR
583 579 .fi
584 580 .in -2
585 581 .sp
586 582
587 583 .LP
588 584 \fBExample 3 \fRUsing the \fB-s\fR Option
589 585 .sp
590 586 .LP
591 587 The following command illustrates the use of the \fB-s\fR option.
|
↓ open down ↓ |
298 lines elided |
↑ open up ↑ |
592 588
593 589 .sp
594 590 .in +2
595 591 .nf
596 592 # \fBzoneadm boot -- -s\fR
597 593 .fi
598 594 .in -2
599 595 .sp
600 596
601 597 .SH EXIT STATUS
602 -.sp
603 598 .LP
604 599 The following exit values are returned:
605 600 .sp
606 601 .ne 2
607 602 .na
608 603 \fB\fB0\fR\fR
609 604 .ad
610 605 .sp .6
611 606 .RS 4n
612 607 Successful completion.
613 608 .RE
614 609
615 610 .sp
616 611 .ne 2
617 612 .na
618 613 \fB\fB1\fR\fR
619 614 .ad
620 615 .sp .6
621 616 .RS 4n
622 617 An error occurred.
623 618 .RE
624 619
625 620 .sp
|
↓ open down ↓ |
13 lines elided |
↑ open up ↑ |
626 621 .ne 2
627 622 .na
628 623 \fB\fB2\fR\fR
629 624 .ad
630 625 .sp .6
631 626 .RS 4n
632 627 Invalid usage.
633 628 .RE
634 629
635 630 .SH ATTRIBUTES
636 -.sp
637 631 .LP
638 632 See \fBattributes\fR(5) for descriptions of the following attributes:
639 633 .sp
640 634
641 635 .sp
642 636 .TS
643 637 box;
644 638 c | c
645 639 l | l .
646 640 ATTRIBUTE TYPE ATTRIBUTE VALUE
647 641 _
648 642 Interface Stability Committed
649 643 .TE
650 644
651 645 .SH SEE ALSO
652 -.sp
653 646 .LP
654 647 \fBread\fR(1), \fBsvcs\fR(1), \fBzlogin\fR(1), \fBzonename\fR(1),
655 648 \fBinit\fR(1M), \fBkernel\fR(1M), \fBsvcadm\fR(1M), \fBsvc.startd\fR(1M),
656 649 \fBsvc.startd\fR(1M), \fBzonecfg\fR(1M), \fBlibuuid\fR(3LIB),
657 650 \fBattributes\fR(5), \fBbrands\fR(5), \fBnative\fR(5), \fBsmf\fR(5),
658 651 \fBzones\fR(5)
659 652 .SH NOTES
660 -.sp
661 653 .LP
662 654 The \fBzones\fR(5) service is managed by the service management facility,
663 655 \fBsmf\fR(5), under the service identifier:
664 656 .sp
665 657 .in +2
666 658 .nf
667 659 svc:/system/zones:default
668 660 .fi
669 661 .in -2
670 662 .sp
671 663
672 664 .sp
673 665 .LP
674 666 Administrative actions on this service, such as enabling, disabling, or
675 667 requesting restart, can be performed using \fBsvcadm\fR(1M). The service's
676 668 status can be queried using the \fBsvcs\fR(1) command.
677 669 .sp
678 670 .LP
679 671 The act of installing a new non-global zone is a fresh installation of the
680 672 Solaris operating system. A new installation of Solaris must not require
681 673 interaction with the user (that is, it must be "hands off"). Because of this,
682 674 packages installed in the global zone and all non-global zones cannot contain
683 675 request scripts (see \fBpkgask\fR(1M)). If a package did have a request script,
684 676 then the creation of a non-global zone could not be done without user
685 677 intervention. Any package that contains a request script is added to the global
686 678 zone only. See \fBpkgadd\fR(1M).
|
↓ open down ↓ |
16 lines elided |
↑ open up ↑ |
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX