mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Global File System 2 The Red Hat Global File System 2 (GFS2) is a native file system that interfaces directly with the Linux kernel file system interface (VFS layer). When implemented as a cluster file system, GFS2 employs distributed metadata and multiple journals. GFS2 is based on 64-bit architecture, which can theoretically accommodate an 8 exabyte file system. However, the current supported maximum size of a GFS2 file system is 100 TB. If a system requires GFS2 file systems larger than 100 TB, contact your Red Hat service representative. When determining the size of a file system, consider its recovery needs. Running the fsck command on a very large file system can take a long time and consume a large amount of memory. Additionally, in the event of a disk or disk-subsystem failure, recovery time is limited by the speed of backup media. When configured in a Red Hat Cluster Suite, Red Hat GFS2 nodes can be configured and managed with Red Hat Cluster Suite configuration and management tools. Red Hat GFS2 then provides data sharing among GFS2 nodes in a Red Hat cluster, with a single, consistent view of the file system namespace across the GFS2 nodes. This allows processes on different nodes to share GFS2 files in the same way that processes on the same node can share files on a local file system, with no discernible difference. For information about the Red Hat Cluster Suite, see Red Hat's Cluster Administration guide. A GFS2 must be built on a logical volume (created with LVM) that is a linear or mirrored volume. Logical volumes created with LVM in a Red Hat Cluster suite are managed with CLVM (a cluster-wide implementation of LVM), enabled by the CLVM daemon clvmd , and running in a Red Hat Cluster Suite cluster. The daemon makes it possible to use LVM2 to manage logical volumes across a cluster, allowing all nodes in the cluster to share the logical volumes. For information on the Logical Volume Manager, see Red Hat's Logical Volume Manager Administration guide. The gfs2.ko kernel module implements the GFS2 file system and is loaded on GFS2 cluster nodes. For comprehensive information on the creation and configuration of GFS2 file systems in clustered and non-clustered storage, see Red Hat's Global File System 2 guide.

Commands:
Chapter 4. Advisories related to this release The following advisories are issued to bug fixes and CVE fixes included in this release: RHSA-2022:7008 RHSA-2022:7009 RHSA-2022:7010 RHSA-2022:7011 RHSA-2022:7012 RHSA-2022:7013 RHSA-2022:7052 RHSA-2022:7054 Revised on 2024-05-09 16:47:05 UTC

Commands:
17.4. Displaying Volume Information You can display information about a specific volume, or all volumes, as needed, using the following command: # gluster volume info VOLNAME For example, to display information about test-volume :

Commands:
gluster volume info test-volume Volume Name: test-volume Type: Distribute Status: Created Number of Bricks: 4 Bricks: Brick1: server1:/rhgs/brick1 Brick2: server2:/rhgs/brick2 Brick3: server3:/rhgs/brick3 Brick4: server4:/rhgs/brick4
Chapter 5. Network connections 5.1. Connection URLs Connection URLs encode the information used to establish new connections. Connection URL syntax Scheme - The connection transport, either amqp for unencrypted TCP or amqps for TCP with SSL/TLS encryption. Host - The remote network host. The value can be a hostname or a numeric IP address. IPv6 addresses must be enclosed in square brackets. Port - The remote network port. This value is optional. The default value is 5672 for the amqp scheme and 5671 for the amqps scheme. Connection URL examples

Commands:
scheme://host[:port]
amqps://example.com amqps://example.net:56720 amqp://127.0.0.1 amqp://[::1]:2000
Chapter 4. Tools for application migration Before you migrate your applications from Red Hat build of OpenJDK 8 to Red Hat build of OpenJDK 11, you can use tools to test the suitability of your application to run on Red Hat build of OpenJDK 11. You can use the following steps to enhance your testing process: Update third-party libraries. Compile your application code. Run jdeps on your application's code. Use the migration toolkit for applications (MTA) tool to migrate Java applications from Red Hat build of OpenJDK 8 to Red Hat build of OpenJDK 11. Additional resources For more information about the MTA tool, see the Introduction to the Migration Toolkit for Applications guide.

Commands:
Chapter 31. General Updates The TAB key does not expand USDPWD by default When working in CLI in Red Hat Enterprise Linux 6, pressing the TAB key expanded USDPWD/ to the current directory. In Red Hat Enterprise Linux 7, CLI does not have the same behavior. Users can achieve this behavior by putting the following lines into the USDHOME/.bash_profile file: Upgrading from Red Hat Enterprise Linux 6 may fail on IBM Power Systems Because of a bug in the yaboot boot loader, upgrading from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 can fail on IBM Power Systems servers with an Unknown or corrupt filesystem error. This problem is typically caused by a misplaced yaboot.conf configuration file. Make sure that this file exists, that it is valid, and that it is placed on a standard (non-LVM) /boot partition. The /etc/os-release file contains outdated information after system upgrade Upgrading to the minor release (for example, from Red Hat Enterprise Linux 7.1 to 7.2) does not update the /etc/os-release file with the new product number. Instead, this file continues to list the release number, and a new file named os-release.rpmnew is placed in the /etc directory. If you require the /etc/os-release file to be up-to-date, replace it with /etc/os-release.rpmnew .

Commands:
if ((BASH_VERSINFO[0] >= 4)) && ((BASH_VERSINFO[1] >= 2)); then shopt -s direxpand fi
Chapter 25. Customizing project preferences In Business Central, a project is a part of your space and stores the related assets. You can add multiple projects in a space. For example, an organization includes various departments, such as HR, Payroll, Engineering, and R&D. You can map each department to a space in Business Central, along with adding respective projects. You can customize the project settings in Business Central. Also, you can create a new project or clone projects from an existing Git repository. Procedure In Business Central, select the Admin icon in the upper-right corner and select Projects . In the Project Preferences panel, select the preference you want to modify. The project preferences include: Project Importing : This preference consists of the following property: Select the Allow multiple projects to be imported on cluster to import multiple projects on a cluster. File exporting : This preference consists of the following properties: Table 25.1. File exporting properties Field Description PDF orientation Determines whether the PDF orientation is portrait or landscape. PDF units Determines whether the PDF unit is PT , MM , CN , or IN . PDF page format Determines whether the PDF page format is A[0-10] , B[0-10] , or C[0-10] . Spaces : This preference consists of the following properties: Table 25.2. Spaces properties Field Description Name The default name of the space that is created automatically if none exists. Owner The default owner of the space that is created automatically if none exists. Group ID The default group ID of the space that is created automatically if none exists. Alias (in singular) Determines the customized alias (singular) of the space. Alias (in plural) Determines the customized alias (plural) of the space. Default values : This preference consists of the following properties: Table 25.3. Default values properties Field Description Version The default version number of a project when creating projects. Description The default description of a project when creating projects. Branch The default branch to be used when using a Git repository. Assets Per Page Used to customize the number of assets per page in the project. The default value is 15 . Advanced GAV preferences : This preference consists of the following properties: Table 25.4. Advanced GAV preference properties Field Description Disable GAV conflict check? Determines whether to enable or disable the GAV conflict check. Disabling this checkbox enables the projects to contain the same GAV (group ID, artifact, and version). Allow child GAV edition? Determines whether to allow child or subprojects to contain GAV edition. Note Duplicate GAV detection is disabled for projects in the development mode. To enable duplicate GAV detection for a project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option to OFF (if applicable). Click Save .

Commands:
14.3. Using the Real-Time Clock with Windows Server 2008, Windows Server 2008 R2, and Windows 7 Guests Windows uses both the Real-Time Clock (RTC) and the Time Stamp Counter (TSC). For Windows guest virtual machines the Real-Time Clock can be used instead of the TSC for all time sources, which resolves guest timing issues. The boot.ini file is no longer used as of Windows Server 2008 and newer. Windows Server 2008, Windows Server 2008 R2, and Windows 7 do not use the TSC as a time source if the hypervisor-present bit is set. The Red Hat Enterprise Linux 6 KVM hypervisor enables this CPUID bit by default, so it is no longer necessary to use the Boot Configuration Data Editor ( bcdedit.exe ) to modify the Windows boot parameters. Procedure 14.1. Using the Real-Time Clock with Windows Server 2008 R2 and Windows 7 guests Open the Windows guest virtual machine. Open the Accessories menu of the start menu. Right click on the Command Prompt application, select Run as Administrator . Confirm the security exception, if prompted. Set the boot manager to use the platform clock. This should instruct Windows to use the PM timer for the primary clock source. The system UUID ( {default} in the example below) should be changed if the system UUID is different than the default boot device. This fix should improve time keeping for Windows Server 2008 R2 and Windows 7 guests. Windows 2008 (non-R2) does not support the USEPLATFORMCLOCK parameter, but already uses the Real-Time Clock by default.

Commands:
C:\Windows\system32>bcdedit /set {default} USEPLATFORMCLOCK on The operation completed successfully
2.5. Disaster Recovery Disaster recovery is quicker and easier when the systems are virtualized. On a physical system, if something serious goes wrong, a complete reinstall of the operating system is usually required, resulting in hours of recovery time. However, if the systems are virtualized this is much faster due to the migration ability. If the requirements for live migration are followed, virtual machines can be restarted on another host, and the longest possible delay would be in restoring guest data. Also, because each of the virtualized systems are completely separate to each other, one system's downtime will not affect any others.

Commands:
Chapter 22. Starting and Stopping the glusterd service Using the glusterd command line, logical storage volumes can be decoupled from physical hardware. Decoupling allows storage volumes to be grown, resized, and shrunk, without application or server downtime. Regardless of changes made to the underlying hardware, the trusted storage pool is always available while changes to the underlying hardware are made. As storage is added to the trusted storage pool, volumes are rebalanced across the pool to accommodate the added storage capacity. The glusterd service is started automatically on all servers in the trusted storage pool. The service can also be manually started and stopped as required. Run the following command to start glusterd manually. On RHEL 7 and RHEL 8, run On RHEL 6, run Important Red Hat Gluster Storage is not supported on Red Hat Enterprise Linux 6 (RHEL 6) from 3.5 Batch Update 1 onwards. See Version Details table in section Red Hat Gluster Storage Software Components and Versions of the Installation Guide Run the following command to stop glusterd manually. On RHEL 7 and RHEL 8, run On RHEL 6, run When a Red Hat Gluster Storage server node that hosts a very large number of bricks or snapshots is upgraded, cluster management commands may become unresponsive as glusterd attempts to start all brick processes concurrently for all bricks and snapshots. If you have more than 250 bricks or snapshots being hosted by a single node, Red Hat recommends deactivating snapshots until upgrade is complete.

Commands:
systemctl start glusterd
service glusterd start
systemctl stop glusterd
service glusterd stop
Chapter 14. Running the Camel Debugger You can run the Camel debugger on locally running routing contexts. Note Remote debugging is no longer supported. For remote debugging, you must configure Jolokia and create a specific JMX connection through Jolokia. If your project contains Java code, you can use the standard Eclipse Java debugging tools to debug it. You must set breakpoints in your routing context file before you can start the Camel debugger. Procedure In the Project Explorer view, select the routing context file you want to debug. Right-click the selected file to open the context menu, and then select Debug As Local Camel Context . Fuse Tooling builds the Camel route, starts Apache Camel, starts the routing context, enables JMX, starts the route(s) in the routing context, adds the breakpoints to the nodes, and enables the Camel debugger. The Camel debugger suspends execution of the routing context at the first breakpoint hit (received a message), and prompts you to indicate whether you want it to open the Debug perspective. Click Yes to open the Debug perspective. The Debug perspective opens with the routing context suspended at the first breakpoint encountered in the running routing context. Important Breakpoints are held for a maximum of five minutes, after which debugging automatically resumes, moving on to the breakpoint or to the end of the routing context. Note To see the console output, open the Console view if it was not open when you switched perspectives. Note By default, the Debug perspective displays the Outline view, which provides the means to switch between separate routes in a running routing context. If your routing context contains a single route, closing the Outline view frees space to expand the other views, making it easier to access and examine debugger output. Watching message exchanges progress through the routing context Click (Step Over) to jump to the node of execution in the routing context. Click (Resume) to continue execution at the active breakpoint in the routing context. Related topics Chapter 15, Stopping the Camel Debugger

Commands:
8.83. haproxy 8.83.1. RHBA-2014:1509 - haproxy bug fix and enhancement update Updated haproxy packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The haproxy packages provide a reliable, high-performance network load balancer for TCP and HTTP-based applications. Note The haproxy package has been upgraded to upstream version 1.5.2, which provides a number of bug fixes and enhancements over the version, including support for SSL termination. (BZ# 1081727 ) Users of haproxy are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
2.21. RHEA-2011:0528 - new package: omping A new omping package is now available as a Technology Preview for Red Hat Enterprise Linux 6. Open Multicast Ping (omping) is a tool for testing IP multicast functionality, primarily on a LAN (local area network). It allows users to test multicast and receive sufficient information to detect whether a potential problem exists in the network configuration, or lies elsewhere, as might be the case with a bug. This enhancement update adds a new omping package to Red Hat Enterprise Linux 6 as a Technology Preview. (BZ# 657370 ) More information about Red Hat Technology Previews is available here: https://access.redhat.com/support/offerings/techpreview/ All users who want to use the omping Technology Preview should install this newly-released package, which adds this enhancement.

Commands:
Chapter 38. Database connection Business Central provides a dedicated UserGroupCallback implementation for database server with Red Hat Process Automation Manager to enable the user task service. The user task service helps in retrieving information on users and groups (roles) directly from databases. You can configure the following database UserGroupCallback implementation properties: Table 38.1. Database UserGroupCallback properties Property Description db.ds.jndi.name JNDI name of the data source used for connections db.user.query Verifies the user existence db.user.roles.query Collects the groups for a given user db.roles.query Verifies the group existence 38.1. Database UserGroupCallback implementation In database UserGroupCallback implementation, you must create the required database. You can use this implementation by configuring the respective database properties in one of the following ways: Programmatically: Build a properties object with the respective DBUserGroupCallbackImpl properties and create DBUserGroupCallbackImpl using the same properties object as its parameter. For example: Declaratively: Create the jbpm.usergroup.callback.properties file in the root of your application or specify the file location as a system property. For example: -Djbpm.usergroup.callback.properties=FILE_LOCATION_ON_CLASSPATH Ensure that you register the database callback when starting the user task server. For example: Additional resources Roles and users

Commands:
import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.DS_JNDI_NAME; import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.PRINCIPAL_QUERY; import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.ROLES_QUERY; import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.USER_ROLES_QUERY; props = new Properties(); props.setProperty(DS_JNDI_NAME, "jdbc/jbpm-ds"); props.setProperty(PRINCIPAL_QUERY, "select userId from Users where userId = ?"); props.setProperty(ROLES_QUERY, "select groupId from UserGroups where groupId = ?"); props.setProperty(USER_ROLES_QUERY, "select groupId from UserGroups where userId = ?"); callback = new DBUserGroupCallbackImpl(props);
System.setProperty("jbpm.usergroup.callback.properties", "/jbpm.usergroup.callback.db.properties"); callback = new DBUserGroupCallbackImpl(true); db.ds.jndi.name = jdbc/jbpm-ds db.user.query = select userId from Users where userId = ? db.roles.query = select groupId from UserGroups where groupId = ? db.user.roles.query = select groupId from UserGroups where userId = ?
Appendix G. References What everyone should know about Kubernetes memory limits, OOMKilled pods, and pizza parties Pulp Project Hardware requirements Red Hat Ansible Automation Platform Performance Considerations for Operator Based Installations Deploying the Red Hat Ansible Automation Platform operator on OpenShift Container Platform Pulp Operator storage configuration AWX Operator Resources consumed by idle PostgreSQL connections Operator scoping with OperatorGroups Ansible Tower and Grafana Dashboards

Commands:
18.2.2. Specifying the Mount Options To specify additional mount options, use the command in the following form: When supplying multiple options, do not insert a space after a comma, or mount will incorrectly interpret the values following spaces as additional parameters. Table 18.2, "Common Mount Options" provides a list of common mount options. For a complete list of all available options, consult the relevant manual page as referred to in Section 18.4.1, "Manual Page Documentation" . Table 18.2. Common Mount Options Option Description async Allows the asynchronous input/output operations on the file system. auto Allows the file system to be mounted automatically using the mount -a command. defaults Provides an alias for async,auto,dev,exec,nouser,rw,suid . exec Allows the execution of binary files on the particular file system. loop Mounts an image as a loop device. noauto Default behavior disallows the automatic mount of the file system using the mount -a command. noexec Disallows the execution of binary files on the particular file system. nouser Disallows an ordinary user (that is, other than root ) to mount and unmount the file system. remount Remounts the file system in case it is already mounted. ro Mounts the file system for reading only. rw Mounts the file system for both reading and writing. user Allows an ordinary user (that is, other than root ) to mount and unmount the file system. See Example 18.3, "Mounting an ISO Image" for an example usage. Example 18.3. Mounting an ISO Image An ISO image (or a disk image in general) can be mounted by using the loop device. Assuming that the ISO image of the Fedora 14 installation disc is present in the current working directory and that the /media/cdrom/ directory exists, mount the image to this directory by running the following command as root : Note that ISO 9660 is by design a read-only file system.

Commands:
mount -o options device directory
~]# mount -o ro,loop Fedora-14-x86_64-Live-Desktop.iso /media/cdrom
Chapter 1. ModSecurity module The ModSecurity module is a web application firewall (WAF) that you can use to filter, monitor, and block HTTP traffic that web clients send to a web server application. Unlike a regular firewall, a WAF uses filters to determine which applications and users can interact with your Apache HTTP Server application. The effectiveness of ModSecurity relies on user-defined rules that enable ModSecurity to perform configurable and real-time monitoring of HTTP traffic to detect attacks instantly. Note The Red Hat JBoss Core Services ModSecurity Guide provides information and examples for the ModSecurity version 2.9 module that is available with the Red Hat JBoss Core Services 2.4.57 release. The effectiveness of ModSecurity depends on user-generated rules. This document describes how to create and implement rules. This document does not provide a set of rules to use.

Commands:
5.71. fontforge 5.71.1. RHBA-2012:0351 - fontforge bug fix update Updated fontforge packages that fix one bug are now available for Red Hat Enterprise Linux 6. FontForge is a font editor for outline and bitmap fonts. FontForge supports a range of font formats, including PostScript, TrueType, OpenType and CID-keyed fonts. Bug Fix BZ# 676607 Previously, the "configure.in" file did not include information on how to handle 64-bit PowerPC architectures. Attempting to install the fontforge-devel multilib PowerPC and 64-PowerPC RPM packages on the same 64-bit PowerPC machine led to conflicts between those packages. This update modifies the "configure.in" file, so that fontforge-devel multilib RPM packages are allowed to be installed on the same machine. The conflicts no longer occur in the described scenario. All users of fontforge are advised to upgrade to these updated packages, which fix this bug.

Commands: