mtpti5iD/redhat-docs_dataset huggingface dataset:
7.311. expect 7.311.1. RHBA-2013:1497 - expect bug fix update Updated expect packages that fix one bug are now available for Red Hat Enterprise Linux 6. The "expect" packages contains a tool for automating and testing interactive command line programs and Tk applications. Tcl is a portable and widely used scripting language, while Tk is a graphical toolkit that eases development of text-based and GUI applications. Bug Fix BZ# 1025202 Prior to this update, the "expect" utility leaked memory when used with the "-re" option, and its memory usage kept increasing indefinitely. A patch has been provided to fix this bug, and "expect" memory usage is now stable and without any leaks. Users of expect are advised to upgrade to these updated packages, which fix this bug.

Commands:
21.2. Canceling Event Notifications in the Administration Portal A user has configured some unnecessary email notifications and wants them canceled. Canceling Event Notifications Click Administration Users . Click the user's User Name to open the details view. Click the Event Notifier tab to list events for which the user receives email notifications. Click Manage Events . Use the Expand All button, or the subject-specific expansion buttons, to view the events. Clear the appropriate check boxes to remove notification for that event. Click OK .

Commands:
4.265. Red Hat Enterprise Linux Release Notes 4.265.1. RHEA-2011:1773 - Red Hat Enterprise Linux 6.2 Release Notes Updated packages containing the Release Notes for Red Hat Enterprise Linux 6.2 are now available. Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security and bug fix errata. The Red Hat Enterprise Linux 6.2 Release Notes documents the major changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications for this minor release. Detailed notes on all changes in this minor release are available in the Technical Notes. Refer to the Online Release Notes for the most up-to-date version of the Red Hat Enterprise Linux 6.2 Release Notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_Release_Notes/index.html 4.265.2. RHEA-2011:1543 - Red Hat Enterprise Linux 6.2 Release Notes Updated packages containing the Release Notes for Red Hat Enterprise Linux 6.2 are now available. Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security and bug fix errata. The Red Hat Enterprise Linux 6.2 Release Notes documents the major changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications for this minor release. Detailed notes on all changes in this minor release are available in the Technical Notes. Refer to the Online Release Notes for the most up-to-date version of the Red Hat Enterprise Linux 6.2 Release Notes: https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/6.2_Release_Notes/index.html

Commands:
16.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. By default, mounted NFS volumes on the client side are labeled with a default context defined by policy for NFS. In common policies, this default context uses the nfs_t type. The root user is able to override the default type using the mount -context option. The following types are used with NFS. Different types allow you to configure flexible access: var_lib_nfs_t This type is used for existing and new files copied to or created in the /var/lib/nfs/ directory. This type should not need to be changed in normal operation. To restore changes to the default settings, run the restorecon -R -v /var/lib/nfs command as the root user. nfsd_exec_t The /usr/sbin/rpc.nfsd file is labeled with the nfsd_exec_t , as are other system executables and libraries related to NFS. Users should not label any files with this type. nfsd_exec_t will transition to nfsd_t .

Commands:
21.14. Verifying Virtualization Extensions Use this section to determine whether your system has the hardware virtualization extensions. Virtualization extensions (Intel VT-x or AMD-V) are required for full virtualization. Run the following command to verify the CPU virtualization extensions are available: Analyze the output. The following output contains a vmx entry indicating an Intel processor with the Intel VT-x extension: The following output contains an svm entry indicating an AMD processor with the AMD-V extensions: If any output is received, the processor has the hardware virtualization extensions. However in some circumstances manufacturers disable the virtualization extensions in BIOS. The " flags: " output content may appear multiple times, once for each hyperthread, core or CPU on the system. The virtualization extensions may be disabled in the BIOS. If the extensions do not appear or full virtualization does not work refer to Procedure 21.3, "Enabling virtualization extensions in BIOS" . Ensure KVM subsystem is loaded As an additional check, verify that the kvm modules are loaded in the kernel: If the output includes kvm_intel or kvm_amd then the kvm hardware virtualization modules are loaded and your system meets requirements. Note If the libvirt package is installed, the virsh command can output a full list of virtualization system capabilities. Run virsh capabilities as root to receive the complete list.

Commands:
grep -E 'svm|vmx' /proc/cpuinfo
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm syscall lm constant_tsc pni monitor ds_cpl vmx est tm2 cx16 xtpr lahf_lm
flags : fpu tsc msr pae mce cx8 apic mtrr mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni cx16 lahf_lm cmp_legacy svm cr8legacy ts fid vid ttp tm stc
lsmod | grep kvm
4.290. seekwatcher 4.290.1. RHBA-2011:1114 - seekwatcher bug fix update An updated seekwatcher package that fixes one bug is now available for Red Hat Enterprise Linux 6. The seekwatcher package generates graphs from blktrace runs to help visualize I/O patterns and performance. It can plot multiple blktrace runs together, making it easy to compare the differences between different benchmark runs. Bug Fix BZ# 681703 Prior to this update, an obsolete "matplotlib" configuration directive in seekwatcher caused seekwatcher to emit a spurious warning when executed. This bug has been fixed in this update and no longer occurs. All users of seekwatcher should upgrade to this updated package, which fixes this bug.

Commands:
Chapter 1. Remote caches Deploy multiple Data Grid Server instances to create remote cache clusters that give you a fault-tolerant and scalable data tier with high-speed access from Hot Rod and REST clients. 1.1. Remote cache tutorials To run these tutorials you need at least one locally running instance of Data Grid Server. Each tutorial will try to connect to a running server in localhost:11222 with admin/password credentials. However, if a Docker instance is found, and the server is not running, tutorials will spin up a local server with Testcontainers . You can download the distribution and run the following commands: USD ./bin/cli.sh user create admin -p "password" USD ./bin/server.sh Note Data Grid Server enables authentication and authorization by default. Creating a user named admin gives you administrative access to Data Grid Server. Building and running remote cache tutorials You can build and run remote cache tutorials directly in your IDE or from the command line as follows: USD ./mvnw -s /path/to/maven-settings.xml clean package exec:exec 1.2. Hot Rod Java client tutorials Data Grid requires Java 11 at a minimum. However, Hot Rod Java clients running in applications that require Java 8 can continue using older versions of client libraries. Tutorial link Description Remote cache use example The simplest code example that demonstrates how a remote distributed cache works. Per cache configuration Demonstrates how to configure caches dynamically when we connect to the Data Grid Server. Near caches Demonstrates how configure near caching to improve the read performance in remote caches. Cache Admin API Demonstrates how to use the Administration API to create caches and cache templates dynamically. Encoding Demonstrates how encoding of caches work. Client listeners Detect when data changes in a remote cache with Client Listeners. Query Demonstrates how to query remote cache values. Continuous query Demonstrates how to use Continuous Query and remote caches. Transactions Demonstrates how remote transactions work. Secured caches Demonstrates how to configure caches that have authorization enabled. TLS authorization Demonstrates how to connect to Data Grid Server with TLS authorization. Counters Demonstrates how remote counters work. Multimap Demonstrates how remote multimap works. Task execution Demonstrates how to register server tasks and how to execute them from the Hot Rod client. JUnit 5 and Testcontainers Demonstrates how to use the Data Grid and JUnit 5 extension. Persistence Demonstrates how to use the Data Grid and persistent caches. Redis Client Demonstrates how to use the Data Grid and Redis client to read and write using the Resp protocol. Reactive API Demonstrates how to use the Data Grid with the reactive API based on Mutiny. Data Grid documentation You can find more resources for Hot Rod Java clients in our documentation at: Hot Rod Java client guide Marshalling and Encoding Data Guide Querying Data Grid caches REST API Resp Protocol Smallrye Mutiny

Commands:
./bin/cli.sh user create admin -p "password" ./bin/server.sh
./mvnw -s /path/to/maven-settings.xml clean package exec:exec
Chapter 5. Technology previews This section describes the technology preview features introduced in Red Hat OpenShift Data Foundation 4.18 under Technology Preview support limitations. Important Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. Technology Preview features are provided with a limited support scope, as detailed on the Customer Portal: Technology Preview Features Support Scope . 5.1. Multi-Volume Consistency for Backup - CephFS and block Multi-volume consistency which provides crash consistent multi-volume consistency groups for backup solutions can be used by applications that are deployed over multiple volumes. This provides support for OpenShift Virtualization and helps to better support applications. Red Hat OpenShift Data Foundation is the first storage vendor that implements this new and important CSI feature. For more information, see the knowledgebase article CephFS VolumeGroupSnapshot in OpenShift Data Foundation . 5.2. More disaster recovery recipe capabilities for CephFS-based applications The capabilities of disaster recovery recipes are enhanced to support more applications. Support for CephFS baked applications is in technology preview status for this release.

Commands:
Chapter 27. Creating guided decision tables You can use guided decision tables to define rule attributes, metadata, conditions, and actions in a tabular format that can be added to your business rules project. Procedure In Business Central, go to Menu Design Projects and click the project name. Click Add Asset Guided Decision Table . Enter an informative Guided Decision Table name and select the appropriate Package . The package that you specify must be the same package where the required data objects have been assigned or will be assigned. Select Use Wizard to finish setting up the table in the wizard, or leave this option unselected to finish creating the table and specify remaining configurations in the guided decision tables designer. Select the hit policy that you want your rows of rules in the table to conform to. For details, see Chapter 28, Hit policies for guided decision tables . Specify whether you want the Extended entry or Limited entry table. For details, see Section 28.1.1, "Types of guided decision tables" . Click Ok to complete the setup. If you have selected Use Wizard , the Guided Decision Table wizard is displayed. If you did not select the Use Wizard option, this prompt does not appear and you are taken directly to the table designer. For example, the following wizard setup is for a guided decision table in a loan application decision service: Figure 27.1. Create guided decision table If you are using the wizard, add any available imports, fact patterns, constraints, and actions, and select whether table columns should expand. Click Finish to close the wizard and view the table designer. Figure 27.2. Guided Decision Table wizard In the guided decision tables designer, you can add or edit columns and rows, and make other final adjustments.

Commands:
Chapter 1. Overview Red Hat Gluster Storage Web Administration provides visual monitoring and metrics infrastructure for Red Hat Gluster Storage 3.5 and is the primary method to monitor your Red Hat Gluster Storage environment. The Red Hat Gluster Storage Web Administration is based on the Tendrl upstream project and utilizes Ansible automation for installation. The key goal of Red Hat Gluster Storage Web Administration is to provide deep metrics and visualization of Red Hat Storage Gluster clusters and the associated physical storage elements such as storage nodes, volumes, and bricks. Key Features Monitoring dashboards for Clusters, Hosts, Volumes, and Bricks Top-level list views of Clusters, Hosts, and Volumes SNMPv3 Configuration and alerting User Management Importing Gluster cluster

Commands:
Chapter 9. Importing projects from Git repositories Git is a distributed version control system. It implements revisions as commit objects. When you save your changes to a repository, a new commit object in the Git repository is created. Business Central uses Git to store project data, including assets such as rules and processes. When you create a project in Business Central, it is added to a Git repository that is connected to Business Central. If you have projects in Git repositories, you can import the project's master branch or import the master branch along with other specific branches into the Business Central Git repository through Business Central spaces. Prerequisites Red Hat Process Automation Manager projects exist in an external Git repository. You have the credentials required for read access to that external Git repository. Procedure In Business Central, go to Menu Design Projects . Select or create the space into which you want to import the projects. The default space is MySpace . In the upper-right corner of the screen, click the arrow to Add Project and select Import Project . In the Import Project window, enter the URL and credentials for the Git repository that contains the project that you want to import and click Import . The Import Projects page is displayed. Optional: To import master and specific branches, do the following tasks: On the Import Projects page, click the branches icon. In the Branches to be imported window, select branches from the list. Note You must select the master branch as a minimum. Click Ok . On the Import Projects page, ensure the project is highlighted and click Ok .

Commands:
3.6. Runtime Device Power Management Runtime device power management (RDPM) helps to reduce power consumption with minimum user-visible impact. If a device has been idle for a sufficient time and the RDPM hardware support exists in both the device and driver, the device is put into a lower power state. The recovery from the lower power state is assured by an external I/O event for this device, which triggers the kernel and the device driver to bring the device back to the running state. All this occurs automatically, as RDPM is enabled by default. Users are allowed to control RDPM of a device by setting the attribute in a particular RDPM configuration file. The RDPM configuration files for particular devices can be found in the /sys/devices/ device /power/ directory, where device replaces the path to the directory of a particular device. For example, to configure the RDPM for a CPU, access this directory: Bringing a device back from a lower power state to the running state adds additional latency to the I/O operation. The duration of that additional delay is device-specific. The configuration scheme described here allows the system administrator to disable RDPM on a device-by-device basis and to both examine and control some of the other parameters. Every /sys/devices/ device /power directory contains the following configuration files: control This file is used to enable or disable RDPM for a particular device. All devices have one of the following two values of the attribute in the control file: auto default for all devices, they may be subject to automatic RDPM, depending on their driver on prevents the driver from managing the device's power state at run time autosuspend_delay_ms This file controls the auto-suspend delay, which is the minimum time period of inactivity between idle state and suspending of the device. The file contains the auto-suspend delay value in milliseconds. A negative value prevents the device from being suspended at run time, thus having the same effect as setting the attribute in the /sys/devices/ device /power/control file to on . Values higher than 1000 are rounded up to the nearest second.

Commands:
/sys/devices/system/cpu/power/
3.15. RHEA-2011:1622 - new package: python-suds A new python-suds package is now available for Red Hat Enterprise Linux 6. The python-suds package provides a lightweight implementation of the Simple Object Access Protocol (SOAP) for the Python programming environment. This enhancement update adds the python-suds package to Red Hat Enterprise Linux 6. (BZ# 681835 ) All users who require python-suds are advised to install this new package.

Commands:
7.159. perl-Sys-Virt 7.159.1. RHBA-2015:1387 - perl-Sys-Virt bug fix update Updated perl-Sys-Virt packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The Sys::Virt module provides a Perl XS binding to the libvirt virtual machine management APIs. This allows machines running within arbitrary virtualization containers to be managed with a consistent API. Bug Fixes BZ# 905836 Previously, using the libvirt-tck utility to display virtual CPU (VCPU) information only printed a part of the expected diagnostics. With this update, the get_vcpu_info() function handles VCPU flags properly, and libvirt-tck displays the full extent of the expected information. BZ# 908274 Prior to this update, using the libvirt-tck utility to find the parent device of a node device with no parent incorrectly returned a "libvirt error code: 0" error message. Now, it is valid for the virNodeDeviceGetParent() function to return NULL if the parent device is nonexistent, and the error message is no longer displayed. Users of perl-Sys-Virt are advised to upgrade to these updated packages, which fix these bugs.

Commands:
21.2.4. Preserving ACLs The Red Hat Enterprise Linux 4 kernel provides ACL support for the ext3 file system and ext3 file systems mounted with the NFS or Samba protocols. Thus, if an ext3 file system has ACLs enabled for it and is NFS exported, and if the NFS client can read ACLs, they are used by the NFS client as well. For more information about mounting NFS file systems with ACLs, refer to Chapter 14, Access Control Lists .

Commands:
Chapter 3. LVM Administration Overview This chapter provides an overview of the administrative procedures you use to configure LVM logical volumes. This chapter is intended to provide a general understanding of the steps involved. For specific step-by-step examples of common LVM configuration procedures, see Chapter 5, LVM Configuration Examples . For descriptions of the CLI commands you can use to perform LVM administration, see Chapter 4, LVM Administration with CLI Commands . Alternately, you can use the LVM GUI, which is described in Chapter 7, LVM Administration with the LVM GUI . 3.1. Creating LVM Volumes in a Cluster In order to enable the LVM volumes you are creating in a cluster, the cluster infrastructure must be running and the cluster must be quorate. Creating clustered logical volumes also requires changes to the lvm.conf file for cluster-wide locking. Other than this setup, creating LVM logical volumes in a clustered environment is identical to creating LVM logical volumes on a single node. There is no difference in the LVM commands themselves, or in the LVM GUI interface. In order to enable cluster-wide locking, you can run the lvmconf command, as follows: Running the lvmconf command modifies the lvm.conf file to specify the appropriate locking type for clustered volumes. Note Shared storage for use in Red Hat Cluster Suite requires that you be running the cluster logical volume manager daemon ( clvmd ) or the High Availability Logical Volume Management agents (HA-LVM). If you are not able to use either the clvmd daemon or HA-LVM for operational reasons or because you do not have the correct entitlements, you must not use single-instance LVM on the shared disk as this may result in data corruption. If you have any concerns please contact your Red Hat service representative. For information on how to set up the cluster infrastructure, see Configuring and Managing a Red Hat Cluster . For an example of creating a mirrored logical volume in a cluster, see Section 5.5, "Creating a Mirrored LVM Logical Volume in a Cluster" .

Commands:
/usr/sbin/lvmconf --enable-cluster