mtpti5iD/redhat-docs_dataset huggingface dataset:
F.10. Hash Space Allocation F.10.1. About Hash Space Allocation Red Hat JBoss Data Grid is responsible for allocating a portion of the total available hash space to each node. During subsequent operations that must store an entry, JBoss Data Grid creates a hash of the relevant key and stores the entry on the node that owns that portion of hash space. Report a bug F.10.2. Locating a Key in the Hash Space Red Hat JBoss Data Grid always uses an algorithm to locate a key in the hash space. As a result, the node that stores the key is never manually specified. This scheme allows any node to know which node owns a particular key without such ownership information being distributed. This scheme reduces the amount of overhead and, more importantly, improves redundancy because the ownership information does not need to be replicated in case of node failure. Report a bug F.10.3. Requesting a Full Byte Array How can I request the Red Hat JBoss Data Grid return a full byte array instead of partial byte array contents? As a default, JBoss Data Grid only partially prints byte arrays to logs to avoid unnecessarily printing large byte arrays. This occurs when either: JBoss Data Grid caches are configured for lazy deserialization. Lazy deserialization is not available in JBoss Data Grid's Remote Client-Server mode. A Memcached or Hot Rod server is run. In such cases, only the first ten positions of the byte array display in the logs. To display the complete contents of the byte array in the logs, pass the -Dinfinispan.arrays.debug=true system property at start up. Example F.1. Partial Byte Array Log Report a bug

Commands:
2010-04-14 15:46:09,342 TRACE [ReadCommittedEntry] (HotRodWorker-1-1) Updating entry (key=CacheKey{data=ByteArray{size=19, hashCode=1b3278a, array=[107, 45, 116, 101, 115, 116, 82, 101, 112, 108, ..]}} removed=false valid=true changed=true created=true value=CacheValue{data=ByteArray{size=19, array=[118, 45, 116, 101, 115, 116, 82, 101, 112, 108, ..]}, version=281483566645249}] And here's a log message where the full byte array is shown: 2010-04-14 15:45:00,723 TRACE [ReadCommittedEntry] (Incoming-2,Infinispan-Cluster,eq-6834) Updating entry (key=CacheKey{data=ByteArray{size=19, hashCode=6cc2a4, array=[107, 45, 116, 101, 115, 116, 82, 101, 112, 108, 105, 99, 97, 116, 101, 100, 80, 117, 116]}} removed=false valid=true changed=true created=true value=CacheValue{data=ByteArray{size=19, array=[118, 45, 116, 101, 115, 116, 82, 101, 112, 108, 105, 99, 97, 116, 101, 100, 80, 117, 116]}, version=281483566645249}]
16.7.2. Application Access The console user is also allowed access to certain programs with a file bearing the command name in the /etc/security/console.apps/ directory. One notable group of applications the console user has access to are three programs which shut off or reboot the system. These are: /sbin/halt /sbin/reboot /sbin/poweroff Because these are PAM-aware applications, they call the pam_console.so module as a requirement for use. For more information, refer to the Section 16.8.1, "Installed Documentation" .

Commands:
39.4. Migrating over SSL To encrypt the data transmission between LDAP and IdM during a migration: Store the certificate of the CA, that issued the remote LDAP server's certificate, in a file on the IdM server. For example: /etc/ipa/remote.crt . Follow the steps described in Section 39.3, "Migrating an LDAP Server to Identity Management" . However for an encrypted LDAP connection during the migration, use the ldaps protocol in the URL and pass the --ca-cert-file option to the command. For example:

Commands:
ipa migrate-ds --ca-cert-file= /etc/ipa/remote.crt ldaps:// ldap.example.com :636
Chapter 5. Removed features This section describes features and functionality that have been removed from AMQ Broker. Access to the root of the AMQ Broker web server In versions of AMQ Broker, opening the root URL of the AMQ Broker web server, for example, http://localhost:8161/ , in a browser window displays a landing page. The landing page has links to AMQ Management Console and AMQ Broker documentation. In 7.11, all static HTML content is removed from AMQ Broker. Therefore, if you open the root URL of the AMQ Broker web server, a landing page is not displayed. Instead, your browser session is automatically redirected to AMQ Management Console.

Commands:
Chapter 5. Upgrading the Red Hat build of Keycloak Admin Client Be sure that you upgrade the Red Hat build of Keycloak server before you upgrade the admin-client. Earlier versions of the admin-client might work with later versions of Red Hat build of Keycloak server, but earlier versions of Red Hat build of Keycloak server might not work with later versions of the admin-client. Therefore, use the admin-client version that matches the current Red Hat build of Keycloak server version.

Commands:
Chapter 2. Support policy for Red Hat build of OpenJDK Red Hat will support select major versions of Red Hat build of OpenJDK in its products. For consistency, these are the same versions that Oracle designates as long-term support (LTS) for the Oracle JDK. A major version of Red Hat build of OpenJDK will be supported for a minimum of six years from the time that version is first introduced. For more information, see the OpenJDK Life Cycle and Support Policy . Note RHEL 6 reached the end of life in November 2020. Because of this, Red Hat build of OpenJDK is not supporting RHEL 6 as a supported configuration. Important Full support for Red Hat build of OpenJDK 11 ends on 31 October 2024. For more information, see Red Hat build of OpenJDK 11 - End of full support .

Commands:
3.14. Configuring Virtual Machines in a Clustered Environment When you configure your cluster with virtual machine resources, you should use the rgmanager tools to start and stop the virtual machines. Using virsh to start the machine can result in the virtual machine running in more than one place, which can cause data corruption in the virtual machine. To reduce the chances of administrators accidentally "double-starting" virtual machines by using both cluster and non-cluster tools in a clustered environment, you can configure your system by storing the virtual machine configuration files in a non-default location. Storing the virtual machine configuration files somewhere other than their default location makes it more difficult to accidentally start a virtual machine using virsh , as the configuration file will be unknown out of the box to virsh . The non-default location for virtual machine configuration files may be anywhere. The advantage of using an NFS share or a shared GFS2 file system is that the administrator does not need to keep the configuration files in sync across the cluster members. However, it is also permissible to use a local directory as long as the administrator keeps the contents synchronized somehow cluster-wide. In the cluster configuration, virtual machines may reference this non-default location by using the path attribute of a virtual machine resource. Note that the path attribute is a directory or set of directories separated by the colon ':' character, not a path to a specific file. Warning The libvirt-guests service should be disabled on all the nodes that are running rgmanager . If a virtual machine autostarts or resumes, this can result in the virtual machine running in more than one place, which can cause data corruption in the virtual machine. For more information on the attributes of a virtual machine resources, see Table B.26, "Virtual Machine ( vm Resource)" .

Commands:
10.3. Implementing the Incident Response Plan Once a plan of action is created, it must be agreed upon and actively implemented. Any aspect of the plan that is questioned during an active implementation can result in poor response time and downtime in the event of a breach. This is where practice exercises become invaluable. Unless something is brought to attention before the plan is actively set in production, the implementation should be agreed upon by all directly connected parties and executed with confidence. If a breach is detected and the CERT team is present for quick reaction, potential responses can vary. The team can decide to disable the network connections, disconnect the affected systems, patch the exploit, and then reconnect quickly without further, potential complications. The team can also watch the perpetrators and track their actions. The team could even redirect the perpetrator to a honeypot - a system or segment of a network containing intentionally false data - used to track incursion safely and without disruption to production resources. Responding to an incident should also be accompanied by information gathering whenever possible. Running processes, network connections, files, directories, and more should be actively audited in real-time. Having a snapshot of production resources for comparison can be helpful in tracking rogue services or processes. CERT members and in-house experts are great resources in tracking such anomalies in a system. System administrators know what processes should and should not appear when running top or ps . Network administrators are aware of what normal network traffic should look like when running snort or even tcpdump . These team members should know their systems and should be able to spot an anomaly more quickly than someone unfamiliar with the infrastructure.

Commands:
Chapter 1. Operators overview Operators are among the most important components of OpenShift Container Platform. They are the preferred method of packaging, deploying, and managing services on the control plane. They can also provide advantages to applications that users run. Operators integrate with Kubernetes APIs and CLI tools such as kubectl and the OpenShift CLI ( oc ). They provide the means of monitoring applications, performing health checks, managing over-the-air (OTA) updates, and ensuring that applications remain in your specified state. Operators are designed specifically for Kubernetes-native applications to implement and automate common Day 1 operations, such as installation and configuration. Operators can also automate Day 2 operations, such as autoscaling up or down and creating backups. All of these activities are directed by a piece of software running on your cluster. While both follow similar Operator concepts and goals, Operators in OpenShift Container Platform are managed by two different systems, depending on their purpose: Cluster Operators Managed by the Cluster Version Operator (CVO) and installed by default to perform cluster functions. Optional add-on Operators Managed by Operator Lifecycle Manager (OLM) and can be made accessible for users to run in their applications. Also known as OLM-based Operators . 1.1. For developers As an Operator author, you can perform the following development tasks for OLM-based Operators: Install Operator SDK CLI . Create Go-based Operators , Ansible-based Operators , Java-based Operators , and Helm-based Operators . Use Operator SDK to build, test, and deploy an Operator . Install and subscribe an Operator to your namespace . Create an application from an installed Operator through the web console . Additional resources Machine deletion lifecycle hook examples for Operator developers 1.2. For administrators As a cluster administrator, you can perform the following administrative tasks for OLM-based Operators: Manage custom catalogs . Allow non-cluster administrators to install Operators . Install an Operator from OperatorHub . View Operator status . Manage Operator conditions . Upgrade installed Operators . Delete installed Operators . Configure proxy support . Using Operator Lifecycle Manager in disconnected environments . For information about the cluster Operators that Red Hat provides, see Cluster Operators reference . 1.3. steps To understand more about Operators, see What are Operators?

Commands:
5.6. Adding Bricks to Volumes Click Add Bricks to add bricks to your volume. A brick is the basic unit of storage, represented by an export directory on a server in the storage cluster. You can expand or shrink your cluster by adding new bricks or deleting existing bricks. Figure 5.5. Add Bricks Enter the path for the brick and click OK . In the Allow Access From field, specify volume access control as a comma-separated list of IP addresses or hostnames. By default, an asterisk (*) is used as a wildcard to specify ranges of addresses such as IP addresses or hostnames. You need to use IP-based authentication for Gluster exports. Click OK to create the volume. The new volume is added and it appears on the Volumes tab. You can reuse a brick by selecting Allow bricks in root partition and reuse the bricks by clearing xattrs You can create a storage domain using the optimized volume and manage it using Red Hat Virtualization Manager.

Commands:
Chapter 1. Red Hat Ansible Automation Platform installation overview The Red Hat Ansible Automation Platform installation program offers you flexibility, allowing you to install Ansible Automation Platform using a number of supported installation scenarios. Regardless of the installation scenario you choose, installing Ansible Automation Platform involves the following steps: Editing the Red Hat Ansible Automation Platform installer inventory file The Ansible Automation Platform installer inventory file allows you to specify your installation scenario and describe host deployments to Ansible. The examples provided in this document show the parameter specifications needed to install that scenario for your deployment. Running the Red Hat Ansible Automation Platform installer setup script The setup script installs your Private Automation Hub using the required parameters defined in the inventory file. Verifying automation controller installation After installing Ansible Automation Platform, you can verify that the installation has been successful by logging in to the automation controller. Verifying automation hub installation After installing Ansible Automation Platform, you can verify that the installation has been successful by logging in to the automation hub. Post-installation steps After successful installation, you can begin using the features of Ansible Automation Platform. Additional resources For more information about the supported installation scenarios, see the Red Hat Ansible Automation Platform Planning Guide . 1.1. Prerequisites You chose and obtained a platform installer from the Red Hat Ansible Automation Platform Product Software . You are installing on a machine that meets base system requirements. You have updated all of the packages to the recent version of your RHEL nodes. Warning You may experience errors if you do not fully upgrade your RHEL nodes prior to your Ansible Automation Platform installation. You have created a Red Hat Registry Service Account, using the instructions in the Creating Registry Service Accounts guide . Additional resources For more information about obtaining a platform installer or system requirements, refer to the Red Hat Ansible Automation Platform system requirements in the Red Hat Ansible Automation Platform Planning Guide .

Commands:
function::substr Name function::substr - Returns a substring. Synopsis Arguments str The string to take a substring from start Starting position. 0 = start of the string. length Length of string to return. General Syntax substr:string (str:string, start:long, stop:long) Description Returns the substring of the up to the given length starting at the given start position and ending at given stop position.

Commands:
function substr:string(str:string,start:long,length:long)
E.2.12. /proc/ioports The output of /proc/ioports provides a list of currently registered port regions used for input or output communication with a device. This file can be quite long. The following is a partial listing: The first column gives the I/O port address range reserved for the device listed in the second column.

Commands:
0000-001f : dma1 0020-003f : pic1 0040-005f : timer 0060-006f : keyboard 0070-007f : rtc 0080-008f : dma page reg 00a0-00bf : pic2 00c0-00df : dma2 00f0-00ff : fpu 0170-0177 : ide1 01f0-01f7 : ide0 02f8-02ff : serial(auto) 0376-0376 : ide1 03c0-03df : vga+ 03f6-03f6 : ide0 03f8-03ff : serial(auto) 0cf8-0cff : PCI conf1 d000-dfff : PCI Bus #01 e000-e00f : VIA Technologies, Inc. Bus Master IDE e000-e007 : ide0 e008-e00f : ide1 e800-e87f : Digital Equipment Corporation DECchip 21140 [FasterNet] e800-e87f : tulip
B.90.2. RHSA-2011:0328 - Moderate: subversion security update Updated subversion packages that fix one security issue are now available for Red Hat Enterprise Linux 6. 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. Subversion (SVN) is a concurrent version control system which enables one or more users to collaborate in developing and maintaining a hierarchy of files and directories while keeping a history of all changes. The mod_dav_svn module is used with the Apache HTTP Server to allow access to Subversion repositories via HTTP. CVE-2011-0715 A NULL pointer dereference flaw was found in the way the mod_dav_svn module processed certain requests to lock working copy paths in a repository. A remote attacker could issue a lock request that could cause the httpd process serving the request to crash. Red Hat would like to thank Hyrum Wright of the Apache Subversion project for reporting this issue. Upstream acknowledges Philip Martin, WANdisco, Inc. as the original reporter. All Subversion users should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing the updated packages, you must restart the httpd daemon, if you are using mod_dav_svn, for the update to take effect.

Commands:
15.16. Importing the Replication Changelog from an LDIF-formatted Changelog Dump Complete this procedure to import an LDIF-formatted replication changelog dump into Directory Server. Prerequisites Replication is enabled on the Directory Server instance. The changelog dump has been created as described in Section 15.15, "Exporting the Replication Changelog" . Procedure To import the changelog dump from the /tmp/changelog.ldif file, enter: Note that the dirsrv user requires permissions to read the specified file.

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com replication restore-changelog from-ldif /tmp/changelog.ldif
Chapter 14. Samba Samba is an open source implementation of the Server Message Block (SMB) protocol. It allows the networking of Microsoft Windows (R), Linux, UNIX, and other operating systems together, enabling access to Windows-based file and printer shares. Samba's use of SMB allows it to appear as a Windows server to Windows clients. 14.1. Introduction to Samba The third major release of Samba, version 3.0.0, introduced numerous improvements from prior versions, including: The ability to join an Active Directory domain by means of LDAP and Kerberos Built in Unicode support for internationalization Support for Microsoft Windows XP Professional client connections to Samba servers without needing local registry hacking Two new documents developed by the Samba.org team, which include a 400+ page reference manual, and a 300+ page implementation and integration manual. For more information about these published titles, refer to Section 14.9.3, "Related Books" . 14.1.1. Samba Features Samba is a powerful and versatile server application. Even seasoned system administrators must know its abilities and limitations before attempting installation and configuration. What Samba can do: Serve directory trees and printers to Linux, UNIX, and Windows clients Assist in network browsing (with or without NetBIOS) Authenticate Windows domain logins Provide Windows Internet Name Service (WINS) name server resolution Act as a Windows NT (R)-style Primary Domain Controller (PDC) Act as a Backup Domain Controller (BDC) for a Samba-based PDC Act as an Active Directory domain member server Join a Windows NT/2000/2003 PDC What Samba cannot do: Act as a BDC for a Windows PDC (and vice versa) Act as an Active Directory domain controller

Commands:
Chapter 10. Modifying printer settings In GNOME, you can modify printer settings using the Settings application. Prerequisites You have started Settings for setting up printing by following the procedure Accessing printer settings in GNOME 10.1. Displaying and modifying printer's details To maintain a configuration of a printer, use the Settings application: Procedure Click the settings (⚙\ufe0f) button on the right to display a settings menu for the selected printer: Click Printer Details to display and modify selected printer's settings: In this menu, you can select the following actions: Search for Drivers GNOME Control Center communicates with PackageKit that searches for a suitable driver suitable in available repositories. Select from Database This option enables you to select a suitable driver from databases that have already been installed on the system. Install PPD File This option enables you to select from a list of available postscript printer description (PPD) files that can be used as a driver for your printer. 10.2. Setting the default printer You can set the selected printer as the default printer. Procedure Click the settings (⚙\ufe0f) button on the right to display a settings menu for the selected printer: Click Use Printer by Default to set the selected printer as the default printer: 10.3. Setting printing options Procedure Click the settings (⚙\ufe0f) button on the right to display a settings menu for the selected printer: Click Printing Options . 10.4. Removing a printer You can remove a printer using the Settings application. Procedure Click the settings (⚙\ufe0f) button on the right to display a settings menu for the selected printer: Click Remove Printer to remove the selected printer:

Commands:
14.13.5. Configuring Virtual CPU Affinity To configure the affinity of virtual CPUs with physical CPUs: The domain-id parameter is the guest virtual machine's ID number or name. The vcpu parameter denotes the number of virtualized CPUs allocated to the guest virtual machine.The vcpu parameter must be provided. The cpulist parameter is a list of physical CPU identifier numbers separated by commas. The cpulist parameter determines which physical CPUs the VCPUs can run on. Additional parameters such as --config affect the boot, whereas --live affects the running domain, and --current affects the current domain.

Commands:
virsh vcpupin domain-id vcpu cpulist
10.5.9. MPM Specific Server-Pool Directives As explained in Section 10.2.1.2, "Server-Pool Size Regulation" , the responsibility for managing characteristics of the server-pool falls to a module group called MPMs under Apache HTTP Server 2.0. The characteristics of the server-pool differ depending upon which MPM is used. For this reason, an IfModule container is necessary to define the server-pool for the MPM in use. By default, Apache HTTP Server 2.0 defines the server-pool for both the prefork and worker MPMs. The following section list directives found within the MPM-specific server-pool containers. 10.5.9.1. StartServers The StartServers directive sets how many server processes are created upon startup. Since the Web server dynamically kills and creates server processes based on traffic load, it is not necessary to change this parameter. The Web server is set to start 8 server processes at startup for the prefork MPM and 2 for the worker MPM.

Commands: