mtpti5iD/redhat-docs_dataset huggingface dataset:
3.12. UDP Unicast Traffic As of the Red Hat Enterprise Linux 6.2 release, the nodes in a cluster can communicate with each other using the UDP Unicast transport mechanism. It is recommended, however, that you use IP multicasting for the cluster network. UDP unicast is an alternative that can be used when IP multicasting is not available. You can configure the Red Hat High-Availability Add-On to use UDP unicast by setting the cman transport="udpu" parameter in the cluster.conf configuration file. You can also specify Unicast from the Network Configuration page of the Conga user interface, as described in Section 4.5.3, "Network Configuration" .

Commands:
Chapter 80. OpenTelemetryTracing schema reference Used in: KafkaBridgeSpec , KafkaConnectSpec , KafkaMirrorMaker2Spec , KafkaMirrorMakerSpec The type property is a discriminator that distinguishes use of the OpenTelemetryTracing type from JaegerTracing . It must have the value opentelemetry for the type OpenTelemetryTracing . Property Property type Description type string Must be opentelemetry .

Commands:
25.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: openshift_use_nfs Having this Boolean enabled allows installing OpenShift on an NFS share. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, enter the following command: Enter the following command to view description of a particular Boolean: Note that the additional policycoreutils-devel package providing the sepolicy utility is required for this command to work.

Commands:
~]USD getsebool -a | grep service_name
~]USD sepolicy booleans -b boolean_name
Appendix A. Using your subscription Service Registry 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 My 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 at access.redhat.com/downloads . Locate the Red Hat Integration entries in the Integration and Automation category. Select the desired Service Registry product. The Software Downloads page opens. Click the Download link for your component. Revised on 2024-02-22 17:15:23 UTC

Commands:
8.25. createrepo 8.25.1. RHBA-2013:0879 - createrepo bug fix update An updated createrepo package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The createrepo package contains a utility that generates a common metadata repository from a directory of RPM packages. Bug Fixes BZ# 877301 Previously, a time-stamp check did not pass if a file did not exist. As a consequence, an empty repository was incorrectly flagged as being up to date and the "createrepo --checkts" command performed no action on an empty repository. With this update, missing file is now considered as a failure, and not a pass. The "createrepo --checkts" command now properly creates a new repository when called on an empty repository. BZ# 892657 The --basedir, --retain-old-md, and --update-md-path options were reported only in the createrepo utility help message but not in the man page. This update amends the man page and the options are now properly documented in both the help message and the man page. Users of createrepo are advised to upgrade to this updated package, which fixes these bugs.

Commands:
16.6. Additional Resources For additional information, see The DHCP Handbook; Ralph Droms and Ted Lemon; 2003 or the following resources. 16.6.1. Installed Documentation dhcpd man page - Describes how the DHCP daemon works. dhcpd.conf man page - Explains how to configure the DHCP configuration file; includes some examples. dhcpd.leases man page - Describes a persistent database of leases. dhcp-options man page - Explains the syntax for declaring DHCP options in dhcpd.conf ; includes some examples. dhcrelay man page - Explains the DHCP Relay Agent and its configuration options. /usr/share/doc/dhcp-< version >/ - Contains sample files, README files, and release notes for current versions of the DHCP service.

Commands:
Chapter 1. Account configuration After creating your account, update basic information about your company. Set your location and add your contact information. Note 1.1. Add your company information Once you have created your new account, add you company information with these steps: Click the gear icon located in the right of the top navigation bar. You will see the Overview window. to the Account Details heading, click the Edit link. Fill in the information for your account. The address you specify here has two goals: If you are on a paid plan, use this address for billing purposes. If you use the billing and payment modules, this address is also what your user will see on your invoices. 1.2. Select your preferred time zone On the same page you can also select the time zone you will use on all system displays. This setting affects analytics graphs. However, billing cycle calculations are made according to UTC time.

Commands:
The account view is only visible to administrators, not to members.
Chapter 5. Configuring the web console in OpenShift Container Platform You can modify the OpenShift Container Platform web console to set a logout redirect URL or disable the quick start tutorials. 5.1. Prerequisites Deploy an OpenShift Container Platform cluster. 5.2. Configuring the web console You can configure the web console settings by editing the console.config.openshift.io resource. Edit the console.config.openshift.io resource: USD oc edit console.config.openshift.io cluster The following example displays the sample resource definition for the console: apiVersion: config.openshift.io/v1 kind: Console metadata: name: cluster spec: authentication: logoutRedirect: "" 1 status: consoleURL: "" 2 1 Specify the URL of the page to load when a user logs out of the web console. If you do not specify a value, the user returns to the login page for the web console. Specifying a logoutRedirect URL allows your users to perform single logout (SLO) through the identity provider to destroy their single sign-on session. 2 The web console URL. To update this to a custom value, see Customizing the web console URL . 5.3. Disabling quick starts in the web console You can use the Administrator perspective of the web console to disable one or more quick starts. Prerequisites You have cluster administrator permissions and are logged in to the web console. Procedure In the Administrator perspective, navigate to Administation Cluster Settings . On the Cluster Settings page, click the Configuration tab. On the Configuration page, click the Console configuration resource with the description operator.openshift.io . From the Action drop-down list, select Customize , which opens the Cluster configuration page. On the General tab, in the Quick starts section, you can select items in either the Enabled or Disabled list, and move them from one list to the other by using the arrow buttons. To enable or disable a single quick start, click the quick start, then use the single arrow buttons to move the quick start to the appropriate list. To enable or disable multiple quick starts at once, press Ctrl and click the quick starts you want to move. Then, use the single arrow buttons to move the quick starts to the appropriate list. To enable or disable all quick starts at once, click the double arrow buttons to move all of the quick starts to the appropriate list.

Commands:
oc edit console.config.openshift.io cluster
apiVersion: config.openshift.io/v1 kind: Console metadata: name: cluster spec: authentication: logoutRedirect: "" 1 status: consoleURL: "" 2
Chapter 1. Features The features added in this release, and that were not in releases of AMQ Streams, are outlined below. Note To view all the enhancements and bugs that are resolved in this release, see the AMQ Streams Jira project . 1.1. Kafka 2.8.0 support AMQ Streams now supports Apache Kafka version 2.8.0. AMQ Streams uses Kafka 2.8.0. Only Kafka distributions built by Red Hat are supported. For upgrade instructions, see AMQ Streams and Kafka upgrades . Refer to the Kafka 2.7.0 and Kafka 2.8.0 Release Notes for additional information. Note Kafka 2.7.x is supported only for the purpose of upgrading to AMQ Streams 1.8. For more information on supported versions, see the Red Hat Knowledgebase article Red Hat AMQ 7 Component Details Page . Kafka 2.8.0 requires ZooKeeper version 3.5.9. Therefore, you need to upgrade ZooKeeper when upgrading from AMQ Streams 1.7 to AMQ Streams 1.8, as described in the upgrade documentation. Warning Kafka 2.8.0 provides early access to self-managed mode , where Kafka runs without ZooKeeper by utilizing the Raft protocol. Note that self-managed mode is not supported in AMQ Streams .

Commands:
8.130. ltrace 8.130.1. RHBA-2014:1604 - ltrace bug fix update Updated ltrace packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The ltrace utility is a debugging program that runs a specified command until the command exits. While the command is executing, ltrace intercepts and records both the dynamic library calls called by the executed process and the signals received by the executed process. The ltrace utility can also intercept and print system calls executed by the process. Bug Fixes BZ# 868280 Previously, the ltrace utility did not support the Position Independent Executables (PIE) binaries, which are linked similarly to shared libraries, and processes. Consequently, addresses found in images of those binaries needed additional adjustment for the actual address where the binary was loaded during the process startup. With this update, the support for the PIE binaries and processes has been added and ltrace now handles the additional processing for the PIE binaries correctly. BZ# 891607 When copying internal structures after cloning a process, the ltrace utility did not copy a string containing a path to an executable properly. This behavior led to errors in heap management and could cause ltrace to terminate unexpectedly. The underlying source code has been modified and ltrace now copies memory when cloning traced processes correctly. Users of ltrace are advised to upgrade to these updated packages, which fix these bugs.

Commands:
24.2. L1 Cache Configuration 24.2.1. L1 Cache Configuration (Library Mode) The following sample configuration shows the L1 cache default values in Red Hat JBoss Data Grid's Library Mode. Example 24.1. L1 Cache Configuration in Library Mode The l1 element configures the cache behavior in distributed cache instances. If used with non-distributed caches, this element is ignored. The enabled parameter enables the L1 cache. The lifespan parameter sets the maximum life span of an entry when it is placed in the L1 cache. Report a bug 24.2.2. L1 Cache Configuration (Remote Client-Server Mode) The following sample configuration shows the L1 cache default values in Red Hat JBoss Data Grid's Remote Client-Server mode. Example 24.2. L1 Cache Configuration for Remote Client-Server Mode The l1-lifespan element is added to a distributed-cache element to enable L1 caching and to set the life span of the L1 cache entries for the cache. This element is only valid for distributed caches. If l1-lifespan is set to 0 or a negative number ( -1 ), L1 caching is disabled. L1 caching is enabled when the l1-lifespan value is greater than 0 . Note When the cache is accessed remotely via the Hot Rod protocol, the client accesses the owner node directly. Therefore, using L1 Cache in this situation does not offer any performance improvement and is not recommended. Other remote clients (Memcached, REST) cannot target the owner, therefore, using L1 Cache may increase the performance (at the cost of higher memory consumption). Note In Remote Client-Server mode, the L1 cache was enabled by default when distributed cache was used, even if the l1-lifespan attribute is not set. The default lifespan value was 10 minutes. Since JBoss Data Grid 6.3, the default lifespan is 0 which disables the L1 cache. Set a non-zero value for the l1-lifespan parameter to enable the L1 cache. Report a bug

Commands:
<clustering mode="dist"> <sync/> <l1 enabled="true" lifespan="60000" /> </clustering>
<distributed-cache l1-lifespan="USD{VALUE}"> <!-- Additional configuration information here --> </distributed-cache>
Chapter 5. Configuring the JAVA_HOME environment variable on RHEL Some applications require you to set the JAVA_HOME environment variable so that they can find the Red Hat build of OpenJDK installation. Prerequisites You know where you installed Red Hat build of OpenJDK on your system. For example, /opt/jdk/11 . Procedure Set the value of JAVA_HOME . Verify that JAVA_HOME is set correctly. Note You can make the value of JAVA_HOME persistent by exporting the environment variable in ~/.bashrc for single users or /etc/bashrc for system-wide settings. Persistent means that if you close your terminal or reboot your computer, you do not need to reset a value for the JAVA_HOME environment variable. The following example demonstrates using a text editor to enter commands for exporting JAVA_HOME in ~/.bashrc for a single user: Additional resources Be aware of the exact meaning of JAVA_HOME . For more information, see Changes/Decouple system java setting from java command setting .

Commands:
export JAVA_HOME=/opt/jdk/11
printenv | grep JAVA_HOME JAVA_HOME=/opt/jdk/11
> vi ~/.bash_profile export JAVA_HOME=/opt/jdk/11 export PATH="USDJAVA_HOME/bin:USDPATH"
17.4.4. Problems with the X Server Crashing and Non-Root Users If you are having trouble with the X server crashing when anyone logs in, you may have a full file system (or, a lack of available hard drive space). To verify that this is the problem you are experiencing, run the following command: The df command should help you diagnose which partition is full. For additional information about df and an explanation of the options available (such as the -h option used in this example), refer to the df man page by typing man df at a shell prompt. A key indicator is 100% full or a percentage above 90% or 95% on a partition. The /home/ and /tmp/ partitions can sometimes fill up quickly with user files. You can make some room on that partition by removing old files. After you free up some disk space, try running X as the user that was unsuccessful before.

Commands:
df -h
Chapter 1. Installing the Directory Server packages This chapter contains information about installing the Red Hat Directory Server packages. Prerequisites Red Hat Enterprise Linux (RHEL) is installed on the server. For details about the RHEL version required by the Red Hat Directory Server version you want to install, see the Red Hat Directory Server 11 Release Notes . The system Directory Server is registered to the Red Hat subscription management service. For details about using Subscription Manager ,see the corresponding section in the Using and Configuring Subscription Manager guide. A valid Red Hat Directory Server subscription is available in your Red Hat account. The RHEL default repositories, BaseOS and AppStream , are enabled. 1.1. Installing the Directory Server packages Use the following procedure to install the Directory Server packages. Procedure If your account has disabled Simple Content Access (SCA): List the available subscriptions in your Red Hat account and identify the pool ID that provides Red Hat Directory Server. For example: Attach the Red Hat Directory Server subscription to the system using the pool ID from the step: Enable the Directory Server packages repository. For example, to enable the Directory Server 11.9 repository, run: Install the redhat-ds:11 module: This command automatically installs all required dependencies. Additional resources For details about installing Red Hat Enterprise Linux and registering the system to the Red Hat Subscription Management service, see Performing a standard RHEL 8 installation . For further details about using the subscription-manager utility, see the Using Red Hat Subscription Manager . For information how to check your status of SCA, see Simple Content Access . For details about available Directory Server repositories, see What are the names of the Red Hat repositories that have to be enabled .

Commands:
subscription-manager list --all --available --matches 'Red Hat Directory Server' Subscription Name: Example Subscription Provides: Red Hat Directory Server Pool ID: 5ab6a8df96b03fd30aba9a9c58da57a1 Available: 1
subscription-manager attach --pool= 5ab6a8df96b03fd30aba9a9c58da57a1 Successfully attached a subscription for: Example Subscription
subscription-manager repos --enable=dirsrv-11.9-for-rhel-8-x86_64-rpms Repository 'dirsrv-11.9-for-rhel-8-x86_64-rpms' is enabled for this system.
yum module install redhat-ds:11
2.3. Installing the Minimum Amount of Packages Required It is best practice to install only the packages you will use because each piece of software on your computer could possibly contain a vulnerability. If you are installing from the DVD media, take the opportunity to select exactly what packages you want to install during the installation. If you find you need another package, you can always add it to the system later. For more information about installing the Minimal install environment, see the Software Selection chapter of the Red Hat Enterprise Linux 7 Installation Guide. A minimal installation can also be performed by a Kickstart file using the --nobase option. For more information about Kickstart installations, see the Package Selection section from the Red Hat Enterprise Linux 7 Installation Guide.

Commands:
Chapter 6. Upgrading AMQ Interconnect You should upgrade AMQ Interconnect to the latest version to ensure that you have the latest enhancements and fixes. The upgrade process involves installing the new AMQ Interconnect packages and restarting your routers. You can use these instructions to upgrade AMQ Interconnect to a new minor release or maintenance release . Minor Release AMQ Interconnect periodically provides point releases, which are minor updates that include new features, as well as bug and security fixes. If you plan to upgrade from one AMQ Interconnect point release to another, for example, from AMQ Interconnect 1.0 to AMQ Interconnect 1.1, code changes should not be required for applications that do not use private, unsupported, or technical preview components. Maintenance Release AMQ Interconnect also periodically provides maintenance releases that contain bug fixes. Maintenance releases increment the minor release version by the last digit, for example from 1.0.0 to 1.0.1. A maintenance release should not require code changes; however, some maintenance releases might require configuration changes. Prerequisites Before performing an upgrade, you should have reviewed the release notes for the target release to ensure that you understand the new features, enhancements, fixes, and issues. To find the release notes for the target release, see the Red Hat Customer Portal . Procedure Upgrade the qpid-dispatch-router and qpid-dispatch-tools packages and their dependencies: USD sudo yum update qpid-dispatch-router qpid-dispatch-tools For more information, see Chapter 5, Installing AMQ Interconnect . Restart each router in your router network. To avoid disruption, you should restart each router one at a time. This example restarts a router in Red Hat Enterprise Linux 7: USD systemctl restart qdrouterd.service For more information about starting a router, see Section 5.3, "Starting a router" .

Commands:
sudo yum update qpid-dispatch-router qpid-dispatch-tools
systemctl restart qdrouterd.service
8.73. gnome-session 8.73.1. RHBA-2014:1585 - gnome-session bug fix and enhancement update Updated gnome-session packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The gnome-session packages manage the GNOME desktop session. It starts up the other core components of GNOME and handles logout and saving of the session. Bug Fixes BZ# 684767 Due to insufficient checking, the "Switch User" button appeared in the logout dialog window even when user switching was disabled by the lock down configuration. A patch has been provided to fix this bug, and the "Switch User" button is now removed when the user logs out. BZ# 785828 , BZ# 1069503 Due to incorrect clean up of resources at shutdown, the "Startup Applications" GUI did not submit changes immediately. If the user closed the dialog window earlier than 2 seconds after making a change, the change failed to be committed. To fix this bug, the dialog window on shutdown has been deleted, so that its dispose handler commits pending changes immediately. As a result, the user can enable or disable additional startup programs and quickly close the dialog window without the risk of losing changes. BZ# 982423 Prior to this update, there were inadequate checks in the gnome-session utility for a preexisting gnome-session instance. Consequently, running gnome-session within a GNOME session started a nested broken session. With this update, a check for the SESSION_MANAGER environment variable has been added. As a result, if the user runs gnome-session within a preexisting session by mistake, an error message is returned. In addition, this update adds the following Enhancement BZ# 786573 Previously, if the user accidentally clicked "Remember Running Applications" and was using the custom session selector, they could not proceed without saving. This update provides the close button for the session selector to enable the user to refrain from saving. Users of gnome-session are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 2. Updating a model Red Hat Enterprise Linux AI allows you to upgrade LLMs that you locally downloaded to the latest version of the model. Table 2.1. RHEL AI version 1.3 LLM support Feature Description Version introduced NVIDIA AMD granite-7b-starter Granite student model for customizing and fine-tuning RHEL AI 1.1 Deprecated Deprecated granite-7b-redhat-lab Granite model for inference serving RHEL AI 1.1 Deprecated Deprecated granite-8b-starter Granite student model for customizing and fine-tuning RHEL AI 1.3 Generally available Technology preview granite-8b-redhat-lab Granite model for inference serving RHEL AI 1.3 Generally available Technology preview granite-8b-lab-v2-preview Preview of the version 2 8b Granite model for inference serving RHEL AI 1.3 Technology preview Technology preview 2.1. Updating the models You can upgrade your local models to the latest version of the model using the RHEL AI tool set. Prerequisites You installed the InstructLab tools with the bootable container image. You initialized InstructLab and can use the ilab CLI. You downloaded LLMs on Red Hat Enterprise Linux AI. You created a Red Hat registry account and logged in on your machine. Procedure You can upgrade any model by running the following command. USD ilab model download --repository <repository_and_model> --release latest where: <repository_and_model> Specifies the repository location of the model as well as the model. You can access the models from the registry.redhat.io/rhelai1/ repository. <release> Specifies the version of the model. Set to latest , or a specific version of the model, for the most up to date version of the model. Verification You can view all the downloaded models on your system with the following command: USD ilab model list

Commands:
ilab model download --repository <repository_and_model> --release latest
ilab model list