mtpti5iD/redhat-docs_dataset huggingface dataset:
7.3.2.2. Advanced tuning for XFS Before changing XFS parameters, you need to understand why the default XFS parameters are causing performance problems. This involves understanding what your application is doing, and how the file system is reacting to those operations. Observable performance problems that can be corrected or reduced by tuning are generally caused by file fragmentation or resource contention in the file system. There are different ways to address these problems, and in some cases fixing the problem will require that the application, rather than the file system configuration, be modified. If you have not been through this process previously, it is recommended that you engage your local Red Hat support engineer for advice. 7.3.2.2.1. Optimizing for a large number of files XFS imposes an arbitrary limit on the number of files that a file system can hold. In general, this limit is high enough that it will never be hit. If you know that the default limit will be insufficient ahead of time, you can increase the percentage of file system space allowed for inodes with the mkfs.xfs command. If you encounter the file limit after file system creation (usually indicated by ENOSPC errors when attempting to create a file or directory even though free space is available), you can adjust the limit with the xfs_growfs command.

Commands:
Appendix A. Using your Red Hat subscription Red Hat Connectivity Link is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Managing your subscriptions Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. In the menu bar, click Subscriptions to view and manage your subscriptions. Revised on 2025-03-12 11:42:24 UTC

Commands:
Chapter 8. Configuring JBoss EAP subsystems to work on Microsoft Azure Some JBoss EAP subsystems must be configured to work properly on cloud platforms, such as Amazon EC2 and Microsoft Azure. This is required because a JBoss EAP server is usually bound to a cloud virtual machine's private IP address, for example: 10.x.x.x , which is only visible from within the cloud platform. For certain subsystems, this address must also be mapped to a server's public IP address, which is visible from outside the cloud. 8.1. Configuring the web services subsystem to work on Microsoft Azure When a client makes a web service request using Service.create(wsdlURL, serviceName); , the user connects to the server public IP address, but is subsequently redirected to an address defined in the server configuration files in the webservices subsystem. By default, this address is USD{jboss.bind.address:127.0.0.1} , which means that on a cloud platform, the caller will be redirected to the server's private IP address and will be unable to resolve the request. The server's public IP address has to be configured in the wsdl-host element. Procedure Configure the server's public IP address in the wsdl-host element. 8.2. Configuring the messaging subsystem to work on Microsoft Azure When using messaging on a cloud platform, the connection factory that the client uses must have a connector pointing to the server's public IP address. For this reason a new connector and socket binding must be created for JBoss EAP servers running a full profile. Prerequisites JBoss EAP is running a full profile. Procedure Create the referenced http-public socket binding within the socket-binding-group . Create the new http-connector element in the messaging subsystem. Set the connectors in the connection-factory , which will be used by clients. For example, configuration of RemoteConnectionFactory as the default connection will be: 8.3. Configuring the remoting subsystem for high availability to work on Microsoft Azure If you are using JBoss EAP HA features with clustered Jakarta Enterprise Beans on a cloud platform, some extra configuration for the remoting subsystem is required to ensure Jakarta Enterprise Beans clients can receive cluster view updates. Procedure Configure client-mappings for the remoting subsystem socket binding.

Commands:
/subsystem=webservices:write-attribute(name=wsdl-host,value= <PUBLIC_IP_ADDRESS> )
/socket-binding-group=standard-sockets/remote-destination-outbound-socket-binding=http-public:add(host= <PUBLIC_IP_ADDRESS> ,port=USD{jboss.http.port:8080})
/subsystem=messaging-activemq/server=default/http-connector=http-public-connector:add(endpoint=http-acceptor,socket-binding=http-public)
/subsystem=messaging-activemq/server=default/connection-factory=RemoteConnectionFactory:write-attribute(name=connectors, value=["http-public-connector"]
/socket-binding-group=standard-sockets/socket-binding=http:write-attribute(name=client-mappings,value=[{ "destination-address" => " <PUBLIC_IP_ADDRESS> ", "destination-port" => "8080" }])
8.13. Related Information Supported versions of the SCAP Security Guide - The article lists the supported version of the SCAP Security Guide in different versions of RHEL. The OpenSCAP project page - The home page of the OpenSCAP project provides detailed information about the oscap utility and other components and projects related to SCAP. The SCAP Workbench project page - The home page of the SCAP Workbench project provides detailed information about the scap-workbench application. The SCAP Security Guide (SSG) project page - The home page of the SSG project that provides the latest security content for Red Hat Enterprise Linux. Red Hat Security Demos: Creating Customized Security Policy Content to Automate Security Compliance - A hands-on lab to get initial experience in automating security compliance using the tools that are included in Red Hat Enterprise Linux to comply with both industry standard security policies and custom security policies. If you want training or access to these lab exercises for your team, contact your Red Hat account team for additional details. Red Hat Security Demos: Defend Yourself with RHEL Security Technologies - A hands-on lab to learn how to implement security at all levels of your RHEL system, using the key security technologies available to you in Red Hat Enterprise Linux, including OpenSCAP. If you want training or access to these lab exercises for your team, contact your Red Hat account team for additional details. National Institute of Standards and Technology (NIST) SCAP page - This page represents a vast collection of SCAP-related materials, including SCAP publications, specifications, and the SCAP Validation Program. National Vulnerability Database (NVD) - This page represents the largest repository of SCAP content and other SCAP standards-based vulnerability management data. Red Hat OVAL content repository - This is a repository containing OVAL definitions for vulnerabilities of Red Hat Enterprise Linux systems. This is the recommended source of vulnerability content. MITRE CVE - This is a database of publicly known security vulnerabilities provided by the MITRE corporation. For RHEL, using OVAL CVE content provided by Red Hat is recommended. MITRE OVAL - This page represents an OVAL-related project provided by the MITRE corporation. Among other OVAL-related information, these pages contain the latest version of the OVAL language and a repository of OVAL content with thousands of OVAL definitions. Note that for scanning RHEL, using OVAL CVE content provided by Red Hat is recommended. Red Hat Satellite documentation - This set of guides describes, among other topics, how to maintain system security on multiple systems by using OpenSCAP.

Commands:
Chapter 11. Customize plans When you have completed this section you will have customized an application plan for a specific developer. Application plans are a good way to apply standard policies for different segments of your developer community. However, you always have the flexibility to customize the standard plans for any individual developer with unique requirements. Once a plan is customized, you lose the link to the original plan. If you make changes to the original plan, the custom plan does not inherit any of those changes. So you should use this customization feature sparingly, before you become overwhelmed with too many custom plans which you cannot manage effectively. A developer wants to increase their current limits without upgrading to the pricing tier as the current billing period is already under way. A customization could be a good way to handle this situation by enabling the increase in limits and charging only the variable costs incurred. This would also help encourage an upgrade for the following billing month. 11.1. Choose the account To view the details page for the developer Account you are interested in: Navigate to Audience > Accounts > Listing Choose the Developer account 11.2. Select the application Select the application whose plan you wish to customize. 11.3. Customize the application plan Select the option to "customize". This provides the page where all the plan elements can be customized for the application owned by this account. 11.3.1. More information Before you take the step to customize plans, always consider first if you are not better off with a new standard plan (which can be hidden from display in the Developer Portal). Then you would just change to the standard plan and so gain the benefit of reuse if this applies to more than one of your developer partners.

Commands:
B.10. References For more information about tracepoints and the GFS2 glocks file, see the following resources: For information on glock internal locking rules, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/filesystems/gfs2-glocks.rst . For information on event tracing, see https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/trace/events.rst .` For information on the trace-cmd utility, see http://lwn.net/Articles/341902/ .

Commands:
Chapter 54. CruiseControlTemplate schema reference Used in: CruiseControlSpec Property Description deployment Template for Cruise Control Deployment . DeploymentTemplate pod Template for Cruise Control Pods . PodTemplate apiService Template for Cruise Control API Service . InternalServiceTemplate podDisruptionBudget Template for Cruise Control PodDisruptionBudget . PodDisruptionBudgetTemplate cruiseControlContainer Template for the Cruise Control container. ContainerTemplate tlsSidecarContainer The tlsSidecarContainer property has been deprecated. Template for the Cruise Control TLS sidecar container. ContainerTemplate serviceAccount Template for the Cruise Control service account. ResourceTemplate

Commands:
Chapter 6. The ext3 File System The default file system is the journaling ext3 file system. 6.1. Features of ext3 The ext3 file system is essentially an enhanced version of the ext2 file system. These improvements provide the following advantages: Availability After an unexpected power failure or system crash (also called an unclean system shutdown ), each mounted ext2 file system on the machine must be checked for consistency by the e2fsck program. This is a time-consuming process that can delay system boot time significantly, especially with large volumes containing a large number of files. During this time, any data on the volumes is unreachable. The journaling provided by the ext3 file system means that this sort of file system check is no longer necessary after an unclean system shutdown. The only time a consistency check occurs using ext3 is in certain rare hardware failure cases, such as hard drive failures. The time to recover an ext3 file system after an unclean system shutdown does not depend on the size of the file system or the number of files; rather, it depends on the size of the journal used to maintain consistency. The default journal size takes about a second to recover, depending on the speed of the hardware. Data Integrity The ext3 file system provides stronger data integrity in the event that an unclean system shutdown occurs. The ext3 file system allows you to choose the type and level of protection that your data receives. By default, the ext3 volumes are configured to keep a high level of data consistency with regard to the state of the file system. Speed Despite writing some data more than once, ext3 has a higher throughput in most cases than ext2 because ext3's journaling optimizes hard drive head motion. You can choose from three journaling modes to optimize speed, but doing so means trade-offs in regards to data integrity. Easy Transition It is easy to migrate from ext2 to ext3 and gain the benefits of a robust journaling file system without reformatting. Refer to Section 6.3, "Converting to an ext3 File System" for more on how to perform this task. The following sections walk you through the steps for creating and tuning ext3 partitions. For ext2 partitions, skip the partitioning and formating sections below and go directly to Section 6.3, "Converting to an ext3 File System" .

Commands:
7.280. xorg-x11-drv-evdev 7.280.1. RHBA-2013:0297 - xorg-x11-drv-evdev bug fix and enhancement update Updated xorg-x11-drv-evdev packages that fix several bugs add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-evdev packages contain the X.Org X11 input drivers for keyboards and mice. Note The xorg-x11-drv-evdev package has been upgraded to upstream version 2.7.3, which provides a number of bug fixes and enhancements over the version. (BZ#835225) All users of xorg-x11-drv-evdev are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
15.3.2. Installing from a Hard Drive The Select Partition screen applies only if you are installing from a disk partition (that is, you selected Hard Drive in the Installation Method dialog). This dialog allows you to name the disk partition and directory from which you are installing Red Hat Enterprise Linux. If you used the repo=hd boot option, you already specified a partition. Figure 15.5. Selecting Partition Dialog for Hard Drive Installation Select the partition containing the ISO files from the list of available partitions. Internal IDE, SATA, SCSI, and USB drive device names begin with /dev/sd . Each individual drive has its own letter, for example /dev/sda . Each partition on a drive is numbered, for example /dev/sda1 . Also specify the Directory holding images . Enter the full directory path from the drive that contains the ISO image files. The following table shows some examples of how to enter this information: Table 15.1. Location of ISO images for different partition types Partition type Volume Original path to files Directory to use VFAT D:\ D:\Downloads\RHEL6.9 /Downloads/RHEL6.9 ext2, ext3, ext4 /home /home/user1/RHEL6.9 /user1/RHEL6.9 If the ISO images are in the root (top-level) directory of a partition, enter a / . If the ISO images are located in a subdirectory of a mounted partition, enter the name of the directory holding the ISO images within that partition. For example, if the partition on which the ISO images is normally mounted as /home/ , and the images are in /home/new/ , you would enter /new/ . Important An entry without a leading slash may cause the installation to fail. Select OK to continue. Proceed with Chapter 16, Installing Using Anaconda .

Commands:
B.16. Unable to connect to server at 'host:16509': Connection refused ... error: failed to connect to the hypervisor Symptom While libvirtd should listen on TCP ports for connections, the connections fail: The libvirt daemon is not listening on TCP ports even after changing configuration in /etc/libvirt/libvirtd.conf : However, the TCP ports for libvirt are still not open after changing configuration: Investigation The libvirt daemon was started without the --listen option. Verify this by running this command: The output does not contain the --listen option. Solution Start the daemon with the --listen option. To do this, modify the /etc/sysconfig/libvirtd file and uncomment the following line: Then restart the libvirtd service with this command:

Commands:
virsh -c qemu+tcp://host/system error: unable to connect to server at 'host:16509': Connection refused error: failed to connect to the hypervisor
grep listen_ /etc/libvirt/libvirtd.conf listen_tls = 1 listen_tcp = 1 listen_addr = "0.0.0.0"
netstat -lntp | grep libvirtd #
ps aux | grep libvirtd root 27314 0.0 0.0 1000920 18304 ? Sl Feb16 1:19 libvirtd --daemon
#LIBVIRTD_ARGS="--listen"
/etc/init.d/libvirtd restart
1.2.8. Additional Resources A detailed description of all supported features is beyond the scope of this book. For more information, see the resources listed below. Installed Documentation svn help - The output of the svn help command provides detailed information on the svn usage. svnadmin help - The output of the svnadmin help command provides detailed information on the svnadmin usage. Online Documentation Version Control with Subversion - The official Subversion website refers to the Version Control with Subversion manual, which provides an in-depth description of Subversion, its administration and its usage.

Commands:
Chapter 45. Uploading spreadsheet decision tables to Business Central After you define your rules in an external XLS or XLSX spreadsheet of decision tables, you can upload the spreadsheet file to your project in Business Central. Important You should typically upload only one spreadsheet of decision tables, containing all necessary RuleTable definitions, per rule package in Business Central. You can upload separate decision table spreadsheets for separate packages, but uploading multiple spreadsheets in the same package can cause compilation errors from conflicting RuleSet or RuleTable attributes and is therefore not recommended. Procedure In Business Central, go to Menu Design Projects and click the project name. Click Add Asset Decision Table (Spreadsheet) . Enter an informative Decision Table name and select the appropriate Package . Click the Choose File icon, and select the spreadsheet. Click Ok to upload. In the decision tables designer, click Validate in the upper-right toolbar to validate the table. If the table validation fails, open the XLS or XLSX file and address any syntax errors. For syntax help, see Chapter 44, Defining spreadsheet decision tables . You can upload a new version of the decision table or download the current version: Figure 45.1. Uploaded decision table options

Commands:
B.97. tomcat6 B.97.1. RHSA-2011:0335 - Important: tomcat6 security and bug fix update Updated tomcat6 packages that fix two security issues and one bug are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. 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. Apache Tomcat is a servlet container for the Java Servlet and JavaServer Pages (JSP) technologies. CVE-2010-4476 A denial of service flaw was found in the way certain strings were converted to Double objects. A remote attacker could use this flaw to cause Tomcat to hang via a specially-crafted HTTP request. CVE-2011-0534 A flaw was found in the Tomcat NIO (Non-Blocking I/O) connector. A remote attacker could use this flaw to cause a denial of service (out-of-memory condition) via a specially-crafted request containing a large NIO buffer size request value. Bug Fix BZ# 676922 A bug in the "tomcat6" init script prevented additional Tomcat instances from starting. As well, running "service tomcat6 start" caused configuration options applied from "/etc/sysconfig/tomcat6" to be overwritten with those from "/etc/tomcat6/tomcat6.conf". With this update, multiple instances of Tomcat run as expected. Users of Tomcat should upgrade to these updated packages, which contain backported patches to correct these issues. Tomcat must be restarted for this update to take effect.

Commands:
Chapter 8. Catalog selection by priority When multiple catalogs provide the same package, you can resolve ambiguities by specifying the priority in the custom resource (CR) of each catalog. If unspecified, catalogs have a default priority value of 0 . The priority can be any positive or negative 32-bit integer. Note During bundle resolution, catalogs with higher priority values are selected over catalogs with lower priority values. Bundles that are not deprecated are prioritized over bundles that are deprecated. If multiple bundles exist in catalogs with the same priority and the catalog selection is ambiguous, an error is printed. Example cluster catalog CR with a higher priority apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: high-priority-catalog spec: priority: 1000 source: type: Image image: ref: quay.io/example/higher-priority-catalog:latest Example cluster catalog CR with a lower priority apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: lower-priority-catalog spec: priority: 10 source: type: Image image: ref: quay.io/example/lower-priority-catalog:latest

Commands:
apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: high-priority-catalog spec: priority: 1000 source: type: Image image: ref: quay.io/example/higher-priority-catalog:latest
apiVersion: olm.operatorframework.io/v1 kind: ClusterCatalog metadata: name: lower-priority-catalog spec: priority: 10 source: type: Image image: ref: quay.io/example/lower-priority-catalog:latest
9.2. IP Virtual Server (IPVS) Red Hat Enterprise Linux 6.5 introduces a new sync message protocol format. This new format is provided to prevent interruptions to business services caused by persistent connections on backup server nodes timing out prematurely, causing inconsistent state in the case of failover to a backup server node. This new format is not compatible with versions of Red Hat Enterprise Linux 6.4 or earlier, or kernel versions prior to kernel-2.6.32-406.el6. Upgrade backup nodes before upgrading the master node. To continue using the old format for sync messages, for example if you need to upgrade the master node prior to the backup nodes, set the value of /proc/sys/net/ipv4/vs/sync_version to 0 .

Commands:
4.95. ipa-pki-theme 4.95.1. RHBA-2011:1754 - ipa-pki-theme bug fix update Updated ipa-pki-theme packages which fix this bug are now available for Red Hat Enterprise Linux 6. The ipa-pki-theme packages provide Red Hat Identity Management theme components for PKI packages. Certificate System (CS) manages enterprise Public Key Infrastructure (PKI) deployments and requires a theme for the specific type of PKI deployment with which it is used. This package makes a Red Hat Identity Management theme available for CS, and therefore makes it possible for users of Red Hat Enterprise Linux 6 to use CS as a part of Red Hat Identity Management deployments. Bug Fix BZ# 712931 IPA (Identity, Policy and Audit) is an identity and access management system. Prior to this update, Certificate System (CS), which is implemented in pki-core, required multiple ports to be open in a firewall for IPA to work. The number of open ports required has been reduced, and support for a proxy using Apache JServ Protocol (AJP) ports has been added, by enhancements made in pki-core. With this update, ipa-pki-theme has been changed to make use of the updates to CS, including adding the proxy-ipa.conf configuration file, and fixing broken links in certain user interface files. As a result, it is now possible for ipa-pki-theme to support running CS behind a proxy Apache server. Important This theme is mutually exclusive with the PKI themes for other types of PKI deployments, such as dogtag-pki-theme for Dogtag Certificate System deployments and redhat-pki-theme for Red Hat Certificate System deployments. (BZ# 643543 ) All users of ipa-pki-theme are advised to upgrade to these updated packages, which fixes this bug.

Commands: