mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 51. New Drivers Storage Drivers USB Type-C Connector Class (typec.ko.xz): USB Type-C Connector System Software Interface driver (typec_ucsi.ko.xz): TCM QLA2XXX series NPIV enabled fabric driver (tcm_qla2xxx.ko.xz): Chelsio FCoE driver (csiostor.ko.xz): 1.0.0-ko Network Drivers Software simulator of 802.11 radio(s) for mac80211 (mac80211_hwsim.ko.xz): Vsock monitoring device. Based on nlmon device. (vsockmon.ko.xz): Cavium LiquidIO Intelligent Server Adapter Virtual Function Driver (liquidio_vf.ko.xz): 1.6.1 Cavium LiquidIO Intelligent Server Adapter Driver (liquidio.ko.xz): 1.6.1 Mellanox firmware flash lib (mlxfw.ko.xz): Intel OPA Virtual Network driver (opa_vnic.ko.xz): Broadcom NetXtreme-C/E RoCE Driver Driver (bnxt_re.ko.xz): VMware Paravirtual RDMA driver (vmw_pvrdma.ko.xz): Graphics Drivers and Miscellaneous Drivers MC Driver for Intel SoC using Pondicherry memory controller (pnd2_edac.ko.xz): ALPS HID driver (hid-alps.ko.xz): Intel Corporation DAX device (device_dax.ko.xz): Synopsys DesignWare DMA Controller platform driver (dw_dmac.ko.xz): Synopsys DesignWare DMA Controller core driver (dw_dmac_core.ko.xz); Intel Sunrisepoint PCH pinctrl/GPIO driver (pinctrl-sunrisepoint.ko.xz): Intel Lewisburg pinctrl/GPIO driver (pinctrl-lewisburg.ko.xz): Intel Cannon Lake PCH pinctrl/GPIO driver (pinctrl-cannonlake.ko.xz): Intel Denverton SoC pinctrl/GPIO driver (pinctrl-denverton.ko.xz): Intel Gemini Lake SoC pinctrl/GPIO driver (pinctrl-geminilake.ko.xz): Intel pinctrl/GPIO core driver (pinctrl-intel.ko.xz):

Commands:
Chapter 14. Understanding the node_replace_inventory.yml file The node_replace_inventory.yml file is an example Ansible inventory file that you can use to prepare a replacement host for your Red Hat Hyperconverged Infrastructure for Virtualization cluster. You can find this file at /etc/ansible/roles/gluster.ansible/playbooks/hc-ansible-deployment/node_replace_inventory.yml on any hyperconverged host. 14.1. Configuration parameters for node replacement hosts (required) Defines one active host in the cluster using the back-end FQDN. gluster_maintenance_old_node (required) Defines the backend FQDN of the node being replaced. gluster_maintenance_new_node (required) Defines the backend FQDN of the replacement node. gluster_maintenance_cluster_node (required) An active node in the cluster. Cannot be the same as gluster_maintenance_cluster_node_2 . gluster_maintenance_cluster_node_2 (required) An active node in the cluster. Cannot be the same as gluster_maintenance_cluster_node . 14.2. Example node_replace_inventory.yml

Commands:
cluster_nodes: hosts: host2-backend-fqdn.example.com : vars: [common host configuration]
cluster_nodes: hosts: host2-backend-fqdn.example.com : vars: gluster_maintenance_old_node: host1-backend-fqdn.example.com
cluster_nodes: hosts: host2-backend-fqdn.example.com : vars: gluster_maintenance_new_node: new-host-backend-fqdn.example.com
cluster_nodes: hosts: host2-backend-fqdn.example.com : vars: gluster_maintenance_cluster_node: host2-backend-fqdn.example.com
cluster_nodes: hosts: host2-backend-fqdn.example.com : vars: gluster_maintenance_cluster_node_2: host3-backend-fqdn.example.com
cluster_node: hosts: host2-backend-fqdn.example.com : vars: gluster_maintenance_old_node: host1-backend-fqdn.example.com gluster_maintenance_new_node: new-host-backend-fqdn.example.com gluster_maintenance_cluster_node: host2-backend-fqdn.example.com gluster_maintenance_cluster_node_2: host3-backend-fqdn.example.com
32.3.3. Displaying a Backtrace To display the kernel stack trace, type the bt command at the interactive prompt. You can use bt pid to display the backtrace of the selected process. Example 32.4. Displaying the kernel stack trace Type help bt for more information on the command usage.

Commands:
crash> bt PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash" #0 [ef4dbdcc] crash_kexec at c0494922 #1 [ef4dbe20] oops_end at c080e402 #2 [ef4dbe34] no_context at c043089d #3 [ef4dbe58] bad_area at c0430b26 #4 [ef4dbe6c] do_page_fault at c080fb9b #5 [ef4dbee4] error_code (via page_fault) at c080d809 EAX: 00000063 EBX: 00000063 ECX: c09e1c8c EDX: 00000000 EBP: 00000000 DS: 007b ESI: c0a09ca0 ES: 007b EDI: 00000286 GS: 00e0 CS: 0060 EIP: c068124f ERR: ffffffff EFLAGS: 00010096 #6 [ef4dbf18] sysrq_handle_crash at c068124f #7 [ef4dbf24] __handle_sysrq at c0681469 #8 [ef4dbf48] write_sysrq_trigger at c068150a #9 [ef4dbf54] proc_reg_write at c0569ec2 #10 [ef4dbf74] vfs_write at c051de4e #11 [ef4dbf94] sys_write at c051e8cc #12 [ef4dbfb0] system_call at c0409ad5 EAX: ffffffda EBX: 00000001 ECX: b7776000 EDX: 00000002 DS: 007b ESI: 00000002 ES: 007b EDI: b7776000 SS: 007b ESP: bfcb2088 EBP: bfcb20b4 GS: 0033 CS: 0073 EIP: 00edc416 ERR: 00000004 EFLAGS: 00000246
Chapter 15. Configuring kdump in the web console You can set up and test the kdump configuration by using the RHEL 9 web console. The web console can enable the kdump service at boot time. With the web console, you can configure the reserved memory for kdump and to select the vmcore saving location in an uncompressed or compressed format. 15.1. Configuring kdump memory usage and target location in web console You can configure the memory reserve for the kdump kernel and also specify the target location to capture the vmcore dump file with the RHEL web console interface. Prerequisites The web console must be installed and accessible. For details, see Installing the web console . Procedure In the web console, open the Kernel dump tab and start the kdump service by setting the Kernel crash dump switch to on. Configure the kdump memory usage in the terminal, for example: Restart the system to apply the changes. In the Kernel dump tab, click Edit at the end of the Crash dump location field. Specify the target directory for saving the vmcore dump file: For a local filesystem, select Local Filesystem from the drop-down menu. For a remote system by using the SSH protocol, select Remote over SSH from the drop-down menu and specify the following fields: In the Server field, enter the remote server address. In the SSH key field, enter the SSH key location. In the Directory field, enter the target directory. For a remote system by using the NFS protocol, select Remote over NFS from the drop-down menu and specify the following fields: In the Server field, enter the remote server address. In the Export field, enter the location of the shared folder of an NFS server. In the Directory field, enter the target directory. Note You can reduce the size of the vmcore file by selecting the Compression checkbox. Optional: Display the automation script by clicking View automation script . A window with the generated script opens. You can browse a shell script and an Ansible playbook generation options tab. Optional: Copy the script by clicking Copy to clipboard . You can use this script to apply the same configuration on multiple machines. Verification Click Test configuration . Click Crash system under Test kdump settings . Warning When you start the system crash, the kernel operation stops and results in a system crash with data loss. Additional resources Supported kdump targets

Commands:
sudo grubby --update-kernel ALL --args crashkernel=512M
Chapter 3. Configuring signup flows In this section, you will see which settings to configure to adjust signup workflows. Signup workflows are a critical aspect of the developer experience you provide through your Developer Portal. The process can range from being completely automatic and self-service to the other extreme of requiring total control over who gains access to what, with various levels of granularity. The 3scale platform allows you to model your API with a combination of account (optional), service (optional), and application plans. For each of these plans, you can control whether there is an approval gate that you operate. For each one, you also determine whether there is a default, or the developer is required to take the step and make a choice. For the extreme of maximum automation and self-service, remove all approval steps and enable all possible default plans. This way, a key can be issued to provide access to your API immediately after signup. 3.1. Removing all approval steps To remove approvals, go to Audience > Accounts > Usage Rules and in the Signup section, make sure the option of Developers are allowed to sign up themselves is checked. Optionally, if you have account and service plans enabled, scroll down the page and make sure the option Change plan directly is enabled in both cases: 3.2. Enabling all possible default plans Application plans Optionally, if you have account and service plans enabled, choose default plans for those too. Account plans (optional) Service plans (optional) 3.3. Testing the workflow Once you have made your desired settings changes, test out the results by going to your Developer Portal and attempting to sign up as a new developer. Experiment and make any necessary adjustments to get exactly the right workflow for your API. When you are happy with the workflow, it is a good time to check your email notifications to make sure they provide the right information for your developers.

Commands:
Chapter 31. SpEL Overview The Spring Expression Language (SpEL) is an object graph navigation language provided with Spring 3, which can be used to construct predicates and expressions in a route. A notable feature of SpEL is the ease with which you can access beans from the registry. Syntax The SpEL expressions must use the placeholder syntax, #{ SpelExpression } , so that they can be embedded in a plain text string (in other words, SpEL has expression templating enabled). SpEL can also look up beans in the registry (typically, the Spring registry), using the @ BeanID syntax. For example, given a bean with the ID, headerUtils , and the method, count() (which counts the number of headers on the current message), you could use the headerUtils bean in an SpEL predicate, as follows: Adding SpEL package To use SpEL in your routes you need to add a dependency on camel-spring to your project as shown in Example 31.1, "Adding the camel-spring dependency" . Example 31.1. Adding the camel-spring dependency Variables Table 31.1, "SpEL variables" lists the variables that are accessible when using SpEL. Table 31.1. SpEL variables Variable Type Description this Exchange The current exchange is the root object. exchange Exchange The current exchange. exchangeId String The current exchange's ID. exception Throwable The exchange exception (if any). fault Message The fault message (if any). request Message The exchange's In message. response Message The exchange's Out message (if any). properties Map The exchange properties. property( Name ) Object The exchange property keyed by Name . property( Name , Type ) Type The exchange property keyed by Name , converted to the type, Type . XML example For example, to select only those messages whose Country header has the value USA , you can use the following SpEL expression: <route> <from uri="SourceURL"/> <filter> <spel>#{request.headers['Country'] == 'USA'}}</spel> <to uri="TargetURL"/> </filter> </route> Java example You can define the same route in the Java DSL, as follows: from("SourceURL") .filter().spel("#{request.headers['Country'] == 'USA'}") .to("TargetURL"); The following example shows how to embed SpEL expressions within a plain text string: from("SourceURL") .setBody(spel("Hello #{request.body}! What a beautiful #{request.headers['dayOrNight']}")) .to("TargetURL");

Commands:
#{@headerUtils.count > 4}
<!-- Maven POM File --> <properties> <camel-version>2.23.2.fuse-7_13_0-00013-redhat-00001</camel-version> </properties> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-spring</artifactId> <version>USD{camel-version}</version> </dependency> </dependencies>
<route> <from uri="SourceURL"/> <filter> <spel>#{request.headers['Country'] == 'USA'}}</spel> <to uri="TargetURL"/> </filter> </route>
from("SourceURL") .filter().spel("#{request.headers['Country'] == 'USA'}") .to("TargetURL");
from("SourceURL") .setBody(spel("Hello #{request.body}! What a beautiful #{request.headers['dayOrNight']}")) .to("TargetURL");
Chapter 5. Catalog selection by name When a catalog is added to a cluster, a label is created by using the value of the metadata.name field of the catalog custom resource (CR). In the CR of an extension, you can specify the catalog name by using the spec.source.catalog.selector.matchLabels field. The value of the matchLabels field uses the following format: Example label derived from the metadata.name field apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> labels: olm.operatorframework.io/metadata.name: <example_extension> 1 ... 1 A label derived from the metadata.name field and automatically added when the catalog is applied. The following example resolves the <example_extension>-operator package from a catalog with the openshift-redhat-operators label: Example extension CR apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> spec: namespace: <example_namespace> serviceAccount: name: <example_extension>-installer source: sourceType: Catalog catalog: packageName: <example_extension>-operator selector: matchLabels: olm.operatorframework.io/metadata.name: openshift-redhat-operators

Commands:
apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> labels: olm.operatorframework.io/metadata.name: <example_extension> 1
apiVersion: olm.operatorframework.io/v1 kind: ClusterExtension metadata: name: <example_extension> spec: namespace: <example_namespace> serviceAccount: name: <example_extension>-installer source: sourceType: Catalog catalog: packageName: <example_extension>-operator selector: matchLabels: olm.operatorframework.io/metadata.name: openshift-redhat-operators
6.8. Clustering corosync component The redundant ring feature of corosync is not fully supported in combination with InfiniBand or Distributed Lock Manager (DLM). A double ring failure can cause both rings to break at the same time on different nodes. In addition, DLM is not functional if ring0 is down. lvm2 component, BZ# 814779 Clustered environment is not supported by lvmetad at the moment. If global/use_lvmetad=1 is used together with global/locking_type=3 configuration setting (clustered locking), the use_lvmetad setting is automatically overriden to 0 and lvmetad is not used in this case at all. Also, the following warning message is displayed: luci component, BZ# 615898 luci will not function with Red Hat Enterprise Linux 5 clusters unless each cluster node has ricci version 0.12.2-14.

Commands:
WARNING: configuration setting use_lvmetad overriden to 0 due to locking_type 3. Clustered environment not supported by lvmetad yet.
Chapter 7. References 7.1. Red Hat Support Policies for RHEL High Availability Clusters - Management of SAP HANA in a Cluster Automating SAP HANA Scale-Up System Replication using the RHEL HA Add-On Moving Resources Due to Failure Is there a way to manage constraints when running pcs resource move? 7.2. SAP SAP HANA Administration Guide for SAP HANA Platform Disaster Recovery Scenarios for Multitarget System Replication SAP HANA System Replication Configuration Parameter Example: Checking the Status on the Primary and Secondary Systems General Prerequisites for Configuring SAP HANA System Replication Change Log Modes Failed to re-register former primary site as new secondary site due to missing log Checking the Status with landscapeHostConfiguration.py How to Setup SAP HANA Multi-Target System Replication SAP HANA Multitarget System Replication

Commands:
9.10. References Administering an NFS server can be a challenge. Many options, including quite a few not mentioned in this chapter, are available for exporting or mounting NFS shares. Consult the following sources for more information. Installed Documentation man mount - Contains a comprehensive look at mount options for both NFS server and client configurations. man fstab - Gives details for the format of the /etc/fstab file used to mount file systems at boot-time. man nfs - Provides details on NFS-specific file system export and mount options. man exports - Shows common options used in the /etc/exports file when exporting NFS file systems. man 8 nfsidmap - Explains the nfsidmap cammand and lists common options. Useful Websites http://linux-nfs.org - The current site for developers where project status updates can be viewed. http://nfs.sourceforge.net/ - The old home for developers which still contains a lot of useful information. http://www.citi.umich.edu/projects/nfsv4/linux/ - An NFSv4 for Linux 2.6 kernel resource. http://www.vanemery.com/Linux/NFSv4/NFSv4-no-rpcsec.html - Describes the details of NFSv4 with Fedora Core 2, which includes the 2.6 kernel. http://citeseer.ist.psu.edu/viewdoc/summary?doi=10.1.1.111.4086 - An excellent whitepaper on the features and enhancements of the NFS Version 4 protocol. Related Books Managing NFS and NIS by Hal Stern, Mike Eisler, and Ricardo Labiaga; O'Reilly & Associates - Makes an excellent reference guide for the many different NFS export and mount options available as of 2001. NFS Illustrated by Brent Callaghan; Addison-Wesley Publishing Company - Provides comparisons of NFS to other network file systems and shows, in detail, how NFS communication occurs.

Commands:
10.7. Development Considerations MetadataRepository instances are created on a per VDB basis and may be called concurrently for the load of multiple models. See the MetadataFactory and the org.teiid.metadata package javadocs for metadata construction methods and objects. For example if you use your own DDL, then call the MetadataFactory.parse(Reader) method. If you need access to files in a VDB zip deployment, then use the MetadataFactory.getVDBResources method. Use the MetadataFactory.addPermission and add MetadataFactory.addColumnPermission method to grant permissions on the given metadata objects to the named roles. The roles should be declared in your vdb.xml, which is also where they are typically tied to container roles.

Commands:
Chapter 38. Role-based access control for branches in Business Central Business Central provides the option for users to restrict the access for a target branch for a specific collaborator type. The security check uses both the Security Management screen and contributors sources to grant or deny permissions to spaces and projects. For example, if a user has the security permission to update a project and has write permission on that branch, based on the contributor type, then they are able to create new assets. 38.1. Customizing role-based branch access You can customize contributor role permissions for each branch of a project in Business Central. For example, you can set Read , Write , Delete , and Deploy access for each role assigned to a branch. Procedure In Business Central, go to Menu Design Projects . If needed, add a new contributor: Click the project name and then click the Contributors tab. Click Add Contributor . Enter user name in the text field. Select the Contributor role type from the drop-down list. Click Ok . Customize role-based branch access for the relevant contributor: Click Settings Branch Management . Select the branch name from the drop-down list. In the Role Access section, select or deselect the permissions check boxes to specify role-based branch access for each available role type. Click Save and click Save again to confirm your changes.

Commands:
3.6. Adding Journals to a GFS2 File System The gfs2_jadd command is used to add journals to a GFS2 file system. You can add journals to a GFS2 file system dynamically at any point without expanding the underlying logical volume. The gfs2_jadd command must be run on a mounted file system, but it needs to be run on only one node in the cluster. All the other nodes sense that the expansion has occurred. Note If a GFS2 file system is full, the gfs2_jadd command will fail, even if the logical volume containing the file system has been extended and is larger than the file system. This is because in a GFS2 file system, journals are plain files rather than embedded metadata, so simply extending the underlying logical volume will not provide space for the journals. Before adding journals to a GFS2 file system, you can find out how many journals the GFS2 file system currently contains with the gfs2_edit -p jindex command, as in the following example: Usage Number Specifies the number of new journals to be added. MountPoint Specifies the directory where the GFS2 file system is mounted. Examples In this example, one journal is added to the file system on the /mygfs2 directory. In this example, two journals are added to the file system on the /mygfs2 directory. Complete Usage MountPoint Specifies the directory where the GFS2 file system is mounted. Device Specifies the device node of the file system. Table 3.4, "GFS2-specific Options Available When Adding Journals" describes the GFS2-specific options that can be used when adding journals to a GFS2 file system. Table 3.4. GFS2-specific Options Available When Adding Journals Flag Parameter Description -h Help. Displays short usage message. -J Megabytes Specifies the size of the new journals in megabytes. Default journal size is 128 megabytes. The minimum size is 32 megabytes. To add journals of different sizes to the file system, the gfs2_jadd command must be run for each size journal. The size specified is rounded down so that it is a multiple of the journal-segment size that was specified when the file system was created. -j Number Specifies the number of new journals to be added by the gfs2_jadd command. The default value is 1. -q Quiet. Turns down the verbosity level. -V Displays command version information.

Commands:
gfs2_edit -p jindex /dev/sasdrives/scratch|grep journal 3/3 [fc7745eb] 4/25 (0x4/0x19): File journal0 4/4 [8b70757d] 5/32859 (0x5/0x805b): File journal1 5/5 [127924c7] 6/65701 (0x6/0x100a5): File journal2
gfs2_jadd -j Number MountPoint
gfs2_jadd -j 1 /mygfs2
gfs2_jadd -j 2 /mygfs2
gfs2_jadd [ Options ] { MountPoint | Device } [ MountPoint | Device ]
Chapter 4. Distribution of content RHEL 9 for SAP Solutions is installed using ISO images. For more information, see Installing RHEL 9 for SAP Solutions . For information on RHEL for SAP Solutions offerings on Certified Cloud Providers, see SAP Offerings on Certified Cloud Providers . If you need help installing your product, contact Red Hat Customer Service or Technical Support . SAP specific content is available on separate SAP repositories and ISOs and only for SAP-supported architectures (Intel x86_64, IBM Power LE). See How to subscribe SAP HANA systems to the Update Services for SAP Solutions . Performing a standard RHEL 9 installation Package manifest Considerations in adopting RHEL 9

Commands:
7.6. Additional Resources There is a large amount of detailed information available about the X server, the clients that connect to it, and the assorted desktop environments and window managers. 7.6.1. Installed Documentation /usr/X11R6/lib/X11/doc/README - Briefly describes the XFree86 architecture and how to get additional information about the XFree86 project as a new user. /usr/X11R6/lib/X11/doc/RELNOTES - For advanced users that want to read about the latest features available in XFree86. man xorg.conf - Contains information about the xorg.conf configuration files, including the meaning and syntax for the different sections within the files. man X.Org - The primary man page for X.Org Foundation information. man Xorg - Describes the X11R6.8 display server.

Commands: