mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 15. Desktop Mozilla Thunderbird Mozilla Thunderbird , provided by the thunderbird package, has been added in Red Hat Enterprise Linux 7.1 and offers an alternative to the Evolution mail and newsgroup client. Support for Quad-buffered OpenGL Stereo Visuals GNOME Shell and the Mutter compositing window manager now allow you to use quad-buffered OpenGL stereo visuals on supported hardware. You need to have the NVIDIA Display Driver version 337 or later installed to be able to properly use this feature. Online Account Providers A new GSettings key org.gnome.online-accounts.whitelisted-providers has been added to GNOME Online Accounts (provided by the gnome-online-accounts package). This key provides a list of online account providers that are explicitly allowed to be loaded on startup. By specifying this key, system administrators can enable appropriate providers or selectively disable others.

Commands:
Chapter 1. Long Term Support for AMQ Broker 7.12 AMQ Broker 7.12 has been designated as a Long Term Support (LTS) release version. For details of the terms of an LTS release, see How long are AMQ LTS releases supported? Support for Red Hat Enterprise Linux and OpenShift Container Platform The AMQ Broker 7.12 LTS version supports: Red Hat Enterprise Linux 7, 8 and 9 OpenShift Container Platform 4.14, 4.15, 4.16, 4.17 and 4.18 Microsoft Windows Server 2016, 2019 and 2022 Red Hat strives to ensure that AMQ Broker remains compatible with future versions of OpenShift Container Platform; however this compatibility cannot be guaranteed. Interoperability testing is performed for each new OpenShift Container Platform version. If no compatibility issues are found, the new OpenShift Container Platform version is added to the Red Hat AMQ Broker 7 Supported Configurations .

Commands:
Chapter 12. Creating a Red Hat Single Sign-On connection secret Use this procedure to create a connection secret for Red Hat Single Sign-On. Procedure Navigate to https://<sso_host>/auth/realms/ansible-automation-platform . Copy the public_key value. In the OpenShift Web UI, navigate to Workloads Secrets . Select the ansible-automation-platform project. Click Create , and select From YAML . Edit the following YAML to create the secret apiVersion: v1 kind: Secret metadata: name: automation-hub-sso 1 namespace: ansible-automation-platform type: Opaque stringData: keycloak_host: "keycloak-rh-sso.apps-crc.testing" keycloak_port: "443" keycloak_protocol: "https" keycloak_realm: "ansible-automation-platform" keycloak_admin_role: "hubadmin" social_auth_keycloak_key: "automation-hub" social_auth_keycloak_secret: "client-secret" 2 social_auth_keycloak_public_key: >- 3 1 This name is used in the step when creating the automation hub instance. 2 If the secret was changed when creating the Keycloak client for automation hub be sure to change this value to match. 3 Enter the value of the public_key for your Ansible Automation Platform Operator deployment. Click Create and wait for the process to complete.

Commands:
apiVersion: v1 kind: Secret metadata: name: automation-hub-sso 1 namespace: ansible-automation-platform type: Opaque stringData: keycloak_host: "keycloak-rh-sso.apps-crc.testing" keycloak_port: "443" keycloak_protocol: "https" keycloak_realm: "ansible-automation-platform" keycloak_admin_role: "hubadmin" social_auth_keycloak_key: "automation-hub" social_auth_keycloak_secret: "client-secret" 2 social_auth_keycloak_public_key: >- 3
Chapter 29. Graphics Driver and Miscellaneous Driver Updates The HDA driver has been updated to the latest upstream version to use the new jack kctls method. The HPI driver has been updated to version 4.14. The Realtek HD-audio codec driver has been updated to include the update of EAPD init codes. The IPMI driver has been updated to replace the timespec usage by timespec64. The i915 driver has been updated to include the rebase of ACPI Video Extensions driver in Red Hat Enterprise Linux 7.2. The ACPI Fan driver has been updated to version 0.25. The Update NVM-Express driver has been updated to version 3.19. The rtsx driver has been updated to version 4.0 to support rtl8402, rts524A, rts525A chips. The Generic WorkQueue Engine device driver has been updated to the latest upstream version. The PCI driver has been updated to version 3.16. The EDAC kernel module has been updated to provide support for Intel Xeon v4 processors. The pstate driver has been updated to support 6th Generation Intel Core processor. The intel_idle driver has been updated to support 6th Generation Intel Core processor.

Commands:
Chapter 6. Content Delivery Network Structure Red Hat Content Delivery Network (CDN), located at cdn.redhat.com , is a geographically distributed series of static webservers which include content and errata designed to be used by systems. This content can be accessed directly through a system registered using Subscription Manager or through the Satellite web UI. The accessible subset of the CDN is configured through subscriptions attached to a system using Red Hat Subscription Management or using Satellite Server. Red Hat Content Delivery network is protected by X.509 certificate authentication to ensure that only valid users can access it. Directory Structure of the CDN. 1 The content directory. 2 Directory responsible for the lifecycle of the content. Common directories include beta (for Beta code), dist (for Production) and eus (For Extended Update Support) directories. 3 Directory responsible for the Product name. Usually rhel for Red Hat Enterprise Linux. 4 Directory responsible for the type of the Product. For Red Hat Enterprise Linux this might include server , workstation , and computenode directories. 5 Directory responsible for the release version, such as 7 , 7.2 or 7Server . 6 Directory responsible for the base architecture, such as i386 or x86_64 . 7 Directory responsible for the repository name, such as sat-tools , kickstart , rhscl . Some components have additional subdirectories which might vary. This directory structure is also used in the Red Hat Subscription Manifest.

Commands:
tree -d -L 11 └── content 1 ├── beta 2 │ └── rhel 3 │ └── server 4 │ └── 7 5 │ └── x86_64 6 │ └── sat-tools 7 └── dist └── rhel └── server └── 7 ├── 7.2 │ └── x86_64 │ └── kickstart └── 7Server └── x86_64 └── os
9.2. Automatic NUMA Balancing Automatic NUMA balancing improves the performance of applications running on NUMA hardware systems. It is enabled by default on Red Hat Enterprise Linux 7 systems. An application will generally perform best when the threads of its processes are accessing memory on the same NUMA node as the threads are scheduled. Automatic NUMA balancing moves tasks (which can be threads or processes) closer to the memory they are accessing. It also moves application data to memory closer to the tasks that reference it. This is all done automatically by the kernel when automatic NUMA balancing is active. Automatic NUMA balancing uses a number of algorithms and data structures, which are only active and allocated if automatic NUMA balancing is active on the system: Periodic NUMA unmapping of process memory NUMA hinting fault Migrate-on-Fault (MoF) - moves memory to where the program using it runs task_numa_placement - moves running programs closer to their memory 9.2.1. Configuring Automatic NUMA Balancing Automatic NUMA balancing is enabled by default in Red Hat Enterprise Linux 7, and will automatically activate when booted on hardware with NUMA properties. Automatic NUMA balancing is enabled when both of the following conditions are met: # numactl --hardware shows multiple nodes # cat /proc/sys/kernel/numa_balancing shows 1 Manual NUMA tuning of applications will override automatic NUMA balancing, disabling periodic unmapping of memory, NUMA faults, migration, and automatic NUMA placement of those applications. In some cases, system-wide manual NUMA tuning is preferred. To disable automatic NUMA balancing, use the following command: To enable automatic NUMA balancing, use the following command:

Commands:
echo 0 > /proc/sys/kernel/numa_balancing
echo 1 > /proc/sys/kernel/numa_balancing
C.4. CacheLoader org.infinispan.interceptors.CacheLoaderInterceptor This component loads entries from a CacheStore into memory. Table C.6. Attributes Name Description Type Writable cacheLoaderLoads Number of entries loaded from the cache store. long No cacheLoaderMisses Number of entries that did not exist in cache store. long No stores Returns a collection of cache loader types which are configured and enabled. Collection No statisticsEnabled Enables or disables the gathering of statistics by this component. boolean Yes Table C.7. Operations Name Description Signature disableStore Disable all cache loaders of a given type, where type is a fully qualified class name of the cache loader to disable. void disableStore(String storeType) resetStatistics Resets statistics gathered by this component. void resetStatistics() 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
Chapter 1. Introduction to Ceph block devices A block is a set length of bytes in a sequence, for example, a 512-byte block of data. Combining many blocks together into a single file can be used as a storage device that you can read from and write to. Block-based storage interfaces are the most common way to store data with rotating media such as: Hard drives CD/DVD discs Floppy disks Traditional 9-track tapes The ubiquity of block device interfaces makes a virtual block device an ideal candidate for interacting with a mass data storage system like Red Hat Ceph Storage. Ceph block devices are thin-provisioned, resizable and store data striped over multiple Object Storage Devices (OSD) in a Ceph storage cluster. Ceph block devices are also known as Reliable Autonomic Distributed Object Store (RADOS) Block Devices (RBDs). Ceph block devices leverage RADOS capabilities such as: Snapshots Replication Data consistency Ceph block devices interact with OSDs by using the librbd library. Ceph block devices deliver high performance with infinite scalability to Kernel Virtual Machines (KVMs), such as Quick Emulator (QEMU), and cloud-based computing systems, like OpenStack, that rely on the libvirt and QEMU utilities to integrate with Ceph block devices. You can use the same storage cluster to operate the Ceph Object Gateway and Ceph block devices simultaneously. Important To use Ceph block devices, requires you to have access to a running Ceph storage cluster. For details on installing a Red Hat Ceph Storage cluster, see the Red Hat Ceph Storage Installation Guide .

Commands:
Kernel Administration Guide Red Hat Enterprise Linux 7 Using modules, kpatch, or kdump to manage Linux kernel in RHEL Jaroslav Klech Red Hat Customer Content Services jklech@redhat.com Sujata Kurup Red Hat Customer Content Services skurup@redhat.com Khushbu Borole Red Hat Customer Content Services kborole@redhat.com Marie Dolezelova Red Hat Customer Content Services Mark Flitter Red Hat Customer Content Services Douglas Silas Red Hat Customer Content Services Eliska Slobodova Red Hat Customer Content Services Jaromir Hradilek Red Hat Customer Content Services Maxim Svistunov Red Hat Customer Content Services Robert Kratky Red Hat Customer Content Services Stephen Wadeley Red Hat Customer Content Services Florian Nadge Red Hat Customer Content Services

Commands:
Virtualization Deployment and Administration Guide Red Hat Enterprise Linux 7 Installing, configuring, and managing virtual machines on a RHEL physical machine Jiri Herrmann Red Hat Customer Content Services jherrman@redhat.com Parth Shah Red Hat Customer Content Services Yehuda Zimmerman Red Hat Customer Content Services Laura Novich Red Hat Customer Content Services Dayle Parker Red Hat Customer Content Services Scott Radvan Red Hat Customer Content Services Tahlia Richardson Red Hat Customer Content Services

Commands:
3.7. Managing Login Permissions for Domain Users By default, domain-side access control is applied, which means that login policies for domain users are defined in the domain itself. This default behavior can be overridden so that client-side access control is used. With client-side access control, login permission are defined by local policies only. If a domain applies client-side access control, you can use the realmd system to configure basic allow or deny access rules for users from that domain. Note that these access rules either allow or deny access to all services on the system. More specific access rules must be set on a specific system resource or in the domain. To set the access rules, use the following two commands: realm deny The realm deny command simply denies access to all users within the domain. Use this command with the --all option. realm permit The realm permit command can be used to: grant access to all users by using the --all option, for example: grant access to specified users, for example: deny access to specified users by using the -x option, for example: Note that allowing access currently only works for users in primary domains, not for users in trusted domains. This is because while user logins must contain the domain name, SSSD currently cannot provide realmd with information about available child domains. Important It is safer to only allow access to specifically selected users or groups than to deny access to some, while enabling it to everyone else. Therefore, it is not recommended to allow access to all by default while only denying it to specified users with realm permit -x . Instead, Red Hat recommends to maintain a default no access policy for all users and only grant access to selected users using realm permit . For more information about the realm deny and realm permit commands, see the realm (8) man page.

Commands:
realm permit --all
realm permit user@example.com realm permit ' AD.EXAMPLE.COM\user '
realm permit -x ' AD.EXAMPLE.COM\user '
10. Virtualization vhost The new host kernel networking backend, vhost , is a fully supported feature in Red Hat Enterprise Linux 6.1. vhost provides superior throughput and latency over the userspace implementation. qcow2 The qcow2 image format now supports caching of metadata. Additionally, support is added for live snapshots using external qcow2 images. Block I/O latency improvements ioeventfd is now available, providing faster notification of block I/O. Kernel SamePage Merging (KSM) The KVM hypervisor in Red Hat Enterprise Linux 6 features Kernel SamePage Merging (KSM), allowing KVM guests to share identical memory pages. Page sharing reduces memory duplication, allowing a host with similar guest operating systems to run more efficiently. KSM in Red Hat Enterprise Linux 6.1 is Transparent HugePage aware. KSM has the ability to scan subpages inside hugepages and split them when merging is possible. Additionally, KSM enablement can now be controlled on a per-VM basis. PCI device assignment improvements PCI configuration space access is improved, enabling a broader set of PCI devices to be device-assigned to guest VMs. KVMClock Improvements In Red Hat Enterprise Linux 6.1, the Time Stamp Counter (TSC) synchronization can now be automatically detected on guest bootup or when a host CPU is hot-plugged. Additionally, the TSC synchronization frequency is adjusted after a live migration. QEMU monitor Additionally, the new drive_del command allows libvirt to safely remove a block device from a guest. General Updates and Improvements The maximum display resolution on qemu-kvm is now 2560x1600 pixels Red Hat Enterprise Linux 6.1 includes the ability to expose an emulated Intel HDA sound card to all guests. This update enables native sound support for many guests including the 64-bit version of Windows 7 QEMU char device flow control is enabled Message Signaled Interrupts (MSI) implemented for the win-virtio-blk driver A new standard interface for selecting/prioritizing the boot devices of the guest Stability improvements for live migration QEMU userspace static tracing Virtual disk online dynamic resize feature Forbid pci hot unplug of critical devices such as gpu, pci bus controller, isa bus controller

Commands:
3.5. Execution Properties The following table provides a list of execution properties as defined in org.teiid.jdbc.ExecutionProperties . These can be modified using the SET statement. Table 3.2. Execution Properties Constant Identifier String Value Description ANSI_QUOTED_IDENTIFIERS ansiQuotedIdentifiers See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . DISABLE_LOCAL_TRANSACTIONS disableLocalTxn See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . JDBC4COLUMNNAME ANDLABELSEMANTICS useJDBC4ColumnName AndLabelSemantics See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . NOEXEC See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . PROP_FETCH_SIZE fetchSize See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . PROP_PARTIAL_RESULTS_MODE partialResultsMode See Section 1.9, "Connection Properties for the Driver and Data Source Classes" and Section 3.12, "Partial Results Mode" . PROP_TXN_AUTO_WRAP autoCommitTxn See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . PROP_XML_FORMAT XMLFormat Determines the formatting of XML documents returned by XML document models. Can be one of XML_COMPACT_FORMAT or XML_TREE_FORMAT . See Section 3.7, "XML Document Formatting" for more information. PROP_XML_VALIDATION XMLValidation Determines whether XML documents returned by XML document models will be validated against their schema after processing. See Section 3.8, "XML Schema Validation" and topics on "XML SELECT" in the JBoss Data Virtualization Development Guide: Reference Material for more information. QUERYTIMEOUT QUERYTIMEOUT See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . RESULT_SET_CACHE_MODE resultSetCacheMode See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . SQL_OPTION_SHOWPLAN SHOWPLAN See Section 1.9, "Connection Properties for the Driver and Data Source Classes" . See Also: Section 3.9, "The SET Statement"

Commands:
Chapter 6. Deploying the Streams for Apache Kafka Console After you have deployed a Kafka cluster that's managed by Streams for Apache Kafka, you can deploy and connect the Streams for Apache Kafka Console to the cluster. The console facilitates the administration of Kafka clusters, providing real-time insights for monitoring, managing, and optimizing each cluster from its user interface. For more information on connecting to and using the Streams for Apache Kafka Console, see the console guide in the Streams for Apache Kafka documentation .

Commands:
Chapter 1. Using schema properties to configure custom resources Custom resources offer a flexible way to manage and fine-tune the operation of Streams for Apache Kafka components using configuration properties. This reference guide describes common configuration properties that apply to multiple custom resources, as well as the configuration properties available for each custom resource schema available with Streams for Apache Kafka. Where appropriate, expanded descriptions of properties and examples of how they are configured are provided. The properties defined for each schema provide a structured and organized way to specify configuration for the custom resources. Whether it's adjusting resource allocation or specifying access controls, the properties in the schemas allow for a granular level of configuration. For example, you can use the properties of the KafkaClusterSpec schema to specify the type of storage for a Kafka cluster or add listeners that provide secure access to Kafka brokers. Some property options within a schema may be constrained, as indicated in the property descriptions. These constraints define specific options or limitations on the values that can be assigned to those properties. Constraints ensure that the custom resources are configured with valid and appropriate values.

Commands:
Chapter 18. PersistentClaimStorage schema reference Used in: JbodStorage , KafkaClusterSpec , KafkaNodePoolSpec , ZookeeperClusterSpec The type property is a discriminator that distinguishes use of the PersistentClaimStorage type from EphemeralStorage . It must have the value persistent-claim for the type PersistentClaimStorage . Property Description type Must be persistent-claim . string size When type=persistent-claim, defines the size of the persistent volume claim (i.e 1Gi). Mandatory when type=persistent-claim. string selector Specifies a specific persistent volume to use. It contains key:value pairs representing labels for selecting such a volume. map deleteClaim Specifies if the persistent volume claim has to be deleted when the cluster is un-deployed. boolean class The storage class to use for dynamic volume allocation. string id Storage identification number. It is mandatory only for storage volumes defined in a storage of type 'jbod'. integer overrides Overrides for individual brokers. The overrides field allows to specify a different configuration for different brokers. PersistentClaimStorageOverride array

Commands:
23.4. Creating an LDIF File with Example Modification Statements Use the dsctl ldifgen mod-load command to create an LDIF file that contains update operations. This command creates the /tmp/modifications.ldif file with the statements that do the following: Create an LDIF file with 1000 ADD operations to create user entries. Modify all entries by changing their cn , uid , sn attributes. Add additional 10 user entries. Perform 100 MODRDN operations. Delete 100 entries Delete all remaining entries at the end. For further details and other options you can use to create the LDIF file, enter:

Commands:
dsctl instance_name ldifgen mod-load --parent dc=example,dc=com --num-users 1000 --create-users --mod-users 1000 --add-users 10 --del-users 100 --mod-users 1000 --modrdn-users 100 --mod-attrs cn uid sn --delete-users
dsctl instance_name ldifgen mod-load --help
Chapter 61. Kamelet Main Since Camel 3.11 A main class that is opinionated to boostrap and run Camel standalone with Kamelets (or plain YAML routes) for development and demo purposes. 61.1. Initial configuration The KameletMain is pre-configured with the following properties: camel.component.kamelet.location = classpath:/kamelets,github:apache:camel-kamelets/kamelets camel.component.rest.consumerComponentName = platform-http camel.component.rest.producerComponentName = vertx-http You can override these settings by updating the configuration in application.properties . 61.2. Automatic dependencies downloading The Kamelet Main can automatically download Kamelet YAML files from a remote location over http/https, and from github as well. The official Kamelets from the Apache Camel Kamelet Catalog is stored on github and they can be used out of the box as-is. For example a Camel route can be coded in YAML which uses the Earthquake Kamelet from the catalog, as shown below: - route: from: "kamelet:earthquake-source" steps: - unmarshal: json: {} - log: "Earthquake with magnitude USD{body[properties][mag]} at USD{body[properties][place]}" In the above example, the earthquake kamelet will be downloaded from github, and as well its required dependencies. For more information, see Kamelet Main example

Commands:
camel.component.kamelet.location = classpath:/kamelets,github:apache:camel-kamelets/kamelets camel.component.rest.consumerComponentName = platform-http camel.component.rest.producerComponentName = vertx-http
- route: from: "kamelet:earthquake-source" steps: - unmarshal: json: {} - log: "Earthquake with magnitude USD{body[properties][mag]} at USD{body[properties][place]}"
20.22. Editing a Guest Virtual Machine's XML Configuration Settings The virsh edit command enables the user to edit the domain XML configuration file of a specified guest. Running this command opens the XML file in a text editor, specified by the USDEDITOR shell parameter (set to vi by default). Example 20.50. How to edit a guest virtual machine's XML configuration settings The following example opens the XML configuration file associated with the guest1 virtual machine in your default text editor: # virsh edit guest1

Commands: