mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 18. ID Views ID views enable you to specify new values for POSIX user or group attributes, as well as to define on which client host or hosts the new values will apply. For example, you can use ID views to: define different attribute values for different environments; see Section 18.3, "Defining a Different Attribute Value for a User Account on Different Hosts" replace a previously generated attribute value with a different value Important You can apply ID views only to IdM clients, not to IdM servers. Potential Negative Impact on SSSD Performance Applying an ID view can have a negative impact on SSSD performance, because certain optimizations and ID views cannot run at the same time. For example, ID views prevent SSSD from optimizing the process of looking up groups on the server: With ID views, SSSD must check every member on the returned list of group member names if the group name is overridden. Without ID views, SSSD can only collect the user names from the member attribute of the group object. This negative effect mostly becomes apparent when the SSSD cache is empty or after clearing the cache, which makes all entries invalid. Additional Resources ID views also have several use cases in environments involving Active Directory. For details, see the Migrate from Synchronization to Trust Manually Using ID Views chapter in the Windows Integration Guide . 18.1. Attributes an ID View Can Override ID views consist of user and group ID overrides. The overrides define the new attribute values. User and group ID overrides can define new values for the following attributes: User attributes Login name ( uid ) GECOS entry ( gecos ) UID number ( uidNumber ) GID number ( gidNumber ) Login shell ( loginShell ) Home directory ( homeDirectory ) SSH public keys ( ipaSshPubkey ) Certificate ( userCertificate ) Group attributes Group name ( cn ) Group GID number ( gidNumber )

Commands:
Chapter 6. Creating Access to Volumes Warning Do not enable the storage.fips-mode-rchecksum volume option on volumes with clients that use Red Hat Gluster Storage 3.4 or earlier. Red Hat Gluster Storage volumes can be accessed using a number of technologies: Native Client (see Section 6.2, "Native Client" ) Network File System (NFS) v3 (see Section 6.3, "NFS" ) Server Message Block (SMB) (see Section 6.4, "SMB" ) 6.1. Client Support Information 6.1.1. Cross Protocol Data Access Because of differences in locking semantics, a single Red Hat Gluster Storage volume cannot be concurrently accessed by multiple protocols. Current support for concurrent access is defined in the following table. Table 6.1. Cross Protocol Data Access Matrix SMB Gluster NFS NFS-Ganesha Native FUSE Object SMB Yes No No No No Gluster NFS (Deprecated) No Yes No No No NFS-Ganesha No No Yes No No Native FUSE No No No Yes Yes [a] 6.1.2. Client Operating System Protocol Support The following table describes the support level for each file access protocol in a supported client operating system. Table 6.2. Client OS Protocol Support Client OS FUSE Gluster NFS NFS-Ganesha SMB RHEL 5 Unsupported Unsupported Unsupported Unsupported RHEL 6 Supported Deprecated Unsupported Supported RHEL 7 Supported Deprecated Supported Supported RHEL 8 Supported Unsupported Supported Supported Windows Server 2008, 2012, 2016 Unsupported Unsupported Unsupported Supported Windows 7, 8, 10 Unsupported Unsupported Unsupported Supported Mac OS 10.15 Unsupported Unsupported Unsupported Supported 6.1.3. Transport Protocol Support The following table provides the support matrix for the supported access protocols with TCP/RDMA. Table 6.3. Transport Protocol Support Access Protocols TCP RDMA (Deprecated) FUSE Yes Yes SMB Yes No NFS Yes Yes Warning Using RDMA as a transport protocol is considered deprecated in Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support it on new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3. Important Red Hat Gluster Storage requires certain ports to be open. You must ensure that the firewall settings allow access to the ports listed at Chapter 3, Considerations for Red Hat Gluster Storage . Gluster user is created as a part of gluster installation. The purpose of gluster user is to provide privileged access to libgfapi based application (for example, nfs-ganesha and glusterfs-coreutils ). For a normal user of an application, write access to statedump directory is restricted. As a result, attempting to write a state dump to this directory fails. Privileged access is needed by these applications in order to be able to write to the statedump directory. In order to write to this location, the user that runs the application should ensure that the application is added to the gluster user group. After the application is added, restart gluster processes to apply the new group.

Commands:
Chapter 10. (Preview) Streams for Apache Kafka Console (user interface) After you have deployed your Kafka cluster, you can connect it to the Streams for Apache Kafka Console. The Streams for Apache Kafka Console supports the monitoring and management of Kafka clusters. Connect a Kafka cluster managed by Streams for Apache Kafka to gain real-time insights and optimize cluster performance from its user interface. The console's homepage displays connected Kafka clusters, allowing you to access detailed information on components such as brokers, topics, partitions, and consumer groups. From the Streams for Apache Kafka Console, you can view the status of a Kafka cluster before navigating to view information on the cluster's brokers and topics, or the consumer groups connected to the Kafka cluster. You can monitor your deployment by checking the following from the console: Connected clusters The status of cluster brokers The flow of topic messages The status of partitions for specific topics The consumer groups associated with specific topics For more information on connecting to and using the Streams for Apache Kafka Console, see the console guide in the Streams for Apache Kafka documentation . Note The Streams for Apache Kafka Console is currently available as a technology preview.

Commands:
5.324. system-config-lvm 5.324.1. RHBA-2012:0960 - system-config-lvm bug fix update An updated system-config-lvm package that fixes multiple bugs is now available for Red Hat Enterprise Linux 6. The system-config-lvm package contains a utility for configuring logical volumes using a graphical user interface. Bug Fixes BZ# 791153 The system-config-lvm utility incorrectly displayed all LVM devices in the "Unitialized Entities" group. This could confuse users who could try to re-initialize logical volumes unnecessarily. This update modifies system-config-lvm to show LVM devices as "Unitialized Entities" only if the logical volumes really are uninitialized. BZ# 708029 The system-config-lvm utility uses fdisk as a back end for partition operations. The fdisk utility does not support the Extensible Firmware Interface (EFI) GUID Partition Table (GPT), so an attempt to initialize a physical partition on EFI GPT fails. However, system-config-lvm previously did not handle this situation correctly and the operation failed without any error message. This update modifies the underlying code so that system-config-lvm now provides a valid error message in this situation. BZ# 726830 The system-config-lvm utility did not properly handle physical partitions with names in the form of "*p[0-9]", for example, "loop0p0". Therefore, system-config-lvm terminated unexpectedly when attempting to initialize such a partition. This update modifies the underlying code so that system-config-lvm no longer crashes in this scenario. However, system-config-lvm still does not handle such partition names and such partitions cannot be initialized. BZ# 815921 The system-config-lvm utility uses the dmsetup tool for obtaining information from Device Mapper Multipath. Output of dmsetup was designed to be parsed by scripts, however, with an update of device-mapper-multipath to version 1.02.74, this output was changed. As a consequence, system-config-lvm terminated unexpectedly with a traceback when used with Device-Mapper Multipath available on the system. This update modifies system-config-lvm to use a user-specified output which does not change across different versions. The system-config-lvm utility now works as expected. All users of system-config-lvm are advised to upgrade to this updated package, which fixes these bugs.

Commands:
18.3. Options Used within iptables Commands Rules for filtering packets are put in place using the iptables command. The following aspects of the packet are most often used as criteria: Packet Type - Specifies the type of packets the command filters. Packet Source/Destination - Specifies which packets the command filters based on the source or destination of the packet. Target - Specifies what action is taken on packets matching the above criteria. For more information on specific options which address these aspects of a packet, refer to Section 18.3.4, " iptables Match Options" and Section 18.3.5, "Target Options" . The options used with given iptables rules must be grouped logically, based on the purpose and conditions of the overall rule, for the rule to be valid. The remainder of this section explains commonly-used options for the iptables command. 18.3.1. Structure of iptables Options Many iptables commands have the following structure: The <table-name> option allows the user to select a table other than the default filter table to use with the command. The <command> option dictates a specific action to perform, such as appending or deleting the rule specified by the <chain-name> option. Following the <chain-name> are pairs of parameters and options that define what happens when a packet matches the rule. When looking at the structure of an iptables command, it is important to remember that, unlike most other commands, the length and complexity of an iptables command can change based on its purpose. A command to remove a rule from a chain can be very short, while a command designed to filter packets from a particular subnet using a variety of specific parameters and options can be rather lengthy. When creating iptables commands, it is helpful to recognize that some parameters and options may create the need for other parameters and options to further specify the option's request. To construct a valid rule, this must continue until every parameter and option that requires another set of options is satisfied. Type iptables -h to view a comprehensive list of iptables command structures.

Commands:
iptables [-t <table-name> ] <command> <chain-name> <parameter-1> <option-1> <parameter-n> <option-n>
Chapter 1. Removing OpenShift Serverless overview If you need to remove OpenShift Serverless from your cluster, you can do so by manually removing the OpenShift Serverless Operator and other OpenShift Serverless components. Before you can remove the OpenShift Serverless Operator, you must remove Knative Serving and Knative Eventing. After uninstalling the OpenShift Serverless, you can remove the Operator and API custom resource definitions (CRDs) that remain on the cluster. The steps for fully removing OpenShift Serverless are detailed in the following procedures: Uninstalling Knative Eventing . Uninstalling Knative Serving . Removing the OpenShift Serverless Operator . Deleting OpenShift Serverless custom resource definitions .

Commands:
Chapter 4. Managing build output Use the following sections for an overview of and instructions for managing build output. 4.1. Build output Builds that use the docker or source-to-image (S2I) strategy result in the creation of a new container image. The image is then pushed to the container image registry specified in the output section of the Build specification. If the output kind is ImageStreamTag , then the image will be pushed to the integrated OpenShift image registry and tagged in the specified imagestream. If the output is of type DockerImage , then the name of the output reference will be used as a docker push specification. The specification may contain a registry or will default to DockerHub if no registry is specified. If the output section of the build specification is empty, then the image will not be pushed at the end of the build. Output to an ImageStreamTag spec: output: to: kind: "ImageStreamTag" name: "sample-image:latest" Output to a docker Push Specification spec: output: to: kind: "DockerImage" name: "my-registry.mycompany.com:5000/myimages/myimage:tag" 4.2. Output image environment variables docker and source-to-image (S2I) strategy builds set the following environment variables on output images: Variable Description OPENSHIFT_BUILD_NAME Name of the build OPENSHIFT_BUILD_NAMESPACE Namespace of the build OPENSHIFT_BUILD_SOURCE The source URL of the build OPENSHIFT_BUILD_REFERENCE The Git reference used in the build OPENSHIFT_BUILD_COMMIT Source commit used in the build Additionally, any user-defined environment variable, for example those configured with S2I or docker strategy options, will also be part of the output image environment variable list. 4.3. Output image labels docker and source-to-image (S2I) builds set the following labels on output images: Label Description io.openshift.build.commit.author Author of the source commit used in the build io.openshift.build.commit.date Date of the source commit used in the build io.openshift.build.commit.id Hash of the source commit used in the build io.openshift.build.commit.message Message of the source commit used in the build io.openshift.build.commit.ref Branch or reference specified in the source io.openshift.build.source-location Source URL for the build You can also use the BuildConfig.spec.output.imageLabels field to specify a list of custom labels that will be applied to each image built from the build configuration. Custom labels for built images spec: output: to: kind: "ImageStreamTag" name: "my-image:latest" imageLabels: - name: "vendor" value: "MyCompany" - name: "authoritative-source-url" value: "registry.mycompany.com"

Commands:
spec: output: to: kind: "ImageStreamTag" name: "sample-image:latest"
spec: output: to: kind: "DockerImage" name: "my-registry.mycompany.com:5000/myimages/myimage:tag"
spec: output: to: kind: "ImageStreamTag" name: "my-image:latest" imageLabels: - name: "vendor" value: "MyCompany" - name: "authoritative-source-url" value: "registry.mycompany.com"
4.273. rng-tools 4.273.1. RHEA-2011:1774 - rng-tools bug fix update An enhanced rng-tools package that adds two enhancements is now available for Red Hat Enterprise Linux 6. The rng-tools package contains the random number generator user space utilities, such as the rngd daemon. Enhancements BZ# 733452 A new "-i, --ignorefail" command line option has been added to the rngd daemon. This option allows rngd to ignore repeated warning messages about failed FIPS checks. BZ# 749629 The rngd(8) manual page has been modified to include the "-i, --ignorefail" option. All users of rng-tools are advised to upgrade to this updated package, which adds these enhancements. 4.273.2. RHEA-2011:1776 - rng-tools enhancement update An enhanced rng-tools package that adds two enhancements is now available for Red Hat Enterprise Linux 6. The rng-tools package contains the random number generator user space utilities, such as the rngd daemon. Enhancements BZ# 754752 The startup script and configuration files for the rngd daemon have been added to the /etc/init.d/ and /etc/sysconfig/ directory, respectively. All users of rng-tools are advised to upgrade to this updated package, which adds these enhancements.

Commands:
function::usymdata Name function::usymdata - Return the symbol and module offset of an address. EXPERIMENTAL! Synopsis Arguments addr The address to translate. Description Returns the (function) symbol name associated with the given address in the current task if known, the offset from the start and the size of the symbol, plus the module name (between brackets). If symbol is unknown, but module is known, the offset inside the module, plus the size of the module is added. If any element is not known it will be omitted and if the symbol name is unknown it will return the hex string for the given address.

Commands:
function usymdata:string(addr:long)
8.8. aide 8.8.1. RHBA-2014:0948 - aide bug fix update Updated aide packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Advanced Intrusion Detection Environment (AIDE) is a utility that creates a database of files on the system, and then uses that database to ensure file integrity and detect system intrusions. Bug Fixes BZ# 806911 Previously, the AIDE utility did not handle 'prelink' files properly if the prelink package was not installed. As a consequence, initializing the database by running the 'aide --init' command caused errors, and the database could not then be read with the 'aide --check' command. With this update, after running the 'aide --init' command in the described situation, a warning massage is displayed that prompts the user to install the prelink package first. BZ# 1119759 Prior to this update, the AIDE utility did not process the 'report_attributes' parameter correctly. Consequently, running the 'aide --check' command resulted in an incomplete report and a segmentation fault. A patch has been applied to address this bug, and AIDE now works as expected when reporting forced attributes. Users of aide are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 5. Deploying cloud images with Image Builder Image Builder can create custom system images ready for use in clouds of various providers. To use your customized RHEL system image in a cloud, create the system image with Image Builder using the respective output type, configure your system for uploading the image, and upload the image to your cloud account. 5.1. Preparing AWS AMI images for upload This section describes steps to configure a system for uploading AWS AMI images. Prerequisites You must have an Access Key ID configured in the AWS IAM account manager . You must have a writable S3 bucket prepared. Procedure 1. Install Python 3 and the pip tool: 2. Install the AWS command-line tools with pip: 3. Configure the AWS command-line client according to your AWS access details: 4. Configure the AWS command-line client to use your bucket: Replace bucketname with the actual bucket name. 5. Create a vmimport S3 Role in IAM and grant it permissions to access S3, if you have not already done so:

Commands:
yum install python3 python3-pip
pip3 install awscli
aws configure AWS Access Key ID [None]: AWS Secret Access Key [None]: Default region name [None]: Default output format [None]:
BUCKET=bucketname
aws s3 mb s3://USDBUCKET
printf '{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Principal": { "Service": "vmie.amazonaws.com" }, "Action": "sts:AssumeRole", "Condition": { "StringEquals":{ "sts:Externalid": "vmimport" } } } ] }' > trust-policy.json USD printf '{ "Version":"2012-10-17", "Statement":[ { "Effect":"Allow", "Action":[ "s3:GetBucketLocation", "s3:GetObject", "s3:ListBucket" ], "Resource":[ "arn:aws:s3:::%s", "arn:aws:s3:::%s/*" ] }, { "Effect":"Allow", "Action":[ "ec2:ModifySnapshotAttribute", "ec2:CopySnapshot", "ec2:RegisterImage", "ec2:Describe*" ], "Resource":"*" } ] }' USDBUCKET USDBUCKET > role-policy.json USD aws iam create-role --role-name vmimport --assume-role-policy-document file://trust-policy.json USD aws iam put-role-policy --role-name vmimport --policy-name vmimport --policy-document file://role-policy.json
2.36. RHEA-2011:0654 - new package: ras-utils A new ras-utils package is now available for Red Hat Enterprise Linux 6. The ras-utils package contains both the aer-inject (for PCIE AER Injection) and mce-inject (MCE Injection) tools. These tools can be used to insert software-simulated AER and MCE errors. This enhancement update adds a new ras-utils package to Red Hat Enterprise Linux 6. (BZ# 653481 ) All users requiring ras-utils should install these newly-released package, which adds this enhancement.

Commands:
27.3. Additional Resources To learn more about configuring automated tasks, see the following installed documentation: cron man page contains an overview of cron. crontab man pages in sections 1 and 5: The manual page in section 1 contains an overview of the crontab file. The man page in section 5 contains the format for the file and some example entries. anacron manual page contains an overview of anacron. anacrontab manual page contains an overview of the anacrontab file. /usr/share/doc/at- <version> /timespec contains detailed information about the time values that can be used in cron job definitions. at manual page contains descriptions of at and batch and their command-line options.

Commands:
Chapter 2. Changes between OptaPlanner 8.2.0 and OptaPlanner 8.3.0 The changes listed in this section were made between OptaPlanner 8.2.0 and OptaPlanner 8.3.0. ConstraintMatch.compareTo() inconsistent with equals() Minor The equals() override in ConstraintMatch has been removed. As a result, two different ConstraintMatch instances are never considered equal. This contrasts with the compareTo() method, which continues to consider two instances equal if all their field values are equal.

Commands:
Chapter 3. Included features Built on the foundation of Red Hat Enterprise Linux, the RHEL for SAP Solutions subscription includes the following additional components: SAP-specific technical components to support S/4HANA, SAP HANA, and SAP Business Applications. High Availability solutions for S/4HANA, SAP HANA, and SAP Business Applications. RHEL System Roles for SAP, which can be used to automate the configuration of a RHEL system to run SAP workloads. Smart Management and Red Hat Insights for lifecycle management and proactive optimization. SAP HANA tested in-place upgrades and live kernel patching capabilities to maximize SAP business uptime. Update Services for SAP Solutions / Extended Update Support, providing up to four years of support on specified minor releases.

Commands:
probe::netfilter.bridge.pre_routing Name probe::netfilter.bridge.pre_routing - - Called before a bridging packet is routed Synopsis netfilter.bridge.pre_routing Values llcproto_stp Constant used to signify Bridge Spanning Tree Protocol packet pf Protocol family -- always " bridge " nf_drop Constant used to signify a 'drop' verdict br_msg Message age in 1/256 secs indev Address of net_device representing input device, 0 if unknown brhdr Address of bridge header nf_queue Constant used to signify a 'queue' verdict br_fd Forward delay in 1/256 secs br_mac Bridge MAC address br_rid Identity of root bridge nf_accept Constant used to signify an 'accept' verdict br_flags BPDU flags outdev_name Name of network device packet will be routed to (if known) br_prid Protocol identifier br_rmac Root bridge MAC address br_htime Hello time in 1/256 secs br_bid Identity of bridge protocol Packet protocol br_max Max age in 1/256 secs br_type BPDU type nf_stop Constant used to signify a 'stop' verdict br_cost Total cost from transmitting bridge to root nf_stolen Constant used to signify a 'stolen' verdict length The length of the packet buffer contents, in bytes llcpdu Address of LLC Protocol Data Unit outdev Address of net_device representing output device, 0 if unknown nf_repeat Constant used to signify a 'repeat' verdict indev_name Name of network device packet was received on (if known) br_poid Port identifier br_vid Protocol version identifier

Commands:
4.15. Squid Squid has been updated to version 3.1. This update provides native IPv6 support and significantly shortens the /etc/squid/squid.conf configuration file. However, it also comes with some significant change to configuration options, which are not entirely backwards compatible with some older versions of Squid. For complete details on the changes, see the Squid 3.1 release notes: http://www.squid-cache.org/Versions/v3/3.1/RELEASENOTES.html .

Commands: