1 '\" te
2 .\" Copyright (c) 2004, 2009 Sun Microsystems, Inc. All Rights Reserved.
3 .\" Copyright 2013 Joyent, Inc. All Rights Reserved.
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 .\" 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 .\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH ZONECFG 1M "Feb 28, 2014"
8 .SH NAME
9 zonecfg \- set up zone configuration
10 .SH SYNOPSIS
11 .LP
12 .nf
13 \fBzonecfg\fR \fB-z\fR \fIzonename\fR
14 .fi
15
16 .LP
17 .nf
18 \fBzonecfg\fR \fB-z\fR \fIzonename\fR \fIsubcommand\fR
19 .fi
20
21 .LP
22 .nf
23 \fBzonecfg\fR \fB-z\fR \fIzonename\fR \fB-f\fR \fIcommand_file\fR
24 .fi
25
26 .LP
27 .nf
28 \fBzonecfg\fR help
29 .fi
30
31 .SH DESCRIPTION
32 .sp
33 .LP
34 The \fBzonecfg\fR utility creates and modifies the configuration of a zone.
35 Zone configuration consists of a number of resources and properties.
36 .sp
37 .LP
38 To simplify the user interface, \fBzonecfg\fR uses the concept of a scope. The
39 default scope is global.
40 .sp
41 .LP
42 The following synopsis of the \fBzonecfg\fR command is for interactive usage:
43 .sp
44 .in +2
45 .nf
46 zonecfg \fB-z\fR \fIzonename subcommand\fR
47 .fi
48 .in -2
49 .sp
50
51 .sp
52 .LP
55 .sp
56 .LP
57 In addition to creating and modifying a zone, the \fBzonecfg\fR utility can
58 also be used to persistently specify the resource management settings for the
59 global zone.
60 .sp
61 .LP
62 In the following text, "rctl" is used as an abbreviation for "resource
63 control". See \fBresource_controls\fR(5).
64 .sp
65 .LP
66 Every zone is configured with an associated brand. The brand determines the
67 user-level environment used within the zone, as well as various behaviors for
68 the zone when it is installed, boots, or is shutdown. Once a zone has been
69 installed the brand cannot be changed. The default brand is determined by the
70 installed distribution in the global zone. Some brands do not support all of
71 the \fBzonecfg\fR properties and resources. See the brand-specific man page for
72 more details on each brand. For an overview of brands, see the \fBbrands\fR(5)
73 man page.
74 .SS "Resources"
75 .sp
76 .LP
77 The following resource types are supported:
78 .sp
79 .ne 2
80 .na
81 \fB\fBattr\fR\fR
82 .ad
83 .sp .6
84 .RS 4n
85 Generic attribute.
86 .RE
87
88 .sp
89 .ne 2
90 .na
91 \fB\fBcapped-cpu\fR\fR
92 .ad
93 .sp .6
94 .RS 4n
95 Limits for CPU usage.
149 .ne 2
150 .na
151 \fB\fBnet\fR\fR
152 .ad
153 .sp .6
154 .RS 4n
155 Network interface.
156 .RE
157
158 .sp
159 .ne 2
160 .na
161 \fB\fBrctl\fR\fR
162 .ad
163 .sp .6
164 .RS 4n
165 Resource control.
166 .RE
167
168 .SS "Properties"
169 .sp
170 .LP
171 Each resource type has one or more properties. There are also some global
172 properties, that is, properties of the configuration as a whole, rather than of
173 some particular resource.
174 .sp
175 .LP
176 The following properties are supported:
177 .sp
178 .ne 2
179 .na
180 \fB(global)\fR
181 .ad
182 .sp .6
183 .RS 4n
184 \fBzonename\fR
185 .RE
186
187 .sp
188 .ne 2
189 .na
767 .RS 4n
768 The maximum amount of shared memory allowed for this zone. This property is the
769 preferred way to set the \fBzone.max-shm-memory\fR rctl. A scale (K, M, G, T)
770 can be applied to the value for this number (for example, 1M is one megabyte).
771 .RE
772
773 .sp
774 .ne 2
775 .na
776 \fBglobal: \fBscheduling-class\fR\fR
777 .ad
778 .sp .6
779 .RS 4n
780 Specifies the scheduling class used for processes running in a zone. When this
781 property is not specified, the scheduling class is established as follows:
782 .RS +4
783 .TP
784 .ie t \(bu
785 .el o
786 If the \fBcpu-shares\fR property or equivalent rctl is set, the scheduling
787 class FSS is used.
788 .RE
789 .RS +4
790 .TP
791 .ie t \(bu
792 .el o
793 If neither \fBcpu-shares\fR nor the equivalent rctl is set and the zone's pool
794 property references a pool that has a default scheduling class, that class is
795 used.
796 .RE
797 .RS +4
798 .TP
799 .ie t \(bu
800 .el o
801 Under any other conditions, the system default scheduling class is used.
802 .RE
803 .RE
804
805
806
807 .sp
808 .ne 2
809 .na
810 \fB\fBdedicated-cpu\fR: ncpus, importance\fR
811 .ad
812 .sp .6
813 .RS 4n
814 The number of CPUs that should be assigned for this zone's exclusive use. The
815 zone will create a pool and processor set when it boots. See \fBpooladm\fR(1M)
816 and \fBpoolcfg\fR(1M) for more information on resource pools. The \fBncpu\fR
817 property can specify a single value or a range (for example, 1-4) of
818 processors. The \fBimportance\fR property is optional; if set, it will specify
819 the \fBpset.importance\fR value for use by \fBpoold\fR(1M). If this resource is
820 used, there must be enough free processors to allocate to this zone when it
821 boots or the zone will not boot. The processors assigned to this zone will not
822 be available for the use of the global zone or other zones. This resource is
823 incompatible with both the \fBpool\fR and \fBcpu-shares\fR properties. Only a
824 single instance of this resource can be added to the zone.
825 .RE
826
927 swap simple with scale
928 locked simple with scale
929
930 capped-cpu ncpus simple
931 .fi
932 .in -2
933 .sp
934
935 .sp
936 .LP
937 To further specify things, the breakdown of the complex property "value" of the
938 "rctl" resource type, it consists of three name/value pairs, the names being
939 "priv", "limit" and "action", each of which takes a simple value. The "name"
940 property of an "attr" resource is syntactically restricted in a fashion similar
941 but not identical to zone names: it must begin with an alphanumeric, and can
942 contain alphanumerics plus the hyphen (\fB-\fR), underscore (\fB_\fR), and dot
943 (\fB\&.\fR) characters. Attribute names beginning with "zone" are reserved for
944 use by the system. Finally, the "autoboot" global property must have a value of
945 "true" or "false".
946 .SS "Using Kernel Statistics to Monitor CPU Caps"
947 .sp
948 .LP
949 Using the kernel statistics (\fBkstat\fR(3KSTAT)) module \fBcaps\fR, the system
950 maintains information for all capped projects and zones. You can access this
951 information by reading kernel statistics (\fBkstat\fR(3KSTAT)), specifying
952 \fBcaps\fR as the \fBkstat\fR module name. The following command displays
953 kernel statistics for all active CPU caps:
954 .sp
955 .in +2
956 .nf
957 # \fBkstat caps::'/cpucaps/'\fR
958 .fi
959 .in -2
960 .sp
961
962 .sp
963 .LP
964 A \fBkstat\fR(1M) command running in a zone displays only CPU caps relevant for
965 that zone and for projects in that zone. See \fBEXAMPLES\fR.
966 .sp
967 .LP
1080 .ad
1081 .sp .6
1082 .RS 4n
1083 The cap value, in terms of a percentage of a single CPU.
1084 .RE
1085
1086 .sp
1087 .ne 2
1088 .na
1089 \fB\fBzonename\fR\fR
1090 .ad
1091 .sp .6
1092 .RS 4n
1093 Name of the zone for which statistics are displayed.
1094 .RE
1095
1096 .sp
1097 .LP
1098 See \fBEXAMPLES\fR for sample output from a \fBkstat\fR command.
1099 .SH OPTIONS
1100 .sp
1101 .LP
1102 The following options are supported:
1103 .sp
1104 .ne 2
1105 .na
1106 \fB\fB-f\fR \fIcommand_file\fR\fR
1107 .ad
1108 .sp .6
1109 .RS 4n
1110 Specify the name of \fBzonecfg\fR command file. \fIcommand_file\fR is a text
1111 file of \fBzonecfg\fR subcommands, one per line.
1112 .RE
1113
1114 .sp
1115 .ne 2
1116 .na
1117 \fB\fB-z\fR \fIzonename\fR\fR
1118 .ad
1119 .sp .6
1120 .RS 4n
1121 Specify the name of a zone. Zone names are case sensitive. Zone names must
1122 begin with an alphanumeric character and can contain alphanumeric characters,
1123 the underscore (\fB_\fR) the hyphen (\fB-\fR), and the dot (\fB\&.\fR). The
1124 name \fBglobal\fR and all names beginning with \fBSUNW\fR are reserved and
1125 cannot be used.
1126 .RE
1127
1128 .SH SUBCOMMANDS
1129 .sp
1130 .LP
1131 You can use the \fBadd\fR and \fBselect\fR subcommands to select a specific
1132 resource, at which point the scope changes to that resource. The \fBend\fR and
1133 \fBcancel\fR subcommands are used to complete the resource specification, at
1134 which time the scope is reverted back to global. Certain subcommands, such as
1135 \fBadd\fR, \fBremove\fR and \fBset\fR, have different semantics in each scope.
1136 .sp
1137 .LP
1138 \fBzonecfg\fR supports a semicolon-separated list of subcommands. For example:
1139 .sp
1140 .in +2
1141 .nf
1142 # \fBzonecfg -z myzone "add net; set physical=myvnic; end"\fR
1143 .fi
1144 .in -2
1145 .sp
1146
1147 .sp
1148 .LP
1149 Subcommands which can result in destructive actions or loss of work have an
1786
1787 .LP
1788 \fBExample 11 \fRDisplaying CPU Caps for a Specific Zone or Project
1789 .sp
1790 .LP
1791 Using the \fBkstat\fR \fB-c\fR and \fB-i\fR options, you can display CPU caps
1792 for a specific zone or project, as below. The first command produces a display
1793 for a specific project, the second for the same project within zone 1.
1794
1795 .sp
1796 .in +2
1797 .nf
1798 # \fBkstat -c project_caps\fR
1799
1800 # \fBkstat -c project_caps -i 1\fR
1801 .fi
1802 .in -2
1803 .sp
1804
1805 .SH EXIT STATUS
1806 .sp
1807 .LP
1808 The following exit values are returned:
1809 .sp
1810 .ne 2
1811 .na
1812 \fB\fB0\fR\fR
1813 .ad
1814 .sp .6
1815 .RS 4n
1816 Successful completion.
1817 .RE
1818
1819 .sp
1820 .ne 2
1821 .na
1822 \fB\fB1\fR\fR
1823 .ad
1824 .sp .6
1825 .RS 4n
1826 An error occurred.
1827 .RE
1828
1829 .sp
1830 .ne 2
1831 .na
1832 \fB\fB2\fR\fR
1833 .ad
1834 .sp .6
1835 .RS 4n
1836 Invalid usage.
1837 .RE
1838
1839 .SH ATTRIBUTES
1840 .sp
1841 .LP
1842 See \fBattributes\fR(5) for descriptions of the following attributes:
1843 .sp
1844
1845 .sp
1846 .TS
1847 box;
1848 c | c
1849 l | l .
1850 ATTRIBUTE TYPE ATTRIBUTE VALUE
1851 _
1852 Interface Stability Volatile
1853 .TE
1854
1855 .SH SEE ALSO
1856 .sp
1857 .LP
1858 \fBppriv\fR(1), \fBprctl\fR(1), \fBzlogin\fR(1), \fBkstat\fR(1M),
1859 \fBmount\fR(1M), \fBpooladm\fR(1M), \fBpoolcfg\fR(1M), \fBpoold\fR(1M),
1860 \fBrcapd\fR(1M), \fBrctladm\fR(1M), \fBsvcadm\fR(1M), \fBsysidtool\fR(1M),
1861 \fBzfs\fR(1M), \fBzoneadm\fR(1M), \fBpriv_str_to_set\fR(3C),
1862 \fBkstat\fR(3KSTAT), \fBvfstab\fR(4), \fBattributes\fR(5), \fBbrands\fR(5),
1863 \fBfnmatch\fR(5), \fBlx\fR(5), \fBprivileges\fR(5), \fBresource_controls\fR(5),
1864 \fBzones\fR(5)
1865 .sp
1866 .LP
1867 \fISystem Administration Guide: Solaris Containers-Resource Management, and
1868 Solaris Zones\fR
1869 .SH NOTES
1870 .sp
1871 .LP
1872 All character data used by \fBzonecfg\fR must be in US-ASCII encoding.
|
1 '\" te
2 .\" Copyright (c) 2004, 2009 Sun Microsystems, Inc. All Rights Reserved.
3 .\" Copyright 2015 Joyent, Inc.
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 .\" 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 .\" fields enclosed by brackets "[]" replaced with your own identifying information: Portions Copyright [yyyy] [name of copyright owner]
7 .TH ZONECFG 1M "Nov 4, 2015"
8 .SH NAME
9 zonecfg \- set up zone configuration
10 .SH SYNOPSIS
11 .LP
12 .nf
13 \fBzonecfg\fR \fB-z\fR \fIzonename\fR
14 .fi
15
16 .LP
17 .nf
18 \fBzonecfg\fR \fB-z\fR \fIzonename\fR \fIsubcommand\fR
19 .fi
20
21 .LP
22 .nf
23 \fBzonecfg\fR \fB-z\fR \fIzonename\fR \fB-f\fR \fIcommand_file\fR
24 .fi
25
26 .LP
27 .nf
28 \fBzonecfg\fR help
29 .fi
30
31 .SH DESCRIPTION
32 .LP
33 The \fBzonecfg\fR utility creates and modifies the configuration of a zone.
34 Zone configuration consists of a number of resources and properties.
35 .sp
36 .LP
37 To simplify the user interface, \fBzonecfg\fR uses the concept of a scope. The
38 default scope is global.
39 .sp
40 .LP
41 The following synopsis of the \fBzonecfg\fR command is for interactive usage:
42 .sp
43 .in +2
44 .nf
45 zonecfg \fB-z\fR \fIzonename subcommand\fR
46 .fi
47 .in -2
48 .sp
49
50 .sp
51 .LP
54 .sp
55 .LP
56 In addition to creating and modifying a zone, the \fBzonecfg\fR utility can
57 also be used to persistently specify the resource management settings for the
58 global zone.
59 .sp
60 .LP
61 In the following text, "rctl" is used as an abbreviation for "resource
62 control". See \fBresource_controls\fR(5).
63 .sp
64 .LP
65 Every zone is configured with an associated brand. The brand determines the
66 user-level environment used within the zone, as well as various behaviors for
67 the zone when it is installed, boots, or is shutdown. Once a zone has been
68 installed the brand cannot be changed. The default brand is determined by the
69 installed distribution in the global zone. Some brands do not support all of
70 the \fBzonecfg\fR properties and resources. See the brand-specific man page for
71 more details on each brand. For an overview of brands, see the \fBbrands\fR(5)
72 man page.
73 .SS "Resources"
74 .LP
75 The following resource types are supported:
76 .sp
77 .ne 2
78 .na
79 \fB\fBattr\fR\fR
80 .ad
81 .sp .6
82 .RS 4n
83 Generic attribute.
84 .RE
85
86 .sp
87 .ne 2
88 .na
89 \fB\fBcapped-cpu\fR\fR
90 .ad
91 .sp .6
92 .RS 4n
93 Limits for CPU usage.
147 .ne 2
148 .na
149 \fB\fBnet\fR\fR
150 .ad
151 .sp .6
152 .RS 4n
153 Network interface.
154 .RE
155
156 .sp
157 .ne 2
158 .na
159 \fB\fBrctl\fR\fR
160 .ad
161 .sp .6
162 .RS 4n
163 Resource control.
164 .RE
165
166 .SS "Properties"
167 .LP
168 Each resource type has one or more properties. There are also some global
169 properties, that is, properties of the configuration as a whole, rather than of
170 some particular resource.
171 .sp
172 .LP
173 The following properties are supported:
174 .sp
175 .ne 2
176 .na
177 \fB(global)\fR
178 .ad
179 .sp .6
180 .RS 4n
181 \fBzonename\fR
182 .RE
183
184 .sp
185 .ne 2
186 .na
764 .RS 4n
765 The maximum amount of shared memory allowed for this zone. This property is the
766 preferred way to set the \fBzone.max-shm-memory\fR rctl. A scale (K, M, G, T)
767 can be applied to the value for this number (for example, 1M is one megabyte).
768 .RE
769
770 .sp
771 .ne 2
772 .na
773 \fBglobal: \fBscheduling-class\fR\fR
774 .ad
775 .sp .6
776 .RS 4n
777 Specifies the scheduling class used for processes running in a zone. When this
778 property is not specified, the scheduling class is established as follows:
779 .RS +4
780 .TP
781 .ie t \(bu
782 .el o
783 If the \fBcpu-shares\fR property or equivalent rctl is set, the scheduling
784 class \fBFSS\fR is used.
785 .RE
786 .RS +4
787 .TP
788 .ie t \(bu
789 .el o
790 If neither \fBcpu-shares\fR nor the equivalent rctl is set and the zone's pool
791 property references a pool that has a default scheduling class, that class is
792 used.
793 .RE
794 .RS +4
795 .TP
796 .ie t \(bu
797 .el o
798 Under any other conditions, the system default scheduling class is used.
799 .RE
800 .sp
801 If the \fBFX\fR scheduling class is specified, then the optional
802 \fBfixed-hi-pri\fR attribute can be set to \fBtrue\fR. This causes all of the
803 processes in the zone to run at the highest \fBFX\fR priority. By default
804 processes under \fBFX\fR run at the lowest priority. See \fBpriocntl\fR(2)
805 for details on each scheduling class.
806 .RE
807
808
809 .sp
810 .ne 2
811 .na
812 \fB\fBdedicated-cpu\fR: ncpus, importance\fR
813 .ad
814 .sp .6
815 .RS 4n
816 The number of CPUs that should be assigned for this zone's exclusive use. The
817 zone will create a pool and processor set when it boots. See \fBpooladm\fR(1M)
818 and \fBpoolcfg\fR(1M) for more information on resource pools. The \fBncpu\fR
819 property can specify a single value or a range (for example, 1-4) of
820 processors. The \fBimportance\fR property is optional; if set, it will specify
821 the \fBpset.importance\fR value for use by \fBpoold\fR(1M). If this resource is
822 used, there must be enough free processors to allocate to this zone when it
823 boots or the zone will not boot. The processors assigned to this zone will not
824 be available for the use of the global zone or other zones. This resource is
825 incompatible with both the \fBpool\fR and \fBcpu-shares\fR properties. Only a
826 single instance of this resource can be added to the zone.
827 .RE
828
929 swap simple with scale
930 locked simple with scale
931
932 capped-cpu ncpus simple
933 .fi
934 .in -2
935 .sp
936
937 .sp
938 .LP
939 To further specify things, the breakdown of the complex property "value" of the
940 "rctl" resource type, it consists of three name/value pairs, the names being
941 "priv", "limit" and "action", each of which takes a simple value. The "name"
942 property of an "attr" resource is syntactically restricted in a fashion similar
943 but not identical to zone names: it must begin with an alphanumeric, and can
944 contain alphanumerics plus the hyphen (\fB-\fR), underscore (\fB_\fR), and dot
945 (\fB\&.\fR) characters. Attribute names beginning with "zone" are reserved for
946 use by the system. Finally, the "autoboot" global property must have a value of
947 "true" or "false".
948 .SS "Using Kernel Statistics to Monitor CPU Caps"
949 .LP
950 Using the kernel statistics (\fBkstat\fR(3KSTAT)) module \fBcaps\fR, the system
951 maintains information for all capped projects and zones. You can access this
952 information by reading kernel statistics (\fBkstat\fR(3KSTAT)), specifying
953 \fBcaps\fR as the \fBkstat\fR module name. The following command displays
954 kernel statistics for all active CPU caps:
955 .sp
956 .in +2
957 .nf
958 # \fBkstat caps::'/cpucaps/'\fR
959 .fi
960 .in -2
961 .sp
962
963 .sp
964 .LP
965 A \fBkstat\fR(1M) command running in a zone displays only CPU caps relevant for
966 that zone and for projects in that zone. See \fBEXAMPLES\fR.
967 .sp
968 .LP
1081 .ad
1082 .sp .6
1083 .RS 4n
1084 The cap value, in terms of a percentage of a single CPU.
1085 .RE
1086
1087 .sp
1088 .ne 2
1089 .na
1090 \fB\fBzonename\fR\fR
1091 .ad
1092 .sp .6
1093 .RS 4n
1094 Name of the zone for which statistics are displayed.
1095 .RE
1096
1097 .sp
1098 .LP
1099 See \fBEXAMPLES\fR for sample output from a \fBkstat\fR command.
1100 .SH OPTIONS
1101 .LP
1102 The following options are supported:
1103 .sp
1104 .ne 2
1105 .na
1106 \fB\fB-f\fR \fIcommand_file\fR\fR
1107 .ad
1108 .sp .6
1109 .RS 4n
1110 Specify the name of \fBzonecfg\fR command file. \fIcommand_file\fR is a text
1111 file of \fBzonecfg\fR subcommands, one per line.
1112 .RE
1113
1114 .sp
1115 .ne 2
1116 .na
1117 \fB\fB-z\fR \fIzonename\fR\fR
1118 .ad
1119 .sp .6
1120 .RS 4n
1121 Specify the name of a zone. Zone names are case sensitive. Zone names must
1122 begin with an alphanumeric character and can contain alphanumeric characters,
1123 the underscore (\fB_\fR) the hyphen (\fB-\fR), and the dot (\fB\&.\fR). The
1124 name \fBglobal\fR and all names beginning with \fBSUNW\fR are reserved and
1125 cannot be used.
1126 .RE
1127
1128 .SH SUBCOMMANDS
1129 .LP
1130 You can use the \fBadd\fR and \fBselect\fR subcommands to select a specific
1131 resource, at which point the scope changes to that resource. The \fBend\fR and
1132 \fBcancel\fR subcommands are used to complete the resource specification, at
1133 which time the scope is reverted back to global. Certain subcommands, such as
1134 \fBadd\fR, \fBremove\fR and \fBset\fR, have different semantics in each scope.
1135 .sp
1136 .LP
1137 \fBzonecfg\fR supports a semicolon-separated list of subcommands. For example:
1138 .sp
1139 .in +2
1140 .nf
1141 # \fBzonecfg -z myzone "add net; set physical=myvnic; end"\fR
1142 .fi
1143 .in -2
1144 .sp
1145
1146 .sp
1147 .LP
1148 Subcommands which can result in destructive actions or loss of work have an
1785
1786 .LP
1787 \fBExample 11 \fRDisplaying CPU Caps for a Specific Zone or Project
1788 .sp
1789 .LP
1790 Using the \fBkstat\fR \fB-c\fR and \fB-i\fR options, you can display CPU caps
1791 for a specific zone or project, as below. The first command produces a display
1792 for a specific project, the second for the same project within zone 1.
1793
1794 .sp
1795 .in +2
1796 .nf
1797 # \fBkstat -c project_caps\fR
1798
1799 # \fBkstat -c project_caps -i 1\fR
1800 .fi
1801 .in -2
1802 .sp
1803
1804 .SH EXIT STATUS
1805 .LP
1806 The following exit values are returned:
1807 .sp
1808 .ne 2
1809 .na
1810 \fB\fB0\fR\fR
1811 .ad
1812 .sp .6
1813 .RS 4n
1814 Successful completion.
1815 .RE
1816
1817 .sp
1818 .ne 2
1819 .na
1820 \fB\fB1\fR\fR
1821 .ad
1822 .sp .6
1823 .RS 4n
1824 An error occurred.
1825 .RE
1826
1827 .sp
1828 .ne 2
1829 .na
1830 \fB\fB2\fR\fR
1831 .ad
1832 .sp .6
1833 .RS 4n
1834 Invalid usage.
1835 .RE
1836
1837 .SH ATTRIBUTES
1838 .LP
1839 See \fBattributes\fR(5) for descriptions of the following attributes:
1840 .sp
1841
1842 .sp
1843 .TS
1844 box;
1845 c | c
1846 l | l .
1847 ATTRIBUTE TYPE ATTRIBUTE VALUE
1848 _
1849 Interface Stability Volatile
1850 .TE
1851
1852 .SH SEE ALSO
1853 .LP
1854 \fBppriv\fR(1), \fBprctl\fR(1), \fBzlogin\fR(1), \fBkstat\fR(1M),
1855 \fBmount\fR(1M), \fBpooladm\fR(1M), \fBpoolcfg\fR(1M), \fBpoold\fR(1M),
1856 \fBrcapd\fR(1M), \fBrctladm\fR(1M), \fBsvcadm\fR(1M), \fBsysidtool\fR(1M),
1857 \fBzfs\fR(1M), \fBzoneadm\fR(1M), \fBpriocntl\fR(2), \fBpriv_str_to_set\fR(3C),
1858 \fBkstat\fR(3KSTAT), \fBvfstab\fR(4), \fBattributes\fR(5), \fBbrands\fR(5),
1859 \fBfnmatch\fR(5), \fBlx\fR(5), \fBprivileges\fR(5), \fBresource_controls\fR(5),
1860 \fBzones\fR(5)
1861 .sp
1862 .LP
1863 \fISystem Administration Guide: Solaris Containers-Resource Management, and
1864 Solaris Zones\fR
1865 .SH NOTES
1866 .LP
1867 All character data used by \fBzonecfg\fR must be in US-ASCII encoding.
|