mtpti5iD/redhat-docs_dataset huggingface dataset:
8.123. libtirpc 8.123.1. RHBA-2014:1419 - libtirpc bug fix update Updated libtirpc packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The libtirpc packages contain SunLib's implementation of transport independent RPC (TI-RPC) documentation. This includes a library required by programs in the nfs-utils and rpcbind packages. Bug Fixes BZ# 1082807 Previously, the libtirpc library included the authgss_get_private_data() system call, but not the authgss_free_private_data() system call. As a consequence, private data were obtained but not freed afterwards. This caused the authgss_destroy_context() call to send an incorrect RPCSEC_GSS_DESTROY request, and the client was in turn not able to clear the state data on the server. With this update, authgss_free_private_data() has been added to libtirpc, and the data is now freed correctly. As a result, the client can now reset the server state as expected. BZ# 1031498 Prior to this update, due to race conditions, using TI-RPC in the glibc library caused TI-RPC to terminate unexpectedly with a segmentation fault on some file operations, such as fclose() call and the endnetconfig() call. This update prevents the race conditions from occurring in the above scenario, and TI-RPC thus no longer crashes when used in glibc. BZ# 1056809 Due to buffer overruns in libtrpc, the rpcbind utility sometimes terminated unexpectedly with a segmentation fault. With this update, buffer is allocated by the svcauth_gss_validate() call, which avoids the buffer overruns and thus prevents the rpcbind crashes. BZ# 869397 Previously, the libtirpc-devel RPM incorrectly installed the /lib64/libtirpc.a and /lib64/libtirpc.la static libraries, which caused compiling software that linked libtirpc to fail. This update removes libtirpc.a and libtirpc.la and compiling with libtirpc.so now works as expected. BZ# 982064 Due to a code error in libtirpc, the automount utility sometimes terminated unexpectedly with a segmentation fault when a RPC was rejected with an invalid rejection status. This update fixes this bug and automount no longer crashes when receiving an invalid server rejection. Users of libtirpc are advised to upgrade to these updated packages, which fix these bugs.

Commands:
14.7.11. Listing Devices on a Node The virsh nodedev-list cap --tree command lists all the devices available on the node that are known by libvirt . cap is used to filter the list by capability types, each separated by a comma and cannot be used with --tree . Using the --tree option, puts the output into a tree structure as shown:

Commands:
virsh nodedev-list --tree computer | +- net_lo_00_00_00_00_00_00 +- net_macvtap0_52_54_00_12_fe_50 +- net_tun0 +- net_virbr0_nic_52_54_00_03_7d_cb +- pci_0000_00_00_0 +- pci_0000_00_02_0 +- pci_0000_00_16_0 +- pci_0000_00_19_0 | | | +- net_eth0_f0_de_f1_3a_35_4f (this is a partial screen)
Chapter 23. MAC Address Pools 23.1. MAC Address Pool Elements The macpools collection provides information about the MAC address pools in a Red Hat Virtualization environment. An API user accesses this information through the rel="macpools" link obtained from the entry point URI. The following table shows specific elements contained in a MAC address pool resource representation. Table 23.1. MAC address pool elements Element Type Description Properties name string A plain text, human-readable name for the MAC address pool. description string A plain text, human-readable description of the MAC address pool. allow_duplicates Boolean: true or false Defines whether duplicate MAC addresses are permitted in the pool. If not specified, allow_duplicates defaults to false. default_pool Boolean: true or false Defines whether this is the default pool. If not specified, default_pool defaults to false. ranges complex Defines the range of MAC addresses for the pool. Multiple ranges can be defined within the ranges element.

Commands:
Chapter 11. Supported and Unsupported features for IBM Power and IBM Z Table 11.1. List of supported and unsupported features on IBM Power and IBM Z Features IBM Power IBM Z Compact deployment Unsupported Unsupported Dynamic storage devices Unsupported Supported Stretched Cluster - Arbiter Supported Unsupported Federal Information Processing Standard Publication (FIPS) Unsupported Unsupported Ability to view pool compression metrics Supported Unsupported Automated scaling of Multicloud Object Gateway (MCG) endpoint pods Supported Unsupported Alerts to control overprovision Supported Unsupported Alerts when Ceph Monitor runs out of space Supported Unsupported Extended OpenShift Data Foundation control plane which allows pluggable external storage such as IBM Flashsystem Unsupported Unsupported IPV6 support Unsupported Unsupported Multus Unsupported Unsupported Multicloud Object Gateway (MCG) bucket replication Supported Unsupported Quota support for object data Supported Unsupported Minimum deployment Unsupported Unsupported Regional-Disaster Recovery (Regional-DR) with Red Hat Advanced Cluster Management (RHACM) Supported Unsupported Metro-Disaster Recovery (Metro-DR) multiple clusters with RHACM Supported Supported Single Node solution for Radio Access Network (RAN) Unsupported Unsupported Support for network file system (NFS) services Supported Unsupported Ability to change Multicloud Object Gateway (MCG) account credentials Supported Unsupported Multicluster monitoring in Red Hat Advanced Cluster Management console Supported Unsupported Deletion of expired objects in Multicloud Object Gateway lifecycle Supported Unsupported Agnostic deployment of OpenShift Data Foundation on any Openshift supported platform Unsupported Unsupported Installer provisioned deployment of OpenShift Data Foundation using bare metal infrastructure Unsupported Unsupported Openshift dual stack with OpenShift Data Foundation using IPv4 Unsupported Unsupported Ability to disable Multicloud Object Gateway external service during deployment Unsupported Unsupported Ability to allow overriding of default NooBaa backing store Supported Unsupported Allowing ocs-operator to deploy two MGR pods, one active and one standby Unsupported Unsupported

Commands:
Chapter 37. Upgrading Your Current System The procedure for performing an in-place upgrade on your current system is handled by the following utilities: The Preupgrade Assistant , which is a diagnostics utility that assesses your current system and identifies potential problems you might encounter during and/or after the upgrade. The Red Hat Upgrade Tool utility, which is used to upgrade a system from Red Hat Enterprise Linux to version 7. The current documentation for testing this procedure can be found in the following Red Hat Knowledgebase article: https://access.redhat.com/site/solutions/637583

Commands:
7.211. sysvinit 7.211.1. RHBA-2015:1362 - sysvinit bug fix update Updated sysvinit packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The sysvinit packages contain programs that control basic system processes. SysVinit includes the init program, which is the first program started by the Linux kernel when the system boots. The init daemon process is the parent of all processes and continues running until the system is shut down. The sysvinit packages also contain many commonly used utilities, such as reboot, shutdown, poweroff, and sulogin. Bug Fixes BZ# 760251 If a running binary is replaced, its executable symbolic link in the /proc file system is appended with "(deleted)". Previously, the pidof utility could not handle the suffix. As a consequence, pidof falsely reported that there was no running binary with the original path. With this update, the "(deleted)" suffix is removed when parsing /proc, and pidof works correctly in the described situation. BZ# 883857 Usually, init scripts have the same name as the respective daemons and when the init script looks for the name of the daemon, the PID of the init script that starts the search needs to be excluded. Previously, the pidofproc() function could falsely identify certain processes started by an init script as the daemon of the same name, as the init script could, for example, be running twice. Consequently, pidofproc() failed to return the correct PID of the daemon. With this update, a new "-m" option is available for the pidof utility. The new "-m" option makes it possible to omit any processes that are similar to those explicitly ignored. Users of sysvinit are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 8. Using Hardware Security Modules for Subsystem Security Databases A subsystem instance generates and stores its key information in a key store, called a security module or a token . A subsystem instance can be configured for the keys to be generated and stored using the internal NSS token or on a separate cryptographic device, a hardware token. 8.1. Installing Certificate System with an HSM Use the following parameters in the configuration file you pass to the pkispawn utility when installing Certificate System with an HSM:

Commands:
######################### Provide HSM parameters # ########################## pki_hsm_enable=True pki_hsm_libfile= hsm_libfile pki_hsm_modulename= hsm_modulename pki_token_name= hsm_token_name pki_token_password= pki_token_password ######################################## Provide PKI-specific HSM token names # ######################################## pki_audit_signing_token= hsm_token_name pki_ssl_server_token= hsm_token_name pki_subsystem_token= hsm_token_name
Chapter 1. Kafka tuning overview Use configuration properties to optimize the performance of Kafka brokers, producers and consumers. You can specify configuration properties for AMQ Streams on OCP and RHEL. A minimum set of configuration properties is required, but you can add or adjust properties to change how producers and consumers interact with Kafka brokers. For example, you can tune latency and throughput of messages so that clients can respond to data in real time. You might start by analyzing metrics to gauge where to make your initial configurations, then make incremental changes and further comparisons of metrics until you have the configuration you need. For more information about Apache Kafka configuration properties, see the Apache Kafka documentation . 1.1. Mapping properties and values How you specify configuration properties depends on the type of deployment. If you deployed AMQ Streams on OCP, you can use the Kafka resource to add configuration for Kafka brokers through the config property. With AMQ Streams on RHEL, you add the configuration to a properties file as environment variables. When you add config properties to custom resources, you use a colon (':') to map the property and value. Example configuration in a custom resource num.partitions:1 When you add the properties as environment variables, you use an equal sign ('=') to map the property and value. Example configuration as an environment variable num.partitions=1 1.2. Tools that help with tuning The following tools help with Kafka tuning: Cruise Control generates optimization proposals that you can use to assess and implement a cluster rebalance Kafka Static Quota plugin sets limits on brokers Rack configuration spreads broker partitions across racks and allows consumers to fetch data from the nearest replica For more information on these tools, see the following guides: Configuring AMQ Streams on OpenShift Using AMQ Streams on RHEL

Commands:
num.partitions:1
num.partitions=1
7.128. microcode_ctl 7.128.1. RHEA-2015:1291 - microcode_ctl enhancement update Updated microcode_ctl packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The microcode_ctl packages provide microcode updates for Intel and AMD processors. Enhancement BZ# 1123992 An updated CPU Microcode data file is now available to be used by the Linux kernel to correct behavior in Intel processors on boot. Users of microcode_ctl are advised to upgrade to these updated packages, which add this enhancement. Note: a system reboot is necessary for this update to take effect.

Commands:
16.2.3. Keeping Quotas Accurate When a file system fails to unmount cleanly (due to a system crash, for example), it is necessary to run quotacheck . However, quotacheck can be run on a regular basis, even if the system has not crashed. Safe methods for periodically running quotacheck include: Ensuring quotacheck runs on reboot Note This method works best for (busy) multiuser systems which are periodically rebooted. As root, place a shell script into the /etc/cron.daily/ or /etc/cron.weekly/ directory-or schedule one using the crontab -e command-that contains the touch /forcequotacheck command. This creates an empty forcequotacheck file in the root directory, which the system init script looks for at boot time. If it is found, the init script runs quotacheck . Afterward, the init script removes the /forcequotacheck file; thus, scheduling this file to be created periodically with cron ensures that quotacheck is run during the reboot. For more information about cron , refer to man cron . Running quotacheck in single user mode An alternative way to safely run quotacheck is to boot the system into single-user mode to prevent the possibility of data corruption in quota files and run the following commands: Running quotacheck on a running system If necessary, it is possible to run quotacheck on a machine during a time when no users are logged in, and thus have no open files on the file system being checked. Run the command quotacheck -vaug file_system ; this command will fail if quotacheck cannot remount the given file_system as read-only. Note that, following the check, the file system will be remounted read-write. Warning Running quotacheck on a live file system mounted read-write is not recommended due to the possibility of quota file corruption. Refer to man cron for more information about configuring cron .

Commands:
quotaoff -vaug / file_system
quotacheck -vaug / file_system
quotaon -vaug / file_system
Chapter 14. Configuring NetworkManager to ignore certain devices By default, NetworkManager manages all devices except the ones described in the /usr/lib/udev/rules.d/85-nm-unmanaged.rules file. To ignore certain other devices, you can configure them in NetworkManager as unmanaged . 14.1. Permanently configuring a device as unmanaged in NetworkManager You can permanently configure devices as unmanaged based on several criteria, such as the interface name, MAC address, or device type. Procedure Optional: Display the list of devices to identify the device or MAC address you want to set as unmanaged : Create the /etc/NetworkManager/conf.d/99-unmanaged-devices.conf file with the following content: To configure a specific interface as unmanaged, add: To configure a device with a specific MAC address as unmanaged, add: To configure all devices of a specific type as unmanaged, add: To set multiple devices as unmanaged, separate the entries in the unmanaged-devices parameter with a semicolon, for example: Reload the NetworkManager service: Verification Display the list of devices: The unmanaged state to the enp1s0 device indicates that NetworkManager does not manage this device. Troubleshooting If the device is not shown as unmanaged , display the NetworkManager configuration: If the output does not match the settings that you configured, ensure that no configuration file with a higher priority overrides your settings. For details about how NetworkManager merges multiple configuration files, see the NetworkManager.conf(5) man page on your system. 14.2. Temporarily configuring a device as unmanaged in NetworkManager You can temporarily configure devices as unmanaged , for example, for testing purposes. Procedure Optional: Display the list of devices to identify the device you want to set as unmanaged : Set the enp1s0 device to the unmanaged state: Verification Display the list of devices: The unmanaged state to the enp1s0 device indicates that NetworkManager does not manage this device. Additional resources NetworkManager.conf(5) man page on your system

Commands:
ip link show 2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000 link/ether 52:54:00:74:79:56 brd ff:ff:ff:ff:ff:ff
[keyfile] unmanaged-devices=interface-name:enp1s0
[keyfile] unmanaged-devices=mac:52:54:00:74:79:56
[keyfile] unmanaged-devices=type:ethernet
[keyfile] unmanaged-devices=interface-name:enp1s0;interface-name:enp7s0
systemctl reload NetworkManager
nmcli device status DEVICE TYPE STATE CONNECTION enp1s0 ethernet unmanaged --
NetworkManager --print-config [keyfile] unmanaged-devices=interface-name:enp1s0
nmcli device status DEVICE TYPE STATE CONNECTION enp1s0 ethernet disconnected --
nmcli device set enp1s0 managed no
nmcli device status DEVICE TYPE STATE CONNECTION enp1s0 ethernet unmanaged --
8.75. ipvsadm 8.75.1. RHBA-2013:1639 - ipvsadm bug fix and enhancement update Updated ipvsadm packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The ipvsadm package provides the ipsvadm tool to administer the IP Virtual Server services offered by the Linux kernel. Note The ipvsadm packages have been upgraded to upstream version 1.26, which provides new features to IPVS from the kernel side, which take full-advantage of PE config of SIP PE-data. In addition, this update: * fixes the "One Packet Scheduler" output for the status and save operations to include all Virtual Servers instead of only those configured with a persistent flag (BZ# 986189 ) * addresses a possible, but very unlikely, memory corruption issues; * includes minor improvements to the manual pages related to ipvsadm. Users of ipvsadm are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
3.18. Searching for Users The following table describes all search options for users. Table 3.14. Searching for Users Property (of resource or resource-type) Type Description (Reference) Vms. Vms-prop Depends on property type The property of the virtual machines associated with the user. Hosts. hosts-prop Depends on property type The property of the hosts associated with the user. Templates. templates-prop Depends on property type The property of the templates associated with the user. Events. events-prop Depends on property type The property of the events associated with the user. name String The name of the user. lastname String The last name of the user. usrname String The unique name of the user. department String The department to which the user belongs. group String The group to which the user belongs. title String The title of the user. status String The status of the user. role String The role of the user. tag String The tag to which the user belongs. pool String The pool to which the user belongs. sortby List Sorts the returned results by one of the resource properties. page Integer The page number of results to display. Example Users: Events.severity > normal and Vms.status = up or Vms.status = pause This example returns a list of users where events of greater than normal severity have occurred on their virtual machines AND the virtual machines are still running; or the users' virtual machines are paused.

Commands:
Chapter 12. Installation and Booting GRUB does not support NVMe devices Non-volatile memory NVM Express (NVMe) devices are not supported by the GRUB boot loader in Red Hat Enterprise Linux 6, and therefore the boot loader can't be installed on these devices. To work around the problem, you can: Use another storage device to install the boot loader Upgrade to RHEL 7, which uses GRUB2 as the default boot loader and supports installation to NVMe devices (BZ# 1227194 ) GRUB updates are not applied to the system When the GRUB boot loader is updated using yum or rpm (for example, rpm -Uvh grub ), and the update process succeeds, then the grub-install command is not being run automatically due to technical limitations of GRUB . The updated package is downloaded and installed, but the new version of the boot loader provided by that package is not automatically applied to the system. Instead, the old version is used even after the package update, and therefore any fixes provided in the update are not applied to the system. To work around this problem, run the grub-install command manually using a command line with root privileges every time an update to the grub package is installed. (BZ# 1573121 ) GRUB Legacy does not support SHA-encrypted passwords In UEFI mode, GRUB Legacy supports only MD5-encrypted passwords and does not support SHA256 and SHA512-encrypted passwords. Consequently, the operating system becomes unresponsive at boot time, when using SHA256 and SHA512-encrypted passwords in UEFI mode. To work around this problem, you can: Configure your system to boot in Legacy BIOS mode. For more information, see https://access.redhat.com/solutions/68828 . Upgrade to Red Hat Enterprise Linux 7, which uses the GRUB 2 boot loader that supports SHA-encrypted passwords. (BZ#1598553)

Commands:
D.18. Model Extension Definition Registry View (MED Registry View) To open Teiid Designer's MED Registry View , click the main menu's Window > Show View > Other... and then click the Teiid Designer > Model Extension Registry view in the dialog. The Model Extension Registry view shows the currently registered MEDs. Registered MEDs can be applied to models in the workspace (see Managing Model Object Extensions). The Model Extension Registry view looks like this: Figure D.30. System Catalog View You can also open the view by clicking the MED Editor toolbar action in the right corner of shared sub-editor header section. For each registered MED, the namespace prefix, namespace URI, extended model class, version, and description is shown. In addition, a flag indicating if the MED is built-in is shown. The Model Extension Registry view has toolbar actions that register a workspace MED file, unregister a user defined MED, and copy a registered MED to the workspace. All these actions are also available via a context menu. A MED registry keeps track of all the MEDs that are registered in a workspace. Only registered MEDs can be used to extend a model. There are 2 different types of MEDs stored in the registry: Built-In MED - these are registered during Teiid Designer installation. These MEDs cannot be updated or unregistered by the user. User-Defined MED - these are created by the user. These MEDs can be updated, registered, and unregistered by the user. Note When a workspace MED is registered it can be deleted from the workspace if desired. The registry keeps its own copy. And a registered MED can always be copied back to the workspace by using the appropriate toolbar or context menu action.

Commands:
5.262. python-rtslib 5.262.1. RHBA-2012:0855 - python-rtslib bug fix update Updated python-rtslib packages that fix one bug are now available for Red Hat Enterprise Linux 6. The python-rtslib packages provide a Python library to configure the kernel target subsystem with the configfs file system. Bug Fix BZ# 813676 Prior to this update, configurations were not saved when the targetcli tool exited. This update improves the mechanism for saving and restoring target configuration across system restarts. All users of python-rtslib are advised to upgrade to these updated packages, which fix this bug.

Commands: