mtpti5iD/redhat-docs_dataset huggingface dataset:
15.20. Setting Replication Timeout Periods Suppliers must have an exclusive connection to a consumer to send updates to the directory. As mentioned in Section 15.3.3, "Preventing Monopolization of a Consumer in Multi-Supplier Replication" , it is possible to configure a wait time for suppliers attempting to connect to a consumer, so that the supplier does not hang while the consumer is tied up with another supplier. It is also possible to set a timeout period for a supplier, so that it does not stay connected to a consumer interminably attempting to send updates over a slow or broken connection. There are two attributes which set the timeout period: nsDS5ReplicaTimeout sets the number of seconds that the replication operation waits for a response from the consumer before timing out and failing. To set the optimum number, check the access logs to see the average amount of time that the replication process takes, and set the timeout period accordingly. nsDS5DebugReplicaTimeout sets the timeout period for the replication operation when debug logging is enabled. This setting may be appreciably higher than the nsDS5ReplicaTimeout setting because debug logging can slow down directory operations. This attribute can optionally set an error log level where this parameter is applied; the default is replication debugging (8192). Both of these attributes are set in the replication agreement of the replicated suffix:

Commands:
ldapmodify -D "cn=Directory Manager" -W -x dn: cn= example-agreement ,cn=replica,cn= dc\3Dexample\2Cdc\3Dcom ,cn=mapping tree,cn=config changetype: modify add: nsDS5ReplicaTimeout nsDS5ReplicaTimeout: 600 - add: nsDS5DebugReplicaTimeout nsDS5DebugReplicaTimeout: 6000
Chapter 21. Red Hat Software Collections Red Hat Software Collections is a Red Hat content set that provides a set of dynamic programming languages, database servers, and related packages that you can install and use on all supported releases of Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 on AMD64 and Intel 64 architectures. Red Hat Developer Toolset is included as a separate Software Collection. Red Hat Developer Toolset is designed for developers working on the Red Hat Enterprise Linux platform. It provides current versions of the GNU Compiler Collection, GNU Debugger, and other development, debugging, and performance monitoring tools. Since Red Hat Software Collections 2.3, the Eclipse development platform is provided as a separate Software Collection. Dynamic languages, database servers, and other tools distributed with Red Hat Software Collections do not replace the default system tools provided with Red Hat Enterprise Linux, nor are they used in preference to these tools. Red Hat Software Collections uses an alternative packaging mechanism based on the scl utility to provide a parallel set of packages. This set enables optional use of alternative package versions on Red Hat Enterprise Linux. By using the scl utility, users can choose which package version they want to run at any time. Important Red Hat Software Collections has a shorter life cycle and support term than Red Hat Enterprise Linux. For more information, see the Red Hat Software Collections Product Life Cycle . See the Red Hat Software Collections documentation for the components included in the set, system requirements, known problems, usage, and specifics of individual Software Collections. See the Red Hat Developer Toolset documentation for more information about the components included in this Software Collection, installation, usage, known problems, and more.

Commands:
5.4.16.4. Converting a Mirrored LVM Device to a RAID1 Device You can convert an existing mirrored LVM device to a RAID1 LVM device with the lvconvert command by specifying the --type raid1 argument. This renames the mirror subvolumes ( *_mimage_* ) to RAID subvolumes ( *_rimage_* ). In addition, the mirror log is removed and metadata subvolumes ( *_rmeta_* ) are created for the data subvolumes on the same physical volumes as the corresponding data subvolumes. The following example shows the layout of a mirrored logical volume my_vg/my_lv . The following command converts the mirrored logical volume my_vg/my_lv to a RAID1 logical volume.

Commands:
lvs -a -o name,copy_percent,devices my_vg LV Copy% Devices my_lv 15.20 my_lv_mimage_0(0),my_lv_mimage_1(0) [my_lv_mimage_0] /dev/sde1(0) [my_lv_mimage_1] /dev/sdf1(0) [my_lv_mlog] /dev/sdd1(0)
lvconvert --type raid1 my_vg/my_lv lvs -a -o name,copy_percent,devices my_vg LV Copy% Devices my_lv 100.00 my_lv_rimage_0(0),my_lv_rimage_1(0) [my_lv_rimage_0] /dev/sde1(0) [my_lv_rimage_1] /dev/sdf1(0) [my_lv_rmeta_0] /dev/sde1(125) [my_lv_rmeta_1] /dev/sdf1(125)
2.3. Monitoring Database Link Activity The activity for database links (chained databases) can also be displayed, however, only using the command line: The following table describes the attributes the command returns: Table 2.5. Database Link Monitoring Attributes Attribute Name Description nsAddCount The number of add operations received. nsDeleteCount The number of delete operations received. nsModifyCount The number of modify operations received. nsRenameCount The number of rename operations received. nsSearchBaseCount The number of base-level searches received. nsSearchOneLevelCount The number of one-level searches received. nsSearchSubtreeCount The number of subtree searches received. nsAbandonCount The number of abandon operations received. nsBindCount The number of bind request received. nsUnbindCount The number of unbinds received. nsCompareCount The number of compare operations received. nsOperationConnectionCount The number of open connections for normal operations. nsBindConnectionCount The number of open connections for bind operations.

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com monitor chaining
5.3. Using MACsec with wpa_supplicant and NetworkManager Media Access Control Security ( MACsec , IEEE 802.1AE) encrypts and authenticates all traffic in LANs with the GCM-AES-128 algorithm. MACsec can protect not only IP but also Address Resolution Protocol (ARP), Neighbor Discovery (ND), or DHCP . While IPsec operates on the network layer (layer 3) and SSL or TLS on the application layer (layer 7), MACsec operates in the data link layer (layer 2). Combine MACsec with security protocols for other networking layers to take advantage of different security features that these standards provide. To enable MACsec with a switch that performs authentication using a pre-shared Connectivity Association Key/CAK Name (CAK/CKN) pair: Procedure Create a CAK/CKN pair. For example, the following command generates a 16-byte key in hexadecimal notation: Create the wpa_supplicant.conf configuration file and add the following lines to it: Use the values from the step to complete the mka_cak and mka_ckn lines in the wpa_supplicant.conf configuration file. See the wpa_supplicant.conf(5) man page for more information. Assuming you are using wlp61s0 to connect to your network, start wpa_supplicant using the following command: Instead of creating and editing the wpa_supplicant.conf file, Red Hat recommends using the nmcli command to configure wpa_supplicant equivalently as in the steps. The following example assumes that you already have a 16-byte hexadecimal CAK ( USDMKA_CAK ) and a 32-byte hexadecimal CKN ( USDMKA_CKN ): After this step, the macsec0 device should be configured and used for networking. For more details, see the What's new in MACsec: setting up MACsec using wpa_supplicant and (optionally) NetworkManager article. In addition, see the MACsec: a different solution to encrypt network traffic article for more information about the architecture of a MACsec network, use case scenarios, and configuration examples.

Commands:
~]USD dd if=/dev/urandom count=16 bs=1 2> /dev/null | hexdump -e '1/2 "%02x"'
ctrl_interface=/var/run/wpa_supplicant eapol_version=3 ap_scan=0 fast_reauth=1 network={ key_mgmt=NONE eapol_flags=0 macsec_policy=1 mka_cak=0011... # 16 bytes hexadecimal mka_ckn=2233... # 32 bytes hexadecimal }
~]# wpa_supplicant -i wlp61s0 -Dmacsec_linux -c wpa_supplicant.conf
~]# nmcli connection add type macsec con-name test-macsec+ ifname macsec0 connection.autoconnect no macsec.parent wlp61s0 macsec.mode psk macsec.mka-cak USDMKA_CAK macsec.mka-cak-flags 0 macsec.mka-ckn USDMKA_CKN ~]# nmcli connection up test-macsec+
Chapter 6. Installing a three-node cluster on OpenStack In OpenShift Container Platform version 4.17, you can install a three-node cluster on Red Hat OpenStack Platform (RHOSP). A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster on installer-provisioned infrastructure only. 6.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... 6.2. steps Installing a cluster on OpenStack with customizations

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
Chapter 335. Using OpenApi in rest-dsl You can enable the OpenApi api from the rest-dsl by configuring the apiContextPath dsl as shown below: public class UserRouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { // configure we want to use servlet as the component for the rest DSL // and we enable json binding mode restConfiguration().component("netty-http").bindingMode(RestBindingMode.json) // and output using pretty print .dataFormatProperty("prettyPrint", "true") // setup context path and port number that netty will use .contextPath("/").port(8080) // add OpenApi api-doc out of the box .apiContextPath("/api-doc") .apiProperty("api.title", "User API").apiProperty("api.version", "1.2.3") // and enable CORS .apiProperty("cors", "true"); // this user REST service is json only rest("/user").description("User rest service") .consumes("application/json").produces("application/json") .get("/{id}").description("Find user by id").outType(User.class) .param().name("id").type(path).description("The id of the user to get").dataType("int").endParam() .to("bean:userService?method=getUser(USD{header.id})") .put().description("Updates or create a user").type(User.class) .param().name("body").type(body).description("The user to update or create").endParam() .to("bean:userService?method=updateUser") .get("/findAll").description("Find all users").outType(User[].class) .to("bean:userService?method=listUsers"); } }

Commands:
public class UserRouteBuilder extends RouteBuilder { @Override public void configure() throws Exception { // configure we want to use servlet as the component for the rest DSL // and we enable json binding mode restConfiguration().component("netty-http").bindingMode(RestBindingMode.json) // and output using pretty print .dataFormatProperty("prettyPrint", "true") // setup context path and port number that netty will use .contextPath("/").port(8080) // add OpenApi api-doc out of the box .apiContextPath("/api-doc") .apiProperty("api.title", "User API").apiProperty("api.version", "1.2.3") // and enable CORS .apiProperty("cors", "true"); // this user REST service is json only rest("/user").description("User rest service") .consumes("application/json").produces("application/json") .get("/{id}").description("Find user by id").outType(User.class) .param().name("id").type(path).description("The id of the user to get").dataType("int").endParam() .to("bean:userService?method=getUser(USD{header.id})") .put().description("Updates or create a user").type(User.class) .param().name("body").type(body).description("The user to update or create").endParam() .to("bean:userService?method=updateUser") .get("/findAll").description("Find all users").outType(User[].class) .to("bean:userService?method=listUsers"); } }
probe::signal.procmask Name probe::signal.procmask - Examining or changing blocked signals Synopsis Values how Indicates how to change the blocked signals; possible values are SIG_BLOCK=0 (for blocking signals), SIG_UNBLOCK=1 (for unblocking signals), and SIG_SETMASK=2 for setting the signal mask. name Name of the probe point oldsigset_addr The old address of the signal set (sigset_t) sigset The actual value to be set for sigset_t (correct?) sigset_addr The address of the signal set (sigset_t) to be implemented

Commands:
signal.procmask
10.5.10. Listen The Listen command identifies the ports on which the Web server accepts incoming requests. By default, the Apache HTTP Server is set to listen to port 80 for non-secure Web communications and (in the /etc/httpd/conf.d/ssl.conf file which defines any secure servers) to port 443 for secure Web communications. If the Apache HTTP Server is configured to listen to a port under 1024, only the root user can start it. For port 1024 and above, httpd can be started as a regular user. The Listen directive can also be used to specify particular IP addresses over which the server accepts connections.

Commands:
Chapter 1. Ceph administration A Red Hat Ceph Storage cluster is the foundation for all Ceph deployments. After deploying a Red Hat Ceph Storage cluster, there are administrative operations for keeping a Red Hat Ceph Storage cluster healthy and performing optimally. The Red Hat Ceph Storage Administration Guide helps storage administrators to perform such tasks as: How do I check the health of my Red Hat Ceph Storage cluster? How do I start and stop the Red Hat Ceph Storage cluster services? How do I add or remove an OSD from a running Red Hat Ceph Storage cluster? How do I manage user authentication and access controls to the objects stored in a Red Hat Ceph Storage cluster? I want to understand how to use overrides with a Red Hat Ceph Storage cluster. I want to monitor the performance of the Red Hat Ceph Storage cluster. A basic Ceph storage cluster consist of two types of daemons: A Ceph Object Storage Device (OSD) stores data as objects within placement groups assigned to the OSD A Ceph Monitor maintains a master copy of the cluster map A production system will have three or more Ceph Monitors for high availability and typically a minimum of 50 OSDs for acceptable load balancing, data re-balancing and data recovery.

Commands:
Chapter 1. Backup and recovery of Red Hat Ansible Automation Platform To safeguard against unexpected data loss and application errors, it is critical that you perform periodic backups of your Red Hat Ansible Automation Platform deployment. In addition to data loss prevention, backups allow you to fall back to a different deployment state. 1.1. About backup and recovery Red Hat recommends backing up deployments of Red Hat Ansible Automation Platform in your Red Hat OpenShift Container Platform environment to prevent data loss. A backup resource of your Red Hat Ansible Automation Platform deployment includes the following: Custom deployment of specific values in the spec section of the Ansible Automation Platform custom resource object. Back up of the postgresql database. secret_key , admin_password , and broadcast_websocket secrets. Database configuration. Note Be sure to secure your backup resources because they can include sensitive information. 1.1.1. Backup recommendations Recovering from data loss requires that you plan for and create backup resources of your Red Hat Ansible Automation Platform deployments on a regular basis. At a minimum, Red Hat recommends backing up deployments of Red Hat Ansible Automation Platform under the following circumstances: Before upgrading your Red Hat Ansible Automation Platform deployments. Before upgrading your OpenShift cluster. Once per week. This is particularly important if your environment is configured for automatic upgrades.

Commands:
Chapter 14. Removing the trust using Ansible You can remove the Identity Management (IdM)/Active Directory (AD) trust on the IdM side by using an Ansible playbook. Prerequisites You have obtained a Kerberos ticket as an IdM administrator. For details, see Logging in to IdM in the Web UI: Using a Kerberos ticket . You have configured your Ansible control node to meet the following requirements: You are using Ansible version 2.15 or later. You have installed the ansible-freeipa package. The example assumes that in the ~/ MyPlaybooks / directory, you have created an Ansible inventory file with the fully-qualified domain name (FQDN) of the IdM server. The example assumes that the secret.yml Ansible vault stores your ipaadmin_password . The target node, that is the node on which the ansible-freeipa module is executed, is part of the IdM domain as an IdM client, server or replica. Procedure Navigate to your ~/ MyPlaybooks / directory: Create an del-trust.yml playbook with the following content: In the example, realm defines the AD realm name string. Save the file. Run the Ansible playbook. Specify the playbook file, the file storing the password protecting the secret.yml file, and the inventory file: Note Removing the trust configuration does not automatically remove the ID range IdM has created for AD users. This way, if you add the trust again, the existing ID range is re-used. Also, if AD users have created files on an IdM client, their POSIX IDs are preserved in the file metadata. To remove all information related to an AD trust, remove the AD user ID range after removing the trust configuration and trust object: Verification Use the ipa trust-show command to confirm that the trust has been removed. Additional resources /usr/share/doc/ansible-freeipa/README-trust.md /usr/share/doc/ansible-freeipa/playbooks/trust

Commands:
cd ~/ MyPlaybooks /
--- - name: Playbook to delete trust hosts: ipaserver vars_files: - /home/user_name/MyPlaybooks/secret.yml tasks: - name: ensure the trust is absent ipatrust: ipaadmin_password: "{{ ipaadmin_password }}" realm: ad.example.com state: absent
ansible-playbook --vault-password-file=password_file -v -i inventory del-trust.yml
ipa idrange-del AD.EXAMPLE.COM_id_range systemctl restart sssd
ipa trust-show ad.example.com ipa: ERROR: ad.example.com: trust not found
7.193. python-ethtool 7.193.1. RHBA-2013:0454 - python-ethtool bug fix and enhancement update Updated python-ethtool packages that fix four bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The python-ethtool package makes the ethtool kernel interface available within the Python programming environment to allow querying and changing of Ethernet card settings, such as speed, port, auto-negotiation, and PCI locations. Bug Fixes BZ# 692028 With this update, a typographical error has been corrected in the output of the "pethtool --help" command. BZ# 698125 Prior to this update, a memory leak occurred when the get_active_devices() and get_interfaces_info() functions were called repeatedly. This bug has been fixed and the memory leak no longer occurs in the described scenario. BZ# 714753 Due to a bug in the command-line parser, the pifconfig utility did not accept an interface as an argument if specified on the command line. Consequently, the utility displayed all interfaces rather than just information about the specified interface as was expected. The bug in the parser has been fixed and pifconfig now correctly parses passed arguments. BZ#759150 Previously, if one network interface controller (NIC) had more IP addresses, only the first address was reported multiple times. With this update, the get_ipv4_addresses() method has been implemented to report all IP addresses on the NIC. Enhancement BZ# 698192 With this update, support for devices configured with IPv6 has been added to the pifconfig utility. All users of python-ethtool are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
8.7. System Users The threshold for statically assigned UID/GID numbers (defined by the setup package in the /usr/share/doc/setup-*/uidgid file) has increased from 100 (in Red Hat Enterprise Linux 3, 4, and 5) to 200 in Red Hat Enterprise Linux 6. This change can affect systems that have 100-200 dynamically or statically assigned UID/GIDs, and cause failure in the installation and running of some applications. Dynamic UID/GID allocation now ranges from 499 downward in Red Hat Enterprise Linux 6. For static system user creation without reservations enforced by the setup package, it is recommended to use the UID/GID area of 300 and above.

Commands:
4.219. passwd 4.219.1. RHEA-2012:0328 - passwd enhancement update An updated passwd package that adds two enhancements is now available for Red Hat Enterprise Linux 6. The passwd packages contain a system utility, "passwd", which changes passwords and displays password status information using the Pluggable Authentication Modules (PAM) and Libuser libraries. Enhancements BZ# 791139 The passwd command now supports a new option, "-e", that allows the system administrator to expire the password of the specified user so that the user is forced to change the password on the login attempt. BZ# 791143 The passwd executable file is a setuid program so it needs to be well protected against various types of attacks. With this update, passwd has been built with the Position Independent Executables (PIE) flag, "-fPIE -pie", and the full read-only relocations (RELRO) flags, "-Wl,-z,relro,-z,now". The passwd binary is now well protected against "return-to-text" and memory corruption attacks and also against attacks based on the program's ELF section overwriting. All users of passwd are advised to upgrade to this updated package, which adds these enhancements.

Commands: