mtpti5iD/redhat-docs_dataset huggingface dataset:
1.2. Logical Volumes Volume management creates a layer of abstraction over physical storage, allowing you to create logical storage volumes. This provides much greater flexibility in a number of ways than using physical storage directly. With a logical volume, you are not restricted to physical disk sizes. In addition, the hardware storage configuration is hidden from the software so it can be resized and moved without stopping applications or unmounting file systems. This can reduce operational costs. Logical volumes provide the following advantages over using physical storage directly: Flexible capacity When using logical volumes, file systems can extend across multiple disks, since you can aggregate disks and partitions into a single logical volume. Resizeable storage pools You can extend logical volumes or reduce logical volumes in size with simple software commands, without reformatting and repartitioning the underlying disk devices. Online data relocation To deploy newer, faster, or more resilient storage subsystems, you can move data while your system is active. Data can be rearranged on disks while the disks are in use. For example, you can empty a hot-swappable disk before removing it. Convenient device naming Logical storage volumes can be managed in user-defined and custom named groups. Disk striping You can create a logical volume that stripes data across two or more disks. This can dramatically increase throughput. Mirroring volumes Logical volumes provide a convenient way to configure a mirror for your data. Volume Snapshots Using logical volumes, you can take device snapshots for consistent backups or to test the effect of changes without affecting the real data. The implementation of these features in LVM is described in the remainder of this document.

Commands:
9.7. Setting the Highest TLS Encryption Protocol Version To set the highest TLS protocol version Directory Server supports, enter: If you set the parameter to a value lower than in sslVersionMin , then Directory Server sets sslVersionMax to the same value as sslVersionMin . Important To always use the strongest supported encryption protocol version in the sslVersionMax parameter, do not set this parameter.

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com security set --tls-protocol-max=" protocol_version "
Chapter 8. Hardware Enablement Support of Future Intel SOC Processors Device support is enabled in the operating system for future Intel System-on-Chip (SOC) processors. These include Dual Atom processors, memory controller, SATA, Universal Asynchronous Receiver/Transmitter, System Management Bus (SMBUS), USB and Intel Legacy Block (ILB - lpc, timers, SMBUS (i2c_801 module)). Support of 12Gbps LSI SAS Devices The mpt3sas driver adds support for 12Gbps SAS devices from LSI in Red Hat Enterprise Linux. Support of Dynamic Hardware Partitioning and System Board Slot Recognition The dynamic hardware partitioning and system board slot recognition features alert high-level system middleware or applications for reconfiguration and allow users to grow the system to support additional workloads without reboot. Support for future Intel 2D and 3D Graphics Support for future Intel 2D and 3D graphics has been added to allow systems using future Intel processors to be certified through the Red Hat Hardware Certification program. Frequency Sensitivity Feedback Monitor Frequency sensitivity feedback monitor provides the operating system with better information so that it can make better frequency change decisions while saving power. ECC Memory Support The Error-correcting code (ECC) memory has been enabled for a future generation of AMD processors. This feature provides the ability to check for performance and errors by accessing ECC memory related counters and status bits. Support for AMD Systems with More Than 1TB Memory The kernel now supports memory configurations with more than 1TB of RAM on AMD systems.

Commands:
Chapter 1. Introduction to Red Hat JBoss Data Grid 6.6.2 Welcome to Red Hat JBoss Data Grid 6.6.2. As you become familiar with the newest version of JBoss Data Grid these Release Notes provide you with information about new features, as well as known and resolved issues. Use this document in conjunction with the entire JBoss Data Grid documentation suite, available at the Red Hat Customer Service Portal's JBoss Data Grid documentation page . Report a bug 1.1. About Red Hat JBoss Data Grid Red Hat's JBoss Data Grid is an open source, distributed, in-memory key/value data store built from the Infinispan open source software project. Whether deployed in client/server mode or embedded in a Java Virtual Machine, it is built to be elastic, high performance, highly available and to scale linearly. JBoss Data Grid is accessible for both Java and Non-Java clients. Using JBoss Data Grid, data is distributed and replicated across a manageable cluster of nodes, optionally written to disk and easily accessible using the REST, Memcached and Hot Rod protocols, or directly in process through a traditional Java Map API. Report a bug

Commands:
Chapter 6. Deleting OpenShift Serverless custom resource definitions After uninstalling the OpenShift Serverless, the Operator and API custom resource definitions (CRDs) remain on the cluster. You can use the following procedure to remove the remaining CRDs. Important Removing the Operator and API CRDs also removes all resources that were defined by using them, including Knative services. 6.1. Removing OpenShift Serverless Operator and API CRDs Delete the Operator and API CRDs using the following procedure. Prerequisites Install the OpenShift CLI ( oc ). You have cluster administrator permissions on OpenShift Container Platform, or you have cluster or dedicated administrator permissions on Red Hat OpenShift Service on AWS or OpenShift Dedicated. You have uninstalled Knative Serving and removed the OpenShift Serverless Operator. Procedure To delete the remaining OpenShift Serverless CRDs, enter the following command: USD oc get crd -oname | grep 'knative.dev' | xargs oc delete

Commands:
oc get crd -oname | grep 'knative.dev' | xargs oc delete
2.8. RHEA-2011:0658 - new package: icedtea-web New icedtea-web packages are now available for Red Hat Enterprise Linux 6. The IcedTea-Web project provides a Java web browser plug-in and an implementation of Java Web Start, which is based on the NetX project. It also contains a preview version of a configuration tool for managing deployment settings for the plug-in and Web Start implementations. This enhancement update adds the icedtea-web packages to Red Hat Enterprise Linux 6. (BZ# 664063 ) All users who require icedtea-web are advised to install these new packages.

Commands:
Appendix A. Revision History Revision History Revision 3.3-5 Wed Dec 20 2023 Lenka Spackova Fixed broken links and anchors. Revision 3.3-4 Fri Nov 12 2021 Lenka Spackova Updated Section 4.7, "Database Connectors" . Revision 3.3-3 Tue Mar 17 2020 Lenka Spackova Added a reference to container-specific upgrading instructions for PostgreSQL . Revision 3.3-2 Fri Nov 15 11 2019 Lenka Spackova Updated Migrating to MariaDB 10.3. Revision 3.3-1 Tue Jun 11 2019 Lenka Spackova Release of Red Hat Software Collections 3.3 Release Notes. Revision 3.3-0 Tue Apr 16 2019 Lenka Spackova Release of Red Hat Software Collections 3.3 Beta Release Notes.

Commands:
4.366. yum-utils 4.366.1. RHBA-2011:1703 - yum-utils bug fix and enhancement update Updated yum-utils packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The yum-utils packages provide a collection of utilities and examples for the Yum package manager. Bug Fixes BZ# 694188 When using the version of the yum-groups-manager utility, an attempt to use the "-c" (or "--config") command line option to specify an alternative configuration file failed, and the utility incorrectly used the default /etc/yum.conf file. This update adapts the underlying source code to correct this error, and yum-groups-manager now accepts alternative configuration files as expected. BZ# 699470 Prior to this update, when the yumdownloader utility failed to download a requested package, it incorrectly exited with a status of 0. With this update, yumdownloader exits with a non-zero status in these situations. BZ# 709043 Due to an error in the detection of the return value of an internal method, the version of the yum-builddep utility failed to exit with a non-zero exit status when it encountered an error. This update applies a patch that ensures the return value of the aforementioned method is correctly evaluated, and when an error is encountered, yum-builddep now exits with a non-zero status as expected. BZ# 713108 Previously, when a user executed the reposync utility with the "-r" (or "--repoid") command line option, the utility incorrectly used repositories that were enabled in the configuration. This update applies a patch to make sure these command line options work correctly. BZ# 734428 When using the priorities plug-in, running the "yum update" command may have incorrectly failed to offer some packages for update. This update corrects this error, and the priorities plug-in no longer prevents "yum update" from fully updating the system. BZ# 659740 Prior to this update, certain commands in the EXAMPLES sections of the repoquery(1), show-installed(1), yum-filter-data(1), yum-groups-manager(1), yum-list-data(1), and yum-verify(1) manual pages used incorrect glyphs for single quotes. Consequent to this, an attempt to copy such a command and run it on the command line failed with an error. This update ensures that all command examples now use typewriter straight single quotes as expected. BZ# 720967 Various typos in the yum-security(8) manual page have been corrected. Enhancement BZ# 710469 Source repository patterns for Red Hat Network (RHN) have been added to the yumdownloader and yum-builddep utilities. All users of yum-utils are advised to upgrade to these updated packages, which fix these bugs.

Commands:
10.2.2. Setting up Communication between Guest Agent and Host The host machine communicates with the guest agent through a VirtIO serial connection between the host and guest machines. A VirtIO serial channel is connected to the host via a character device driver (typically a Unix socket), and the guest listens on this serial channel. The following procedure shows how to set up the host and guest machines for guest agent use. Note For instructions on how to set up the QEMU guest agent on Windows guests, refer to the instructions found here . Procedure 10.1. Setting up communication between guest agent and host Open the guest XML Open the guest XML with the QEMU guest agent configuration. You will need the guest name to open the file. Use the command # virsh list on the host machine to list the guests that it can recognize. In this example, the guest's name is rhel6 : Edit the guest XML file Add the following elements to the XML file and save the changes. <channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/rhel6.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> </channel> Figure 10.1. Editing the guest XML to configure the QEMU guest agent Start the QEMU guest agent in the guest Download and install the guest agent in the guest virtual machine using yum install qemu-guest-agent if you have not done so already. Once installed, start the service as follows: You can now communicate with the guest by sending valid libvirt commands over the established character device driver.

Commands:
virsh edit rhel6
<channel type='unix'> <source mode='bind' path='/var/lib/libvirt/qemu/rhel6.agent'/> <target type='virtio' name='org.qemu.guest_agent.0'/> </channel>
service start qemu-guest-agent
Chapter 23. General Updates runc notifies systemd about user-specified CPU quota limits Previously, the runc program did not notify systemd about user-specified CPU quota limits when a container was started. Consequently, systemd was unaware of the user-specified limits, and therefore the CPU quota was reset to the default value (unlimited) during the systemctl daemon-reload operation. With this update, runc now notifies systemd about user-specified CPU quota limits when a container is started, and the described problem no longer occurs. (BZ#1455071) Segmentation faults in applications because of only non-existent paths in LD_LIBRARY_PATH no longer happen Previously, when the LD_LIBRARY_PATH environment variable contained only non-existent paths, the dynamic loader produced a segmentation fault. Consequently, applications terminated unexpectedly with a segmentation fault at startup in the described situation. The dynamic loader has been fixed. As a result, applications no longer terminate unexpectedly in the described situation. Note that updating the glibc package is enough to fix this bug for any affected applications. (BZ# 1443236 ) The setup package now creates the tape group with the correct group number Previously, when installing the setup package, the tape group was created with an ID that was inconsistent with all other versions of Red Hat Enterprise Linux. With this update, the group ID has been changed from 30 to the standard 33 . As a result, fresh installations of the operating system now have the correct group number for the tape group. On previously installed systems affected by this problem: 1. Edit the group ID in the /etc/group and /etc/gshadow files. 2. Change the group ownership for all files owned by the former tape group. (BZ#1433020)

Commands:
6.4. JAR Deployment For development time or quick deployment you can deploy the translator JAR using the Management CLI or AdminShell or Management Console. When you deploy dependencies in JAR form to Red Hat JBoss Data Virtualization, Java libraries and any other third-party libraries must be defined under META-INF/MANIFEST.MF file. Example 6.2. Example MANIFEST.mf file The following example is the /META-INF/MANIFEST.mf file provided in the Loopback translator JAR file, EAP_HOME/modules/system/layers/dv/org/jboss/teiid/translator/loopback/main/translator-loopback-[VERSION].jar .

Commands:
Manifest-Version: 1.0 Bnd-LastModified: 1516984498575 Build-Jdk: 1.7.0_85 Build-Timestamp: Fri, 26 Jan 2018 11:34:13 -0500 Built-By: mockbuild Bundle-Description: Loopback Translator Bundle-DocURL: http://www.jboss.org/ Bundle-License: http://www.gnu.org/licenses/lgpl.html Bundle-ManifestVersion: 2 Bundle-Name: Loopback Translator Bundle-SymbolicName: org.jboss.teiid.connectors.translator-loopback Bundle-Vendor: JBoss by Red Hat Bundle-Version: 8.12.11.6_4-redhat-64-12 Created-By: Apache Maven Bundle Plugin Export-Package: org.teiid.translator.loopback;uses:="org.teiid.language, org.teiid.metadata,org.teiid.translator";version="8.12.11" Implementation-Title: Loopback Translator Implementation-URL: http://www.jboss.org/teiid/connectors/translator-loo pback Implementation-Vendor: JBoss by Red Hat Implementation-Vendor-Id: org.jboss.teiid.connectors Implementation-Version: 8.12.11.6_4-redhat-64-12 Import-Package: org.teiid.core.util;version="[8.12,9)",org.teiid.languag e;version="[8.12,9)",org.teiid.logging;version="[8.12,9)",org.teiid.met adata;version="[8.12,9)",org.teiid.translator,org.teiid.translator.jdbc .teiid;version="[8.12,9)" Java-Vendor: Oracle Corporation Java-Version: 1.7.0_85 Os-Arch: amd64 Os-Name: Linux Os-Version: 2.6.32-696.18.7.el6.x86_64 Require-Capability: osgi.ee;filter:="(&(osgi.ee=JavaSE)(version=1.6))" Scm-Connection: scm:git:git://github.com/teiid/teiid.git/connectors/tran slator-loopback Scm-Revision: 01b968a220e981ee820ab1b07df148833eb8b995 Scm-Url: http://github.com/teiid/teiid/connectors/translator-loopback Specification-Title: Loopback Translator Specification-Vendor: JBoss by Red Hat Specification-Version: 8.12.11.6_4-redhat-64-12 Tool: Bnd-2.3.0.201405100607
13.3.3. LDAP Client Applications There are graphical LDAP clients available which support creating and modifying directories, but they are not included with Red Hat Enterprise Linux. One such application is LDAP Browser/Editor - A Java-based tool available online at http://www.iit.edu/~gawojar/ldap/ . Most other LDAP clients access directories as read-only, using them to reference, but not alter, organization-wide information. Some examples of such applications are Sendmail, Mozilla , Gnome Meeting , and Evolution .

Commands:
Providing feedback on Red Hat documentation If you have a suggestion to improve this documentation, or find an error, you can contact technical support at https://access.redhat.com to open a request. Important Ansible plug-ins for Red Hat Developer Hub is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope .

Commands:
3.12. Software Collection Lock File Support By default, programs packaged into a Software Collection create lock files in the /opt/ provider /%{scl}/root/var/lock/ directory. To make lock files more accessible and easier to manage, you are advised to use the nfsmountable macro that redefines the _localstatedir macro. This results in lock files being created underneath the /var/opt/ provider /%{scl}/lock/ directory, outside of the /opt/ provider /%{scl} file system hierarchy. If applications or services packaged into your Software Collection write the lock underneath the /var/opt/ provider /%{scl}/lock/ directory, then those applications and services can run concurrently with the system versions (when the resources of your Software Collection's applications and services will not conflict with the system versions' resources). For example, a lock file mylockfile.lock is normally created in the /var/lock/ directory in the base system installation. If the lock file is a part of a software_collection Software Collection and the nfsmountable macro is defined, the path to the lock file in software_collection is as follows: For more information on using the nfsmountable macro, see Section 3.1, "Using Software Collections over NFS" . Preventing Programs from Running Concurrently If you want to prevent your Software Collection's applications or services from running while the system version of the respective application or service is running, make sure that your applications or services, which require a lock, write the lock to the system directory /var/lock/ . In this way, your applications or services' lock file will not be overwritten. The lock file will not be renamed and the name stays the same as the system version. 3.12.1. Software Collection SysV init Lock File Support When a service is started by an init script, a lock file is touched in the /var/lock/subsys/ directory with the same name as the init script. As discussed in Section 3.4, "Managing Services in Software Collections" , service names include a Software Collection prefix. Use the same naming convention for files underneath /var/lock/subsys/ to ensure that the lock file names do not conflict with the base system installation.

Commands:
/var/opt/ provider / software_collection /lock/ mylockfile.lock
18.3. Installation in Non-Interactive Line Mode If the inst.cmdline option was specified as a boot option in your parameter file (see Section 21.4, "Parameters for Kickstart Installations" ) or the cmdline option was specified in your Kickstart file (see Chapter 27, Kickstart Installations ), Anaconda starts with non-interactive text line mode. In this mode, all necessary information must be provided in the Kickstart file. The installation program will not allow user interaction and it will stop if any required commands are missing.

Commands:
B.31.2. RHSA-2011:0291 - Moderate: java-1.5.0-ibm security update Updated java-1.5.0-ibm packages that fix one security issue are now available for Red Hat Enterprise Linux 4 Extras, and Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The IBM 1.5.0 Java release includes the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. CVE-2010-4476 A denial of service flaw was found in the way certain strings were converted to Double objects. A remote attacker could use this flaw to cause Java based applications to hang, for example, if they parsed Double values in a specially-crafted HTTP request. All users of java-1.5.0-ibm are advised to upgrade to these updated packages, containing the IBM 1.5.0 SR12-FP3 Java release. All running instances of IBM Java must be restarted for this update to take effect.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 8.9 is distributed with the kernel version 4.18.0-513.5.1, which provides support for the following architectures: AMD and Intel 64-bit architectures The 64-bit ARM architecture IBM Power Systems, Little Endian 64-bit IBM Z Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures . For a list of available subscriptions, see Subscription Utilization on the Customer Portal.

Commands:
5.8. Changing the CD for a Virtual Machine You can change the CD accessible to a virtual machine while that virtual machine is running, using ISO images that have been uploaded to the data domain of the virtual machine's cluster. See Uploading Images to a Data Storage Domain in the Administration Guide for details. Changing the CD for a Virtual Machine Click Compute Virtual Machines and select a running virtual machine. Click More Actions ( ), then click Change CD . Select an option from the drop-down list: Select an ISO file from the list to eject the CD currently accessible to the virtual machine and mount that ISO file as a CD. Select [Eject] from the list to eject the CD currently accessible to the virtual machine. Click OK .

Commands:
3.2. Managing Users via the User Manager Application The User Manager application allows you to view, modify, add, and delete local users and groups in the graphical user interface. To start the User Manager application: From the toolbar, select System Administration Users and Groups . Or, type system-config-users at the shell prompt. Note Unless you have superuser privileges, the application will prompt you to authenticate as root . 3.2.1. Viewing Users In order to display the main window of the User Manager to view users, from the toolbar of User Manager select Edit Preferences . If you want to view all the users, that is including system users, clear the Hide system users and groups check box. The Users tab provides a list of local users along with additional information about their user ID, primary group, home directory, login shell, and full name. Figure 3.1. Viewing Users To find a specific user, type the first few letters of the name in the Search filter field and either press Enter , or click the Apply filter button. You can also sort the items according to any of the available columns by clicking the column header.

Commands: