mtpti5iD/redhat-docs_dataset huggingface dataset:
Part I. About simple content access Simple content access provides a subscription experience that removes many of the time-consuming and complex business processes associated with the classic Red Hat entitlement-based enforcement model. The simple content access tool is intended to simplify content access (consumption of technology, including product and service offerings) and streamline the workflow associated with adding, removing, and renewing subscriptions. Learn more To learn more about simple content access, see the following information: What is simple content access? To learn more about the benefits and limitations of simple content access, see the following information: What are the benefits and limitations of simple content access? To learn more about how enabling simple content access creates significant operational changes for subscription management, see the following information: How does simple content access change subscription tools and workflows?

Commands:
Chapter 6. Automation Platform Operator {OperatorPlatform} provides cloud-native, push-button deployment of new Ansible Automation Platform instances in your OpenShift environment. Bug fixes Enabled configuration of resource requirements for automation controller init containers. Added securityContext for Event-Driven Ansible Operator deployments to be Pod Security Admission compliant. Resolved error Controller: Error 413 Entity too large when doing bulk updates. Ansible token is now obfuscated in YAML job details.

Commands:
15.17. Moving the Replication Changelog Directory In certain situations, you might want to change the Directory Server replication changelog directory. For example, to change the directory to /var/lib/dirsrv/slapd- instance_name /new_changelogdb/ : Display the current path to the changelog and set the new path: Using the command line: Display the current directory: You need the displayed path in a later step to move the directory. Set the new path: Using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Open the Replication menu, and select the Replication Changelog entry. Click Show Advanced Settings . Identify the current path in the Changelog Location field. You need the displayed path in a later step to move the directory. Set the new path in the Changelog Location field. Click Save . Stop the Directory Server instance: Move the content of the directory to /var/lib/dirsrv/slapd- instance_name /new_changelogdb/ : Delete the directory: Start the Directory Server instance:

Commands:
ldapsearch -D "cn=Directory Manager" -W -p 389 -h server.example.com -x -b "cn=changelog5,cn=config" nsslapd-changelogdir nsslapd-changelogdir: /var/lib/dirsrv/slapd- instance_name /changelogdb/
ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: cn=changelog5,cn=config changetype: modify replace: nsslapd-changelogdir nsslapd-changelogdir: /var/lib/dirsrv/slapd- instance_name /new_changelogdb/
dsctl instance_name stop
mv /var/lib/dirsrv/slapd- instance_name /changelogdb/ /var/lib/dirsrv/slapd- instance_name /new_changelogdb/
rm /var/lib/dirsrv/slapd- instance_name /changelogdb/
dsctl instance_name start
Chapter 3. Installing and configuring ReaR Before you back up the undercloud and the overcloud control plane nodes, you must first install and configure Relax and Recover (ReaR) on the undercloud and on each control plane node. 3.1. Installing the required packages You must install the Relax and Recover (ReaR) packages and packages for generating ISO images on the undercloud node and on each control plane node. Procedure Install the required packages on the undercloud and on each control plane node. For example: Create a backup directory on the undercloud and on each control plane node. For example: Mount the ctl_plane_backups NFS directory from the backup node running NFS on the undercloud and on each control plane node. For example: Replace <ip-addr> with the IP address of the backup node running the NFS server. 3.2. Creating the configuration files As the root user on the undercloud and on each control plane node, perform the following steps: Create the ReaR configuration file: Replace <SERVER_NAME-X> with the hostname of the node. For example, if the node hostname is controller-0 , replace <SERVER_NAME-X> with controller-0 . Replace <ip-addr> with the IP address of the backup node running the NFS server configured in Chapter 2, Preparing the backup node . Important If the undercloud or control plane nodes use UEFI as their boot mode, you must add USING_UEFI_BOOTLOADER=1 to the configuration file too. Create the rescue.conf file:

Commands:
dnf install rear genisoimage nfs-utils -y
mkdir -p /ctl_plane_backups
mount -t nfs <ip-addr>:/ctl_plane_backups /ctl_plane_backups
mkdir -p /etc/rear tee -a "/etc/rear/local.conf" > /dev/null <<'EOF' OUTPUT=ISO OUTPUT_URL=nfs://<ip-addr>/ctl_plane_backups ISO_PREFIX=<SERVER_NAME-X> BACKUP=NETFS BACKUP_PROG_COMPRESS_OPTIONS=( --gzip ) BACKUP_PROG_COMPRESS_SUFFIX=".gz" BACKUP_PROG_EXCLUDE=( '/tmp/*' '/data/*' ) BACKUP_URL=nfs://<ip-addr>/ctl_plane_backups BACKUP_PROG_EXCLUDE=("USD{BACKUP_PROG_EXCLUDE[@]}" '/media' '/var/tmp' '/var/crash') BACKUP_PROG_OPTIONS+=( --anchored --xattrs-include='*.*' --xattrs ) EOF
tee -a "/etc/rear/rescue.conf" > /dev/null <<'EOF' BACKUP_PROG_OPTIONS+=( --anchored --xattrs-include='*.*' --xattrs ) EOF
2.2. Library and Runtime Details 2.2.1. The GNU C++ Standard Library The libstdc++ package contains the GNU C++ Standard Library , which is an ongoing project to implement the ISO 14882 Standard C++ library. Installing the libstdc++ package will provide just enough to satisfy link dependencies (that is, only shared library files). To make full use of all available libraries and header files for C++ development, you must install libstdc++-devel as well. The libstdc++-devel package also contains a GNU-specific implementation of the Standard Template Library (STL). For Red Hat Enterprise Linux 4, 5, and 6, the C++ language and runtime implementation has remained stable, and thus no compatibility libraries are required for libstdc++ . 2.2.1.1. Additional information To use the man pages for library components, install the libstdc++-docs package. This will provide man page information for nearly all resources provided by the library; for example, to view information about the vector container, use its fully-qualified component name: man std::vector . The libstdc++-docs package also provides manuals and reference information in HTML form in the following directory: /usr/share/doc/libstdc++-docs- version /html/spine.html .

Commands:
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 8 release of Eclipse Temurin includes, see OpenJDK 8u372 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements included with the Eclipse Temurin 8.0.372 release: Detection of control group (cgroup) v2 host systems in Linux containers The OpenJDK 8.0.372 release includes an update to the HotSpot runtime code and the core libraries code in the JDK. This update enables the detection of cgroup v2 host systems when running OpenJDK within a Linux container. Previously, from the OpenJDK release 8u202 onward, the container detection code recognized cgroup v1 (legacy) host Linux systems only. Now, from OpenJDK 8.0.372 onward, OpenJDK detects both versions of the underlying cgroups pseudo file-system and applies corresponding container limits to the OpenJDK runtime. Without this enhancement, when running on a cgroup v2 Linux host system, OpenJDK would have used the underlying hosts' resource limits instead of applying container resource limits. See JDK-8305562 (JDK Bug System) . Configuration of third port for remote Java Management Extensions (JMX) In release OpenJDK 8.0.372, you can configure a local access port for remote JMX connections by setting the com.sun.management.jmxremote.local.port property. In releases, OpenJDK selected this local port at random, which could lead to port collisions. The com.sun.management.jmxremote.local.port property works in the same way as the existing properties for configuring the remote access port ( com.sun.management.jmxremote.port ) and the Remote Method Invocation (RMI) port ( com.sun.management.jmxremote.rmi.port ). See JDK-8234484 (JDK Bug System) . Certigna (Dhimyotis) root certificate authority (CA) certificate added In release OpenJDK 8.0.372, the cacerts truststore includes the Certigna (Dhimyotis) root certificate: Name: Certigna (Dhimyotis) Alias name: certignarootca Distinguished name: CN=Certigna, O=Dhimyotis, C=FR See JDK-8245654 (JDK Bug System) . Enhanced Swing platform support In earlier releases of OpenJDK, HTML object tags rendered embedded in Swing HTML components. With release OpenJDK 8.0.372, rendering only occurs if you set the new system property swing.html.object to true. By default, the swing.html.object property is set to false. JDK bug system reference ID: JDK-8296832. Revised on 2024-05-10 09:07:16 UTC

Commands:
4.3. Clustering and High Availability pcs The pcs package has been added to Red Hat Enterprise Linux 6 as a Technology Preview. This package provides a command-line tool configure and manage the corosync and pacemaker utilities. Package: pcs-0.9.26-10 luci support for fence_sanlock The luci tool now supports the Sanlock fence agent as a Technology Preview, which is available in the luci's list of agents. Package: luci-0.26.0-37 Recovering a node via a hardware watchdog device New fence_sanlock agent and checkquorum.wdmd, included in Red Hat Enterprise Linux 6.4 as a Technology Preview, provide new mechanisms to trigger the recovery of a node via a hardware watchdog device. Tutorials on how to enable this Technology Preview will be available at https://fedorahosted.org/cluster/wiki/HomePage Note that SELinux in enforcing mode is currently not supported. Package: cluster-3.0.12.1-49 keepalived Red Hat Enterprise Linux 6.4 includes the keepalived package as a Technology Preview. The keepalived package provides simple and robust facilities for load-balancing and high-availability. The load-balancing framework relies on the well-know and widely used Linux Virtual Server kernel module providing Layer4 network load-balancing. The keepalived daemon implements a set of health checkers to load-balanced server pools according to their state. The keepalived daemon also implements the Virtual Router Redundancy Protocol (VRRP), allowing router or director failover to achieve high availability. Package: keepalived-1.2.7-3 HAProxy HAProxy is a stand-alone, layer-7, high-performance network load balancer for TCP and HTTP-based applications which can perform various types of scheduling based on the content of the HTTP requests. Red Hat Enterprise Linux 6.4 introduces the haproxy package as a Technology Preview. Package: haproxy-1.4.22-3 libqb package The libqb package provides a library with the primary purpose of providing high performance client server reusable features, such as high performance logging, tracing, inter-process communication, and polling. This package is introduced as a dependency of the pacemaker package, and is considered a Technology Preview. Package: libqb-0.14.2-3 pacemaker, BZ# 456895 Pacemaker, a scalable high-availability cluster resource manager, is included in Red Hat Enterprise Linux 6 as a Technology Preview. Pacemaker is not fully integrated with the Red Hat cluster stack. Package: pacemaker-1.1.8-7

Commands:
Chapter 26. Extending a Stratis volume with additional block devices You can attach additional block devices to a Stratis pool to provide more storage capacity for Stratis file systems. You can do it manually or by using the web console. 26.1. Adding block devices to a Stratis pool You can add one or more block devices to a Stratis pool. Prerequisites Stratis is installed. See Installing Stratis . The stratisd service is running. The block devices that you are adding to the Stratis pool are not in use and not mounted. The block devices that you are adding to the Stratis pool are at least 1 GiB in size each. Procedure To add one or more block devices to the pool, use: Additional resources stratis(8) man page on your system 26.2. Adding a block device to a Stratis pool by using the web console You can use the web console to add a block device to an existing Stratis pool. You can also add caches as a block device. Prerequisites You have installed the RHEL 9 web console. You have enabled the cockpit service. Your user account is allowed to log in to the web console. For instructions, see Installing and enabling the web console . The stratisd service is running. A Stratis pool is created. The block devices on which you are creating a Stratis pool are not in use and are not mounted. Each block device on which you are creating a Stratis pool is at least 1 GB. Procedure Log in to the RHEL 9 web console. For details, see Logging in to the web console . Click Storage . In the Storage table, click the Stratis pool to which you want to add a block device. On the Stratis pool page, click Add block devices and select the Tier where you want to add a block device as data or cache. If you are adding the block device to a Stratis pool that is encrypted with a passphrase, enter the passphrase. Under Block devices , select the devices you want to add to the pool. Click Add .

Commands:
stratis pool add-data my-pool device-1 device-2 device-n
22.3. Specifying Module Parameters In some situations, it may be necessary to supply parameters to a module as it is loaded for it to function properly. For instance, to enable full duplex at 100Mbps connection speed for an Intel Ether Express/100 card, load the e100 driver with the e100_speed_duplex=4 option. Warning When a parameter has commas, be sure not to put a space after a comma. Note The modinfo command is also useful for listing various information about a kernel module, such as version, dependencies, paramater options, and aliases.

Commands:
Chapter 6. Starting to use Red Hat Quay With Red Hat Quay now running, you can: Select Tutorial from the Quay home page to try the 15-minute tutorial. In the tutorial, you learn to log into Quay, start a container, create images, push repositories, view repositories, and change repository permissions with Quay. Refer to the Use Red Hat Quay for information on working with Red Hat Quay repositories.

Commands:
Chapter 4. August 2024 4.1. Major updates to Azure integrations Based on customer feedback, the instructions for how to create an integration with Microsoft Azure were updated. The new version of the documentation reflects the latest changes to the Azure UI and aims to resolve customer pain points by being more clear and easy to follow. There are two options when you create an integration: a basic path where you use unfiltered data, and an advanced path with filtered data. The instructions for both sections are updated. To learn more about Azure and explore the new updates, go to Integrating Microsoft Azure data into cost management . 4.2. Attribute the cost of node attached storage to OpenShift Projects Unattributed Storage is a type of project that gets created when cost management is unable to correlate a portion of the cloud cost to an OpenShift namespace. There are two scenarios where Unattributed Storage can happen: Volumes without a claim A persistent volume (PV) exists, but there are no persistent volume claims (PVCs) that use the volume. Without a claim, the cloud cost cannot be associated with a node or namespace. Unutilized disk space In some situations, cost management creates its own project because it cannot determine which project should be charged with the money from Azure. To learn more about how to calculate Unattributed Storage in Azure, see Unattributed Storage project .

Commands:
7.6. Managed Resources You can set a resource to unmanaged mode, which indicates that the resource is still in the configuration but Pacemaker does not manage the resource. The following command sets the indicated resources to unmanaged mode. The following command sets resources to managed mode, which is the default state. You can specify the name of a resource group with the pcs resource manage or pcs resource unmanage command. The command will act on all of the resources in the group, so that you can manage or unmanage all of the resource in a group with a single command and then manage the contained resources individually.

Commands:
pcs resource unmanage resource1 [ resource2 ]
pcs resource manage resource1 [ resource2 ]
10.4.2. Gathering Post-Breach Information The topic of digital forensics and analysis itself is quite broad, yet the tools are mostly architecture specific and cannot be applied generically. However, incident response, analysis, and recovery are important topics. With proper knowledge and experience, Red Hat Enterprise Linux can be an excellent platform for performing these types of analysis, as it includes several utilities for performing post-breach response and restoration. Table 10.1, "File Auditing Tools" details some commands for file auditing and management. It also lists some examples that can be used to properly identify files and file attributes (such as permissions and access dates) to allow the collection of further evidence or items for analysis. These tools, when combined with intrusion detection systems, firewalls, hardened services, and other security measures, can help reduce the amount of potential damage when an attack occurs. Note For detailed information about each tool, refer to their respective man pages. Table 10.1. File Auditing Tools Command Function Example dd Creates a bit-image copy (or disk dump ) of files and partitions. Combined with a check of the md5sums of each image, administrators can compare a pre-breach image of a partition or file with a breached system to see if the sums match. dd if=/bin/ls of=ls.dd |md5sum ls.dd >ls-sum.txt grep Finds useful string (text) information inside files and directories as well as reveals permissions, script changes, file attributes, and more. Used mostly as a piped command of for commands like ls , ps , or ifconfig . ps auxw |grep /bin strings Prints the strings of printable characters within a file. It is most useful for auditing executables for anomalies such as mail commands to unknown addresses or logging to a non-standard log file. strings /bin/ps |grep 'mail' file Determines the characteristics of files based on format, encoding, linked-libraries (if any), and file type (binary, text, and more). It is useful for determining whether an executable such as /bin/ls has been modified using static libraries, which is a sure sign that the executable has been replaced with one installed by a malicious user. file /bin/ls find Searches directories for particular files. It is a useful tool for searching the directory structure by keyword, date and time of access, permissions, and more. It can also be useful for administrators that perform general system audits of particular directories or files. find -atime +12 -name *log* -perm u+rw stat Displays file status information, including time last accessed, permissions, UID and GID bit settings, and more. It can be useful for checking when a breached system executable was last used or modified. stat /bin/netstat md5sum Calculates the 128-bit checksum using the md5 hash algorithm. Use this command to create a text file that lists all crucial executables that are often modified or replaced in a security compromise. Redirect the sums to a file to create a simple database of checksums and then copy the file onto a read-only medium such as CD-ROM. md5sum /usr/bin/gdm >>md5sum.txt

Commands:
20.24. Displaying CPU Statistics for a Specified Guest Virtual Machine The virsh cpu-stats domain --total start count command provides the CPU statistical information on the specified guest virtual machine. By default, it shows the statistics for all CPUs, as well as a total. The --total option will only display the total statistics. The --count option will only display statistics for count CPUs. Example 20.51. How to generate CPU statistics for the guest virtual machine The following example generates CPU statistics for the guest virtual machine named guest1 .

Commands:
virsh cpu-stats guest1 CPU0: cpu_time 242.054322158 seconds vcpu_time 110.969228362 seconds CPU1: cpu_time 170.450478364 seconds vcpu_time 106.889510980 seconds CPU2: cpu_time 332.899774780 seconds vcpu_time 192.059921774 seconds CPU3: cpu_time 163.451025019 seconds vcpu_time 88.008556137 seconds Total: cpu_time 908.855600321 seconds user_time 22.110000000 seconds system_time 35.830000000 seconds
Chapter 39. Configuring Maven using settings.xml file Java application development uses the Apache Maven build automation tool to build and manage software projects. Maven uses Project Object Model (POM) configuration XML files to define both, the project properties and the build process. Maven uses repositories to store Java libraries, plug-ins, and other build artifacts. Repositories can be either local or remote. A local repository is a download of artifacts from a remote repository cached on a local machine. A remote repository is any other repository accessed using common protocols, such as http:// when located on an HTTP server, or file:// when located on a file server. The default repository is the public remote Maven 2 Central Repository. Configuration of Maven is performed by modifying the settings.xml file. You can either configure global Maven settings in the M2_HOME/conf/settings.xml file, or user-level settings in the USER_HOME/.m2/settings.xml file. Additional resources Configuring an external Maven repository for Business Central and KIE Server Packaging and deploying a Red Hat Process Automation Manager project in Maven Maven settings and repositories for Red Hat Process Automation Manager System integration with Maven Welcome to Apache Maven Apache Maven Project - Introduction to Repositories Apache Maven Parent POMs Reference .

Commands: