mtpti5iD/redhat-docs_dataset huggingface dataset:
7.184. rng-tools 7.184.1. RHBA-2015:1416 - rng-tools bug fix and enhancement update Updated rng-tools packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The rng-tools packages contain the random number generator user space utilities, such as the rngd daemon. Note The rng-tools packages have been upgraded to upstream version 5, which provides a number of bug fixes and enhancements over the version. Notably, this update enables the RDRAND and RDSEED hardware random number generator instructions on supported Intel x86- and Intel 64-based EM64T and AMD64 CPU models. (BZ# 833620 ) Users of rng-tools are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 8. Managing PKI ACME Responder This chapter describes how to manage PKI ACME Responder . For information on how to set up PKI ACME Responder, see the Setting up PKI ACME Responder chapter in the Red Hat Certificate System Planning, Installation, and Deployment Guide . 8.1. Enabling/Disabling ACME Services Users that belong to the Administrators group can enable or disable services in the ACME responder. The user can authenticate either with basic authentication or client certificate authentication. To enable or disable ACME services with basic authentication, specify the username and password: To enable or disable ACME services with client certificate authentication, specify the certificate nickname and NSS database password:

Commands:
pki -u <username> -p <password> acme-<enable/disable>
pki -n <nickname> -c <password> acme-<enable/disable>
7.5. Other Printer Types There are other types of printers available, mostly special-purpose printers for professional graphics or publishing organizations. These printers are not for general purpose use, however. Because they are relegated to niche uses, their prices (both one-time and recurring consumables costs) tend to be higher relative to more mainstream units. Thermal Wax Printers These printers are used mostly for business presentation transparencies and for color proofing (creating test documents and images for close quality inspection before sending off master documents to be printed on industrial four-color offset printers). Thermal wax printers use sheet-sized, belt driven CMYK ribbons and specially-coated paper or transparencies. The printhead contains heating elements that melt each wax color onto the paper as it is rolled through the printer. Dye-Sublimation Printers Used in organizations such as service bureaus -- where professional quality documents, pamphlets, and presentations are more important than consumables costs -- dye-sublimation (or dye-sub) printers are the workhorses of quality CMYK printing. The concepts behind dye-sub printers are similar to thermal wax printers except for the use of diffusive plastic dye film instead of colored wax. The printhead heats the colored film and vaporizes the image onto specially coated paper. Dye-sub is quite popular in the design and publishing world as well as the scientific research field, where preciseness and detail are required. Such detail and print quality comes at a price, as dye-sub printers are also known for their high costs-per-page. Solid Ink Printers Used mostly in the packaging and industrial design industries, solid ink printers are prized for their ability to print on a wide variety of paper types. Solid ink printers, as the name implies, use hardened ink sticks that that are melted and sprayed through small nozzles on the printhead. The paper is then sent through a fuser roller which further forces the ink onto the paper. The solid ink printer is ideal for prototyping and proofing new designs for product packages; as such, most service-oriented businesses would not have a need for this type of printer.

Commands:
Chapter 5. Fixed issues The issues fixed in AMQ Streams 2.1 on RHEL are shown in the following table. For details of the issues fixed in Kafka 3.1.0, refer to the Kafka 3.1.0 Release Notes . Table 5.1. Fixed common vulnerabilities and exposures (CVEs) Issue Number Description ENTMQST-2851 CVE-2021-3520 lz4: memory corruption due to an integer overflow bug caused by memmove argument ENTMQST-3631 CVE-2021-43797 netty: control chars in header names may lead to HTTP request smuggling

Commands:
Chapter 2. Using FIPS mode with MicroShift You can use FIPS mode with RPM-based installations of MicroShift on Red Hat Enterprise Linux (RHEL) 9. To enable FIPS mode in MicroShift containers, the worker machine kernel must be enabled to run in FIPS mode before the machine starts. Using FIPS with Red Hat Enterprise Linux for Edge (RHEL for Edge) images is not supported. Using FIPS with image mode for RHEL is not supported. 2.1. FIPS mode with RHEL RPM-based installations Using FIPS with MicroShift requires enabling the cryptographic module self-checks in your Red Hat Enterprise Linux (RHEL) installation. After the host operating system has been configured to start with the FIPS modules, MicroShift containers are automatically enabled to run in FIPS mode. When RHEL is started in FIPS mode, MicroShift core components use the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 validation on only the x86_64 architectures. You must enable FIPS mode when you install RHEL 9 on the machines that you plan to use as worker machines. Important Because FIPS must be enabled before the operating system that your cluster uses starts for the first time, you cannot enable FIPS after you deploy a cluster. MicroShift uses a FIPS-compatible Golang compiler. FIPS is supported in the CRI-O container runtime. 2.1.1. Limitations TLS implementation FIPS support is not complete. The FIPS implementation does not offer a single function that both computes hash functions and validates the keys that are based on that hash. This limitation continues to be evaluated for improvement in future MicroShift releases. 2.2. Additional resources Switching RHEL to FIPS mode

Commands:
3.3. Network Architecture Networking in Red Hat Virtualization includes basic networking, networking within a cluster, and host networking configurations. Basic networking The basic hardware and software elements that facilitate networking. Networking within a cluster Network interactions among cluster objects such as hosts, logical networks and virtual machines. Host networking configurations Supported configurations for networking within a host. A well designed and built network ensures that high bandwidth tasks receive adequate bandwidth, that latency does not impact user interactions, and that virtual machines can be successfully migrated within a migration domain. A poorly built network can cause unacceptable latency, and migration and cloning failures that result from network flooding. An alternative method of managing your network is by integrating with Cisco Application Centric Infrastructure (ACI), by configuring Red Hat Virtualization on Cisco's Application Policy Infrastructure Controller (APIC) version 3.1(1) and later according to Cisco's documentation . On the Red Hat Virtualization side, all that is required is connecting the hosts' NICs to the network and the virtual machines' vNICs to the required network. The remaining configuration tasks are managed by Cisco ACI.

Commands:
Preface Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To propose improvements, open a Jira issue and describe your suggested changes. Provide as much detail as possible to enable us to address your request quickly. Prerequisite You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one. Procedure Click the following link: Create issue . In the Summary text box, enter a brief description of the issue. In the Description text box, provide the following information: The URL of the page where you found the issue. A detailed description of the issue. You can leave the information in any other fields at their default values. Click Create to submit the Jira issue to the documentation team. Thank you for taking the time to provide feedback.

Commands:
3.2. libvirt and libvirt Tools The libvirt package provides a hypervisor-independent virtualization API that can interact with the virtualization capabilities of a range of operating systems. It includes: A virtualization layer to securely manage virtual machines on a host. An interface for managing local and networked hosts. The APIs required to provision, create, modify, monitor, control, migrate, and stop virtual machines. Although multiple hosts may be accessed with libvirt simultaneously, the APIs are limited to single node operations. Note Only operations supported by the hypervisor can be performed using libvirt. libvirt focuses on managing single hosts and provides APIs to enumerate, monitor and use the resources available on the managed node, including CPUs, memory, storage, networking and Non-Uniform Memory Access (NUMA) partitions. The management tools do not need to be on the same physical machine as the machines on which the hosts are running. In such a scenario, the machine on which management tools run communicates with the machines on which the hosts are running using secure protocols. Red Hat Enterprise Linux 6 supports libvirt and includes libvirt -based tools as its default method for virtualization management (as in Red Hat Virtualization Management). The libvirt package is available as free software under the GNU Lesser General Public License. The libvirt project aims to provide a long term stable C API to virtualization management tools, running on top of varying hypervisor technologies. The libvirt package supports Xen on Red Hat Enterprise Linux 5, and it supports KVM on both Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6. Notably, libvirt also provides the two central tools for controlling virtualization on Red Hat Enterprise Linux 6: virsh and virt-manager

Commands:
11.6. Additional Resources The following is a list of additional documentation about email applications. 11.6.1. Installed Documentation Information on configuring Sendmail is included with the sendmail and sendmail-cf packages. /usr/share/sendmail-cf/README.cf - Contains information on m4 , file locations for Sendmail, supported mailers, how to access enhanced features, and more. In addition, the sendmail and aliases man pages contain helpful information covering various Sendmail options and the proper configuration of the Sendmail /etc/mail/aliases file. /usr/share/doc/postfix- <version-number> - Contains a large amount of information about ways to configure Postfix. Replace <version-number> with the version number of Postfix. /usr/share/doc/fetchmail- <version-number> - Contains a full list of Fetchmail features in the FEATURES file and an introductory FAQ document. Replace <version-number> with the version number of Fetchmail. /usr/share/doc/procmail- <version-number> - Contains a README file that provides an overview of Procmail, a FEATURES file that explores every program feature, and an FAQ file with answers to many common configuration questions. Replace <version-number> with the version number of Procmail. When learning how Procmail works and creating new recipes, the following Procmail man pages are invaluable: procmail - Provides an overview of how Procmail works and the steps involved with filtering email. procmailrc - Explains the rc file format used to construct recipes. procmailex - Gives a number of useful, real-world examples of Procmail recipes. procmailsc - Explains the weighted scoring technique used by Procmail to match a particular recipe to a message. /usr/share/doc/spamassassin- <version-number> / - Contains a large amount of information pertaining to SpamAssassin. Replace <version-number> with the version number of the spamassassin package.

Commands:
7.74. graphviz 7.74.1. RHBA-2012:1291 - graphviz bug fix update Updated graphviz packages that fix three bugs are now available for Red Hat Enterprise Linux 6. Graphviz is open-source graph-visualization software. Graph visualization is a way of representing structural information as diagrams of abstract graphs and networks. It has important applications in networking, bioinformatics, software engineering, database and web design, machine learning, and in visual interfaces for other technical domains. Bug Fixes BZ# 772637 Previously, the dot tool could generate different images on 32-bit and 64-bit architectures, which could consequently lead to multilib conflicts of packages that use graphviz during its build process. The problem was caused by different instructions used for floating points processing. On 32-bit Intel architecture, the code is now compiled with the "--ffloat-store" compiler flag, which ensures that identical images are generated regardless of the used architecture. BZ#821920 The graphviz-tcl package included the "demo" directory, which contained examples in various languages. This caused implicit dependencies to be introduced. With this update, all examples are installed as documentation, which reduces the number of implicit dependencies. BZ# 849134 The "dot -c" command which is run in the %postun scriptlet recreates graphviz configuration files to be up-to-date with the current state of the installed plug-ins. Previously, if the command failed to load plug-ins specified in the configuration files, warning messages were printed when removing the graphviz-gd package. These messages could have been confusing, and have been therefore removed. All users of graphviz are advised to upgrade to these updated packages, which fix these bugs.

Commands:
5.5.2. Configuring Booleans Run the setsebool utility in the setsebool boolean_name on/off form to enable or disable Booleans. The following example demonstrates configuring the httpd_can_network_connect_db Boolean: By default, the httpd_can_network_connect_db Boolean is off, preventing Apache HTTP Server scripts and modules from connecting to database servers: To temporarily enable Apache HTTP Server scripts and modules to connect to database servers, run the setsebool httpd_can_network_connect_db on command as the Linux root user. Use the getsebool httpd_can_network_connect_db command to verify the Boolean is enabled: This allows Apache HTTP Server scripts and modules to connect to database servers. This change is not persistent across reboots. To make changes persistent across reboots, run the setsebool -P boolean-name on command as the Linux root user: [7] [7] To temporarily revert to the default behavior, as the Linux root user, run the setsebool httpd_can_network_connect_db off command. For changes that persist across reboots, run the setsebool -P httpd_can_network_connect_db off command.

Commands:
~]USD getsebool httpd_can_network_connect_db httpd_can_network_connect_db --> off
~]USD getsebool httpd_can_network_connect_db httpd_can_network_connect_db --> on
~]# setsebool -P httpd_can_network_connect_db on
Chapter 7. Deleting a system from Insights inventory You can delete a system from the Red Hat Hybrid Cloud Console inventory so that the system is no longer visible in the Red Hat Insights for Red Hat Enterprise Linux Inventory or advisor service Systems list. The Insights client will be unregistered on the system and no longer report data to Red Hat Insights for Red Hat Enterprise Linux. To delete a system, complete the steps in the procedure below that is most relevant to your use case. Procedure 1: Delete using the Insights client Enter the following command on the system command line: Procedure 2: Delete from the Red Hat Satellite 6 UI Log in to the Satellite web UI. Navigate to Insights > Inventory. Select the system profile to be unregistered. Click Actions > Unregister . Procedure 3: Delete using the Red Hat Insights API Use this option only when the actual system is destroyed/re-installed. If you use the DELETE API without unregistering the client, hosts will reappear the time the client uploads data. Get the list of system profiles from inventory. If the json_pp command does not exist on the system then install the perl-JSON-PP package. Get the ID of the system from the hosts.json file and confirm system details; for example, "id" : "f59716a6-5d64-4901-b65f-788b1aee25cc". Delete the system profile using the following command:

Commands:
insights-client --unregister
curl -k --user PORTALUSERNAME https://console.redhat.com/api/inventory/v1/hosts | json_pp > hosts.json
yum install perl-JSON-PP
curl -k --user PORTALUSERNAME https://console.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc
curl -k --user PORTALUSERNAME -X "DELETE" https://console.redhat.com/api/inventory/v1/hosts/f59716a6-5d64-4901-b65f-788b1aee25cc
Chapter 22. Set Up JBoss Operations Network (JON) 22.1. About JBoss Operations Network (JON) The JBoss Operations Network (JON) is JBoss' administration and management platform used to develop, test, deploy and monitor the application life cycle. JBoss Operations Network is JBoss' enterprise management solution and is recommended for the management of multiple Red Hat JBoss Data Grid instances across servers. JBoss Operations Network's agent and auto discovery features facilitate monitoring the Cache Manager and Cache instances in JBoss Data Grid. JBoss Operations Network presents graphical views of key runtime parameters and statistics and allows administrators to set thresholds and be notified if usage exceeds or falls under the set thresholds. Important In Red Hat JBoss Data Grid Remote Client-Server mode, statistics are enabled by default. While statistics are useful in assessing the status of JBoss Data Grid, they adversely affect performance and must be disabled if they are not required. In JBoss Data Grid Library mode, statistics are disabled by default and must be explicitly enabled when required. Important To achieve full functionality of JBoss Operations Network library plugin for JBoss Data Grid's Library mode, upgrade to JBoss Operations Network 3.2.0 with patch Update 02 or higher version. For information on upgrading the JBoss Operations Network, see the Upgrading JBoss ON section in the JBoss Operations Network Installation Guide . Report a bug

Commands:
3.2.2. Direct Routing and iptables You may also work around the ARP issue using the direct routing method by creating iptables firewall rules. To configure direct routing using iptables , you must add rules that create a transparent proxy so that a real server will service packets sent to the VIP address, even though the VIP address does not exist on the system. The iptables method is simpler to configure than the arptables_jf method. This method also circumvents the LVS ARP issue entirely, because the virtual IP address(es) only exist on the active LVS director. However, there are performance issues using the iptables method compared to arptables_jf , as there is overhead in forwarding/masquerading every packet. You also cannot reuse ports using the iptables method. For example, it is not possible to run two separate Apache HTTPD Server services bound to port 80, because both must bind to INADDR_ANY instead of the virtual IP addresses. To configure direct routing using the iptables method, perform the following steps: On each real server, enter the following command for every VIP, port, and protocol (TCP or UDP) combination intended to be serviced for the real server: iptables -t nat -A PREROUTING -p <tcp|udp> -d <vip> --dport <port> -j REDIRECT This command will cause the real servers to process packets destined for the VIP and port that they are given. Save the configuration on each real server: The commands above cause the system to reload the iptables configuration on bootup - before the network is started.

Commands:
service iptables save chkconfig --level 2345 iptables on
Installing Red Hat Developer Hub on OpenShift Container Platform Red Hat Developer Hub 1.4 Red Hat Customer Content Services

Commands:
global: auth: backend: enabled: true clusterRouterBase: apps.<clusterName>.com # other Red Hat Developer Hub Helm Chart configurations
Loaded config from app-config-from-configmap.yaml, env 2023-07-24T19:44:46.223Z auth info Configuring "database" as KeyStore provider type=plugin Backend failed to start up Error: Missing required config value at 'backend.database.client'
NAMESPACE=<emphasis><rhdh></emphasis> new-project USD{NAMESPACE} || oc project USD{NAMESPACE}
helm upgrade redhat-developer-hub -i https://github.com/openshift-helm-charts/charts/releases/download/redhat-redhat-developer-hub-1.4.2/redhat-developer-hub-1.4.2.tgz
PASSWORD=USD(oc get secret redhat-developer-hub-postgresql -o jsonpath="{.data.password}" | base64 -d) CLUSTER_ROUTER_BASE=USD(oc get route console -n openshift-console -o=jsonpath='{.spec.host}' | sed 's/^[^.]*\.//') helm upgrade redhat-developer-hub -i "https://github.com/openshift-helm-charts/charts/releases/download/redhat-redhat-developer-hub-1.4.2/redhat-developer-hub-1.4.2.tgz" --set global.clusterRouterBase="USDCLUSTER_ROUTER_BASE" --set global.postgresql.auth.password="USDPASSWORD"
echo "https://redhat-developer-hub-USDNAMESPACE.USDCLUSTER_ROUTER_BASE"
Chapter 1. Developing clients overview Develop Kafka client applications for your Streams for Apache Kafka installation that can produce messages, consume messages, or do both. You can develop client applications for use with Streams for Apache Kafka on OpenShift or Streams for Apache Kafka 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. Streams for Apache Kafka 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 Streams for Apache 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 Streams for Apache 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 Streams for Apache Kafka on OpenShift Using Streams for Apache Kafka on RHEL in KRaft mode Using Streams for Apache Kafka on RHEL with ZooKeeper 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: