160
161 # zoneadm -z my-zone detach
162
163
164 The source zone must be halted before this subcommand can be used.
165
166
167 halt
168 Halt the specified zones. halt bypasses running the shutdown
169 scripts inside the zone. It also removes run time resources of the
170 zone.
171
172
173 help [subcommand]
174 Display general help. If you specify subcommand, displays help on
175 subcommand.
176
177
178 install [-x nodataset] [brand-specific options]
179 Install the specified zone on the system. This subcommand
180 automatically attempts to verify first. It refuses to install if
181 the verify step fails. See the verify subcommand.
182
183 -x nodataset
184 Do not create a ZFS file system.
185
186 The zone's brand may include additional options that govern how the
187 software will be installed in the zone. See brands(5) for specific
188 brand information.
189
190
191 list [list_options]
192 Display the name of the current zones, or the specified zone if
193 indicated.
194
195 By default, all running zones are listed. If you use this
196 subcommand with the zoneadm -z zonename option, it lists only the
197 specified zone, regardless of its state. In this case, the -i and -c
198 options are disallowed.
199
200 If neither the -i or -c options are given, all running zones are
201 listed.
417
418
419
420 Administrative actions on this service, such as enabling, disabling, or
421 requesting restart, can be performed using svcadm(1M). The service's
422 status can be queried using the svcs(1) command.
423
424
425 The act of installing a new non-global zone is a fresh installation of
426 the Solaris operating system. A new installation of Solaris must not
427 require interaction with the user (that is, it must be "hands off").
428 Because of this, packages installed in the global zone and all non-
429 global zones cannot contain request scripts (see pkgask(1M)). If a
430 package did have a request script, then the creation of a non-global
431 zone could not be done without user intervention. Any package that
432 contains a request script is added to the global zone only. See
433 pkgadd(1M).
434
435
436
437 October 30, 2013 ZONEADM(1M)
|
160
161 # zoneadm -z my-zone detach
162
163
164 The source zone must be halted before this subcommand can be used.
165
166
167 halt
168 Halt the specified zones. halt bypasses running the shutdown
169 scripts inside the zone. It also removes run time resources of the
170 zone.
171
172
173 help [subcommand]
174 Display general help. If you specify subcommand, displays help on
175 subcommand.
176
177
178 install [-x nodataset] [brand-specific options]
179 Install the specified zone on the system. This subcommand
180 automatically attempts to verify first, most verification errors
181 are fatal. See the verify subcommand.
182
183 -x nodataset
184 Do not create a ZFS file system.
185
186 The zone's brand may include additional options that govern how the
187 software will be installed in the zone. See brands(5) for specific
188 brand information.
189
190
191 list [list_options]
192 Display the name of the current zones, or the specified zone if
193 indicated.
194
195 By default, all running zones are listed. If you use this
196 subcommand with the zoneadm -z zonename option, it lists only the
197 specified zone, regardless of its state. In this case, the -i and -c
198 options are disallowed.
199
200 If neither the -i or -c options are given, all running zones are
201 listed.
417
418
419
420 Administrative actions on this service, such as enabling, disabling, or
421 requesting restart, can be performed using svcadm(1M). The service's
422 status can be queried using the svcs(1) command.
423
424
425 The act of installing a new non-global zone is a fresh installation of
426 the Solaris operating system. A new installation of Solaris must not
427 require interaction with the user (that is, it must be "hands off").
428 Because of this, packages installed in the global zone and all non-
429 global zones cannot contain request scripts (see pkgask(1M)). If a
430 package did have a request script, then the creation of a non-global
431 zone could not be done without user intervention. Any package that
432 contains a request script is added to the global zone only. See
433 pkgadd(1M).
434
435
436
437 December 26, 2014 ZONEADM(1M)
|