mtpti5iD/redhat-docs_dataset huggingface dataset:
7.242. zsh 7.242.1. RHBA-2015:1273 - zsh bug fix and enhancement update Updated zsh packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The zsh shell is a command interpreter usable as an interactive login shell and as a shell script command processor. Zsh resembles the ksh shell (the Korn shell), but includes many enhancements. Zsh supports command-line editing, built-in spelling correction, programmable command completion, shell functions (with autoloading), a history mechanism, and more. Bug Fixes BZ# 1132710 Parameter expansion has been enhanced to provide the USD{NAME:OFFSET} and USD{NAME:OFFSET:LENGTH} syntaxes for substrings and subarrays present in several other shells. Numeric expansion with braces has been extended, which allows users to specify a step in the numeric expansion, for example {3..9..2}. BZ# 878324 Prior to this update, when the "jobs -Z" built-in zsh command was invoked, some environment variables were overwritten. An upstream patch has been applied to preserve the environment variables when "jobs -Z" is run, thus fixing this bug. BZ# 1146119 Due to a parser error, the zsh shell previously interpreted variable assignments as other commands, and attempted to execute them when zsh was running in ksh compatibility mode. This update modifies the underlying code to interpret variable assignments as expected in the described situation. BZ# 1131172 Prior to this update, the speed of the pattern matching in the zsh shell decreased when multiple subsequent occurrences of the "*" wildcard symbol were used in a pattern. An upstream patch has been applied on zsh source code to optimize the implementation of pattern matching in zsh with redundant "*" symbols in the pattern. As a result, the speed of pattern matching in zsh is no longer affected by the count of subsequent "*" symbols. BZ# 1103697 An incorrect comment in the /etc/zshenv configuration file caused that the users erroneously expected that the file takes no effect if the zsh shell is started with the "-f" option. The comment in the /etc/zshenv file has been changed to describe the configuration file correctly. BZ# 567215 When processing overly-long input data, the zsh shell terminated unexpectedly because of a stack-based buffer overflow. With this update, arrays of variable sizes are allocated on heap memory instead of stack memory, thus fixing the bug. BZ# 1104021 Prior to this update, the description of emulation mode in the zsh man page was incomplete. With this update, the documentation has been updated to provide users with more information about the command that starts emulation mode. Users of zsh are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Configuring Argo CD RBAC By default, if you are logged into Argo CD using Red Hat SSO (RH SSO), you are a read-only user. You can change and manage the user level access. 1.1. Configuring user level access To manage and modify the user level access, configure the role-based access control (RBAC) section in the Argo CD custom resource (CR). Procedure Edit the argocd CR: USD oc edit argocd [argocd-instance-name] -n [namespace] Output metadata ... ... rbac: policy: 'g, rbacsystem:cluster-admins, role:admin' scopes: '[groups]' Add the policy configuration to the rbac section and add the name , email and the role of the user: metadata ... ... rbac: policy: <name>, <email>, role:<admin> scopes: '[groups]' Note Currently, RHSSO cannot read the group information of Red Hat OpenShift GitOps users. Therefore, configure the RBAC at the user level. 1.2. Modifying RHSSO resource requests/limits By default, the RHSSO container is created with resource requests and limitations. You can change and manage the resource requests. Resource Requests Limits CPU 500 1000m Memory 512 Mi 1024 Mi Procedure Modify the default resource requirements patching the Argo CD custom resource (CR): USD oc -n openshift-gitops patch argocd openshift-gitops --type='json' -p='[{"op": "add", "path": "/spec/sso", "value": {"provider": "keycloak", "resources": {"requests": {"cpu": "512m", "memory": "512Mi"}, "limits": {"cpu": "1024m", "memory": "1024Mi"}} }}]' Note RHSSO created by the Red Hat OpenShift GitOps only persists the changes that are made by the operator. If the RHSSO restarts, any additional configuration created by the Admin in RHSSO is deleted.

Commands:
oc edit argocd [argocd-instance-name] -n [namespace]
metadata rbac: policy: 'g, rbacsystem:cluster-admins, role:admin' scopes: '[groups]'
metadata rbac: policy: <name>, <email>, role:<admin> scopes: '[groups]'
oc -n openshift-gitops patch argocd openshift-gitops --type='json' -p='[{"op": "add", "path": "/spec/sso", "value": {"provider": "keycloak", "resources": {"requests": {"cpu": "512m", "memory": "512Mi"}, "limits": {"cpu": "1024m", "memory": "1024Mi"}} }}]'
Chapter 81. KafkaConnectTemplate schema reference Used in: KafkaConnectSpec , KafkaMirrorMaker2Spec Property Property type Description deployment DeploymentTemplate The deployment property has been deprecated. Kafka Connect and MirrorMaker 2 operands do not use Deployment resources anymore. This field will be ignored. Template for Kafka Connect Deployment . podSet ResourceTemplate Template for Kafka Connect StrimziPodSet resource. pod PodTemplate Template for Kafka Connect Pods . apiService InternalServiceTemplate Template for Kafka Connect API Service . headlessService InternalServiceTemplate Template for Kafka Connect headless Service . connectContainer ContainerTemplate Template for the Kafka Connect container. initContainer ContainerTemplate Template for the Kafka init container. podDisruptionBudget PodDisruptionBudgetTemplate Template for Kafka Connect PodDisruptionBudget . serviceAccount ResourceTemplate Template for the Kafka Connect service account. clusterRoleBinding ResourceTemplate Template for the Kafka Connect ClusterRoleBinding. buildPod PodTemplate Template for Kafka Connect Build Pods . The build pod is used only on OpenShift. buildContainer ContainerTemplate Template for the Kafka Connect Build container. The build container is used only on OpenShift. buildConfig BuildConfigTemplate Template for the Kafka Connect BuildConfig used to build new container images. The BuildConfig is used only on OpenShift. buildServiceAccount ResourceTemplate Template for the Kafka Connect Build service account. jmxSecret ResourceTemplate Template for Secret of the Kafka Connect Cluster JMX authentication.

Commands:
B.5. Glock Holders Table B.5, "Glock holder flags" shows the meanings of the different glock holder flags. Table B.5. Glock holder flags Flag Name Meaning a Async Do not wait for glock result (will poll for result later) A Any Any compatible lock mode is acceptable c No cache When unlocked, demote DLM lock immediately e No expire Ignore subsequent lock cancel requests E Exact Must have exact lock mode F First Set when holder is the first to be granted for this lock H Holder Indicates that requested lock is granted p Priority Enqueue holder at the head of the queue t Try A "try" lock T Try 1CB A "try" lock that sends a callback W Wait Set while waiting for request to complete The most important holder flags are H (holder) and W (wait) as mentioned earlier, since they are set on granted lock requests and queued lock requests respectively. The ordering of the holders in the list is important. If there are any granted holders, they will always be at the head of the queue, followed by any queued holders. If there are no granted holders, then the first holder in the list will be the one that triggers the state change. Since demote requests are always considered higher priority than requests from the file system, that might not always directly result in a change to the state requested. The glock subsystem supports two kinds of "try" lock. These are useful both because they allow the taking of locks out of the normal order (with suitable back-off and retry) and because they can be used to help avoid resources in use by other nodes. The normal t (try) lock is just what its name indicates; it is a "try" lock that does not do anything special. The T ( try 1CB ) lock, on the other hand, is identical to the t lock except that the DLM will send a single callback to current incompatible lock holders. One use of the T ( try 1CB ) lock is with the iopen locks, which are used to arbitrate among the nodes when an inode's i_nlink count is zero, and determine which of the nodes will be responsible for deallocating the inode. The iopen glock is normally held in the shared state, but when the i_nlink count becomes zero and ->evict_inode () is called, it will request an exclusive lock with T ( try 1CB ) set. It will continue to deallocate the inode if the lock is granted. If the lock is not granted it will result in the node(s) which were preventing the grant of the lock marking their glock(s) with the D (demote) flag, which is checked at ->drop_inode () time in order to ensure that the deallocation is not forgotten. This means that inodes that have zero link count but are still open will be deallocated by the node on which the final close () occurs. Also, at the same time as the inode's link count is decremented to zero the inode is marked as being in the special state of having zero link count but still in use in the resource group bitmap. This functions like the ext3 file system3's orphan list in that it allows any subsequent reader of the bitmap to know that there is potentially space that might be reclaimed, and to attempt to reclaim it.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install AMQ Spring Boot Starter in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with AMQ Spring Boot Starter, you must install Apache Maven . To use AMQ Spring Boot Starter, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.amqphub.spring</groupId> <artifactId>amqp-10-jms-spring-boot-starter</artifactId> <version>2.3.3.redhat-00001</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, AMQ Spring Boot Starter can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the AMQ Clients 2.8.0 Spring Boot Starter Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-clients-2.8.0-spring-boot-starter-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" .

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.amqphub.spring</groupId> <artifactId>amqp-10-jms-spring-boot-starter</artifactId> <version>2.3.3.redhat-00001</version> </dependency>
unzip amq-clients-2.8.0-spring-boot-starter-maven-repository.zip
Part V. Deprecated Functionality This part provides an overview of functionality that has been deprecated in all minor releases up to Red Hat Enterprise Linux 7.3. Deprecated functionality continues to be supported until the end of life of Red Hat Enterprise Linux 7. Deprecated functionality will likely not be supported in future major releases of this product and is not recommended for new deployments. For the most recent list of deprecated functionality within a particular major release, refer to the latest version of release documentation. Deprecated hardware components are not recommended for new deployments on the current or future major releases. Hardware driver updates are limited to security and critical fixes only. Red Hat recommends replacing this hardware as soon as reasonably feasible. A package can be deprecated and not recommended for further use. Under certain circumstances, a package can be removed from a product. Product documentation then identifies more recent packages that offer functionality similar, identical, or more advanced to the one deprecated, and provides further recommendations.

Commands:
Chapter 47. Security USBGuard enables blocking USB devices while the screen is locked as a Technology Preview With the USBGuard framework, you can influence how an already running usbguard-daemon instance handles newly inserted USB devices by setting the value of the InsertedDevicePolicy runtime parameter. This functionality is provided as a Technology Preview, and the default choice is to apply the policy rules to figure out whether to authorize the device or not. See the Blocking USB devices while the screen is locked Knowledge Base article: https://access.redhat.com/articles/3230621 (BZ#1480100) pk12util can now import certificates signed with RSA-PSS The pk12util tool now provides importing a certificate signed with the RSA-PSS algorithm as a Technology Preview. Note that if the corresponding private key is imported and has the PrivateKeyInfo.privateKeyAlgorithm field that restricts the signing algorithm to RSA-PSS , it is ignored when importing the key to a browser. See https://bugzilla.mozilla.org/show_bug.cgi?id=1413596 for more information. (BZ# 1431210 ) Support for certificates signed with RSA-PSS in certutil has been improved Support for certificates signed with the RSA-PSS algorithm in the certutil tool has been improved. Notable enhancements and fixes include: The --pss option is now documented. The PKCS#1 v1.5 algorithm is no longer used for self-signed signatures when a certificate is restricted to use RSA-PSS . Empty RSA-PSS parameters in the subjectPublicKeyInfo field are no longer printed as invalid when listing certificates. The --pss-sign option for creating regular RSA certificates signed with the RSA-PSS algorithm has been added. Support for certificates signed with RSA-PSS in certutil is provided as a Technology Preview. (BZ# 1425514 ) NSS is now able to verify RSA-PSS signatures on certificates With the new version of the nss package, the Network Security Services (NSS) libraries now provide verifying RSA-PSS signatures on certificates as a Technology Preview. Prior to this update, clients using NSS as the SSL backend were not able to establish a TLS connection to a server that offered only certificates signed with the RSA-PSS algorithm. Note that the functionality has the following limitations: The algorithm policy settings in the /etc/pki/nss-legacy/rhel7.config file do not apply to the hash algorithms used in RSA-PSS signatures. RSA-PSS parameters restrictions between certificate chains are ignored and only a single certificate is taken into account. (BZ# 1432142 ) SECCOMP can be now enabled in libreswan As a Technology Preview, the seccomp=enabled|tolerant|disabled option has been added to the ipsec.conf configuration file, which makes it possible to use the Secure Computing mode (SECCOMP). This improves the syscall security by whitelisting all the system calls that Libreswan is allowed to execute. For more information, see the ipsec.conf(5) man page. (BZ# 1375750 )

Commands:
Part II. Designing a decision service using PMML models As a business rules developer, you can use Predictive Model Markup Language (PMML) to define statistical or data-mining models that you can integrate with your decision services in Red Hat Process Automation Manager. Red Hat Process Automation Manager includes consumer conformance support of PMML 4.2.1 for Regression, Scorecard, Tree, and Mining models. Red Hat Process Automation Manager does not include a built-in PMML model editor, but you can use an XML or PMML-specific authoring tool to create PMML models and then integrate them with your Red Hat Process Automation Manager projects. For more information about PMML, see the DMG PMML specification . Note You can also design your decision service using Decision Model and Notation (DMN) models and include your PMML models as part of your DMN service. For information about DMN support in Red Hat Process Automation Manager 7.13, see the following resources: Getting started with decision services (step-by-step tutorial with a DMN decision service example) Designing a decision service using DMN models (overview of DMN support and capabilities in Red Hat Process Automation Manager)

Commands:
Chapter 46. Networking Cisco usNIC driver Cisco Unified Communication Manager (UCM) servers have an optional feature to provide a Cisco proprietary User Space Network Interface Controller (usNIC), which allows performing Remote Direct Memory Access (RDMA)-like operations for user-space applications. The libusnic_verbs driver, which is available as a Technology Preview, makes it possible to use usNIC devices via standard InfiniBand RDMA programming based on the Verbs API. (BZ#916384) Cisco VIC kernel driver The Cisco VIC Infiniband kernel driver, which is available as a Technology Preview, allows the use of Remote Directory Memory Access (RDMA)-like semantics on proprietary Cisco architectures. (BZ#916382) Trusted Network Connect Trusted Network Connect, available as a Technology Preview, is used with existing network access control (NAC) solutions, such as TLS, 802.1X, or IPsec to integrate endpoint posture assessment; that is, collecting an endpoint's system information (such as operating system configuration settings, installed packages, and others, termed as integrity measurements). Trusted Network Connect is used to verify these measurements against network access policies before allowing the endpoint to access the network. (BZ#755087) SR-IOV functionality in the qlcnic driver Support for Single-Root I/O virtualization (SR-IOV) has been added to the qlcnic driver as a Technology Preview. Support for this functionality will be provided directly by QLogic, and customers are encouraged to provide feedback to QLogic and Red Hat. Other functionality in the qlcnic driver remains fully supported. (BZ#1259547) The libnftnl and nftables packages Starting with Red Hat Enterprise Linux 7.3., the nftables and libnftl packages are available as a Technology Preview. The nftables packages provide a packet-filtering tool, with numerous improvements in convenience, features, and performance over packet-filtering tools. It is the designated successor to the iptables , ip6tables , arptables , and ebtables utilities. The libnftnl packages provide a library for low-level interaction with nftables Netlink's API over the libmnl library. (BZ#1332585) The flower classifier with off-loading support flower is a Traffic Control (TC) classifier intended to allow users to configure matching on well-known packet fields for various protocols. It is intended to make it easier to configure rules over the u32 classifier for complex filtering and classification tasks. flower also supports the ability to off-load classification and action rules to underlying hardware if the hardware supports it. The flower TC classifier is now provided as a Technology Preview. (BZ#1393375)

Commands:
Preface This guide contains information about installing, updating, and uninstalling Red Hat Directory Server and the Password Synchronization service. Additionally, this guide includes information about migrating Directory Server 10 to Directory Server 11. To familiarize yourself with the concepts of a directory service and planning a Directory Server installation, see the Red Hat Directory Server Deployment Guide . For details about managing and configuring a Directory Server instance after the installation, see the Red Hat Directory Server Administration Guide .

Commands:
4.241. pykickstart 4.241.1. RHBA-2011:1682 - pykickstart bug fix update An updated pykickstart package that fixes a bug is now available for Red Hat Enterprise Linux 6. The pykickstart package contains a python library for manipulating kickstart files. Bug Fix BZ# 656278 When validating the syntax of a kickstart file in certain locales, the ksvalidator tool terminated with a traceback if the kickstart file contained any deprecated syntax. This has been fixed: ksvalidator terminates no longer and prints a warning message that the kickstart file contains a deprecated syntax. All users of pykickstart are advised to upgrade to this updated package, which resolves this bug.

Commands:
Chapter 1. Migrating Red Hat Single Sign-On 7.6 to Red Hat build of Keycloak The purpose of this guide is to document the steps that are required to successfully migrate Red Hat Single Sign-On 7.6 to Red Hat build of Keycloak 26.0. The instructions address migration of the following elements: Red Hat Single Sign-On 7.6 server Operator deployments on OpenShift Template deployments on OpenShift Applications secured by Red Hat Single Sign-On 7.6 Custom providers Custom themes This guide also includes guidelines for migrating upstream Keycloak to Red Hat build of Keycloak 26.0. Before you start the migration, you might consider installing a new instance of Red Hat build of Keycloak to become familiar with the changes for this release. See the Red Hat build of Keycloak Getting Started Guide .

Commands:
5.2. Changing the Database Checkpoint Interval At regular intervals, the Directory Server writes operations logged in the transaction log to the database index files and logs a checkpoint entry in the database transaction log. By indicating which changes have already been written to the database indexes, checkpoint entries indicate where to begin recovery from the transaction log, thus speeding up the recovery process. By default, the Directory Server is set up to send a checkpoint entry to the database transaction log every 60 seconds. Increasing the checkpoint interval may increase the performance of directory write operations. However, increasing the checkpoint interval may also increase the amount of time required to recover directory databases after a disorderly shutdown and require more disk space due to large database transaction log files. Therefore, only modify this attribute if you are familiar with database optimization and can fully assess the effect of the change. 5.2.1. Changing the Database Checkpoint Interval Using the Command Line To change the database checkpoint interval using the command line, enter: This example changes the interval to 120 seconds. 5.2.2. Changing the Database Checkpoint Interval Using the Web Console To change the database checkpoint interval using the Web Console: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. On the Database tab, select Global Database Configuration . Click Show Advanced Settings . Update the value in the Database Checkpoint Interval field. Click Save Configuration .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend config set --checkpoint-interval= 120