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