mtpti5iD/redhat-docs_dataset huggingface dataset:
7.223. scl-utils 7.223.1. RHBA-2013:0400 - scl-utils bug fix and enhancement update Updated scl-utils packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The scl-utils packages provide a runtime utility and RPM packaging macros for packaging Software Collections. Software Collections allow users to concurrently install multiple versions of the same RPM packages on the system. Using the scl utility, users may enable specific versions of RPMs, which are installed into the /opt directory. BZ#855999 The scl-utils packages have been upgraded to upstream version 20120927, which provides a number of bug fixes and enhancements over the version. The following list includes notable bug fixes: The fix has been provided for a double free or corruption error when reading commands from the standard input, which could have led to a segmentation fault under certain circumstances. The /usr/lib/rpm/redhat/brp-compress script now properly compresses man pages in %_mandir. All users who require scl-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
7.11. bash 7.11.1. RHBA-2013:0306 - bash bug fix and enhancement update Updated bash packages that fix three bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The bash packages provide the Bash (Bourne-again shell) shell, which is the default shell for Red Hat Enterprise Linux. Bug Fixes BZ# 695656 Prior to this update, the trap handler could, under certain circumstances, lose signals during another trap initialization. This update blocks the signal while the trap string and handler are being modified. Now, the signals are no longer lost. BZ# 799958 Prior to this update, the manual page for trap in Bash did not mention that signals ignored upon entry cannot be listed later. This is now fixed and the manual page entry text is amended to "Signals ignored upon entry to the shell cannot be trapped, reset or listed". BZ#800473 Prior to this update, the Bash shell called the trap handler within a signal handler when a SIGCHLD signal was received in job control mode and a handler for the signal was installed. This was a security risk and could cause Bash to enter a deadlock or to terminate unexpectedly with a segmentation fault due to memory corruption. With this update, the trap handler is now called outside of the signal handler, and Bash no longer enters a deadlock. Enhancement BZ# 677439 This update enables the system-wide "/etc/bash.bash_logout" file. This allows administrators to write system-wide logout actions for all users. All users of bash are advised to upgrade to these updated packages, which fix these bugs and add this enhancement. 7.11.2. RHBA-2013:1096 - bash bug fix update Updated bash packages that fix one bug are now available for Red Hat Enterprise Linux 6. The GNU Bourne Again shell (Bash) is a shell and command language interpreter compatible with the Bourne shell (sh). Bash is the default shell for Red Hat Enterprise Linux. Bug Fix BZ# 982610 When a trap handler was invoked while running another trap handler, which was invoked during a pipeline call, bash was unresponsive. With this update, pipeline calls are saved and subsequently restored in this scenario, and bash responds normally. All users of bash are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.2. Setting up Users to Be Enrolled When the Token Processing System is installed, one of its configuration settings is the LDAP directory which contains the users who are allowed to enroll a token. Only users who are stored within this authentication directory are allowed to enroll, format, or have a token. Before attempting to enroll a token or smart card, make sure that the person requesting the operation has an entry in the LDAP directory. The TPS is configured to look at a specific base DN in the LDAP directory. This is configured in the TPS's CS.cfg : For a user to be allowed to enroll a token, the user must be somewhere below the base DN. If the user does not already have an entry, then the administrator must add the user to the specified LDAP directory in the specified base DN before any tokens can be enrolled for the user.

Commands:
auth.instance.0.baseDN= dc=example,dc=com auth.instance.0.hostport= server.example.com:389
/usr/bin/ldapmodify -a -D "cn=Directory Manager" -w secret -p 389 -h server.example.com dn: uid=jsmith,ou=People, dc=example,dc=com objectclass: person objectclass: inetorgperson objectclass: top uid: jsmith cn: John Smith email: jsmith@example.com userPassword: secret
Chapter 6. Container validation If your driver is included as part of RHOSO (In-tree), you do not need to certify a custom container image. However, if you provide your own container image (Out-of-tree), you must certify the container image with Red Hat Connect as a prerequisite. For more information on container image certification, see Integrating partner content . When you create a new product request for RHOSO on Red Hat Connect, you can initially select Tech-Preview as the Release Category. After certifying the container image, you can choose the General Availability (GA) option.

Commands:
29.4. Saving Data Sometimes it is useful to save samples at a specific time. For example, when profiling an executable, it may be useful to gather different samples based on different input data sets. If the number of events to be monitored exceeds the number of counters available for the processor, multiple runs of OProfile can be used to collect data, saving the sample data to different files each time. To save the current set of sample files, execute the following command, replacing name with a unique descriptive name for the current session. The directory /var/lib/oprofile/samples/ name / is created and the current sample files are copied to it.

Commands:
~]# opcontrol --save= name
4.10. PTP IEEE 1588 Precision Time Protocol Version 2 (PTPv2) is used to precisely synchronize clocks in an Ethernet network. When used in conjunction with hardware support, it is capable of achieving clock accuracy in the sub-microsecond range. As of Red Hat Enterprise Linux 6.5, PTP is fully supported by Red Hat and compatible with the Broadcom (bnx2x, tg3), Intel (e1000e, igb, ixgbe), and Solarflare (sfc) network drivers.

Commands:
13.5. Setting Search Attributes for Users and User Groups When searching entries for a specified keyword using the ipa user-find keyword and ipa group-find keyword commands, IdM only searches certain attributes. Most notably: In user searches: first name, last name, user name (login ID), job title, organization unit, phone number, UID, email address. In group searches: group name, description. The following procedure shows how to configure IdM to search other attributes as well. Note that IdM always searches the default attributes. For example, even if you remove the job title attribute from the list of user search attributes, IdM will still search user titles. Prerequisites Before adding a new attribute, make sure that a corresponding index exists within the LDAP directory for this attribute. Most standard LDAP attributes have indexes in LDAP, but if you want to add a custom attribute, you must create an index manually. See Creating Standard Indexes in the Red Hat Directory Server 10 Administration Guide . Web UI: Setting Search Attributes Select IPA Server Configuration . In the User Options area, set the user search attributes in User search fields . In the Group Options area, set the group search attributes in Group search fields . Click Save at the top of the page. Command Line: Setting Search Attributes Use the ipa config-mod command with these options: --usersearch defines a new list of search attributes for users --groupsearch defines a new list of search attributes for groups For example:

Commands:
ipa config-mod --usersearch="uid,givenname,sn,telephonenumber,ou,title" ipa config-mod --groupsearch="cn,description"
1.3.2. Server Weight and Scheduling The administrator of Load Balancer Add-On can assign a weight to each node in the real server pool. This weight is an integer value which is factored into any weight-aware scheduling algorithms (such as weighted least-connections) and helps the LVS router more evenly load hardware with different capabilities. Weights work as a ratio relative to one another. For instance, if one real server has a weight of 1 and the other server has a weight of 5, then the server with a weight of 5 gets 5 connections for every 1 connection the other server gets. The default value for a real server weight is 1. Although adding weight to varying hardware configurations in a real server pool can help load-balance the cluster more efficiently, it can cause temporary imbalances when a real server is introduced to the real server pool and the virtual server is scheduled using weighted least-connections. For example, suppose there are three servers in the real server pool. Servers A and B are weighted at 1 and the third, server C, is weighted at 2. If server C goes down for any reason, servers A and B evenly distribute the abandoned load. However, once server C comes back online, the LVS router sees it has zero connections and floods the server with all incoming requests until it is on par with servers A and B.

Commands:
function::user_string2_utf16 Name function::user_string2_utf16 - Retrieves UTF-16 string from user memory with alternative error string Synopsis Arguments addr The user address to retrieve the string from err_msg The error message to return when data isn't available Description This function returns a null terminated UTF-8 string converted from the UTF-16 string at a given user memory address. Reports the given error message on string copy fault or conversion error.

Commands:
user_string2_utf16:string(addr:long,err_msg:string)
Deploying OpenShift Data Foundation using IBM Z Red Hat OpenShift Data Foundation 4.14 Instructions on deploying Red Hat OpenShift Data Foundation to use local storage on IBM Z Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install Red Hat OpenShift Data Foundation to use local storage on IBM Z. Note While this document refers only to IBM Z, all information in it also applies to IBM(R) LinuxONE.

Commands:
Chapter 7. Supported integration products AMQ Streams 1.7 supports integration with the following Red Hat products. Red Hat Single Sign-On 7.4 and later for OAuth 2.0 authentication and OAuth 2.0 authorization Red Hat 3scale API Management 2.6 and later to secure the Kafka Bridge and provide additional API management features Red Hat Debezium 1.4 and later for monitoring databases and creating event streams Service Registry 2020-Q4 and later as a centralized store of service schemas for data streaming For information on the functionality these products can introduce to your AMQ Streams deployment, refer to the AMQ Streams 1.7 documentation.

Commands:
10.3. Querying Cluster Property Settings In most cases, when you use the pcs command to display values of the various cluster components, you can use pcs list or pcs show interchangeably. In the following examples, pcs list is the format used to display an entire list of all settings for more than one property, while pcs show is the format used to display the values of a specific property. To display the values of the property settings that have been set for the cluster, use the following pcs command. To display all of the values of the property settings for the cluster, including the default values of the property settings that have not been explicitly set, use the following command. To display the current value of a specific cluster property, use the following command. For example, to display the current value of the cluster-infrastructure property, execute the following command: For informational purposes, you can display a list of all of the default values for the properties, whether they have been set to a value other than the default or not, by using the following command.

Commands:
pcs property list
pcs property list --all
pcs property show property
pcs property show cluster-infrastructure Cluster Properties: cluster-infrastructure: cman
pcs property [list|show] --defaults
3.12. Searching for Storage The following table describes all search options for storage. Table 3.8. Searching for Storage Property (of resource or resource-type) Type Description (Reference) Hosts. hosts-prop Depends on property type The property of the hosts associated with the storage. Clusters. clusters-prop Depends on property type The property of the clusters associated with the storage. name String The unique name that identifies the storage on the network. status String The status of the storage domain. external_status String The health status of the storage domain as reported by external systems and plug-ins. datacenter String The data center to which the storage belongs. type String The type of the storage. size Integer The size of the storage. used Integer The amount of the storage that is used. committed Integer The amount of the storage that is committed. sortby List Sorts the returned results by one of the resource properties. page Integer The page number of results to display. Example Storage: size > 200 or used < 50 This example returns a list of storage with total storage space greater than 200 GB, or used storage space less than 50 GB.

Commands:
Chapter 4. Advisories related to this release The following advisories are issued to document bug fixes and CVE fixes included in this release: RHSA-2023:5725 RHSA-2023:5726 RHSA-2023:5727 RHSA-2023:5728 RHSA-2023:5729 RHSA-2023:5730 RHSA-2023:5731 RHSA-2023:5732 RHSA-2023:5733 RHSA-2023:5761 Revised on 2024-05-10 09:06:27 UTC

Commands:
Chapter 6. Using the Topology plugin Topology is a front-end plugin that enables you to view the workloads as nodes that power any service on the Kubernetes cluster. 6.1. Enable users to use the Topology plugin The Topology plugin is defining additional permissions. When Authorization is enabled, to enable users to use the Topology plugin, grant them: The topology.view.read read permission to view the Topology panel. The kubernetes.proxy use permission to view the pod logs. The catalog-entity read permission to view the Red Hat Developer Hub software catalog items. Prerequisites You are managing Authorization by using external files . Procedure Add the following permission policies to your rbac-policy.csv file to create a topology-viewer role that has access to the Topology plugin features, and add the role to the users requiring this authorization: 1 Grants the user the ability to see the Topology panel. 2 Grants the user the ability to view the pod logs. 3 Grants the user the ability to see the catalog item. 6.2. Using the Topology plugin Prerequisites Your Red Hat Developer Hub instance is installed and running. You have installed the Topology plugin. You have enabled the users to use the Topology plugin . Procedure Open your RHDH application and select a component from the Catalog page. Go to the TOPOLOGY tab and you can view the workloads such as deployments or pods as nodes. Select a node and a pop-up appears on the right side that contains two tabs: Details and Resources . The Details and Resources tabs contain the associated information and resources for the node. Click the Open URL button on the top of a node. Click the Open URL button to access the associated Ingresses and run your application in a new tab.

Commands:
g, user:default/<YOUR_USERNAME>, role:default/topology-viewer p, role:default/topology-viewer, topology.view.read, read, allow 1 p, role:default/topology-viewer, kubernetes.proxy, use, allow 2 p, role:default/topology-viewer, catalog-entity, read, allow 3
5.11. Cluster Resources Cleanup If a resource has failed, a failure message appears when you display the cluster status. If you resolve that resource, you can clear that failure status with the pcs resource cleanup command. This command resets the resource status and failcount, telling the cluster to forget the operation history of a resource and re-detect its current state. The following command cleans up the resource specified by resource_id .

Commands:
pcs resource cleanup resource_id
7.4.2.2. Adding Fonts to xfs To add fonts to the core X font subsystem ( xfs ), follow these steps: If it does not already exist, create a directory called /usr/share/fonts/local/ using the following command as root: If creating the /usr/share/fonts/local/ directory is necessary, it must be added to the xfs path using the following command as root: Copy the new font file into the /usr/share/fonts/local/ directory Update the font information by issuing the following command as root: Reload the xfs font server configuration file by issuing the following command as root:

Commands:
mkdir /usr/share/fonts/local/
chkfontpath --add /usr/share/fonts/local/
ttmkfdir -d /usr/share/fonts/local/ -o /usr/share/fonts/local/fonts.scale
service xfs reload
Chapter 51. Getting started with DPDK The data plane development kit (DPDK) provides libraries and network drivers to accelerate packet processing in user space. Administrators use DPDK, for example, in virtual machines to use Single Root I/O Virtualization (SR-IOV) to reduce latencies and increase I/O throughput. Note Red Hat does not support experimental DPDK APIs. 51.1. Installing the dpdk package To use DPDK, install the dpdk package. Procedure Use the yum utility to install the dpdk package: 51.2. Additional resources Network Adapter Fast Datapath Feature Support Matrix

Commands:
yum install dpdk
A.3. Changing Passwords The ldappasswd command can either set a new user-defined password or generate a new password for an account. Other settings (for bind information, connection information, or other command settings) may be required and are listed in the OpenLDAP manpages. Important Password change operations must be run over a secure connection, such as TLS, STARTTLS, or SASL. For information on how to configure TLS for LDAP clients, see Section 9.9.4, "Authenticating Using a Certificate" . Example A.3. Directory Manager Changing a User's Password Over TLS The Directory Manager changes the password of the user uid=tuser1,ou=People,dc=example,dc=com to new_password over TLS. Example A.4. Directory Manager Generating a User's Password The Directory Manager generates the password of the user uid=tuser2,ou=People,dc=example,dc=com over TLS. Example A.5. User Changing His Own Password A user, tuser3 , changes the password from old_newpassword to new_password over TLS. Example A.6. User Authenticating with DIGEST_MD5 and Changing His Password A user, jsmith, authenticates with GSS-API and changes the password to new_password . Example A.7. User Already Authenticated by Kerberos Prompts for a New Password A user, who has already authenticated by Kerberos, prompts for the new password. This is not performed over TLS.

Commands:
ldappasswd -x -D bind_dn -W -p server_port -h server_hostname [-A | -a oldPassword ] [-S | -s newPassword ] [ user ]
ldappasswd -D "cn=Directory Manager" -W -ZZ -p 389 -h server.example.com -x -s new_password "uid=tuser1,ou=People,dc=example,dc=com"
ldappasswd -D "cn=Directory Manager" -W -ZZ -p 389 -h server.example.com -x "uid=tuser2,ou=People,dc=example,dc=com"
ldappasswd -p 389 -h server.example.com -ZZ -x -D "uid=tuser3,ou=People,dc=example,dc=com" -W -a old_password -s new_password
ldappasswd -p 389 -h server.example.com -O noplain,minssf=1,maxbufsize=512 -Y GSSAPI -U "dn:uid=jsmith,ou=people,dc=example,dc=com" -R EXAMPLE.COM -W -s new_password
ldappasswd -p 389 -h server.example.com -O noplain,minssf=1,maxbufsize=512 -I
18.3.3. Saving and Restoring IPTables Rules Changes to iptables are transitory; if the system is rebooted or if the iptables service is restarted, the rules are automatically flushed and reset. To save the rules so that they are loaded when the iptables service is started, use the following command: The rules are stored in the file /etc/sysconfig/iptables and are applied whenever the service is started or the machine is rebooted.

Commands:
service iptables save
5.9. Propagating The Configuration File: New Cluster For newly defined clusters, you must propagate the configuration file to the cluster nodes as follows: Log in to the node where you created the configuration file. Using the scp command, copy the /etc/cluster/cluster.conf file to all nodes in the cluster. Note Propagating the cluster configuration file this way is necessary for the first time a cluster is created. Once a cluster is installed and running, the cluster configuration file is propagated using the Red Hat cluster management GUI Send to Cluster button. For more information about propagating the cluster configuration using the GUI Send to Cluster button, refer to Section 6.3, "Modifying the Cluster Configuration" .

Commands:
17.5. Setting up the rndc Service The ipa-dns-install command does not automatically configure the system's rndc service. This must be configured manually, after DNS is configured for IdM. Create the rndc configuration file and key. This may require some user input to create entropy while the key is being created. Change the owner and permissions of the rndc key file.

Commands:
/usr/sbin/rndc-confgen -a /sbin/restorecon /etc/rndc.conf
chown root:named /etc/rndc.key chmod 0640 /etc/rndc.key
6.4. Removing a Server from the Topology IdM does not allow removing a server from the topology if one of the following applies: the server being removed is the only server connecting other servers with the rest of the topology; this would cause the other servers to become isolated, which is not allowed the server being removed is your last CA or DNS server In these situations, the attempt fails with an error. For example, on the command line: 6.4.1. Web UI: Removing a Server from the Topology To remove a server from the topology without uninstalling the server components from the machine: Select IPA Server Topology IPA Servers . Click on the name of the server you want to delete. Figure 6.13. Selecting a Server Click Delete Server . 6.4.2. Command Line: Removing a Server from the Topology Important Removing a server is an irreversible action. If you remove a server, the only way to introduce it back into the topology is to install a new replica on the machine. To remove server1.example.com : On another server, run the ipa server-del command to remove server1.example.com . The command removes all topology segments pointing to the server: On server1.example.com , run the ipa server-install --uninstall command to uninstall the server components from the machine.

Commands:
ipa server-del Server name: server1.example.com Removing server1.example.com from replication topology, please wait ipa: ERROR: Server removal aborted: Removal of 'server1.example.com' leads to disconnected topology in suffix 'domain': Topology does not allow server server2.example.com to replicate with servers: server3.example.com server4.example.com
[user@server2 ~]USD ipa server-del Server name: server1.example.com Removing server1.example.com from replication topology, please wait ---------------------------------------------------------- Deleted IPA server "server1.example.com" ----------------------------------------------------------
ipa server-install --uninstall