mtpti5iD/redhat-docs_dataset huggingface dataset:
8.27. certmonger 8.27.1. RHBA-2014:1512 - certmonger bug fix and enhancement update Updated certmonger packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The certmonger service monitors certificates, warning of their impending expiration, and optionally attempting to re-enroll with supported Certificate Authorities (CA). This update also fixes the following bugs: Note The certmonger packages have been upgraded to upstream version 0.75.13, which provides a number of bug fixes and enhancements over the version including: - support for retrieving an IPA server's root certificate and optionally storing it to specified locations - improvements in how the certmonger daemon handles disconnection from the system message bus - improvements in how the certmonger daemon runs enrollment helpers and parses results returned by them - fixed bug causing unexpected termination if an attempt to save a certificate failed - fixed incorrect use of the libdbus library that triggered the _dbus_abort() function - fixed segmentation fault with incorrectly structured entries in the /var/lib/certmonger/cas/ directory (BZ# 1098208 , BZ# 948993 , BZ# 1032760 , BZ# 1103090 , BZ# 1115831 ) This update also fixes the following bugs: Bug Fix BZ# 1125342 This update fixes the implementation of the remove_known_ca dbus call in the certmonger package to prevent the certmonger daemon from terminating unexpectedly when called by remove_known_ca. The certmonger packages have been upgraded to upstream version 0.75.13, which provides a number of bug fixes and enhancements over the version including: - support for retrieving an IPA server's root certificate and optionally storing it to specified locations - improvements in how the certmonger daemon handles disconnection from the system message bus - improvements in how the certmonger daemon runs enrollment helpers and parses results returned by them - fixed bug causing unexpected termination if an attempt to save a certificate failed - fixed incorrect use of the libdbus library that triggered the _dbus_abort() function - fixed segmentation fault with incorrectly structured entries in the /var/lib/certmonger/cas/ directory (BZ#1098208, BZ#948993, BZ#1032760, BZ#1103090, BZ#1115831) In addition, this update adds the following Enhancement BZ# 1027265 This update adds the certmonger_selinux manual page to document the effect that SELinux has in limiting the allowed access to locations for the certmonger daemon. Also, the selinux.txt document has been added to the certmonger package to provide more details about interaction with SELinux. A reference to certmonger_selinux and selinux.txt has been added to other certmonger man pages. Users of certmonger are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
16.4.5. Augeas and libguestfs Scripting Combining libguestfs with Augeas can help when writing scripts to manipulate Linux guest virtual machine configuration. For example, the following script uses Augeas to parse the keyboard configuration of a guest virtual machine, and to print out the layout. Note that this example only works with guest virtual machines running Red Hat Enterprise Linux: Augeas can also be used to modify configuration files. You can modify the above script to change the keyboard layout: Note the three changes between the two scripts: The --ro option has been removed in the second example, giving the ability to write to the guest virtual machine. The aug-get command has been changed to aug-set to modify the value instead of fetching it. The new value will be "gb" (including the quotes). The aug-save command is used here so Augeas will write the changes out to disk. Note More information about Augeas can be found on the website http://augeas.net . guestfish can do much more than we can cover in this introductory document. For example, creating disk images from scratch: Or copying out whole directories from a disk image: For more information see the man page guestfish(1).

Commands:
#!/bin/bash - set -e guestname="USD1" guestfish -d "USD1" -i --ro <<'EOF' aug-init / 0 aug-get /files/etc/sysconfig/keyboard/LAYOUT EOF
#!/bin/bash - set -e guestname="USD1" guestfish -d "USD1" -i <<'EOF' aug-init / 0 aug-set /files/etc/sysconfig/keyboard/LAYOUT '"gb"' aug-save EOF
guestfish -N fs
><fs> copy-out /home /tmp/home
Chapter 26. Storage Driver Updates The md driver has been updated to the latest upstream version. The nvme driver has been updated to version 0.10. The O2Micro card reader driver, which specifically enables the SDHCI card reader to work on the O2Micro chips, has been updated to the latest upstream version. The ipr driver, used to enable new SAS VRAID adapters on POWER, has been updated to version 2.6.3. The tcm_fc.ko (FCoE fabric) driver has been updated to the latest upstream version. The qla2xxx driver has been updated to version 8.07.00.26.06.8-k. The LPFC (Avago Emulex Fibrechannel) driver has been updated to version 11.0.0.4. The megaraid_sas driver has been updated to version 06.810.09.00-rh1. The mpt2sas driver has been updated to version 20.102.00.00. The mpt3sas driver has been updated to version 09.102.00.00-rh. The hpsa (HP Smart Array SCSI driver) driver has been updated to version 3.4.10-0-RH1.

Commands:
9.7.5. NFS over RDMA NFS over Remote Direct Memory Access (NFSoRDMA) is best suited for CPU-intensive workloads where a large amount of data needs to be transferred. NFSoRDMA is usually used over an InfiniBand fiber, which provides higher performance with lower latency. The data movement offload feature available with RDMA reduces the amount of data copied around. Procedure 9.2. Enabling RDMA transport in the NFS server Ensure the RDMA RPM is installed and the RDMA service is enabled: Ensure the package that provides the nfs-rdma service is installed and the service is enabled: Ensure that the RDMA port is set to the preferred port (default for Red Hat Enterprise Linux 6 is 2050 ): edit the /etc/rdma/rdma.conf file to set NFSoRDMA_LOAD=yes and NFSoRDMA_PORT to the desired port. Set up the exported file system as normal for NFS mounts. Procedure 9.3. Enabling RDMA from the client Ensure the RDMA RPM is installed and the RDMA service is enabled: Mount the NFS exported partition using the RDMA option on the mount call. The port option can optionally be added to the call. The following Red Hat Knowledgebase article provides on overview of cards that use kernel modules supported for NFSoRDMA: What RDMA hardware is supported in Red Hat Enterprise Linux?

Commands:
yum install rdma; chkconfig --level 2345 rdma on
yum install rdma; chkconfig --level 345 nfs-rdma on
yum install rdma; chkconfig --level 2345 rdma on
mount -t nfs -o rdma,port= port_number
function::ipmib_filter_key Name function::ipmib_filter_key - Default filter function for ipmib.* probes Synopsis Arguments skb pointer to the struct sk_buff op value to be counted if skb passes the filter SourceIsLocal 1 is local operation and 0 is non-local operation Description This function is a default filter function. The user can replace this function with their own. The user-supplied filter function returns an index key based on the values in skb . A return value of 0 means this particular skb should be not be counted.

Commands:
ipmib_filter_key:long(skb:long,op:long,SourceIsLocal:long)
6.3. RHEA-2013:0422 - new packages: libjpeg-turbo New libjpeg-turbo packages are now available for Red Hat Enterprise Linux 6. The libjpeg-turbo packages contain a library of functions for manipulating JPEG images. They also contain simple client programs for accessing the libjpeg functions. These packages provide the same functionality and API as libjpeg but with better performance. This enhancement update adds the libjpeg-turbo packages to Red Hat Enterprise Linux 6. (BZ#788687) All users who require libjpeg-turbo are advised to install these new packages.

Commands:
Providing feedback on Red Hat documentation We appreciate your input on our documentation. Tell us how we can make it better. Providing documentation feedback in Jira Use the Create Issue form to provide feedback on the documentation for Red Hat OpenStack Services on OpenShift (RHOSO) or earlier releases of {osp_long} ({osp_acro}). When you create an issue for RHOSO or {osp_acro} documents, the issue is recorded in the RHOSO Jira project, where you can track the progress of your feedback. To complete the Create Issue form, ensure that you are logged in to Jira. If you do not have a Red Hat Jira account, you can create an account at https://issues.redhat.com . Click the following link to open a Create Issue page: Create Issue Complete the Summary and Description fields. In the Description field, include the documentation URL, chapter or section number, and a detailed description of the issue. Do not modify any other fields in the form. Click Create .

Commands:
Chapter 51. TlsSidecar schema reference Used in: CruiseControlSpec , EntityOperatorSpec Full list of TlsSidecar schema properties Configures a TLS sidecar, which is a container that runs in a pod, but serves a supporting purpose. In Streams for Apache Kafka, the TLS sidecar uses TLS to encrypt and decrypt communication between components and ZooKeeper. The TLS sidecar is used in the Entity Operator. The TLS sidecar is configured using the tlsSidecar property in Kafka.spec.entityOperator . The TLS sidecar supports the following additional options: image resources logLevel readinessProbe livenessProbe The resources property specifies the memory and CPU resources allocated for the TLS sidecar. The image property configures the container image which will be used. The readinessProbe and livenessProbe properties configure healthcheck probes for the TLS sidecar. The logLevel property specifies the logging level. The following logging levels are supported: emerg alert crit err warning notice info debug The default value is notice . Example TLS sidecar configuration apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster spec: # ... entityOperator: # ... tlsSidecar: resources: requests: cpu: 200m memory: 64Mi limits: cpu: 500m memory: 128Mi # ... 51.1. TlsSidecar schema properties Property Property type Description image string The docker image for the container. livenessProbe Probe Pod liveness checking. logLevel string (one of [emerg, debug, crit, err, alert, warning, notice, info]) The log level for the TLS sidecar. Default value is notice . readinessProbe Probe Pod readiness checking. resources ResourceRequirements CPU and memory resources to reserve.

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster spec: # entityOperator: # tlsSidecar: resources: requests: cpu: 200m memory: 64Mi limits: cpu: 500m memory: 128Mi #
12.2. LVM Partition Management The following commands can be found by issuing lvm help at a command prompt. Table 12.2. LVM commands Command Description dumpconfig Dump the active configuration formats List the available metadata formats help Display the help commands lvchange Change the attributes of logical volume(s) lvcreate Create a logical volume lvdisplay Display information about a logical volume lvextend Add space to a logical volume lvmchange Due to use of the device mapper, this command has been deprecated lvmdiskscan List devices that may be used as physical volumes lvmsadc Collect activity data lvmsar Create activity report lvreduce Reduce the size of a logical volume lvremove Remove logical volume(s) from the system lvrename Rename a logical volume lvresize Resize a logical volume lvs Display information about logical volumes lvscan List all logical volumes in all volume groups pvchange Change attributes of physical volume(s) pvcreate Initialize physical volume(s) for use by LVM pvdata Display the on-disk metadata for physical volume(s) pvdisplay Display various attributes of physical volume(s) pvmove Move extents from one physical volume to another pvremove Remove LVM label(s) from physical volume(s) pvresize Resize a physical volume in use by a volume group pvs Display information about physical volumes pvscan List all physical volumes segtypes List available segment types vgcfgbackup Backup volume group configuration vgcfgrestore Restore volume group configuration vgchange Change volume group attributes vgck Check the consistency of a volume group vgconvert Change volume group metadata format vgcreate Create a volume group vgdisplay Display volume group information vgexport Unregister a volume group from the system vgextend Add physical volumes to a volume group vgimport Register exported volume group with system vgmerge Merge volume groups vgmknodes Create the special files for volume group devices in /dev/ vgreduce Remove a physical volume from a volume group vgremove Remove a volume group vgrename Rename a volume group vgs Display information about volume groups vgscan Search for all volume groups vgsplit Move physical volumes into a new volume group version Display software and driver version information

Commands:
Preface Thank you for your interest in Red Hat Ansible Automation Platform. Ansible Automation Platform is a commercial offering that helps teams manage complex multi-tier deployments by adding control, knowledge, and delegation to Ansible-powered environments. This guide helps you to understand the requirements and processes behind setting up an automation mesh on a operator-based installation of Red Hat Ansible Automation Platform. This document has been updated to include information for the latest release of Ansible Automation Platform.

Commands:
2.8.6. Malicious Software and Spoofed IP Addresses More elaborate rules can be created that control access to specific subnets, or even specific nodes, within a LAN. You can also restrict certain dubious applications or programs such as Trojans, worms, and other client/server viruses from contacting their server. For example, some Trojans scan networks for services on ports from 31337 to 31340 (called the elite ports in cracking terminology). Since there are no legitimate services that communicate via these non-standard ports, blocking them can effectively diminish the chances that potentially infected nodes on your network independently communicate with their remote master servers. The following rules drop all TCP traffic that attempts to use port 31337: You can also block outside connections that attempt to spoof private IP address ranges to infiltrate your LAN. For example, if your LAN uses the 192.168.1.0/24 range, you can design a rule that instructs the Internet-facing network device (for example, eth0) to drop any packets to that device with an address in your LAN IP range. Because it is recommended to reject forwarded packets as a default policy, any other spoofed IP address to the external-facing device (eth0) is rejected automatically. Note There is a distinction between the DROP and REJECT targets when dealing with appended rules. The REJECT target denies access and returns a connection refused error to users who attempt to connect to the service. The DROP target, as the name implies, drops the packet without any warning. Administrators can use their own discretion when using these targets.

Commands:
~]# iptables -A OUTPUT -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP ~]# iptables -A FORWARD -o eth0 -p tcp --dport 31337 --sport 31337 -j DROP
~]# iptables -A FORWARD -s 192.168.1.0/24 -i eth0 -j DROP
4.3.2. Creating a Virtual Machine with Virtual Machine Manager Follow these steps to create a Red Hat Enterprise Linux 7 virtual machine on Virtual Machine Manager . Procedure 4.2. Creating a guest virtual machine with Virtual Machine Manager Open Virtual Machine Manager Click Applications System Tools Virtual Machine Manager or Open the terminal and use the virt-manager . Create a new virtual machine Click to open the New VM wizard. Specify name and installation method In Step 1, type in a virtual machine name and choose an installation type to install the guest virtual machine's operating system. Figure 4.2. Name virtual machine and select installation method For this tutorial, select Local install media (ISO image) . This installation method uses an image of an installation disk (in this case an .iso file). Click Forward to continue to the step. Locate installation media Select the Use ISO Image option. Click Browse Browse Local buttons. Locate the ISO downloaded in Procedure 4.1, "Installing the virtualization packages with yum " on your machine. Select the ISO file and click Open . Ensure that Virtual Machine Manager correctly detected the OS type. If not, uncheck Automatically detect operating system based on install media and select Linux from the OS type drop-down and Red Hat Enterprise Linux 7 from the Version drop-down. Figure 4.3. Local ISO image installation Configure memory and CPU You can use step 3 of the wizard to configure the amount of memory and the number of CPUs to allocate to the virtual machine. The wizard shows the number of CPUs and amount of memory available to allocate. For this tutorial, leave the default settings and click Forward . Figure 4.4. Configuring CPU and Memory Configure storage Using step 4 of the wizard, you can assign storage to the guest virtual machine. The wizard shows options for storage, including where to store the virtual machine on the host machine. For this tutorial, leave the default settings and click Forward . Figure 4.5. Configuring storage Review the configuration Using step 5 of the wizard, you can configure the virtualization type, and guest architecture, and networking settings. For this tutorial, verify the settings, and click Finish . Virtual Machine Manager will create a virtual machine with the specified hardware settings. Figure 4.6. Verifying the configuration After Virtual Machine Manager creates your Red Hat Enterprise Linux 7 virtual machine, the virtual machine's window will open, and the installation of the selected operating system will begin in it. Follow the instructions in the Red Hat Enterprise Linux 7 installer to complete the installation of the virtual machine's operating system. Note For help with Red Hat Enterprise Linux 7 installation, refer to the Red Hat Enterprise Linux 7 Installation Guide .

Commands:
4.10. Suspending Activity on a File System You can suspend write activity to a file system by using the dmsetup suspend command. Suspending write activity allows hardware-based device snapshots to be used to capture the file system in a consistent state. The dmsetup resume command ends the suspension. Usage Start Suspension End Suspension MountPoint Specifies the file system. Examples This example suspends writes to file system /mygfs2 . This example ends suspension of writes to file system /mygfs2 .

Commands:
dmsetup suspend MountPoint
dmsetup resume MountPoint
dmsetup suspend /mygfs2
dmsetup resume /mygfs2
Chapter 2. Architectures Red Hat Enterprise Linux 7.6 is distributed with the kernel version 3.10.0-957, which provides support for the following architectures: [1] 64-bit AMD 64-bit Intel IBM POWER7+ (big endian) IBM POWER8 (big endian) [2] IBM POWER8 (little endian) [3] IBM POWER9 (little endian) [4] [5] IBM Z [4] [6] 64-bit ARM [4] [1] Note that the Red Hat Enterprise Linux 7.6 installation is supported only on 64-bit hardware. Red Hat Enterprise Linux 7.6 is able to run 32-bit operating systems, including versions of Red Hat Enterprise Linux, as virtual machines. [2] Red Hat Enterprise Linux 7.6 POWER8 (big endian) are currently supported as KVM guests on Red Hat Enterprise Linux 7.6 POWER8 systems that run the KVM hypervisor, and on PowerVM. [3] Red Hat Enterprise Linux 7.6 POWER8 (little endian) is currently supported as a KVM guest on Red Hat Enterprise Linux 7.6 POWER8 systems that run the KVM hypervisor, and on PowerVM. In addition, Red Hat Enterprise Linux 7.6 POWER8 (little endian) guests are supported on Red Hat Enterprise Linux 7.6 POWER9 systems that run the KVM hypervisor in POWER8-compatibility mode on version 4.14 kernel using the kernel-alt package. [4] This architecture is supported with the kernel version 4.14, provided by the kernel-alt packages. For details, see the Red Hat Enterprise Linux 7.5 . [5] Red Hat Enterprise Linux 7.6 POWER9 (little endian) is currently supported as a KVM guest on Red Hat Enterprise Linux 7.6 POWER9 systems that run the KVM hypervisor on version 4.14 kernel using the kernel-alt package, and on PowerVM. [6] Red Hat Enterprise Linux 7.6 for IBM Z (both the 3.10 kernel version and the 4.14 kernel version) is currently supported as a KVM guest on Red Hat Enterprise Linux 7.6 for IBM Z hosts that run the KVM hypervisor on version 4.14 kernel using the kernel-alt package.

Commands:
4.67. fuse 4.67.1. RHBA-2011:1756 - fuse bug fix update An updated fuse package that fixes one bug is now available in Red Hat Enterprise Linux 6. The fuse package contains the file system in userspace utilities and libraries required for using fuse file systems. Bug Fix BZ# 723757 Prior to this update, fusermount used an incorrect path to unmount. As a result, fusermount was unable to unmount mounted fuse file systems. This update, modifies fusermount to use the correct mount path. Now, mounted fuse file systems can be successfully unmounted with fusermount. All users who use fuse file systems in their environment are advised to upgrade to this updated fuse package, which fixes this bug.

Commands:
24.3.2. Problems When You Try to Log In If you did not create a user account in the firstboot screens, switch to a console by pressing Ctrl + Alt + F2 , log in as root and use the password you assigned to root. If you cannot remember your root password, boot your system into single user mode by appending the boot option single to the zipl boot menu or by any other means to append kernel command line options at IPL. Once you have booted into single user mode and have access to the # prompt, you must type passwd root , which allows you to enter a new password for root. At this point you can type shutdown -r now to reboot the system with the new root password. If you cannot remember your user account password, you must become root. To become root, type su - and enter your root password when prompted. Then, type passwd <username> . This allows you to enter a new password for the specified user account. If the graphical login screen does not appear, check your hardware for compatibility issues. The Hardware Compatibility List can be found at:

Commands:
https://hardware.redhat.com/