mtpti5iD/redhat-docs_dataset huggingface dataset:
24.2.2. Saving Traceback Messages If anaconda encounters an error during the graphical installation process, it presents you with a crash reporting dialog box: Figure 24.1. The Crash Reporting Dialog Box Details shows you the details of the error: Figure 24.2. Details of the Crash Save saves details of the error locally or remotely: Exit exits the installation process. If you select Save from the main dialog, you can choose from the following options: Figure 24.3. Select reporter Logger saves details of the error as a log file to the local hard drive at a specified location. Red Hat Customer Support submits the crash report to Customer Support for assistance. Report uploader uploads a compressed version of the crash report to Bugzilla or a URL of your choice. Before submitting the report, click Preferences to specify a destination or provide authentication details. Select the reporting method you need to configure and click Configure Event . Figure 24.4. Configure reporter preferences Logger Specify a path and a filename for the log file. Check Append if you are adding to an existing log file. Figure 24.5. Specify local path for log file Red Hat Customer Support Enter your Red Hat Network username and password so your report reaches Customer Support and is linked with your account. The URL is prefilled and Verify SSL is checked by default. Figure 24.6. Enter Red Hat Network authentication details Report uploader Specify a URL for uploading a compressed version of the crash report. Figure 24.7. Enter URL for uploading crash report Bugzilla Enter your Bugzilla username and password to lodge a bug with Red Hat's bug-tracking system using the crash report. The URL is prefilled and Verify SSL is checked by default. Figure 24.8. Enter Bugzilla authentication details Once you have entered your preferences, click OK to return to the report selection dialog. Select how you would like to report the problem and then click Forward . Figure 24.9. Confirm report data You can now customize the report by checking and unchecking the issues that will be included. When finished, click Apply . Figure 24.10. Report in progress This screen displays the outcome of the report, including any errors in sending or saving the log. Click Forward to proceed. Figure 24.11. Reporting done Reporting is now complete. Click Forward to return to the report selection dialog. You can now make another report, or click Close to exit the reporting utility and then Exit to close the installation process.

Commands:
Chapter 6. Configuring Knative broker for Apache Kafka The Knative broker implementation for Apache Kafka provides integration options for you to use supported versions of the Apache Kafka message streaming platform with OpenShift Serverless. Kafka provides options for event source, channel, broker, and event sink capabilities. In addition to the Knative Eventing components that are provided as part of a core OpenShift Serverless installation, the KnativeKafka custom resource (CR) can be installed by: Cluster administrators, for OpenShift Container Platform Cluster or dedicated administrators, for Red Hat OpenShift Service on AWS or for OpenShift Dedicated. The KnativeKafka CR provides users with additional options, such as: Kafka source Kafka channel Kafka broker Kafka sink

Commands:
Chapter 12. Preparing the system for IdM client installation Ensure your system meets the following conditions before you install an Identity Management (IdM) client. 12.1. Supported versions of RHEL for installing IdM clients An Identity Management deployment in which IdM servers are running on the latest minor version of Red Hat Enterprise Linux 9 supports clients that are running on the latest minor versions of: RHEL 7 RHEL 8 RHEL 9 Note While other client systems, for example Ubuntu, can work with IdM 9 servers, Red Hat does not provide support for these clients. 12.2. DNS requirements for IdM clients Client installer by default tries to search for _ldap._tcp.DOMAIN DNS SRV records for all domains that are parent to its hostname. For example, if a client machine has a hostname client1.idm.example.com , the installer will try to retrieve an IdM server hostname from _ldap._tcp.idm.example.com , _ldap._tcp.example.com and _ldap._tcp.com DNS SRV records, respectively. The discovered domain is then used to configure client components (for example, SSSD and Kerberos 5 configuration) on the machine. However, the hostnames of IdM clients are not required to be part of the primary DNS domain. If the client machine hostname is not in a subdomain of an IdM server, pass the IdM domain as the --domain option of the ipa-client-install command. In that case, after the installation of the client, both SSSD and Kerberos components will have the domain set in their configuration files and will use it to autodiscover IdM servers. Additional resources For details on DNS requirements in IdM, see Host name and DNS requirements for IdM . 12.3. Port requirements for IdM clients Identity Management (IdM) clients connect to a number of ports on IdM servers to communicate with their services. On IdM client, these ports must be open in the outgoing direction . If you are using a firewall that does not filter outgoing packets, such as firewalld , the ports are already available in the outgoing direction. Additional resources For information about which specific ports are used, see Port requirements for IdM . 12.4. IPv6 requirements for IdM clients Identity Management (IdM) does not require the IPv6 protocol to be enabled in the kernel of the host that you want to enroll into IdM. For example, if your internal network only uses the IPv4 protocol, you can configure the System Security Services Daemon (SSSD) to only use IPv4 to communicate with the IdM server. You can do this by inserting the following line into the [domain/ NAME ] section of the /etc/sssd/sssd.conf file: Additional resources For more information about the lookup_family_order option, see the sssd.conf(5) man page on your system. 12.5. Installing packages required for an IdM client Installing the ipa-client package automatically installs other required packages as dependencies, such as the System Security Services Daemon (SSSD) packages. Procedure Install the ipa-client package:

Commands:
lookup_family_order = ipv4_only
dnf install ipa-client
7.80. hplip 7.80.1. RHSA-2013:0500 - Low: hplip security, bug fix and enhancement update Updated hplip packages that fix several security issues, multiple bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The hplip packages contain the Hewlett-Packard Linux Imaging and Printing Project (HPLIP), which provides drivers for Hewlett-Packard printers and multi-function peripherals. Security Fix CVE-2013-0200 , CVE-2011-2722 Several temporary file handling flaws were found in HPLIP. A local attacker could use these flaws to perform a symbolic link attack, overwriting arbitrary files accessible to a process using HPLIP. The CVE-2013-0200 issues were discovered by Tim Waugh of Red Hat. Note The hplip packages have been upgraded to upstream version 3.12.4, which provides a number of bug fixes and enhancements over the version. (BZ# 731900 ) Bug Fixes BZ#829453 Previously, the hpijs package required the obsolete cupsddk-drivers package, which was provided by the cups package. Under certain circumstances, this dependency caused hpijs installation to fail. This bug has been fixed and hpijs no longer requires cupsddk-drivers. BZ# 683007 The configuration of the Scanner Access Now Easy (SANE) back end is located in the /etc/sane.d/dll.d/ directory, however, the hp-check utility checked only the /etc/sane.d/dll.conf file. Consequently, hp-check checked for correct installation, but incorrectly reported a problem with the way the SANE back end was installed. With this update, hp-check properly checks for installation problems in both locations as expected. All users of hplip are advised to upgrade to these updated packages, which fix these issues and add these enhancements. 7.80.2. RHSA-2013:1274 - Important: hplip security update Updated hplip 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 associated with the description below. The hplip packages contain the Hewlett-Packard Linux Imaging and Printing Project (HPLIP), which provides drivers for Hewlett-Packard printers and multi-function peripherals. Security Fix CVE-2013-4325 HPLIP communicated with PolicyKit for authorization via a D-Bus API that is vulnerable to a race condition. This could lead to intended PolicyKit authorizations being bypassed. This update modifies HPLIP to communicate with PolicyKit via a different API that is not vulnerable to the race condition. All users of hplip are advised to upgrade to these updated packages, which contain a backported patch to correct this issue.

Commands:
31.3.2. Kickstart Considerations If your target system will be booting over the network, VNC is still available. Just add the vnc command to the kickstart file for the system. You will be able to connect to the target system using your VNC viewer and monitor the installation progress. The address to use is the one the system is configured with via the kickstart file. If you are using DHCP for the target system, the reverse vncconnect method may work better for you. Rather than adding the vnc boot parameter to the kickstart file, add the vncconnect= HOST parameter to the list of boot arguments for the target system. For HOST, put the IP address or DNS host name of the VNC viewer system. See the section for more details on using the vncconnect mode.

Commands:
B.65.2. RHSA-2011:0309 - Critical: pango security update Updated pango 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 critical security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Pango is a library used for the layout and rendering of internationalized text. CVE-2011-0064 It was discovered that Pango did not check for memory reallocation failures in the hb_buffer_ensure() function. An attacker able to trigger a reallocation failure by passing sufficiently large input to an application using Pango could use this flaw to crash the application or, possibly, execute arbitrary code with the privileges of the user running the application. Red Hat would like to thank the Mozilla Security Team for reporting this issue. All pango users should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing this update, you must restart your system or restart the X server for the update to take effect.

Commands:
4.97. iproute 4.97.1. RHBA-2011:1690 - iproute bug fix update An updated iproute package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The iproute package contains networking utilities (ip and rtmon, for example) which are designed to use the advanced networking capabilities of the Linux kernel. Bug Fixes BZ# 692867 Prior to this update, the "ip" utility lacked the "mode" parameter support for macvtap devices. As a consequence affected users could not create macvtap devices in "bridge" or "private" modes. With this update the "ip" utility now fully supports macvtap devices along with the "mode" parameter and its options, "bridge", "private", and "vepa" (default). As a result users can now utilize macvtap functionality via the iproute package. BZ# 693878 Prior to this update, the "ip" tool lacked the "passthru" mode parameter support for macvtap and macvlan devices. Consequently users could not create macvtap and macvlan devices in "passthru" mode. The "ip" tool now fully supports macvtap and macvlan devices along with the "mode" parameter and its options, "bridge", "private", "passthru", and "vepa" (default). As a result users can now utilize "passthru" mode as part of macvtap and macvlan functionality via the iproute package. BZ# 709652 Prior to this update, the "tc" utility ignored GRED (Generalized RED) queue options. Consequently "tc" users could not configure certain GRED queue related parameters. With this update the "tc" utility no longer accidentally overwrites the user specified options. As a result "tc" users can now reliably define all GRED parameters. All users of iproute are advised to upgrade to this updated package, which fixes these bugs.

Commands:
20.35. Retrieving Storage Volume Information The virsh vol-pool vol command returns the pool name or UUID for a given storage volume. By default, the storage pool name is returned. If the --uuid option is used, the pool UUID is returned instead. The command requires the key or path of the storage volume for which to return the requested information. Example 20.96. How to display the storage volume's name or UUID The following examples retrieves the name for the storage volume that is found in the path /var/lib/libvirt/images/vol-new : The vol-path --pool pool-or-uuid vol-name-or-key command returns the path for a given volume. The command requires --pool pool-or-uuid , which is the name or UUID of the storage pool the volume is in. It also requires vol-name-or-key which is the name or key of the volume for which the path has been requested. The vol-name vol-key-or-path command returns the name for a given volume, where vol-key-or-path is the key or path of the volume to return the name for. The vol-key --pool pool-or-uuid vol-name-or-path command returns the volume key for a given volume where --pool pool-or-uuid is the name or UUID of the storage pool the volume is in and vol-name-or-path is the name or path of the volume to return the volume key for.

Commands:
virsh vol-pool /var/lib/libvirt/images/vol-new vol-new
11.2.2. Mail Delivery Agent A Mail Delivery Agent ( MDA ) is invoked by the MTA to file incoming email in the proper user's mailbox. In many cases, the MDA is actually a Local Delivery Agent ( LDA ), such as mail or Procmail. Any program that actually handles a message for delivery to the point where it can be read by an email client application can be considered an MDA. For this reason, some MTAs (such as Sendmail and Postfix) can fill the role of an MDA when they append new email messages to a local user's mail spool file. In general, MDAs do not transport messages between systems nor do they provide a user interface; MDAs distribute and sort messages on the local machine for an email client application to access.

Commands:
Preface Red Hat Fuse provides two enterprise monitoring tools for viewing and managing Fuse integrations: The Fuse Console is a web-based console that you access from a browser to monitor and manage a running Fuse container. The Fuse Console is based on Hawtio open source software ( https://hawt.io/ ). This guide describes how to use the Fuse Console. Prometheus stores system and integration-level metrics for Fuse distributions. You can use a graphical analytics interface, such as Grafana, to view and analyze the stored historical data. To learn more about using Prometheus, see the the Prometheus documentation . The audience for this guide is Red Hat Fuse on Apache Karaf administrators. This guide assumes that you are familiar with the Red Hat Fuse platform, Apache Camel, and the processing requirements for your organization.

Commands:
3.2. Avoiding Data Corruption by Monitoring Free Database Locks Running out of database locks can lead to data corruption. To avoid this, Directory Server, by default, monitors the remaining number of free database locks every 500 milliseconds and, if the number of active database locks is equal or higher than the 90%, Directory Server aborts all searches. You can change the interval and threshold: For example, to set the interval to 600 milliseconds and the threshold to 85 percent, enter: The --locks-monitoring-enabled on option ensure that the feature is enabled. Note If you set a too high interval, the server can run out of locks before the monitoring check happens. Setting a too short interval can slow down the server. Restart the instance:

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend config set --locks-monitoring-enabled on --locks-monitoring-pause 600 --locks-monitoring-threshold 85
dsctl instance_name restart
Chapter 12. Recertification As an existing partner you must recertify your application: on every major and minor release of the Red Hat Enterprise Linux on every major and minor release of your application Note To recertify your application, it is mandatory to create a new certification request for recertification. To recertify your application, submit a new certification request through the Red Hat Certification tool or create a new component in the Red Hat Partner Connect . Run the certification tests on SUT and proceed with the regular certification workflow, like a new certification.

Commands:
8.125. nmap 8.125.1. RHBA-2013:0881 - nmap bug fix update Updated nmap packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The nmap packages provide a network exploration utility and a security scanner. Bug Fixes BZ# 729045 Previously, the debuginfo file for the ncat utility was missing in the nmap debuginfo package. Consequently, debugging and analysis of unexpected terminations could not be done properly. This update ensure the missing file is present in the package, thus fixing this bug. BZ# 826601 In a version, the ncat utility failed to write its session data to an output file when the used protocol was UDP. This update provides a patch, which ensures that the data are properly written in the described scenario, thus fixing this bug. Users of nmap are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.3. Reference Key Columns Column Name Type Description PKTABLE_CAT string VDB name PKTABLE_SCHEM string Schema Name PKTABLE_NAME string Table/View Name PKCOLUMN_NAME string Column Name FKTABLE_CAT string VDB Name FKTABLE_SCHEM string Schema Name FKTABLE_NAME string Table/View Name FKCOLUMN_NAME string Column Name KEY_SEQ short Key Sequence UPDATE_RULE integer Update Rule DELETE_RULE integer Delete Rule FK_NAME string FK Name PK_NAME string PK Name DEFERRABILITY integer -

Commands:
4.188. ncompress 4.188.1. RHBA-2012:0043 - ncompress bug fix update An updated ncompress package that fixes one bug is now available for Red Hat Enterprise Linux 6. The ncompress package contains the compress and uncompress file compression and decompression utilities, which are compatible with the original UNIX compress utility (.Z file extensions). Bug Fix BZ# 781973 The ncompress utility previously relied on the glibc implementation of the memcpy() function. A recent glibc update optimized memcpy(), which resulted in data corruption in ncompress file compression and decompression. This update replaces memcpy() with the memmove() function and ncompress now works as expected. All users of ncompress are advised to upgrade to this updated package, which fixes this bug.

Commands:
5.81. gegl 5.81.1. RHSA-2012:1455 - Moderate: gegl security update Updated gegl 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 moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. GEGL (Generic Graphics Library) is a graph-based image processing framework. Security Fix CVE-2012-4433 An integer overflow flaw, leading to a heap-based buffer overflow, was found in the way the gegl utility processed .ppm (Portable Pixel Map) image files. An attacker could create a specially-crafted .ppm file that, when opened in gegl, would cause gegl to crash or, potentially, execute arbitrary code. This issue was discovered by Murray McAllister of the Red Hat Security Response Team. Users of gegl should upgrade to these updated packages, which contain a backported patch to correct this issue.

Commands:
4.341. virt-what 4.341.1. RHEA-2011:1556 - virt-what bug fix and enhancement update An updated virt-what package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The virt-what package provides a command line tool that is used to detect whether the operating system is running inside a virtual machine. The virt-what package has been upgraded to upstream version 1.11, which provides a number of bug fixes and enhancements over the version. (BZ# 672211 ) Bug Fix BZ# 707524 On the 64-bit x86 architecture, if the user configured a CPU model for the virtual machine, the virt-what utility failed to detect that the guest was running inside a virtual machine. The order of tests has been rearranged, fixing the problem. Users of virt-what are advised to upgrade to this updated package which fixes these bugs and adds these enhancements.

Commands: