mtpti5iD/redhat-docs_dataset huggingface dataset:
C.7. Additional Resources There is a large amount of detailed information available about the X server, the clients that connect to it, and the assorted desktop environments and window managers. C.7.1. Installed Documentation /usr/share/X11/doc/ - contains detailed documentation on the X Window System architecture, as well as how to get additional information about the Xorg project as a new user. /usr/share/doc/gdm- <version-number> /README - contains information on how display managers control user authentication. man xorg.conf - Contains information about the xorg.conf configuration files, including the meaning and syntax for the different sections within the files. man Xorg - Describes the Xorg display server.

Commands:
Chapter 5. Unsupported Features in Fuse 7.13 The following features are unsupported in Red Hat Fuse 7.13. camel-leveldb component is not supported for Fuse on the IBM PowerPC and Z platforms When Fuse is installed on the IBM PowerPC or IBM Z platforms, the Camel LevelDB component is not supported. Installing Fuse Console using the Operator is not supported on OCP 3.11 Installing Fuse Console using the Operator is not supported and does not work on OpenShift Container Platform (OCP) 3.11. The recommended way to install Fuse Console on OCP 3.11 is to use templates. Apache Karaf EclipseLink feature is unsupported The Apache Karaf EclipseLink feature is not supported in Fuse, because this feature depends on JPA 2.2, while the Karaf container for Fuse 7.2 is aligned with JPA 2.1. Apache Aries Blueprint Web module is unsupported The Apache Aries Blueprint Web module is not supported in Fuse. The presence of an example featuring Blueprint Web in the community edition of Apache Camel (provided as a separate download) does not imply that this feature is supported in Fuse. The PHP scripting language is not supported in Apache Camel on Apache Karaf The PHP scripting language is not supported in Camel applications on the Apache Karaf container, because there is no OSGi bundle available for PHP. The PHP scripting language is deprecated in Camel applications on the JBoss EAP container and on the Spring Boot container. The Python scripting language is not supported in Apache Camel on Apache Karaf The Python scripting language is not supported in Camel applications on the Apache Karaf container, because there is no OSGi bundle available for Python. The Python scripting language is deprecated in Camel applications on the JBoss EAP container and on the Spring Boot container.

Commands:
B.17.3. Logic and Configuration Errors A well-formatted XML document can contain errors that are correct in syntax but libvirt cannot parse. Many of these errors exist, with two of the most common cases outlined below. B.17.3.1. Vanishing parts Symptom Parts of the change you have made do not show up and have no effect after editing or defining the domain. The define or edit command works, but when dumping the XML once again, the change disappears. Investigation This error likely results from a broken construct or syntax that libvirt does not parse. The libvirt tool will generally only look for constructs it knows but ignore everything else, resulting in some of the XML changes vanishing after libvirt parses the input. Solution Validate the XML input before passing it to the edit or define commands. The libvirt developers maintain a set of XML schemas bundled with libvirt which define the majority of the constructs allowed in XML documents used by libvirt . Validate libvirt XML files using the following command: If this command passes, libvirt will likely understand all constructs from your XML, except if the schemas cannot detect options which are valid only for a given hypervisor. For example, any XML generated by libvirt as a result of a virsh dump command should validate without error.

Commands:
virt-xml-validate libvirt.xml
Chapter 3. Key concepts in cost management Review the following terms to ensure you understand important definitions in cost management. Cost The sum of infrastructure and supplementary costs or the total cost for the filtered data. This sum can include the cost for a particular account, region, or service. Raw cost The costs that a cloud provider reports before any cost model calculations. Unallocated costs The costs that you can view when you group OpenShift cost data by project. These costs are in the rows Platform unallocated and Worker unallocated and are available when viewing OpenShift cost data by project. Platform unallocated costs The costs for parts of primary and infrastructure nodes that are not allocated to run workloads. In this case, those workloads are the OpenShift platform or control plane. Network unattributed costs Costs associated with ingress and egress network traffic for individual nodes. Worker unallocated costs The costs that represent any unused part of your worker node's usage and request capacity. Unattributed cost The costs associated with a cloud integration that is not attributed to an OpenShift project. Overhead costs The costs that you outlay to administer your cloud account. 3.1. Cost layers You can create costs at different layers of the environment. In cost management, all costs can be classified as either infrastructure or supplementary costs. To customize what cost management shows on the Details page, you can allocate and present your costs as any of the cost layers in your cost model. Infrastructure cost In cost management, all cloud costs are considered infrastructure costs. They can include costs that cloud providers directly report through an Amazon (AWS), Microsoft Azure, or Google Cloud export. However, you can also designate infrastructure costs calculated from a price list for rates specifically marked as infrastructure. Note OpenShift Container Platform node and cluster cost per month rates are classified as infrastructure cost by default. You can choose to classify them as supplementary. Supplementary cost All costs not directly attributed to infrastructure are identified as supplementary costs. In cost management, these costs come from applying a price list to the metrics taken from an OpenShift cluster. The rates in the price list must be specified as supplementary. This is the default for all OpenShift costs except node and cluster cost per month. 3.2. Additional resources For more information about cost models, see Cost model terminology . For information about distributing costs, see Understanding cost distribution in cost management

Commands:
8.52. ethtool 8.52.1. RHBA-2014:1421 - ethtool bug fix and enhancement update Updated ethtool packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Ethtool is a utility that enables querying and changing settings such as speed, port autonegotiation, PCI locations, and checksum offload on many network devices, especially on ethernet devices. Bug Fixes BZ# 1003891 Previously, the ethtool utility did not support the Backplane link type. As a consequence, ethtool did not return "supported link modes" and "advertised link modes" on be2net-based devices. With this update, the support for Backplane has been added, and ethtool now returns "supported link modes" and "advertised link modes" as expected. BZ# 1010843 Previously, the ethtool utility did not correctly communicate with the network device driver when attempting to set Large Receive Offload (LRO) options. Consequently, it was not possible to set the LRO options on devices supporting LRO. With this update, ethtool has been fixed to communicate correctly with the network device driver, and the LRO options can now be set on network devices. BZ# 1018367 Due to a change to the ixgbe driver, the "ethtool -d" command in non-raw mode stopped providing output. As a consequence, "ethtool -d" could not be used to examine the state of ixgbe devices. To fix this bug, ethool has been changed to work with the new ixgbe device driver, and the "ethtool -d" command in non-raw mode can now be used again on the ixgbe devices. In addition, this update provides the following Enhancement BZ# 1105589 With this update, the ethtool utility supports the Medium Dependent Interface Crossover (MDI-X) mode setting on the e1000, e1000e, and igb drivers. Users of ethtool are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
2.8.5.2. Prerouting If you have a server on your internal network that you want make available externally, you can use the -j DNAT target of the PREROUTING chain in NAT to specify a destination IP address and port where incoming packets requesting a connection to your internal service can be forwarded. For example, if you want to forward incoming HTTP requests to your dedicated Apache HTTP Server at 172.31.0.23, use the following command as the root user: This rule specifies that the NAT table use the built-in PREROUTING chain to forward incoming HTTP requests exclusively to the listed destination IP address of 172.31.0.23. Note If you have a default policy of DROP in your FORWARD chain, you must append a rule to forward all incoming HTTP requests so that destination NAT routing is possible. To do this, use the following command as the root user: This rule forwards all incoming HTTP requests from the firewall to the intended destination; the Apache HTTP Server behind the firewall.

Commands:
~]# iptables -t nat -A PREROUTING -i eth0 -p tcp --dport 80 -j DNAT --to 172.31.0.23:80
~]# iptables -A FORWARD -i eth0 -p tcp --dport 80 -d 172.31.0.23 -j ACCEPT
Chapter 4. Analyzing your projects with the MTA extension You can analyze your projects with the MTA extension by creating a run configuration and running an analysis. 4.1. MTA extension interface The interface of the Migration Toolkit for Applications (MTA) extension is designed to make it easier for you to find information and perform actions: In the left pane, you can see a directory tree named Analysis Results with a report icon at its top. You can click the icon to open the MTA report in your browser. Beneath the report icon are the other elements of the tree: the applications analyzed by MTA, the rulesets used, and the issues discovered by the analysis. In the upper right pane, you can configure an analysis. In the lower right pane, you can see the settings of the configuration, including source, target, and advanced options. You can view the progress of an analysis in this pane. When the analysis is completed, you can click the Open Report button to open the MTA report, which describes any issues you need to address before you migrate or modernize your application. For more information, see Reviewing the reports in the CLI Guide . 4.2. Configuring a run configuration MTA extension interface You can configure multiple run configurations to run against each project you import to VS Code. Prerequisites mta-cli executable installed. You can download the mta-cli executable from mta download . Procedure In Extensions view, click the Migration Toolkit for Applications icon ( ) on the Activity bar. Click the + (plus sign) to Migration Toolkit for Applications to add a run configuration. Complete the following configuration fields: Name : Enter a meaningful name for the analysis configuration or accept the default. cli : Enter the path to the cli executable. For example: USDHOME/mta-cli-7.2.1.GA-redhat/bin/mta-cli . Input : Set to the path of the project that you have open within your IDE by clicking Add and doing one of the following: Enter the input file or directory and press Enter. Click Open File Explorer and select the directory. Target : Select one or more target migration paths. Right-click the run configuration and select Run . When the analysis is completed, you can click the Open Report button to open the MTA report, which describes any issues you need to address before you migrate or modernize your application. For more information, see Reviewing the reports in the CLI Guide .

Commands:
8.174. perl-Crypt-SSLeay 8.174.1. RHBA-2014:0466 - perl-Crypt-SSLeay bug fix update Updated perl-Crypt-SSLeay packages that fix one bug are now available for Red Hat Enterprise Linux 6. The perl-Crypt-SSLeay packages contain Perl modules that provide support for the HTTPS protocol under Library for WWW in Perl (LWP) so that LWP::UserAgent can make HTTPS GET, HEAD, and POST requests. The perl-Crypt-SSLeay packages contain Net::SSL module, which is automatically loaded by requests from the LWP::Protocol::https module, and provide the necessary SSL glue for the module to work. Bug Fix BZ# 1059992 The perl-Crypt-SSLeay packages included their own certification authority's (CA) certificates bundle. As a consequence, the content provided by the /usr/share/doc/perl-Crypt-SSLeay-0.57/ca-bundle.crt file became out of date. With this update, /usr/share/doc/perl-Crypt-SSLeay-0.57/ca-bundle.crt has been replaced with a symbolic link to the /etc/pki/tls/certs/ca-bundle.crt file, which is a system-wide storage file for trusted CA certificates. As a result, the perl-Crypt-SSLeay documentation does not contain a bundle of CA certificates that is out of date and could confuse the user. Users of perl-Crypt-SSLeay are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 17. Troubleshooting Installation on an IBM Power Systems server 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. You may also find the IBM Online Alert Section for System p useful. It is located at: 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). 17.1. You Are Unable to Boot Red Hat Enterprise Linux 17.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. If you receive a fatal signal 11 error during your installation, it is probably due to a hardware error in memory on your system's bus. Like other operating systems, Red Hat Enterprise Linux places its own demands on your system's hardware. Some of this hardware may not be able to meet those demands, even if they work properly under another OS. Ensure that you have the latest installation updates and images. Review the online errata to see if newer versions are available. If the latest images still fail, it may be due to a problem with your hardware. Commonly, these errors are in your memory or CPU-cache. A possible solution for this error is turning off the CPU-cache in the BIOS, if your system supports this. You could also try to swap your memory around in the motherboard slots to check if the problem is either slot or memory related. Another option is to perform a media check on your installation DVD. Anaconda , the installation program, has the ability to test the integrity of the installation media. It works with the DVD, hard drive ISO, and NFS ISO installation methods. Red Hat recommends that you test all installation media before starting the installation process, and before reporting any installation-related bugs (many of the bugs reported are actually due to improperly-burned DVDs). To use this test, type the following command at the boot: or yaboot: prompt: For more information concerning signal 11 errors, refer to:

Commands:
http://www14.software.ibm.com/webapp/set2/sas/f/lopdiags/info/LinuxAlerts.html
linux mediacheck
http://www.bitwizard.nl/sig11/
4.11. Kerberos In Red Hat Enterprise Linux 6, Kerberos clients and servers (including KDCs) will default to not using keys for the ciphers des-cbc-crc , des-cbc-md4 , des-cbc-md5 , des-cbc-raw , des3-cbc-raw , des-hmac-sha1 , and arcfour-hmac-exp . By default, clients will not be able to authenticate to services which have keys of these types. Most services can have a new set of keys (including keys for use with stronger ciphers) added to their keytabs and experience no downtime, and the ticket granting service's keys can likewise be updated to a set which includes keys for use with stronger ciphers, using the kadmin cpw -keepold command. As a temporary workaround, systems that need to continue to use the weaker ciphers require the allow_weak_crypto option in the libdefaults section of the /etc/krb5.conf file. This variable is set to false by default, and authentication will fail without having this option enabled: Additionally, support for Kerberos IV, both as an available shared library and as a supported authentication mechanism in applications, has been removed. Newly-added support for lockout policies requires a change to the database dump format. Master KDCs which need to dump databases in a format that older KDCs can consume must run kdb5_util's dump command with the -r13 option.

Commands:
[libdefaults] allow_weak_crypto = yes
2.2.2.3. Packages Changes These changes affect the %packages section: The --ignoreDeps and --resolveDeps arguments have been removed. Anaconda automatically resolves dependencies, but will skip installation of packages that have unmet dependencies. If you want to get the exact same set of packages using Kickstart that you would in a default GUI install accepting all of the defaults, add the following: You can also optionally specify the architecture of packages that you want installed for multi-arch installs. For instance: This would add the x86 glibc package to the set, which can be useful on AMD64 and Intel 64 systems that require the 32-bit packages for compatibility reasons. It is not possible to audit and migrate all of the packages and groups in the %packages section. Some packages and groups have been removed, some added, and some have had their name changed. See the Release Notes for more details.

Commands:
%packages --default %end
%packages glibc.i686 %end
3.3.2. Behavioral changes Red Hat Enterprise Linux 6 provides full support for ext4 and it is the default file system for new installations. This section explains the major changes in behavior that this new file system introduces. The included version of the GRUB boot loader provides full support for ext4 partitions. The installer also allows you to place any /boot file system on an ext4 partition. The included version of the e2fsprogs package is fully compatible with ext4. In some cases, ext4 file systems created under Red Hat Enterprise Linux 5.3 with the e4fsprogs package created an ext4dev file system type. The test_fs feature flag identifying these file systems as a development version can be removed with the following command: tune2fs -E ^test_fs . This is done so that these file systems will be recognized as regular ext4 file systems.

Commands:
probe::ioblock_trace.bounce Name probe::ioblock_trace.bounce - Fires whenever a buffer bounce is needed for at least one page of a block IO request. Synopsis Values None Description name - name of the probe point q - request queue on which this bio was queued. devname - device for which a buffer bounce was needed. ino - i-node number of the mapped file bytes_done - number of bytes transferred sector - beginning sector for the entire bio flags - see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block BIO_EOF 2 out-out-bounds error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user pages BIO_EOPNOTSUPP 7 not supported rw - binary trace for read/write request vcnt - bio vector count which represents number of array element (page, offset, length) which makes up this I/O request idx - offset into the bio vector array phys_segments - number of segments in this bio after physical address coalescing is performed. size - total size in bytes bdev - target block device bdev_contains - points to the device object which contains the partition (when bio structure represents a partition) p_start_sect - points to the start sector of the partition structure of the device Context The process creating a block IO request.

Commands:
ioblock_trace.bounce
12. General Updates Multilib Python Packages Removed In Red Hat Enterprise Linux 6.1, multilib Python packages and packages dependent on them have been removed. This was because installing Python packages for multiple architectures on one system can cause various problems. For more information, refer to https://access.redhat.com/knowledge/solutions/68140 . Automated Bug Reporting Tool Red Hat Enterprise Linux 6 introduced the new Automated Bug Reporting Tool (ABRT). ABRT logs details of software crashes on a local system, and provides interfaces (both graphical and command line based) to report issues to Red Hat support. In Red Hat Enterprise Linux 6.1, ABRT is updated to version 1.1.16. This update provides an enhanced graphical user interface (GUI) in addition to a range of other bugfixes and enhancements. openCryptoki openCryptoki contains version 2.11 of the PKCS#11 API, implemented for IBM Cryptocards. openCryptoki is updated in Red Hat Enterprise Linux 6.1, providing many bugfixes and enhancements, including better overall performance. OpenLDAP OpenLDAP is an open source suite of Lightweight Directory Access Protocol (LDAP) applications and development tools. OpenLDAP in Red Hat Enterprise Linux 6.1 is updated to version 2.4.23. This updated version of OpenLDAP utilizes Network Security Services (NSS) cryptographic libraries, replacing OpenSSL. TigerVNC TigerVNC provides client and server software for Virtual Network Computing (VNC). VNC is a remote display system, allowing a user to view a computing desktop environment over a network connection.TigerVNC is updated to version 1.1.0, providing many bugfixes enhanced encryption support. tuned tuned is a system tuning daemon that monitors system components and dynamically tunes system settings. Utilizing ktune (the static mechanism for system tuning), tuned can monitor and tune devices (e.g. hard disk drives and ethernet devices). In Red Hat Enterprise Linux 6.1, the tuned tuning profiles now include support for the s390x architectures.

Commands:
6.3. RHEA-2015:1414 - new package: python-argparse A new python-argparse package is now available for Red Hat Enterprise Linux 6. The python-argparse package provides the argparse module, which is an improved version of the optparse command-line parser. This enhancement update adds the python-argparse package to Red Hat Enterprise Linux 6. The package is now available from the base channels in Red Hat Network. (BZ# 1173360 ) All users who require python-argparse are advised to install this new package.

Commands: