mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Developing clients overview Develop Kafka client applications for your AMQ Streams installation that can produce messages, consume messages, or do both. You can develop client applications for use with AMQ Streams on OpenShift or AMQ Streams on RHEL. Messages comprise an optional key and a value that contains the message data, plus headers and related metadata. The key identifies the subject of the message, or a property of the message. You must use the same key if you need to process a group of messages in the same order as they are sent. Messages are delivered in batches. Messages contain headers and metadata that provide details that are useful for filtering and routing by clients, such as the timestamp and offset position for the message. Kafka provides client APIs for developing client applications. Kafka producer and consumer APIs are the primary means of interacting with a Kafka cluster in a client application. The APIs control the flow of messages. The producer API sends messages to Kafka topics, while the consumer API reads messages from topics. AMQ Streams supports clients written in Java. How you develop your clients depends on your specific use case. Data durability might be a priority or high throughput. These demands can be met through configuration of your clients and brokers. All clients, however, must be able to connect to all brokers in a given Kafka cluster. 1.1. Supporting a HTTP client As an alternative to using the Kafka producer and consumer APIs in your client, you can set up and use the AMQ Streams Kafka Bridge. The Kafka Bridge provides a RESTful interface that allows HTTP-based clients to interact with a Kafka cluster. It offers the advantages of a web API connection to Strimzi, without the need for client applications that need to interpret the Kafka protocol. Kafka uses a binary protocol over TCP. For more information, see Using the AMQ Streams Kafka Bridge . 1.2. Tuning your producers and consumers You can add more configuration properties to optimize the performance of your Kafka clients. You probably want to do this when you've had some time to analyze how your client and broker configuration performs. For more information, see Kafka configuration tuning . 1.3. Monitoring client interaction Distributed tracing facilitates the end-to-end tracking of messages. You can enable tracing in Kafka consumer and producer client applications. For more information, see the documentation for distributed tracing in the following guides: Deploying and Upgrading AMQ Streams on OpenShift Using AMQ Streams on RHEL Note When we use the term client application, we're specifically referring to applications that use Kafka producers and consumers to send and receive messages to and from a Kafka cluster. We are not referring to other Kafka components, such as Kafka Connect or Kafka Streams, which have their own distinct use cases and functionality.

Commands:
Chapter 5. Profiles There are features in Red Hat Single Sign-On that are not enabled by default, these include features that are not fully supported. In addition there are some features that are enabled by default, but that can be disabled. The features that can be enabled and disabled are: Name Description Enabled by default Support level account2 New Account Management Console Yes Supported account_api Account Management REST API Yes Supported admin_fine_grained_authz Fine-Grained Admin Permissions No Preview ciba OpenID Connect Client Initiated Backchannel Authentication (CIBA) Yes Supported client_policies Add client configuration policies Yes Supported client_secret_rotation Enables client secret rotation for confidential clients Yes Preview par OAuth 2.0 Pushed Authorization Requests (PAR) Yes Supported declarative_user_profile Configure user profiles using a declarative style No Preview docker Docker Registry protocol No Supported impersonation Ability for admins to impersonate users Yes Supported openshift_integration Extension to enable securing OpenShift No Preview recovery_codes Recovery codes for authentication No Preview scripts Write custom authenticators using JavaScript No Preview step_up_authentication Step-up authentication Yes Supported token_exchange Token Exchange Service No Preview upload_scripts Upload scripts No Deprecated web_authn W3C Web Authentication (WebAuthn) Yes Supported update_email Update Email Workflow No Preview To enable all preview features start the server with: You can set this permanently by creating the file standalone/configuration/profile.properties (or domain/servers/server-one/configuration/profile.properties for server-one in domain mode). Add the following to the file: To enable a specific feature start the server with: For example to enable Docker use -Dkeycloak.profile.feature.docker=enabled . You can set this permanently in the profile.properties file by adding: To disable a specific feature start the server with: For example to disable Impersonation use -Dkeycloak.profile.feature.impersonation=disabled . You can set this permanently in the profile.properties file by adding:

Commands:
bin/standalone.sh|bat -Dkeycloak.profile=preview
profile=preview
bin/standalone.sh|bat -Dkeycloak.profile.feature.<feature name>=enabled
feature.docker=enabled
bin/standalone.sh|bat -Dkeycloak.profile.feature.<feature name>=disabled
feature.impersonation=disabled
Chapter 5. MTR 1.2.4 5.1. New features This section describes the new features of the Migration Toolkit for Runtimes (MTR) 1.2.4: New rules support the migration of Red Hat JBoss Enterprise Application Platform (EAP 7) to EAP 8. New rules support the migration of Jakarta EE applications to Quarkus. 5.2. Known issues For a complete list of all known issues, see the list of MTR 1.2.4 known issues in Jira. 5.3. Resolved issues CVE-2023-26159: follow-redirects package before 1.15.4 are vulnerable to Improper Input Validation Versions of the follow-redirects package before 1.15.4 are vulnerable to Improper Input Validation. This vulnerability is due to the improper handling of URLs by the url.parse() function. When a new URL returns an error, it can be manipulated to misinterpret the hostname. An attacker could exploit this weakness to redirect traffic to a malicious site, potentially leading to information disclosure, phishing attacks, or other security breaches. For more details, see (CVE-2023-26159) . CVE-2022-25883: Regular Expression Denial of Service (ReDoS) vulnerability was discovered in the node-semver package Versions of the semver npm package before 7.5.2 are vulnerable to Regular Expression Denial of Service (ReDoS). This ReDoS vulnerability comes from the new Range function, when untrusted user data is provided as a range. For more details, see (CVE-2022-25883) . CVE-2023-26136: tough-cookie package before 4.1.3 are vulnerable to Prototype Pollution Versions of the tough-cookie package before 4.1.3 are vulnerable to Prototype Pollution. This vulnerability is due to improper handling of Cookies when using CookieJar in rejectPublicSuffixes=false mode. This issue arises from the manner in which the objects are initialized. For more details, see (CVE-2023-26136) . CVE-2023-35116: jackson-databind before 2.15.2 are vulnerable to Denial of Service or other unspecified impact Versions of the jackson-databind library before 2.15.2 are vulnerable to Denial of Service (DoS) attacks or other unspecified impacts using a crafted object that uses cyclic dependencies. For more details, see (CVE-2023-35116) . For a complete list of all issues resolved in this release, see the list of MTR 1.2.4 resolved issues in Jira.

Commands:
1.3. Related Documentation For more information about using Red Hat Enterprise Linux, see the following resources: Installation Guide - Documents relevant information regarding the installation of Red Hat Enterprise Linux 6. Deployment Guide - Documents relevant information regarding the deployment, configuration and administration of Red Hat Enterprise Linux 6. Storage Administration Guide - Provides instructions on how to effectively manage storage devices and file systems on Red Hat Enterprise Linux 6. For more information about the High Availability Add-On and the Resilient Storage Add-On for Red Hat Enterprise Linux 6, see the following resources: High Availability Add-On Overview - Provides a high-level overview of the Red Hat High Availability Add-On. Cluster Administration - Provides information about installing, configuring and managing the Red Hat High Availability Add-On, Global File System 2: Configuration and Administration - Provides information about installing, configuring, and maintaining Red Hat GFS2 (Red Hat Global File System 2), which is included in the Resilient Storage Add-On. DM Multipath - Provides information about using the Device-Mapper Multipath feature of Red Hat Enterprise Linux 6. Load Balancer Administration - Provides information on configuring high-performance systems and services with the Load Balancer Add-On, a set of integrated software components that provide Linux Virtual Servers (LVS) for balancing IP load across a set of real servers. Release Notes - Provides information about the current release of Red Hat products. Red Hat documents are available in HTML, PDF, and RPM versions on the Red Hat Enterprise Linux Documentation CD and online at https://access.redhat.com/site/documentation/ .

Commands:
2.8. ss ss is a command-line utility that prints statistical information about sockets, allowing administrators to assess device performance over time. By default, ss lists open non-listening TCP sockets that have established connections, but a number of useful options are provided to help administrators filter out statistics about specific sockets. Red Hat recommends using ss over netstat in Red Hat Enterprise Linux 7. One common usage is ss -tmpie which displays detailed information (including internal information) about TCP sockets, memory usage, and processes using the socket. ss is provided by the iproute package. For more information, see the man page:

Commands:
man ss
Chapter 4. Performance impact of alt-java The alt-java binary contains the SSB mitigation, so the SSB mitigation performance impact no longer exists on java . Note Using alt-java might significantly reduce the performance of Java programs. You can find detailed information of some Java performance issues that might exist with using alt-java by selecting any of the Red Hat Bugzilla links listed in the Additional resources section. Additional resources (java-11-openjdk) Seccomp related performance regression in RHEL8 . (java-1.8.0-openjdk) Seccomp related performance regression in RHEL8 . CVE-2018-3639 Detail . CVE-2018-3639 hw: cpu: speculative store bypass . CVE-2018-3639 java-1.8.0-openjdk: hw: cpu: speculative store bypass (rhel-7.6) Revised on 2024-05-10 09:08:04 UTC

Commands:
16.3. Installation To install libguestfs, guestfish, the libguestfs tools, guestmount and support for Windows guest virtual machines, subscribe to the Red Hat Enterprise Linux V2WIN channel, go to the Red Hat Website and run the following command: To install every libguestfs-related package including the language bindings, run the following command:

Commands:
yum install libguestfs guestfish libguestfs-tools libguestfs-winsupport
yum install '*guestf*'
Chapter 13. Change requests in Business Central If you have more than one branch in a Business Central project and you make a change in a branch that you want to merge to another branch, you can create a change request. Any user with permission to view the target branch, usually the master branch, can see the change request. 13.1. Creating change requests You can create a change request in a Business Central project after you have made a change in your project, for example after you have added or deleted an attribute to an asset. Prerequisites You have more than one branch of a Business Central project. You made a change in one branch that you want to merge to another branch. Procedure In Business Central, go to Menu Design Projects and select the space and project that contains the change that you want to merge. On the project page, select the branch that contains the change. Figure 13.1. Select a branch menu Do one of the following tasks to submit the change request: Click in the upper-right corner of the screen and select Submit Change Request . Click the Change Requests tab and then click Submit Change Request . The Submit Change Request window appears. Enter a summary and a description, select the target branch, and click Submit . The target branch is the branch where the change will be merged. After you click Submit , the change request window appears. 13.2. Working with change requests You can view change requests for any branch that you have access to. You must have administrator permissions to accept a change request. Prerequisites You have more than one branch of a Business Central project. Procedure In Business Central, go to Menu Design Projects and select a space and project. On the project page, verify that you are on the correct branch. Click the Change Requests tab. A list of pending change requests appears. To filter change requests, select Open , Closed , or All to the left of the Search box. To search for specific change requests, enter an ID or text in the Search box and click the magnifying glass. To view the change request details, click the summary link. The change request window has two tabs: Review the Overview tab for general information about the change request. Click the Changed Files tab and expand a file to review the proposed changes. Click a button in the top right corner. Click Squash and Merge to squash all commits into a single commit and merge the commit to the target branch. Click Merge to merge the changes into the target branch. Click Reject to reject the changes and leave the target branch unchanged. Click Close to close the change request without rejecting or accepting it. Note that only the user who created the submitted the change request can close it. Click Cancel to return to the project window without making any changes.

Commands:
7.253. tcsh 7.253.1. RHBA-2013:0446 - tcsh bug fix update Updated tcsh packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The tcsh packages provide an enhanced and compatible version of the C shell (csh) command language interpreter, which can be used as an interactive login shell, as well as a shell script command processor. Bug Fixes BZ#769157 Prior to this update, the tcsh command language interpreter could run out of memory because of random "sbrk()" failures in the internal "malloc()" function. As a consequence, tcsh could abort with a segmentation fault. This update uses "system malloc" instead and tcsh no longer aborts. BZ#814069 Prior to this update, aliases were inserted into the history buffer when saving the history in loops if the alias included a statement that did not work in the loop. This update no longer allows to save the history in loops. Now, only the first line of loops and the "if" statement are saved in the history. Aliases now work as expected. BZ# 821796 Prior to this update, casting was removed when calling a function in the history file locking patch. As a consequence, multibyte tests failed. This update reverts the status before the patch and tests no longer fail. BZ# 847102 Prior to this update, the tcsh logic did not handle file sourcing as expected. As a consequence, source commands failed when using a single-line "if" statement. This update modifies the underlying code to handle source commands as expected. BZ# 884937 Prior to this update, the SIGINT signal was not blocked when the tcsh command language interpreter waited for the child process to finish. As a consequence, tcsh could be aborted with the key combination Ctrl+c. This update blocks the SIGINT signal and tcsh is no longer aborted. All users of tcsh are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 8. Enabling accelerators Before you can use an accelerator in OpenShift AI, you must install the relevant software components. The installation process varies based on the accelerator type. Prerequisites You have logged in to your OpenShift cluster. You have the cluster-admin role in your OpenShift cluster. You have installed an accelerator and confirmed that it is detected in your environment. Procedure Follow the appropriate documentation to enable your accelerator: NVIDIA GPUs : See Enabling NVIDIA GPUs . Intel Gaudi AI accelerators : See Enabling Intel Gaudi AI accelerators . AMD GPUs : See Enabling AMD GPUs . After installing your accelerator, create an accelerator profile as described in: Working with accelerator profiles . Verification From the Administrator perspective, go to the Operators Installed Operators page. Confirm that the following Operators appear: The Operator for your accelerator Node Feature Discovery (NFD) Kernel Module Management (KMM) The accelerator is correctly detected a few minutes after full installation of the Node Feature Discovery (NFD) and the relevant accelerator Operator. The OpenShift command line interface (CLI) displays the appropriate output for the GPU worker node. For example, here is output confirming that an NVIDIA GPU is detected:

Commands:
Expected output when the accelerator is detected correctly describe node <node name> Capacity: cpu: 4 ephemeral-storage: 313981932Ki hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 16076568Ki nvidia.com/gpu: 1 pods: 250 Allocatable: cpu: 3920m ephemeral-storage: 288292006229 hugepages-1Gi: 0 hugepages-2Mi: 0 memory: 12828440Ki nvidia.com/gpu: 1 pods: 250
4.4. Turning Off Local Transactions In some cases, tools or frameworks above JBoss Data Virtualization will call setAutoCommit(false) , commit() and rollback() even when all access is read-only and no transactions are necessary. In the scope of a local transaction, JBoss Data Virtualization will start and attempt to commit an XA transaction, possibly complicating configuration or causing performance degradation. In these cases, you can override the default JDBC behavior to indicate that these methods should perform no action regardless of the commands being executed. To turn off the use of local transactions, add the following property to the JDBC connection URL: Warning Turning off local transactions can be dangerous and can result in inconsistent results when reading or inconsistent data in data stores when writing. For safety, this mode should be used only if you are certain that the calling application does not need local transactions.

Commands:
disableLocalTxn=true
Chapter 12. kar 12.1. kar:create 12.1.1. Description Create a kar file for a list of feature repos 12.1.2. Syntax kar:create [options] repoName [features] 12.1.3. Arguments Name Description repoName Repository name. The kar will contain all features of the named repository by default features Names of the features to include. If set then only these features will be added 12.1.4. Options Name Description --help Display this help message 12.2. kar:install 12.2.1. Description Installs a KAR file. 12.2.2. Syntax kar:install [options] url 12.2.3. Arguments Name Description url The URL of the KAR file to install. 12.2.4. Options Name Description --help Display this help message --no-start Do not start the bundles automatically 12.3. kar:list 12.3.1. Description List the installed KAR files. 12.3.2. Syntax kar:list [options] 12.3.3. Options Name Description --help Display this help message --no-format Disable table rendered output 12.4. kar:uninstall 12.4.1. Description Uninstall a KAR file. 12.4.2. Syntax kar:uninstall [options] name 12.4.3. Arguments Name Description name The name of the KAR file to uninstall. 12.4.4. Options Name Description --help Display this help message

Commands:
function::returnstr Name function::returnstr - Formats the return value as a string Synopsis Arguments format Variable to determine return type base value Description This function is used by the nd_syscall tapset, and returns a string. Set format equal to 1 for a decimal, 2 for hex, 3 for octal. Note that this function should only be used in dwarfless probes (i.e. 'kprobe.function( " foo " )'). Other probes should use return_str .

Commands:
returnstr:string(format:long)
12.2. About Host Entry Configuration Properties A host entry can contain information about the host that is outside its system configuration, such as its physical location, MAC address, keys, and certificates. This information can be set when the host entry is created if it is created manually; otherwise, most of this information needs to be added to the host entry after the host is enrolled in the domain. Table 12.1. Host Configuration Properties UI Field Command-Line Option Description Description --desc = description A description of the host. Locality --locality = locality The geographic location of the host. Location --location = location The physical location of the host, such as its data center rack. Platform --platform = string The host hardware or architecture. Operating system --os = string The operating system and version for the host. MAC address --macaddress = address The MAC address for the host. This is a multi-valued attribute. The MAC address is used by the NIS plug-in to create a NIS ethers map for the host. SSH public keys --sshpubkey = string The full SSH public key for the host. This is a multi-valued attribute, so multiple keys can be set. Principal name (not editable) --principalname = principal The Kerberos principal name for the host. This defaults to the host name during the client installation, unless a different principal is explicitly set in the -p . This can be changed using the command-line tools, but cannot be changed in the UI. Set One-Time Password --password = string Sets a password for the host which can be used in bulk enrollment. - --random Generates a random password to be used in bulk enrollment. - --certificate = string A certificate blob for the host. - --updatedns This sets whether the host can dynamically update its DNS entries if its IP address changes.

Commands: