mtpti5iD/redhat-docs_dataset huggingface dataset:
5.325. system-config-printer 5.325.1. RHBA-2012:0448 - system-config-printer bug fix update Updated system-config-printer packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The system-config-printer package contains a print queue configuration tool with a graphical user interface. Bug Fixes BZ# 739745 Previously, displaying tooltips while being in a main loop recursion caused the system-config-printer utility to terminate unexpectedly. To prevent system-config-printer from crashing, displaying tooltips is now avoided during the main loop recursion. BZ# 744519 Python bindings for the CUPS library were not reliable when threads were used. In particular, a single password callback function was used instead of one for each thread. This, in some cases, caused the system-config-printer utility to terminate unexpectedly with a segmentation fault. With this update, thread local storage is used for the password callback function in Python bindings for the CUPS library. All users of system-config-printer are advised to upgrade to these updated packages, which fix these bugs.

Commands:
B.35. kabi-whitelists B.35.1. RHBA-2010:0856 - kabi-whitelists bug fix update An updated kabi-whitelists package that fixes a bug is now available. The kabi-whitelists package contains reference files documenting interfaces provided by the Red Hat Enterprise Linux 6 kernel that are considered to be stable by Red Hat kernel engineering, and safe for longer term use by third party loadable device drivers, as well as for other purposes. Bug Fix BZ# 643570 Two exported kernel symbols were removed from the final version of the Kernel Application Binary Interface (kABI) whitelists package in Red Hat Enterprise Linux 6. All users are advised to upgrade to this updated package, which fixes this bug.

Commands:
7.179. redhat-support-tool 7.179.1. RHBA-2015:1406 - redhat-support-tool and redhat-support-lib-python update Updated redhat-support-tool and redhat-support-lib-python packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The redhat-support-tool utility facilitates console-based access to Red Hat's subscriber services and gives Red Hat subscribers more venues for accessing the content and services available to them as Red Hat customers. Further, it enables Red Hat customers to integrate and automate their helpdesk services with our subscription services. Bug Fixes BZ# 1198411 Previously, bugs in the redhat-support-lib-python library caused the "addattachment" command to fail with an error message "TypeError: unhashable type" when files were uploaded using FTP through an HTTP proxy configured to proxy FTP. As a consequence, attachments could not be sent to the RedHat FTP dropbox if redhat-support-tool was configured to use an HTTP proxy and the "-f" option was used with the "addattachment" command. The underlying redhat-support-lib-python code has been fixed, and the "redhat-support-tool addattachment -f" command now successfully uploads files to the RedHat FTP dropbox in this scenario. BZ# 1146360 Due to bugs in redhat-support-lib-python, the "addattachment" command failed with an error message "unknown URL type" when files were uploaded to the Customer Portal using an HTTP proxy. Consequently, attachments could not be added to cases if redhat-support-tool was configured to use an HTTP proxy. This bug has been fixed, and the "redhat-support-tool addattachment" command now successfully uploads files to the Customer Portal through an HTTP proxy. BZ# 1198616 When retrieving case information from the Customer Portal using the /rs/case Representational State Transfer (REST) endpoint, the case group number was included in the response but not in the case group name. Consequently, when viewing the case details with the "redhat-support-tool getcase" command, the case group number and name were not displayed. With this update, an additional call to the /rs/groups endpoint has been added, and "redhat-support-tool getcase" now displays the case group name along with other case information. BZ# 1104722 Previously, the way redhat-support-tool stored Customer Portal passwords was inconsistent in terms of encoding and decoding. As a consequence, certain passwords could not be decoded correctly. With this update, the method of decoding of the stored Customer Portal passwords has been made consistent with how the passwords were encoded, and the described problem no longer occurs. Users of redhat-support-tool and redhat-support-lib-python are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Appendix B. Provisioning FIPS-Compliant Hosts Satellite supports provisioning hosts that comply with the National Institute of Standards and Technology's Security Requirements for Cryptographic Modules standard, reference number FIPS 140-2, referred to here as FIPS. To enable the provisioning of hosts that are FIPS-compliant, complete the following tasks: Change the provisioning password hashing algorithm for the operating system Create a host group and set a host group parameter to enable FIPS For more information, see Creating a Host Group in the Managing Hosts guide. The provisioned hosts have the FIPS-compliant settings applied. To confirm that these settings are enabled, complete the steps in Section B.3, "Verifying FIPS Mode is Enabled" . B.1. Changing the Provisioning Password Hashing Algorithm To provision FIPS-compliant hosts, you must first set the password hashing algorithm that you use in provisioning to SHA256. This configuration setting must be applied for each operating system you want to deploy as FIPS-compliant. Procedure Identify the Operating System IDs: Update each operating system's password hash value. Note that you cannot use a comma-separated list of values. B.2. Setting the FIPS-Enabled Parameter To provision a FIPS-compliant host, you must create a host group and set the host group parameter fips_enabled to true . If this is not set to true , or is absent, the FIPS-specific changes do not apply to the system. You can set this parameter when you provision a host or for a host group. To set this parameter when provisioning a host, append --parameters fips_enabled=true to the Hammer command. For more information, see the output of the command hammer hostgroup set-parameter --help . B.3. Verifying FIPS Mode is Enabled To verify these FIPS compliance changes have been successful, you must provision a host and check its configuration. Procedure Log on to the host as root or with an admin-level account. Enter the following command: A value of 1 confirms that FIPS mode is enabled.

Commands:
hammer os list
hammer os update --password-hash SHA256 --title " My_Operating_System "
hammer hostgroup set-parameter --hostgroup " My_Host_Group " --name fips_enabled --value "true"
cat /proc/sys/crypto/fips_enabled
Chapter 3. Configuring Fencing with Conga This chapter describes how to configure fencing in Red Hat High Availability Add-On using Conga . Note Conga is a graphical user interface that you can use to administer the Red Hat High Availability Add-On. Note, however, that in order to use this interface effectively you need to have a good and clear understanding of the underlying concepts. Learning about cluster configuration by exploring the available features in the user interface is not recommended, as it may result in a system that is not robust enough to keep all services running when components fail. Section 3.2, "Configuring Fence Devices" 3.1. Configuring Fence Daemon Properties Clicking on the Fence Daemon tab displays the Fence Daemon Properties page, which provides an interface for configuring Post Fail Delay and Post Join Delay . The values you configure for these parameters are general fencing properties for the cluster. To configure specific fence devices for the nodes of the cluster, use the Fence Devices menu item of the cluster display, as described in Section 3.2, "Configuring Fence Devices" . The Post Fail Delay parameter is the number of seconds the fence daemon ( fenced ) waits before fencing a node (a member of the fence domain) after the node has failed. The Post Fail Delay default value is 0 . Its value may be varied to suit cluster and network performance. The Post Join Delay parameter is the number of seconds the fence daemon ( fenced ) waits before fencing a node after the node joins the fence domain. The Post Join Delay default value is 6 . A typical setting for Post Join Delay is between 20 and 30 seconds, but can vary according to cluster and network performance. Enter the values required and click Apply for changes to take effect. Note For more information about Post Join Delay and Post Fail Delay , see the fenced (8) man page.

Commands:
6.2. Debugging P2V conversions Problems encountered during P2V conversion can be more easily explained to engineers or support services if debugging messages are enabled when running virt-p2v . P2V debugging is available in Red Hat Enterprise Linux 6.5 and above. To enable P2V debugging, select the Enable server-side debugging check box on the convert screen in the virt-p2v client before clicking the Convert button. This instructs the server to write LIBGUESTFS_TRACE and LIBGUESTFS_DEBUG output during the virt-p2v conversion process. Refer to Chapter 5, Converting physical machines to virtual machines for instructions on using virt-p2v .

Commands:
B.32.2. RHSA-2011:0290 - Moderate: java-1.6.0-ibm security update Updated java-1.6.0-ibm packages that fix one security issue are now available for Red Hat Enterprise Linux 4 Extras, and Red Hat Enterprise Linux 5 and 6 Supplementary. 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. The IBM 1.6.0 Java release includes the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. CVE-2010-4476 A denial of service flaw was found in the way certain strings were converted to Double objects. A remote attacker could use this flaw to cause Java based applications to hang, for example, if they parsed Double values in a specially-crafted HTTP request. All users of java-1.6.0-ibm are advised to upgrade to these updated packages, containing the IBM 1.6.0 SR9 Java release. All running instances of IBM Java must be restarted for the update to take effect.

Commands:
Chapter 7. Removing Service Telemetry Framework from the Red Hat OpenShift Container Platform environment Remove Service Telemetry Framework (STF) from an Red Hat OpenShift Container Platform environment if you no longer require the STF functionality. To remove STF from the Red Hat OpenShift Container Platform environment, you must perform the following tasks: Delete the namespace. Remove the cert-manager Operator. Remove the Cluster Observability Operator. 7.1. Deleting the namespace To remove the operational resources for STF from Red Hat OpenShift Container Platform, delete the namespace. Procedure Run the oc delete command: USD oc delete project service-telemetry Verify that the resources have been deleted from the namespace: USD oc get all No resources found. 7.2. Removing the cert-manager Operator for Red Hat OpenShift If you are not using the cert-manager Operator for Red Hat OpenShift for any other applications, delete the Subscription, ClusterServiceVersion, and CustomResourceDefinitions. For more information about removing the cert-manager for Red Hat OpenShift Operator, see Removing cert-manager Operator for Red Hat OpenShift in the OpenShift Container Platform Documentation . Additional resources Deleting Operators from a cluster . 7.3. Removing the Cluster Observability Operator If you are not using the Cluster Observability Operator for any other applications, delete the Subscription, ClusterServiceVersion, and CustomResourceDefinitions. For more information about removing the Cluster Observability Operator, see Uninstalling the Cluster Observability Operator using the web console in the OpenShift Container Platform Documentation . Additional resources Deleting Operators from a cluster .

Commands:
oc delete project service-telemetry
oc get all No resources found.
Appendix A. Using your subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the AMQ Streams for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-08-12 11:04:59 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
4.3. IPTables/Firewalls IPTables includes a SECMARK target module. This is used to set the security mark value associated with the packet for use by security subsystems such as SELinux. It is only valid in the mangle table. Refer to the following for example usage:

Commands:
iptables -t mangle -A INPUT -p tcp --dport 80 -j SECMARK --selctx \ system_u:object_r:httpd_packet_t:s0
8.262. xfsprogs 8.262.1. RHBA-2014:1564 - xfsprogs bug update Updated xfsprogs packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The xfsprogs packages contain a set of commands to use the XFS file system, including the mkfs.xfs command to construct an XFS file system. Bug Fixes BZ# 1018751 Due to a bug in the underlying source code, an attempt to use the xfs_io "pwrite" command to write to a block device residing on an XFS file system failed with the following error: XFS_IOC_FSGEOMETRY: Inappropriate ioctl for device. This update applies a patch to fix this bug and the command no longer fails in the described scenario. BZ# 1020438 Previously, the thread local data were used incorrectly. As a consequence, when the xfs_repair utility was executed with the ag_stride option, the utility could terminate unexpectedly with a segmentation fault. The underlying source code has been modified to fix this bug and xfs_repair no longer crashes in the described situation. BZ# 1024702 Under certain conditions, the xfs_fsr utility failed to reorganize files with SELinux attributes. With this update, a patch has been provided to address this bug and xfs_fsr can successfully defragment files with SELinux attributes. BZ# 1100107 , BZ# 1104956 When the sector size of the source file system was larger than 512 bytes, the xfs_copy utility could create a corrupted copy of that system. In addition, the utility exited with a non-zero return code in all cases, even if the operation was successful. This update applies a patch to fix these bugs and the utility now works as expected. Users of xfsprogs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 8.4 is distributed with the kernel version 4.18.0-305, which provides support for the following architectures: AMD and Intel 64-bit architectures The 64-bit ARM architecture IBM Power Systems, Little Endian 64-bit IBM Z Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures . For a list of available subscriptions, see Subscription Utilization on the Customer Portal.

Commands:
2.3. Global Utilization The Global Utilization section shows the system utilization of the CPU, Memory and Storage. Figure 2.3. Global Utilization The top section shows the percentage of the available CPU, memory or storage and the over commit ratio. For example, the over commit ratio for the CPU is calculated by dividing the number of virtual cores by the number of physical cores that are available for the running virtual machines based on the latest data in Data Warehouse. The donut displays the usage in percentage for the CPU, memory or storage and shows the average usage for all hosts based on the average usage in the last 5 minutes. Hovering over a section of the donut will display the value of the selected section. The line graph at the bottom displays the trend in the last 24 hours. Each data point shows the average usage for a specific hour. Hovering over a point on the graph displays the time and the percentage used for the CPU graph and the amount of usage for the memory and storage graphs. 2.3.1. Top Utilized Resources Figure 2.4. Top Utilized Resources (Memory) Clicking the donut in the global utilization section of the Dashboard will display a list of the top utilized resources for the CPU, memory or storage. For CPU and memory the pop-up shows a list of the ten hosts and virtual machines with the highest usage. For storage the pop-up shows a list of the top ten utilized storage domains and virtual machines. The arrow to the right of the usage bar shows the trend of usage for that resource in the last minute.

Commands:
2.6. Removing Control Groups Use cgdelete to remove cgroups. It has similar syntax as cgcreate . Run the following command: where: subsystems is a comma‐separated list of subsystems. path is the path to the cgroup relative to the root of the hierarchy. For example: cgdelete can also recursively remove all subgroups with the option -r . When you delete a cgroup, all its tasks move to its parent group.

Commands:
cgdelete subsystems : path
~]# cgdelete cpu,net_cls:/test-subgroup
Chapter 46. Performance tuning considerations with Business Central The following key concepts or suggested practices can help you optimize Business Central configuration and Red Hat Process Automation Manager performance. These concepts are summarized in this section as a convenience and are explained in more detail in the cross-referenced documentation, where applicable. This section will expand or change as needed with new releases of Red Hat Process Automation Manager. Ensure that development mode is enabled during development You can set KIE Server or specific projects in Business Central to use production mode or development mode. By default, KIE Server and all new projects in Business Central are in development mode. This mode provides features that facilitate your development experience, such as flexible project deployment policies, and features that optimize KIE Server performance during development, such as disabled duplicate GAV detection. Use development mode until your Red Hat Process Automation Manager environment is established and completely ready for production mode. For more information about configuring the environment mode or duplicate GAV detection, see the following resources: Chapter 41, Configuring the environment mode in KIE Server and Business Central Packaging and deploying an Red Hat Process Automation Manager project Disable verification and validation of complex guided decision tables The decision table verification and validation feature of Business Central is enabled by default. This feature helps you validate your guided decision tables, but with complex guided decision tables, this feature can hinder decision engine performance. You can disable this feature by setting the org.kie.verification.disable-dtable-realtime-verification system property value to true . For more information about guided decision table validation, see Designing a decision service using guided decision tables . Disable automatic builds if you have many large projects In Business Central, when you navigate between projects in the Project Explorer side panel, the selected project is built automatically so that the Alerts window is updated to show any build errors for the project. If you have large projects or frequently switch between many projects that are under active development, this feature can hinder Business Central and decision engine performance. To disable automatic project builds, set the org.kie.build.disable-project-explorer system property to true .

Commands:
4. Related Documentation For more information about using Red Hat Enterprise Linux, refer to the following resources: Red Hat Enterprise Linux Installation Guide - Provides information regarding installation of Red Hat Enterprise Linux. Red Hat Enterprise Linux Introduction to System Administration - Provides introductory information for new Red Hat Enterprise Linux system administrators. Red Hat Enterprise Linux System Administration Guide - Provides more detailed information about configuring Red Hat Enterprise Linux to suit your particular needs as a user. Red Hat Enterprise Linux Reference Guide - Provides detailed information suited for more experienced users to reference when needed, as opposed to step-by-step instructions. Red Hat Enterprise Linux Security Guide - Details the planning and the tools involved in creating a secured computing environment for the data center, workplace, and home. For more information about Red Hat Cluster Suite for Red Hat Enterprise Linux, refer to the following resources: Red Hat Cluster Suite Overview - Provides a high level overview of the Red Hat Cluster Suite. Configuring and Managing a Red Hat Cluster - Provides information about installing, configuring and managing Red Hat Cluster components. Global File System: Configuration and Administration - Provides information about installing, configuring, and maintaining Red Hat GFS (Red Hat Global File System). LVM Administrator's Guide: Configuration and Administration - Provides a description of the Logical Volume Manager (LVM), including information on running LVM in a clustered environment. Using Device-Mapper Multipath - Provides information about using the Device-Mapper Multipath feature of Red Hat Enterprise Linux. Linux Virtual Server Administration - Provides information on configuring high-performance systems and services with the Linux Virtual Server (LVS). Red Hat Cluster Suite Release Notes - Provides information about the current release of Red Hat Cluster Suite. Red Hat Cluster Suite documentation and other Red Hat documents are available in HTML and PDF versions online at the following location: http://www.redhat.com/docs

Commands:
1.3. Dependencies The Ruby Software Development Kit has the following dependencies, which you must install manually if you are using gem : libxml2 for parsing and rendering XML libcurl for HTTP transfers C compiler Required header and library files Note You do not need to install the dependency files if you installed the RPM. Install the dependency files: Note If you are using Debian or Ubuntu, use apt-get :

Commands:
dnf install gcc libcurl-devel libxml2-devel ruby-devel
apt-get install gcc libxml2-dev libcurl-dev ruby-dev
probe::sunrpc.clnt.bind_new_program Name probe::sunrpc.clnt.bind_new_program - Bind a new RPC program to an existing client Synopsis sunrpc.clnt.bind_new_program Values progname the name of new RPC program old_prog the number of old RPC program vers the version of new RPC program servername the server machine name old_vers the version of old RPC program old_progname the name of old RPC program prog the number of new RPC program

Commands: