mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 18. Desktop The vmware driver does not support multiple displays The vmware video driver for the X11 window system misses certain features related to multi-display support. As a consequence, Red Hat Enterprise Linux 6 guests running on VMware cannot correctly use multiple displays and only single-display support is available. Please contact Red Hat support for test packages if you require multi-display support. (BZ# 1320480 ) Incorrect mouse pointer movement after screen rotation inside a virtual machine in VMWare 11 or VMWare 12 If the screen rotation is changed inside a virtual machine in VMWare 11 or VMWare 12, the pointer movement remains unchanged. This only happens when the xorg-x11-drv-vmware driver is used, which initializes an absolute-axis device rather than a relative-axis device. The pointer does not follow the expected path because the driver is still mapping to the original coordinate system. To work around this problem, it it necessary to manually rotate the device, for example by running the following command: Note that the command above is only an example. In general, the matrix needs to be adjusted depending on the specific scenario. Once the matrix is applied, pointer movement matches the rotation of the screen. (BZ# 1322712 , BZ# 1318340 ) Using Radeon or Nouveau can cause incorrectly rendered graphics A bug in the Xorg server can, under rare circumstances, cause graphics to be rendered incorrectly if using the Radeon or Nouveau graphics device driver. For example, the Thunderbird message pane can be displayed incorrectly. For Nouveau, as a workaround, add the WrappedFB option to the xorg.conf file as follows: This workaround avoids the faulty logic in the X server, and the Thunderbird message pane will be displayed correctly. (BZ#1076595)

Commands:
xinput set-prop "ImPS/2 Generic Wheel Mouse" "Coordinate Transformation Matrix" 0 -1 1 1 0 0 0 0 1
Section "Device" Identifier "nouveau-device" Driver "nouveau" Option "WrappedFB" "true" EndSection
5.6.3.4. With LVM, Why Use RAID? Given that LVM has some features similar to RAID (the ability to dynamically replace failing drives, for instance), and some features providing capabilities that cannot be matched by most RAID implementations (such as the ability to dynamically add more storage to a central storage pool), many people wonder whether RAID is no longer important. Nothing could be further from the truth. RAID and LVM are complementary technologies that can be used together (in a manner similar to nested RAID levels), making it possible to get the best of both worlds.

Commands:
4.4. Authentication Apache Modules for External Authentication A set of Apache modules has been added to Red Hat Enterprise Linux 6.6 as a Technology Preview. The mod_authnz_pam , mod_intercept_form_submit , and mod_lookup_identity Apache modules in the respective packages can be used by Web applications to achieve tighter interaction with external authentication and identity sources, such as Identity Management in Red Hat Enterprise Linux. Simultaneous maintaining of TGTs for multiple KDCs Kerberos version 1.10 added a new cache storage type, DIR:, which allows Kerberos to maintain Ticket Granting Tickets (TGTs) for multiple Key Distribution Centers (KDCs) simultaneously and auto-select between them when negotiating with Kerberized resources. Red Hat Enterprise Linux 6.4 and later includes SSSD enhanced to allow the users to select the DIR: cache for users that are logging in via SSSD. This feature is introduced as a Technology Preview. Package: sssd-1.12.4-31

Commands:
Chapter 21. Branding a Red Hat Quay deployment on the legacy UI You can brand the UI of your Red Hat Quay deployment by changing the registry title, logo, footer image, and by directing users to a website embedded in the footer image. Procedure Update your Red Hat Quay config.yaml file to add the following parameters: BRANDING: logo: 1 footer_img: 2 footer_url: 3 --- REGISTRY_TITLE: 4 REGISTRY_TITLE_SHORT: 5 1 The URL of the image that will appear at the top of your Red Hat Quay deployment. 2 The URL of the image that will appear at the bottom of your Red Hat Quay deployment. 3 The URL of the website that users will be directed to when clicking the footer image. 4 The the long-form title for the registry. This is displayed in frontend of your Red Hat Quay deployment, for example, at the sign in page of your organization. 5 The short-form title for the registry. The title is displayed on various pages of your organization, for example, as the title of the tutorial on your organization's Tutorial page. Restart your Red Hat Quay deployment. After restarting, your Red Hat Quay deployment is updated with a new logo, footer image, and footer image URL.

Commands:
BRANDING: logo: 1 footer_img: 2 footer_url: 3 --- REGISTRY_TITLE: 4 REGISTRY_TITLE_SHORT: 5
Appendix C. Revision History 0.1-5 Fri Apr 28 2023, Lucie Varakova ( lvarakova@redhat.com ) Added a known issue (Authentication and Interoperability). 0.1-4 Tue Mar 02 2021, Lenka Spackova ( lspackova@redhat.com ) Updated a link to Upgrading from RHEL 6 to RHEL 7 . Fixed CentOS Linux name. 0.1-3 Wed Sep 2 2020, Jaroslav Klech ( jklech@redhat.com ) Added a kernel enhancement that IBPB cannot be directly disabled. 0.1-2 Tue Apr 28 2020, Lenka Spackova ( lspackova@redhat.com ) Updated information about in-place upgrades. 0.1-1 Thu Mar 19 2020, Lenka Spackova ( lspackova@redhat.com ) Added a known issue related to installation. 0.1-0 Thu Mar 12 2020, Lenka Spackova ( lspackova@redhat.com ) Added information about the storage RHEL System Role. 0.0-9 Wed Feb 12 2020, Jaroslav Klech ( jklech@redhat.com ) Provided a complete kernel version to Architectures and New Features chapters. 0.0-8 Mon Feb 03 2020, Lenka Spackova ( lspackova@redhat.com ) Added a known issue about an error message when upgrading from the RHEL 7.6 version of PCP . 0.0-7 Tue Nov 05 2019, Lenka Spackova ( lspackova@redhat.com ) Updated Overview with the new supported in-place upgrade path from RHEL 7.6 to RHEL 8.1. Updated deprecated functionality. 0.0-6 Fri Oct 25 2019, Lenka Spackova ( lspackova@redhat.com ) Added a note that RHEL System Roles for SAP are now available as a Technology Preview. 0.0-5 Mon Oct 7 2019, Jiri Herrman ( jherrman@redhat.com ) Clarified a Technology Preview note related to OVMF. 0.0-4 Wed Aug 21 2019, Lenka Spackova ( lspackova@redhat.com ) Added instructions on how to enable the Extras channel to the YUM 4 Technology Preview note (System and Subscription Management). 0.0-3 Tue Aug 20 2019, Lenka Spackova ( lspackova@redhat.com ) Added a known issue related to kdump (Kernel). Updated text of a Technology Preview description (Virtualization). 0.0-2 Thu Aug 15 2019, Lenka Spackova ( lspackova@redhat.com ) Added a Technology Preview related to Azure M416v2 as a host (Virtualization). Added a link to Intel(R) Omni-Path Architecture documentation (Kernel). Added an SSSD-related feature: a new default value for the fallback_homedir parameter (Authentication and Interoperability). Added a known issue related to the bnx2x driver (Kernel). Added two desktop-related bug fixes. 0.0-1 Tue Aug 06 2019, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.7 Release Notes. 0.0-0 Wed Jun 05 2019, Lenka Spackova ( lspackova@redhat.com ) Release of the Red Hat Enterprise Linux 7.7 Beta Release Notes.

Commands:
4.5. Changing SELinux Modes at Boot Time On boot, you can set several kernel parameters to change the way SELinux runs: enforcing=0 Setting this parameter causes the system to start in permissive mode, which is useful when troubleshooting issues. Using permissive mode might be the only option to detect a problem if your file system is too corrupted. Moreover, in permissive mode, the system continues to create the labels correctly. The AVC messages that are created in this mode can be different than in enforcing mode. In permissive mode, only the first denial from a series of the same denials is reported. However, in enforcing mode, you might get a denial related to reading a directory, and an application stops. In permissive mode, you get the same AVC message, but the application continues reading files in the directory and you get an AVC for each denial in addition. selinux=0 This parameter causes the kernel to not load any part of the SELinux infrastructure. The init scripts notice that the system booted with the selinux=0 parameter and touch the /.autorelabel file. This causes the system to automatically relabel the time you boot with SELinux enabled. Important Red Hat does not recommend using the selinux=0 parameter. To debug your system, prefer using permissive mode. autorelabel=1 This parameter forces the system to relabel similarly to the following commands: If the system labeling contains a large amount of errors, you might need to boot in permissive mode in order that the autorelabel succeeds. For additional SELinux-related kernel boot parameters, such as checkreqprot , see the /usr/share/doc/kernel-doc- <KERNEL_VER> /Documentation/kernel-parameters.txt file. This documentation is installed with the kernel-doc package. Replace the <KERNEL_VER> string with the version number of the installed kernel, for example:

Commands:
~]# touch /.autorelabel ~]# reboot
~]# yum install kernel-doc ~]USD less /usr/share/doc/kernel-doc- 3.10.0 /Documentation/kernel-parameters.txt
5.9. Multiple Monitoring Operations You can configure a single resource with as many monitor operations as a resource agent supports. In this way you can do a superficial health check every minute and progressively more intense ones at higher intervals. Note When configuring multiple monitor operations, you must ensure that no two operations are performed at the same interval. To configure additional monitoring operations for a resource that supports more in-depth checks at different levels, you add an OCF_CHECK_LEVEL= n option. For example, if you configure the following IPaddr2 resource, by default this creates a monitoring operation with an interval of 10 seconds and a timeout value of 20 seconds. If the Virtual IP supports a different check with a depth of 10, the following command causes Pacemaker to perform the more advanced monitoring check every 60 seconds in addition to the normal Virtual IP check every 10 seconds. (As noted, you should not configure the additional monitoring operation with a 10-second interval as well.)

Commands:
pcs resource create VirtualIP ocf:heartbeat:IPaddr2 ip=192.168.0.99 cidr_netmask=24 nic=eth2
pcs resource op add VirtualIP monitor interval=60s OCF_CHECK_LEVEL=10
Chapter 72. ClientTls schema reference Used in: KafkaBridgeSpec , KafkaConnectSpec , KafkaMirrorMaker2ClusterSpec , KafkaMirrorMakerConsumerSpec , KafkaMirrorMakerProducerSpec Full list of ClientTls schema properties Configures TLS trusted certificates for connecting KafkaConnect, KafkaBridge, KafkaMirror, KafkaMirrorMaker2 to the cluster. 72.1. trustedCertificates Provide a list of secrets using the trustedCertificates property . 72.2. ClientTls schema properties Property Property type Description trustedCertificates CertSecretSource array Trusted certificates for TLS connection.

Commands:
4.21. RHEA-2012:0786 - new packages: kmod-hpsa New kmod-hpsa packages are now available for Red Hat Enterprise Linux 6. The kmod-hpsa packages provide kernel modules for controlling HP Smart Array Controllers. The kmod-hpsa packages provide temporary drivers for the following hardware beyond what was delivered in Red Hat Enterprise Linux 6.3: HP Smart Array Controllers This enhancement update adds the kmod-hpsa packages to Red Hat Enterprise Linux 6 as part of the Red Hat Enterprise Linux Driver Update Program (DUP). Only users requiring temporary driver support for the specific hardware noted above should install these packages. Unless a system includes the exact hardware explicitly supported by the kmod-hpsa packages, these packages must not be installed. Note that before installation of Red Hat Enterprise Linux 6.3 with the hpsa Driver Update Disk (DUD), you are advised to use the "pci=nomsi" kernel parameter to work around the hpsa driver load/unload issue described in BZ# 904945 . Once the installation is complete, this kernel parameter is no longer needed.

Commands:
Chapter 1. Streams for Apache Kafka Console overview The Streams for Apache Kafka Console provides a user interface to facilitate the administration of Kafka clusters, delivering real-time insights for monitoring, managing, and optimizing each cluster from its user interface. 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 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.

Commands:
Chapter 2. Disaster recovery subscription requirement Disaster Recovery features supported by Red Hat OpenShift Data Foundation require all of the following prerequisites to successfully implement a disaster recovery solution: A valid Red Hat OpenShift Data Foundation Advanced entitlement A valid Red Hat Advanced Cluster Management for Kubernetes subscription Any Red Hat OpenShift Data Foundation Cluster containing PVs participating in active replication either as a source or destination requires OpenShift Data Foundation Advanced entitlement. This subscription should be active on both source and destination clusters. To know how subscriptions for OpenShift Data Foundation work, see knowledgebase article on OpenShift Data Foundation subscriptions .

Commands:
6.9. Configuring Global Cluster Resources You can configure two types of resources: Global - Resources that are available to any service in the cluster. Service-specific - Resources that are available to only one service. To see a list of currently configured resources and services in the cluster, execute the following command: To add a global cluster resource, execute the following command. You can add a resource that is local to a particular service when you configure the service, as described in Section 6.10, "Adding a Cluster Service to the Cluster" . For example, the following command adds a global file system resource to the cluster configuration file on node01.example.com . The name of the resource is web_fs , the file system device is /dev/sdd2 , the file system mountpoint is /var/www , and the file system type is ext3 . For information about the available resource types and resource options, see Appendix B, HA Resource Parameters . To remove a global resource, execute the following command: If you need to modify the parameters of an existing global resource, you can remove the resource and configure it again. Note that when you have finished configuring all of the components of your cluster, you will need to sync the cluster configuration file to all of the nodes, as described in Section 6.15, "Propagating the Configuration File to the Cluster Nodes" .

Commands:
ccs -h host --lsservices
ccs -h host --addresource resourcetype [resource options]
ccs -h node01.example.com --addresource fs name=web_fs device=/dev/sdd2 mountpoint=/var/www fstype=ext3
ccs -h host --rmresource resourcetype [resource options]
7.262. valgrind 7.262.1. RHBA-2013:0347 - valgrind bug fix and enhancement update Updated valgrind packages that fix several bugs and add an enhancement are now available for Red Hat Enterprise Linux 6. The valgrind packages provide a programming utility for debugging memory, detecting memory leaks, and profiling. Note The valgrind packages have been upgraded to upstream version 3.8.1, which provides a number of bug fixes over the version. (BZ#823005) Bug Fixes BZ# 730303 When running a large program under valgrind, the "Valgrind: FATAL: VG_N_SEGNAMES is too low." error messages could be returned. With this update, the compile time constants have been increased (VG_N_SEGMENTS to 50000, VG_N_SEGNAMES to 25000) and these errors no longer occur. BZ# 862795 Previously, the valgrind gdbserver did not properly report exit or a fatal-signal process termination to the gdb debugger. Consequently, the "Remote connection closed" error messages were returned. This bug has been fixed in the code and the process termination is now properly reported in gdb. BZ# 816244 On IBM S/390 architecture, valgrind could report a "Conditional jump or move depends on uninitialized value(s)" warning message for the tsearch() function in glibc. This update includes a standard suppression for these warning messages, which are no longer reported. Enhancement BZ# 672959 The embedded gdbserver has been added to allow integration of valgrind with the gdb debugger. Users of valgrind are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 6. Encryption token is deleted or expired Use this procedure to update the token if the encryption token for your key management system gets deleted or expires. Prerequisites Ensure that you have a new token with the same policy as the deleted or expired token Procedure Log in to OpenShift Container Platform Web Console. Click Workloads Secrets To update the ocs-kms-token used for cluster wide encryption: Set the Project to openshift-storage . Click ocs-kms-token Actions Edit Secret . Drag and drop or upload your encryption token file in the Value field. The token can either be a file or text that can be copied and pasted. Click Save . To update the ceph-csi-kms-token for a given project or namespace with encrypted persistent volumes: Select the required Project . Click ceph-csi-kms-token Actions Edit Secret . Drag and drop or upload your encryption token file in the Value field. The token can either be a file or text that can be copied and pasted. Click Save . Note The token can be deleted only after all the encrypted PVCs using the ceph-csi-kms-token have been deleted.

Commands:
8.4. Snapshot Previews To select which snapshot a virtual disk will be reverted to, the administrator can preview all previously created snapshots. From the available snapshots per guest, the administrator can select a snapshot volume to preview its contents. As depicted in Figure 8.3, "Preview Snapshot" , each snapshot is saved as a COW volume, and when it is previewed, a new preview layer is copied from the snapshot being previewed. The guest interacts with the preview instead of the actual snapshot volume. After the administrator previews the selected snapshot, the preview can be committed to restore the guest data to the state captured in the snapshot. If the administrator commits the preview, the guest is attached to the preview layer. After a snapshot is previewed, the administrator can select Undo to discard the preview layer of the viewed snapshot. The layer that contains the snapshot itself is preserved despite the preview layer being discarded. Figure 8.3. Preview Snapshot

Commands:
Chapter 1. Introduction to JDK Flight Recorder JDK Flight Recorder (JFR) is a low overhead framework for monitoring and profiling Java applications. For more information, see JEP 328: Flight Recorder . You can collect data from events originating within the JVM and the application code. Data is then written in memory. At first, to thread-local buffer and then promoted to fixed-size global ring buffer before being flushed to JFR files (*.jfr) on the disk. Other applications can consume these files for analysis. For example, the JDK Mission Control (JMC) tool. 1.1. JDK Flight Recorder (JFR) components You can use JFR functionality to observe events that run inside a JVM, and then create recordings from data collected from these observed events. The following list details key JFR functionality: Recordings You can manage system recordings. Each recording has a unique configuration. You can start or stop the recording, or save it to disk on demand. Events You can use events or custom events to trace your Java application's data and metadata, and then save the data and metadata from either event type in a JFR file. You can use various tools, such as Java Mission Control (JMC), jcmd , and so on, to view and analyze information stored in a JFR file. The Java Virtual Machine (JVM) has many pre-existing events that are continuously added. An API is available for users to inject custom events into their applications. You can enable or disable any event when recording to minimize overhead by supplying event configurations. These configurations take the form of xml documents and are called JFR profiles ( *.jfc ). The Red Hat build of OpenJDK comes with the following two profiles for the most common set of use cases: default : The default profile is a low-overhead configuration that is safe for continuous use in production environments. Typically, overhead is less than 1%. profile : The profile profile is a low-overhead configuration that is ideal for profiling. Typically, overhead is less than 2%. 1.2. Benefits of using JDK Flight Recorder Some of the key benefits of using JDK Flight Recorder (JFR) are: JFR allows recording on a running JVM. It is ideal to use JFR in production environments where it is difficult to restart or rebuild the application. JFR allows for the definition of custom events and metrics to monitor. JFR is built into the JVM to achieve the minimum performance overhead (around 1%). JFR uses coherent data modeling to provide better cross-referencing of events and filtering of data. JFR allows for monitoring of third-party applications using APIs. JFR helps in reducing the cost of ownership by: Spending less time diagnosing. Aiding in troubleshooting problems. JFR reduces operating costs and business interruptions by: Providing faster resolution time. Identifying the performance issues which helps in improving system efficiency.

Commands:
8.2.3. Channel Bonding Interfaces Red Hat Enterprise Linux allows administrators to bind multiple network interfaces together into a single channel using the bonding kernel module and a special network interface called a channel bonding interface. Channel bonding enables two or more network interfaces to act as one, simultaneously increasing the bandwidth and providing redundancy. To create a channel bonding interface, create a file in the /etc/sysconfig/network-scripts/ directory called ifcfg-bond <N> , replacing <N> with the number for the interface, such as 0 . The contents of the file can be identical to whatever type of interface that is getting bonded, such as an Ethernet interface. The only difference is that the DEVICE= directive must be bond <N> , replacing <N> with the number for the interface. The following is a sample channel bonding configuration file: After the channel bonding interface is created, the network interfaces to be bound together must be configured by adding the MASTER= and SLAVE= directives to their configuration files. The configuration files for each of the channel bonded interfaces can be nearly identical. For example, if channel bonding two Ethernet interfaces, both eth0 and eth1 may look like the following example: In this example, replace <N> with the numerical value for the interface. For a channel bonding interface to be valid, the kernel module must be loaded. To insure that the module is loaded when the channel bonding interface is brought up, add the following line to /etc/modprobe.conf : Once /etc/modprobe.conf is configured, and the channel bonding interface and network interfaces are configured, the ifup command can be used to bring up the channel bonding interface. Important Important aspects of the channel bonding interface are controlled through the kernel module. For more information about controlling the bonding modules, refer to Section 22.5.2, "The Channel Bonding Module" .

Commands:
DEVICE=bond0 BOOTPROTO=none ONBOOT=yes NETWORK=10.0.1.0 NETMASK=255.255.255.0 IPADDR=10.0.1.27 USERCTL=no
DEVICE=eth <N> BOOTPROTO=none ONBOOT=yes MASTER=bond0 SLAVE=yes USERCTL=no
install bond0 /sbin/modprobe bonding -o bond0