mtpti5iD/redhat-docs_dataset huggingface dataset:
8.52. ghostscript 8.52.1. RHBA-2013:1624 - ghostscript bug fix update Updated ghostscript packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The Ghostscript suite contains utilities for rendering PostScript and PDF documents. Ghostscript translates PostScript code to common, bitmap formats so that the code can be displayed or printed. Bug Fixes BZ# 893775 Due to a bug in a function that copies CID-keyed Type 2 fonts, document conversion attempts sometimes caused the ps2pdf utility to terminate unexpectedly with a segmentation fault. A patch has been provided to address this bug so that the function now copies fonts properly and ps2pdf no longer crashes when converting documents. BZ# 916162 Due to lack of support for the TPGDON option for JBIG2 encoded regions, some PDF files were not displayed correctly. A patch has been provided to add this support so that PDF files using the TPGDON option are now displayed correctly. BZ# 1006165 Previously, some PDF files with incomplete ASCII base-85 encoded images caused the ghostscript utility to terminate with the following error: /syntaxerror in ID The problem occurred when the image ended with "~" (tilde) instead of "~>" (tilde, right angle bracket) as defined in the PDF specification. Although this is an improper encoding, an upstream patch has been applied, and ghostscript now handles these PDF files without errors. Users of ghostscript are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 1. Preparing to deploy OpenShift Data Foundation Deploying OpenShift Data Foundation on OpenShift Container Platform using dynamic storage devices provides you with the option to create internal cluster resources. This will result in the internal provisioning of the base services, which helps to make additional storage classes available to applications. Before you begin the deployment of OpenShift Data Foundation, follow these steps: Setup a chrony server. See Configuring chrony time service and use knowledgebase solution to create rules allowing all traffic. Optional: If you want to enable cluster-wide encryption using an external Key Management System (KMS): Ensure that a policy with a token exists and the key value backend path in Vault is enabled. See enabled the key value backend path and policy in Vault . Ensure that you are using signed certificates on your Vault servers. Minimum starting node requirements [Technology Preview] An OpenShift Data Foundation cluster is deployed with minimum configuration when the standard deployment resource requirement is not met. See Resource requirements section in Planning guide. Regional-DR requirements [Developer Preview] Disaster Recovery features supported by Red Hat OpenShift Data Foundation require all of the following prerequisites in order to successfully implement a Disaster Recovery solution: A valid Red Hat OpenShift Data Foundation Advanced subscription A valid Red Hat Advanced Cluster Management for Kubernetes subscription For detailed requirements, see Regional-DR requirements and RHACM requirements . 1.1. Enabling key value backend path and policy in Vault Prerequisites Administrator access to Vault. Carefully, choose a unique path name as the backend path that follows the naming convention since it cannot be changed later. Procedure Enable the Key/Value (KV) backend path in Vault. For Vault KV secret engine API, version 1: For Vault KV secret engine API, version 2: Create a policy to restrict users to perform a write or delete operation on the secret using the following commands. Create a token matching the above policy.

Commands:
vault secrets enable -path=odf kv
vault secrets enable -path=odf kv-v2
echo ' path "odf/*" { capabilities = ["create", "read", "update", "delete", "list"] } path "sys/mounts" { capabilities = ["read"] }'| vault policy write odf -
vault token create -policy=odf -format json
Chapter 193. Kie-Camel 193.1. Overview The kie-camel component is an Apache Camel endpoint provided by Red Hat Fuse that integrates Fuse with Red Hat Process Automation Manager. It enables you to specify a Red Hat Process Automation Manager module by using a Maven group ID, artifact ID, and version (GAV) identifier which you can pull into the route and execute. It also enables you to specify portions of the message body as facts. You can use the kie-camel component with embedded engines or with Process Server. For more details about the kie-camel component, see Integrating Red Hat Fuse with Red Hat Process Automation Manager .

Commands:
Chapter 4. Compatibility matrix for Red Hat Ceph Storage 4.3 The following tables list products and their versions compatible with Red Hat Ceph Storage (RHCS) 4.3. Host Operating System Version Notes Red Hat Enterprise Linux 7.9, 8.4 EUS, 8.5 and 8.6 Included in the product Important All nodes in the cluster and their clients must use the supported OS version(s) to ensure that the version of the ceph package is the same on all nodes. Using different versions of the ceph package is not supported. Important Red Hat no longer supports using Ubuntu as a host operating system to deploy Red Hat Ceph Storage. Product Version Notes Ansible 2.9 Included in the product Red Hat OpenShift 3.0 and later 3.x versions The RBD driver is supported starting with version 3.0 and Cinder driver is supported starting with version 3.1. Red Hat OpenShift 4 is not supported. Red Hat OpenStack Platform 13, 15 and 16 Red Hat OpenStack Platform 11, 12 and 14 is not supported. Red Hat OpenStack Platform 10 and Red Hat Ceph Storage 4 are not a tested combination. Director 13 deployed Red Hat Ceph Storage 3.1+ also supports external Red Hat Ceph Storage 4. Director 16 deployed Red Hat Ceph Storage 4.3 also supports external Red Hat Ceph Storage 5. Red Hat Satellite 6.x Only registering with the Content Delivery Network (CDN) is supported. Registering with Red Hat Network (RHN) is deprecated and not supported. Red Hat OpenShift Container Storage 4.6 Red Hat Ceph Storage 4.2 and later versions are supported for Red Hat OpenShift Storage 4.6 external mode. Client Connector Version Notes S3A 2.8.x, 3.2.x, and trunk Red Hat Enterprise Linux iSCSI Initiator The latest versions of the iscsi-initiator-utils and device-mapper-multipath packages RHCS as a backup target Version Notes CommVault Cloud Data Management v11 IBM Spectrum Protect Plus 10.1.5 IBM Spectrum Protect server 8.1.8 NetApp AltaVault 4.3.2 and 4.4 Rubrik Cloud Data Management (CDM) 3.2 and later Trilio, TrilioVault 3.0 S3 target Veeam (object storage) Veeam Availability Suite 9.5 Update 4 Supported on Red Hat Ceph Storage object storage with the S3 protocol Veritas NetBackup for Symantec OpenStorage (OST) cloud backup 7.7 and 8.0 Independent Software vendors Version Notes IBM Spectrum Discover 2.0.3

Commands:
11. Entitlement Red Hat Subscription Manager and the Subscription Service Effective software and infrastructure management requires a mechanism to handle the software inventory - both the type of products and the number of systems that the software is installed on. In parallel with Red Hat Enterprise Linux 6.1, Red Hat is introducing a new subscription service which provides oversight for the software subscriptions for an organization and a more effective content delivery system. On local systems, the new Red Hat Subscription Manager offers both GUI and command-line tools to manage the local system and its allocated subscriptions. A better method to handle subscriptions will help our customers allocate their subscriptions more effectively and will make installing and updating Red Hat products much simpler. In Red Hat Enterprise Linux 6.0 and 5.6 and older, subscriptions were based on access to channels and were assigned to an organization as a whole. Starting in Red Hat Enterprise Linux 6.1, subscriptions are based on installed products and are assigned to systems individually. This provides clear and delineated control over the products used by and subscribed to by a specific system. As part of the new subscription structure, the Customer Portal provides two paths to manage subscriptions: Certificate-based Red Hat Network, which uses the new subscription service, and RHN Classic, which uses the traditional channels. Systems must be managed either by the new Certificate-based Red Hat Network or by RHN Classic, but not both. If a system was previously managed by RHN Classic, there is no direct, supported migration path from RHN Classic to Certificate-based Red Hat Network. Note The Red Hat Enterprise Linux 6 Subscription Management Guide contains further information on managing subscriptions. The Red Hat Enterprise Linux 6 Installation Guide contains further information on the registration and subscription process during firstboot and kickstart.

Commands:
8.182. polkit-gnome 8.182.1. RHBA-2014:0425 - polkit-gnome bug fix update Updated polkit-gnome packages that fix one bug are now available for Red Hat Enterprise Linux 6. The polkit-gnome packages provide an authentication agent for the polkit authentication manager, which is an application-level toolkit for defining and handling the policy that allows non-privileged processes communicate with privileged ones. * Due to a bug in the source code, the authentication dialog of the polkit GNOME authentication manager could send an invalid time stamp to the window manager when the dialog was displayed for the first time. Consequently, the dialog did not receive focus for keyboard input, and the input was sent to the previously-focused window instead. This bug has been fixed, and valid time stamps are now obtained and sent to the window manager. As a result, keyboard input is always sent to the displayed authentication dialog as expected. (BZ# 872918 ) Bug Fix BZ# 872918 Due to a bug in the source code, the authentication dialog of the polkit GNOME authentication manager could send an invalid time stamp to the window manager when the dialog was displayed for the first time. Consequently, the dialog did not receive focus for keyboard input, and the input was sent to the previously-focused window instead. This bug has been fixed, and valid time stamps are now obtained and sent to the window manager. As a result, keyboard input is always sent to the displayed authentication dialog as expected. Users of polkit-gnome are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Red Hat build of OpenJDK overview OpenJDK is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of OpenJDK is based on the upstream OpenJDK 8u, OpenJDK 11u, and OpenJDK 17u projects and includes the Shenandoah Garbage Collector in all versions. Multi-platform - The Red Hat build of OpenJDK is now supported on Windows and RHEL. This helps you standardize on a single Java platform across desktop, datacenter, and hybrid cloud. Frequent releases - Red Hat delivers quarterly updates of JRE and JDK for the Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, and Red Hat build of OpenJDK 17 distributions. These are available as rpm , portables, msi , zip files and containers. Long-term support - Red Hat supports the recently released Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, and Red Hat build of OpenJDK 17 distributions. For more information about the support lifecycle, see OpenJDK Life Cycle and Support Policy . Java Web Start - Red Hat build of OpenJDK supports Java Web Start for RHEL.

Commands:
Chapter 6. Developer previews This section describes the developer preview features introduced in Red Hat OpenShift Data Foundation 4.18. Important Developer preview feature is subject to Developer preview support limitations. Developer preview releases are not intended to be run in production environments. The clusters deployed with the developer preview features are considered to be development clusters and are not supported through the Red Hat Customer Portal case management system. If you need assistance with developer preview features, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on availability and work schedules. 6.1. Consistent RADOS block device (RBD) group disaster recovery The OpenShift Data Foundation Disaster Recovery solution provides a way to consistently mirror multiple ReadWriteOnce (RWO) persistent volumes (PVs) with regional disaster recovery. For more information, see the knowledgebase article, Enabling and Managing Consistency Groups in OpenShift 4.18 .

Commands:
Chapter 2. General Updates Cross channel package dependency improvements The yum utility has been enhanced to prompt the end user to search disabled package repositories on the system when a package dependency error occurs. This change will allow users to quickly resolve dependency errors by first checking all known channels for the missing package dependency. To enable this functionality, execute yum update yum subscription-manager prior to upgrading your machine to Red Hat Enterprise Linux 6.8. See the System and Subscription Management chapter for further details on the implementation of this feature. (BZ#1197245) Packages moved to the Optional Channel The following packages have been moved to the Optional channel: gnome-devel-docs libstdc++-docs xorg-x11-docs Note that if any of these packages have previously been installed, using the yum update command for updating these packages can lead to problems causing the update to fail. Enable the Optional channel before updating the mentioned installed packages or uninstall them before updating your system. For detailed instructions on how to subscribe your system to the Optional channel, see the relevant Knowledgebase articles on Red Hat Customer Portal: https://access.redhat.com/solutions/392003 for Red Hat Subscription Management or https://access.redhat.com/solutions/70019 if your system is registered with RHN Classic. (BZ#1300789)

Commands:
Chapter 2. Getting Started: Overview This chapter provides a summary procedure for setting up a basic Red Hat High Availability cluster consisting of two nodes running Red Hat Enterprise Linux release 6. This procedure uses the luci user interface to create the cluster. While this procedure creates a basic cluster, it does not yield a complete supported cluster configuration. Further details on planning and deploying a cluster are provided in the remainder of this document. 2.1. Installation and System Setup Before creating a Red Hat High Availability cluster, perform the following setup and installation steps. Ensure that your Red Hat account includes the following support entitlements: RHEL: Server Red Hat Applications: High availability Red Hat Applications: Resilient Storage, if using the Clustered Logical Volume Manager (CLVM) and GFS2 file systems. Register the cluster systems for software updates, using either Red Hat Subscriptions Manager (RHSM) or RHN Classic. On each node in the cluster, configure the iptables firewall. The iptables firewall can be disabled, or it can be configured to allow cluster traffic to pass through. To disable the iptables system firewall, execute the following commands. For information on configuring the iptables firewall to allow cluster traffic to pass through, see Section 3.3, "Enabling IP Ports" . On each node in the cluster, configure SELinux. SELinux is supported on Red Hat Enterprise Linux 6 cluster nodes in Enforcing or Permissive mode with a targeted policy, or it can be disabled. To check the current SELinux state, run the getenforce : For information on enabling and disabling SELinux, see the Security-Enhanced Linux user guide. Install the cluster packages and package groups. On each node in the cluster, install the High Availability and Resiliant Storage package groups. On the node that will be hosting the web management interface, install the luci package.

Commands:
service iptables stop chkconfig iptables off
getenforce Permissive
yum groupinstall 'High Availability' 'Resilient Storage'
yum install luci
15.5. Adding a Remote Connection This procedure covers how to set up a connection to a remote system using virt-manager . To create a new connection open the File menu and select the Add Connection... menu item. The Add Connection wizard appears. Select the hypervisor. For Red Hat Enterprise Linux 6 systems select QEMU/KVM . Select Local for the local system or one of the remote connection options and click Connect . This example uses Remote tunnel over SSH which works on default installations. For more information on configuring remote connections refer to Chapter 5, Remote Management of Guests Figure 15.8. Add Connection Enter the root password for the selected host when prompted. A remote host is now connected and appears in the main virt-manager window. Figure 15.9. Remote host in the main virt-manager window

Commands:
Chapter 18. Re-enabling accounts that reached the inactivity limit If Directory Server inactivated an account because it reached the inactivity limit, an administrator can re-enable the account. 18.1. Re-enabling accounts inactivated by the Account Policy plug-in You can re-enable accounts using the dsconf account unlock command or by manually updating the lastLoginTime attribute of the inactivated user. Prerequisites An inactivated user account. Procedure Reactivate the account using one of the following methods: Using the dsconf account unlock command: # dsidm -D "cn=Directory manager" ldap://server.example.com -b " dc=example,dc=com " account unlock " uid=example,ou=People,dc=example,dc=com " By setting the lastLoginTime attribute of the user to a recent time stamp: # ldapmodify -H ldap://server.example.com -x -D " cn=Directory Manager " -W dn: uid=example,ou=People,dc=example,dc=com changetype: modify replace: lastLoginTime lastLoginTime: 20210901000000Z Verification Authenticate as the user that you have reactivated. For example, perform a search: # ldapsearch -H ldap://server.example.com -x -D " uid=example,ou=People,dc=example,dc=com " -W -b " dc=example,dc=com -s base" If the user can successfully authenticate, the account was reactivated.

Commands:
dsidm -D "cn=Directory manager" ldap://server.example.com -b " dc=example,dc=com " account unlock " uid=example,ou=People,dc=example,dc=com "
ldapmodify -H ldap://server.example.com -x -D " cn=Directory Manager " -W dn: uid=example,ou=People,dc=example,dc=com changetype: modify replace: lastLoginTime lastLoginTime: 20210901000000Z
ldapsearch -H ldap://server.example.com -x -D " uid=example,ou=People,dc=example,dc=com " -W -b " dc=example,dc=com -s base"
Appendix A. Revision History Revision History Revision 6-1 Wed Aug 7 2019 Steven Levine Preparing document for 7.7 GA publication. Revision 5-2 Thu Oct 4 2018 Steven Levine Preparing document for 7.6 GA publication. Revision 4-2 Wed Mar 14 2018 Steven Levine Preparing document for 7.5 GA publication. Revision 4-1 Thu Dec 14 2017 Steven Levine Preparing document for 7.5 Beta publication. Revision 3-4 Wed Aug 16 2017 Steven Levine Updated version for 7.4. Revision 3-3 Wed Jul 19 2017 Steven Levine Document version for 7.4 GA publication. Revision 3-1 Wed May 10 2017 Steven Levine Preparing document for 7.4 Beta publication. Revision 2-6 Mon Apr 17 2017 Steven Levine Update for 7.3 Revision 2-4 Mon Oct 17 2016 Steven Levine Version for 7.3 GA publication. Revision 2-3 Fri Aug 12 2016 Steven Levine Preparing document for 7.3 Beta publication. Revision 1.2-3 Mon Nov 9 2015 Steven Levine Preparing document for 7.2 GA publication. Revision 1.2-2 Tue Aug 18 2015 Steven Levine Preparing document for 7.2 Beta publication. Revision 1.1-19 Mon Feb 16 2015 Steven Levine Version for 7.1 GA release Revision 1.1-10 Thu Dec 11 2014 Steven Levine Version for 7.1 Beta release Revision 0.1-33 Mon Jun 2 2014 Steven Levine Version for 7.0 GA release

Commands:
14.15.2.2. Creating a snapshot for the current domain The virsh snapshot-create-as domain command creates a snapshot for the domain with the properties specified in the domain XML file (such as <name> and <description> elements). If these values are not included in the XML string, libvirt will choose a value. To create a snapshot run: The remaining options are as follows: --print-xml creates appropriate XML for snapshot-create as output, rather than actually creating a snapshot. --diskspec option can be used to control how --disk-only and external checkpoints create external files. This option can occur multiple times, according to the number of <disk> elements in the domain XML. Each <diskspec> is in the form disk [,snapshot=type][,driver=type][,file=name] . To include a literal comma in disk or in file=name , escape it with a second comma. A literal --diskspec must precede each diskspec unless all three of <domain>, <name>, and <description> are also present. For example, a diskspec of vda,snapshot=external,file=/path/to,,new results in the following XML: --reuse-external creates an external snapshot reusing an existing file as the destination (meaning this file is overwritten). If this destination does not exist, the snapshot request will be refused to avoid losing contents of the existing files. --no-metadata creates snapshot data but any metadata is immediately discarded (that is, libvirt does not treat the snapshot as current, and cannot revert to the snapshot unless snapshot-create is later used to teach libvirt about the metadata again). This option is incompatible with --print-xml .

Commands:
virsh snapshot-create-as domain {[--print-xml] | [--no-metadata] [--reuse-external]} [name] [description] [--diskspec] diskspec]
<disk name='vda' snapshot='external'> <source file='/path/to,new'/> </disk>
4.267. redhat-rpm-config 4.267.1. RHBA-2011:1748 - redhat-rpm-config bug fix update An updated redhat-rpm-config package that fixes several bugs is now available for Red Hat Enterprise Linux 6. The redhat-rpm-config package is used during building of RPM packages to apply various default distribution options determined by Red Hat. It also provides a few Red Hat RPM macro customizations, such as those used during the building of Driver Update packages. Bug Fixes BZ# 642768 Previously, when building two RPM packages, where one depended on symbols in the other, the Driver Update Program (DUP) generated "Provides" and "Requires" symbols that did not match. This bug has been fixed, and these symbols are now generated correctly by DUP in the described scenario. BZ# 681884 If two kernel modules had a dependency, where one module referred to a function implemented by the other, the symbol reference was built incorrectly. As a consequence, the package that contained the module that depended on the other module, could not be installed. A patch has been provided to address this issue, and symbol references are now generated correctly in the described scenario. Enhancement BZ# 720866 Driver Update Disks now include additional dependency information to work with later releases of Red Hat Enterprise Linux 6, in which a small change to installer behavior will impact only newly-created Driver Update Disks. Disks made previously are not affected by this update. Users of redhat-rpm-config are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands: