mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 50. Configuring 802.3 link settings Auto-negotiation is a feature of the IEEE 802.3u Fast Ethernet protocol. It targets the device ports to provide an optimal performance of speed, duplex mode, and flow control for information exchange over a link. Using the auto-negotiation protocol, you have optimal performance of data transfer over the Ethernet. Note To utilize maximum performance of auto-negotiation, use the same configuration on both sides of a link. 50.1. Configuring 802.3 link settings using the nmcli utility To configure the 802.3 link settings of an Ethernet connection, modify the following configuration parameters: 802-3-ethernet.auto-negotiate 802-3-ethernet.speed 802-3-ethernet.duplex Procedure Display the current settings of the connection: You can use these values if you need to reset the parameters in case of any problems. Set the speed and duplex link settings: This command enables auto-negotiation and sets the speed of the connection to 10000 Mbit full duplex. Reactivate the connection: Verification Use the ethtool utility to verify the values of Ethernet interface enp1s0 : Additional resources nm-settings(5) man page on your system

Commands:
nmcli connection show Example-connection 802-3-ethernet.speed: 0 802-3-ethernet.duplex: -- 802-3-ethernet.auto-negotiate: no
nmcli connection modify Example-connection 802-3-ethernet.auto-negotiate yes 802-3-ethernet.speed 10000 802-3-ethernet.duplex full
nmcli connection up Example-connection
ethtool enp1s0 Settings for enp1s0: Speed: 10000 Mb/s Duplex: Full Auto-negotiation: on Link detected: yes
Chapter 9. Enforcing Puppet Configuration on Managed Hosts You can enforce configuration from Satellite either manually on demand (run once) or automatically in configurable intervals. 9.1. Running Puppet Once Using SSH Assign the proper job template to the Run Puppet Once feature to run Puppet on managed hosts. Procedure In the Satellite web UI, navigate to Administer > Remote Execution Features . Select the puppet_run_host remote execution feature. Assign the Run Puppet Once - SSH Default job template. Run Puppet on managed hosts by running a job and selecting category Puppet and template Run Puppet Once - SSH Default . Alternatively, click the Run Puppet Once button in the Schedule Remote Job drop down menu on the host details page. 9.2. Understanding Intervals of Automatic Enforcement Satellite considers hosts to be out of sync if the last Puppet report is older than the combined values of outofsync_interval and puppet_interval set in minutes. By default, the Puppet agent on managed hosts runs every 30 minutes, the puppet_interval is set to 35 minutes and the global outofsync_interval is set to 30 minutes. The effective time after which hosts are considered out of sync is the sum of outofsync_interval and puppet_interval . For example, setting the global outofsync_interval to 30 and the puppet_interval to 60 results in a total of 90 minutes after which the host status changes to out of sync . 9.3. Setting the Puppet Agent Run Interval on a Host Set the interval when the Puppet agent runs and sends reports to Satellite. Procedure Connect to your managed host using SSH. Add the Puppet agent run interval to /etc/puppetlabs/puppet/puppet.conf , for example runinterval = 1h . 9.4. Setting the Global Out-of-Sync Interval Procedure In the Satellite web UI, navigate to Administer > Settings . On the General tab, edit Out of sync interval . Set a duration, in minutes, after which hosts are considered to be out of sync. You can also override this interval on host groups or individual hosts by adding the outofsync_interval parameter. 9.5. Setting the Puppet Out-of-Sync Interval Procedure In the Satellite web UI, navigate to Administer > Settings , and click the Config Management tab. In the Puppet interval field, set the value to the duration, in minutes, after which hosts reporting using Puppet are considered to be out of sync. 9.6. Overriding Out-of-Sync Interval for a Host Group Procedure In the Satellite web UI, navigate to Configure > Host Groups . Select a host group. On the Parameters tab, click Add Parameter . In the Name field, enter outofsync_interval . From the Type dropdown menu, select integer . In the Value field, enter the new interval in minutes. Click the Submit button. 9.7. Overriding Out-of-Sync Interval for an Individual Host Procedure In the Satellite web UI, navigate to Hosts > All Hosts . Click Edit for a selected host. On the Parameters tab, click Add Parameter . In the Name field, enter outofsync_interval . From the Type dropdown menu, select integer . In the Value field, enter the new interval in minutes. Click the Submit button.

Commands:
D.22. Connections View The Connections View provides a quick overview and management of Connection Profiles and Deployed Data Sources. When the Local Profiles section is marked, add button opens the wizard for creating a new Connection Profile. When the Deployed section is marked, add button opens the wizard for creating a new Data Source. Figure D.34. Connections View Connections View contains these buttons: Create a new Data Source or Connection Profile Delete marked Data Source or Connection Profile Edit marked Data Source or Connection Profile Refresh profiles and deployed data sources The Connections View also contains Default Server panel which is described in the Server Version Status Panel section.

Commands:
Chapter 1. 3scale API Management general configuration options As a Red Hat 3scale API Management administrator, there are general configuration options available to you in your installation or account to adjust settings. 1.1. Configuring a valid login session length As a Red Hat 3scale API Management administrator, you can configure a valid login session length for the Admin Portal and the Developer Portal so there is a limit for maximum timeout and inactivity. To implement a valid login session length you must set USER_SESSION_TTL to seconds. For example 1,800 seconds is 30 minutes. If the value is null , that is, not set, or is set to an empty string, the session default length is for 2 weeks. Prerequisites A 3scale account with administrator privileges. Procedure Update the USER_SESSION_TTL value in the system-app secret in seconds: USD oc patch secret system-app -p '{"stringData": {"USER_SESSION_TTL": "'1800'"}}' Rollout system-app : USD oc rollout restart deployment/system-app

Commands:
oc patch secret system-app -p '{"stringData": {"USER_SESSION_TTL": "'1800'"}}'
oc rollout restart deployment/system-app
7.3. File Systems 7.3.1. The Ext4 File System The ext4 file system is a scalable extension of the default ext3 file system available in Red Hat Enterprise Linux 5. Ext4 is now the default file system for Red Hat Enterprise Linux 6, and is supported for a maximum file system size of 16 TB and a single file maximum size of 16TB. It also removes the 32000 sub-directory limit present in ext3. Note For file systems larger than 16TB, we recommend using a scalable high capacity file system such as XFS. For further information, see Section 7.3.2, "The XFS File System" . The ext4 file system defaults are optimal for most workloads, but if performance analysis shows that file system behavior is impacting performance, several tuning options are available: Inode table initialization For very large file systems, the mkfs.ext4 process can take a very long time to initialize all inode tables in the file system. This process can be deferred with the -E lazy_itable_init=1 option. If this is used, kernel processes will continue to initialize the file system after it is mounted. The rate at which this initialization occurs can be controlled with the -o init_itable=n option for the mount command, where the amount of time spent performing this background initialization is roughly 1/n. The default value for n is 10 . Auto-fsync behavior Because some applications do not always properly fsync() after renaming an existing file, or truncating and rewriting, ext4 defaults to automatic syncing of files after replace-via-rename and replace-via-truncate operations. This behavior is largely consistent with older ext3 filesystem behavior. However, fsync() operations can be time consuming, so if this automatic behavior is not required, use the -o noauto_da_alloc option with the mount command to disable it. This will mean that the application must explicitly use fsync() to ensure data persistence. Journal I/O priority By default, journal commit I/O is given a slightly higher priority than normal I/O. This priority can be controlled with the journal_ioprio=n option of the mount command. The default value is 3 . Valid values range from 0 to 7, with 0 being the highest priority I/O. For other mkfs and tuning options, please see the mkfs.ext4(8) and mount(8) man pages, as well as the Documentation/filesystems/ext4.txt file in the kernel-doc package.

Commands:
8.151. perl-XML-Dumper 8.151.1. RHBA-2013:0838 - perl-XML-Dumper bug fix update An updated perl-XML-Dumper package that fixes one bug is now available for Red Hat Enterprise Linux 6. The perl-XML-Dumper package provides the XML::Dumper module that allows converting Perl objects to XML format. XML::Dumper can also read XML data that was previously dumped by the module and convert it back to Perl objects. To ensure their correct behavior, the Perl objects should be converted and reconstituted in the same environment. When installed along with the Compress::Zlib module, XML::Dumper can also dump data to, and read data from, a compressed file with the ".xml.gz" extension. Bug Fix BZ# 652833 The XML::Dumper module could not be used due to a missing dependency to the XML::Parser module. This update adds the required dependency to the perl-XML-Dumper spec file and XML::Dumper can now be used as expected. Users of perl-XML-Dumper are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 6. Notable changes to containers A set of container images is available for Red Hat Enterprise Linux (RHEL) 8.0. Notable changes include: Docker is not included in RHEL 8.0. For working with containers, use the podman , buildah , skopeo , and runc tools. For information on these tools and on using containers in RHEL 8, see Building, running, and managing containers . The podman tool has been released as a fully supported feature. The podman tool manages pods, container images, and containers on a single node. It is built on the libpod library, which enables management of containers and groups of containers, called pods. To learn how to use podman , see Building, running, and managing containers . In RHEL 8 GA, Red Hat Universal Base Images (UBI) are newly available. UBIs replace some of the images Red Hat previously provided, such as the standard and the minimal RHEL base images. Unlike older Red Hat images, UBIs are freely redistributable. This means they can be used in any environment and shared anywhere. You can use them even if you are not a Red Hat customer. For UBI documentation, see Building, running, and managing containers . In RHEL 8 GA, additional container images are available that provide AppStream components, for which container images are distributed with Red Hat Software Collections in RHEL 7. All of these RHEL 8 images are based on the ubi8 base image. Container images ARM for the 64-bit ARM architecture are fully supported in RHEL 8. The rhel-tools container has been removed in RHEL 8. The sos and redhat-support-tool tools are provided in the support-tools container. System administrators can also use this image as a base for building system tools container image. The support for rootless containers is available as a technology preview in RHEL 8. Rootless containers are containers that are created and managed by regular system users without administrative permissions.

Commands:
Chapter 10. Application failover between managed clusters This section provides instructions on how to failover the busybox sample application. The failover method for Regional-DR is application based. Each application that is to be protected in this manner must have a corresponding DRPlacementControl resource and a PlacementRule resource created in the application namespace as shown in the Create Sample Application for DR testing section. Procedure On the Hub cluster navigate to Installed Operators and then click Openshift DR Hub Operator . Click DRPlacementControl tab. Click DRPC busybox-drpc and then the YAML view. Add the action and failoverCluster details as shown in below screenshot. The failoverCluster should be the ACM cluster name for the Secondary managed cluster. DRPlacementControl add action Failover Click Save . Verify that the application busybox is now running in the Secondary managed cluster, the failover cluster ocp4perf2 specified in the YAML file. Example output: Verify that busybox is no longer running on the Primary managed cluster. Example output: Important Be aware of known Regional-DR issues as documented in Known Issues section of Release Notes. If you need assistance with developer preview features, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on availability and work schedules.

Commands:
oc get pods,pvc -n busybox-sample
NAME READY STATUS RESTARTS AGE pod/busybox 1/1 Running 0 35s NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE persistentvolumeclaim/busybox-pvc Bound pvc-79f2a74d-6e2c-48fb-9ed9-666b74cfa1bb 5Gi RWO ocs-storagecluster-ceph-rbd 35s
oc get pods,pvc -n busybox-sample
No resources found in busybox-sample namespace.
Appendix B. Revision History Revision History Revision 1-0.2 2015-02-25 Laura Bailey Rebuild with sort_order Revision 1-0.1.400 2013-10-31 Rudiger Landmann Rebuild with publican 4.0.0 Revision 1-0.1 Tue Dec 6 2011 Martin Prpic Release of the Red Hat Enterprise Linux 6.2 Release Notes

Commands:
Chapter 9. Certified SAP applications on RHEL 8 SAP Max DB 7.9.10.02 and later (See SAP Note 1444241 ) SAP ASE 16 (See SAP Note 2489781 ) SAP HANA 2.0 SPS04 and later (See SAP Note 2235581 ) SAP BI 4.3 and later (See SAP Note 1338845 ) SAP NetWeaver (See SAP Note 2772999 ) In general, SAP documents support of their products for certain versions of Red Hat Linux Enterprise in their SAP Product Availability Matrix .

Commands:
Chapter 4. Advisories related to this release The following advisories are issued to document bug fixes and CVE fixes included in this release: RHSA-2023:1875 RHSA-2023:1877 RHSA-2023:1878 RHSA-2023:1880 RHSA-2023:1882 RHSA-2023:1883 RHSA-2023:1889 RHSA-2023:1892 RHSA-2023:1895 RHSA-2023:1899 Revised on 2024-05-09 16:47:23 UTC

Commands:
5.192. mingw32-matahari 5.192.1. RHBA-2012:0984 - mingw32-matahari bug fix update An updated mingw32-matahari package that fixes one bug is now available for Red Hat Enterprise Linux 6. This package includes Matahari Qpid Management Framework (QMF) Agents for Windows guests. QMF Agent can be used to control and manage various pieces of functionality for an ovirt node, using the Advanced Message Queuing Protocol (AMQP) protocol. Bug Fix BZ# 806948 Previously, Matahari depended on libqpidclient and libqpidcommon. As a result, Qpid's APIs using libqpidclient and libqpidcommon did not have stable ABI and rebuilding Qpid negatively affected mingw32-matahari. With this update, the dependencies have been removed, thus fixing this bug. All mingw32-matahari users are advised to upgrade to this updated package, which fixes this bug.

Commands:
7.7. Searching the Audit Log Files The ausearch utility allows you to search Audit log files for specific events. By default, ausearch searches the /var/log/audit/audit.log file. You can specify a different file using the ausearch options -if file_name command. Supplying multiple options in one ausearch command is equivalent to using the AND operator. Example 7.6. Using ausearch to search Audit log files To search the /var/log/audit/audit.log file for failed login attempts, use the following command: To search for all account, group, and role changes, use the following command: To search for all logged actions performed by a certain user, using the user's login ID ( auid ), use the following command: To search for all failed system calls from yesterday up until now, use the following command: For a full listing of all ausearch options, see the ausearch (8) man page.

Commands:
~]# ausearch --message USER_LOGIN --success no --interpret
~]# ausearch -m ADD_USER -m DEL_USER -m ADD_GROUP -m USER_CHAUTHTOK -m DEL_GROUP -m CHGRP_ID -m ROLE_ASSIGN -m ROLE_REMOVE -i
~]# ausearch -ua 500 -i
~]# ausearch --start yesterday --end now -m SYSCALL -sv no -i
Part VI. Installing and configuring KIE Server on Oracle WebLogic Server Red Hat Decision Manager is a subset of Red Hat Process Automation Manager. Starting with this release, the distribution files for Red Hat Decision Manager are replaced with Red Hat Process Automation Manager files. There are no Decision Manager artifacts. The Red Hat Decision Manager subscription, support entitlements, and fees remain the same. Red Hat Decision Manager subscribers will continue to receive full support for the decision management and optimization capabilities of Red Hat Decision Manager. The business process management (BPM) capabilities of Red Hat Process Automation Manager are exclusive to Red Hat Process Automation Manager subscribers. They are available for use by Red Hat Decision Manager subscribers but with development support services only. Red Hat Decision Manager subscribers can upgrade to a full Red Hat Process Automation Manager subscription at any time to receive full support for BPM features. As a system administrator, you can configure your Oracle WebLogic Server for Red Hat KIE Server and install KIE Server on that Oracle server instance. Note Support for Red Hat Decision Manager on Oracle WebLogic Server is now in the maintenance phase. Red Hat will continue to support Red Hat Decision Manager on Oracle WebLogic Server with the following limitations: Red Hat will not release new certifications or software functionality. Red Hat will release only qualified security patches that have a critical impact and mission-critical bug fix patches. In the future, Red Hat might direct customers to migrate to new platforms and product components that are compatible with the Red Hat hybrid cloud strategy. Prerequisites An Oracle WebLogic Server instance version 12.2.1.3.0 or later is installed. For complete installation instructions, see the Oracle WebLogic Server product page . You have access to the Oracle WebLogic Server Administration Console, usually at http://<HOST>:7001/console .

Commands:
Chapter 5. Configuring compliance policy deployment methods Use one the following procedures to configure Satellite for the method that you have selected to deploy compliance policies. You will select one of these methods when you later create a compliance policy . Procedure for Ansible deployment Import the theforeman.foreman_scap_client Ansible role. For more information, see Managing configurations using Ansible integration . Assign the created policy and the theforeman.foreman_scap_client Ansible role to a host or host group. To trigger the deployment, run the Ansible role on the host or host group either manually, or set up a recurring job by using remote execution for regular policy updates. For more information, see Configuring and Setting Up Remote Jobs in Managing hosts . Procedure for Puppet deployment Ensure Puppet is enabled. Ensure the Puppet agent is installed on hosts. Import the Puppet environment that contains the foreman_scap_client Puppet module. For more information, see Managing configurations using Puppet integration . Assign the created policy and the foreman_scap_client Puppet class to a host or host group. Puppet triggers the deployment on the regular run or you can run Puppet manually. Puppet runs every 30 minutes by default. Procedure for manual deployment For the manual deployment method, no additional Satellite configuration is required. For information on manual deployment, see How to set up OpenSCAP Policies using Manual Deployment option in the Red Hat Knowledgebase .

Commands:
B.70. polkit B.70.1. RHSA-2011:0455 - Important: polkit security update Updated polkit packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. PolicyKit is a toolkit for defining and handling authorizations. CVE-2011-1485 A race condition flaw was found in the PolicyKit pkexec utility and polkitd daemon. A local user could use this flaw to appear as a privileged user to pkexec, allowing them to execute arbitrary commands as root by running those commands with pkexec. Red Hat would like to thank Neel Mehta of Google for reporting this issue. All polkit users should upgrade to these updated packages, which contain backported patches to correct this issue. The system must be rebooted for this update to take effect.

Commands:
Chapter 24. Troubleshooting Installation on IBM System z This section discusses some common installation problems and their solutions. For debugging purposes, anaconda logs installation actions into files in the /tmp directory. These files include: /tmp/anaconda.log general anaconda messages /tmp/program.log all external programs run by anaconda /tmp/storage.log extensive storage module information /tmp/yum.log yum package installation messages /tmp/syslog hardware-related system messages If the installation fails, the messages from these files are consolidated into /tmp/anaconda-tb- identifier , where identifier is a random string. All of the files above reside in the installer's ramdisk and are thus volatile. To make a permanent copy, copy those files to another system on the network using scp on the installation image (not the other way round). 24.1. You Are Unable to Boot Red Hat Enterprise Linux 24.1.1. Is Your System Displaying Signal 11 Errors? A signal 11 error, commonly known as a segmentation fault , means that the program accessed a memory location that was not assigned to it. A signal 11 error may be due to a bug in one of the software programs that is installed, or faulty hardware. Ensure that you have the latest installation updates and images from Red Hat. Review the online errata to see if newer versions are available.

Commands:
4.343. vte 4.343.1. RHBA-2011:1204 - vte bug fix update An updated vte package that fixes one bug is now available for Red Hat Enterprise Linux 6. VTE is a terminal emulator widget for use with GTK+ 2.0. Bug Fix BZ# 658774 Previously, setting a cursor color was not working properly in that a terminal (text) cursor was invisible in some applications which used vte. With this update, the bug has been fixed so that the cursor is now rendered properly and is visible as expected. All vte users are advised to upgrade to this updated package, which fixes this bug.

Commands: