mtpti5iD/redhat-docs_dataset huggingface dataset:
7.158. nss-pam-ldapd 7.158.1. RHBA-2013:0413 - nss-pam-ldapd bug fix update Updated nss-pam-ldapd packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The nss-pam-ldapd packages provides the nss-pam-ldapd daemon (nslcd), which uses a directory server to look up name service information on behalf of a lightweight nsswitch module. Bug Fixes BZ#747281 Prior to this update, the disconnect logic contained a misprint and a failure return value was missing. This update corrects the misprint and adds the missing return value. BZ#769289 Prior to this update, the nslcd daemon performed the idle time expiration check for the LDAP connection before starting an LDAP search operation. On a lossy network or if the LDAP server was under a heavy load, the connection could time out after the successful check and the search operation then failed. With this update, the idle time expiration test is now performed during the LDAP search operation so that the connection now no longer expires under these circumstances. BZ#791042 Prior to this update, when the nslcd daemon requested access to a large group, a buffer provided by the glibc library could not contain such a group and retried again with a larger buffer to process the operation successfully. As a consequence, redundant error messages were logged in the /var/log/message file. This update makes sure that even when glibc provides a buffer that is too small on first attempt in the described scenario, no redundant error messages are returned. All users of nss-pam-ldapd are advised to upgrade to these updated packages, which fix these bugs. 7.158.2. RHSA-2013:0590 - Important: nss-pam-ldapd security update Updated nss-pam-ldapd packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link associated with the description below. The nss-pam-ldapd packages provide the nss-pam-ldapd daemon (nslcd), which uses a directory server to lookup name service information on behalf of a lightweight nsswitch module. Security Fix CVE-2013-0288 An array index error, leading to a stack-based buffer overflow flaw, was found in the way nss-pam-ldapd managed open file descriptors. An attacker able to make a process have a large number of open file descriptors and perform name lookups could use this flaw to cause the process to crash or, potentially, execute arbitrary code with the privileges of the user running the process. Red Hat would like to thank Garth Mollett for reporting this issue. All users of nss-pam-ldapd are advised to upgrade to these updated packages, which contain a backported patch to fix this issue.

Commands:
Chapter 2. What is deployed with AMQ Streams Apache Kafka components are provided for deployment to OpenShift with the AMQ Streams distribution. The Kafka components are generally run as clusters for availability. A typical deployment incorporating Kafka components might include: Kafka cluster of broker nodes ZooKeeper cluster of replicated ZooKeeper instances Kafka Connect cluster for external data connections Kafka MirrorMaker cluster to mirror the Kafka cluster in a secondary cluster Kafka Exporter to extract additional Kafka metrics data for monitoring Kafka Bridge to make HTTP-based requests to the Kafka cluster Not all of these components are mandatory, though you need Kafka and ZooKeeper as a minimum. Some components can be deployed without Kafka, such as MirrorMaker or Kafka Connect. 2.1. Order of deployment The required order of deployment to an OpenShift cluster is as follows: Deploy the Cluster operator to manage your Kafka cluster Deploy the Kafka cluster with the ZooKeeper cluster, and include the Topic Operator and User Operator in the deployment Optionally deploy: The Topic Operator and User Operator standalone if you did not deploy them with the Kafka cluster Kafka Connect Kafka MirrorMaker Kafka Bridge Components for the monitoring of metrics 2.2. Additional deployment configuration options The deployment procedures in this guide describe a deployment using the example installation YAML files provided with AMQ Streams. The procedures highlight any important configuration considerations, but they do not describe all the configuration options available. You can use custom resources to refine your deployment. You may wish to review the configuration options available for Kafka components before you deploy AMQ Streams. For more information on the configuration through custom resources, see Deployment configuration in the Using AMQ Streams on OpenShift guide. 2.2.1. Securing Kafka On deployment, the Cluster Operator automatically sets up TLS certificates for data encryption and authentication within your cluster. AMQ Streams provides additional configuration options for encryption , authentication and authorization , which are described in the Using AMQ Streams on OpenShift guide: Secure data exchange between the Kafka cluster and clients by configuration of Kafka resources . Configure your deployment to use an authorization server to provide OAuth 2.0 authentication and OAuth 2.0 authorization . Secure Kafka using your own certificates . 2.2.2. Monitoring your deployment AMQ Streams supports additional deployment options to monitor your deployment. Extract metrics and monitor Kafka components by deploying Prometheus and Grafana with your Kafka cluster . Extract additional metrics, particularly related to monitoring consumer lag, by deploying Kafka Exporter with your Kafka cluster . Track messages end-to-end by setting up distributed tracing , as described in the Using AMQ Streams on OpenShift guide.

Commands:
23.2. The Text Mode Installation Program User Interface While text mode installations are not explicitly documented, those using the text mode installation program can easily follow the GUI installation instructions. However, because text mode presents you with a simpler, more streamlined installation process, certain options that are available in graphical mode are not also available in text mode. These differences are noted in the description of the installation process in this guide, and include: Interactively activating FCP LUNs configuring advanced storage methods such as LVM, RAID, FCoE, zFCP, and iSCSI. customizing the partition layout customizing the bootloader layout selecting packages during installation configuring the installed system with firstboot

Commands:
Chapter 4. Adding Fuse users to JBoss EAP Run the JBoss EAP add-user script to add Fuse users to JBoss EAP. Prerequisites JBoss EAP is running. Procedure Navigate to EAP_HOME/bin . Run the add-user script. For example: ./add-user.sh Respond to the prompts to create a new user: Management User is a Fuse administrative user on JBoss EAP. Application User is a Fuse non-administrative user on JBoss EAP.

Commands:
10.13. Debug Logging for Distributed Lock Manager (DLM) Needs to be Enabled There are two debug options for the Distributed Lock Manager (DLM) that you can enable, if necessary: DLM kernel debugging, and POSIX lock debugging. To enable DLM debugging, edit the /etc/cluster/cluster.conf file to add configuration options to the dlm tag. The log_debug option enables DLM kernel debugging messages, and the plock_debug option enables POSIX lock debugging messages. The following example section of a /etc/cluster/cluster.conf file shows the dlm tag that enables both DLM debug options: After editing the /etc/cluster/cluster.conf file, run the cman_tool version -r command to propagate the configuration to the rest of the cluster nodes.

Commands:
<cluster config_version="42" name="cluster1"> <dlm log_debug="1" plock_debug="1"/> </cluster>
Chapter 2. Installing .NET 6.0 .NET 6.0 is included in the AppStream repositories for RHEL 9. The AppStream repositories are enabled by default on RHEL 9 systems. You can install the .NET 6.0 runtime with the latest 6.0 Software Development Kit (SDK). When a newer SDK becomes available for .NET 6.0, you can install it by running sudo yum upgrade . Prerequisites Installed and registered RHEL 9 with attached subscriptions. For more information, see Performing a standard RHEL installation . Procedure Install .NET 6.0 and all of its dependencies: Verification steps Verify the installation: The output returns the relevant information about the .NET installation and the environment.

Commands:
sudo yum install dotnet-sdk-6.0 -y
dotnet --info
4.8. RHEA-2012:0838 - new package: java-1.7.0-oracle New java-1.7.0-oracle package is now available for Red Hat Enterprise Linux 6. The java-1.7.0-oracle package provides the Oracle Java 7 Runtime Environment and the Oracle Java 7 Software Development Kit. This update adds the java-1.7.0-oracle packages to Red Hat Enterprise Linux 6. (BZ# 720928 ) Note Before applying this update, make sure that any Oracle Java packages have been removed. All users who require java-1.7.0-oracle should install these new packages.

Commands:
4.75. gnome-screensaver 4.75.1. RHEA-2011:1652 - gnome-screensaver bug fix and enhancement update An updated gnome-screensaver package that fixes various bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6. The gnome-screensaver package contains the GNOME project's official screen saver program. It is designed for improved integration with the GNOME desktop, including themeability, language support, and Human Interface Guidelines (HIG) compliance. It also provides screen-locking and fast user-switching from a locked screen. Bug Fixes BZ# 648850 When the user locked the screen and the X Window System did not support the X Resize, Rotate (XRandR) or XF86VM gamma fade extensions, then the gnome-screensaver utility terminated with a segmentation fault. With this update, additional checks are made before calling the fade_setup() function, and gnome-screensaver no longer terminates. BZ# 697892 Prior to this update, the Unlock dialog box arbitrarily changed between the monitors in dual head setups, based on the position of the mouse pointer. The Unlock dialog box is now placed on a consistent monitor instead of where the mouse is located. BZ# 719023 Previously, when docking a laptop and using an external monitor, parts of the background got cut off due to incorrect logic for determining monitor dimensions. With this update, the source code is modified and the login screen is now displayed correctly. BZ# 740892 Previously, in rare cases, the screen saver entered a deadlock if monitors were removed during the fade up. The screen was locked as a consequence. This update modifies gnome-screensaver so that the screen saver responds as expected. Enhancement BZ# 677580 Previously, there was no indicator of the keyboard layout when the screen was locked. Users who used more than one layout did not know which layout was active. Consequently, users could be forced to type the password several times. This update adds the missing keyboard layout indicator. All users of gnome-screensaver are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
probe::linuxmib.DelayedACKs Name probe::linuxmib.DelayedACKs - Count of delayed acks Synopsis linuxmib.DelayedACKs Values op Value to be added to the counter (default value of 1) sk Pointer to the struct sock being acted on Description The packet pointed to by skb is filtered by the function linuxmib_filter_key . If the packet passes the filter is is counted in the global DelayedACKs (equivalent to SNMP's MIB LINUX_MIB_DELAYEDACKS)

Commands:
probe::tty.resize Name probe::tty.resize - Called when a terminal resize happens Synopsis tty.resize Values new_row the new row value old_row the old row value name the tty name new_col the new col value old_xpixel the old xpixel old_col the old col value new_xpixel the new xpixel value old_ypixel the old ypixel new_ypixel the new ypixel value

Commands:
Chapter 8. Clustering Dynamic Token Timeout for Corosync The token_coefficient option has been added to the Corosync Cluster Engine . The value of token_coefficient is used only when the nodelist section is specified and contains at least three nodes. In such a situation, the token timeout is computed as follows: This allows the cluster to scale without manually changing the token timeout every time a new node is added. The default value is 650 milliseconds, but it can be set to 0, resulting in effective removal of this feature. This feature allows Corosync to handle dynamic addition and removal of nodes. Corosync Tie Breaker Enhancement The auto_tie_breaker quorum feature of Corosync has been enhanced to provide options for more flexible configuration and modification of tie breaker nodes. Users can now select a list of nodes that will retain a quorum in case of an even cluster split, or choose that a quorum will be retained by the node with the lowest node ID or the highest node ID. Enhancements for Red Hat High Availability For the Red Hat Enterprise Linux 7.1 release, the Red Hat High Availability Add-On supports the following features. For information on these features, see the High Availability Add-On Reference manual. The pcs resource cleanup command can now reset the resource status and failcount for all resources. You can specify a lifetime parameter for the pcs resource move command to indicate a period of time that the resource constraint this command creates will remain in effect. You can use the pcs acl command to set permissions for local users to allow read-only or read-write access to the cluster configuration by using access control lists (ACLs). The pcs constraint command now supports the configuration of specific constraint options in addition to general resource options. The pcs resource create command supports the disabled parameter to indicate that the resource being created is not started automatically. The pcs cluster quorum unblock command prevents the cluster from waiting for all nodes when establishing a quorum. You can configure resource group order with the before and after parameters of the pcs resource create command. You can back up the cluster configuration in a tarball and restore the cluster configuration files on all nodes from backup with the backup and restore options of the pcs config command.

Commands:
[token + (amount of nodes - 2)] * token_coefficient
Chapter 11. Consistent Network Device Naming Red Hat Enterprise Linux provides methods for consistent and predictable network device naming for network interfaces. These features change the name of network interfaces on a system in order to make locating and differentiating the interfaces easier. Traditionally, network interfaces in Linux are enumerated as eth[0123...]s0 , but these names do not necessarily correspond to actual labels on the chassis. Modern server platforms with multiple network adapters can encounter non-deterministic and counter-intuitive naming of these interfaces. This affects both network adapters embedded on the motherboard ( Lan-on-Motherboard , or LOM ) and add-in (single and multiport) adapters. In Red Hat Enterprise Linux, udev supports a number of different naming schemes. The default is to assign fixed names based on firmware, topology, and location information. This has the advantage that the names are fully automatic, fully predictable, that they stay fixed even if hardware is added or removed (no re-enumeration takes place), and that broken hardware can be replaced seamlessly. The disadvantage is that they are sometimes harder to read than the eth or wla names traditionally used. For example: enp5s0 . Warning Red Hat does not support systems with consistent device naming disabled. For further details, see Is it safe to set net.ifnames=0? 11.1. Naming Schemes Hierarchy By default, systemd will name interfaces using the following policy to apply the supported naming schemes: Scheme 1: Names incorporating Firmware or BIOS provided index numbers for on-board devices (example: eno1 ), are applied if that information from the firmware or BIOS is applicable and available, else falling back to scheme 2. Scheme 2: Names incorporating Firmware or BIOS provided PCI Express hotplug slot index numbers (example: ens1 ) are applied if that information from the firmware or BIOS is applicable and available, else falling back to scheme 3. Scheme 3: Names incorporating physical location of the connector of the hardware (example: enp2s0 ), are applied if applicable, else falling directly back to scheme 5 in all other cases. Scheme 4: Names incorporating interface's MAC address (example: enx78e7d1ea46da ), is not used by default, but is available if the user chooses. Scheme 5: The traditional unpredictable kernel naming scheme, is used if all other methods fail (example: eth0 ). This policy, the procedure outlined above, is the default. If the system has biosdevname enabled, it will be used. Note that enabling biosdevname requires passing biosdevname=1 as a kernel command-line parameter, except in the case of a Dell system, where biosdevname will be used by default as long as it is installed. If the user has added udev rules which change the name of the kernel devices, those rules will take precedence.

Commands:
Chapter 1. Overview As part of an {PlatformName} subscription, customers have access to a supported version of {HubName}. Red Hat provides a published product life cycle for {HubName} so that customers and partners can properly plan, deploy, support, and maintain their {PrivateHubName}s that they use with the {PlatformNameShort}. This life cycle encompasses stated time periods for each version of {HubName}, starting with 4.2. The life cycle for each version of {HubName} is split into production phases, each identifying the various levels of maintenance over a period of time from the initial release date. While multiple versions of {HubName} will be supported at any one time, note that this life cycle applies to each specific version of {HubName} (4.2, 4.3 and so on). Customers are expected to upgrade their {HubName} environments to the most current supported version of the product in a timely fashion. Bug fixes and feature-work will target only the latest versions of the product, though some allowance may be given for high security risk items. Glossary Maintenance - Security and Application Bug fixes. Updates - Application Feature Enhancements Private Automation Hub - Refers to the customer installable {HubName} as provided via Subscription Manager.

Commands:
20.9. Block I/O tuning <domain> ... <blkiotune> <weight>800</weight> <device> <path>/dev/sda</path> <weight>1000</weight> </device> <device> <path>/dev/sdb</path> <weight>500</weight> </device> </blkiotune> ... </domain> Figure 20.11. Block I/O Tuning Although all are optional, the components of this section of the domain XML are as follows: Table 20.8. Block I/O tuning elements Element Description <blkiotune> This optional element provides the ability to tune Blkio cgroup tunable parameters for the domain. If this is omitted, it defaults to the OS provided defaults. <weight> This optional weight element is the overall I/O weight of the guest virtual machine. The value should be within the range 100 - 1000. <device> The domain may have multiple <device> elements that further tune the weights for each host physical machine block device in use by the domain. Note that multiple guest virtual machine disks can share a single host physical machine block device. In addition, as they are backed by files within the same host physical machine file system, this tuning parameter is at the global domain level, rather than being associated with each guest virtual machine disk device (contrast this to the <iotune> element which can be applied to a single <disk> ). Each device element has two mandatory sub-elements, <path> describing the absolute path of the device, and <weight> giving the relative weight of that device, which has an acceptable range of 100 - 1000.

Commands:
<domain> <blkiotune> <weight>800</weight> <device> <path>/dev/sda</path> <weight>1000</weight> </device> <device> <path>/dev/sdb</path> <weight>500</weight> </device> </blkiotune> </domain>
16.7. Keyboard Configuration Using your mouse, select the correct layout type (for example, U.S. English) for the keyboard you would prefer to use for the installation and as the system default (refer to Figure 16.3, "Keyboard Configuration" ). Once you have made your selection, click to continue. Figure 16.3. Keyboard Configuration Note To change your keyboard layout type after you have completed the installation, use the Keyboard Configuration Tool . Type the system-config-keyboard command in a shell prompt to launch the Keyboard Configuration Tool . If you are not root, it prompts you for the root password to continue.

Commands:
Preface Red Hat Quay offers a comprehensive permissions model, which allows administrators the ability to control who can access, manage, and modify repositories at a granular level. The following sections show you how to manage user access, define team roles, set permissions for users and robot accounts, and define the visibility of a repository. These guides include instructions using both the Red Hat Quay UI and the API. The following topics are covered: Role-based access controls Adjusting repository visibility Creating and managing robot accounts Clair vulnerability reporting

Commands:
Kafka configuration properties Red Hat Streams for Apache Kafka 2.7 Use configuration properties to configure Kafka components

Commands:
Further, when in `read_committed` the seekToEnd method will return the LSO .
1) If no partition is specified but a key is present, choose a partition based on a hash of the key.
2) If no partition or key is present, choose the sticky partition that changes when at least batch.size bytes are produced to the partition. * `org.apache.kafka.clients.producer.RoundRobinPartitioner`: A partitioning strategy where each record in a series of consecutive records is sent to a different partition, regardless of whether the 'key' is provided or not, until partitions run out and the process starts over again. Note: There's a known issue that will cause uneven distribution when a new batch is created. See KAFKA-9965 for more detail.
dnf install <package_name>
dnf install <path_to_download_package>