mtpti5iD/redhat-docs_dataset huggingface dataset:
8.235. system-config-keyboard 8.235.1. RHBA-2014:1617 - system-config-keyboard bug fix update Updated system-config-keyboard packages that fix one bug are now available for Red Hat Enterprise Linux 6. The system-config-keyboard packages provide a graphical user interface that allows the user to change the default keyboard of the system. Bug Fix BZ# 1136833 versions of gtk2 used a horizontal separator between the dialog contents and the buttons in GUI windows. The system-config-keyboard program was configured to remove this separator from its GUI without additional checks. With the gtk2 update, this separator was no longer displayed and system-config-keyboard instead removed the "OK" button from its GUI. With this update, system-config-keyboard has been modified to check if the item to be deleted is actually a horizontal separator. As a result, the "OK" button remains and no horizontal separator is shown, regardless of the gtk2 package version currently installed. Users of system-config-keyboard are advised to upgrade to these updated packages, which fix this bug.

Commands:
11.3. Forwarding SNMP traps It is possible to forward SNMP traps to a machine that is not part of the cluster where you can use the snmptrapd daemon on the external machine and customize how to respond to the notifications. Perform the following steps to forward SNMP traps in a cluster to a machine that is not one of the cluster nodes: For each node in the cluster, follow the procedure described in Section 11.2, "Configuring SNMP with the Red Hat High Availability Add-On" , setting the trap2sink host entry in the /etc/snmp/snmpd.conf file to specify the external host that will be running the snmptrapd daemon. On the external host that will receive the traps, edit the /etc/snmp/snmptrapd.conf configuration file to specify your community strings. For example, you can use the following entry to allow the snmptrapd daemon to process notifications using the public community string. On the external host that will receive the traps, make sure that the snmptrapd daemon is enabled and running by executing the following commands: For further information on processing SNMP notifications, see the snmptrapd.conf man page.

Commands:
authCommunity log,execute,net public
chkconfig snmptrapd on service snmptrapd start
Chapter 1. Rust Toolset Rust Toolset is a Red Hat offering for developers on Red Hat Enterprise Linux (RHEL). It provides the rustc compiler for the Rust programming language, the Rust package manager Cargo, the rustfmt formatting tool, and required libraries. For Red Hat Enterprise Linux 8, Rust Toolset is available as a module. Rust Toolset is available as packages for Red Hat Enterprise Linux 9. 1.1. Rust Toolset components The following components are available as part of Rust Toolset: Name Version Description rust 1.71.1 The Rust compiler front-end for LLVM. cargo 1.71.1 A build system and dependency manager for Rust. rustfmt 1.71.1 A tool for automatic formatting of Rust code. 1.2. Rust Toolset compatibility Rust Toolset is available for Red Hat Enterprise Linux 8 and Red Hat Enterprise Linux 9 on the following architectures: AMD and Intel 64-bit 64-bit ARM IBM Power Systems, Little Endian 64-bit IBM Z 1.3. Installing Rust Toolset Complete the following steps to install Rust Toolset including all development and debugging tools as well as dependent packages. Note that Rust Toolset has a dependency on LLVM Toolset. Prerequisites All available Red Hat Enterprise Linux updates are installed. Procedure On Red Hat Enterprise Linux 8, install the rust-toolset module by running: On Red Hat Enterprise Linux 9, install the rust-toolset package by running: 1.4. Installing Rust documentation The The Rust Programming Language book is available as installable documentation. Prerequisites Rust Toolset is installed. For more information, see Installing Rust Toolset . Procedure To install the rust-doc package, run the following command: On Red Hat Enterprise Linux 8: You can find the The Rust Programming Language book under the following path: /usr/share/doc/rust/html/index.html . You can find the API documentation for all Rust code packages under the following path: /usr/share/doc/rust/html/std/index.html . On Red Hat Enterprise Linux 9: You can find the The Rust Programming Language book under the following path: /usr/share/doc/rust/html/index.html . You can find the API documentation for all Rust code packages under the following path: /usr/share/doc/rust/html/std/index.html . 1.5. Installing Cargo documentation The Cargo, Rust's Package Manager book is available as installable documentation for Cargo. Note From Rust Toolset 1.71, the cargo-doc package is included in the rust-doc package. Prerequisites Rust Toolset is installed. For more information, see Installing Rust Toolset . Procedure To install the cargo-doc package, run: On Red Hat Enterprise Linux 8: You can find the Cargo, Rust's Package Manager book under the following path: /usr/share/doc/cargo/html/index.html . On Red Hat Enterprise Linux 9: You can find the Cargo, Rust's Package Manager book under the following path: /usr/share/doc/cargo/html/index.html . 1.6. Additional resources For more information on the Rust programming language, see the official Rust documentation .

Commands:
yum module install rust-toolset
dnf install rust-toolset
yum install rust-doc
dnf install rust-doc
yum install cargo-doc
dnf install cargo-doc
Chapter 1. Red Hat build of Keycloak Operator installation Use this procedure to install the Red Hat build of Keycloak Operator in an OpenShift cluster. Open the OpenShift Container Platform web console. In the left column, click Home , Operators , OperatorHub . Search for "Keycloak" on the search input box. Select the Operator from the list of results. Follow the instructions on the screen. For general instructions on installing Operators by using either the CLI or web console, see Installing Operators in your namespace . In the default Catalog, the Operator is named rhbk-operator . Make sure to use the channel corresponding with your desired Red Hat build of Keycloak version.

Commands:
Chapter 1. Support policy for Red Hat build of OpenJDK Red Hat will support select major versions of Red Hat build of OpenJDK in its products. For consistency, these versions remain similar to Oracle JDK versions that are designated as long-term support (LTS). A major version of Red Hat build of OpenJDK will be supported for a minimum of six years from the time that version is first introduced. For more information, see the OpenJDK Life Cycle and Support Policy . Note RHEL 6 reached the end of life in November 2020. Because of this, Red Hat build of OpenJDK is not supporting RHEL 6 as a supported configuration.

Commands:
4.8. Red Hat Virtualization 4.3 Batch Update 7 (ovirt-4.3.10) 4.8.1. Bug Fix These bugs were fixed in this release of Red Hat Virtualization: BZ# 1796136 Previously, the landing page for the RHV Manager did not support scrolling. As a result, with specific resolutions or zoom ratios, some areas of the landing page were not visible, including the link to the Administration Portal. The current release fixes this issue by enabling users to scroll the landing page and access any of the links on it. BZ# 1820642 Previously, a new DB was introduced as part of the cinderlib (managed block storage) support, but did not include a backup and restore option. The current release fixes this issue by providing a backup and restore option. BZ# 1828067 Previously, using the Administration Portal to import a storage domain omitted custom mount options for NFS storage servers. The current release fixes this issue by including the custom mount options. BZ# 1837994 Previously,creating a live snapshot with memory while LiveSnapshotPerformFreezeInEngine was set to True, resulted in a virtual machine file system that is frozen when previewing or committing the snapshot with memory restore. In this release, LiveSnapshotPerformFreezeInEngine is set to False by default, making the virtual machine run successfully after creating a preview snapshot from a memory snapshot. 4.8.2. Enhancements This release of Red Hat Virtualization features the following enhancements: BZ# 1764779 The current release adds support for installing Red Hat OpenShift Container Platform (RHOCP) version 4.4 on Red Hat Virtualization (RHV). The installer that deploys RHOCP on RHV automates the process using "installer-provisioned infrastructure." This installer is available for Linux and macOS only. The resulting RHOCP cluster runs the master and worker nodes on virtual machines in RHV. BZ# 1835929 Red Hat Virtualization now supports native 4K block size on Red Hat Gluster Storage and local storage. 4.8.3. Known Issues These known issues exist in Red Hat Virtualization at this time: BZ# 1765993 When using the REST API to restore a virtual machine snapshot, the request returns before the snapshot commit has finished. Workaround: Confirm that the commit operation has completed before attempting to restart the virtual machine.

Commands:
Chapter 1. Template APIs 1.1. BrokerTemplateInstance [template.openshift.io/v1] Description BrokerTemplateInstance holds the service broker-related state associated with a TemplateInstance. BrokerTemplateInstance is part of an experimental API. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.2. PodTemplate [v1] Description PodTemplate describes a template for creating copies of a predefined pod. Type object 1.3. Template [template.openshift.io/v1] Description Template contains the inputs needed to produce a Config. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.4. TemplateInstance [template.openshift.io/v1] Description TemplateInstance requests and records the instantiation of a Template. TemplateInstance is part of an experimental API. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object

Commands:
3.6. Saving Network Packet Filter Settings After configuring the appropriate network packet filters for your situation, save the settings so they get restored after a reboot. For iptables , type the following command: /sbin/service iptables save This saves the settings in /etc/sysconfig/iptables so they can be recalled at boot time. Once this file is written, you are able to use the /sbin/service command to start, stop, and check the status (using the status switch) of iptables . The /sbin/service will automatically load the appropriate module for you. For an example of how to use the /sbin/service command, see Section 2.3, "Starting the Piranha Configuration Tool Service" . Finally, you need to be sure the appropriate service is set to activate on the proper runlevels. For more on this, see Section 2.1, "Configuring Services on the LVS Routers" . The chapter explains how to use the Piranha Configuration Tool to configure the LVS router and describe the steps necessary to activate LVS.

Commands:
27.2.3. Configuring an At Job To schedule a one-time job for a specific time with the At utility, do the following: On the command line, type the command at TIME , where TIME is the time when the command is to be executed. The TIME argument can be defined in any of the following formats: HH : MM specifies the exact hour and minute; For example, 04:00 specifies 4:00 a.m. midnight specifies 12:00 a.m. noon specifies 12:00 p.m. teatime specifies 4:00 p.m. MONTH DAY YEAR format; For example, January 15 2012 specifies the 15th day of January in the year 2012. The year value is optional. MMDDYY , MM / DD / YY , or MM . DD . YY formats; For example, 011512 for the 15th day of January in the year 2012. now + TIME where TIME is defined as an integer and the value type: minutes, hours, days, or weeks. For example, now + 5 days specifies that the command will be executed at the same time five days from now. The time must be specified first, followed by the optional date. For more information about the time format, see the /usr/share/doc/at- <version> /timespec text file. If the specified time has past, the job is executed at the time the day. In the displayed at> prompt, define the job commands: Type the command the job should execute and press Enter . Optionally, repeat the step to provide multiple commands. Enter a shell script at the prompt and press Enter after each line in the script. The job will use the shell set in the user's SHELL environment, the user's login shell, or /bin/sh (whichever is found first). Once finished, press Ctrl + D on an empty line to exit the prompt. If the set of commands or the script tries to display information to standard output, the output is emailed to the user. To view the list of pending jobs, use the atq command. See Section 27.2.5, "Viewing Pending Jobs" for more information. You can also restrict the usage of the at command. For more information, see Section 27.2.7, "Controlling Access to At and Batch" for details.

Commands:
9.19. Installing Packages At this point there is nothing left for you to do until all the packages have been installed. How quickly this happens depends on the number of packages you have selected and your computer's speed. Depending on the available resources, you might see the following progress bar while the installer resolves dependencies of the packages you selected for installation: Figure 9.56. Starting installation Red Hat Enterprise Linux reports the installation progress on the screen as it writes the selected packages to your system. Figure 9.57. Packages completed For your reference, a complete log of your installation can be found in /root/install.log once you reboot your system. After installation completes, select Reboot to restart your computer. Red Hat Enterprise Linux ejects any loaded discs before the computer reboots.

Commands:
8.120. mysql 8.120.1. RHBA-2013:1647 - mysql bug fix update Updated mysql packages that fix several bugs are now available for Red Hat Enterprise Linux 6. MySQL is a multi-user, multi-threaded SQL database server. It consists of the MySQL server daemon (mysqld) and many client programs and libraries. Bug Fixes BZ# 842052 Prior to this update, the mysqld daemon worked with uninitialized memory when accessing non-nullable GEOMETRY types. Cosequenutly, mysqld could terminate unexpectedly when the mysqldump utility was running. With this update, mysqld initializes memory properly and thus no longer crashes in this scenario BZ# 877557 Previously, the mysqldump utility expected log tables to be created on the MySQL 5.0.x server, from which it retrieved data. Consequently, mysqldump could not dump the MySQL system table. With this update, mysqldump no longer expects log tables to be created, and it is now able to dump the system table in the described scenario as expected. BZ# 884651 Prior to this update, the mysqld init script did not correctly verify the status of the mysqld daemon. Consequently, the script could return an error message even when the daemon had successfully started. The mysqld init script has been fixed, and it now checks the daemon status properly. BZ# 904061 Previously, the mysql-server sub-packages did not contain the logrotate script. Consequently, the log rotation had to be configured manually. With this update, the logrotate script has been provided by the mysql-server sub-packages, and users can use the script to log into the mysqld.log file by uncommenting appropriate lines in the script. Users of mysql are advised to upgrade to these updated packages, which fix these bugs. After installing this update, the MySQL server daemon (mysqld) will be restarted automatically.

Commands:
Chapter 5. Validating the deployment After you successfully run the playbook, the JBoss EAP collection automatically installs JBoss EAP on your target hosts and sets up JBoss EAP as an eap service that is managed by systemd . If you have added customized tasks to the playbook, Ansible also automatically deploys any JBoss EAP applications on your target hosts, as appropriate. You can optionally check the status of JBoss EAP by using the JBoss EAP Management CLI to connect to the server. Prerequisites You have run the playbook . Procedure On your target host, launch the Management CLI and connect to the server: Note The JBoss EAP collection also includes a validate.yml playbook in the playbooks folder. You can run the validate.yml playbook if you want the JBoss EAP collection to perform automated validation checks. For more information about the validate.yml playbook, refer to the eap_validation role in Ansible automation hub . Additional resources Getting Started with the Management CLI Revised on 2024-06-14 18:23:41 UTC

Commands:
<EAP_HOME> /bin/jboss-cli.sh --connect --controller=192.168.0.1:9991
Chapter 19. Defining Access Control for IdM Users Access control is a set of security features which defines who can access certain resources, such as machines, services or entries, and what kinds of operations they are allowed to perform. Identity Management provides several access control areas to make it clear what kind of access is being granted and to whom it is granted. As part of this, Identity Management draws a distinction between access controls to resources within the domain and access control to the IdM configuration itself. For details on the different internal access control mechanisms that are available for users within IdM to the IdM server and other IdM users, see Chapter 10, Defining Access Control for IdM Users .

Commands:
Chapter 4. File Systems Support of XFS File System The default file system for an Anaconda -based installation of Red Hat Enterprise Linux 7 is now XFS , which replaces the Fourth Extended Filesystem ( ext4 ) used by default in Red Hat Enterprise Linux 6. The ext4 , ext3 and ext2 file systems can be used as alternatives to XFS . XFS is a highly scalable, high-performance file system which was originally designed at Silicon Graphics, Inc. It was created to support file systems up to 16 exabytes (approximately 16 million terabytes), files up to 8 exabytes (approximately 8 million terabytes) and directory structures containing tens of millions of entries. XFS supports metadata journaling, which facilitates quicker crash recovery. XFS file system can also be defragmented and expanded while mounted and active. Note that it is not possible to shrink XFS file system. For information about changes between commands used for common tasks in ext4 and XFS , see the Reference Table in the Installation Guide . Support of Btrfs File System The Btrfs (B-Tree) file system is supported as a Technology Preview in Red Hat Enterprise Linux 7. This file system offers advanced management, reliability, and scalability features. It enables users to create snapshots, it allows for compression and integrated device management. For more information about the Btrfs Technology Preview, see Storage Administration Guide Fast Block Devices Caching Slower Block Devices LVM provides the ability to have fast block devices act as a cache for slower block devices. This feature is introduced as a Technology Preview in Red Hat Enterprise Linux 7 and allows a PCIe SSD device to act as a cache for direct-attached storage (DAS) or storage area network (SAN) storage, which improves file system performance. For more information, refer to the LVM Cache entry in Chapter 3, Storage and the lvm(8) manual page.

Commands:
34.4. Setting up a Kerberos-aware NFS Client If the NFS clients supports only weak cryptography, such as a Red Hat Enterprise Linux 5 client, set the following entry in the /etc/krb5.conf file of the server to allow weak cryptography: If the NFS client is not enrolled as a client in the IdM domain, set up the required host entries, as described in Section 12.3, "Adding Host Entries" . Install the nfs-utils package: Obtain a Kerberos ticket before running IdM tools. Run the ipa-client-automount utility to configure the NFS settings: By default, this enables secure NFS in the /etc/sysconfig/nfs file and sets the IdM DNS domain in the Domain parameter in the /etc/idmapd.conf file. Configure the services to start automatically when the system boots: Add the following entries to the /etc/fstab file to mount the NFS shares from the nfs-server.example.com host when the system boots: These settings configure Red Hat Enterprise Linux to mount the /export share to the /mnt and the /home share to the /home directory. Create the mount points if they do not exist: Mount the NFS shares: The command uses the information from the /etc/fstab entry. Configure SSSD to renew Kerberos tickets: Set the following parameters in the IdM domain section of the /etc/sssd/sssd.conf file to configure SSSD to automatically renew tickets: Restart SSSD: Important The pam_oddjob_mkhomedir module does not support automatic creation of home directories on an NFS share. Therefore, you must manually create the home directories on the server in the root of the share that contains the home directories.

Commands:
allow_weak_crypto = true
yum install nfs-utils
kinit admin
[root@nfs-client ~] ipa-client-automount Searching for IPA server IPA server: DNS discovery Location: default Continue to configure the system with these values? [no]: yes Configured /etc/sysconfig/nfs Configured /etc/idmapd.conf Started rpcidmapd Started rpcgssd Restarting sssd, waiting for it to become available. Started autofs
systemctl enable rpc-gssd.service systemctl enable rpcbind.service
nfs-server.example.com:/export /mnt nfs4 sec=krb5p,rw nfs-server.example.com:/home /home nfs4 sec=krb5p,rw
mkdir -p /mnt/ mkdir -p /home
mount /mnt/ mount /home
[domain/EXAMPLE.COM] krb5_renewable_lifetime = 50d krb5_renew_interval = 3600
systemctl restart sssd