mtpti5iD/redhat-docs_dataset huggingface dataset:
19.6.3. Related Books Sendmail Milters: A Guide for Fighting Spam by Bryan Costales and Marcia Flynt; Addison-Wesley - A good Sendmail guide that can help you customize your mail filters. Sendmail by Bryan Costales with Eric Allman et al.; O'Reilly & Associates - A good Sendmail reference written with the assistance of the original creator of Delivermail and Sendmail. Removing the Spam: Email Processing and Filtering by Geoff Mulligan; Addison-Wesley Publishing Company - A volume that looks at various methods used by email administrators using established tools, such as Sendmail and Procmail, to manage spam problems. Internet Email Protocols: A Developer's Guide by Kevin Johnson; Addison-Wesley Publishing Company - Provides a very thorough review of major email protocols and the security they provide. Managing IMAP by Dianna Mullet and Kevin Mullet; O'Reilly & Associates - Details the steps required to configure an IMAP server.

Commands:
7.57. gcc 7.57.1. RHBA-2015:1339 - gcc bug fix and enhancement update Updated gcc packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The gcc packages provide compilers for C, C++, Java, Fortran, Objective C, and Ada 95 GNU, as well as related support libraries. Bug Fixes BZ# 1190640 Previously, due to a bug in the stdarg functions optimization, the compiler could produce incorrect code. The problem occurred only when the va_list variable escaped a PHI node. This bug has been fixed, and the compiler now generates correct code. BZ# 1150606 Previously, when the vectorization optimization was enabled, the compiler could extract a scalar component of a vector with element types whose precision did not match the precision of their mode. Consequently, GCC could terminate unexpectedly while trying to vectorize a code that was using bit-fields. With this update, the compiler no longer vectorizes such code, and the code now compiles correctly. BZ# 1177458 Previously, the compiler did not properly handle incorrect usage of the PCH (Precompiled Headers) feature. When a PCH file was not included as the first include, the compiler terminated unexpectedly with a segmentation fault. The compiler has been fixed not to use such incorrect includes, and it no longer crashes in this scenario. BZ# 1134560 In versions of the GNU Fortran compiler, the type specifiers for Cray pointees were incorrectly overwritten by the type specifiers of components with the same name. Consequently, compiling failed with an error message. This bug has been fixed, and the Cray pointers are now handled correctly. Enhancement BZ# 1148120 The gcc hotpatch attribute implements support for online patching of multithreaded code on System z binaries. With this update, it is possible to select specific functions for hotpatching using a "function attribute" and to enable hotpatching for all functions using the "-mhotpatch=" command-line option. As enabled hotpatching has negative impact on software size and performance, it is recommended to use hotpatching for specific functions and not to enable hotpatch support in general. Users of gcc are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
24.5.4. Using the lscpu Command The lscpu command allows you to list information about CPUs that are present in the system, including the number of CPUs, their architecture, vendor, family, model, CPU caches, etc. To do so, type the following at a shell prompt: lscpu For example: For a complete list of available command-line options, see the lscpu (1) manual page.

Commands:
~]USD lscpu Architecture: x86_64 CPU op-mode(s): 32-bit, 64-bit Byte Order: Little Endian CPU(s): 4 On-line CPU(s) list: 0-3 Thread(s) per core: 1 Core(s) per socket: 4 Socket(s): 1 NUMA node(s): 1 Vendor ID: GenuineIntel CPU family: 6 Model: 23 Stepping: 7 CPU MHz: 1998.000 BogoMIPS: 4999.98 Virtualization: VT-x L1d cache: 32K L1i cache: 32K L2 cache: 3072K NUMA node0 CPU(s): 0-3
Configuring your Red Hat build of Quarkus applications by using a YAML file Red Hat build of Quarkus 3.15 Red Hat Customer Content Services

Commands:
<dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-config-yaml</artifactId> </dependency>
./mvnw quarkus:add-extension -Dextensions="quarkus-config-yaml"
Properties that configure the JDBC data source driver of your PostgreSQL data source quarkus: datasource: db-kind: postgresql jdbc: url: jdbc:postgresql://localhost:5432/quarkus_test username: quarkus_test password: quarkus_test Property that configures the URL of the endpoint to which the REST client sends requests quarkus: rest-client: org.acme.rest.client.ExtensionsService: url: https://stage.code.quarkus.io/api Property that configures the log message level for your application For configuration property names that use quotes, do not split the string inside the quotes quarkus: log: category: "io.quarkus.category": level: INFO
"%dev": quarkus: datasource: db-kind: postgresql jdbc: url: jdbc:postgresql://localhost:5432/quarkus_test username: quarkus_test password: quarkus_test
mach: 3 x: factor: 2.23694 display: mach: USD{mach} unit: name: "mph" factor: USD{x.factor}
├── config │ └── application.yaml ├── my-app-runner
quarkus: http: cors: ~: true methods: GET,PUT,POST
./mvnw quarkus:dev
Chapter 3. Red Hat build of OpenJDK features The latest Red Hat build of OpenJDK 21 release might include new features. Additionally, the latest release might enhance, deprecate, or remove features that originated from earlier Red Hat build of OpenJDK 21 releases. Note For all the other changes and security fixes, see OpenJDK 21.0.6 Released . Red Hat build of OpenJDK enhancements Red Hat build of OpenJDK 21 provides enhancements to features originally created in earlier releases of Red Hat build of OpenJDK. Option for jar command to avoid overwriting files when extracting an archive In earlier Red Hat build of OpenJDK releases, when the jar tool extracted files from an archive, the jar tool overwrote any existing files with the same name in the target directory. Red Hat build of OpenJDK 21.0.6 adds a new ‐k (or ‐‐keep-old-files ) option that you can use to ensure that the jar tool does not overwrite existing files. You can specify this new option in either short or long format. For example: jar xkf myfile.jar jar --extract ‐‐keep-old-files ‐‐file myfile.jar Note In Red Hat build of OpenJDK 21.0.6, the jar tool retains the old behavior by default. If you do not explicitly specify the ‐k (or ‐‐keep-old-files ) option, the jar tool automatically overwrites any existing files with the same name. See JDK-8335912 (JDK Bug System) and JDK bug system reference ID: JDK-8337499. IANA time zone database updated to version 2024b In Red Hat build of OpenJDK 21.0.6, the in-tree copy of the Internet Assigned Numbers Authority (IANA) time zone database is updated to version 2024b. This update is primarily concerned with improving historical data for Mexico, Mongolia, and Portugal. This update to the IANA database also includes the following changes: Asia/Choibalsan is an alias for Asia/Ulaanbaatar . The Middle European Time (MET) time zone is equal to Central European Time (CET). Some legacy time-zone IDs are mapped to geographical names rather than fixed offsets: Eastern Standard Time (EST) is mapped to America/Panama rather than -5:00 . Mountain Standard Time (MST) is mapped to America/Phoenix rather than -7:00 . Hawaii Standard Time (HST) is mapped to Pacific/Honolulu rather than -10:00 . Red Hat build of OpenJDK overrides the change in the legacy time-zone ID mappings by retaining the existing fixed-offset mapping. See JDK-8339637 (JDK Bug System) .

Commands:
32.5.2. Check the memory dump When the memory dump is finished and Red Hat Enterprise Linux is rebooted, you can check the memory dump with the crash command by opening the special device file. The following example shows how to check the memory dump which is saved on /dev/sdb1. Example 32.9. Checking Dump Integrity

Commands:
crash /usr/lib/debug/lib/modules/2.6.32-358.el6.x86_64/vmlinux /dev/sdb1
4.244. python-dmidecode 4.244.1. RHBA-2011:1589 - python-dmidecode bug fix update An updated python-dmidecode package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The python-dmidecode package provides a python extension module that uses the code-base of the dmidecode utility and presents the data as python data structures or as XML data using the libxml2 library. The python-dmidecode package has been upgraded to upstream version 3.10.13, which provides a number of bug fixes over the version. (BZ# 621567 ) Bug Fixes BZ# 627901 When trying to identify the processor type by performing a string comparison, Python terminated with a segmentation fault. This was caused by DMI tables which did not report the CPU processor information as a string and returned a NULL value instead. This update adds additional checks for NULL values before doing the string comparison. BZ# 646429 Previously, when calling the memcpy() function on the IBM System z machine which was under heavy memory load, a SIGILL signal was triggered. As a consequence, the complete Python interpreter core dumped. A signal handler was added to properly handle heavy memory loads. BZ# 667363 Prior to this update, when running the rhn_register utility, providing a valid user name and password, and clicking the Forward button, the tool terminated unexpectedly with a segmentation fault. This was caused by the dmi_processor_id() function not checking whether the version pointer was NULL. This update adds additional checks for NULL values, fixing the problem. All users of python-dmidecode are advised to upgrade to this updated package, which resolves these bugs.

Commands:
4.334. usbutils 4.334.1. RHBA-2011:1646 - usbutils bug fix and enhancement update An updated usbutils package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The usbutils package contains utilities for inspecting devices connected to a USB bus. The usbutils package has been upgraded to upstream version 003, which adds support for USB3 devices. Note: warning messages about short transfer on control endpoint and stalled endpoint can under circumstances be logged after the upgrade. This is the standard behavior of the xHCI driver and these messages can be safely ignored. This update also provides a number of bug fixes and enhancements over the version. (BZ# 725973 , BZ# 725096 ) Bug Fixes BZ# 725982 Previously, when running the "lsusb -t" command in a KVM guest, the lsusb utility terminated with a segmentation fault. The utility has been modified and now lists USB devices correctly. BZ# 730671 The FILES item in the lsusb(8) manual page displayed an incorrect path to the usb.ids file. This path has been changed to the correct /usr/share/hwdata/usb.ids path. All users of usbutils are advised to upgrade to this updated usbutils package, which fixes these bugs and adds these enhancements.

Commands:
1.4. Cluster Configuration Considerations When configuring a Red Hat High Availability Add-On cluster, you must take the following considerations into account: Red Hat does not support cluster deployments greater than 16 full cluster nodes. It is possible, however, to scale beyond that limit with remote nodes running the pacemaker_remote service. For information on the pacemaker_remote service, see Section 8.4, "The pacemaker_remote Service" . The use of Dynamic Host Configuration Protocol (DHCP) for obtaining an IP address on a network interface that is utilized by the corosync daemons is not supported. The DHCP client can periodically remove and re-add an IP address to its assigned interface during address renewal. This will result in corosync detecting a connection failure, which will result in fencing activity from any other nodes in the cluster using corosync for heartbeat connectivity.

Commands:
5.6. Resizing an Online Multipathed Device (RHEL 4.8 and later) In systems running RHEL 4.8 and later, is is possible to resize a multipath device while it is online. This allows you to resize the device when it is open, as when a file system is currently mounted. Use the following procedure to resize an online multipath device. Resize your physical device. Resize your paths. For SCSI devices, writing a 1 to the rescan file for the device causes the SCSI driver to rescan. You can use the following command: Resize your multipath device by running the multipath command: Your hardware setup may require that you temporarily take the actual storage offline in order to resize your physical device. If you take your storage offline and your multipath device is not set to queue when all paths are down, any I/O activity while your storage is offline will fail. You can work around this by executing the following command before taking your storage offline: After you resize your storage and take it back online, you must run the following command before resizing your paths:

Commands:
echo 1 > /sys/block/ device_name /device/rescan
multipath
dmsetup suspend --noflush device_name
dmsetup resume device_name
Chapter 7. Verifying the post-upgrade state of the RHEL 8 system This procedure lists Verification recommended to perform after an in-place upgrade to RHEL 8. Prerequisites The system has been upgraded following the steps described in Performing the upgrade from RHEL 7 to RHEL 8 and you have been able to log in to RHEL 8. Procedure After the upgrade completes, determine whether the system is in the required state, at least: Verify that the current OS version is Red Hat Enterprise Linux 8: Replace target_os_version with the target OS version, for example 8.10. Check the OS kernel version: The target_os should be either 8 or the target OS version, for example 8_10 . Note that .el8 is important and the version should not be earlier than 4.18.0-305. If you are using the Red Hat Subscription Manager: Verify that the correct product is installed: Replace target_os_version with the target OS version, for example 8.10. Verify that the release version is set to the target OS version immediately after the upgrade: Replace target_os_version with the target OS version, for example 8.10. Verify that network services are operational, for example, try to connect to a server using SSH. Check the post-upgrade status of your applications. In some cases, you may need to perform migration and configuration changes manually. For example, to migrate your databases, follow instructions in RHEL 8 Database servers documentation .

Commands:
cat /etc/redhat-release Red Hat Enterprise Linux release <target_os_version> (Ootpa)
uname -r 4.18.0-305.el <target_os> .x86_64
subscription-manager list --installed +-----------------------------------------+ Installed Product Status +-----------------------------------------+ Product Name: Red Hat Enterprise Linux for x86_64 Product ID: 479 Version: <target_os_version> Arch: x86_64 Status: Subscribed
subscription-manager release Release: <target_os_version>
2.4.4. Changing port numbers Depending on policy configuration, services may only be allowed to run on certain port numbers. Attempting to change the port a service runs on without changing policy may result in the service failing to start. Run the semanage port -l | grep -w "http_port_t" command as the root user to list the ports SELinux allows httpd to listen on: By default, SELinux allows http to listen on TCP ports 80, 443, 488, 8008, 8009, or 8443. If /etc/httpd/conf/httpd.conf is configured so that httpd listens on any port not listed for http_port_t , httpd fails to start. To configure httpd to run on a port other than TCP ports 80, 443, 488, 8008, 8009, or 8443: Edit /etc/httpd/conf/httpd.conf as the root user so the Listen option lists a port that is not configured in SELinux policy for httpd . The following example configures httpd to listen on the 10.0.0.1 IP address, and on TCP port 12345: Run the semanage port -a -t http_port_t -p tcp 12345 command as the root user to add the port to SELinux policy configuration. Run the semanage port -l | grep -w http_port_t command as the root user to confirm the port is added: If you no longer run httpd on port 12345, run the semanage port -d -t http_port_t -p tcp 12345 command as the root user to remove the port from policy configuration.

Commands:
~]# semanage port -l | grep -w http_port_t http_port_t tcp 80, 443, 488, 8008, 8009, 8443
Change this to Listen on specific IP addresses as shown below to prevent Apache from glomming onto all bound IP addresses (0.0.0.0) # #Listen 12.34.56.78:80 Listen 10.0.0.1:12345
~]# semanage port -l | grep -w http_port_t http_port_t tcp 12345, 80, 443, 488, 8008, 8009, 8443
4.2. Networking Mellanox SR-IOV Support Single Root I/O Virtualization (SR-IOV) is now supported as a Technology Preview in the Mellanox libmlx4 library and the following drivers: mlx_core mlx4_ib (InfiniBand protocol) mlx_en (Ethernet protocol) Package: kernel-2.6.32-335 Open multicast ping (Omping), BZ# 657370 Open Multicast Ping (Omping) is a tool to test the IP multicast functionality, primarily in the local network. This utility allows users to test IP multicast functionality and assists in the diagnosing if an issues is in the network configuration or elsewhere (that is, a bug). In Red Hat Enterprise Linux 6 Omping is provided as a Technology Preview. Package: omping-0.0.4-1 QFQ queuing discipline In Red Hat Enterprise Linux 6, the tc utility has been updated to work with the Quick Fair Scheduler (QFQ) kernel features. Users can now take advantage of the new QFQ traffic queuing discipline from userspace. This feature is considered a Technology Preview. Package: kernel-2.6.32-431 vios-proxy, BZ# 721119 vios-proxy is a stream-socket proxy for providing connectivity between a client on a virtual guest and a server on a Hypervisor host. Communication occurs over virtio-serial links. Package: vios-proxy-0.2-1

Commands:
9.8. LOB Considerations Although, you can find information about all JBoss Data Virtualization settings using the Management CLI (see Section 10.1, "JBoss Data Virtualization Settings" ), this section provides some additional information about those settings related to large objects (LOBs). lob-chunk-size-in-kb LOBs and XML documents are streamed from the JBoss Data Virtualization server to the JDBC API. Normally, these values are not materialized in the server memory, avoiding potential out-of-memory issues. When using style sheets, or XQuery, whole XML documents must be materialized on the server. Even when using the XMLQuery or XMLTable functions and document projection is applied, memory issues may occur for large documents. LOBs are broken into pieces when being created and streamed. The maximum size of each piece when fetched by the client can be configured with the lob-chunk-size-in-kb property. The default value is 100. When dealing with extremely large LOBs, you may consider increasing lob-chunk-size-in-kb to decrease the amount of round-trips to stream the result. Setting the value too high may cause the server or client to have memory issues. Source LOB values are typically accessed by reference, rather than having the value copied to a temporary location. Thus care must be taken to ensure that source LOBs are returned in a memory-safe manner. This caution is more for the source driver vendors not to consume VM memory for LOBs.

Commands:
Appendix A. Revision History Revision History Revision 6.6.0-2 Fri 7 Jul 2017 John Brier Added deprecation notice of NotifyingFuture. Revision 6.6.0-1 Tue 26 Jan 2016 Christian Huffman Added deprecation notice of Spring Framework. Revision 6.6.0-0 Thu 7 Jan 2016 Christian Huffman Initial Draft for 6.6.0. Included all Known and Resolved Issues. Added deprecation notes.

Commands:
Index D device-mapper multipath, Considerations for Using GNBD with Device-Mapper Multipath fencing GNBD server nodes, Fencing GNBD Server Nodes Linux page caching, Linux Page Caching driver and command usage, GNBD Driver and Command Usage exporting from a server, Exporting a GNBD from a Server importing on a client, Importing a GNBD on a Client E exporting from a server daemon, Exporting a GNBD from a Server F feedback, Feedback fencing GNBD server nodes, Fencing GNBD Server Nodes G GFS, using on a GNBD server node, Running GFS on a GNBD Server Node GNBD, using with Red Hat GFS, Using GNBD with Red Hat GFS gnbd.ko module, GNBD Driver and Command Usage , Importing a GNBD on a Client gnbd_export command , GNBD Driver and Command Usage , Usage gnbd_import command , GNBD Driver and Command Usage , Usage gnbd_serv daemon, GNBD Driver and Command Usage , Exporting a GNBD from a Server I importing on a client module, Importing a GNBD on a Client L Linux page caching, Linux Page Caching S software subsystem components, Using GNBD with Red Hat GFS

Commands:
14.13.3. Configuring Virtual CPU Affinity To configure the affinity of virtual CPUs with physical CPUs, refer to Example 14.3, "Pinning vCPU to a host physical machine's CPU" . Example 14.3. Pinning vCPU to a host physical machine's CPU The virsh vcpupin assigns a virtual CPU to a physical one. The vcpupin can take the following options: --vcpu requires the vcpu number [--cpulist] >string< lists the host physical machine's CPU number(s) to set, or omit an optional query --config affects boot --live affects the running domain --current affects the current domain

Commands:
virsh vcpupin rhel6 VCPU: CPU Affinity ---------------------------------- 0: 0-3 1: 0-3
Chapter 3. Custom issuers for cert-manager An issuer is a resource that acts as a certificate authority for a specific namespace, and is managed by the cert-manager Operator. TLS-e (TLS everywhere) is enabled in Red Hat OpenStack Services on OpenShift (RHOSO) environments, and it uses the following issuers by default: rootca-internal rootca-libvirt rootca-ovn rootca-public 3.1. Creating a custom issuer You can create custom ingress as well as custom internal issuers. To create and manage your own certificates for internal endpoints, you must create a custom internal issuer. Procedure Create a custom issuer in a file named rootca-custom.yaml : Replace <issuer_name> with the name of your custom issuer, for example, rootca-ingress-custom . Replace <secret_name> with the name of the Secret CR used by the certificate for your custom issuer. If you do not include a secret, one is created automatically. Create a certificate in a file named ca-issuer-certificate.yaml : Replace <issuer_name> with the name of your custom issuer. This matches the issuer created in the first step. Replace <hours> with the duration in hours, for example, a value of 87600h is equivalent to 3650 days, or about 10 years. Replace <secret_name> with the name of the Secret CR used by the certificate for your custom issuer. If you do not include a secret, one is created automatically. Create the issuer and certificate: Add the custom issuer to the TLS service definition in the control plane CR file. If your custom issuer is an ingress issuer, the customer issuer is defined under the ingress attribute as shown below: Replace <issuer_name> with the name of your custom issuer. This matches the issuer created in the first step. If your custom issuer is an internal issuer, the custom issuer is defined at the pod level under the internal attribute as shown below: Replace <issuer_name> with the name of your custom issuer. This matches the issuer created in the first step. Additional resources Configuring certificates with an issuer

Commands:
apiVersion: cert-manager.io/v1 kind: Issuer metadata: name: <issuer_name> spec: ca: secretName: <secret_name>
apiVersion: cert-manager.io/v1 kind: Certificate metadata: name: <issuer_name> spec: commonName: <issuer_name> isCA: true duration: <hours> privateKey: algorithm: RSA size: 3072 issuerRef: name: selfsigned-issuer kind: Issuer secretName: <secret-name>
oc create -f rootca-custom.yaml oc create -f ca-issuer-certificate.yaml
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane metadata: name: openstack-control-plane spec: tls: ingress: enabled: true ca: customIssuer: <issuer_name>
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane metadata: name: myctlplane spec: tls: ingress: enabled: true podLevel: enabled: true internal: ca: customIssuer: <issuer_name>