mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Installing Red Hat build of OpenJDK with the MSI installer This procedure describes how to install Red Hat build of OpenJDK 11 for Microsoft Windows using the MSI-based installer. Procedure Download the MSI-based installer of Red Hat build of OpenJDK 11 for Microsoft Windows. Run the installer for Red Hat build of OpenJDK 11 for Microsoft Windows. Click on the welcome screen. Check I accept the terms in license agreement , then click . Click . Accept the defaults or review the optional properties . Click Install . Click Yes on the Do you want to allow this app to make changes on your device? . Verify the Red Hat build of OpenJDK 11 for Microsoft Windows is successfully installed, run java -version command in the command prompt and you must get the following output:

Commands:
openjdk version "11.0.3-redhat" 2019-04-16 LTS OpenJDK Runtime Environment 18.9 (build 11.0.3-redhat+7-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.3-redhat+7-LTS, mixed mode)
Chapter 14. Using Cruise Control to modify topic replication factor Make requests to the /topic_configuration endpoint of the Cruise Control REST API to modify topic configurations, including the replication factor. Prerequisites You are logged in to Red Hat Enterprise Linux as the kafka user. You have configured Cruise Control . You have deployed the Cruise Control Metrics Reporter . Procedure Start the Cruise Control server. The server starts on port 9092 by default; optionally, specify a different port. cd /opt/cruise-control/ ./kafka-cruise-control-start.sh config/cruisecontrol.properties <port_number> To verify that Cruise Control is running, send a GET request to the /state endpoint of the Cruise Control server: curl -X GET 'http://<cc_host>:<cc_port>/kafkacruisecontrol/state' Run the bin/kafka-topics.sh command with the --describe option and to check the current replication factor of the target topic: /opt/kafka/bin/kafka-topics.sh \ --bootstrap-server localhost:9092 \ --topic <topic_name> \ --describe Update the replication factor for the topic: curl -X POST 'http://<cc_host>:<cc_port>/kafkacruisecontrol/topic_configuration?topic=<topic_name>&replication_factor=<new_replication_factor>&dryrun=false' For example, curl -X POST 'localhost:9090/kafkacruisecontrol/topic_configuration?topic=topic1&replication_factor=3&dryrun=false' . Run the bin/kafka-topics.sh command with the --describe option, as before, to see the results of the change to the topic.

Commands:
cd /opt/cruise-control/ ./kafka-cruise-control-start.sh config/cruisecontrol.properties <port_number>
curl -X GET 'http://<cc_host>:<cc_port>/kafkacruisecontrol/state'
/opt/kafka/bin/kafka-topics.sh --bootstrap-server localhost:9092 --topic <topic_name> --describe
curl -X POST 'http://<cc_host>:<cc_port>/kafkacruisecontrol/topic_configuration?topic=<topic_name>&replication_factor=<new_replication_factor>&dryrun=false'
Chapter 5. Enabling kdump For your RHEL 9 systems, you can configure enabling or disabling the kdump functionality on a specific kernel or on all installed kernels. However, you must routinely test the kdump functionality and validate its working status. 5.1. Enabling kdump for all installed kernels The kdump service starts by enabling kdump.service after the kexec tool is installed. You can enable and start the kdump service for all kernels installed on the machine. Prerequisites You have administrator privileges. Procedure Add the crashkernel= command-line parameter to all installed kernels: xxM is the required memory in megabytes. Enable the kdump service: Verification Check that the kdump service is running: 5.2. Enabling kdump for a specific installed kernel You can enable the kdump service for a specific kernel on the machine. Prerequisites You have administrator privileges. Procedure List the kernels installed on the machine. Add a specific kdump kernel to the system's Grand Unified Bootloader (GRUB) configuration. For example: xxM is the required memory reserve in megabytes. Enable the kdump service. Verification Check that the kdump service is running. 5.3. Disabling the kdump service You can stop the kdump.service and disable the service from starting on your RHEL 9 systems. Prerequisites Fulfilled requirements for kdump configurations and targets. For details, see Supported kdump configurations and targets . All configurations for installing kdump are set up according to your needs. For details, see Installing kdump . Procedure To stop the kdump service in the current session: To disable the kdump service: Warning It is recommended to set kptr_restrict=1 as default. When kptr_restrict is set to (1) as default, the kdumpctl service loads the crash kernel regardless of whether the Kernel Address Space Layout ( KASLR ) is enabled. If kptr_restrict is not set to 1 and KASLR is enabled, the contents of /proc/kore file are generated as all zeros. The kdumpctl service fails to access the /proc/kcore file and load the crash kernel. The kexec-kdump-howto.txt file displays a warning message, which recommends you to set kptr_restrict=1 . Verify for the following in the sysctl.conf file to ensure that kdumpctl service loads the crash kernel: Kernel kptr_restrict=1 in the sysctl.conf file. Additional resources Managing systemd

Commands:
grubby --update-kernel=ALL --args="crashkernel=xxM"
systemctl enable --now kdump.service
systemctl status kdump.service ○ kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled) Active: active (live)
ls -a /boot/vmlinuz- * /boot/vmlinuz-0-rescue-2930657cd0dc43c2b75db480e5e5b4a9 /boot/vmlinuz-4.18.0-330.el8.x86_64 /boot/vmlinuz-4.18.0-330.rt7.111.el8.x86_64
grubby --update-kernel= vmlinuz-4.18.0-330.el8.x86_64 --args="crashkernel= xxM "
systemctl enable --now kdump.service
systemctl status kdump.service ○ kdump.service - Crash recovery kernel arming Loaded: loaded (/usr/lib/systemd/system/kdump.service; enabled; vendor preset: disabled) Active: active (live)
systemctl stop kdump.service
systemctl disable kdump.service
4.53. e2fsprogs 4.53.1. RHBA-2011:1735 - e2fsprogs bug fix and enhancement update Updated e2fsprogs packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The e2fsprogs packages contain a number of utilities that create, check, modify, and correct inconsistencies in ext2, ext3, and ext4 file systems. This includes e2fsck (which repairs file system inconsistencies after an unclean shutdown), mke2fs (which initializes a partition to contain an empty file system), tune2fs (which modifies file system parameters), and most of the other core file system utilities. Bug Fixes BZ# 676465 Running the "e2fsck" command on certain corrupted file systems failed to correct all errors during the first run. This occurred when a file had its xattr block cloned as a duplicate, but the block was later removed from the file because the file system did not contain the xattr feature. However, the block was not cleared from the block bitmaps. During the second run, e2fsck found the cloned xattr block as in use, but not owned by any file, and had to repair the block bitmaps. With this update, the processing of duplicate xattr blocks is skipped on non-xattr file systems. All problems are now discovered during the first run. BZ# 679931 On certain devices with very large physical sector size, the mke2fs utility set the block size to be as large as the size of the physical sector. In some cases, the size of the physical sector was larger than the page size. As a consequence, the file system could not be mounted and, in rare cases, the utility could even fail. With this update, the default block size is not set to be larger than the system's page size, even for large physical sector devices. BZ# 683906 Previously, multiple manual pages contained typos. These typos have been corrected with this update. BZ# 713475 This update modifies parameters of the "mke2fs" command to be consistent with the "discard" and "nodiscard" mount options for all system tools (like mount, fsck, or mkfs). The user is now also informed about the ongoing discard process. BZ# 730083 Previously, the libcomm_err libraries were built without the read-only relocation (RELRO) flag. Programs built against these libraries could be vulnerable to various attacks based on overwriting the ELF section of a program. To enhance the security, the e2fsprogs package is now provided with partial RELRO support. Enhancements BZ# 679892 Previously, the tune2fs tool could not set "barrier=0" as the default option on the ext3 and ext4 file systems. With this update, users are now able to set this option when creating the file system, and do not have to maintain the option in the /etc/fstab file across all of the file systems and servers. BZ# 713468 Previously, raw e2image output files could be extremely large sparse files, which were difficult to copy, archive, and transport. This update adds support for exporting images in the qcow format. Images in this format are small and easy to manipulate. Users are advised to upgrade to these updated e2fsprogs packages, which fix these bugs and add these enhancements.

Commands:
17.6. Establishing a Token Ring Connection A token ring network is a network in which all the computers are connected in a circular pattern. A token , or a special network packet, travels around the token ring and allows computers to send information to each other. Note For more information on using token rings under Linux, refer to the Linux Token Ring Project website available at http://www.linuxtr.net/ . To add a token ring connection, follow these steps: Click the Devices tab. Click the New button on the toolbar. Select Token Ring connection from the Device Type list and click Forward . If you have already added the token ring card to the hardware list, select it from the Tokenring card list. Otherwise, select Other Tokenring Card to add the hardware device. If you selected Other Tokenring Card , the Select Token Ring Adapter window as shown in Figure 17.10, "Token Ring Settings" appears. Select the manufacturer and model of the adapter. Select the device name. If this is the system's first token ring card, select tr0 ; if this is the second token ring card, select tr1 (and so on). The Network Administration Tool also allows the user to configure the resources for the adapter. Click Forward to continue. Figure 17.10. Token Ring Settings On the Configure Network Settings page, choose between DHCP and static IP address. You may specify a hostname for the device. If the device receives a dynamic IP address each time the network is started, do not specify a hostname. Click Forward to continue. Click Apply on the Create Tokenring Device page. After configuring the token ring device, it appears in the device list as shown in Figure 17.11, "Token Ring Device" . Figure 17.11. Token Ring Device Be sure to select File => Save to save the changes. After adding the device, you can edit its configuration by selecting the device from the device list and clicking Edit . For example, you can configure whether the device is started at boot time. When the device is added, it is not activated immediately, as seen by its Inactive status. To activate the device, select it from the device list, and click the Activate button. If the system is configured to activate the device when the computer starts (the default), this step does not have to be performed again.

Commands:
1.2. Image Builder terminology Blueprints Blueprints define customized system images by listing packages and customizations that will be part of the system. Blueprints can be edited and they are versioned. When a system image is created from a blueprint, the image is associated with the blueprint in the Image Builder interface of the RHEL 7 web console. Blueprints are presented to the user as plain text in the Tom's Obvious, Minimal Language (TOML) format. Compose Composes are individual builds of a system image, based on a particular version of a particular blueprint. Compose as a term refers to the system image, the logs from its creation, inputs, metadata, and the process itself. Customization Customizations are specifications for the system, which are not packages. This includes user accounts, groups, kernel, timezone, locale, firewall and ssh key.

Commands:
Appendix A. Using your subscription Debezium 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 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 . Scroll down to INTEGRATION AND AUTOMATION . Click the name of a component to display a list of the artifacts that are available to download. Click the Download link for the artifact that you want. Revised on 2024-10-09 03:04:12 UTC

Commands:
Chapter 2. Red Hat Enterprise Linux Atomic Host 7.8.3 2.1. Atomic Host OStree update : New Tree Version: 7.8.3 (hash: dfd383553c0f25c503272b0d193ac863f2deede0fa69278391bd2b1e6d02b56a) Changes since Tree Version 7.8.2 (hash: 48c78ed67690eff2c0ab803c163753ea3d3f00ec001a05f37b41eb6d71b463ab) 2.1.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Universal Base Image 7 Init Container Image (rhel7/ubi7-init) 2.1.2. Last release This is the last release of Red Hat Enterprise Linux Atomic Host.

Commands:
Appendix A. Revision History Revision History Revision 1.0-56 Thu May 23 2019 Jiri Herrmann Version for 7.6 GA publication Revision 1.0-55 Thu Oct 25 2018 Jiri Herrmann Version for 7.6 GA publication Revision 1.0-53 Thu Aug 5 2018 Jiri Herrmann Version for 7.6 Beta publication Revision 1.0-52 Thu Apr 5 2018 Jiri Herrmann Version for 7.5 GA publication Revision 1.0-49 Thu Jul 27 2017 Jiri Herrmann Version for 7.4 GA publication Revision 1.0-46 Mon Oct 17 2016 Jiri Herrmann Version for 7.3 GA publication Revision 1.0-44 Mon Dec 21 2015 Laura Novich Republished the guide for several bug fixes Revision 1.0-43 Thu Oct 08 2015 Jiri Herrmann Cleaned up the Revision History Revision 1.0-42 Sun Jun 28 2015 Jiri Herrmann Updated for the 7.2 beta release

Commands:
2.2.7.2. Python Documentation For more information about Python, see man python . You can also install python-docs , which provides HTML manuals and references in the following location: file:///usr/share/doc/python-docs- version /html/index.html For details on library and language components, use pydoc component_name . For example, pydoc math will display the following information about the math Python module: The main site for the Python development project is hosted on python.org .

Commands:
Help on module math: NAME math FILE /usr/lib64/python2.6/lib-dynload/mathmodule.so DESCRIPTION This module is always available. It provides access to the mathematical functions defined by the C standard. FUNCTIONS acos[...] acos(x) Return the arc cosine (measured in radians) of x. acosh[...] acosh(x) Return the hyperbolic arc cosine (measured in radians) of x. asin(...) asin(x) Return the arc sine (measured in radians) of x. asinh[...] asinh(x) Return the hyperbolic arc sine (measured in radians) of x.
Chapter 1. Red Hat OpenShift Service on AWS 4 Documentation Welcome to the official Red Hat OpenShift Service on AWS (ROSA) documentation, where you can learn about ROSA and start exploring its features. To learn about ROSA, interacting with ROSA by using Red Hat OpenShift Cluster Manager and command-line interface (CLI) tools, consumption experience, and integration with Amazon Web Services (AWS) services, start with the Introduction to ROSA documentation . To navigate the ROSA documentation, use the left navigation bar.

Commands:
7.145. mlocate 7.145.1. RHBA-2012:1355 - mlocate bug fix update Updated mlocate packages that fix two bugs are now available for Red Hat Enterprise 6. The mlocate packages provide a locate/updatedb implementation. Mlocate keeps a database of all existing files and allows you to look up files by name. Bug Fixes BZ# 690800 Prior to this update, the locate(1) manual page contained a misprint. This update corrects the misprint. BZ# 699363 Prior to this update, the mlocate tool aborted the "updatedb" command if an incorrect filesystem implementation returned a zero-length file name. As a consequence, the locate database was not be updated. This update detects invalid zero-length file names, warns about them, and continues to the locate database. All users of mlocate are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 5. Changes in Rust 1.71.1 Toolset Rust Toolset has been updated from version 1.66.1 to 1.71.1 on RHEL 8 and RHEL 9. Notable changes include: A new implementation of multiple producer, single consumer (mpsc) channels to improve performance. A new Cargo sparse index protocol for more efficient use of the crates.io registry. New OnceCell and OnceLock types for one-time value initialization. A new C-unwind ABI string to enable usage of forced unwinding across Foreign Function Interface (FFI) boundaries. For detailed information regarding the updates, see the series of upstream release announcements: Announcing Rust 1.67.0 Announcing Rust 1.68.0 Announcing Rust 1.69.0 Announcing Rust 1.70.0 Announcing Rust 1.71.0

Commands:
Chapter 5. Unsupported features when using JBoss EAP in Microsoft Azure There are some unsupported features when using JBoss EAP in Microsoft Azure. ActiveMQ Artemis High Availability Using a Shared Store JBoss EAP messaging high availability using Artemis shared stores is not supported in Microsoft Azure. To configure JBoss EAP messaging high availability in Azure, see the instructions in the Configuration for ActiveMQ Artemis high availability in Microsoft Azure section. mod_custer Advertising If you want to use JBoss EAP as an Undertow mod_cluster proxy load balancer, the mod_cluster advertisement functionally is unsupported because of Azure UDP multicast limitations. For more information, see Configuration for load balancing with mod_cluster in Microsoft Azure . Virtual Machine Scale Set Transactions in Microsoft Azure Virtual Machine Scale Set (VMSS) is unsupported because the automatic scale down feature does not wait for all transactions to be completed during the scale down process. This could cause data integrity issues. Microsoft Azure VMSS destroys an EAP VM and does not support proper shutdown, which results in the following limitation for EAP clustering: VMSS should be supported for the configurations, in which the server-side state for HA needs to be externalized to a third-party service, such as Red Hat Data Grid. JBoss EAP supports VMSS for HttpSessions externalization, but not for the stateful session bean. Azure App Service JTS is not supported in the JBoss EAP Azure App Service offering. Note Although JTS is not supported, Jakarta Transactions are supported under the following conditions: The automatic removal of instances is disabled. Instances are not removed manually, for example, by reducing the number of running instances using the Azure dashboard. Also, transactions over Jakarta Enterprise Beans-remoting are not supported.

Commands:
8.6. The Replication Queue In replication mode, Red Hat JBoss Data Grid uses a replication queue to replicate changes across nodes based on the following: Previously set intervals. The queue size exceeding the number of elements. A combination of previously set intervals and the queue size exceeding the number of elements. The replication queue ensures that during replication, cache operations are transmitted in batches instead of individually. As a result, a lower number of replication messages are transmitted and fewer envelopes are used, resulting in improved JBoss Data Grid performance. A disadvantage of using the replication queue is that the queue is periodically flushed based on the time or the queue size. Such flushing operations delay the realization of replication, distribution, or invalidation operations across cluster nodes. When the replication queue is disabled, the data is directly transmitted and therefore the data arrives at the cluster nodes faster. A replication queue is used in conjunction with asynchronous mode. Report a bug 8.6.1. Replication Queue Usage When using the replication queue, do one of the following: Disable asynchronous marshalling. Set the max-threads count value to 1 for the transport executor . The transport executor is defined in standalone.xml or clustered.xml as follows: To implement either of these solutions, the replication queue must be in use in asynchronous mode. Asynchronous mode can be set, along with the queue timeout ( queue-flush-interval , value is in milliseconds) and queue size ( queue-size ) as follows: Example 8.1. Replication Queue in Asynchronous Mode The replication queue allows requests to return to the client faster, therefore using the replication queue together with asynchronous marshalling does not present any significant advantages. Report a bug

Commands:
<transport executor="infinispan-transport"/>
<replicated-cache name="asyncCache" start="EAGER" mode="ASYNC" batching="false" indexing="NONE" statistics="true" queue-size="1000" queue-flush-interval="500"> <!-- Additional configuration information here --> </replicated-cache>