mtpti5iD/redhat-docs_dataset huggingface dataset:
10.2. Setting Up a Cache Currently, Red Hat Enterprise Linux 6 only provides the cachefiles caching back-end. The cachefilesd daemon initiates and manages cachefiles . The /etc/cachefilesd.conf file controls how cachefiles provides caching services. To configure a cache back-end of this type, the cachefilesd package must be installed. The first setting to configure in a cache back-end is which directory to use as a cache. To configure this, use the following parameter: Typically, the cache back-end directory is set in /etc/cachefilesd.conf as /var/cache/fscache , as in: FS-Cache will store the cache in the file system that hosts /path/to/cache . On a laptop, it is advisable to use the root file system ( / ) as the host file system, but for a desktop machine it would be more prudent to mount a disk partition specifically for the cache. File systems that support functionalities required by FS-Cache cache back-end include the Red Hat Enterprise Linux 6 implementations of the following file systems: ext3 (with extended attributes enabled) ext4 BTRFS XFS The host file system must support user-defined extended attributes; FS-Cache uses these attributes to store coherency maintenance information. To enable user-defined extended attributes for ext3 file systems (i.e. device ), use: Alternatively, extended attributes for a file system can be enabled at mount time, as in: The cache back-end works by maintaining a certain amount of free space on the partition hosting the cache. It grows and shrinks the cache in response to other elements of the system using up free space, making it safe to use on the root file system (for example, on a laptop). FS-Cache sets defaults on this behavior, which can be configured via cache cull limits . For more information about configuring cache cull limits, refer to Section 10.4, "Setting Cache Cull Limits" . Once the configuration file is in place, start up the cachefilesd daemon: To configure cachefilesd to start at boot time, execute the following command as root:

Commands:
dir /path/to/cache
dir /var/cache/fscache
tune2fs -o user_xattr /dev/ device
mount /dev/ device /path/to/cache -o user_xattr
service cachefilesd start
chkconfig cachefilesd on
Chapter 3. Locating your created Immutable (OSTree) images You can list your immutable systems on the Hosted Inventory dashboard. You can see detailed information about your immutable systems, update one or more systems, and add or remove these systems to a group. Note If you do not have a Immutable OSTree system created, the Immutable(OSTree) tab is not displayed. In this case, you must create your Immutable (OStree) images from image builder. See Building an OSTree image with custom repositories . + To locate your images in the image builder dashboard, complete the following steps. Prerequisites You must have a Red Hat Hybrid Cloud Console account. Procedure Access Red Hat Hybrid Cloud Console platform and log in. From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory > Images . The Insights image builder environment opens. Locate your image by name. Type your image name in the search bar menu. If your image exists, click the image name. You can see the image details, such as version, OSTree commit hash, SSH key, added packages, among others.

Commands:
Chapter 2. Architecture and Concepts This chapter provides an overview of Red Hat Gluster Storage architecture and Storage concepts. 2.1. Architecture At the core of the Red Hat Gluster Storage design is a completely new method of architecting storage. The result is a system that has immense scalability, is highly resilient, and offers extraordinary performance. In a scale-out system, one of the biggest challenges is keeping track of the logical and physical locations of data and metadata. Most distributed systems solve this problem by creating a metadata server to track the location of data and metadata. As traditional systems add more files, more servers, or more disks, the central metadata server becomes a performance bottleneck, as well as a central point of failure. Unlike other traditional storage solutions, Red Hat Gluster Storage does not need a metadata server, and locates files algorithmically using an elastic hashing algorithm. This no-metadata server architecture ensures better performance, linear scalability, and reliability. Figure 2.1. Red Hat Gluster Storage Architecture

Commands:
Chapter 10. Entitlement Certificate-based RHN The new subscription management platform delivers Red Hat subscriptions and software services in a flexible, scalable and secure way. When installing a new Red Hat Enterprise Linux 6 system, a user receives X.509 certificates which contain information about which Red Hat products are installed and what subscriptions the machine is consuming. The subscription information includes support levels, expiration dates, Red Hat account numbers, and Red Hat contract numbers. In addition, an X.509 certificate allows a machine to authenticate to the Red Hat Content Delivery Network (CDN). The globally distributed Red Hat Content Delivery Network (CDN) is designed to work even with an outage of the Red Hat systems. Users outside of North America should see improved update speeds and availability with the new system. RHN Classic continues to be the default option for computer registration and for receiving updates. Entitlement certificates for disconnected systems Red Hat customer portal, in conjunction with new functionality available in Red Hat Enterprise Linux 6.2, allows customers to register and subscribe up to 25 machines that are completely disconnected from the Internet. Prior to this enhancement, customers with disconnected systems were not able to receive the benefits of subscription information and tracking from the RHN website. For customers with more than 25 disconnected machines, RHN Satellite continues to be the recommended option at additional cost. Automatic regeneration of a certificate after renewal of a subscription It is now possible to automatically regenerate new entitlement certificates after the renewal of a subscription. Prior to this enhancement, customers were required to manually regenerate the certificate in order to continue receiving software updates and other subscription services. Automatically regenerating a certificate minimizes service interruptions. Users are also notified of cases where auto regeneration of certificates was not successful. For more information, refer to https://www.redhat.com/rhel/renew/faqs/ . Red Hat Subscription Manager and the Subscription Service In Red Hat Enterprise Linux 6.2, during system registration, the Red Hat Subscription Manager is now used by default. Note The Red Hat Enterprise Linux 6 Subscription Management Guide contains further information on managing subscriptions. The Red Hat Enterprise Linux 6 Installation Guide contains further information on the registration and subscription process during firstboot and kickstart .

Commands:
Chapter 13. System calls in RHEL for Real Time The real-time system call is a function used by application programs to communicate with the kernel. It is a mechanism for programs to order resources from the kernel. 13.1. sched_yield() function The sched_yield() function is designed for a processor to select a process other than the running one. This type of request is prone to failure when issued from within a poorly-written application. When the sched_yield() function is used within processes with real-time priorities, it can display unexpected behavior. The process that calls sched_yield() moves to the tail of the queue of processes running at same priority. When there are no other processes running at the same priority, the process that called sched_yield() continues to run. If the priority of that process is high, it can potentially create a busy loop, rendering the machine unusable. In general, do not use sched_yield() on real-time processes. 13.2. getrusage() function The getrusage() function retrieves important information from a specified process or its threads. It reports on information such as: The number of voluntary and involuntary context switches. Major and minor page faults. Amount of memory in use. getrusage() enables you to query an application to provide information relevant to both performance tuning and debugging activities. getrusage() retrieves information that would otherwise need to be cataloged from several different files in the /proc/ directory and would be hard to synchronize with specific actions or events on the application. Note Not all the fields contained in the structure filled with getrusage() results are set by the kernel. Some of them are kept for compatibility reasons only. Additional resources getrusage(2) man page on your system

Commands:
3.2.4. Standby Mode The following command puts the specified node into standby mode. The specified node is no longer able to host resources. Any resources currently active on the node will be moved to another node. If you specify the --all , this command puts all nodes into standby mode. You can use this command when updating a resource's packages. You can also use this command when testing a configuration, to simulate recovery without actually shutting down a node. The following command removes the specified node from standby mode. After running this command, the specified node is then able to host resources. If you specify the --all , this command removes all nodes from standby mode. Note that when you execute the pcs cluster standby command, this adds constraints to the resources to prevent them from running on the indicated node. When you execute the pcs cluster unstandby command, this removes the constraints. This does not necessarily move the resources back to the indicated node; where the resources can run at that point depends on how you have configured your resources initially. For information on resource constraints, see Chapter 6, Resource Constraints .

Commands:
pcs cluster standby node | --all
pcs cluster unstandby node | --all
6.4. Projection Queries In many cases returning the full domain object is unnecessary, and only a small subset of attributes are desired by the application. Projection Queries allow a specific subset of attributes (or attribute paths) to be returned. If a projection query is used then the Query.list() will not return the whole domain entity ( List<Object> ), but instead will return a List<Object[]> , with each entry in the array corresponding to a projected attribute. To define a projection query use the select(...) method when building the query, as seen in the following example: Example 6.4. Retrieving title and publication year Report a bug

Commands:
// Match all books that have the word "engine" in their title or description // and return only their title and publication year. Query query = queryFactory.from(Book.class) .select(Expression.property("title"), Expression.property("publicationYear")) .having("title").like("%engine%") .or().having("description").like("%engine%") .toBuilder() .build(); // results.get(0)[0] contains the first matching entry's title // results.get(0)[1] contains the first matching entry's publication year List<Object[]> results = query.list();
Chapter 6. Security mapping to a security domain When you add a security mapping to a security domain, this allows you to combine authentication and authorization information after the authentication or authorization occurs, but before the information passes to the application. To add a security mapping to an existing security domain, a code , type , and relevant module options must be configured. Example: Management CLI commands for adding a SimpleRoles security mapping to an existing security domain /subsystem=security/security-domain=sampleapp/mapping=classic:add /subsystem=security/security-domain=sampleapp/mapping=classic/mapping-module=SimpleRoles:add(code=SimpleRoles,type=role,module-options=[("user1"=>"specialRole")]) reload The code field is the short name, for example SimpleRoles , PropertiesRoles , DatabaseRoles , or class name of the security mapping module. The type field refers to the type of mapping this module performs, and the allowed values are principal , role , attribute , or credential . Additional resources For more information on security mapping, see Security mapping in JBoss EAP . For a full list of the available security mapping modules and their module options, see Security mapping modules in JBoss EAP .

Commands:
/subsystem=security/security-domain=sampleapp/mapping=classic:add /subsystem=security/security-domain=sampleapp/mapping=classic/mapping-module=SimpleRoles:add(code=SimpleRoles,type=role,module-options=[("user1"=>"specialRole")]) reload
Chapter 16. Graphics The X server shipped in Red Hat Enterprise Linux 6.2 has been updated to the upstream X.org 1.10 X server and the upstream Mesa 7.11 releases. The X server had internal structure changes that required updating all video and input drivers. In addition, the kernel graphics support has been updated to include new hardware support and bug fixes. AMD Improved support for ATI/AMD GPU series HD2xxx, HD4xxx, HD5xxx, FirePro. Support added for new HD6xxx series, new model in the FirePro series and new mobile GPU HD6xxxM series. Intel Support has been added for Intel's generation class of chipsets. Nouveau 2D/Xv acceleration is now supported on GeForce GT2xx (and Quadro equivalents). Suspend/resume support has been improved. X server RandR-enabled drivers (Intel, Nouveau, Radeon) now confine the cursor to the visible area of the screen in asymmetric multihead configurations. The Composite extension is now functional when Xinerama is used to span a single desktop across multiple GPUs. X server configuration may now be managed with configuration file snippets under /etc/X11/xorg.conf.d/ in addition to /etc/X11/xorg.conf itself. X.org input device configuration in these snippets applies when the device becomes available to the X server at runtime. Refer to the 1.10 X server upstream announcement for additional information: http://lists.freedesktop.org/archives/xorg-announce/2011-February/001612.html . Mesa See the Mesa 7.11 upstream announcement for release notes: http://www.mesa3d.org/relnotes/7.11.html .

Commands:
Chapter 8. Configuring the OpenTelemetry Collector metrics You can enable metrics and alerts of OpenTelemetry Collector instances. Prerequisites Monitoring for user-defined projects is enabled in the cluster. Procedure To enable metrics of an OpenTelemetry Collector instance, set the spec.observability.metrics.enableMetrics field to true : apiVersion: opentelemetry.io/v1beta1 kind: OpenTelemetryCollector metadata: name: <name> spec: observability: metrics: enableMetrics: true Verification You can use the Administrator view of the web console to verify successful configuration: Go to Observe Targets , filter by Source: User , and check that the ServiceMonitors in the opentelemetry-collector-<instance_name> format have the Up status. Additional resources Enabling monitoring for user-defined projects

Commands:
apiVersion: opentelemetry.io/v1beta1 kind: OpenTelemetryCollector metadata: name: <name> spec: observability: metrics: enableMetrics: true
Chapter 1. Insights proxy overview Red Hat Insights is a Software-as-a-Service (SaaS) application included with every subscription to Red Hat Enterprise Linux, Red Hat OpenShift, and Red Hat Ansible Automation Platform. Red Hat Insights provides predictive analytics, automatically discovers relevant insights, recommends tailored actions, and automates tasks. If you have constraints that prevent your systems from directly accessing the Internet, Insights proxy provides capabilities and features for securely and efficiently connecting your systems to Red Hat Insights, including: Easy Access The Insights proxy resolves architectural, technical and firewall configuration issues, freeing you from troubleshooting these issues yourself. Security The Insights proxy protects your systems from malware threats by filtering traffic and scanning for malicious content. It can also serve as a firewall. Quickly view and execute recommendations You can view and execute recommendations to keep your fleet efficient, secure, compliant, and updated. Simply send a subset of log data to the Red Hat Insights service by using a single proxy. Patching You can connect to Red Hat as needed to pull the most recent patches into your network. This enables you to push updates to systems behind your firewall, using your own tools and schedules.

Commands:
7.69. gstreamer-plugins-good 7.69.1. RHBA-2015:0666 - gstreamer-plugins-good bug fix update Updated gstreamer-plugins-good packages that fix one bug are now available for Red Hat Enterprise Linux 6. GStreamer is a streaming media framework based on graphs of filters which operate on media data. The gstreamer-plugins-good packages contain a collection of well-supported plug-ins of good quality and under the LGPL license. Bug Fix BZ# 622776 Previously, using GStreamer with the Phonon back end, common in the K Desktop Environment (KDE), led to sound synchronization problems, which caused jitter in the audio output. With this update, the improperly working GStreamer component and the consequent sound synchronization problems have been fixed. As a result, sound quality in applications using Phonon is no longer affected. Users of gstreamer-plugins-good are advised to upgrade to these updated packages, which fix this bug.

Commands:
Installing Red Hat Virtualization as a self-hosted engine using the command line Red Hat Virtualization 4.4 Using the command line to install the Red Hat Virtualization Manager as a virtual machine running on the same hosts it manages Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to install a self-hosted engine environment - where the Red Hat Virtualization Manager (or "engine") is installed on a virtual machine that runs on specialized hosts in the same environment it manages - using the command line to configure and run an automated installation. If this is not the configuration you want to use, see the other Installation Options in the Product Guide .

Commands:
Chapter 15. Registering RHEL by using Subscription Manager Post-installation, you must register your system to get continuous updates. 15.1. Registering RHEL 9 using the installer GUI You can register a Red Hat Enterprise Linux 9 by using the RHEL installer GUI. Prerequisites You have a valid user account on the Red Hat Customer Portal. See the Create a Red Hat Login page . You have a valid Activation Key and Organization id. Procedure From the Installation Summary screen, under Software , click Connect to Red Hat . Authenticate your Red Hat account using the Account or Activation Key option. Optional: In the Set System Purpose field select the Role , SLA , and Usage attribute that you want to set from the drop-down menu. At this point, your Red Hat Enterprise Linux 9 system has been successfully registered. 15.2. Registration Assistant Registration Assistant is designed to help you choose the most suitable registration option for your Red Hat Enterprise Linux environment. Additional resources For assistance with using a username and password to register RHEL with the Subscription Manager client, see the RHEL registration assistant on the Customer Portal. For assistance with registering your RHEL system to Red Hat Insights, see the Insights registration assistant on the Hybrid Cloud Console. 15.3. Registering your system using the command line You can register your Red Hat Enterprise Linux 9 subscription by using the command line. For an improved and simplified experience registering your hosts to Red Hat, use remote host configuration (RHC). The RHC client registers your system to Red Hat making your system ready for Insights data collection and enabling direct issue remediation from Insights for Red Hat Enterprise Linux. For more information, see RHC registration . Prerequisites You have an active, non-evaluation Red Hat Enterprise Linux subscription. Your Red Hat subscription status is verified. You have not previously received a Red Hat Enterprise Linux 9 subscription. You have successfully installed Red Hat Enterprise Linux 9 and logged into the system as root. Procedure Open a terminal window as a root user. Register your Red Hat Enterprise Linux system by using the activation key: When the system is successfully registered, an output similar to the following is displayed: Additional resources Using an activation key to register a system with Red Hat Subscription Manager Getting Started with RHEL System Registration

Commands:
subscription-manager register --activationkey= <activation_key_name> --org= <organization_ID>
The system has been registered with id: 62edc0f8-855b-4184-b1b8-72a9dc793b96
Appendix B. RHEL 8 repositories If your system is registered to the Red Hat Content Delivery Network (CDN) using the Red Hat Subscription Manager (RHSM), RHEL 8 repositories are automatically enabled during the in-place upgrade. However, on systems registered to Red Hat Satellite using RHSM, you must manually enable and synchronize both RHEL 7 and RHEL 8 repositories before running the pre-upgrade report. Note Make sure to enable the target operating system (OS) version of each repository, for example RHEL 8.10. If you have enabled only the RHEL 8 version of the repositories, the in-place upgrade is inhibited. If you plan to use Red Hat Satellite during the upgrade, you must enable and synchronize at least the following RHEL 8 repositories before the upgrade using either the Satellite web UI or the hammer repository-set enable and hammer product synchronize commands: Note Replace <target_os_version> with the target operating system (OS) version, for example 8.10. Table B.1. RHEL 8 repositories Architecture Repository Repository ID Repository name Release version 64-bit Intel BaseOS rhel-8-for-x86_64-baseos-rpms Red Hat Enterprise Linux 8 for x86_64 - BaseOS (RPMs) x86_64 <target_os_version> AppStream rhel-8-for-x86_64-appstream-rpms Red Hat Enterprise Linux 8 for x86_64 - AppStream (RPMs) x86_64 <target_os_version> IBM Power8 (little endian) BaseOS rhel-8-for-ppc64le-baseos-rpms Red Hat Enterprise Linux 8 for Power, little endian - BaseOS (RPMs) ppc64le <target_os_version> AppStream rhel-8-for-ppc64le-appstream-rpms Red Hat Enterprise Linux 8 for Power, little endian - AppStream (RPMs) ppc64le <target_os_version> IBM Z BaseOS rhel-8-for-s390x-baseos-rpms Red Hat Enterprise Linux 8 for IBM z Systems - BaseOS (RPMs) s390x <target_os_version> AppStream rhel-8-for-s390x-appstream-rpms Red Hat Enterprise Linux 8 for IBM z Systems - AppStream (RPMs) s390x <target_os_version>

Commands:
Chapter 4. Managing Satellite with Ansible Collections Satellite Ansible Collections is a set of Ansible modules that interact with the Satellite API. You can use Satellite Ansible Collections to manage and automate many aspects of Satellite. 4.1. Installing the Satellite Ansible Modules Use this procedure to install the Satellite Ansible modules. Prerequisite Ensure that the Ansible 2.9 or later repository is enabled and the ansible package is updated: Procedure Install the package using the following command: 4.2. Viewing the Satellite Ansible Modules You can view the installed Satellite Ansible modules by listing the content of the following directory: Note At the time of writing, the ansible-doc -l command does not list collections yet. Alternatively, you can also see the complete list of Satellite Ansible modules and other related information at Red Hat Ansible Automation Platform . All modules are in the redhat.satellite namespace and can be referred to in the format redhat.satellite._module_name_ . For example, to display information about the activation_key module, enter the following command:

Commands:
subscription-manager repos --enable rhel-7-server-ansible-2.9-rpms satellite-maintain packages update ansible
satellite-maintain packages install ansible-collection-redhat-satellite
ls /usr/share/ansible/collections/ansible_collections/redhat/satellite/plugins/modules/
ansible-doc redhat.satellite.activation_key