mtpti5iD/redhat-docs_dataset huggingface dataset:
7.240. yum 7.240.1. RHBA-2015:1384 - yum bug fix and enhancement update Updated yum package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. Yum is a utility that can check for and automatically download and install updated RPM packages. Dependencies are obtained and downloaded automatically, prompting the user for permission as necessary. Bug Fixes BZ# 893994 Yum has been updated to detect severity conflicts in the updateinfo.xml file. BZ# 905100 Previously, the "yum grouplist" command terminated unexpectedly with the "ValueError: unknown locale" message when a user-defined locale was specified on the system. With this update, "yum grouplist" has been modified to correctly process user-defined locale files, thus fixing this bug. BZ# 1016148 Under certain circumstances, when attempting to install locally stored packages, yum terminated with the following message: ValueError: your.rpm has no attribute basepath This bug has been fixed, and yum now installs local packages as expected. BZ# 1051931 Yum has been modified to properly notify the user if there is not enough space for the installed package in the installation destination. Now, the space required for the package is displayed correctly in MB or KB. BZ# 1076076 Prior to this update, yum did not show the echo output from the %postun RPM scriplet during package removal. This bug has been fixed, and the output is now displayed correctly. BZ# 1144503 Previously, the yum-plugin-downloadonly plug-in returned exit code 1 even when it executed successfully. The functionality of the plug-in has been incorporated into yum as the "--downloadonly" option. The "yum --downloadonly" command now returns the correct exit code on success. BZ# 1171543 The yum-plugin-security plug-in did not show any advisory if the architecture of the updated package changed. This bug has been fixed, and yum-plugin-security now works as expected. BZ# 1200159 Prior to this update, when epoch was defined in the rpm specification file of the kernel package, yum removed the running kernel package after updating. This bug has been fixed, and the running kernel is no longer removed in the described case. Enhancements BZ# 1154076 The "--exclude" option has been enhanced to exclude the already installed packages. BZ# 1136212 The "yum check" command has been enhanced to execute faster. BZ# 1174612 The "--assumeno" option has been backported to the yum package. Users of yum are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
10.2. Tuning Directory Server For Importing a Large Number of Entries When you import a large number of entries, operating system settings on the maximum number of user processes can limit the performance of Directory Server. To temporarily increase the maximum number of processes, enter: When a user logs off, the changes are back to the default settings. To permanently increase the maximum number of processes, see " How to set ulimit values " .

Commands:
ulimit -u 32000
14.8. Samba Distribution Programs 14.8.1. findsmb findsmb <subnet_broadcast_address> The findsmb program is a Perl script which reports information about SMB-aware systems on a specific subnet. If no subnet is specified the local subnet is used. Items displayed include IP address, NetBIOS name, workgroup or domain name, operating system, and version. The following example shows the output of executing findsmb as any valid user on a system:

Commands:
~]USD findsmb IP ADDR NETBIOS NAME WORKGROUP/OS/VERSION ------------------------------------------------------------------ 10.1.59.25 VERVE [MYGROUP] [Unix] [Samba 3.0.0-15] 10.1.59.26 STATION22 [MYGROUP] [Unix] [Samba 3.0.2-7.FC1] 10.1.56.45 TREK +[WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager] 10.1.57.94 PIXEL [MYGROUP] [Unix] [Samba 3.0.0-15] 10.1.57.137 MOBILE001 [WORKGROUP] [Windows 5.0] [Windows 2000 LAN Manager] 10.1.57.141 JAWS +[KWIKIMART] [Unix] [Samba 2.2.7a-security-rollup-fix] 10.1.56.159 FRED +[MYGROUP] [Unix] [Samba 3.0.0-14.3E] 10.1.59.192 LEGION *[MYGROUP] [Unix] [Samba 2.2.7-security-rollup-fix] 10.1.56.205 NANCYN +[MYGROUP] [Unix] [Samba 2.2.7a-security-rollup-fix]
Chapter 3. Updating Red Hat build of OpenJDK container images To ensure that an Red Hat build of OpenJDK container with Java applications includes the latest security updates, rebuild the container. Procedure Pull the base Red Hat build of OpenJDK image. Deploy the Red Hat build of OpenJDK application. For more information, see Deploying Red Hat build of OpenJDK applications in containers . The Red Hat build of OpenJDK container with the Red Hat build of OpenJDK application is updated. Additional resources For more information, see Red Hat OpenJDK Container images . Revised on 2024-05-03 15:34:48 UTC

Commands:
7.11. Creating a Cloned Virtual Machine Based on a Template Cloned virtual machines are based on templates and inherit the settings of the template. A cloned virtual machine does not depend on the template on which it was based after it has been created. This means the template can be deleted if no other dependencies exist. Note If you clone a virtual machine from a template, the name of the template on which that virtual machine was based is displayed in the General tab of the Edit Virtual Machine window for that virtual machine. If you change the name of that template, the name of the template in the General tab will also be updated. However, if you delete the template from the Manager, the original name of that template will be displayed instead. Cloning a Virtual Machine Based on a Template Click Compute Virtual Machines . Click New . Select the Cluster on which the virtual machine will run. Select a template from the Based on Template drop-down menu. Enter a Name , Description and any Comments . You can accept the default values inherited from the template in the rest of the fields, or change them if required. Click the Resource Allocation tab. Select the Clone radio button in the Storage Allocation area. Select the disk format from the Format drop-down list. This affects the speed of the clone operation and the amount of disk space the new virtual machine initially requires. QCOW2 (Default) Faster clone operation Optimized use of storage capacity Disk space allocated only as required Raw Slower clone operation Optimized virtual machine read and write operations All disk space requested in the template is allocated at the time of the clone operation Use the Target drop-down menu to select the storage domain on which the virtual machine's virtual disk will be stored. Click OK . Note Cloning a virtual machine may take some time. A new copy of the template's disk must be created. During this time, the virtual machine's status is first Image Locked , then Down . The virtual machine is created and displayed in the Virtual Machines tab. You can now assign users to it, and can begin using it when the clone operation is complete.

Commands:
5.5. Additional Resources Below are additional sources of information about proc file system. 5.5.1. Installed Documentation Below is a list of directories you can consult for more information about the proc file system. These documents are installed through the kernel-doc package. /usr/share/doc/kernel-doc- <version> /Documentation/filesystems/proc.txt - Contains assorted, but limited, information about all aspects of the /proc/ directory. /usr/share/doc/kernel-doc- <version> /Documentation/sysrq.txt - An overview of System Request Key options. /usr/share/doc/kernel-doc- <version> /Documentation/sysctl/ - A directory containing a variety of sysctl tips, including modifying values that concern the kernel ( kernel.txt ), accessing file systems ( fs.txt ), and virtual memory use ( vm.txt ). /usr/share/doc/kernel-doc- <version> /Documentation/networking/ip-sysctl.txt - A detailed overview of IP networking options.

Commands:
8.180. rhn-client-tools 8.180.1. RHBA-2013:1702 - rhn-client-tools bug fix update Updated rhn-client-tools packages that fix several bugs are now available for Red Hat Enterprise Linux 6. Red Hat Network Client Tools provide programs and libraries that allow the system to receive software updates from Red Hat Network (RHN). Bug Fixes BZ# 891746 Previously, the rhn-channel manual page incorrectly referred to the "--username" option instead of "--user". This mistake has been corrected and the rhn-channel manual page now correctly refers to the "--user" option. BZ# 912984 Prior to this update, some messages written in English occurred in the Japanese installation of Red Hat Enterprise Linux 6.4. The untranslated strings have been translated, and the messages are now shown in the correct language. BZ# 983999 Previously, the rhn-client-tools code called by the sosreport utility on Red Hat Enterprise Linux 6 terminated unexpectedly with a traceback. The bug has been fixed and and the information about hardware is now correctly gathered by sosreport. BZ# 994531 Previously, a machine with many CPUs could report large value for idle time for all its processors. Consequently, the idle time value did not fit into XML-RPC's integer limits and running the rhn_check command on a problematic machine resulted in a traceback error. The bug has been fixed and rhn_check in the problematic scenarios works now correctly. BZ# 997637 Previously, the rhn-profile-sync utility terminated unexpectedly with a traceback when an older version of the rhn-virtualization-host package was installed on the machine. The bug has been fixed by requiring a newer version of rhn-virtualization-host. Users of rhn-client-tools are advised to upgrade to these updated packages, which fix these bugs. 8.180.2. RHBA-2013:1087 - rhn-client-tools bug fix and enhancement update Updated rhn-client-tools packages that fix one bug and add one enhancement are now available. Red Hat Network Client Tools provide programs and libraries that allow systems to receive software updates from Red Hat Network (RHN). Bug Fix BZ#949648 The RHN Proxy did not work properly if separated from a parent by a slow enough network. Consequently, users who attempted to download larger repodata files and RPMs experienced timeouts. This update changes both RHN Proxy and Red Hat Enterprise Linux RHN Client to allow all communications to obey a configured timeout value for connections. Enhancement BZ# 949640 While Satellite 5.3.0 now has the ability to get the number of CPUs via an API call, there was no function to obtain the number of sockets from the registered systems. This update adds a function to get the number of physical CPU sockets in a managed system from Satellite via an API call. Users of rhn-client-tools are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
B.2. iSCSI Disks During Start Up Events related to iSCSI might occur at a number of points while the system is starting: The init script in the initrd will log into iSCSI targets used for / , if any. This is done using the iscsistart utility, without requiring iscsid to run. Note If the root file system is on an iSCSI disk connected using IPv6, ensure that the installed system is using the correct ip= boot option, for example ip=eth0:auto6 . If this option is not set, the installed system can spend up to 20 minutes at boot time attempting to establish a connection, before eventually succeeding. Using the correct ip= option eliminates this delay. When the root file system has been mounted and the various service init scripts are running, the iscsi init script will get called. This script then starts the iscsid daemon if any iSCSI targets are used for / , or if any targets in the iSCSI database are marked to be logged into automatically. After the classic network service script has been run, the iscsi init script will run. If the network is accessible, this will log into any targets in the iSCSI database that are marked to be logged into automatically. If the network is not accessible, this script will exit quietly. When using NetworkManager to access the network, instead of the classic network service script, NetworkManager will call the iscsi init script. Also see the /etc/NetworkManager/dispatcher.d/04-iscsi file for further reference. Important Because NetworkManager is installed in the /usr directory, you cannot use it to configure network access if /usr is on network-attached storage such as an iSCSI target. If iscsid is not needed as the system starts, it will not start automatically. If you start iscsiadm , iscsiadm will start iscsid in turn.

Commands:
RPM Packaging Guide Red Hat Enterprise Linux 7 Basic and advanced software packaging scenarios using the RPM package manager Customer Content Services rhel-notes@redhat.com Marie Dolezelova Red Hat Customer Content Services mdolezel@redhat.com Maxim Svistunov Red Hat Customer Content Services Adam Miller Red Hat Adam Kvitek Red Hat Customer Content Services Petr Kovar Red Hat Customer Content Services Miroslav Suchy Red Hat

Commands:
Chapter 5. Reviewing the pre-conversion analysis report using Insights To assess whether your CentOS Linux systems can be converted to RHEL, run the Pre-conversion analysis for converting to RHEL task. The pre-conversion analysis generates a report that summarizes potential problems and suggests recommended solutions. The report also helps you decide whether it is possible or advisable to proceed with the conversion to RHEL. Prerequisites You have completed the steps listed in Preparing for a RHEL conversion using Insights . Procedure Log in to the Red Hat Hybrid Cloud Console and go to Red Hat Enterprise Linux > Insights for RHEL > Automation toolkit > Tasks . Locate the Pre-conversion analysis for converting to RHEL task and click Select systems . Alternatively, log in to the Red Hat Hybrid Cloud Console , go to Red Hat Enterprise Linux > Insights for RHEL > Inventory > Systems , choose a system you want to convert and click Convert system to RHEL label. In the Task name field type the name of the task and select the CentOS Linux 7 systems that you want to analyze for conversion. Click . Configure the pre-conversion analysis task with the following settings: Do not use the ELS subscription Choose this option if you plan to upgrade your RHEL system to version 8 or higher. Allow kernel modules outside of RHEL repositories on the system Choose this option to allow the pre-conversion analysis to ignore kernel modules that are not part of RHEL repositories. Allow outdated kernel on the system Choose this option to allow the pre-conversion analysis to ignore when your system is booted from an outdated kernel. Allow outdated packages on the system Choose this option to allow the pre-conversion analysis to ignore all outdated packages on the system. Click Run task . The pre-conversion analysis can take up to an hour to complete. The pre-conversion analysis utility generates a new report in the Activity tab. Select the report to view a summary of issues found in each system. You can also review further by selecting a system to view each issue and, when applicable, a potential remediation in detail. Each issue is assigned a severity level: Inhibitor Would cause the conversion to fail because it is very likely to result in a deteriorated system state. You must resolve this issue before converting. Overridable inhibitor Would cause the conversion to fail because it is very likely to result in a deteriorated system state. You must resolve or manually override this issue before converting. For more details about which inhibitors you can override, see the step about configuring the settings of the pre-conversion analysis in this procedure. Skipped Could not run this test because of a prerequisite test failing. Could cause the conversion to fail. Warning Would not cause the conversion to fail. System and application issues might occur after the conversion. Info Informational with no expected impact to the system or applications. After reviewing the report and resolving all reported issues, click Run task again to rerun the analysis and confirm that there are no issues outstanding.

Commands:
Chapter 1. Getting started overview Use Red Hat AMQ Streams to create and set up Kafka clusters, then connect your applications and services to those clusters. This guide describes how to install and start using AMQ Streams on OpenShift Container Platform. You can install the AMQ Streams operator directly from the OperatorHub in the OpenShift web console. The AMQ Streams operator understands how to install and manage Kafka components. Installing from the OperatorHub provides a standard configuration of AMQ Streams that allows you to take advantage of automatic updates. When the AMQ Streams operator is installed, it provides the resources to install instances of Kafka components. After installing a Kafka cluster, you can start producing and consuming messages. Note If you require more flexibility with your deployment, you can use the installation artifacts provided with AMQ Streams. For more information on using the installation artifacts, see Deploying and Upgrading AMQ Streams on OpenShift . 1.1. Prerequsites The following prerequisites are required for getting started with AMQ Streams. You have a Red Hat account. JDK 11 or later is installed. An OpenShift 4.12 and later cluster is available. The OpenShift oc command-line tool is installed and configured to connect to the running cluster. The steps to get started are based on using the OperatorHub in the OpenShift web console, but you'll also use the OpenShift oc CLI tool to perform certain operations. You'll need to connect to your OpenShift cluster using the oc tool. You can install the oc CLI tool from the web console by clicking the '?' help menu, then Command Line Tools . You can copy the required oc login details from the web console by clicking your profile name, then Copy login command . 1.2. Additional resources Strimzi Overview Deploying and Upgrading AMQ Streams on OpenShift

Commands:
4.101. iscsi-initiator-utils 4.101.1. RHBA-2011:1722 - iscsi-initiator-utils bug fix and enhancement update An updated iscsi-initiator-utils package that fixes one bug and adds various enhancements is now available for Red Hat Enterprise Linux 6. The iscsi package provides the server daemon for the Internet Small Computer System Interface (iSCSI) protocol, as well as the utility programs used to manage it. iSCSI is a protocol for distributed disk access using SCSI commands sent over Internet Protocol networks. Bug Fix BZ# 715434 The iscsiadm utility displayed the discovery2 mode in the help output but did not accept the mode as a valid one. This entry has been replaced with the valid discoverydb mode entry as displayed in the ISCSIADM(8) manual page. Enhancements BZ# 602959 The brcm_iscsiuio daemon did not rotate its log file, /var/log/brcm-iscsi.log. As a consequence, the log file may have filled up the available disk space. The brcm_iscsiuio daemon now supports log rotation, which fixes the problem. BZ# 696808 The brcm_iscsiuio daemon has been updated to provide enhanced support for IPv6 (Internet Protocol version 6), VLAN (Virtual Local Area Network), and Broadcom iSCSI Offload Engine Technology. The daemon has been renamed to iscsiuio with this update. BZ# 749051 The bnx2i driver can now be used for install or boot. To install or boot to targets using this driver, turn on the HBA (Host Bus Adapter) mode in the card's BIOS boot setup screen. In addition, the iSCSI tools can now set up networking and manage sessions for QLogic iSCSI adapters that use the qla4xxx driver. For more information, see section 5.1.2 of the README file which is located in the /usr/share/doc/iscsi-initiator-utils-6.2.0.872 directory. Users are advised to upgrade to this updated iscsi-initiator-utils package, which fixes this bug and adds these enhancements.

Commands:
7.120. libsoup 7.120.1. RHBA-2013:0313 - libsoup bug fix update Updated libsoup packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The libsoup packages provide an HTTP client and server library for GNOME. Bug Fixes BZ# 657622 Prior to this update, the clock-applet did not handle canceled requests during a DNS lookup correctly and accessed already freed memory. As a consequence, the weather view of the clock-applet could, under certain circumstances, abort with a segmentation fault when updating the weather if the hostname of the weather server needed more than 30 seconds, for example due to network problems. This update modifies the underlying code to allow requests that take too long to be canceled. BZ#746587 Prior to this update, the weather view of the clock-applet tried to connect to the weather server indefinitely as fast as it could if the weather server (or an HTTP proxy) closed the connection without responding. This update modifies the underlying code to retry a request only if the server unexpectedly closes a previously-used connection, not a new connection. Now, libsoup returns a "Connection terminated unexpectedly" error, so the clock-applet does not update the weather display, and tries again later. All users of libsoup are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 13. Determining whether manual activation of the subscriptions service is necessary The subscriptions service must be activated to begin tracking usage for the Red Hat account for your organization. The activation process can be automatic or manual. Procedure Review the following tasks that activate the subscriptions service automatically. If someone in your organization has completed one or more of these tasks, manual activation of the subscriptions service is not needed. Purchasing a pay-as-you-go On-Demand subscription for Red Hat OpenShift Container Platform or Red Hat OpenShift Dedicated through Red Hat Marketplace. As the pay-as-you-go clusters begin reporting usage through OpenShift Cluster Manager and the monitoring stack, the subscriptions service activates automatically for the organization. Purchasing an Red Hat OpenShift pay-as-you-go On-Demand subscription through a cloud provider marketplace, such as Red Hat Marketplace or Amazon Web Services (AWS). Examples of these types of products include Red Hat OpenShift AI or Red Hat Advanced Cluster Security for Kubernetes. As these products begin reporting usage through the monitoring stack, the subscriptions service activates automatically for the organization. Creating an Amazon Web Services integration through the integrations service in the Hybrid Cloud Console with the RHEL management bundle selected. The process of creating the integration also activates the subscriptions service. Creating a Microsoft Azure integration through the integrations service in the Hybrid Cloud Console with the RHEL management bundle selected. The process of creating the integration also activates the subscriptions service. Note The integrations service was formerly known as the {SourcesName} service in the Hybrid Cloud Console. These tasks, especially purchasing tasks, might be performed by a user that has the Organization Administrator (org admin) role in the Red Hat organization for your company. The integration creation tasks must be performed by a user with the Cloud administrator role in the role-based access control (RBAC) system for the Hybrid Cloud Console.

Commands: