mtpti5iD/redhat-docs_dataset huggingface dataset:
3.3. Managing Groups via the User Manager Application 3.3.1. Viewing Groups In order to display the main window of User Manager to view groups, from the toolbar select Edit Preferences . If you want to view all the groups, clear the Hide system users and groups check box. The Groups tab provides a list of local groups with information about their group ID and group members as you can see in the picture below. Figure 3.3. Viewing Groups To find a specific group, type the first few letters of the name in the Search filter field and either press Enter , or click the Apply filter button. You can also sort the items according to any of the available columns by clicking the column header.

Commands:
9.18.2. Rescue Mode Rescue mode provides the ability to boot a small Red Hat Enterprise Linux environment entirely from boot media or some other boot method instead of the system's hard drive. There may be times when you are unable to get Red Hat Enterprise Linux running completely enough to access files on your system's hard drive. Using rescue mode, you can access the files stored on your system's hard drive, even if you cannot actually run Red Hat Enterprise Linux from that hard drive. If you need to use rescue mode, try the following method: Boot an x86, AMD64, or Intel 64 system from any installation medium, such as CD, DVD, USB, or PXE, and type linux rescue at the installation boot prompt. Refer to Chapter 36, Basic System Recovery for a more complete description of rescue mode. For additional information, refer to the Red Hat Enterprise Linux Deployment Guide .

Commands:
8.23. crash 8.23.1. RHEA-2013:1565 - crash enhancement update Updated crash packages that add various enhancements are now available for Red Hat Enterprise Linux 6. The crash packages provide a self-contained tool that can be used to investigate live systems and kernel core dumps created from the netdump, diskdump, kdump, and Xen/KVM "virsh dump" facilities from Red Hat Enterprise Linux. Enhancements BZ# 902141 Currently, dump files created by the makedumpfile utility using the snappy compression format are now readable by the crash utility. The snappy format is suitable for the crash dump mechanism that requires stable performance in any situation with enterprise application use. BZ# 902144 With this update, dump files created by the makedumpfile utility using the LZO compression format are now readable by the crash utility. The LZO compression format is fast and stable for randomized data. BZ# 1006622 This update adds support for compressed dump files created by the makedumpfile utility that were generated on systems with physical memory requiring more than 44 bits. BZ# 1017930 This update fixes faulty panic-task backtraces generated by the bt command in KVM guest dump files. The bt command now shows a trace when the guest operating system is panicking. BZ# 1019483 This update fixes the CPU number display on systems with 255 or more CPUs during the initialization, by the set command, the ps command, and by all commands that display the per-task header consisting of the task address, PID, CPU and command name. Without the patch, for CPU 255, the sys command displays "NO_PROC_ID", and the other commands show a "-" for the CPU number; for CPU numbers greater than 255, garbage values would be displayed in the CPU number field. Users of crash are advised to upgrade to these updated packages, which add these enhancements.

Commands:
7.19. RHEA-2014:1471 - new package: scap-security-guide A new scap-security-guide package is now available for Red Hat Enterprise Linux 6. The scap-security-guide package provides a SCAP Security Guide (SSG) project's guide for configuration of the system from the final system's security point of view. The guidance is specified in the Security Content Automation Protocol (SCAP) format and constitutes a catalog of practical hardening advice, linked to government requirements where applicable. The project bridges the gap between generalized policy requirements and specific implementation guidelines. The Red Hat Enterprise Linux 6 system administrator can use the oscap command-line tool from the openscap-utils package to verify that the system conforms to the provided guideline. For further information. see the scap-security-guide(8) manual page. This enhancement update adds the scap-security-guide package to Red Hat Enterprise Linux 6. (BZ#1066390) All users who require scap-security-guide are advised to install this new package.

Commands:
Chapter 8. Updated Packages 8.1. abrt 8.1.1. RHBA-2013:1586 - abrt, libreport and btparser bug fix and enhancement update Updated abrt, libreport, and btparser packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. ABRT is a tool to help users to detect defects in applications and to create a problem report with all the information needed by a maintainer to fix it. ABRT uses a plug-in system to extend its functionality. The libreport libraries provide an API for reporting different problems in applications to different bug targets like Bugzilla, ftp, and trac. The btparser utility is a backtrace parser and analyzer library, which works with backtraces produced by the GNU Project Debugger. It can parse a text file with a backtrace to a tree of C structures, allowing to analyze the threads and frames of the backtrace and process them. Bug Fixes BZ# 854668 If the /etc/abrt/abrt.conf file was modified so that the "DumpLocation" and "WatchCrashdumpArchiveDir" variables referred to the same directory, the ABRT utility tried to process the files in that directory as both archives and new problem directories, which led to unpredictable results. With this update, ABRT refuses to start if such misconfiguration is detected. BZ# 896090 While creating a case, the reporter-rhtsupport utility sent the operation system (OS) version value which RHT customer center server did not accept. Consequently, a new case failed to be created and an error message was returned. With this update, suffixes such as "Beta" in the OS version value are not stripped, RHT customer center server accepts the version value, and a case is created. BZ# 952773 Prior to this update, the abrt-watch-log and abrt-dump-oops utilities were creating too many new problem directories when a kernel error occurred periodically. As a consequence, the user was flooded with problem reports and the /var partition could overflow. To fix this bug, abrt-dump-oops has been changed to ignore all additional problems for a few minutes after it sees 5 or more of them. As a result, the user is not flooded with problem reports. Enhancements BZ# 952704 The Red Hat Support tool required an API for querying crashes caught by ABRT. With this update, python API for ABRT has been provided and it is now possible to use python API to query bugs caught by ABRT. BZ# 961231 There is a high probability that users who do not use the graphical environment (headless systems) will miss the problems detected by the ABRT utility. When the user installs the abrt-console-notification packages, they now see a warning message in the console regarding new problems detected since the last login. All users of abrt, libreport and btparser are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Part II. Deploying Red Hat build of Kogito microservices on Red Hat OpenShift Container Platform As a developer of business decisions and processes, you can deploy Red Hat build of Kogito microservices on Red Hat OpenShift Container Platform for cloud implementation. The RHPAM Kogito Operator automates many of the deployment steps for you or guides you through the deployment process. Prerequisites Red Hat OpenShift Container Platform 4.6 or 4.7 is installed. The OpenShift project for the deployment is created.

Commands:
Chapter 1. Power monitoring for Red Hat OpenShift release notes Important Power monitoring is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . Power monitoring for Red Hat OpenShift enables you to monitor the power usage of workloads and identify the most power-consuming namespaces running in an OpenShift Container Platform cluster with key power consumption metrics, such as CPU or DRAM, measured at container level. These release notes track the development of power monitoring for Red Hat OpenShift in the OpenShift Container Platform. For an overview of the Power monitoring Operator, see About power monitoring . 1.1. Power monitoring 0.3 (Technology Preview) This release includes the following version updates: Kepler 0.7.12 Power monitoring Operator 0.15.0 The following advisory is available for power monitoring 0.3: RHEA-2024:9961 1.1.1. Bug fixes Before this update, the Power monitoring Operator dashboard used an invalid Prometheus rule, which caused the panel for OTHER Power Consumption(W) by Pods to display incorrect data. With this update, the rule is corrected, ensuring the dashboard now shows accurate power consumption data. 1.1.2. CVEs CVE-2023-37920 CVE-2024-2236 CVE-2024-2511 CVE-2024-3596 CVE-2024-4603 CVE-2024-4741 CVE-2024-5535 CVE-2024-34397 1.2. Power monitoring 0.2 (Technology Preview) This release includes the following version updates: Kepler 0.7.10 Power monitoring Operator 0.13.0 The following advisory is available for power monitoring 0.2: RHEA-2024:2923 1.2.1. Features With this update, you can enable the Redfish API in Kepler. Kepler uses Redfish to get the power consumed by nodes. With this update, you can install the Power monitoring Operator in the namespace of your choice. With this update, you can access the power monitoring Overview dashboard from the Developer perspective. 1.2.2. CVEs CVE-2022-48554 CVE-2023-2975 CVE-2023-3446 CVE-2023-3817 CVE-2023-5678 CVE-2023-6129 CVE-2023-6237 CVE-2023-7008 CVE-2024-0727 CVE-2024-25062 CVE-2024-28834 CVE-2024-28835 1.3. Power monitoring 0.1 (Technology Preview) This release introduces a Technology Preview version of power monitoring for Red Hat OpenShift. The following advisory is available for power monitoring 0.1: RHEA-2024:0078 1.3.1. Features Deployment and deletion of Kepler Power usage metrics from Intel-based bare-metal deployments Dashboards for plotting power usage

Commands:
Chapter 5. Installing Red Hat build of OpenJDK with the MSI installer This procedure discribes how to install Red Hat build of OpenJDK 8 for Microsoft Windows using the MSI-based installer. Procedure Download the MSI-based installer of Red Hat build of OpenJDK 8 for Microsoft Windows. Run the installer Red Hat build of OpenJDK 8 for Microsoft Windows. Click on the welcome screen. Check I accept the terms in license agreement , then click . Click . Accept the defaults or review the optional properties . Click Install . Click Yes on the Do you want to allow this app to make changes on your device? . Verify the Red Hat build of OpenJDK 8 for Microsoft Windows is successfully installed, run java -version command in the command prompt and you must get the following output:

Commands:
java version "1.8.0_181" Java(TM) SE Runtime Environment (build 1.8.0_181-b13) Java HotSpot(TM) 64-Bit Server VM (build 25.181-b13, mixed mode)
8.110. man-pages-fr 8.110.1. RHBA-2013:1093 - man-pages-fr bug fix update Updated man-pages-fr packages that fix one bug are now available. The man-pages-fr packages contain manual pages in French. Bug Fix BZ# 903048 Due to some problem in the build system of the French manual page package man-pages-fr, some manual pages were not included in the package. Some manual pages, for example the manual page of "echo" were displayed in English even when the system was running in a French locale. Thus, the command "man echo" displayed an English manual page. The build problem in the man-pages-fr package is fixed, and the missing manual pages are now included. Hence, manual pages are now displayed in French when the system is running in a French locale, for example "man echo" now shows a French manual page. Users of man-pages-fr are advised to upgrade to these updated packages, which fixes this bug.

Commands:
Chapter 2. Deleting a collection on automation hub You can further manage your collections by deleting unwanted collections, provided that the collection is not dependent on other collections. Click the Dependencies tab on a collection to see a list of other collections that uses the current collection. Prerequisites The collection being deleted does not have dependencies with other collections. You have Delete Collections permissions Procedure Log in to Red Hat Ansible Automation Platform. Navigate to Automation Hub Collections . Click a collection to delete. Click then select an option: Delete entire collection to delete all versions in this collection. Delete version [number] to delete the current version of this collection. You can change versions using the Version dropdown menu. Note If the selected collection has any dependencies with other collections, these actions will be unavailable to you until you delete those dependencies. Click the Dependencies tab to see a list of dependencies to delete before you proceed. When the confirmation window appears, verify that the collection or version number is correct, then click the checkbox Delete .

Commands:
Chapter 3. Prerequisite For the solution to work, the following requirements must be met. All nodes must have the same: number of CPUs and RAM software configuration RHEL release firewall settings SAP HANA release (SAP HANA 2.0 SPS04 or later) The pacemaker packages are only installed on the cluster nodes and must use the same version of resource-agents-sap-hana (0.162.1 or later). To be able to support SAP HANA Multitarget System Replication , refer to Add SAP HANA Multitarget System Replication autoregister support . Also, set the following: use register_secondaries_on_takeover=true use log_mode=normal The initial setup is based on the installation guide, Automating SAP HANA Scale-Up System Replication using the RHEL HA Add-On . The system replication configuration of all SAP HANA instances is based on SAP requirements. For more information, refer to the guidelines from SAP based on the SAP HANA Administration Guide .

Commands:
8.4.2. The KSM Tuning Service The ksmtuned service fine-tunes the kernel same-page merging (KSM) configuration by looping and adjusting ksm . In addition, the ksmtuned service is notified by libvirt when a guest virtual machine is created or destroyed. The ksmtuned service has no options. The ksmtuned service can be tuned with the retune parameter, which instructs ksmtuned to run tuning functions manually. The /etc/ksmtuned.conf file is the configuration file for the ksmtuned service. The file output below is the default ksmtuned.conf file: Within the /etc/ksmtuned.conf file, npages sets how many pages ksm will scan before the ksmd daemon becomes inactive. This value will also be set in the /sys/kernel/mm/ksm/pages_to_scan file. The KSM_THRES_CONST value represents the amount of available memory used as a threshold to activate ksm . ksmd is activated if either of the following occurs: The amount of free memory drops below the threshold, set in KSM_THRES_CONST . The amount of committed memory plus the threshold, KSM_THRES_CONST , exceeds the total amount of memory.

Commands:
systemctl start ksmtuned Starting ksmtuned: [ OK ]
Configuration file for ksmtuned. How long ksmtuned should sleep between tuning adjustments KSM_MONITOR_INTERVAL=60 Millisecond sleep between ksm scans for 16Gb server. Smaller servers sleep more, bigger sleep less. KSM_SLEEP_MSEC=10 KSM_NPAGES_BOOST - is added to the `npages` value, when `free memory` is less than `thres`. KSM_NPAGES_BOOST=300 KSM_NPAGES_DECAY - is the value given is subtracted to the `npages` value, when `free memory` is greater than `thres`. KSM_NPAGES_DECAY=-50 KSM_NPAGES_MIN - is the lower limit for the `npages` value. KSM_NPAGES_MIN=64 KSM_NPAGES_MAX - is the upper limit for the `npages` value. KSM_NPAGES_MAX=1250 KSM_THRES_COEF - is the RAM percentage to be calculated in parameter `thres`. KSM_THRES_COEF=20 KSM_THRES_CONST - If this is a low memory system, and the `thres` value is less than `KSM_THRES_CONST`, then reset `thres` value to `KSM_THRES_CONST` value. KSM_THRES_CONST=2048 uncomment the following to enable ksmtuned debug information LOGFILE=/var/log/ksmtuned DEBUG=1
Chapter 9. Using the config tool to reconfigure Red Hat Quay on OpenShift Container Platform As of Red Hat Quay 3.10, the configuration tool has been removed on OpenShift Container Platform deployments, meaning that users cannot configure, or reconfigure, directly from the OpenShift Container Platform console. Additionally, the quay-config-editor pod no longer deploys, users cannot check the status of the config editor route, and the Config Editor Endpoint no longer generates on the Red Hat Quay Operator Details page As a workaround, you can deploy the configuration tool locally and create your own configuration bundle. This includes entering the database and storage credentials used for your Red Hat Quay on OpenShift Container Platform deployment, generating a config.yaml file, and using it to deploy Red Hat Quay on OpenShift Container Platform via the command-line interface. To deploy the configuration tool locally, see Getting started with Red Hat Quay and follow the instructions up to "Configuring Red Hat Quay". Advanced configuration settings, such as using custom SSL certificates, can be found on the same page. steps Red Hat Quay features

Commands:
B.18. dracut B.18.1. RHEA-2011:0141 - dracut enhancement update Updated dracut packages that add an enhancement are now available for Red Hat Enterprise Linux 6. The dracut packages provide an event-driven initramfs generator infrastructure based around udev. The initramfs is loaded together with the kernel at boot time and initializes the system, so it can read and boot from the root partition. Enhancement BZ# 661298 The dracut packages have been updated to support the new kernel boot option, "rdinsmodpost=[module]", which allows a user to specify a kernel module to be loaded after all device drivers are loaded automatically. Users of dracut are advised to upgrade to these updated packages, which add this enhancement.

Commands:
22.17. Configuring the Hardware Clock Update To configure the system clock to update the hardware clock, also known as the real-time clock (RTC), once after executing ntpdate , add the following line to /etc/sysconfig/ntpdate : To update the hardware clock from the system clock, issue the following command as root : When the system clock is being synchronized by ntpd , the kernel will in turn update the RTC every 11 minutes automatically.

Commands:
SYNC_HWCLOCK=yes
~]# hwclock --systohc
Chapter 2. Backing up storage data from Google Persistent Disk Red Hat recommends that you back up the data on your persistent volume claims (PVCs) regularly. Backing up your data is particularly important before deleting a user and before uninstalling OpenShift AI, as all PVCs are deleted when OpenShift AI is uninstalled. Prerequisites You have credentials for OpenShift Cluster Manager ( https://console.redhat.com/openshift/ ). You have administrator access to the OpenShift Dedicated cluster. You have credentials for the Google Cloud Platform (GCP) account that the OpenShift Dedicated cluster is deployed under. Procedure Determine the IDs of the persistent volumes (PVs) that you want to back up. In the OpenShift Dedicated web console, change into the Administrator perspective. Click Home Projects . Click the rhods-notebooks project. The Details page for the project opens. Click the PersistentVolumeClaims in the Inventory section. The PersistentVolumeClaims page opens. Note the ID of the persistent volume (PV) that you want to back up. The persistent volume (PV) IDs are required to identify the correct persistent disk to back up in your GCP instance. Locate the persistent disk containing the PVs that you want to back up. Log in to the Google Cloud console ( https://console.cloud.google.com ) and ensure that you are viewing the region that your OpenShift Dedicated cluster is deployed in. Click the navigation menu (≡) and then click Compute Engine . From the side navigation, under Storage , click Disks . The Disks page opens. In the Filter query box, enter the ID of the persistent volume (PV) that you made a note of earlier. The Disks page reloads to display the search results. Click on the disk shown and verify that any kubernetes.io/created-for/pvc/namespace tags contain the value rhods-notebooks , and any kubernetes.io/created-for/pvc/name tags match the name of the persistent volume that the persistent disk is being used for, for example, jupyterhub-nb-user1-pvc . Back up the persistent disk that contains your persistent volume (PV). Select CREATE SNAPSHOT from the top navigation. The Create a snapshot page opens. Enter a unique Name for the snapshot. Under Source disk , verify the persistent disk you want to back up is displayed. Change any optional settings as needed. Click CREATE . The snapshot of the persistent disk is created. Verification The snapshot that you created is visible on the Snapshots page in GCP. Additional resources Google Cloud documentation: Create and manage disk snapshots

Commands:
Chapter 1. Software management tools in Red Hat Enterprise Linux 8 In Red Hat Enterprise Linux (RHEL) 8, use YUM to manage software. YUM is based on the DNF technology, which adds support for modular features. Note Upstream documentation identifies the technology as DNF , and the tool is referred to as DNF . As a result, some output returned by the new YUM tool in RHEL 8 mentions DNF . Although YUM is based on DNF , it is compatible with YUM used in RHEL 7. For software installation, the yum command and most of its options work the same way in RHEL 8 as they did in RHEL 7. Selected YUM plug-ins and utilities have been ported to the new DNF back end and can be installed under the same names as in RHEL 7. Packages also provide compatibility symlinks. Therefore, you can find binaries, configuration files, and directories in usual locations. Note The legacy Python API provided by YUM in RHEL 7 is no longer available. You can migrate your plug-ins and scripts to the new DNF Python API provided by YUM in RHEL 8. For more information, see DNF API Reference .

Commands:
7.279. xorg-x11-drv-ati 7.279.1. RHBA-2013:0302 - xorg-x11-drv-ati bug fix and enhancement update Updated xorg-x11-drv-ati packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-ati packages provide a driver for ATI graphics cards for the X.Org implementation of the X Window System. Note The xorg-x11-drv-ati packages have been upgraded to upstream version 6.99.99, which provides a number of bug fixes and enhancements over the version. (BZ#835218) All users of xorg-x11-drv-ati are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: