mtpti5iD/redhat-docs_dataset huggingface dataset:
8.17. compat-openmpi 8.17.1. RHBA-2013:1711 - compat-openmpi bug fix update Updated compat-openmpi packages that fix one bug are now available for Red Hat Enterprise Linux 6. The compat-openmpi packages contain shared libraries from earlier versions of Open Message Passing Interface (Open MPI). The libraries from releases have been compiled against the current version of Red Hat Enterprise Linux 6, and the packages enable earlier programs to keep functioning properly. Bug Fix BZ# 876315 The compat-openmpi packages previously did not ensure compatibility with earlier versions of the Open MPI shared libraries. Consequently, the users failed to run certain applications using Open MPI on Red Hat Enterprise Linux 6.3 and later if those applications were compiled against Open MPI versions used on Red Hat Enterprise Linux 6.2 and earlier. After this update, the compat-openmpi packages now maintain compatibility with earlier versions of Open MPI on Red Hat Enterprise Linux 6. Users of compat-openmpi are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 9. Supplementary Server Variant The following table lists all the packages in the Supplementary Server variant. For more information about support scope, see the Scope of Coverage Details document. Package Core Package? License acroread No Commercial acroread-plugin No Commercial chromium-browser No BSD and LGPLv2+ flash-plugin No Commercial java-1.5.0-ibm No IBM Binary Code License java-1.5.0-ibm-demo No IBM Binary Code License java-1.5.0-ibm-devel No IBM Binary Code License java-1.5.0-ibm-javacomm No IBM Binary Code License java-1.5.0-ibm-jdbc No IBM Binary Code License java-1.5.0-ibm-plugin No IBM Binary Code License java-1.5.0-ibm-src No IBM Binary Code License java-1.6.0-ibm No IBM Binary Code License java-1.6.0-ibm-demo No IBM Binary Code License java-1.6.0-ibm-devel No IBM Binary Code License java-1.6.0-ibm-javacomm No IBM Binary Code License java-1.6.0-ibm-jdbc No IBM Binary Code License java-1.6.0-ibm-plugin No IBM Binary Code License java-1.6.0-ibm-src No IBM Binary Code License java-1.7.1-ibm No IBM Binary Code License java-1.7.1-ibm-demo No IBM Binary Code License java-1.7.1-ibm-devel No IBM Binary Code License java-1.7.1-ibm-jdbc No IBM Binary Code License java-1.7.1-ibm-plugin No IBM Binary Code License java-1.7.1-ibm-src No IBM Binary Code License java-1.8.0-ibm No IBM Binary Code License java-1.8.0-ibm-demo No IBM Binary Code License java-1.8.0-ibm-devel No IBM Binary Code License java-1.8.0-ibm-jdbc No IBM Binary Code License java-1.8.0-ibm-plugin No IBM Binary Code License java-1.8.0-ibm-src No IBM Binary Code License kmod-kspiceusb-rhel60 No GPLv2 libdfp No LGPLv2.1 libdfp-devel No LGPLv2.1 spice-usb-share No Redistributable, no modification permitted system-switch-java No GPLv2+ virtio-win No Red Hat Proprietary and GPLv2

Commands:
probe::signal.do_action Name probe::signal.do_action - Examining or changing a signal action Synopsis Values sa_mask The new mask of the signal name Name of the probe point sig_name A string representation of the signal oldsigact_addr The address of the old sigaction struct associated with the signal sig The signal to be examined/changed sa_handler The new handler of the signal sigact_addr The address of the new sigaction struct associated with the signal

Commands:
signal.do_action
Appendix E. Cephx configuration options The following are Cephx configuration options that can be set up during deployment. auth_cluster_required Description If enabled, the Red Hat Ceph Storage cluster daemons, ceph-mon and ceph-osd , must authenticate with each other. Valid settings are cephx or none . Type String Required No Default cephx . auth_service_required Description If enabled, the Red Hat Ceph Storage cluster daemons require Ceph clients to authenticate with the Red Hat Ceph Storage cluster in order to access Ceph services. Valid settings are cephx or none . Type String Required No Default cephx . auth_client_required Description If enabled, the Ceph client requires the Red Hat Ceph Storage cluster to authenticate with the Ceph client. Valid settings are cephx or none . Type String Required No Default cephx . keyring Description The path to the keyring file. Type String Required No Default /etc/ceph/USDcluster.USDname.keyring,/etc/ceph/USDcluster.keyring,/etc/ceph/keyring,/etc/ceph/keyring.bin keyfile Description The path to a key file (that is. a file containing only the key). Type String Required No Default None key Description The key (that is, the text string of the key itself). Not recommended. Type String Required No Default None ceph-mon Location USDmon_data/keyring Capabilities mon 'allow *' ceph-osd Location USDosd_data/keyring Capabilities mon 'allow profile osd' osd 'allow *' radosgw Location USDrgw_data/keyring Capabilities mon 'allow rwx' osd 'allow rwx' cephx_require_signatures Description If set to true , Ceph requires signatures on all message traffic between the Ceph client and the Red Hat Ceph Storage cluster, and between daemons comprising the Red Hat Ceph Storage cluster. Type Boolean Required No Default false cephx_cluster_require_signatures Description If set to true , Ceph requires signatures on all message traffic between Ceph daemons comprising the Red Hat Ceph Storage cluster. Type Boolean Required No Default false cephx_service_require_signatures Description If set to true , Ceph requires signatures on all message traffic between Ceph clients and the Red Hat Ceph Storage cluster. Type Boolean Required No Default false cephx_sign_messages Description If the Ceph version supports message signing, Ceph will sign all messages so they cannot be spoofed. Type Boolean Default true auth_service_ticket_ttl Description When the Red Hat Ceph Storage cluster sends a Ceph client a ticket for authentication, the cluster assigns the ticket a time to live. Type Double Default 60*60

Commands:
9.5. Network Devices Red Hat Virtualization is able to expose three different types of network interface controller to guests. The type of network interface controller to expose to a guest is chosen when the guest is created but is changeable from the Red Hat Virtualization Manager. The e1000 network interface controller exposes a virtualized Intel PRO/1000 (e1000) to guests. The virtio network interface controller exposes a para-virtualized network device to guests. The rtl8139 network interface controller exposes a virtualized Realtek Semiconductor Corp RTL8139 to guests. Multiple network interface controllers are permitted per guest. Each controller added takes up an available PCI slot on the guest.

Commands:
B.38.12. RHBA-2011:1283 - kernel bug fix update Updated kernel packages that fix various bugs are now available for Red Hat Enterprise Linux 6. The kernel packages contain the Linux kernel, the core of any Linux operating system. Bug Fixes BZ# 731968 Prior to this update, a kernel panic could occur when the Intel 82599 Virtual Function driver was used from the guest. As a result, 10 gigabit Ethernet(10GbE) network interface cards (NICs) could not be used correctly. This update modifies the code so that 10GbE NICs can be used when they are operated from the guest. All users are advised to upgrade to these updated packages, which fix this bug. The system must be rebooted for this update to take effect.

Commands:
D.3. Selection-Based Action Menus Selecting specific objects in the Model Explorer provides a context from which the Teiid Designer presents a customized menu of available actions. Selecting a view model, for instance, results in a number of high level options to manage edit model content, perform various operations and provides quick access to other important actions available in Teiid Designer . These may include specialized actions based on model type. Figure D.5. Sample Context Menu

Commands:
5.9. Smart Card Authentication Smart cards are an external hardware security feature, most commonly seen in credit cards, but also used by many businesses as authentication tokens. Smart cards can be used to protect Red Hat Virtualization virtual machines. Enabling Smart Cards Ensure that the smart card hardware is plugged into the client machine and is installed according to manufacturer's directions. Click Compute Virtual Machines and select a virtual machine. Click Edit . Click the Console tab and select the Smartcard enabled check box. Click OK . Connect to the running virtual machine by clicking the Console button. Smart card authentication is now passed from the client hardware to the virtual machine. Important If the Smart card hardware is not correctly installed, enabling the Smart card feature will result in the virtual machine failing to load properly. Disabling Smart Cards Click Compute Virtual Machines and select a virtual machine. Click Edit . Click the Console tab, and clear the Smartcard enabled check box. Click OK . Configuring Client Systems for Smart Card Sharing Smart cards may require certain libraries in order to access their certificates. These libraries must be visible to the NSS library, which spice-gtk uses to provide the smart card to the guest. NSS expects the libraries to provide the PKCS #11 interface. Make sure that the module architecture matches the spice-gtk / remote-viewer architecture. For instance, if you have only the 32b PKCS #11 library available, you must install the 32b build of virt-viewer in order for smart cards to work. Configuring RHEL Clients for Smart Card support Red Hat Enterprise Linux provides support for Smart cards. Install the Smart card support group. If the Smart Card Support group is installed on a Red Hat Enterprise Linux system, smart cards are redirected to the guest when Smart Cards are enabled. To install the Smart card support group, run the following command: # dnf groupinstall "Smart card support" Configuring RHEL Clients with Other Smart Card Middleware Red Hat Enterprise Linux provides a system-wide registry of pkcs11 modules in the p11-kit , and these are accessible to all applications. To register the third party PKCS#11 library in the p11-kit database, run the following command as root: To verify the Smart card is visible for p11-kit through this library run the following command: Configuring Windows Clients Red Hat does not provide PKCS #11 support to Windows clients. Libraries that provide PKCS #11 support must be obtained from third parties. When such libraries are obtained, register them by running the following command as a user with elevated privileges: modutil -dbdir %PROGRAMDATA%\pki\nssdb -add " module name " -libfile C:_\Path\to\module_.dll

Commands:
dnf groupinstall "Smart card support"
echo "module: /path/to/library.so" > /etc/pkcs11/modules/my.module
p11-kit list-modules
modutil -dbdir %PROGRAMDATA%\pki\nssdb -add " module name " -libfile C:_\Path\to\module_.dll
7.233. spice-protocol 7.233.1. RHBA-2013:0510 - spice-protocol bug fix and enhancement update Updated spice-protocol packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The spice-protocol packages provide header files to describe the SPICE protocol and the QXL para-virtualized graphics card. The SPICE protocol is needed to build newer versions of the spice-client and the spice-server packages. Note The spice-protocol package has been upgraded to upstream version 0.12.2, which provides a number of enhancements over the version, including support for USB redirection. (BZ# 842352 ) Enhancement BZ# 846910 This update adds support for seamless migration to the spice-protocol packages. All users who build spice packages are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
25.5.2. Creating a New Directory for rsyslog Log Files Rsyslog runs as the syslogd daemon and is managed by SELinux. Therefore all files to which rsyslog is required to write to, must have the appropriate SELinux file context. Procedure 25.4. Creating a New Working Directory If required to use a different directory to store working files, create a directory as follows: Install utilities to manage SELinux policy: Set the SELinux directory context type to be the same as the /var/lib/rsyslog/ directory: Apply the SELinux context: If required, check the SELinux context as follows: Create subdirectories as required. For example: The subdirectories will be created with the same SELinux context as the parent directory. Add the following line in /etc/rsyslog.conf immediately before it is required to take effect: This setting will remain in effect until the WorkDirectory directive is encountered while parsing the configuration files.

Commands:
~]# mkdir /rsyslog
~]# yum install policycoreutils-python
~]# semanage fcontext -a -t syslogd_var_lib_t /rsyslog
~]# restorecon -R -v /rsyslog restorecon reset /rsyslog context unconfined_u:object_r:default_t:s0->unconfined_u:object_r:syslogd_var_lib_t:s0
~]# ls -Zd /rsyslog drwxr-xr-x. root root system_u:object_r:syslogd_var_lib_t:s0 /rsyslog
~]# mkdir /rsyslog/work
USDWorkDirectory /rsyslog/work
11.3. Understanding the Predictable Network Interface Device Names The names have two-character prefixes based on the type of interface: en for Ethernet, wl for wireless LAN (WLAN), ww for wireless wide area network (WWAN). The names have the following types: o< index > on-board device index number s< slot> [f< function> ][d< dev_id >] hotplug slot index number. All multi-function PCI devices will carry the [f< function >] number in the device name, including the function 0 device. x< MAC > MAC address [P< domain >]p< bus >s< slot >[f< function >][d< dev_id >] PCI geographical location. In PCI geographical location, the [P< domain >] number is only mentioned if the value is not 0 . For example: ID_NET_NAME_PATH=P1enp5s0 [P< domain >]p< bus >s< slot >[f< function >][u< port >][..][c< config >][i< interface >] USB port number chain. For USB devices, the full chain of port numbers of hubs is composed. If the name gets longer than the maximum number of 15 characters, the name is not exported. If there are multiple USB devices in the chain, the default values for USB configuration descriptors (c1) and USB interface descriptors (i0) are suppressed.

Commands:
Chapter 65. Virtualization Booting OVMF guests fails Attempting to boot a guest virtual machine that uses the Open Virtual Machine Firmware (OVMF) on a Red Hat Enterprise Linux host using the qemu-kvm package currently fails, with the guest becoming unresponsive and displaying a blank screen. (BZ#1174132) Bridge creation with virsh iface-bridge fails When installing Red Hat Enterprise Linux 7 from other sources than the network, network device names are not specified by default in the interface configuration files (this is done with a DEVICE= line). As a consequence, creating a network bridge by using the virsh iface-bridge command fails with an error message. To work around the problem, add DEVICE= lines into the /etc/sysconfig/network-scripts/ifcfg-* files. For more information, see the Red Hat Knowledgebase: https://access.redhat.com/solutions/2792701 (BZ#1100588) Guests sometimes fail to boot on ESXi 5.5 When running Red Hat Enterprise Linux 7 guests with 12 GB RAM or above on a VMware ESXi 5.5 hypervisor, certain components currently initialize with incorrect memory type range register (MTRR) values or incorrectly reconfigure MTRR values across boots. This sometimes causes the guest kernel to panic or the guest to become unresponsive during boot. To work around this problem, add the disable_mtrr_trim option to the guest's kernel command line, which enables the guest to continue booting when MTRRs are configured incorrectly. Note that with this option, the guest prints WARNING: BIOS bug messages during boot, which you can safely ignore. (BZ#1429792) The STIG for Red Hat Virtualization Hypervisor profile is not displayed in Anaconda The oscap-anaconda-addon module is currently not able to properly parse the STIG for Red Hat Virtualization Hypervisor security hardening profile. As a consequence, the profile's name is shown as DISA STIG for Red Hat Enterprise Linux 7 or United States Government Configuration Baseline (USGCB / STIG) - DRAFT in the Anaconda interface selection. However, this is only a display problem, and you can safely use the DISA STIG for Red Hat Enterprise Linux 7 profile instead of the STIG for Red Hat Virtualization Hypervisor profile. (BZ# 1437106 )

Commands:
4.7.3. Related Books The following books discuss various issues related to resource monitoring, and are good resources for Red Hat Enterprise Linux system administrators: The System Administrators Guide ; Red Hat, Inc -- Includes a chapter on many of the resource monitoring tools described here. Linux Performance Tuning and Capacity Planning by Jason R. Fink and Matthew D. Sherer; Sams -- Provides more in-depth overviews of the resource monitoring tools presented here and includes others that might be appropriate for more specific resource monitoring needs. Red Hat Linux Security and Optimization by Mohammed J. Kabir; Red Hat Press -- Approximately the first 150 pages of this book discuss performance-related issues. This includes chapters dedicated to performance issues specific to network, Web, email, and file servers. Linux Administration Handbook by Evi Nemeth, Garth Snyder, and Trent R. Hein; Prentice Hall -- Provides a short chapter similar in scope to this book, but includes an interesting section on diagnosing a system that has suddenly slowed down. Linux System Administration: A User's Guide by Marcel Gagne; Addison Wesley Professional -- Contains a small chapter on performance monitoring and tuning. Essential System Administration (3rd Edition) by Aeleen Frisch; O'Reilly &Associates -- The chapter on managing system resources contains good overall information, with some Linux specifics included. System Performance Tuning (2nd Edition) by Gian-Paolo D. Musumeci and Mike Loukides; O'Reilly &Associates -- Although heavily oriented toward more traditional UNIX implementations, there are many Linux-specific references throughout the book.

Commands:
9.2. Setting a Minimum Strength Factor For additional security, the Directory Server can be configured to require a certain level of encryption before it allows a connection. The Directory Server can define and require a specific Security Strength Factor (SFF) for any connection. The SSF sets a minimum encryption level, defined by its key strength, for any connection or operation. To require a minimum SSF for any and all directory operations, set the nsslapd-minssf configuration attribute. When enforcing a minimum SSF, Directory Server looks at each available encryption type for an operation - TLS or SASL - and determines which has the higher SSF value and then compares the higher value to the minimum SSF. It is possible for both SASL authentication and TLS to be configured for some server-to-server connections, such as replication. Note Alternatively, use the nsslapd-minssf-exclude-rootdse configuration attribute. This sets a minimum SSF setting for all connections to the Directory Server except for queries against the root DSE. A client may need to obtain information about the server configuration, like its default naming context, before initiating an operation. The nsslapd-minssf-exclude-rootdse attribute allows the client to get that information without having to establish a secure connection first. The SSF for a connection is evaluated when the first operation is initiated on a connection. This allows STARTTLS and SASL binds to succeed, even though those two connections initially open a regular connection. After the TLS or SASL session is opened, then the SSF is evaluated. Any connection which does not meet the SSF requirements is closed with an LDAP unwilling to perform error. Set a minimum SSF to disable insecure connections to a directory. Warning If you connect to the directory using the unencrypted LDAP protocol without SASL, the first LDAP message can contain the bind request. In this case, the credentials are sent unencrypted over the network before the server cancels the connection, because the SSF did not met the minimum value set. Use the LDAPS protocol or SASL binds to ensure that the credentials are never sent unencrypted. The default nsslapd-minssf attribute value is 0, which means there is no minimum SSF for server connections. The value can be set to any reasonable positive integer. The value represents the required key strength for any secure connection. The following example sets the nsslapd-minssf parameter to 128 : Note An ACI can be set to require an SSF for a specific type of operation, as in Section 18.11.2.4, "Requiring a Certain Level of Security in Connections" . Secure connections can be required for bind operations by turning on the nsslapd-require-secure-binds attribute, as in Section 20.12.1, "Requiring Secure Binds" .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-minssf=128 Successfully replaced "nsslapd-minssf"
D.2. Enabling FIPS in RHV hosts and the standalone Manager You can enable FIPS mode when installing a Red Hat Enterprise Linux (RHEL) host or Red Hat Virtualization Host (RHVH). For details, see Installing a RHEL 8 system with FIPS mode enabled in the guide Security hardening for Red Hat Enterprise Linux 8. Red Hat does not support switching a provisioned host or Manager machine to FIPS mode Verification Verify that FIPS is enabled by entering the command fips-mode-setup --check on the host. The command should return FIPS mode is enabled : # fips-mode-setup --check FIPS mode is enabled.

Commands:
fips-mode-setup --check FIPS mode is enabled.
2. Clients The Customer Portal API is, by nature, client-agnostic. It is expressed as a set of resource URLs which send and receive XML data. Some common clients and platforms include, but are not limited to, the following: Client Platform/Environment Comments cURL [a] Command Line (Linux, UNIX, Mac OS X, Microsoft Windows) Easy and transparent way to test commands and do simple integration Apache HTTP Client [b] Java Most common Java library with which to talk HTTP; offers little semantic value beyond simple HTTP; no intrinsic binding of XML RESTeasy Client [c] Java Full Java model integration; no need to think about HTTP or XML; uses Apache HTTP Client underneath [a] http://curl.haxx.se/ [b] http://hc.apache.org/httpclient-3.x/ [c] http://docs.jboss.org/resteasy/docs/2.0.0.GA/userguide/html/RESTEasy_Client_Framework.html

Commands:
18.2.5. Saving the Settings Click OK to save the changes and enable or disable the firewall. If Enable firewall was selected, the options selected are translated to iptables commands and written to the /etc/sysconfig/iptables file. The iptables service is also started so that the firewall is activated immediately after saving the selected options. If Disable firewall was selected, the /etc/sysconfig/iptables file is removed and the iptables service is stopped immediately. The selected options are also written to the /etc/sysconfig/system-config-selinux file so that the settings can be restored the time the application is started. Do not edit this file by hand. Even though the firewall is activated immediately, the iptables service is not configured to start automatically at boot time. Refer to Section 18.2.6, "Activating the IPTables Service" for more information.

Commands: