mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Selecting a specific Red Hat build of OpenJDK from the installed versions for an application You can select a specific Red Hat build of OpenJDK from the installed versions on Microsoft Windows for an application. Prerequisites More than one Red Hat build of OpenJDK is already installed on the system. Procedure Log in as a Windows system administrator. On the command line, set the prompt to C:/ . Enter dir /b /s java.exe to list all of the installed OpenJDKs on the system. Set the value of the environment variable to your Red Hat build of OpenJDK (or JRE) installation path: If the path contains spaces, use the shortened path name. Restart Command Prompt to reload the environment variables. Retrieve the value of the path variable: Set the value of path variable:

Commands:
setx -m JAVA_HOME "Path to Java"
echo %JAVA_HOME%
setx -m PATH "%PATH%;%JAVA_HOME%\bin";
Chapter 1. About this release Red Hat Trusted Application Pipeline 1.4 is now generally available. To learn more about support for all versions, refer to the RHTAP life cycle policy . To learn more about RHTAP, refer to the About RHTAP product overview. To install RHTAP, refer to Installing Red Hat Trusted Application Pipeline . Note The products that the RHTAP installer deploys are production ready, but they are sized for a proof of concept or a very small team. For larger teams, manual reconfiguration of the products is most likely necessary and should be done by following procedures documented for each individual product.

Commands:
Appendix C. Checking OpenShift logs You can use the oc logs command to view the OpenShift logs or the logs that the console provides for a running container. Procedure Enter the following command: Note In the preceding command, replace <pod_name> and <container_name> with appropriate values for your deployment. Access logs are stored in the /opt/jws-6.0/tomcat/logs/ directory.

Commands:
oc logs -f <pod_name> <container_name>
Chapter 25. Guided decision tables Guided decision tables are a wizard-led alternative to spreadsheet decision tables for defining business rules in a tabular format. With guided decision tables, you are led by a UI-based wizard in Business Central that helps you define rule attributes, metadata, conditions, and actions based on specified data objects in your project. After you create your guided decision tables, the rules you defined are compiled into Drools Rule Language (DRL) rules as with all other rule assets. All data objects related to a guided decision table must be in the same project package as the guided decision table. Assets in the same package are imported by default. After you create the necessary data objects and the guided decision table, you can use the Data Objects tab of the guided decision tables designer to verify that all required data objects are listed or to import other existing data objects by adding a New item .

Commands:
8.72. ipmitool 8.72.1. RHBA-2013:1259 - ipmitool bug fix update Updated ipmitool packages that fix several bugs are now available. The ipmitool package contains a command-line utility for interfacing with devices that support the Intelligent Platform Management Interface (IPMI) specification. IPMI is an open standard for machine health, inventory, and remote power control. Bug Fixes BZ# 826027 In a ipmitool update, the new options "-R" and "-N" were added to adjust the retransmission rate of outgoing IPMI requests over LAN and lanplus interfaces. Implementation of these options set a wrong default value of the retransmission timeout, and an outgoing request timed out prematurely. In addition, in some corner cases, ipmitool could terminate unexpectedly with a segmentation fault when the timeout occurred. This update fixes the default timeout value, so ipmitool without the "-N" option retransmits outgoing IPMI requests as in versions, and crashes no longer occur in the described scenario. BZ#903251 Previously, enabling the "ipmi" and "link" keys in user access information using the ipmitool utility did not work properly. Consequently, the values of these settings were not taken into account. A patch has been provided that ensures the values of these settings are read and processed as expected. BZ#923192 In cases of congested network or slow-responding Baseboard Management Controller (BMC), the reply operation timeout triggered the protocol command retry action. Consequently, the ipmitool utility could incorrectly process a LAN session protocol command with the reply from a protocol command. This update fixes handling of expected replies for each command alone, and cleans up expected replies between commands. Now, the retried reply of the first command is correctly ignored while the later command, which is currently pending, is properly processed in the described scenario. Users of ipmitool are advised to upgrade to these updated packages, which fix these bugs. After installing this update, the IPMI event daemon (ipmievd) will be restarted automatically.

Commands:
2.2. Volume Groups Physical volumes are combined into volume groups (VGs). This creates a pool of disk space out of which logical volumes can be allocated. Within a volume group, the disk space available for allocation is divided into units of a fixed-size called extents. An extent is the smallest unit of space that can be allocated. Within a physical volume, extents are referred to as physical extents. A logical volume is allocated into logical extents of the same size as the physical extents. The extent size is thus the same for all logical volumes in the volume group. The volume group maps the logical extents to physical extents.

Commands:
20.2. General Changes In Internationalization New yum-langpacks Plug-In A new Yum plug-in, yum-langpacks enables users to install translation subpackages for various packages for the current language locale. This plug-in also provides Yum commands that show available languages support, display the list of installed languages, allow users to install new languages, remove installed languages and also show which packages will be installed when the user wants to install new language support. These changes can be illustrated by the following example: To install language packs for the Marathi or Czech languages in Red Hat Enterprise Linux 6, run: To install language packs for the Marathi or Czech languages in Red Hat Enterprise Linux 7, run: Please refer to the yum-langpacks(8) man page for more information. Changing Locale and Keyboard Layout Settings localectl is a new utility used to query and change the system locale and keyboard layout settings; the settings are used in text consoles and inherited by desktop environments. localectl also accepts a hostname argument to administer remote systems over SSH.

Commands:
]# yum groupinstall marathi-support ~]# yum groupinstall czech-support
~]# yum langinstall mr ~]# yum langinstall cs
Chapter 5. Additional links and references 5.1. Reference Architectures Deploying Red Hat OpenShift Container Platform 3.11 on Red Hat OpenStack Platform 13 Deploying Red Hat OpenShift Container Platform 4.4 on Red Hat OpenStack Platform 13 and 16 Deploying Red Hat Openshift Container Platform 4.6 and 4.7 on Red Hat Openstack Platform 16.1 5.2. Additional documentation links 5.2.1. Red Hat OpenShift Container Platform Official Product Documentation Installing OpenShift Container Platform on OpenStack clusters Upstream installer code and documentation Installation configuration file parameters for 4.12 Learn more about OpenShift Container Platform 5.2.2. Red Hat OpenStack Platform Official Product Documentation Deploying an overcloud with containerized Red Hat Ceph 5.2.3. Red Hat Ceph Storage Official Product Documentation

Commands:
Chapter 8. Uninstalling Dev Spaces Warning Uninstalling OpenShift Dev Spaces removes all OpenShift Dev Spaces-related user data! Use oc to uninstall the OpenShift Dev Spaces instance. Prerequisites dsc . See: Section 1.2, "Installing the dsc management tool" . Procedure Remove the OpenShift Dev Spaces instance: Tip The --delete-namespace option removes the OpenShift Dev Spaces namespace. The --delete-all option removes the Dev Workspace Operator and the related resources.

Commands:
dsc server:delete
Chapter 6. DNS-as-a-service (designate) parameters You can modify the designate service with DNS parameters. Parameter Description DesignateBindQueryLogging Set to true to enable logging of queries on BIND. The default value is false . DesignateManagedResourceEmail Configure email address to be set in zone SOAs. Leaving unset results in service defaults being used. DesignateMdnsProxyBasePort Configure the base port for the MiniDNS proxy endpoints on the external/public access network. The default value is 16000 . DesignateMinTTL Configure the minimum allowable TTL in seconds. The default value is 0 which leaves the parameter unset. The default value is 0 . DesignateWorkers Number of workers for Designate services. The default value is 0 . UnboundAllowedCIDRs A list of CIDRs allowed to make queries through Unbound. Example, [ 192.0.2.0/24 , 198.51.100.0/24 ]. UnboundAllowRecursion When false, Unbound will not attempt to recursively resolve the request. It will only answer for queries using local information. The default value is true . UnboundDesignateIntegration Set to false to disable configuring neutron using the deployed unbound server as the default resolver. The default value is true . UnboundForwardFallback When true, if the forwarded query receives a SERVFAIL, Unbound will process the request as a standard recursive resolution. The default value is true . UnboundForwardResolvers A list of DNS resolver IP addresses, with optional port, that Unbound will forward resolution requests to if Unbound does not have the answer. Example, [ 192.0.2.10 , 192.0.2.20@53 ]. UnboundLogQueries If true, Unbound will log the query requests. The default value is false . UnboundSecurityHarden When true, Unbound will block certain queries that could have security implications to the Unbound service. The default value is true .

Commands:
11.8. Controlling the Selection of Network Device Names Device naming can be controlled in the following manner: By identifying the network interface device Setting the MAC address in an ifcfg file using the HWADDR directive enables it to be identified by udev . The name will be taken from the string given by the DEVICE directive, which by convention is the same as the ifcfg suffix. For example, ifcfg - enp1s0 . By turning on or off biosdevname The name provided by biosdevname will be used (if biosdevname can determine one). By turning on or off the systemd-udev naming scheme The name provided by systemd-udev will be used (if systemd-udev can determine one).

Commands:
Chapter 6. Observability 6.1. Health & Liveness checks Health & liveness checks are supported via the MicroProfile Health extension. They can be configured via the Camel Health API or via Quarkus MicroProfile Health. All configured checks are available on the standard MicroProfile Health endpoint URLs: http://localhost:8080/q/health http://localhost:8080/q/health/live http://localhost:8080/q/health/ready 6.2. Metrics We provide MicroProfile Metrics for exposing metrics. Some basic Camel metrics are provided for you out of the box, and these can be supplemented by configuring additional metrics in your routes. Metrics are available on the standard Quarkus metrics endpoint: http://localhost:8080/q/metrics

Commands:
Chapter 94. ExternalConfigurationEnv schema reference The type ExternalConfigurationEnv has been deprecated. Please use ContainerEnvVar instead. Used in: ExternalConfiguration Property Property type Description name string Name of the environment variable which will be passed to the Kafka Connect pods. The name of the environment variable cannot start with KAFKA_ or STRIMZI_ . valueFrom ExternalConfigurationEnvVarSource Value of the environment variable which will be passed to the Kafka Connect pods. It can be passed either as a reference to Secret or ConfigMap field. The field has to specify exactly one Secret or ConfigMap.

Commands:
Appendix A. Tool Reference This appendix provides a quick reference for the various tools in Red Hat Enterprise Linux 7 that can be used to tweak performance. See the relevant man page for your tool for complete, up-to-date, detailed reference material. A.1. irqbalance irqbalance is a command line tool that distributes hardware interrupts across processors to improve system performance. It runs as a daemon by default, but can be run once only with the --oneshot option. The following parameters are useful for improving performance. --powerthresh Sets the number of CPUs that can idle before a CPU is placed into powersave mode. If more CPUs than the threshold are more than 1 standard deviation below the average softirq workload and no CPUs are more than one standard deviation above the average, and have more than one irq assigned to them, a CPU is placed into powersave mode. In powersave mode, a CPU is not part of irq balancing so that it is not woken unnecessarily. --hintpolicy Determines how irq kernel affinity hinting is handled. Valid values are exact ( irq affinity hint is always applied), subset ( irq is balanced, but the assigned object is a subset of the affinity hint), or ignore ( irq affinity hint is ignored completely). --policyscript Defines the location of a script to execute for each interrupt request, with the device path and irq number passed as arguments, and a zero exit code expected by irqbalance . The script defined can specify zero or more key value pairs to guide irqbalance in managing the passed irq . The following are recognized as valid key value pairs. ban Valid values are true (exclude the passed irq from balancing) or false (perform balancing on this irq ). balance_level Allows user override of the balance level of the passed irq . By default the balance level is based on the PCI device class of the device that owns the irq . Valid values are none , package , cache , or core . numa_node Allows user override of the NUMA node that is considered local to the passed irq . If information about the local node is not specified in ACPI, devices are considered equidistant from all nodes. Valid values are integers (starting from 0) that identify a specific NUMA node, and -1 , which specifies that an irq should be considered equidistant from all nodes. --banirq The interrupt with the specified interrupt request number is added to the list of banned interrupts. You can also use the IRQBALANCE_BANNED_CPUS environment variable to specify a mask of CPUs that are ignored by irqbalance . For further details, see the man page:

Commands:
man irqbalance
22.4.2. Useful Websites http://www.samba.org/ - The Samba webpage contains useful documentation, information about mailing lists, and a list of GUI interfaces. http://www.samba.org/samba/docs/using_samba/toc.html - an online version of Using Samba, 2nd Edition by Jay Ts, Robert Eckstein, and David Collier-Brown; O'Reilly &Associates

Commands:
16.10. Time Zone Configuration Set your time zone by selecting the city closest to your computer's physical location. Click on the map to zoom in to a particular geographical region of the world. From here there are two ways for you to select your time zone: Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red X appears indicating your selection. You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection. If Red Hat Enterprise Linux is the only operating system on your computer, select System clock uses UTC . The system clock is a piece of hardware on your computer system. Red Hat Enterprise Linux uses the timezone setting to determine the offset between the local time and UTC on the system clock. This behavior is standard for systems that use UNIX, Linux, and similar operating systems. Click to proceed. Note To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool . Type the system-config-date command in a shell prompt to launch the Time and Date Properties Tool . If you are not root, it prompts you for the root password to continue.

Commands:
2.7. GNOME Power Manager GNOME Power Manager is a daemon that is installed as part of the GNOME desktop. Much of the power-management functionality that GNOME Power Manager provided in earlier versions of Red Hat Enterprise Linux has become part of DeviceKit-power in Red Hat Enterprise Linux 6 (refer to Section 2.6, "DeviceKit-power and devkit-power" . However, GNOME Power Manager remains a front end for that functionality. Through an applet in the system tray, GNOME Power Manager notifies you of changes in your system's power status; for example, a change from battery to AC power. It also reports battery status, and warns you when battery power is low. GNOME Power Manager also allows you to configure some basic power management settings. To access these settings, click the GNOME Power Manager icon in the system tray, then click Preferences The Power Management Preferences screen contains two tabs: On AC Power General On a laptop, Power Management Preferences will contain a third tab: On Battery Power Use the On AC Power and On Battery Power tabs to specify how much time must pass before the display is turned off on an inactive system, how much time must pass before an inactive system is put to sleep, and whether the system should spin down hard disks when not in use. The On Battery Power tab also allows you to set the display brightness and to choose a behavior for a system with a critically low battery. For example, by default, GNOME Power Manager makes a system hibernate when its battery level reaches a critically low level. Use the General tab to set behaviours for the (physical) power button and suspend button on your system, and to specify the circumstances under which the GNOME Power Manager icon should appear in the system tray.

Commands:
Chapter 16. Supportability and Maintenance ABRT Authorized Micro-Reporting In Red Hat Enterprise Linux 7.1, the Automatic Bug Reporting Tool ( ABRT ) receives tighter integration with the Red Hat Customer Portal and is capable of directly sending micro-reports to the Portal. ABRT provides a utility, abrt-auto-reporting , to easily configure user's Portal credentials necessary to authorize micro-reports. The integrated authorization allows ABRT to reply to a micro-report with a rich text which may include possible steps to fix the cause of the micro-report. For example, ABRT can suggest which packages are supposed to be upgraded or offer Knowledge base articles related to the issue. See the Customer Portal for more information on this feature .

Commands:
C.6. CacheStore org.infinispan.interceptors.CacheWriterInterceptor The CacheStore component stores entries to a CacheStore from memory. Table C.10. Attributes Name Description Type Writable writesToTheStores Number of writes to the store. long No statisticsEnabled Enables or disables the gathering of statistics by this component. boolean Yes Table C.11. Operations Name Description Signature resetStatistics Resets statistics gathered by this component. void resetStatistics() 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
Chapter 3. Prerequisites for the Migration Toolkit for Applications installation The following are the prerequisites for the Migration Toolkit for Applications (MTA) installation: Java Development Kit (JDK) is installed. MTA supports the following JDKs: OpenJDK 11 OpenJDK 17 Oracle JDK 11 Oracle JDK 17 Eclipse TemurinTM JDK 11 Eclipse TemurinTM JDK 17 8 GB RAM macOS installation: the value of maxproc must be 2048 or greater.

Commands:
Chapter 1. Overview Installer-provisioned installation on bare metal nodes deploys and configures the infrastructure that an OpenShift Container Platform cluster runs on. This guide provides a methodology to achieving a successful installer-provisioned bare-metal installation. The following diagram illustrates the installation environment in phase 1 of deployment: For the installation, the key elements in the diagram are: Provisioner : A physical machine that runs the installation program and hosts the bootstrap VM that deploys the control plane of a new OpenShift Container Platform cluster. Bootstrap VM : A virtual machine used in the process of deploying an OpenShift Container Platform cluster. Network bridges : The bootstrap VM connects to the bare metal network and to the provisioning network, if present, via network bridges, eno1 and eno2 . API VIP : An API virtual IP address (VIP) is used to provide failover of the API server across the control plane nodes. The API VIP first resides on the bootstrap VM. A script generates the keepalived.conf configuration file before launching the service. The VIP moves to one of the control plane nodes after the bootstrap process has completed and the bootstrap VM stops. In phase 2 of the deployment, the provisioner destroys the bootstrap VM automatically and moves the virtual IP addresses (VIPs) to the appropriate nodes. The keepalived.conf file sets the control plane machines with a lower Virtual Router Redundancy Protocol (VRRP) priority than the bootstrap VM, which ensures that the API on the control plane machines is fully functional before the API VIP moves from the bootstrap VM to the control plane. Once the API VIP moves to one of the control plane nodes, traffic sent from external clients to the API VIP routes to an haproxy load balancer running on that control plane node. This instance of haproxy load balances the API VIP traffic across the control plane nodes. The Ingress VIP moves to the compute nodes. The keepalived instance also manages the Ingress VIP. The following diagram illustrates phase 2 of deployment: After this point, the node used by the provisioner can be removed or repurposed. From here, all additional provisioning tasks are carried out by the control plane. Note For installer-provisioned infrastructure installations, CoreDNS exposes port 53 at the node level, making it accessible from other routable networks. Additional resources Using DNS forwarding Important The provisioning network is optional, but it is required for PXE booting. If you deploy without a provisioning network, you must use a virtual media baseboard management controller (BMC) addressing option such as redfish-virtualmedia or idrac-virtualmedia .

Commands:
Chapter 4. Remediate issues directly from Insights for Red Hat Enterprise Linux Remote host configuration (rhc) allows you to remediate issues on your Red Hat Enterprise Linux (RHEL) systems directly from Insights for Red Hat Enterprise Linux. Direct remediation is available when you have the rhc client installed on your RHEL 8.5 and later system. For complete remediations documentation for Red Hat Insights, see the Red Hat Insights Remediations Guide .

Commands:
Chapter 5. Increasing the amount of memory that users are allowed to pin in the system Remote direct memory access (RDMA) operations require the pinning of physical memory. As a consequence, the kernel is not allowed to write memory into the swap space. If a user pins too much memory, the system can run out of memory, and the kernel terminates processes to free up more memory. Therefore, memory pinning is a privileged operation. If non-root users need to run large RDMA applications, it is necessary to increase the amount of memory to maintain pages in primary memory pinned all the time. Procedure As the root user, create the file /etc/security/limits.conf with the following contents: Verification Log in as a member of the rdma group after editing the /etc/security/limits.conf file. Note that Red Hat Enterprise Linux applies updated ulimit settings when the user logs in. Use the ulimit -l command to display the limit: If the command returns unlimited , the user can pin an unlimited amount of memory. Additional resources limits.conf(5) man page on your system

Commands:
@rdma soft memlock unlimited @rdma hard memlock unlimited
ulimit -l unlimited