mtpti5iD/redhat-docs_dataset huggingface dataset:
1.2. Cluster Creation This procedure creates a Red Hat High Availability Add-On cluster that consists of the nodes z1.example.com and z2.example.com . Execute the following command from z1.example.com to create the two-node cluster my_cluster that consists of nodes z1.example.com and z2.example.com . This will propagate the cluster configuration files to both nodes in the cluster. This command includes the --start option, which will start the cluster services on both nodes in the cluster. Enable the cluster services to run on each node in the cluster when the node is booted. Note For your particular environment, you may choose to leave the cluster services disabled by skipping this step. This allows you to ensure that if a node goes down, any issues with your cluster or your resources are resolved before the node rejoins the cluster. If you leave the cluster services disabled, you will need to manually start the services when you reboot a node by executing the pcs cluster start command on that node. You can display the current status of the cluster with the pcs cluster status command. Because there may be a slight delay before the cluster is up and running when you start the cluster services with the --start option of the pcs cluster setup command, you should ensure that the cluster is up and running before performing any subsequent actions on the cluster and its configuration.

Commands:
pcs cluster setup --start --name my_cluster z1.example.com z2.example.com z1.example.com: Succeeded z1.example.com: Starting Cluster z2.example.com: Succeeded z2.example.com: Starting Cluster
pcs cluster enable --all
pcs cluster status Cluster Status: Last updated: Thu Jul 25 13:01:26 2013 Last change: Thu Jul 25 13:04:45 2013 via crmd on z2.example.com Stack: corosync Current DC: z2.example.com (2) - partition with quorum Version: 1.1.10-5.el7-9abe687 2 Nodes configured 0 Resources configured
3.8. RHEA-2011:1545 - new package: passsync A new passsync package is now available for Red Hat Enterprise Identity Replication. PassSync is a Windows service that runs on every domain controller. This intercepts clear text password updates and sends them to the directory server running on Red Hat Enterprise Linux. PassSync works together with the Windows Synchronization (WinSync) feature of the directory server to keep passwords synchronized between Active Directory (AD) and the directory server running on Red Hat Enterprise Linux. This enhancement update adds the passsync package to Red Hat Enterprise Identity Replication which is an add-on for Red Hat Enterprise Linux 6. (BZ# 690622 ) Users who require password synchronization together with WinSync are advised to install this new package.

Commands:
8.140. parted 8.140.1. RHBA-2013:1627 - parted bug fix update Updated parted packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The parted packages provide tools to create, destroy, resize, move, and copy hard disk partitions. The parted program can be used for creating space for new operating systems, reorganizing disk usage, and copying data to new hard disks. Bug Fixes BZ#851705 After removing a partition from a Device Mapper Multipath (DM-Multipath) device that contained the only partition, the parted utility failed to remove the DM-Multipath device as expected until system reboot. With this update, a bug in the libparted library has been fixed, so that parted now correctly removes DM-Multipath devices in this scenario. BZ#869743 Previously, the parted utility was only able to handle loop devices with a size limited to an unsigned 32-bit integer. As a consequence, using parted with loop devices larger than 4 GiB failed. With this update, the above mentioned limit has been increased to an unsigned 64-bit integer, and loop devices up to 2^64 of size are now supported. BZ#631928 Previously, the parted utility was not able to handle Extended Address Volumes (EAV) Direct Access Storage Devices (DASD) that have more than 65535 cylinders. Consequently, EAV DASD drives could not be partitioned using parted, and installation on EAV DASD drives failed. This update adds support for EAV DASD devices with more than 65535 cylinders, and parted now handles them correctly. Users of parted are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 12. Compiler and Tools Automatic Bug Reporting Tool (ABRT), Change in the Default Set of Reporters Running the abrt-cli --report DIR command now shows the following choice of reporters: ABRT Notifications On the Console Red Hat Enterprise Linux 6.5 provides a new package, abrt-console-notification . With this package installed, users can see warnings on the console if a new problem has been detected by Automatic Bug Reporting Tool (ABRT) since the last login. This was previously not possible and is useful especially for users who do not use the graphical environment, for example, on headless systems. These users could otherwise miss problems detected by ABRT.

Commands:
How would you like to report the problem? 1) New Red Hat Support case 2) Existing Red Hat Support case 3) Save to tar archive
20.16.7. Redirected Devices USB device redirection through a character device is supported by configuring it with management tools that modify the following section of the domain xml: ... <devices> <redirdev bus='usb' type='tcp'> <source mode='connect' host='localhost' service='4000'/> <boot order='1'/> </redirdev> <redirfilter> <usbdev class='0x08' vendor='0x1234' product='0xbeef' version='2.00' allow='yes'/> <usbdev allow='no'/> </redirfilter> </devices> ... Figure 20.33. Devices - redirected devices The components of this section of the domain XML are as follows: Table 20.15. Redirected device elements Parameter Description redirdev This is the main container for describing redirected devices. bus must be usb for a USB device. An additional attribute type is required, matching one of the supported serial device types, to describe the host physical machine side of the tunnel; type='tcp' or type='spicevmc' (which uses the usbredir channel of a SPICE graphics device) are typical. The redirdev element has an optional sub-element address which can tie the device to a particular controller. Further sub-elements, such as source , may be required according to the given type , although a target sub-element is not required (since the consumer of the character device is the hypervisor itself, rather than a device visible in the guest virtual machine). boot Specifies that the device is bootable. The order attribute determines the order in which devices will be tried during boot sequence. The per-device boot elements cannot be used together with general boot elements in BIOS boot loader section. redirfilter This is used for creating the filter rule to filter out certain devices from redirection. It uses sub-element usbdev to define each filter rule. The class attribute is the USB Class code.

Commands:
<devices> <redirdev bus='usb' type='tcp'> <source mode='connect' host='localhost' service='4000'/> <boot order='1'/> </redirdev> <redirfilter> <usbdev class='0x08' vendor='0x1234' product='0xbeef' version='2.00' allow='yes'/> <usbdev allow='no'/> </redirfilter> </devices>
Chapter 1. Red Hat JBoss Web Server 6.0 Welcome to the Red Hat JBoss Web Server version 6.0 release. Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web applications. It consists of an application server (Apache Tomcat servlet container) and the Apache Tomcat Native Library. JBoss Web Server includes the following key components: Apache Tomcat is a servlet container in accordance with the Java Servlet Specification. JBoss Web Server contains Apache Tomcat 10.1. The Apache Tomcat Native Library improves Tomcat scalability, performance, and integration with native server technologies. Tomcat-vault is an extension for the JBoss Web Server that is used for securely storing passwords and other sensitive information used by a JBoss Web Server. The mod_cluster library enables communication between JBoss Web Server and the Apache HTTP Server mod_proxy_cluster module. The mod_cluster library enables you to use the Apache HTTP Server as a load balancer for JBoss Web Server. For more information about configuring mod_cluster , or for information about installing and configuring alternative load balancers such as mod_jk and mod_proxy , see the Apache HTTP Server Connectors and Load Balancing Guide . Apache portable runtime (APR) is a runtime that provides an OpenSSL-based TLS implementation for the HTTP connectors. JBoss Web Server provides a distribution of APR for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the APR package that the operating system provides. OpenSSL is a software library that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and includes a basic cryptographic library. JBoss Web Server provides a distribution of OpenSSL for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the OpenSSL package that the operating system provides. This release introduces support for Apache Tomcat 10.1 and fixes some security issues. This release of JBoss Web Server provides OpenShift images based on Red Hat Enterprise Linux 8.

Commands:
Chapter 1. Upgrading the Red Hat Developer Hub Operator If you use the Operator to deploy your Red Hat Developer Hub instance, then an administrator can use the OpenShift Container Platform web console to upgrade the Operator to a later version. OpenShift Container Platform is currently supported from version 4.13 to 4.15. See also the Red Hat Developer Hub Life Cycle . Prerequisites You are logged in as an administrator on the OpenShift Container Platform web console. You have installed the Red Hat Developer Hub Operator. You have configured the appropriate roles and permissions within your project to create or access an application. For more information, see the Red Hat OpenShift Container Platform documentation on Building applications . Procedure In the Administrator perspective of the OpenShift Container Platform web console, click Operators > Installed Operators . On the Installed Operators page, click Red Hat Developer Hub Operator . On the Red Hat Developer Hub Operator page, click the Subscription tab. From the Upgrade status field on the Subscription details page, click Upgrade available . Note If there is no upgrade available, the Upgrade status field value is Up to date . On the InstallPlan details page, click Preview InstallPlan > Approve . Verification The Upgrade status field value on the Subscription details page is Up to date . Additional resources Installing Red Hat Developer Hub on OpenShift Container Platform with the Operator . Installing from OperatorHub using the web console

Commands:
B.3. Tracking Certificates with certmonger certmonger can manage the entire certificate lifecycle. Along with generating requests, certmonger can track a certificate and automatically renew it when it expires at the end of its validity period. This is done using the start-tracking command with the getcert command. The -I option creates the tracking entry, along with pointers to the key and certificate files, either in an NSS database ( -d and -n ) or in the PEM file ( -f and -k ). The -r option tells certmonger to renew the certificate. Note The -r option can be passed with the request command, in Example B.1, "Using certmonger for a Service" . In that case, the requested certificate is automatically tracked and renewed by certmonger . Then, it is not necessary to configure tracking manually. A certificate can be un tracked by certmonger by using the stop-tracking command.

Commands:
ipa-getcert start-tracking -I cert1-tracker -d /export/alias -n ServerCert -r
Preface The OpenStack Networking service (codename neutron ) is the software-defined networking component of Red Hat OpenStack Platform 16.0. Software-defined networking (SDN) Network administrators can use software-defined networking (SDN) to manage network services through abstraction of lower-level functionality. While server workloads have been migrated into virtual environments, they are still just servers that look for a network connection to send and receive data. SDN meets this need by moving networking equipment (such as routers and switches) into the same virtualized space. If you are already familiar with basic networking concepts, then it is easy to consider that these physical networking concepts have now been virtualized, just like the servers that they connect. Topics covered in this book Preface - Offers a brief definition of software-defined networking (SDN). Part 1 - Covers common administrative tasks and basic troubleshooting steps: Adding and removing network resources Troubleshooting basic networks Troubleshooting project networks Part 2 - Contains cookbook-style scenarios for advanced Red Hat OpenStack Platform Networking features, including: Configuring Layer 3 High Availability for virtual routers Configuring DVR and other networking features

Commands:
Chapter 113. KafkaUserSpec schema reference Used in: KafkaUser Property Property type Description authentication KafkaUserTlsClientAuthentication , KafkaUserTlsExternalClientAuthentication , KafkaUserScramSha512ClientAuthentication Authentication mechanism enabled for this Kafka user. The supported authentication mechanisms are scram-sha-512 , tls , and tls-external . scram-sha-512 generates a secret with SASL SCRAM-SHA-512 credentials. tls generates a secret with user certificate for mutual TLS authentication. tls-external does not generate a user certificate. But prepares the user for using mutual TLS authentication using a user certificate generated outside the User Operator. ACLs and quotas set for this user are configured in the CN=<username> format. Authentication is optional. If authentication is not configured, no credentials are generated. ACLs and quotas set for the user are configured in the <username> format suitable for SASL authentication. authorization KafkaUserAuthorizationSimple Authorization rules for this Kafka user. quotas KafkaUserQuotas Quotas on requests to control the broker resources used by clients. Network bandwidth and request rate quotas can be enforced.Kafka documentation for Kafka User quotas can be found at http://kafka.apache.org/documentation/#design_quotas . template KafkaUserTemplate Template to specify how Kafka User Secrets are generated.

Commands:
8.173. perl-Class-MethodMaker 8.173.1. RHBA-2014:0534 - perl-Class-MethodMaker bug fix update Updated perl-Class-MethodMaker packages that fix one bug are now available for Red Hat Enterprise Linux 6. The perl-Class-MethodMake packages provide the perl module Class::MethodMaker which solves the problem of having to continually write accessor methods for your objects that perform standard tasks. Bug Fix BZ# 1064837 Previously, the perl-Class-MethodMake source package contained some source code used for testing that was licensed under a restrictive license. This bug fix removes all tests that used that source code. The binary packages have been updated to use this new source package. However, there has been no change in the functionality of these packages. Users of perl-Class-MethodMaker are advised to upgrade to these updated packages, which fix this bug.

Commands:
17.7. The Default Configuration When the libvirtd daemon ( libvirtd ) is first installed, it contains an initial virtual network switch configuration in NAT mode. This configuration is used so that installed guests can communicate to the external network, through the host physical machine. The following image demonstrates this default configuration for libvirtd : Figure 17.7. Default libvirt network configuration Note A virtual network can be restricted to a specific physical interface. This may be useful on a physical system that has several interfaces (for example, eth0 , eth1 and eth2 ). This is only useful in routed and NAT modes, and can be defined in the dev=<interface> option, or in virt-manager when creating a new virtual network.

Commands:
Chapter 387. Master RoutePolicy You can also use a RoutePolicy to control routes in master/slave mode. When doing so you must configure the route policy with url to zookeeper ensemble name of cluster group important and set the route to not auto startup A little example MasterRoutePolicy master = new MasterRoutePolicy(); master.setZooKeeperUrl("localhost:2181"); master.setGroupName("myGroup"); // its import to set the route to not auto startup // as we let the route policy start/stop the routes when it becomes a master/slave etc from("file:target/inbox?delete=true").noAutoStartup() // use the zookeeper master route policy in the clustered group // to run this route in master/slave mode .routePolicy(master) .log(name + " - Received file: USD{file:name}") .delay(delay) .log(name + " - Done file: USD{file:name}") .to("file:target/outbox"); 387.1. See Also Configuring Camel Component Endpoint Getting Started

Commands:
MasterRoutePolicy master = new MasterRoutePolicy(); master.setZooKeeperUrl("localhost:2181"); master.setGroupName("myGroup"); // its import to set the route to not auto startup // as we let the route policy start/stop the routes when it becomes a master/slave etc from("file:target/inbox?delete=true").noAutoStartup() // use the zookeeper master route policy in the clustered group // to run this route in master/slave mode .routePolicy(master) .log(name + " - Received file: USD{file:name}") .delay(delay) .log(name + " - Done file: USD{file:name}") .to("file:target/outbox");
5.8. Multipath Queries with multipath Command You can use the -l and -ll options of the multipath command to display the current multipath configuration. The -l option displays multipath topology gathered from information in sysfs and the device mapper. The -ll option displays the information the -l option displays in addition to all other available components of the system. When displaying the multipath configuration, there are three verbosity levels you can specify with the -v option of the multipath command. Specifying -v0 yields no output. Specifying -v1 outputs the created or updated multipath names only, which you can then feed to other tools such as kpartx . Specifying -v2 prints all detected paths, multipaths, and device maps. The following example shows the output of a multipath -l command. The following example shows the output of a multipath -ll command.

Commands:
multipath -l 3600d0230000000000e13955cc3757800 dm-1 WINSYS,SF2372 size=269G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=active | `- 6:0:0:0 sdb 8:16 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 7:0:0:0 sdf 8:80 active ready running
multipath -ll 3600d0230000000000e13955cc3757801 dm-10 WINSYS,SF2372 size=269G features='0' hwhandler='0' wp=rw |-+- policy='round-robin 0' prio=1 status=enabled | `- 19:0:0:1 sdc 8:32 active ready running `-+- policy='round-robin 0' prio=1 status=enabled `- 18:0:0:1 sdh 8:112 active ready running 3600d0230000000000e13955cc3757803 dm-2 WINSYS,SF2372 size=125G features='0' hwhandler='0' wp=rw `-+- policy='round-robin 0' prio=1 status=active |- 19:0:0:3 sde 8:64 active ready running `- 18:0:0:3 sdj 8:144 active ready running
4.2. Logical Volume Creation Overview The following is a summary of the steps to perform to create an LVM logical volume. Initialize the partitions you will use for the LVM volume as physical volumes (this labels them). Create a volume group. Create a logical volume. After creating the logical volume you can create and mount the file system. The examples in this document use GFS2 file systems. Note Although a GFS2 file system can be implemented in a standalone system or as part of a cluster configuration, for the Red Hat Enterprise Linux 6 release Red Hat does not support the use of GFS2 as a single-node file system. Red Hat will continue to support single-node GFS2 file systems for mounting snapshots of cluster file systems (for example, for backup purposes). Create a GFS2 file system on the logical volume with the mkfs.gfs2 command. Create a new mount point with the mkdir command. In a clustered system, create the mount point on all nodes in the cluster. Mount the file system. You may want to add a line to the fstab file for each node in the system. Alternately, you can create and mount the GFS2 file system with the LVM GUI. Creating the LVM volume is machine independent, since the storage area for LVM setup information is on the physical volumes and not the machine where the volume was created. Servers that use the storage have local copies, but can recreate that from what is on the physical volumes. You can attach physical volumes to a different server if the LVM versions are compatible.

Commands:
Migrating Fuse 7 Applications to Camel Extensions for Quarkus Red Hat build of Apache Camel Extensions for Quarkus 2.13 Migrating Fuse 7 Applications to Camel Extensions for Quarkus provided by Red Hat Camel Extensions for Quarkus Documentation Team fuse-docs-support@redhat.com Camel Extensions for Quarkus Support Team http://access.redhat.com/support

Commands:
Appendix D. Revision History Revision History Revision 0.1-95 Mon Aug 05 2018 Marie Dolezelova Version for 7.7 GA publication. Revision 0.1-87 Wed Jul 26 2017 Jana Heves Version for 7.4 GA publication. Revision 0.1-86 Mon Oct 17 2016 Marie Dolezelova Version for 7.3 GA publication. Revision 0.1-85 Mon Oct 17 2016 Marie Dolezelova Version for 7.3 GA publication. Revision 0.1-84 Wed 17 Aug 2016 Marie Dolezelova Red Hat Enterprise Linux 7.3 Beta release of the book. Revision 0.1-83 Fri 01 Apr 2016 Jana Heves Republish reflecting the rebase of GNOME to version 3.14. Revision 0.1-82 Wed 11 Nov 2015 Jana Heves Red Hat Enterprise Linux 7.2 release of the book. Revision 0.1-80 Wed 24 Jun 2015 Petr Kovar Added a link to the Anaconda Customization Guide for Red Hat Enterprise Linux 7. Revision 0.1-78 Tue 07 Apr 2015 Petr Kovar Added section Allowing and Disallowing Online Accounts . Revision 0.1-76 Tue 17 Feb 2015 Petr Kovar Red Hat Enterprise Linux 7.1 release of the book. Revision 0.1-74 Thu 04 Dec 2014 Petr Kovar Red Hat Enterprise Linux 7.1 Beta release of the book. Revision 0.1-69 Mon 02 Jun 2014 Petr Kovar Red Hat Enterprise Linux 7.0 release of the book. Revision 0.1-35 Wed 11 Dec 2013 Petr Kovar Red Hat Enterprise Linux 7.0 Beta release of the book.

Commands:
probe::tcpmib.OutRsts Name probe::tcpmib.OutRsts - Count the sending of a reset packet Synopsis tcpmib.OutRsts Values sk pointer to the struct sock being acted on op value to be added to the counter (default value of 1) Description The packet pointed to by skb is filtered by the function tcpmib_filter_key . If the packet passes the filter is is counted in the global OutRsts (equivalent to SNMP's MIB TCP_MIB_OUTRSTS)

Commands: