mtpti5iD/redhat-docs_dataset huggingface dataset:
19.5. Bug Fixes The ld linker generates correct dynamic executables Previously, the ld linker failed to create correct dynamic executables and terminated when invoked by the Go language compiler go on the 64-bit ARM architecture. The linker has been updated to correctly handle copy relocations. As a result, the linker no longer fails in the described situation. (BZ# 1430743 ) The ld linker generates correct dynamic relocations for constant data Previously, the ld linker generated an incorrect kind of dynamic relocations for constant data shared between a library and executable on the 64-bit ARM architecture. As a consequence, the produced executable files wasted resources and terminated unexpectedly when the shared data was accessed. The linker has been updated to generate correct dynamic relocations, and the described problem no longer occurs. (BZ#1452170) qrwlock is now enabled for 64-bit ARM systems This update introduces the qrwlock queued read-write lock for 64-bit ARM systems. The implementation of this mechanism improves performance and prevents lock starvation by ensuring fair handling of multiple CPUs competing for the global task lock. This change also resolves a known issue tracked in Red Hat Bugzilla #1454844, which was present in earlier releases and which caused soft lockups under heavy load. Note that any kernel modules built for versions of Red Hat Enterprise Linux 7 for ARM (against the kernel-alt packages) must be rebuilt against the updated kernel. CMA disabled by default On 64-bit ARM Red Hat Enterprise Linux systems with memory limited to 1G or below, the Contiguous Memory Allocator (CMA) consumed large amount of memory, thus leaving insufficient memory for the rest of the kernel. Consequently, the out-of-memory (OOM) condition sometimes occurred in the kernel or certain user-space applications, such as Shared Memory in Linux (SHM)(/dev/shm). The CMA support in the Red Hat Enterprise Linux kernel is now disabled by default for all architectures, and CMA no longer causes OOM.(BZ# 1519317 )

Commands:
Chapter 2. AMQ Streams installation methods You can install AMQ Streams on OpenShift 4.6 to 4.10 in two ways. Installation method Description Installation artifacts (YAML files) Download Red Hat AMQ Streams 2.1 OpenShift Installation and Example Files from the AMQ Streams software downloads page . Deploy the YAML installation artifacts to your OpenShift cluster using oc . You start by deploying the Cluster Operator from install/cluster-operator to a single namespace, multiple namespaces, or all namespaces. You can also use the install/ artifacts to deploy the following: AMQ Streams administrator roles ( strimzi-admin ) A standalone Topic Operator ( topic-operator ) A standalone User Operator ( user-operator ) AMQ Streams Drain Cleaner ( drain-cleaner ) OperatorHub Use the Red Hat Integration - AMQ Streams in the OperatorHub to deploy AMQ Streams to a single namespace or all namespaces. For the greatest flexibility, choose the installation artifacts method. The OperatorHub method provides a standard configuration and allows you to take advantage of automatic updates.

Commands:
4.82. graphviz 4.82.1. RHBA-2011:0965 - graphviz bug fix update Updated graphviz packages that fix several bugs are now available for Red Hat Enterprise Linux 6. Graphviz is graph visualization software used to represent structural information as diagrams, abstract graphs or networks. Bug Fixes BZ# 624658 Several links in the Graphviz Documentation Index file led to nonexistent or incorrectly named files. This update fixes these links so that their targets resolve correctly. BZ# 624690 The graphviz test suite was disabled on the PowerPC, 64-bit PowerPC and SPARC64 architectures due to unexpected terminations with segmentation faults. The test code used in the test suite did not set the TextLayout plugin correctly, which led to the crash of the test suite. This has been fixed and the test suite passes on all architectures. BZ# 640247 Prior to this update, the About dialog box displayed "<unknown>" instead of the real name of the DotEdit utility. This has been fixed and the name is now displayed correctly. BZ# 679715 When using the graphviz utility with PHP, the gv.so module did not load and displayed the following error message: This was caused by the SWIG tool which used the zend_error_noreturn() function to build the PHP module. SWIG has been modified and the bug no longer occurs. All users of graphviz are advised to upgrade to these updated packages, which fix these bugs.

Commands:
/usr/lib64/php/modules/gv.so' - /usr/lib64/php/modules/gv.so: undefined symbol: zend_error_noreturn in Unknown on line 0
1.3. SELinux Architecture SELinux is a Linux Security Module (LSM) that is built into the Linux kernel. The SELinux subsystem in the kernel is driven by a security policy which is controlled by the administrator and loaded at boot. All security-relevant, kernel-level access operations on the system are intercepted by SELinux and examined in the context of the loaded security policy. If the loaded policy allows the operation, it continues. Otherwise, the operation is blocked and the process receives an error. SELinux decisions, such as allowing or disallowing access, are cached. This cache is known as the Access Vector Cache (AVC). When using these cached decisions, SELinux policy rules need to be checked less, which increases performance. Remember that SELinux policy rules have no effect if DAC rules deny access first.

Commands:
Chapter 1. Development workflow The development workflow involves creating, updating, securing, and deploying applications. It also allows integration with various repositories, container registries, and CI/CD tools for flexibility. Step Description Install RHTAP Install RHTAP to enable secure and efficient DevSecOps workflows. Create an application Use pre-built templates to create an application. These templates are customizable and include pipelines and configurations to simplify the development process. When creating an application you can choose: GitHub (default), Gitlab, or Bitbucket for repositories Quay (default) or Jfrog Artifactory for registries Tekton (default), GitHub Actions, Jenkins CI, or GitLab CI for CI/CD workflows Note If you select Bitbucket, GitLab CI, or Jenkins CI during application setup, you must configure these tools to trigger pipeline runs. Update an application Push updates to your application code. The pipeline automatically processes and secures the changes. View security insights Pipeline runs provide a visual representation of all tasks, offering insights into security checks and compliance. Deploy an application Promote your application from Development to Staging and then to Production environments. (Optional) Customize templates and pipelines Modify templates and pipelines to meet your organization's specific requirements. step Install Red Hat Trusted Application Pipeline . If you have already installed Red Hat Trusted Application Pipeline, build an application with sample software templates .

Commands:
Chapter 4. Migrating Camel Quarkus projects 4.1. Updating projects to the latest Quarkus version We recommend that you use Maven to update and upgrade your projects to the latest Quarkus version. Section 4.1.2, "Updating with Maven" Important For projects that use Hibernate ORM or Hibernate Reactive, review the Hibernate ORM 5 to 6 migration quick reference. The following update command covers only a subset of this guide. 4.1.1. Prerequisites Roughly 30 minutes JDK installed with JAVA_HOME configured appropriately Apache Maven 3.8.6 Optionally, the Quarkus CLI if you want to use it A project based on Camel Quarkus version 2.13 or later. 4.1.2. Updating with Maven Configure your extension registry client as described in the Configuring Quarkus extension registry client section of the Quarkus Getting Started guide. Update with Maven: Go to the project directory and update the project to the latest stream: Ensure that the Quarkus Maven plugin version aligns with the latest supported Red Hat build of Quarkus version. Run the update with the following command: mvn io.quarkus.platform:quarkus-maven-plugin:3.5.2:update -N For multi-module projects use following command find . -type f -name "pom.xml" -execdir sh -c 'mvn io.quarkus.platform:quarkus-maven-plugin:3.5.2:update -N' \; Optional By default, this command updates to the latest current version. To update to a specific stream instead of latest current version, add the stream option to this command followed by the version; for example: --Dstream=3.2 Note Updates of multi-module project may show a lot of errors, because the update tool fails to update modules with <packaging>pom</packaging> . If such modules are present (typically containing versions), update them manually. Analyze the update command output for potential instructions and perform the suggested tasks if needed. Use a diff tool to inspect all changes. Review the migration guide for items that were not updated by the update command. If your project has such items, implement the additional steps advised in these topics. Ensure the project builds without errors, all tests pass, and the application functions as required before deploying to production. Before deploying your updated Quarkus application to production, ensure the following: The project builds without errors. All tests pass. The application functions as required.

Commands:
mvn io.quarkus.platform:quarkus-maven-plugin:3.5.2:update -N
find . -type f -name "pom.xml" -execdir sh -c 'mvn io.quarkus.platform:quarkus-maven-plugin:3.5.2:update -N' \;
5.77. gcc 5.77.1. RHBA-2012:0941 - gcc bug fix and enhancement update Updated gcc packages that fix various bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The gcc packages include C, C++, Java, Fortran, Objective C, Objective C++, and Ada 95 GNU compilers, along with related support libraries. Bug Fixes BZ# 751767 The gfortran compiler could fail to compile the code with an internal compiler error. This happened because the gfc_type_for_size() function from the trans-types.c library did not return the correct data type if the demanded bit precision was less than the built-in bit precision size of the corresponding type. With this update, the function returns the corresponding wider type if no suitable narrower type has been found and the code is compiled correctly. BZ# 756138 The G++ compiler terminated unexpectedly with a segmentation fault and returned an internal compiler error when compiling with the -O2 or -O3 optimization option. This happened because the compiler tried to cancel the same loop twice in the remove_path() function. With this update, the loop is canceled only once and the segmentation fault no longer occurs in this scenario. BZ# 756651 Previously, GCC could generate incorrect code if combining instructions when splitting a two-set pattern. This was due to an error in the way the split patterns were handled while combining the instructions. With this update, the code handling instruction combining has been fixed and the problem no longer occurs. BZ# 767604 Previously, GCC could terminate unexpectedly with an internal compiler error, which was triggered by aggressive loop peeling enabled by the "-mtune=z10" setting when moving registers. With this update, the registers are determined from the instruction patterns correctly and the compilation succeeds in this scenario. BZ# 799491 Typing into Web Console in Firefox caused Firefox to terminate unexpectedly. This happened because the compiler incorrectly cloned one of the functions called under these circumstances. With this update, the function is no longer cloned and the problem no longer occurs. Enhancement BZ# 739443 Previously, the GCC compiler did not contain the header with functions for converting the half-float type. This update adds the header and also fixes GCC so that it works correctly with the "-march=native" option on AMD FX processor microarchitectures. All users of gcc are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Appendix B. Revision History Revision History Revision 1.1-7.400 2013-10-31 Rudiger Landmann Rebuild with publican 4.0.0 Revision 1.1-7 2012-07-18 Anthony Towns Rebuild for Publican 3.0 Revision 1.1-0 Wed Mar 17 2010 Paul Kennedy Resolves #570798 Clarifies the number of nodes supported. Revision 1.0-0 Wed Apr 01 2009

Commands:
Chapter 5. Unsupported and deprecated features Cryostat 2.0 removes some features because of their high maintenance costs, low community interest, and better alternative solutions. ContainerJFR variants The Cryostat namespace replaces the ContainerJFR namespace, so Cryostat 2.0 no longer specifies any variants of the ContainerJFR namespace. Event specifier string syntax Cryostat 2.0 does not include any event specific string syntax. Event templates offer a better alternative to event specific string syntax. Interactive mode commands The HTTP API and Notification Channels replace the Command Channel. You cannot use any Command Channel implementations or their CommandExecutor interfaces in Cryostat 2.0. TTY/TCP execution modes Cryostat 2.0 does not contain any TTY and TCP socket execution modes or any mode's configurations. These execution modes did not support platform authentication or target authentication. You can continue to use the supported WebSocket execution mode. WebSocket commands Cryostat 2.0 removed all WebSocket commands. These commands were deprecated in the Cryostat 1 release. WebSever IO cleanup Cryostat 2.0 removed the low-memory pressure mode for embedded WebSever IOs. You can no longer use this mode to apply a constant memory size mapping to an embedded WebServer IO.

Commands:
1.3. Storage Array Support By default, DM Multipath includes support for the most common storage arrays that themselves support DM Multipath. For information on the default configuration values, including supported devices, run either of the following commands. If your storage array supports DM Multipath and is not configured by default, you may need to add it to the DM Multipath configuration file, multipath.conf . For information on the DM Multipath configuration file, see Chapter 4, The DM Multipath Configuration File . Some storage arrays require special handling of I/O errors and path switching. These require separate hardware handler kernel modules.

Commands:
multipathd show config multipath -t
8.154. numad 8.154.1. RHBA-2014:1594 - numad bug fix update Updated numad packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The numad packages provide a daemon for NUMA (Non-Uniform Memory Architecture) systems, monitors NUMA characteristics and manages placement of processes and memory to minimize memory latency. The packages also provide an interface that can be used to query the numad daemon for the best manual placement of an application. Bug Fixes BZ# 872524 Previously, running the numad daemon on a system executing a process with very large resident memory, such as a Windows Server 2012 guest, could cause memory swapping. As a consequence, significant latencies under some circumstances occurred on the system, which could in turn lead to other processes, such as qemu-kvm, becoming unresponsive. With this update, numad no longer causes memory swapping in the above scenario, and the consequent latencies and hangs no longer occur. BZ# 999062 Prior to this update, when a process bound to a set of NUMA nodes depleted the system memory, the system started memory swapping instead of using other NUMA nodes for memory allocation. Consequently, the system experienced significant latencies or became unresponsive. With this update, numad unbinds memory nodes after moving the process memory, which allows for other nodes to be used for memory allocation, and thus prevents the described latencies and hangs. BZ# 1011908 Previously, the numad daemon ignored existing control groups when localizing QEMU threads, and as a consequence, it incorrectly consolidated all running threads into a single control group. This update introduces numad support for multiple control groups, and numad therefore no longer moves QEMU threads into undesired control groups. Users of numad are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.4.5. Validating SCAP Content Before you start using a security policy on your systems, you should first verify the policy in order to avoid any possible syntax or semantic errors in the policy. The oscap utility can be used to validate the security content against standard SCAP XML schemas. The validation results are printed to the standard error stream (stderr). The general syntax of such a validation command is the following: oscap module validate [ module_options_and_arguments ] file Where file is the full path to the file being validated. The only exception is the data stream module ( ds ), which uses the sds-validate operation instead of validate . Note that all SCAP components within the given data stream are validated automatically, and none of the components is specified separately, as can be seen in the following example: With certain SCAP content, such as OVAL specification, you can also perform a Schematron validation. The Schematron validation is slower than the standard validation but provides deeper analysis, and is thus able to detect more errors. The following SSG example shows typical usage of the command:

Commands:
~]USD oscap ds sds-validate /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml
~]USD oscap oval validate --schematron /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml
14.5. Manual ID Range Extension and Assigning a New ID Range In certain situations, it is necessary to manually adjust an ID range: An assigned ID range has been depleted A replica has exhausted the ID range that was assigned to it, and requesting additional IDs failed because no more free IDs are available in the ID ranges of other replicas. You want to extend the ID range assigned to the replica. This might involve splitting an existing ID range or extending it past the initial configured ID range for the server. Alternatively, you might want to assign a new ID range. Note If you assign a new ID range, the UIDs of the already existing entries on the server or replica stay the same. This does not pose a problem because even if you change the current ID range, IdM keeps a record of what ranges were assigned in the past. A replica stopped functioning ID range is not automatically retrieved when a replica dies and needs to be deleted, which means the ID range previously assigned to the replica becomes unavailable. You want to recover the ID range and make it available for other replicas. If you want to recover the ID range belonging to a server that stopped functioning and assign it to another server, first find out what are the ID range values using the ipa-replica-manage dnarange-show command described in Section 14.3, "Displaying Currently Assigned ID Ranges" , and then manually assign that ID range to the server. Also, to avoid duplicate UIDs or GIDs, make sure that no ID value from the recovered range was previously assigned to a user or group; you can do this by examining the UIDs and GIDs of existent users and groups. To manually define the ID ranges, use the following two commands: ipa-replica-manage dnarange-set allows you to define the current ID range for a specified server: ipa-replica-manage dnanextrange-set allows you to define the ID range for a specified server: For more information about these commands, see the ipa-replica-manage (1) man page. Important Be careful not to create overlapping ID ranges. If any of the ID ranges you assign to servers or replicas overlap, it could result in two different servers assigning the same ID value to different entries. Do not set ID ranges that include UID values of 1000 and lower; these values are reserved for system use. Also, do not set an ID range that would include the 0 value; the SSSD service does not handle the 0 ID value. When extending an ID range manually, make sure that the newly extended range is included in the IdM ID range; you can check this using the ipa idrange-find command. Run the ipa idrange-find -h command to display help for how to use ipa idrange-find .

Commands:
ipa-replica-manage dnarange-set masterA.example.com 1250-1499
ipa-replica-manage dnanextrange-set masterB.example.com 1001-5000
8.134. man-pages-ja 8.134.1. RHEA-2014:0681 - man-pages-ja enhancement update An updated man-pages-ja package that adds various enhancements is now available for Red Hat Enterprise 6. The man-pages-ja package contains manual pages in Japanese. Enhancements BZ# 976137 The description of the syslog option in the Japanese version of the sudoers(5) manual page has been amended to correctly match the English version. BZ# 993511 The "Files" section in the Japanese version of the crontab(1) manual page has been amended to correctly match the English version. BZ# 1035088 The Japanese version of the nfs(5) manual page has been updated to reflect the current English version more closely. BZ# 1059046 The explanation of the sysconf(_SC_GETGR_R_SIZE_MAX) call in the getgrnam(3) manual page has been amended to describe the function of sysconf(_SC_GETGR_R_SIZE_MAX) clearly and correctly. Users of man-pages-ja are advised to upgrade to this updated package, which adds these enhancements.

Commands:
Chapter 65. KafkaStatus schema reference Used in: Kafka Property Property type Description conditions Condition array List of status conditions. observedGeneration integer The generation of the CRD that was last reconciled by the operator. listeners ListenerStatus array Addresses of the internal and external listeners. kafkaNodePools UsedNodePoolStatus array List of the KafkaNodePools used by this Kafka cluster. clusterId string Kafka cluster Id. operatorLastSuccessfulVersion string The version of the Streams for Apache Kafka Cluster Operator which performed the last successful reconciliation. kafkaVersion string The version of Kafka currently deployed in the cluster. kafkaMetadataVersion string The KRaft metadata.version currently used by the Kafka cluster. kafkaMetadataState string (one of [PreKRaft, ZooKeeper, KRaftMigration, KRaftDualWriting, KRaftPostMigration, KRaft]) Defines where cluster metadata are stored. Possible values are: ZooKeeper if the metadata are stored in ZooKeeper; KRaftMigration if the controllers are connected to ZooKeeper, brokers are being rolled with Zookeeper migration enabled and connection information to controllers, and the metadata migration process is running; KRaftDualWriting if the metadata migration process finished and the cluster is in dual-write mode; KRaftPostMigration if the brokers are fully KRaft-based but controllers being rolled to disconnect from ZooKeeper; PreKRaft if brokers and controller are fully KRaft-based, metadata are stored in KRaft, but ZooKeeper must be deleted; KRaft if the metadata are stored in KRaft.

Commands:
probe::ioscheduler_trace.elv_requeue_request Name probe::ioscheduler_trace.elv_requeue_request - Fires when a request is Synopsis ioscheduler_trace.elv_requeue_request Values rq Address of request. name Name of the probe point elevator_name The type of I/O elevator currently enabled. rq_flags Request flags. disk_minor Disk minor number of request. disk_major Disk major no of request. Description put back on the queue, when the hadware cannot accept more requests.

Commands: