| /illumos-gate/usr/src/man/man8/ |
| H A D | vscanadm.8 | 65 The \fBvscanadm\fR command sets and displays properties of the \fBvscan\fR
83 The \fBvscan\fR service properties are divided into two categories: scan engine
84 properties, which are specific to a scan engine definition, and general
85 properties, which apply to the service and are not scan engine-specific.
96 Sets the values of \fBvscan\fR service general properties.
115 Displays the values of \fBvscan\fR service general properties. If no properties
116 are specified, all \fBvscan\fR service general properties are displayed.
130 The following properties are available for the \fBvscanadm set\fR and
225 The following properties are available for the \fBvscanadm import\fR,
269 used for any scan engine properties that are not specified. The hostname
[all …]
|
| H A D | svccfg.8 | 136 is a service profile, properties, including general/enabled, that are specified
138 Not-yet-existent properties and property groups will be created.
140 Existing properties
158 This command requires privileges to modify properties in the service and
162 for the privileges required to modify properties.
175 persistent properties in the repository.
176 This does not include transient properties such as service state, and is
255 For existing services and instances, properties which have not changed since
259 .Pq properties which have been changed both in the repository and the manifest
266 properties,
[all …]
|
| H A D | flowadm.8 | 72 properties.
130 An optional comma-separated list of properties to be set to the specified
131 values. Flow properties are documented in the "Flow Properties" section, below.
316 Set values of one or more properties on the flow specified by name. The
317 complete list of properties can be retrieved using the \fBshow-flowprop\fR
338 persistent setting of properties.
348 A comma-separated list of properties to be set to the specified values.
361 Resets one or more properties to their default values on the specified flow. If
362 no properties are specified, all properties are reset. See the
363 \fBshow-flowprop\fR subcommand for a description of properties, which includes
[all …]
|
| H A D | devprop.8 | 8 devprop \- display device properties
18 The \fBdevprop\fR command displays named device properties from the device
23 device properties for that device node.
39 The properties to be output are sequences of bytes (\fBDI_PROP_TYPE_BYTES\fR).
51 The properties to be output are integers (\fBDI_PROP_TYPE_INT\fR).
61 The properties to be output are 64-bit integers (\fBDI_PROP_TYPE_INT64\fR).
71 The properties to be output are strings (\fBDI_PROP_TYPE_STRING\fR) (the
82 The path to a target device node for which properties are displayed. The
94 Specifies quoted output mode, in which string properties are output surrounded
|
| H A D | inetadm.8 | 64 Lists the services' properties and values.
135 List all properties for the specified service instances as
139 properties do not have a specified service instance default.
169 Change the values of the specified properties of the identified service
170 instances. Properties are specified as whitespace-separated
183 Change the values of the specified \fBinetd\fR default properties. Properties
189 \fBExample 1 \fRDisplaying Properties for a Service
192 The following command displays the properties for the \fBspray\fR service.
224 \fBExample 2 \fRDisplaying Default Properties
227 The following command displays default properties.
|
| H A D | zfs.8 | 372 unmounting, taking snapshots, and setting properties.
487 The physical properties of an added file system are controlled by the global
497 The zone administrator can change properties of the dataset or any of its
504 properties of the delegated dataset can be modified only by the global
510 However, its physical properties can be modified only by the global
529 .Ss Native Properties
530 Properties are divided into two types, native properties and user-defined
534 properties.
535 Native properties either export internal statistics or control ZFS behavior.
536 In addition, native properties are either editable or read-only.
[all …]
|
| /illumos-gate/usr/src/man/man1/ |
| H A D | svcprop.1 | 9 svcprop \- retrieve values of service configuration properties
23 The \fBsvcprop\fR utility prints values of properties in the service
24 configuration repository. Properties are selected by \fB-p\fR options and the
29 effective properties. The effective properties of a service are its directly
30 attached properties. The effective properties of a service instance are the
31 union of properties in the composed view of its \fBrunning\fR snapshot and the
32 properties in nonpersistent property groups in the composed view of the
33 instance's directly attached properties. See \fBsmf\fR(7) for an explanation of
35 instance's directly attached properties are used instead.
45 When multiple properties are selected, a single line is printed for each. Each
[all …]
|
| /illumos-gate/usr/src/man/man7/ |
| H A D | overlay.7 | 85 .Sx Plugins and their Properties .
115 .Sx Plugins and their Properties .
129 .Sh PLUGINS AND PROPERTIES
130 Properties fall into three categories in the system:
133 Generic properties all overlay devices have
135 Properties specific to the encapsulation plugin
137 Properties specific to the search plugin
143 link properties:
151 Properties that are valid for all overlay devices and not specific to a
189 the system considers them read-only properties or read-write properties.
[all …]
|
| H A D | smf_security.7 | 26 properties, and to read protected property values.
31 The \fBsmf\fR(7) configuration subsystem associates properties with each
32 service and service instance. Related properties are grouped. Groups can
97 properties, and to read protected property values.
102 Property group-specific authorization can be specified by properties contained
110 Authorizations allow the addition, deletion, or modification of properties
140 The above authorization properties are only used if they have type
142 properties, but the instance's service has a property group of the same name
148 store properties with values that require protection. They must not be revealed
151 If this property is present, the values of all properties in the property group
|
| /illumos-gate/usr/src/man/man9f/ |
| H A D | ddi_prop_op.9f | 112 do not look at PROM properties (ignored on architectures that do not support
113 PROM properties)
160 The \fBddi_prop_op()\fR function gets arbitrary-size properties for leaf
178 the property search order which is to first search software properties created
180 properties created by the \fIsystem\fR in LIFO order, then search PROM
181 properties if they exist in the system architecture.
188 this case. Property lengths are \fB0\fR for boolean properties,
189 \fBsizeof\|(int)\fR for integer properties, and size in bytes for long
190 (variable size) properties.
217 The \fBddi_getprop()\fR function returns boolean and integer-size properties.
[all …]
|
| H A D | ddi_prop_exists.9f | 64 Do not look at \fBPROM \fRproperties (ignored on platforms that do not support
65 \fBPROM \fRproperties).
84 Properties are searched for based on the \fIdip\fR, \fIname\fR, and
89 Search software properties created by the driver.
94 Search the software properties created by the system (or nexus nodes in the
100 Search the driver global properties list.
105 If \fBDDI_PROP_NOTPROM\fR is not set, search the \fBPROM \fRproperties (if
128 \fBDDI_DEV_T_ANY.\fR \fBPROM \fRproperties are always created with
|
| H A D | ddi_prop_get_int.9f | 67 Do not look at \fBPROM \fRproperties (ignored on platforms that do not support
68 \fBPROM \fRproperties).
98 Properties are searched for based on the \fIdip\fR, \fIname\fR,
104 Search software properties created by the driver.
109 Search the software properties created by the system (or nexus nodes in the
115 Search the driver global properties list.
120 If \fBDDI_PROP_NOTPROM\fR is not set, search the \fBPROM \fRproperties (if
143 \fRproperties are always created with \fImatch_dev\fR set to
|
| H A D | ldi_prop_exists.9f | 64 Do not look at PROM properties (ignored on platforms that do not support PROM
65 properties).
83 Properties are searched for based on the dip and dev_t values associated with
93 Search software-properties created by the driver.
98 Search the software properties created by the system (or nexus nodes in the
104 Search the driver global properties list.
109 If DDI_PROP_NOTPROM is not set, search the PROM properties (if they exist).
134 LDI_DEV_T_ANY flag. PROM properties are always created with a dev_t set to
|
| H A D | mac_prop_info.9f | 83 .Sy PROPERTIES
93 .Sy PROPERTIES
150 For the most case, properties will only take one of two values:
192 and some are used for specific properties.
195 function works with properties that describe flow control properties.
203 function sets the default value for properties that use strings.
212 functions set the default value for values whose properties are 8-, 16-,
217 function is used for properties that describe link forward error
|
| /illumos-gate/usr/src/man/man9e/ |
| H A D | mc_propinfo.9e | 64 to give users and administrators of the system access to the properties of the
70 The set of possible properties and their meaning is listed in the
71 .Sy PROPERTIES
94 on it, comparing it to each of its private properties to identify which
114 of the auto-negotiation properties.
126 These are used for integer properties such as
148 unsupported and unknown properties.
194 * The ADV properties represent things that the device supports and
195 * can't be changed by the user. These are good examples of properties
215 * The EN properties represent the speeds advertised by the driver. On
[all …]
|
| /illumos-gate/usr/src/test/zfs-tests/tests/functional/cli_root/zfs_receive/ |
| H A D | zfs_receive_014_pos.ksh | 26 # Verify ZFS successfully receive and restore properties.
30 # 2. Create a full stream with properties and receive it.
31 # 3. Create also an incremental stream without some properties and a truncated
34 # received properties are still present.
36 # properties are successfully received.
83 log_assert "ZFS successfully receive and restore properties."
90 # 2. Create a full stream with properties and receive it.
99 # 3. Create also an incremental stream without some properties and a truncated
111 # received properties are still present.
117 # properties are successfully received.
[all …]
|
| H A D | zfs_receive_015_pos.ksh | 26 # Verify ZFS can receive custom properties on both filesystems and
32 # 3. Set custom properties on both the fs and snapshots.
33 # 4. Create different send streams with the properties.
34 # 5. Receive the send streams and verify the properties.
54 log_assert "ZFS can receive custom properties."
65 # 3. Set custom properties on both the fs and snapshots.
71 # 4. Create different send streams with the properties.
75 # 5. Receive the send streams and verify the properties.
83 log_pass "ZFS can receive custom properties passed."
|
| H A D | receive-o-x_props_override.ksh | 33 # we can both override and exclude native and user properties.
89 # 3.2 Verify -o property=value works on streams without properties.
95 # Receive the full stream, override some properties
105 # 3.3 Verify -o property=value and -x work on both native and user properties
114 # Fill the datasets with properties and create an incremental replication stream
127 # Verify we can correctly override and exclude properties
150 # 3.4 Verify '-x property' does not remove existing local properties and a
167 # Set new custom properties on both source and destination
173 # Receive the new stream, verify we preserve locally set properties
195 # 3.5 Verify we can exclude non-inheritable properties from a send stream
[all …]
|
| /illumos-gate/usr/src/lib/libsecdb/ |
| H A D | auth_attr.txt | 111 solaris.smf.modify.:::Modify All SMF Service Properties::help=SmfModifyHeader.html
114 solaris.smf.modify.application:::Modify Application Type Properties::help=SmfModifyAppl.html
115 solaris.smf.modify.framework:::Modify Framework Type Properties::help=SmfModifyFramework.html
158 solaris.smf.value.:::Change Values of SMF Service Properties::help=SmfValueHeader.html
160 solaris.smf.value.coreadm:::Change Values of SMF Coreadm Properties::help=SmfValueCoreadm.html
161 …overy.printers.snmp:::Manage Network Attached Device Discovery Service Properties::help=SmfValueNA…
162 …ed-accounting.flow:::Change Values of Flow Extended Accounting Service Properties::help=SmfValueEx…
163 …ounting.process:::Change Values of Process Extended Accounting Service Properties::help=SmfValueEx…
164 …ed-accounting.task:::Change Values of Task Extended Accounting Service Properties::help=SmfValueEx…
166 solaris.smf.value.idmap:::Change Values of SMF Identity Mapping Service Properties::help=SmfValueId…
[all …]
|
| /illumos-gate/usr/src/test/zfs-tests/tests/functional/cli_root/zpool_get/ |
| H A D | zpool_get_003_pos.ksh | 38 # Zpool get returns values for all known properties
41 # 1. For all properties, verify zpool get retrieves a value
44 log_assert "Zpool get returns values for all known properties"
52 while [ $i -lt "${#properties[@]}" ]
54 log_note "Checking for ${properties[$i]} property"
55 log_must eval "zpool get ${properties[$i]} $TESTPOOL > /tmp/value.$$"
56 grep "${properties[$i]}" /tmp/value.$$ > /dev/null 2>&1
59 log_fail "${properties[$i]} not seen in output"
71 log_pass "Zpool get returns values for all known properties"
|
| /illumos-gate/usr/src/cmd/hal/hald/ |
| H A D | device.c | 69 g_slist_foreach (device->properties, (GFunc) hal_property_free, NULL); in hal_device_finalize()
71 g_slist_free (device->properties); in hal_device_finalize()
185 /** Merge all properties from source where the key starts with
189 * @param target Device to put properties onto
190 * @param source Device to retrieve properties from
209 for (iter = source->properties; iter != NULL; iter = iter->next) { in hal_device_merge_with_rewrite()
218 /* only care about properties that match source namespace */ in hal_device_merge_with_rewrite()
284 for (iter = source->properties; iter != NULL; iter = iter->next) { in hal_device_merge()
358 for (iter = device1->properties; iter != NULL; iter = iter->next) { in hal_device_matches()
472 return g_slist_length (device->properties); in hal_device_num_properties()
[all …]
|
| /illumos-gate/usr/src/test/zfs-tests/tests/functional/cli_root/zfs_send/ |
| H A D | zfs_send-b.ksh | 25 # 1. Create a source dataset and set some properties
27 # 3. Send the dataset and its properties to a new "backup" destination
28 # 4. Set some properties on the new "backup" dataset
30 # 6. Verify only original (received) properties are sent from "backup"
49 # 1. Create a source dataset and set some properties
74 # 3. Send the dataset and its properties to a new "backup" destination
75 # NOTE: only need to send properties (-p) here
78 # 4. Set some properties on the new "backup" dataset
79 # NOTE: override "received" values and set some new properties as well
90 # 6. Verify only original (received) properties are sent from "backup"
|
| /illumos-gate/usr/src/lib/scsi/plugins/ses/ses2/common/ |
| H A D | ses2.h | 34 * Node properties
140 * Audible Alarm properties
151 * Nonvolatile Cache properties
156 * Cooling Element properties
172 * Device/Array Device properties
204 * Display Element properties
224 * Current Sensor properties
229 * Door Lock properties
234 * SCSI Initiator or Target Port properties
239 * Language Module properties
[all …]
|
| /illumos-gate/usr/src/lib/fm/topo/modules/common/zen/ |
| H A D | topo_zen.h | 43 * Property groups and their corresponding properties. The properties listed
57 #define TOPO_PGROUP_CCD "ccd-properties"
61 #define TOPO_PGROUP_CCX "ccx-properties"
65 #define TOPO_PGROUP_CORE "core-properties"
74 #define TOPO_PGROUP_STRAND "strand-properties"
79 * These chip properties are loosely shared with the i86pc chip module. They're
82 #define TOPO_PGROUP_CHIP "chip-properties"
|
| /illumos-gate/usr/src/uts/common/io/bge/ |
| H A D | bge.conf | 29 # All the properties below can be set globally (i.e. for all instances
31 # of the syntax of global and per-instance properties.
33 # Properties specified in this file take effect when the driver is first
44 # The autonegotiation feature can be controlled by the boolean properties
50 # speed/duplex properties force selection of a specific mode, namely,
69 # properties control which capabilities are advertised to the partner.
71 # supports; thus, the properties below serve only to limit the advertised
122 # parameters corresponding to the properties above.
128 # As a third alternative, the following two properties can be set to
131 # properties above, and take precedence over all other means of setting
[all …]
|