mtpti5iD/redhat-docs_dataset huggingface dataset:
7.146. mod_authz_ldap 7.146.1. RHBA-2012:1389 - mod_authz_ldap bug fix update Updated mod_authz_ldap packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The mod_authz_ldap packages provide a module for the Apache HTTP Server to authenticate users against an LDAP database. Bug Fixes BZ#607797 Prior to this update, the License field of the mod_authz_ldap packages contained an incorrect tag. This update modifies the license text. Now, the license tag correctly reads "ASL1.0". BZ#643691 Prior to this update, the mod_authz_ldap module could leak memory. As a consequence, the memory consumption of the httpd process could increase as more requests were processed. This update modifies the underlying code to handle LDAP correctly. Now, the memory consumption as at expected levels. BZ# 782442 Prior to this update, passwords were logged in plain text to the error log when an LDAP bind password was configured if a connection error occurred. This update modifies the underlying code to prevent passwords from being logged in error conditions. All users of mod_authz_ldap are advised to upgrade to this updated package, which fixes these bugs.

Commands:
2.8.7. IPTables and Connection Tracking You can inspect and restrict connections to services based on their connection state. A module within iptables uses a method called connection tracking to store information about incoming connections. You can allow or deny access based on the following connection states: NEW - A packet requesting a new connection, such as an HTTP request. ESTABLISHED - A packet that is part of an existing connection. RELATED - A packet that is requesting a new connection but is part of an existing connection. For example, FTP uses port 21 to establish a connection, but data is transferred on a different port (typically port 20). INVALID - A packet that is not part of any connections in the connection tracking table. You can use the stateful functionality of iptables connection tracking with any network protocol, even if the protocol itself is stateless (such as UDP). The following example shows a rule that uses connection tracking to forward only the packets that are associated with an established connection:

Commands:
~]# iptables -A FORWARD -m state --state ESTABLISHED,RELATED -j ACCEPT
2.3. Installing GRUB If GRUB was not installed during the installation process, it can be installed afterward. Once installed, it automatically becomes the default boot loader. Before installing GRUB, make sure to use the latest GRUB package available or use the GRUB package from the installation CD-ROMs. For instructions on installing packages, refer to the chapter titled Package Management with RPM in the System Administrators Guide . Once the GRUB package is installed, open a root shell prompt and run the command /sbin/grub-install <location> , where <location> is the location that the GRUB Stage 1 boot loader should be installed. For example, the following command installs GRUB to the MBR of the master IDE device on the primary IDE bus: The time the system boots, the GRUB graphical boot loader menu appears before the kernel loads into memory. Important If GRUB is installed on a RAID 1 array, the system may become unbootable in the event of disk failure. An unsupported workaround is provided online at the following URL: http://www.dur.ac.uk/a.d.stribblehill/mirrored_grub.html

Commands:
/sbin/grub-install /dev/hda
Chapter 4. Ceph on-disk encryption About LUKS Disk Encryption and its Benefits You can use the Linux Unified Key Setup-on-disk-format (LUKS) method to encrypt partitions on the Linux system. LUKS encrypts the entire block devices and is therefore well-suited for protecting the contents of mobile devices such as removable storage media or laptop disk drives. Use the ceph-ansible utility to create encrypted OSD nodes to protect data stored on them. For details, see the Installing a Red hat Ceph Storage Cluster section in the Red Hat Ceph Storage 4 Installation Guide. For details on LUKS, see the Overview of LUKS section in the Security Guide for Red Hat Enterprise Linux 7. How ceph-ansible Creates Encrypted Partitions During the OSD installation, ceph-ansible calls the ceph-disk utility that is responsible for creating encrypted partitions. The ceph-disk utility creates a small ceph lockbox partition in addition to the data ( ceph data ) and journal ( ceph journal ) partitions. Also, ceph-disk creates the cephx client.osd-lockbox user. The ceph lockbox partition contains a key file that client.osd-lockbox uses to retrieve the LUKS private key needed to decrypt encrypted ceph data and ceph journal partitions. Then, ceph-disk calls the cryptsetup utility that creates two dm-crypt devices for the ceph data and ceph journal partitions. The dm-crypt devices use the ceph data and ceph journal GUID as an identifier. Important The ceph-disk command is deprecated in Red Hat Ceph Storage 4. The ceph-volume command is now the preferred method for deploying OSDs from the command-line interface. Currently, the ceph-volume command only supports the lvm plugin. See the Red Hat Ceph Storage Administration Guide , for more information on using the ceph-volume command. How ceph-ansible Handles the LUKS Keys The ceph-ansible utility stores the LUKS private keys in the Ceph Monitor key-value store. Each OSD has its own key for decrypting the dm-crypt devices containing the OSD data and the journal. The encrypted partitions are decrypted on boot automatically.

Commands:
4.230. piranha 4.230.1. RHBA-2011:1716 - piranha bug fix update An updated piranha package that fixes various bugs is now available for Red Hat Enterprise Linux 6. Piranha provides high-availability and load balancing services for Red Hat Enterprise Linux. The piranha package contains various tools to administer and configure the Linux Virtual Server (LVS), as well as the heartbeat and failover components. LVS is a dynamically-adjusted kernel routing mechanism that provides load balancing, primarily for Web and FTP servers. Bug Fixes BZ# 593728 Previously, failure to start a single nanny daemon could terminate all the other nanny daemons. As a result, piranha could stop routing requests to real servers if one service monitor failed. This update adds a new option in the lvs.cf file, "hard_shutdown". The old behavior is retained with the default setting of 1. If a 0 value is set, a single nanny does not kill all nannies but the system needs manual intervention. BZ# 628872 Previously, the piranha-gui init script searched for programs in the current working directory. As a consequence, SELinux Access Vector Cache (AVC) denials could be generated when starting the piranha-gui service in unusual locations without the "service" utility. The init script has been modified to avoid this problem. Now, SELinux denials are no longer logged. BZ# 703146 Adding or removing Virtual Service descriptions in the LVS configuration requires restarting the pulse daemon (service pulse reload). Prior to this update all services (running or not) were started. When reloading the pulse daemon, if a service did not have any servers defined, the pulse daemon terminated unexpectedly with a segmentation fault. With this update, only running services are restarted. Now, the pulse daemon reloads as expected. BZ# 706881 Prior to this update, terminating a nanny or an lvs daemon did not trigger a failover to the backup server. As a consequence, the load balancer stopped working. With this update, the pulse daemon shuts down if either the nanny daemon or the lvs daemon terminates. Now, the load balancer works as expected. BZ# 708036 Previously, the piranha-gui utility reported an HTTP 414 error (Request-URI Too Long) if too many virtual servers were defined. As a consequence, when trying to edit a virtual server, the error message "Too many arguments in the URL" appeared. With this update, the number of defined virtual servers does not affect the length of the URI. Now, error messages are no longer reported. BZ# 729828 This update adds the 255.255.254.0 network mask to the piranha-gui drop-down menus. All users of piranha are advised to upgrade to this updated package, which fixes these bugs.

Commands:
31.3. Adding HBAC Service Entries for Custom HBAC Services Only the most common services and service groups are configured for HBAC rules by default. However, you can also configure any other pluggable authentication module (PAM) service as an HBAC service. This enables you to define the custom PAM service in an HBAC rule. Note Adding a service as an HBAC service is not the same as adding a service to the domain. Adding a service to the domain (described in Section 16.1, "Adding and Editing Service Entries and Keytabs" ) makes the service a recognized resource available to other resources in the domain, but it does not enable you to use the service in HBAC rules. To add an HBAC service entry, you can use: the IdM web UI (see the section called "Web UI: Adding an HBAC Service Entry" ) the command line (see the section called "Command Line: Adding an HBAC Service Entry" ) Web UI: Adding an HBAC Service Entry Select Policy Host-Based Access Control HBAC Services . Click Add to add an HBAC service entry. Enter a name for the service, and click Add . Command Line: Adding an HBAC Service Entry Use the ipa hbacsvc-add command. For example, to add an entry for the tftp service:

Commands:
ipa hbacsvc-add tftp ------------------------- Added HBAC service "tftp" ------------------------- Service name: tftp
4.3.6. Alternative User Interfaces for GDB GDB uses the command line as its default interface. However, it also has an API called machine interface (MI). MI allows IDE developers to create other user interfaces to GDB. Some examples of these interfaces are: Eclipse (CDT) A graphical debugger interface integrated with the Eclipse development environment. More information can be found at the Eclipse website . Nemiver A graphical debugger interface which is well suited to the GNOME Desktop Environment. More information can be found at the Nemiver website Emacs A GDB interface which is integrated with the emacs. More information can be found at the Emacs website

Commands:
7.4.2. Laser Printer Consumables Depending on the type of laser printer deployed, consumable costs are usually proportional to the volume of printing. Toner comes in cartridges that are usually replaced outright; however, some models come with refillable cartridges. Color laser printers require one toner cartridge for each of the four colors. Additionally, color laser printers require fuser oils to bond toner onto paper and waste toner bottles to capture toner spillover. These added supplies raise the consumables cost of color laser printers; however, it is worth noting that such consumables, on average, last about 6000 pages, which is much greater than comparable inkjet or impact consumable lifespans. Paper type is less of an issue in laser printers, which means bulk purchases of regular xerographic or photocopy paper are acceptable for most print jobs. However, if you plan to print high-quality images, you should opt for glossy paper for a professional finish.

Commands:
20.16.9.11. Overriding the target element To override the target element, use a management tool to make the following changes to the domain XML: ... <devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> </interface> </devices> ... Figure 20.48. Devices - network interfaces- overriding the target element If no target is specified, certain hypervisors will automatically generate a name for the created tun device. This name can be manually specified, however the name must not start with either 'vnet' or 'vif', which are prefixes reserved by libvirt and certain hypervisors. Manually specified targets using these prefixes will be ignored.

Commands:
<devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> </interface> </devices>
4.351. xkeyboard-config 4.351.1. RHBA-2011:1591 - xkeyboard-config bug fix and enhancement update An updated xkeyboard-config package that fixes one bug and adds two enhancements is now available for Red Hat Enterprise Linux 6. The xkeyboard-config package provides the xkeyboard-config alternative xkb data files. Bug Fix BZ# 638612 Prior to this update, duplicate mapping for the backslash key caused the Indic Onscreen Keyboard (IOK) to exit with a segmentation fault when the Hindi Wx mapping was selected. This update modifies the mapping so that IOK no longer exits unexpectedly. Enhancements BZ# 651774 With this update, the Unicode Rupee symbol is now included in the Indic keyboard layouts. BZ# 713863 This update upgrades the xkeyboard-config data files to upstream version 2.3. All users of xkeyboard-config are advised to upgrade to this updated package, which addresses this bug and adds these enhancements.

Commands:
Chapter 2. Components 2.1. AMQP clients AMQ Clients includes a suite of AMQP 1.0 messaging APIs. AMQP is an ISO-standard, general-purpose messaging protocol with rich messaging capabilities. AMQ Broker and AMQ Interconnect offer AMQP 1.0 support and therefore interoperate with any AMQP 1.0 client. AMQ C++ AMQ JavaScript AMQ JMS (Java) AMQ .NET AMQ Python AMQ Ruby 2.2. JMS clients AMQ Clients offers multiple implementations of the widely used Java Message Service (JMS) API. AMQ JMS - AMQ JMS provides full AMQP 1.0 support and works with any AMQ AMQP 1.0 server or service. AMQ Core Protocol JMS - To support existing applications based on the ActiveMQ Artemis Core protocol, AMQ includes the AMQ Core Protocol JMS client. 2.3. Adapters and libraries AMQ Clients includes components for integrating with other platforms and components. AMQ JMS Pool - To support efficient use of JMS resources, AMQ includes the AMQ JMS Pool library. It enables reuse of connection resources beyond the standard lifecycle defined by the JMS API. AMQ Spring Boot Starter - AMQ Spring Boot Starter enables you to build standalone Spring applications that use AMQP 1.0 messaging. 2.4. Component compatibility The following table lists the supported languages, platforms, protocols, and servers for the AMQ Clients components. Component Languages Platforms Protocols Servers and services AMQ C++ C++ Linux, Windows AMQP 1.0 AMQ Broker, AMQ Interconnect, and A-MQ 6 AMQ JavaScript JavaScript Linux, Windows, browsers AMQP 1.0 AMQ Broker, AMQ Interconnect, and A-MQ 6 AMQ JMS Java JVM AMQP 1.0 AMQ Broker, AMQ Interconnect, and A-MQ 6 AMQ .NET C# Linux, Windows AMQP 1.0 AMQ Broker, AMQ Interconnect, and A-MQ 6 AMQ Python Python Linux, Windows AMQP 1.0 AMQ Broker, AMQ Interconnect, and A-MQ 6 AMQ Ruby Ruby Linux AMQP 1.0 AMQ Broker, AMQ Interconnect, and A-MQ 6 AMQ Spring Boot Starter Java JVM AMQP 1.0 AMQ Broker, AMQ Interconnect, and A-MQ 6 AMQ Core Protocol JMS Java JVM Core Protocol AMQ Broker and A-MQ 6 AMQ JMS Pool Java JVM - - For more information, see Red Hat AMQ 7 Supported Configurations .

Commands:
Chapter 1. Red Hat Quay features Red Hat Quay is regularly released with new features and software updates. The following features are available for Red Hat Quay deployments, however the list is not exhaustive: High availability Geo-replication Repository mirroring Docker v2, schema 2 (multi-arch) support Continuous integration Security scanning with Clair Custom log rotation Zero downtime garbage collection 24/7 support Users should check the Red Hat Quay Release Notes for the latest feature information.

Commands:
Chapter 8. Volume size overrides You can specify the desired size of storage resources provisioned for managed components. The default size for Clair and the PostgreSQL databases is 50Gi . You can now choose a large enough capacity upfront, either for performance reasons or in the case where your storage backend does not have resize capability. In the following example, the volume size for the Clair and the Quay PostgreSQL databases has been set to 70Gi : apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quay-example namespace: quay-enterprise spec: configBundleSecret: config-bundle-secret components: - kind: objectstorage managed: false - kind: route managed: true - kind: tls managed: false - kind: clair managed: true overrides: volumeSize: 70Gi - kind: postgres managed: true overrides: volumeSize: 70Gi - kind: clairpostgres managed: true Note The volume size of the clairpostgres component cannot be overridden. To override the clairpostgres component, you must override the clair component. This is a known issue and will be fixed in a future version of Red Hat Quay. ( PROJQUAY-4301 )

Commands:
apiVersion: quay.redhat.com/v1 kind: QuayRegistry metadata: name: quay-example namespace: quay-enterprise spec: configBundleSecret: config-bundle-secret components: - kind: objectstorage managed: false - kind: route managed: true - kind: tls managed: false - kind: clair managed: true overrides: volumeSize: 70Gi - kind: postgres managed: true overrides: volumeSize: 70Gi - kind: clairpostgres managed: true
Migrating applications to Red Hat build of Quarkus 3.8 Red Hat build of Quarkus 3.8 Red Hat Customer Content Services

Commands:
quarkus update
mvn com.redhat.quarkus.platform:quarkus-maven-plugin:3.8.6.SP3-redhat-00002:update
<dependency> <groupId>org.flywaydb</groupId> <artifactId>flyway-database-oracle</artifactId> </dependency>
Chapter 3. Compatibility matrix for Red Hat Ceph Storage 4.2 The following tables list products and their versions compatible with Red Hat Ceph Storage (RHCS) 4.2. Host Operating System Version Notes Red Hat Enterprise Linux 7.9, 8.2, 8.3, and 8.4 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.2 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:
Telemetry data collection Red Hat Developer Hub 1.4 Collecting and analyzing telemetry data to enhance Red Hat Developer Hub experience Red Hat Customer Content Services

Commands:
kind: ConfigMap apiVersion: v1 metadata: name: dynamic-plugins-rhdh data: dynamic-plugins.yaml: | includes: - dynamic-plugins.default.yaml plugins: - package: './dynamic-plugins/dist/backstage-community-plugin-analytics-provider-segment' disabled: true
spec: application: dynamicPluginsConfigMapName: dynamic-plugins-rhdh
global: dynamic: plugins: - package: './dynamic-plugins/dist/backstage-community-plugin-analytics-provider-segment' disabled: true
kind: ConfigMap apiVersion: v1 metadata: name: dynamic-plugins-rhdh data: dynamic-plugins.yaml: | includes: - dynamic-plugins.default.yaml plugins: - package: './dynamic-plugins/dist/backstage-community-plugin-analytics-provider-segment' disabled: false
spec: application: dynamicPluginsConfigMapName: dynamic-plugins-rhdh
global: dynamic: plugins: - package: './dynamic-plugins/dist/backstage-community-plugin-analytics-provider-segment' disabled: false
spec: application: extraEnvs: envs: - name: SEGMENT_WRITE_KEY value: <segment_key> 1
upstream: backstage: extraEnvVars: - name: SEGMENT_WRITE_KEY value: <segment_key> 1
Chapter 23. Dynamic Host Configuration Protocol (DHCP) Dynamic Host Configuration Protocol (DHCP) is a network protocol for automatically assigning TCP/IP information to client machines. Each DHCP client connects to the centrally-located DHCP server which returns that client's network configuration, including the IP address, gateway, and DNS servers. 23.1. Why Use DHCP? DHCP is useful for automatic configuration of client network interfaces. When configuring the client system, the administrator can choose DHCP and instead of entering an IP address, netmask, gateway, or DNS servers. The client retrieves this information from the DHCP server. DHCP is also useful if an administrator wants to change the IP addresses of a large number of systems. Instead of reconfiguring all the systems, he can just edit one DHCP configuration file on the server for the new set of IP addresses. If the DNS servers for an organization changes, the changes are made on the DHCP server, not on the DHCP clients. Once the network is restarted on the clients (or the clients are rebooted), the changes take effect. Furthermore, if a laptop or any type of mobile computer is configured for DHCP, it can be moved from office to office without being reconfigured as long as each office has a DHCP server that allows it to connect to the network.

Commands: