mtpti5iD/redhat-docs_dataset huggingface dataset:
1.3. Before Setting Up GFS2 Before you install and set up GFS2, note the following key characteristics of your GFS2 file systems: GFS2 nodes Determine which nodes in the cluster will mount the GFS2 file systems. Number of file systems Determine how many GFS2 file systems to create initially. (More file systems can be added later.) File system name Determine a unique name for each file system. The name must be unique for all lock_dlm file systems over the cluster. Each file system name is required in the form of a parameter variable. For example, this book uses file system names mydata1 and mydata2 in some example procedures. Journals Determine the number of journals for your GFS2 file systems. One journal is required for each node that mounts a GFS2 file system. GFS2 allows you to add journals dynamically at a later point as additional servers mount a file system. For information on adding journals to a GFS2 file system, see Section 3.6, "Adding Journals to a GFS2 File System" . Storage devices and partitions Determine the storage devices and partitions to be used for creating logical volumes (using CLVM) in the file systems. Time protocol Make sure that the clocks on the GFS2 nodes are synchronized. It is recommended that you use the Precision Time Protocol (PTP) or, if necessary for your configuration, the Network Time Protocol (NTP) software provided with your Red Hat Enterprise Linux distribution. Note The system clocks in GFS2 nodes must be within a few minutes of each other to prevent unnecessary inode time stamp updating. Unnecessary inode time stamp updating severely impacts cluster performance. Note You may see performance problems with GFS2 when many create and delete operations are issued from more than one node in the same directory at the same time. If this causes performance problems in your system, you should localize file creation and deletions by a node to directories specific to that node as much as possible. For further recommendations on creating, using, and maintaining a GFS2 file system. see Chapter 2, GFS2 Configuration and Operational Considerations .

Commands:
Chapter 4. Production phases Full Support Phase During the Full Support Phase, Red Hat will provide: Qualified critical and important security fixes Urgent and high priority bug fixes Select enhanced software functionality This will be delivered in the form of sub-minor releases. A release of {HubName} is supported under the Full Support Phase for 6 months after its initial release. Maintenance Support 1 Phase During the Maintenance Support 1 Phase, Red Hat will provide: Qualified critical security fixes Urgent bug fixes These fixes will be delivered in the form of sub-minor releases. A release of {HubName} is supported under the Maintenance Support 1 Phase for 6 months after it leaves the Full Support Phase. Maintenance Support 2 Phase During the Maintenance Support 2 Phase, Red Hat will provide: Qualified critical security fixes These fixes will be delivered in the form of sub-minor releases. A release of {HubName} is supported under the Maintenance Support 2 Phase for 6 months after it leaves the Maintenance Support 1 Phase. All updates are provided at Red Hat's discretion.

Commands:
7.132. logrotate 7.132.1. RHBA-2012:1172 - logrotate bug fix update Updated logrotate packages that fix one bug are now available for Red Hat Enterprise Linux 6. The logrotate utility simplifies the administration of multiple log files, allowing the automatic rotation, compression, removal, and mailing of log files. Bug Fix BZ# 827570 Attempting to send a file to a specific e-mail address failed if the "mailfirst" and "delaycompress" options were used at the same time. This was because logrotate searched for a file with the "gz" suffix, however the file had not yet been compressed. The underlying source code has been modified, and logrotate correctly finds and sends the file under these circumstances. All users of logrotate are advised to upgrade to these updated packages, which fix this bug.

Commands:
probe::nfsd.read Name probe::nfsd.read - NFS server reading data from a file for client Synopsis nfsd.read Values offset the offset of file vlen read blocks file argument file, indicates if the file has been opened. fh file handle (the first part is the length of the file handle) count read bytes client_ip the ip address of client size read bytes vec struct kvec, includes buf address in kernel address and length of each buffer

Commands:
Chapter 14. Log Record Fields The following fields can be present in log records exported by the logging subsystem. Although log records are typically formatted as JSON objects, the same data model can be applied to other encodings. To search these fields from Elasticsearch and Kibana, use the full dotted field name when searching. For example, with an Elasticsearch /_search URL , to look for a Kubernetes pod name, use /_search/q=kubernetes.pod_name:name-of-my-pod . The top level fields may be present in every record.

Commands:
18.2. Differences between iptables and ipchains At first glance, ipchains and iptables appear to be quite similar. Both methods of packet filtering use chains of rules operating within the Linux kernel to decide what to do with packets that match the specified rule or set of rules. However, iptables offers a more extensible way of filtering packets, giving the administrator a greater amount of control without building a great deal of complexity into the system. Specifically, users comfortable with ipchains should be aware of the following significant differences between ipchains and iptables before attempting to use iptables : Under iptables , each filtered packet is processed using rules from only one chain rather than multiple chains. For instance, a FORWARD packet coming into a system using ipchains would have to go through the INPUT, FORWARD, and OUTPUT chains to move along to its destination. However, iptables only sends packets to the INPUT chain if they are destined for the local system and only sends them to the OUTPUT chain if the local system generated the packets. For this reason, it is important to place the rule designed to catch a particular packet within the rule that actually handles the packet. The DENY target has been changed to DROP. In ipchains , packets that matched a rule in a chain could be directed to the DENY target. This target must be changed to DROP under iptables . Order matters when placing options in a rule. With ipchains , the order of the rule options does not matter. The iptables command uses stricter syntax. In iptables commands, the protocol (ICMP, TCP, or UDP) must be specified before the source or destination ports. When specifying network interfaces to be used with a rule, you must only use incoming interfaces ( -i option) with INPUT or FORWARD chains and outgoing interfaces ( -o option) with FORWARD or OUTPUT chains. This is necessary because OUTPUT chains are no longer used by incoming interfaces, and INPUT chains are not seen by packets moving through outgoing interfaces. This is not a comprehensive list of the changes, given that iptables is a fundamentally rewritten network filter. For more specific information, refer to the Linux Packet Filtering HOWTO referenced in Section 18.7, "Additional Resources" .

Commands:
Chapter 8. JSR-107 (JCache) API Starting with JBoss Data Grid 6.5 an implementation of the JCache 1.0.0 API ( JSR-107 ) is included. JCache specified a standard Java API for caching temporary Java objects in memory. Caching java objects can help get around bottlenecks arising from using data that is expensive to retrieve (i.e. DB or web service), or data that is hard to calculate. Caching these types of objects in memory can help speed up application performance by retrieving the data directly from memory instead of doing an expensive roundtrip or recalculation. This document specifies how to use JCache with JBoss Data Grid's implementation of the new specification, and explains key aspects of the API. Report a bug 8.1. Dependencies The JCache dependencies may either be defined in Maven or added to the classpath; both methods are described below: Option 1: Maven In order to use the JCache implementation the following dependencies need to be added to the Maven pom.xml depending on how it is used: embedded: remote: Option 2: Adding the necessary files to the classpath When not using Maven the necessary jar files must be on the classpath at runtime. Having these available at runtime may either be accomplished by embedding the jar files directly, by specifying them at runtime, or by adding them into the container used to deploy the application. Procedure 8.1. Embedded Mode Download the Red Hat JBoss Data Grid 6.6.1 Library from the Red Hat Customer Portal. Extract the downloaded archive to a local directory. Locate the following files: jboss-datagrid-6.6.1-library/infinispan-embedded-6.4.1.Final-redhat-1.jar jboss-datagrid-6.6.1-library/lib/cache-api-1.0.0.redhat-1.jar Ensure both of the above jar files are on the classpath at runtime. Procedure 8.2. Remote Mode Download the Red Hat JBoss Data Grid 6.6.1 Hot Rod Java Client from the Red Hat Customer Portal. Extract the downloaded archive to a local directory. Locate the following files: jboss-datagrid-6.6.1-remote-java-client/infinispan-remote-6.4.1.Final-redhat-1.jar jboss-datagrid-6.6.1-remote-java-client/cache-api-1.0.0.redhat-1.jar Ensure both of the above jar files are on the classpath at runtime. Report a bug

Commands:
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-embedded</artifactId> <version>USD{infinispan.version}</version> </dependency> <dependency> <groupId>javax.cache</groupId> <artifactId>cache-api</artifactId> <version>1.0.0.redhat-1</version> </dependency>
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-remote</artifactId> <version>USD{infinispan.version}</version> </dependency> <dependency> <groupId>javax.cache</groupId> <artifactId>cache-api</artifactId> <version>1.0.0.redhat-1</version> </dependency>
Chapter 39. InternalServiceTemplate schema reference Used in: CruiseControlTemplate , KafkaBridgeTemplate , KafkaClusterTemplate , KafkaConnectTemplate , ZookeeperClusterTemplate Property Description metadata Metadata applied to the resource. MetadataTemplate ipFamilyPolicy Specifies the IP Family Policy used by the service. Available options are SingleStack , PreferDualStack and RequireDualStack . SingleStack is for a single IP family. PreferDualStack is for two IP families on dual-stack configured clusters or a single IP family on single-stack clusters. RequireDualStack fails unless there are two IP families on dual-stack configured clusters. If unspecified, OpenShift will choose the default value based on the service type. string (one of [RequireDualStack, SingleStack, PreferDualStack]) ipFamilies Specifies the IP Families used by the service. Available options are IPv4 and IPv6 . If unspecified, OpenShift will choose the default value based on the ipFamilyPolicy setting. string (one or more of [IPv6, IPv4]) array

Commands:
13.2. Setting up the Job Scheduler The Certificate Manager can execute a job only if the Job Scheduler is enabled. The job settings, such as enabling the job schedule, setting the frequency, and enabling the job modules, can be done through the Certificate System CA Console or through editing the CS.cfg file. To turn the Job Scheduler on: Open the Certificate Manager Console. In the Configuration tab navigation tree, click Job Scheduler . This opens the General Settings tab, which shows whether the Job Scheduler is currently enabled. Click the Enable Jobs Schedule checkbox to enable or disable the Job Scheduler. Disabling the Job Scheduler turns off all the jobs. Set the frequency which the scheduler checks for jobs in the Check Frequency field. The frequency is how often the Job Scheduler daemon thread wakes up and calls the configured jobs that meet the cron specification. By default, it is set to one minute. Note The window for entering this information may be too small to see the input. Drag the corners of the Certificate Manager Console to enlarge the entire window. Click Save . Note pkiconsole is being deprecated.

Commands:
pkiconsole https://server.example.com:8443/ca
4.7. Kernel Kernel Media support The following features are presented as Technology Previews: The latest upstream video4linux Digital video broadcasting Primarily infrared remote control device support Various webcam support fixes and improvements Package: kernel-2.6.32-431 Linux (NameSpace) Container [LXC] Linux containers provide a flexible approach to application runtime containment on bare-metal systems without the need to fully virtualize the workload. Red Hat Enterprise Linux 6 provides application level containers to separate and control the application resource usage policies via cgroups and namespaces. This release includes basic management of container life-cycle by allowing creation, editing and deletion of containers via the libvirt API and the virt-manager GUI. Linux Containers are a Technology Preview. Packages: libvirt-0.9.10-21 , virt-manager-0.9.0-14 Diagnostic pulse for the fence_ipmilan agent, BZ# 655764 A diagnostic pulse can now be issued on the IPMI interface using the fence_ipmilan agent. This new Technology Preview is used to force a kernel dump of a host if the host is configured to do so. Note that this feature is not a substitute for the off operation in a production cluster. Package: fence-agents-3.1.5-35

Commands:
E.2.3. Features of GRUB GRUB contains several features that make it preferable to other boot loaders available for the x86 architecture. Below is a partial list of some of the more important features: GRUB provides a true command-based, pre-OS environment on x86 machines. This feature affords the user maximum flexibility in loading operating systems with specified options or gathering information about the system. For years, many non-x86 architectures have employed pre-OS environments that allow system booting from a command line. GRUB supports Logical Block Addressing (LBA) mode. LBA places the addressing conversion used to find files in the hard drive's firmware, and is used on many IDE and all SCSI hard devices. Before LBA, boot loaders could encounter the 1024-cylinder BIOS limitation, where the BIOS could not find a file after the 1024 cylinder head of the disk. LBA support allows GRUB to boot operating systems from partitions beyond the 1024-cylinder limit, so long as the system BIOS supports LBA mode. Most modern BIOS revisions support LBA mode. GRUB can read ext2 partitions. This functionality allows GRUB to access its configuration file, /boot/grub/grub.conf , every time the system boots, eliminating the need for the user to write a new version of the first stage boot loader to the MBR when configuration changes are made. The only time a user needs to reinstall GRUB on the MBR is if the physical location of the /boot/ partition is moved on the disk.

Commands:
3.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. Label files with the samba_share_t type to allow Samba to share them. Only label files you have created, and do not relabel system files with the samba_share_t type: Booleans can be enabled to share such files and directories. SELinux allows Samba to write to files labeled with the samba_share_t type, as long as /etc/samba/smb.conf and Linux permissions are set accordingly. The samba_etc_t type is used on certain files in /etc/samba/ , such as smb.conf . Do not manually label files with the samba_etc_t type. If files in /etc/samba/ are not labeled correctly, run the restorecon -R -v /etc/samba command as the root user to restore such files to their default contexts. If /etc/samba/smb.conf is not labeled with the samba_etc_t type, the service smb start command may fail and an SELinux denial may be logged. The following is an example denial when /etc/samba/smb.conf was labeled with the httpd_sys_content_t type:

Commands:
setroubleshoot: SELinux is preventing smbd (smbd_t) "read" to ./smb.conf (httpd_sys_content_t). For complete SELinux messages. run sealert -l deb33473-1069-482b-bb50-e4cd05ab18af
Chapter 7. Deleting virtual machines To delete virtual machines in RHEL 9, use the command line or the web console GUI . 7.1. Deleting virtual machines by using the command line To delete a virtual machine (VM), you can remove its XML configuration and associated storage files from the host by using the command line. Follow the procedure below: Prerequisites Back up important data from the VM. Shut down the VM. Make sure no other VMs use the same associated storage. Procedure Use the virsh undefine utility. For example, the following command removes the guest1 VM, its associated storage volumes, and non-volatile RAM, if any. Additional resources virsh undefine --help command virsh man page on your system 7.2. Deleting virtual machines by using the web console To delete a virtual machine (VM) and its associated storage files from the host to which the RHEL 9 web console is connected with, follow the procedure below: Prerequisites You have installed the RHEL 9 web console. You have enabled the cockpit service. Your user account is allowed to log in to the web console. For instructions, see Installing and enabling the web console . You have installed the RHEL 9 web console. You have enabled the cockpit service. Your user account is allowed to log in to the web console. For instructions, see Installing and enabling the web console . The web console VM plug-in is installed on your system . Back up important data from the VM. Make sure no other VM uses the same associated storage. Optional: Shut down the VM. Procedure Log in to the RHEL 9 web console. For details, see Logging in to the web console . In the Virtual Machines interface, click the Menu button ... of the VM that you want to delete. A drop down menu appears with controls for various VM operations. Click Delete . A confirmation dialog appears. Optional: To delete all or some of the storage files associated with the VM, select the checkboxes to the storage files you want to delete. Click Delete . The VM and any selected storage files are deleted.

Commands:
virsh undefine guest1 --remove-all-storage --nvram Domain 'guest1' has been undefined Volume 'vda'(/home/images/guest1.qcow2) removed.
Chapter 1. New features and enhancements Red Hat JBoss Core Services (JBCS) 2.4.57 Service Pack 5 includes the following new features and enhancements. 1.1. JBCS support for UnsafeAllow3F flag for URL rewrites JBCS 2.4.57 Service Pack 5 introduces support for the UnsafeAllow3F flag, which you can specify as part of the RewriteRule directive of the mod_rewrite module. You must set the UnsafeAllow3F flag if you want to allow a URL rewrite to continue when the HTTP request has an encoded question mark, %3f , and the rewritten result has a ? character in the substitution. This flag protects the HTTP request from a malicious URL that could take advantage of a capture and re-substitution of the encoded question mark. For more information, see RewriteRule Flags: UnsafeAllow3F . 1.2. JBCS support for UnsafePrefixStat flag for URL rewrites JBCS 2.4.57 Service Pack 5 introduces support for the UnsafePrefixStat flag, which you can specify as part of the RewriteRule directive of the mod_rewrite module. You must set the UnsafePrefixStat flag in server-scoped substitutions that start with a variable or back-reference and resolve to a file-system path. These substitutions are not prefixed with the document root. This flag protects the HTTP request from a malicious URL that could cause the expanded substitution to map to an unexpected file-system location. For more information, see RewriteRule Flags: UnsafePrefixStat .

Commands:
1.4. Installing Red Hat High Availability Add-On software To install Red Hat High Availability Add-On software, you must have entitlements for the software. If you are using the luci configuration GUI, you can let it install the cluster software. If you are using other tools to configure the cluster, secure and install the software as you would with Red Hat Enterprise Linux software. You can use the following yum install command to install the Red Hat High Availability Add-On software packages: Note that installing only the rgmanager will pull in all necessary dependencies to create an HA cluster from the HighAvailability channel. The lvm2-cluster and gfs2-utils packages are part of ResilientStorage channel and may not be needed by your site. Warning After you install the Red Hat High Availability Add-On packages, you should ensure that your software update preferences are set so that nothing is installed automatically. Installation on a running cluster can cause unexpected behaviors. Upgrading Red Hat High Availability Add-On Software It is possible to upgrade the cluster software on a given major release of Red Hat Enterprise Linux without taking the cluster out of production. Doing so requires disabling the cluster software on one host at a time, upgrading the software, and restarting the cluster software on that host. Shut down all cluster services on a single cluster node. For instructions on stopping cluster software on a node, see Section 9.1.2, "Stopping Cluster Software" . It may be desirable to manually relocate cluster-managed services and virtual machines off of the host prior to stopping rgmanager . Execute the yum update command to update installed packages. Reboot the cluster node or restart the cluster services manually. For instructions on starting cluster software on a node, see Section 9.1.1, "Starting Cluster Software" .

Commands:
yum install rgmanager lvm2-cluster gfs2-utils
Chapter 4. Technology previews This part provides a list of all Technology Previews available in Red Hat Satellite 6.15. For information on Red Hat scope of support for Technology Preview features, see Technology Preview Features Support Scope . OpenShift Virtualization plugin You can provision virtual machines by using the OpenShift Virtualization plugin. Jira:SAT-18663 OVAL / CVE Reporting Support Satellite now includes the ability to scan systems for vulnerabilities using the OVAL standard data feed provided by Red Hat. foreman_openscap contains the API to upload the OVAL content used to trigger the OVAL oscap scans. The results are parsed for CVEs and sent to Satellite which then generates reports of managed hosts and the CVEs that effect them. Note that this feature is no longer available in future releases. Jira:SAT-21011 Kernel execution template You can use the kernel execution (kexec) provisioning template for PXE-less boot methods. Jira:SAT-21012

Commands:
9.3.5. Tuning vCPU Pinning with virsh Important These are example commands only. You will need to substitute values according to your environment. The following example virsh command will pin the vcpu thread (rhel6u4) which has an ID of 1 to the physical CPU 2: You can also obtain the current vcpu pinning configuration with the virsh command. For example:

Commands:
% virsh vcpupin rhel6u4 1 2
% virsh vcpupin rhel6u4