mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Updating Red Hat build of OpenJDK 11 on RHEL The following sections provide instructions for updating Red Hat build of OpenJDK 11 on RHEL. 4.1. Updating Red Hat build of OpenJDK 11 on RHEL by using yum The installed Red Hat build of OpenJDK packages can be updated by using the yum system package manager. Prerequisites You must have root privileges on the system. Procedure Check the current Red Hat build of OpenJDK version: A list of installed Red Hat build of OpenJDK packages displays. Update a specific package. For example: Verify that the update worked by checking the current Red Hat build of OpenJDK versions: Note If the output from the command shows that you have a different major version of Red Hat build of OpenJDK checked out on your system, you can enter the following command in your CLI to switch your system to use Red Hat build of OpenJDK 11: 4.2. Updating Red Hat build of OpenJDK 11 on RHEL by using an archive You can update Red Hat build of OpenJDK by using the archive. This is useful if the Red Hat build of OpenJDK administrator does not have root privileges. Prerequisites Know the generic path pointing to your JDK or JRE installation. For example, ~/jdks/java-11 Procedure Remove the existing symbolic link of the generic path to your JDK or JRE. For example: Install the latest version of the JDK or JRE in your installation location. Additional resources For instructions on installing a JRE, see Installing a JRE on RHEL by using an archive . For instructions on installing a JDK, see Installing Red Hat build of OpenJDK on RHEL by using an archive . Revised on 2024-05-09 16:48:57 UTC

Commands:
sudo yum list installed "java*"
Installed Packages java-1.8.0-openjdk.x86_64 1:1.8.0.322.b06-2.el8_5 @rhel-8-for-x86_64-appstream-rpms java-11-openjdk.x86_64 1:11.0.14.0.9-2.el8_5 @rhel-8-for-x86_64-appstream-rpms java-17-openjdk.x86_64 1:17.0.2.0.8-4.el8_5 @rhel-8-for-x86_64-appstream-rpms
sudo yum update java-11-openjdk
java -version openjdk version "11.0.14" 2022-01-18 LTS OpenJDK Runtime Environment 18.9 (build 11.0.14+9-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.14+9-LTS, mixed mode, sharing)
sudo update-alternatives --config 'java'
unlink ~/jdks/java-11
Chapter 15. Displaying resource constraints and resource dependencies There are a several commands you can use to display constraints that have been configured. You can display all configured resource constraints, or you can limit the display of esource constraints to specific types of resource constraints. Additionally, you can display configured resource dependencies. Displaying all configured constraints The following command lists all current location, order, and colocation constraints. If the --full option is specified, show the internal constraint IDs. By default, listing resource constraints does not display expired constraints. To include expired constaints in the listing, use the --all option of the pcs constraint command. This will list expired constraints, noting the constraints and their associated rules as (expired) in the display. Displaying location constraints The following command lists all current location constraints. If resources is specified, location constraints are displayed per resource. This is the default behavior. If nodes is specified, location constraints are displayed per node. If specific resources or nodes are specified, then only information about those resources or nodes is displayed. Displaying ordering constraints The following command lists all current ordering constraints. Displaying colocation constraints The following command lists all current colocation constraints. Displaying resource-specific constraints The following command lists the constraints that reference specific resources. Displaying resource dependencies The following command displays the relations between cluster resources in a tree structure. If the --full option is used, the command displays additional information, including the constraint IDs and the resource types. In the following example, there are 3 configured resources: C, D, and E. In the following example, there are 2 configured resources: A and B. Resources A and B are part of resource group G.

Commands:
pcs constraint [list|show] [--full]
pcs constraint location [show [resources [ resource ...]] | [nodes [ node ...]]] [--full]
pcs constraint order [show]
pcs constraint colocation [show]
pcs constraint ref resource
pcs resource relations resource [--full]
pcs constraint order start C then start D Adding C D (kind: Mandatory) (Options: first-action=start then-action=start) pcs constraint order start D then start E Adding D E (kind: Mandatory) (Options: first-action=start then-action=start) pcs resource relations C C `- order | start C then start D `- D `- order | start D then start E `- E pcs resource relations D D |- order | | start C then start D | `- C `- order | start D then start E `- E pcs resource relations E E `- order | start D then start E `- D `- order | start C then start D `- C
pcs resource relations A A `- outer resource `- G `- inner resource(s) | members: A B `- B pcs resource relations B B `- outer resource `- G `- inner resource(s) | members: A B `- A pcs resource relations G G `- inner resource(s) | members: A B |- A `- B
16.6. PAM and Administrative Credential Caching A variety of graphical administrative tools under Red Hat Enterprise Linux give users elevated privileges for up to five minutes via the pam_timestamp.so module. It is important to understand how this mechanism works because a user who walks away from a terminal while pam_timestamp.so is in effect leaves the machine open to manipulation by anyone with physical access to the console. Under the PAM timestamp scheme, the graphical administrative application prompts the user for the root password when it is launched. Once authenticated, the pam_timestamp.so module creates a timestamp file within the /var/run/sudo/ directory by default. If the timestamp file already exists, other graphical administrative programs do not prompt for a password. Instead, the pam_timestamp.so module freshens the timestamp file - reserving an extra five minutes of unchallenged administrative access for the user. The existence of the timestamp file is denoted by an authentication icon in the notification area of the panel. Below is an illustration of the authentication icon: Figure 16.1. The Authentication Icon 16.6.1. Removing the Timestamp File It is recommended that before walking away from a console where a PAM timestamp is active, the timestamp file be destroyed. To do this from within a graphical environment, click on the authentication icon on the panel. When a dialog box appears, click on the Forget Authorization button. Figure 16.2. Authentication Icon Dialog If logged into a system remotely using ssh , use the /sbin/pam_timestamp_check -k root command to destroy the timestamp file. Note You must be logged in as the user who originally invoked the pam_timestamp.so module in order to use the /sbin/pam_timestamp_check command. Do not log in as root to issue this command. For information about destroying the timestamp file using pam_timestamp_check , refer to the pam_timestamp_check man page.

Commands:
5.3. Boot Logging The boot log is the record of events that occur while the server is starting up (or booting). Red Hat JBoss Data Grid also includes a server log, which includes log entries generated after the server concludes the boot process. Report a bug 5.3.1. Configure Boot Logging Edit the logging.properties file to configure the boot log. This file is a standard Java properties file and can be edited in a text editor. Each line in the file has the format of property=value . In Red Hat JBoss Data Grid, the logging.properties file is available in the USDJDG_HOME/standalone/configuration folder. Report a bug 5.3.2. Default Log File Locations The following table provides a list of log files in Red Hat JBoss Data Grid and their locations: Table 5.1. Default Log File Locations Log File Location Description boot.log USDJDG_HOME/standalone/log/ The Server Boot Log. Contains log messages related to the start up of the server. server.log USDJDG_HOME/standalone/log/ The Server Log. Contains all log messages once the server has launched. Report a bug

Commands:
Chapter 9. Deploying with Key Manager If you have deployed edge sites to the release of Red Hat OpenStack Platform 16.1.2, you will need to regenerate roles.yaml to implement this feature: To implement the feature, regenerate the roles.yaml file used for the DCN site's deployment. 9.1. Deploying edge sites with Key Manager If you want to include access to the Key Manager (barbican) service at edge sites, you must configure barbican at the central location. For information on installing and configuring barbican, see Deploying Barbican . You can configure access to barbican from DCN sites by including the /usr/share/openstack-tripleo-heat-templates/environments/services/barbican-edge.yaml .

Commands:
openstack overcloud roles generate DistributedComputeHCI DistributedComputeHCIScaleOut -o ~/dcn0/roles_data.yaml
openstack overcloud deploy --stack dcn0 --templates /usr/share/openstack-tripleo-heat-templates/ -r ~/dcn0/roles_data.yaml . -e /usr/share/openstack-tripleo-heat-templates/environments/services/barbican-edge.yaml
Chapter 6. 7 March 2024 This release includes several enhancements, additions, and fixes that have been implemented in Red Hat Ansible Lightspeed. 6.1. New features and enhancements Ansible code bot General Availability Previously, Red Hat Ansible Lightspeed provided the Ansible code bot as a Technology Preview release. Now, the Ansible code bot is available as General Availability release along with an improved performance and an Ansible code bot dashboard. The dashboard displays a list of your repositories where the code bot is installed, the status of your repository scans, and indicates whether the scan schedule is not set, or is set to manual or scheduled scan. From the dashboard, you can start a manual scan, view the scan history, and view the repository. For more information, see Installing and configuring the Ansible code bot . Ability to collect and manage the Admin dashboard telemetry Red Hat Ansible Lightspeed now collects Admin dashboard telemetry data that provides insight into how your organization users are using the Ansible Lightspeed service, and displays the metrics on the Admin dashboard. If you no longer want to collect and manage the Admin dashboard telemetry, you can disable it for your organization. For more information, see Viewing and managing Admin dashboard telemetry .

Commands:
Chapter 1. Introducing the GNOME 3 Desktop 1.1. What Is GNOME 3? In Red Hat Enterprise Linux 7, GNOME 3 is the default desktop environment. It is the major version of the GNOME Desktop, which introduces a new user interface and substantial feature improvements over the GNOME 2 Desktop shipped with Red Hat Enterprise Linux 5 and 6. Figure 1.1. The GNOME 3 Desktop (GNOME Classic) GNOME 3 provides a focused working environment that encourages productivity. A powerful search feature lets you access all your work from one place. For example, you can turn off notifications when you need to concentrate on the task in hand. Important To function properly, GNOME requires your system to support 3D acceleration . This includes bare metal systems, as well as hypervisor solutions such as VMWare . If GNOME does not start or performs poorly on your VMWare virtual machine (VM), see the following solution: Why does the GUI fail to start on my VMware virtual machine? . For more information, see Section 1.2.1, "Hardware Acceleration and Software Rendering" . GNOME 3 is built on a number of powerful components: GNOME Shell GNOME Shell is a modern and intuitive graphical user interface. It provides quality user experience, including visual effects and hardware acceleration support. GNOME Classic GNOME Classic combines old and new; it keeps the familiar look and feel of GNOME 2, but adds the powerful new features and 3-D capabilities of GNOME Shell. GNOME Classic is the default GNOME session and GNOME Shell mode in Red Hat Enterprise Linux 7. GSettings GSettings is a configuration storage system, replacing GConf found in older GNOME versions. For more information about the transition from GConf to GSettings , see Chapter 3, GSettings and dconf . To learn more about configuring your desktop with GSettings , read Chapter 9, Configuring Desktop with GSettings and dconf . GVFS GVFS provides complete virtual file system infrastructure and handles storage in the GNOME Desktop in general. Through GVFS , GNOME 3 integrates well with online document-storage services, calendars, and contact lists, so all your data can be accessed from the same place. Read more about GVFS in Chapter 15, Virtual File Systems and Disk Management . GTK+ GTK+ , a multi-platform toolkit for creating graphical user interfaces, provides a highly-usable feature-rich API. Thanks to GTK+ , GNOME 3 is able to change the look of an application or provide smooth appearance of graphics. In addition, GTK+ contains a number of features such as object-oriented programming support (GObject), wide support of international character sets and text layouts (Pango), or a set of accessibility interfaces (ATK).

Commands:
Chapter 5. dev 5.1. dev:dump-create 5.1.1. Description Creates zip archive with diagnostic info. 5.1.2. Syntax dev:dump-create [options] [name] 5.1.3. Arguments Name Description name Name of created zip or directory 5.1.4. Options Name Description --help Display this help message --no-heap-dump Include or not the heap dump in ZIP archive --no-thread-dump Include or not the thread dump in ZIP archive -d, --directory Creates dump in a directory in place of a ZIP archive

Commands:
20.15. Displaying the IP Address and Port Number for the VNC Display The virsh vncdisplay command returns the IP address and port number of the VNC display for the specified guest virtual machine. If the information is unavailable for the guest, the exit code 1 is displayed. Note that for this command to work, VNC has to be specified as a graphics type in the devices element of the guest's XML file. For further information, see Section 23.17.11, "Graphical Framebuffers" . Example 20.37. How to display the IP address and port number for VNC The following example displays the port number for the VNC display of the guest1 virtual machine:

Commands:
virsh vncdisplay guest1 127.0.0.1:0
2.4.2. File Names and Blocklists When typing commands to GRUB that reference a file, such as a menu list, it is necessary to specify an absolute file path immediately after the device and partition numbers. The following illustrates the structure of such a command: ( <device-type><device-number> , <partition-number> ) </path/to/file> In this example, replace <device-type> with hd , fd , or nd . Replace <device-number> with the integer for the device. Replace </path/to/file> with an absolute path relative to the top-level of the device. It is also possible to specify files to GRUB that do not actually appear in the file system, such as a chain loader that appears in the first few blocks of a partition. To load such files, provide a blocklist that specifies block by block where the file is located in the partition. Since a file is often comprised of several different sets of blocks, blocklists use a special syntax. Each block containing the file is specified by an offset number of blocks, followed by the number of blocks from that offset point. Block offsets are listed sequentially in a comma-delimited list. The following is a sample blocklist: This sample blocklist specifies a file that starts at the first block on the partition and uses blocks 0 through 49, 100 through 124, and 200. Knowing how to write blocklists is useful when using GRUB to load operating systems which require chain loading. It is possible to leave off the offset number of blocks if starting at block 0. As an example, the chain loading file in the first partition of the first hard drive would have the following name: The following shows the chainloader command with a similar blocklist designation at the GRUB command line after setting the correct device and partition as root:

Commands:
0+50,100+25,200+1
(hd0,0)+1
chainloader +1
Chapter 53. Desktop Closing laptop lid breaks the GNOME multi-display configuration When using a laptop with the GNOME graphical environment that is connected to one or more external displays, closing the lid to suspend the laptop sometimes causes windows and icons to be moved between displays and the display layout to be reset when the system is resumed. To work around this problem, open the GNOME Displays interface, which causes the display configuration to be reloaded. (BZ#1360906) Limited support for visuals in Xorg In the Xorg server, only TrueColor and DirectColor visuals at depth 16 or higher are supported for hardware drivers. Legacy applications that need a PseudoColor visual can be run against the Xephyr nested X server, which implements PseudoColor translation when displayed on a TrueColor screen. (BZ#1185690)

Commands:
Chapter 1. Overview of OpenShift AI Red Hat OpenShift AI is a platform for data scientists and developers of artificial intelligence and machine learning (AI/ML) applications. OpenShift AI provides an environment to develop, train, serve, test, and monitor AI/ML models and applications on-premise or in the cloud. For data scientists, OpenShift AI includes Jupyter and a collection of default notebook images optimized with the tools and libraries required for model development, and the TensorFlow and PyTorch frameworks. Deploy and host your models, integrate models into external applications, and export models to host them in any hybrid cloud environment. You can enhance your data science projects on OpenShift AI by building portable machine learning (ML) workflows with data science pipelines, using Docker containers. You can also accelerate your data science experiments through the use of graphics processing units (GPUs) and Intel Gaudi AI accelerators. For administrators, OpenShift AI enables data science workloads in an existing Red Hat OpenShift or ROSA environment. Manage users with your existing OpenShift identity provider, and manage the resources available to notebook servers to ensure data scientists have what they require to create, train, and host models. Use accelerators to reduce costs and allow your data scientists to enhance the performance of their end-to-end data science workflows using graphics processing units (GPUs) and Intel Gaudi AI accelerators. OpenShift AI has two deployment options: Self-managed software that you can install on-premise or in the cloud. You can install OpenShift AI Self-Managed in a self-managed environment such as OpenShift Container Platform, or in Red Hat-managed cloud environments such as Red Hat OpenShift Dedicated (with a Customer Cloud Subscription for AWS or GCP), Red Hat OpenShift Service on Amazon Web Services (ROSA Classic or ROSA HCP), or Microsoft Azure Red Hat OpenShift. For information about OpenShift AI as self-managed software on your OpenShift cluster in a connected or a disconnected environment, see Product Documentation for Red Hat OpenShift AI Self-Managed . A managed cloud service , installed as an add-on in Red Hat OpenShift Dedicated (with a Customer Cloud Subscription for AWS or GCP) or in Red Hat OpenShift Service on Amazon Web Services (ROSA Classic). For information about OpenShift AI supported software platforms, components, and dependencies, see the Red Hat OpenShift AI: Supported Configurations Knowledgebase article. For a detailed view of the release lifecycle, including the full support phase window, see the Red Hat OpenShift AI Cloud Service Life Cycle Knowledgebase article.

Commands:
B.10.6. RHBA-2011:0854 - corosync bug fix update Updated corosync packages that fix several bugs are now available for Red Hat Enterprise Linux 6 Extended Update Support. The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software. Bug Fixes BZ# 696735 When the corosync server terminated unexpectedly, if it was connected to corosync clients, a shared memory leak occurred. This bug has been fixed and no memory leaks occur in the described scenario. BZ# 696734 When a ring ID file was smaller than 8 bytes, the corosync server terminated unexpectedly. With this update, if no proper ring ID file can be loaded, the corosync server creates one and no crash will occur. BZ# 696733 During the recovery phase, the corosync server sometimes terminated unexpectedly. As a consequence, a network token was lost and new configuration had to be created. This bug has been fixed and the corosync server no longer crashes in the described scenario. BZ# 696732 In rare circumstances involving multiple running nodes, the corosync server terminated unexpectedly during shut down. This bug has been fixed and the corosync server no longer crashes. BZ# 681258 When inconsistent cluster.conf files with different versions were used among nodes, a memory leak occurred in the corosync server during the configuration reload. This bug has been fixed and the configuration reload via the cman_tool no longer causes memory leaks. All users of corosync are advised to upgrade to these updated packages, which fix these bugs.

Commands:
2.2. For the More Experienced If you have used other Linux distributions, you probably already have a basic grasp of the most frequently used commands. You may have installed your own Linux system, and maybe you have even downloaded and built software you found on the Internet. After installing Linux, however, configuration issues can be very confusing. The System Administrators Guide is designed to help explain the various ways a Red Hat Enterprise Linux system can be configured to meet specific objectives. Use this manual to learn about specific configuration options and how to put them into effect. When you are installing software that is not covered in the System Administrators Guide , it is often helpful to see what other people in similar circumstances have done. HOWTO documents from the Linux Documentation Project, available at http://www.redhat.com/mirrors/LDP/HOWTO/HOWTO-INDEX/howtos.html , document particular aspects of Linux, from low-level kernel esoteric changes to using Linux for amateur radio station work. If you are concerned with the finer points and specifics of the Red Hat Enterprise Linux system, the Reference Guide is a great resource. If you are concerned about security issues, the Security Guide is a great resource - explaining in concise terms best strategies and practices for securing Red Hat Enterprise Linux.

Commands:
4.117. kdepim-runtime 4.117.1. RHBA-2011:1094 - kdepim-runtime bug fix update Updated kdepim-runtime packages that fix two bugs are now available for Red Hat Enterprise Linux 6. KDE is a graphical desktop environment for the X Window System. The kdepim-runtime package contain the KDE PIM Runtime Environment. Bug Fixes BZ# 660581 Prior to this update, it was not possible to build the kdepim-runtime package on Red Hat Enterprise Linux 6. This problem has been resolved in this update and no longer occurs. BZ# 625121 Prior to this update, Akonaditray, which is an application included in KDE, was incorrectly displayed in the GNOME Applications menu. This bug has been fixed in this update so that Akonaditray is no longer displayed in the aforementioned menu. All users of kdepim-runtime are advised to upgrade to these updated packages, which fix these bugs.

Commands: