mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 23. New Drivers Network Drivers Thunderbolt network driver (thunderbolt-net.ko.xz). AMD 10 Gigabit Ethernet Driver (amd-xgbe.ko.xz). Storage Drivers Command Queue Host Controller Interface driver (cqhci.ko.xz). Graphics Drivers and Miscellaneous Drivers DRM GPU scheduler (gpu-sched.ko.xz). Closed hash table (chash.ko.xz). RMI4 SMBus driver (rmi_smbus.ko.xz). RMI bus. RMI F03 module (rmi_core.ko.xz). Dell WMI descriptor driver (dell-wmi-descriptor.ko.xz). Intel(R) PMC Core Driver (intel_pmc_core.ko.xz). Intel(R) WMI Thunderbolt force power driver (intel-wmi-thunderbolt.ko.xz). ACPI Hardware Watchdog (WDAT) driver (wdat_wdt.ko.xz). IIO helper functions for setting up triggered buffers (industrialio-triggered-buffer.ko.xz). HID Sensor Pressure (hid-sensor-press.ko.xz). HID Sensor Device Rotation (hid-sensor-rotation.ko.xz). HID Sensor Inclinometer 3D (hid-sensor-incl-3d.ko.xz). HID Sensor trigger processing (hid-sensor-trigger.ko.xz). HID Sensor common attribute processing (hid-sensor-iio-common.ko.xz). HID Sensor Magnetometer 3D (hid-sensor-magn-3d.ko.xz). HID Sensor ALS (hid-sensor-als.ko.xz). HID Sensor Proximity (hid-sensor-prox.ko.xz). HID Sensor Gyroscope 3D (hid-sensor-gyro-3d.ko.xz). HID Sensor Accel 3D (hid-sensor-accel-3d.ko.xz). HID Sensor Hub driver (hid-sensor-hub.ko.xz). HID Sensor Custom and Generic sensor driver (hid-sensor-custom.ko.xz).

Commands:
30.5. Modifying sudo Commands and Command Groups Modifying sudo Commands and Command Groups in the Web UI Under the Policy tab, click Sudo Sudo Commands or Sudo Sudo Command Groups . Click the name of the command or command group to display its configuration page. Change the settings as required. On some configuration pages, the Save button is available at the top of the page. On these pages, you must click the button to confirm the changes. Modifying sudo Commands and Command Groups from the Command Line To modify a command or command group, use the following commands: ipa sudocmd-mod ipa sudocmdgroup-mod Add command-line options to the above-mentioned commands to update the sudo command or command group attributes. For example, to add a new description for the /usr/bin/less command: For more information about these commands and the options they accept, run them with the --help option added.

Commands:
ipa sudocmd-mod /usr/bin/less --desc="For reading log files" ------------------------------------- Modified Sudo Command "/usr/bin/less" ------------------------------------- Sudo Command: /usr/bin/less Description: For reading log files Sudo Command Groups: files
Chapter 3. Red Hat Enterprise Linux AI hardware requirements Various hardware accelerators require different requirements for serving and inferencing as well as installing, generating and training the granite-7b-starter model on Red Hat Enterprise Linux AI. 3.1. Hardware requirements for end-to-end workflow of Granite models The following charts show the hardware requirements for running the full InstructLab end-to-end workflow to customize the Granite student model. This includes: synthetic data generation (SDG), training, and evaluating a custom Granite model. 3.1.1. Bare metal Hardware vendor Supported accelerators (GPUs) Aggregate GPU memory Recommended additional disk storage NVIDIA 2xA100 4xA100 8xA100 160 GB 320 GB 640 GB 1 TB NVIDIA 2xH100 4xH100 8xH100 160 GB 320 GB 640 GB 1 TB NVIDIA 4xL40S 8xL40S 192 GB 384 GB 1 TB 3.1.2. Amazon Web Services (AWS) Hardware vendor Supported accelerators (GPUs) Aggregate GPU Memory AWS Instance Recommended additional disk storage NVIDIA 8xA100 640 GB p4de.24xlarge 1 TB NVIDIA 8xH100 640 GB p5.48xlarge 1 TB 3.2. Hardware requirements for inference serving Granite models The following charts display the minimum hardware requirements for inference serving a model on Red Hat Enterprise Linux AI. 3.2.1. Bare metal Hardware vendor Supported accelerators (GPUs) minimum Aggregate GPU memory Recommended additional disk storage NVIDIA A100 80 GB 1 TB NVIDIA H100 80 GB 1 TB NVIDIA L40S 48 GB 1 TB NVIDIA L4 24 GB 1 TB 3.2.2. Amazon Web Services (AWS) Hardware vendor Supported accelerators (GPUs) Minimum Aggregate GPU Memory Recommended additional disk storage NVIDIA A100 80 GB 1 TB NVIDIA H100 80 GB 1 TB NVIDIA L40S 48 GB 1 TB NVIDIA L4 24 GB 1 TB 3.2.3. IBM cloud Hardware vendor Supported accelerators (GPUs) Minimum Aggregate GPU Memory Recommended additional disk storage NVIDIA L40S 48 GB 1 TB NVIDIA L4 24 GB 1 TB

Commands:
28.3. Disabling Anonymous Binds Accessing domain resources and running client tools always require Kerberos authentication. However, the backend LDAP directory used by the IdM server allows anonymous binds by default. This potentially opens up all of the domain configuration to unauthorized users, including information about users, machines, groups, services, netgroups, and DNS configuration. It is possible to disable anonymous binds on the 389 Directory Server instance by using LDAP tools to reset the nsslapd-allow-anonymous-access attribute. Change the nsslapd-allow-anonymous-access attribute to rootdse . Important Anonymous access can be completely allowed (on) or completely blocked (off). However, completely blocking anonymous access also blocks external clients from checking the server configuration. LDAP and web clients are not necessarily domain clients, so they connect anonymously to read the root DSE file to get connection information. The rootdse allows access to the root DSE and server configuration without any access to the directory data. Restart the 389 Directory Server instance to load the new setting.

Commands:
ldapmodify -x -D "cn=Directory Manager" -w secret -h server.example.com -p 389 Enter LDAP Password: dn: cn=config changetype: modify replace: nsslapd-allow-anonymous-access nsslapd-allow-anonymous-access: rootdse
service dirsrv restart
Chapter 5. Upgrading from RHEL 7.9 to RHEL 8 Similarly to the in-place upgrade from RHEL 6 to RHEL 7, the in-place upgrade from RHEL 7 to RHEL 8 consists of two major stages, a pre-upgrade assessment of the system in which the system remains unchanged, and the actual in-place upgrade. In case of a RHEL 7 to RHEL 8 upgrade, both phases are handled by the Leapp utility. Note that RHEL version 7.9 is a prerequisite for upgrading to RHEL 8. To perform an in-place upgrade from RHEL 7.9 to RHEL 8: Assess the upgradability of your system and fix reported problems as described in Reviewing the pre-upgrade report of the Upgrading from RHEL 7 to RHEL 8 document. Upgrade your RHEL 7 system to RHEL 8 per instructions in Performing the upgrade from RHEL 7 to RHEL 8 of the Upgrading from RHEL 7 to RHEL 8 document. Additional resources Troubleshooting in the Upgrading from RHEL 7 to RHEL 8 document

Commands:
8.22. biosdevname 8.22.1. RHBA-2014:1459 - biosdevname bug fix and enhancement update Updated biosdevname packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The biosdevname packages contain an optional convention for naming network interfaces; it assigns names to network interfaces based on their physical location. Biosdevname is disabled by default, except for a limited set of Dell PowerEdge, C Series, and Precision Workstation systems. Note The biosdevname packages have been upgraded to upstream version 0.5.1, which provides a number of bug fixes and enhancements over the version. (BZ# 1053492 ) Users of biosdevname are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Preface 1.1. About Red Hat Gluster Storage Red Hat Gluster Storage is a software-only, scale-out storage solution that provides flexible and agile unstructured data storage for the enterprise. Red Hat Gluster Storage provides new opportunities to unify data storage and infrastructure, increase performance, and improve availability and manageability in order to meet a broader set of an organization's storage challenges and needs. The product can be installed and managed on-premises, or in a public cloud.

Commands:
Chapter 15. The Football Quickstart Endpoint Examples The Football application is a simple example to illustrate the use of Red Hat JBoss Data Grid endpoints, namely Hot Rod, REST, and Memcached. Each example shows one of these protocols used to connect to JBoss Data Grid to remotely store, retrieve, and remove data from caches. Each application is a variation of a simple football team manager utility as a console application. Features The following features are available with the example Football Manager application: Add a team Add players Remove all entities (teams and players) Listing all teams and players Location JBoss Data Grid's Football quickstart can be found at the following locations: jboss-datagrid-{VERSION}-quickstarts/rest-endpoint jboss-datagrid-{VERSION}-quickstarts/hotrod-endpoint jboss-datagrid-{VERSION}-quickstarts/memcached-endpoint Report a bug 15.1. Quickstart Prerequisites The prerequisites for this quickstart are as follows: Java 6.0 (Java SDK 1.6) or better JBoss Enterprise Application Platform 6.x or JBoss Enterprise Web Server 2.x Maven 3.0 or better Configure the Maven Repository. For details, see Chapter 3, Install and Use the Maven Repositories Report a bug

Commands:
7.203. strace 7.203.1. RHBA-2015:1308 - strace bug fix and enhancement update Updated strace packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The strace utility intercepts and records the system calls that are made and received by a running process and prints a record of each system call, its arguments, and its return value to standard error output or a file. It is often used for problem diagnoses, debugging, and for instructional purposes. Note The strace packages have been upgraded to upstream version 4.8, which provides a number of bug fixes and enhancements over the version. (BZ# 919101 , BZ# 1056828 ) Bug Fixes BZ# 919101 , BZ# 1056828 This update adds several new command-line options: "-y" to print file descriptor paths, "-P" to filter system calls based on the file descriptor paths, and "-I" to control how interactive strace is. A new command-line utility, strace-log-merge, has been added. This utility can be used to merge timestamped strace output into a single file. The strace utility now uses optimized interfaces to extract data from the traced process for better performance. The strace utility now provides improved support for decoding of arguments for various system calls. In addition, a number of new system calls are supported. BZ# 877193 Previously, the strace utility incorrectly handled the return value from the shmat() system call. Consequently, the return value displayed was "?" instead of the address of the attached shared memory segment. This bug has been fixed, and strace now displays the correct return value for the shmat() system calls. Users of strace are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
8.139. papi 8.139.1. RHBA-2013:1587 - papi bug fix and enhancement update Updated papi packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. PAPI (Performance Application Programming Interface) is a software library that provides access to the processor's performance-monitoring hardware. This allows developers to track performance-related events, such as cache misses, instructions retired, and clock cycles, to better understand the performance issues of the software. Note The papi packages have been upgraded to upstream version 5.1.1, which provides a number of bug fixes and enhancements over the version, including support for Intel Xeon Processor E5-XXXX v2 architecture. (BZ# 831751 ) Bug Fixes BZ# 740909 Due to missing dependencies in the makefile, a parallel rebuild of the PAPI library failed. With this update, new rules have been added to the makefile to address this problem. As a result, PAPI can be successfully rebuild in the described scenario. BZ# 785258 Previously, when Hyper-threading was enabled on the Intel Xeon Processor E5-XXXX node, the PAPI libary could not configure the performance-monitoring hardware to count floating-point operations. This bug has been fixed and the aforementioned error no longer occurs. BZ# 883475 Due to an incorrect ldconfig setting in the papi.spec file, papi failed to be rebuilt from the srpm file when the process was executed by the root user. With this update, the underlying source code has been modified to fix this bug. BZ# 883766 Previously, the papi package failed to be built from the srpm file when a version of papi was installed. During the build, the new version of papi attempted to link to the libpfm.so file of the previously installed papi-devel package, which caused papi to terminate unexpectedly. With this update, a patch has been introduced to reorder the sequence of file linking during the build, so that the locally built files are used first. As a result, papi is built correctly with version installed. Enhancements BZ# 726798 , BZ# 831751 , BZ# 947622 Support for the Intel Xeon Processor E5-XXXX and Intel Xeon Processor E5-XXXX architectures has been added to the PAPI library. BZ# 743648 Support for access to various energy and performance registers through PAPI has been added. BZ# 785975 With this update, several minor grammatical errors have been corrected in the PAPI interface. BZ# 866590 The papi-static subpackage has been added to provide the libraries for static linking. BZ# 910163 The papi-testsuite subpackage has been added to allow testing of papi. All users of papi are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
4.3. Growing a File System on a Logical Volume To grow a file system on a logical volume, perform the following steps: Make a new physical volume. Extend the volume group that contains the logical volume with the file system you are growing to include the new physical volume. Extend the logical volume to include the new physical volume. Grow the file system. If you have sufficient unallocated space in the volume group, you can use that space to extend the logical volume instead of performing steps 1 and 2.

Commands:
10.2.4.3. The mod_proxy Module Proxy access control statements are now placed inside a <Proxy> block rather than a <Directory proxy:> . The caching functionality of the old mod_proxy has been split out into the following three modules: mod_cache mod_disk_cache mod_mem_cache These generally use directives similar to the older versions of the mod_proxy module, but it is advisable to verify each directive before migrating any cache settings. For more on this topic, refer to the following documentation on the Apache Software Foundation's website: http://httpd.apache.org/docs-2.0/mod/mod_proxy.html

Commands:
Chapter 1. Compatibility Matrix for Red Hat Ceph Storage 8.0 The following tables list products and their versions compatible with Red Hat Ceph Storage 8.0. Host Operating System Version Red Hat Enterprise Linux 9.4, 9.5 Standard lifecycle RHEL is included in the product. Important All nodes in the cluster and their clients must use the supported OS version(s) to ensure that the version of the ceph package is the same on all nodes. Using different versions of the ceph package is not supported. Note For Client RPM packages, Red Hat Ceph Storage 8.0 only supports Red Hat Enterprise Linux 9. The cluster bootstrap node must be Red Hat Enterprise Linux 9. Product Version Notes Ansible Supported in a limited capacity. Supported for upgrade and conversion to Cephadm and for other minimal playbooks. Red Hat OpenShift Data Foundation See the Red Hat OpenShift Data Foundation Supportability and Interoperability Checker for detailed external mode version compatibility. Red Hat OpenStack Platform 18.0.3 or later Supports Red Hat Ceph Storage when externally deployed. Red Hat Satellite 6.x Only registering with the Content Delivery Network (CDN) is supported. Registering with Red Hat Network (RHN) is deprecated and not supported. Client Connector Version Notes S3A 2.8.x, 3.2.x, and trunk Red Hat Ceph Storage as a backup target Version Notes CommVault Cloud Data Management v11 IBM Spectrum Protect Plus 10.1.5 IBM Spectrum Protect server 8.1.8 NetApp AltaVault 4.3.2 and 4.4 Rubrik Cloud Data Management (CDM) 3.2 onwards Trilio, TrilioVault 3.0 S3 target Veeam (object storage) Veeam Availability Suite 9.5 Update 4 Supported on Red Hat Ceph Storage object storage with the S3 protocol Veritas NetBackup for Symantec OpenStorage (OST) cloud backup 7.7 and 8.0 Independent Software vendors Version Notes IBM Spectrum Discover 2.0.3 WekaIO 3.12.2

Commands:
Chapter 6. LVM Troubleshooting This chapter provide instructions for troubleshooting a variety of LVM issues. 6.1. Troubleshooting Diagnostics If a command is not working as expected, you can gather diagnostics in the following ways: Use the -v , -vv , -vvv , or -vvvv argument of any command for increasingly verbose levels of output. If the problem is related to the logical volume activation, set 'activation = 1' in the 'log' section of the configuration file and run the command with the -vvvv argument. After you have finished examining this output be sure to reset this parameter to 0, to avoid possible problems with the machine locking during low memory situations. Run the lvmdump command, which provides an information dump for diagnostic purposes. For information, see the lvmdump (8) man page. Execute the lvs -v , pvs -a or dmsetup info -c command for additional system information. Examine the last backup of the metadata in the /etc/lvm/backup file and archived versions in the /etc/lvm/archive file. Check the current configuration information by running the lvm dumpconfig command. Check the .cache file in the /etc/lvm directory for a record of which devices have physical volumes on them.

Commands:
14.8.17. testparm testparm <options> <filename> <hostname IP_address> The testparm program checks the syntax of the smb.conf file. If your smb.conf file is in the default location ( /etc/samba/smb.conf ) you do not need to specify the location. Specifying the hostname and IP address to the testparm program verifies that the hosts.allow and host.deny files are configured correctly. The testparm program also displays a summary of your smb.conf file and the server's role (stand-alone, domain, etc.) after testing. This is convenient when debugging as it excludes comments and concisely presents information for experienced administrators to read. For example:

Commands:
~]# testparm Load smb config files from /etc/samba/smb.conf Processing section "[homes]" Processing section "[printers]" Processing section "[tmp]" Processing section "[html]" Loaded services file OK. Server role: ROLE_STANDALONE Press enter to see a dump of your service definitions <enter> Global parameters [global] workgroup = MYGROUP server string = Samba Server security = SHARE log file = /var/log/samba/%m.log max log size = 50 socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192 dns proxy = No [homes] comment = Home Directories read only = No browseable = No [printers] comment = All Printers path = /var/spool/samba printable = Yes browseable = No [tmp] comment = Wakko tmp path = /tmp guest only = Yes [html] comment = Wakko www path = /var/www/html force user = andriusb force group = users read only = No guest only = Yes
Chapter 29. Best practices for automation controller The following describes best practice for the use of automation controller: 29.1. Use Source Control Automation controller supports playbooks stored directly on the server. Therefore, you must store your playbooks, roles, and any associated details in source control. This way you have an audit trail describing when and why you changed the rules that are automating your infrastructure. Additionally, it permits sharing of playbooks with other parts of your infrastructure or team. 29.2. Ansible file and directory structure If you are creating a common set of roles to use across projects, these should be accessed through source control submodules, or a common location such as /opt . Projects should not expect to import roles or content from other projects. For more information, see the link General tips from the Ansible documentation. Note Avoid using the playbooks vars_prompt feature, as automation controller does not interactively permit vars_prompt questions. If you cannot avoid using vars_prompt , see the Surveys in job templates functionality. Avoid using the playbooks pause feature without a timeout, as automation controller does not permit canceling a pause interactively. If you cannot avoid using pause , you must set a timeout. Jobs use the playbook directory as the current working directory, although jobs must be coded to use the playbook_dir variable rather than relying on this. 29.3. Use Dynamic Inventory Sources If you have an external source of truth for your infrastructure, whether it is a cloud provider or a local CMDB, it is best to define an inventory sync process and use the support for dynamic inventory (including cloud inventory sources). This ensures your inventory is always up to date. Note Edits and additions to Inventory host variables persist beyond an inventory synchronization as long as --overwrite_vars is not set. 29.4. Variable Management for Inventory Keep variable data with the hosts and groups definitions (see the inventory editor), rather than using group_vars/ and host_vars/ . If you use dynamic inventory sources, automation controller can synchronize such variables with the database as long as the Overwrite Variables option is not set. 29.5. Autoscaling Use the "callback" feature to permit newly booting instances to request configuration for auto-scaling scenarios or provisioning integration. 29.6. Larger Host Counts Set "forks" on a job template to larger values to increase parallelism of execution runs. 29.7. Continuous integration / Continuous Deployment For a Continuous Integration system, such as Jenkins, to spawn a job, it must make a curl request to a job template. The credentials to the job template must not require prompting for any particular passwords. For configuration and use instructions, see Installation in the Ansible documentation.

Commands:
31.9. Additional Resources For more information on kernel modules and their utilities, see the following resources. Installed Documentation lsmod(8) - The manual page for the lsmod command. modinfo(8) - The manual page for the modinfo command. modprobe(8) > - The manual page for the modprobe command. rmmod(8) - The manual page for the rmmod command. ethtool(8) - The manual page for the ethtool command. mii-tool(8) - The manual page for the mii-tool command. Installable Documentation /usr/share/doc/kernel-doc- <kernel_version> /Documentation/ - This directory, which is provided by the kernel-doc package, contains information on the kernel, kernel modules, and their respective parameters. Before accessing the kernel documentation, you must run the following command as root: Online Documentation - The Red Hat Knowledgebase article Which bonding modes work when used with a bridge that virtual machine guests connect to?

Commands:
~]# yum install kernel-doc
3.23. RHEA-2011:1625 - new package: wdaemon A new wdaemon package is now available for Red Hat Enterprise Linux 6. The new wdaemon package contains a daemon to wrap input driver hotplugging in the X.Org implementation of the X Window System server. The wdaemon package emulates virtual input devices to avoid otherwise non-persistent configuration of Wacom tablets to persist across device removals. This enhancement update adds the wdaemon package to Red Hat Enterprise Linux 6. All users who require wdaemon should install this new package.

Commands: