mtpti5iD/redhat-docs_dataset huggingface dataset:
3.5. Array Operations in SystemTap This section enumerates some of the most commonly used array operations in SystemTap. 3.5.1. Assigning an Associated Value Use = to set an associated value to indexed unique pairs, as in: Example 3.11, "Basic Array Statements" shows a very basic example of how to set an explicit associated value to a unique key. You can also use a handler function as both your index_expression and value . For example, you can use arrays to set a timestamp as the associated value to a process name (which you wish to use as your unique key), as in: Example 3.12. Associating Timestamps to Process Names Whenever an event invokes the statement in Example 3.12, "Associating Timestamps to Process Names" , SystemTap returns the appropriate tid() value (that is the ID of a thread, which is then used as the unique key). At the same time, SystemTap also uses the function gettimeofday_s() to set the corresponding timestamp as the associated value to the unique key defined by the function tid() . This creates an array composed of key pairs containing thread IDs and timestamps. In this same example, if tid() returns a value that is already defined in the array foo , the operator will discard the original associated value to it, and replace it with the current timestamp from gettimeofday_s() .

Commands:
array_name [ index_expression ] = value
foo[tid()] = gettimeofday_s()
21.3. Creating Netgroups 21.3.1. Adding a Netgroup To add a Netgroup, you can use: the IdM web UI (see the section called "Web UI: Adding a Netgroup" ) the command line (see the section called "Command Line: Adding a Netgroup" ) Web UI: Adding a Netgroup Select Identity Groups Netgroups Click Add . Enter a unique name and, optionally, a description. The group name is the identifier used for the netgroup in the IdM domain. You cannot change it later. Click Add and Edit to save the changes and to start editing the entry. The default NIS domain is set to the IdM domain name. Optionally, you can enter the name of the alternative NIS domain in the NIS domain name field. Figure 21.1. Netgroup Tab The NIS domain name field sets the domain that appears in the netgroup triple. It does not affect which NIS domain the Identity Management NIS listener responds to. Add members, as described in the section called "Web UI: Adding Members to a Netgroup" . Click Save . Command Line: Adding a Netgroup You can add a new netgroup using the ipa netgroup-add command. Specify: the group name. optionally, a description. optionally, the NIS domain name if it is different than the IdM domain name. Note The --nisdomain option sets the domain that appears in the netgroup triple. It does not affect which NIS domain the Identity Management listener responds to. For example: To add members to the netgroup, see the section called "Command Line: Adding Members to a Netgroup" . 21.3.2. Adding Members to a Netgroup Beside users and hosts, netgroups can contain user groups, host groups, and other netgroups (nested groups) as members. Depending on the size of a group, it can take up to several minutes after you create a nested groups for the members of the child group to show up as members of the parent group. To add members to a Netgroup, you can use: the IdM web UI (see the section called "Web UI: Adding Members to a Netgroup" ) the command line (see the section called "Command Line: Adding Members to a Netgroup" ) Warning Do not create recursive nested groups. For example, if GroupA is a member of GroupB , do not add GroupB as a member of GroupA . Recursive groups are not supported and can cause unpredictable behavior. Web UI: Adding Members to a Netgroup To add members to a netgroup using the Web UI: Select Identity Groups Netgroups Click the name of the netgroup to which to add members. Click Add to the required member type. Figure 21.2. User Menu in the Netgroup Tab Select the members you want to add, and click > to confirm. Figure 21.3. Add User Menu in the Netgroup Tab Click Add . Command Line: Adding Members to a Netgroup After you created the netgroup, you can add members using the ipa netgroup-add-member command: To set more than one member, use a comma-separated list inside a set of curly braces. For example:

Commands:
ipa netgroup-add --desc="Netgroup description" --nisdomain="example.com" example-netgroup
ipa netgroup-add-member --users= user_name --groups= group_name --hosts= host_name --hostgroups= host_group_name --netgroups= netgroup_name group_nameame
ipa netgroup-add-member --users={user1;user2,user3} --groups={group1,group2} example-group
Chapter 23. Storage I/O Alignment and Size Recent enhancements to the SCSI and ATA standards allow storage devices to indicate their preferred (and in some cases, required) I/O alignment and I/O size . This information is particularly useful with newer disk drives that increase the physical sector size from 512 bytes to 4k bytes. This information may also be beneficial for RAID devices, where the chunk size and stripe size may impact performance. The Linux I/O stack has been enhanced to process vendor-provided I/O alignment and I/O size information, allowing storage management tools ( parted , lvm , mkfs. * , and the like) to optimize data placement and access. If a legacy device does not export I/O alignment and size data, then storage management tools in Red Hat Enterprise Linux 6 will conservatively align I/O on a 4k (or larger power of 2) boundary. This will ensure that 4k-sector devices operate correctly even if they do not indicate any required/preferred I/O alignment and size. Refer to Section 23.2, "Userspace Access" to learn how to determine the information that the operating system obtained from the device. This data is subsequently used by the storage management tools to determine data placement. The IO scheduler has changed for Red Hat Enterprise Linux 7. Default IO Scheduler is now Deadline , except for SATA drives. CFQ is the default IO scheduler for SATA drives. For faster storage, Deadline outperforms CFQ and when it is used there is a performance increase without the need of special tuning. If default is not right for some disks (for example, SAS rotational disks), then change the IO scheduler to CFQ. This instance will depend on the workload. 23.1. Parameters for Storage Access The operating system uses the following information to determine I/O alignment and size: physical_block_size Smallest internal unit on which the device can operate logical_block_size Used externally to address a location on the device alignment_offset The number of bytes that the beginning of the Linux block device (partition/MD/LVM device) is offset from the underlying physical alignment minimum_io_size The device's preferred minimum unit for random I/O optimal_io_size The device's preferred unit for streaming I/O For example, certain 4K sector devices may use a 4K physical_block_size internally but expose a more granular 512-byte logical_block_size to Linux. This discrepancy introduces potential for misaligned I/O. To address this, the Red Hat Enterprise Linux 6 I/O stack will attempt to start all data areas on a naturally-aligned boundary ( physical_block_size ) by making sure it accounts for any alignment_offset if the beginning of the block device is offset from the underlying physical alignment. Storage vendors can also supply I/O hints about the preferred minimum unit for random I/O ( minimum_io_size ) and streaming I/O ( optimal_io_size ) of a device. For example, minimum_io_size and optimal_io_size may correspond to a RAID device's chunk size and stripe size respectively.

Commands:
5.5. Stopping firewalld To stop firewalld , enter the following command as root : To prevent firewalld from starting automatically at system start, enter the following command as root : To make sure firewalld is not started by accessing the firewalld D-Bus interface and also if other services require firewalld , enter the following command as root :

Commands:
~]# systemctl stop firewalld
~]# systemctl disable firewalld
~]# systemctl mask firewalld
Chapter 3. Prerequisites Before you can install and register Red Hat Satellite and Capsule, you must set up accounts with Amazon Web Services (AWS) and create and start Red Hat Enterprise Linux instances on AWS. 3.1. Amazon Web Service Assumptions To use this guide, you must have a working knowledge of the following aspects of Amazon Web Services: Creating and accessing Red Hat Enterprise Linux images in AWS Editing network access in AWS Security Creating EC2 instances and how to create EBS volumes Launching instances Importing and exporting virtual machines in AWS Using AWS Direct Connect To install Satellite in an AWS environment, you must ensure that your AWS set up meets the System Requirements in Installing Satellite Server in a connected network environment . To install Capsule in an AWS environment, you must ensure that your AWS set up meets the System Requirements in Installing Capsule Server . For more information about Amazon Web Services and terminology, see Amazon Elastic Compute Cloud Documentation . For more information about Amazon Web Services Direct Connect, see What is AWS Direct Connect? 3.2. Red Hat Cloud prerequisites To use this guide, you must complete the following steps: Register with Red Hat Cloud Access. Migrate any Red Hat subscriptions that you want to use. Create an AWS instance and deploy a Red Hat Enterprise Linux virtual machine to the instance. Ensure that your subscriptions are eligible for transfer to Red Hat Cloud. For more information, see Red Hat Cloud Access Program Details . For more information about deploying Red Hat Enterprise Linux in AWS, see How to Locate Red Hat Cloud Access Gold Images on AWS EC2 . 3.3. Red Hat Satellite-specific prerequisites Ensure that the Amazon EC2 instance type meets or exceeds the System Requirements in Installing Satellite Server in a connected network environment . For the best performance, use an AWS storage optimized instance . Use Storage Requirements in Installing Satellite Server in a connected network environment to understand and assign the correct storage to your AWS EBS volumes. Store the synced content on an EBS volume that is separate to the boot volume. Mount the synced content EBS volume separately in the operating system. Optional: Store other data on a separate EBS volume. If you want Satellite Server and Capsule Server to communicate using external DNS hostnames, open the required ports for communication in the AWS Security Group that is associated with the instance. 3.4. Preparing for the Red Hat Satellite Installation In your AWS environment, complete the following steps: Launch an EC2 instance of a Red Hat Enterprise Linux AMI. Connect to the newly created instance. If you use a Red Hat Gold Image, remove the RHUI client and set the enabled parameter in the product-id.conf to 1 .

Commands:
dnf remove -y rh-amazon-rhui-client* dnf clean all cat << EOF > /etc/yum/pluginconf.d/product-id.conf > [main] > enabled=1 > EOF
6.4.2.3. Moving the Data Use the pvmove command to move the data from /dev/sdb1 to /dev/sdd1 .

Commands:
pvmove /dev/sdb1 /dev/sdd1 /dev/sdb1: Moved: 10.0% /dev/sdb1: Moved: 79.7% /dev/sdb1: Moved: 100.0% pvs -o+pv_used PV VG Fmt Attr PSize PFree Used /dev/sda1 myvg lvm2 a- 17.15G 7.15G 10.00G /dev/sdb1 myvg lvm2 a- 17.15G 17.15G 0 /dev/sdc1 myvg lvm2 a- 17.15G 15.15G 2.00G /dev/sdd1 myvg lvm2 a- 17.15G 15.15G 2.00G
Appendix A. Revision History Revision History Revision 6-12 Tue Mar 21 2017 Lenka Spackova Release of the Package Manifest for Red Hat Enterprise Linux 6.9 Revision 6-11 Fri May 06 2016 Lenka Spackova Release of the Package Manifest for Red Hat Enterprise Linux 6.8 Revision 6-10 Fri Jan 08 2016 Lenka Spackova Added the Supplementary channel, updated non-core packages, and improved the structure of the book. Revision 6-8 Tue Jul 28 2015 Laura Bailey Release of the Package Manifest for Red Hat Enterprise Linux 6.7 Revision 6-7 Tue Oct 14 2014 Martin Prpic Release of the Package Manifest for Red Hat Enterprise Linux 6.6 Revision 6-3 Thu Nov 21 2013 Eliska Slobodova Release of the Package Manifest for Red Hat Enterprise Linux 6.5 Revision 6-2 Thu Feb 21 2013 Eliska Slobodova Release of the Package Manifest for Red Hat Enterprise Linux 6.4 Revision 1-1 Wed Jun 20 2012 Eliska Slobodova Release of the Package Manifest for Red Hat Enterprise Linux 6.3 Revision 1-0 Tue Dec 6 2011 Martin Prpic Release of the Package Manifest for Red Hat Enterprise Linux 6.2 Revision 0-0 Tue May 19 2011 Ryan Lerch Initial Version of the Package Manifest for Red Hat Enterprise Linux 6.1

Commands:
Chapter 42. ContainerTemplate schema reference Used in: CruiseControlTemplate , EntityOperatorTemplate , JmxTransTemplate , KafkaBridgeTemplate , KafkaClusterTemplate , KafkaConnectTemplate , KafkaExporterTemplate , KafkaMirrorMakerTemplate , KafkaNodePoolTemplate , ZookeeperClusterTemplate Full list of ContainerTemplate schema properties You can set custom security context and environment variables for a container. The environment variables are defined under the env property as a list of objects with name and value fields. The following example shows two custom environment variables and a custom security context set for the Kafka broker containers: # ... template: kafkaContainer: env: - name: EXAMPLE_ENV_1 value: example.env.one - name: EXAMPLE_ENV_2 value: example.env.two securityContext: runAsUser: 2000 # ... Environment variables prefixed with KAFKA_ are internal to AMQ Streams and should be avoided. If you set a custom environment variable that is already in use by AMQ Streams, it is ignored and a warning is recorded in the log. 42.1. ContainerTemplate schema properties Property Description env Environment variables which should be applied to the container. ContainerEnvVar array securityContext Security context for the container. For more information, see the external documentation for core/v1 securitycontext . SecurityContext

Commands:
template: kafkaContainer: env: - name: EXAMPLE_ENV_1 value: example.env.one - name: EXAMPLE_ENV_2 value: example.env.two securityContext: runAsUser: 2000
Chapter 12. NodeMetrics [metrics.k8s.io/v1beta1] Description NodeMetrics sets resource usage metrics of a node. Type object Required timestamp window usage 12.1. Specification Property Type Description apiVersion string APIVersion defines the versioned schema of this representation of an object. Servers should convert recognized schemas to the latest internal value, and may reject unrecognized values. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#resources kind string Kind is a string value representing the REST resource this object represents. Servers may infer this from the endpoint the client submits requests to. Cannot be updated. In CamelCase. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#types-kinds metadata ObjectMeta_v2 Standard object's metadata. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata timestamp Time The following fields define time interval from which metrics were collected from the interval [Timestamp-Window, Timestamp]. usage object (Quantity) The memory usage is the memory working set. window Duration 12.2. API endpoints The following API endpoints are available: /apis/metrics.k8s.io/v1beta1/nodes GET : list objects of kind NodeMetrics /apis/metrics.k8s.io/v1beta1/nodes/{name} GET : read the specified NodeMetrics 12.2.1. /apis/metrics.k8s.io/v1beta1/nodes HTTP method GET Description list objects of kind NodeMetrics Table 12.1. HTTP responses HTTP code Reponse body 200 - OK NodeMetricsList schema 12.2.2. /apis/metrics.k8s.io/v1beta1/nodes/{name} Table 12.2. Global path parameters Parameter Type Description name string name of the NodeMetrics HTTP method GET Description read the specified NodeMetrics Table 12.3. HTTP responses HTTP code Reponse body 200 - OK NodeMetrics schema

Commands:
function::linuxmib_filter_key Name function::linuxmib_filter_key - Default filter function for linuxmib.* probes Synopsis Arguments sk pointer to the struct sock op value to be counted if sk passes the filter Description This function is a default filter function. The user can replace this function with their own. The user-supplied filter function returns an index key based on the values in sk . A return value of 0 means this particular sk should be not be counted.

Commands:
linuxmib_filter_key:long(sk:long,op:long)
Chapter 22. Policy: Configuring Host-Based Access Control IdM can control access to both machines and the services on those machines within the IdM domain. The rules define who can access what within the domain, not the level of access (which are defined by system or application settings). These access control rules grant access, with all other users and hosts implicitly denied. This is called host-based access control because the rule defines what hosts ( targets ) within the domain a user is allowd to access. This access can be further broken down to users and services on those hosts. Note Using host-based access control requires SSSD to be installed and configured on the IdM client machine. 22.1. About Host-Based Access Control Host-based access control rules (which are described in Chapter 22, Policy: Configuring Host-Based Access Control ) can be applied to individual hosts. However, using host groups allows centralized, and potentially simplified, access control management because an access control rule only needs to be defined once and then it is applied immediately and consistently to all the hosts within the group. Figure 22.1. Host Groups and Host-Based Access Control Note While access must be explicitly granted to users and hosts within the IdM domain, IdM servers are configured by default with an allow all access control rule which allows access for every host within the domain to every host within the domain. To create an IdM server without the default allow all rule, run ipa-server-install with the --no_hbac_allow option. The rule first defines things that can be accessed, and there are two types of entities: Hosts , or target hosts, within the IdM domain. Services on the target hosts. Multiple services can be combined into service groups . The service group can be modified without having to edit the access control rule itself. The rule also sets who can have access (the IdM domain user). Note It is possible to use categories for users and target hosts instead of adding each one individually to the access control rule. The only supported category is all . The entities in host-based access control rules follow the Kerberos principal entries: users, hosts (machines), and services. Users and target hosts can be added directly to host-based access control rules. However, services must be added to the host-based access control configuration first to make it available to rules, and then added to the access control rules.

Commands:
8.157. openmotif 8.157.1. RHBA-2014:1542 - openmotif bug fix update Updated openmotif packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The openmotif packages include the Motif shared libraries needed to run applications which are dynamically linked against Motif, as well as MWM, the Motif Window Manager. Bug Fixes BZ# 869782 , BZ# 953938 Prior to this update, the size set in the GeometryManager() function based on the XmFormConstraint "preferred_width" field was not updated when the label was changed and still contained the label length. Consequently, if the label text was modified while the window was smaller than the actual label width, the resulting size was incorrectly computed and the label text truncated. With this update, the values are updated and the fault no longer occurs in the described scenario. BZ# 1000343 Previously, when the Motif Window Manager, or MWM, was used as the window manager and the Mwm*freezeOnConfig and Mwm*moveOpaque options were set to "False", only icons appeared while moving a window anywhere on the screen, and no frame border was drawn. Consequently, users were having problems navigating the applications on their touch screen monitors. A patch has been provided to fix this bug, and windows are now displayed correctly when being moved anywhere on the screen. BZ# 1058644 Due to a bug in the underlying source code, an attempt to use the XmEXTENDED_SELECT policy could cause the Motif libraries to terminate unexpectedly with a segmentation fault. This update applies a patch to fix this bug and Motif no longer crashes in the described scenario. Users of openmotif are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 6. Configuring guest access with RBAC UI Use guest access with the role-based access control (RBAC) front-end plugin to allow a user to test role and policy creation without the need to set up and configure an authentication provider. Note Guest access is not recommended for production. 6.1. Configuring the RBAC backend plugin You can configure the RBAC backend plugin by updating the app-config.yaml file to enable the permission framework. Prerequisites You have installed the @janus-idp/backstage-plugin-rbac plugin in Developer Hub. For more information, see Configuring dynamic plugins . Procedure Update the app-config.yaml file to enable the permission framework as shown: permission enabled: true rbac: admin: users: - name: user:default/guest pluginsWithPermission: - catalog - permission - scaffolder Note The pluginsWithPermission section of the app-config.yaml section includes only three plugins by default. Update the section as needed to include any additional plugins that also incorporate permissions. 6.2. Setting up the guest authentication provider You can enable guest authentication and use it alongside the RBAC frontend plugin. Prerequisites You have installed the @janus-idp/backstage-plugin-rbac plugin in Developer Hub. For more information, see Configuring dynamic plugins . Procedure In the app-config.yaml file, add the user entity reference to resolve and enable the dangerouslyAllowOutsideDevelopment option, as shown in the following example: auth: environment: development providers: guest: userEntityRef: user:default/guest dangerouslyAllowOutsideDevelopment: true Note You can use user:default/guest as the user entity reference to match the added user under the permission.rbac.admin.users section of the app-config.yaml file.

Commands:
permission enabled: true rbac: admin: users: - name: user:default/guest pluginsWithPermission: - catalog - permission - scaffolder
auth: environment: development providers: guest: userEntityRef: user:default/guest dangerouslyAllowOutsideDevelopment: true
Chapter 7. Directory Server in Red Hat Enterprise Linux About Directory Server for Red Hat Enterprise Linux This section describes changes in the main server component for Red Hat Directory Server - the 389-ds-base package, which includes the LDAP server itself and command line utilities and scripts for its administration. This package is part of the Red Hat Enterprise Linux base subscription channel and therefore available on all Red Hat Enterprise Linux Server systems due to Red Hat Identity Management components which depend on it. Additional Red Hat Directory Server components, such as the Directory Server Console , are available in the rhel-x86_64-server-6-rhdirserv-9 additional subscription channel. A subscription to this channel is also required to obtain support for Red Hat Directory Server. Changes to the additional components in this channel are not described in this document. Red Hat Directory Server version 9 is available for Red Hat Enterprise Linux 6. See https://access.redhat.com/products/red-hat-directory-server/get-started-v9 for information about getting started with Directory Server 9, and https://access.redhat.com/documentation/en/red-hat-directory-server/?version=9 for full documentation. (BZ#1333801) Improved performance when deleting large quantities of multi-valued attributes The API used to delete entries with large amounts of multi-valued attributes has been replaced with a significantly faster one, causing a large performance improvement in such situations. (BZ# 1236148 )

Commands: