mtpti5iD/redhat-docs_dataset huggingface dataset:
7.129. mlocate 7.129.1. RHBA-2015:0676 - mlocate bug fix update Updated mlocate packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The mlocate packages provide a locate/updatedb implementation, and keep a database of all existing files. The database allows files to be looked up by names. Bug Fixes BZ# 1012534 Prior to this update, the cron script which is included in the mlocate packages had permissions which were too loose. Consequently, mlocate did not comply with the Operating System Security Requirements Guide. This update changes the permissions of the cron script to 0700, as required by the guide. BZ# 1023779 The updatedb utility automatically excludes file systems which are marked as "nodev" in the /proc/filesystems file. The ZFS file system is also marked this way despite the fact it actually stores data on a physical device. As a consequence, ZFS volumes were not previously indexed. This update adds an exception for ZFS, which allows updatedb to index files stored on this file system and the locate utility to find such files. BZ# 1182304 Previously, the /var/lib/mlocate/mlocate.db database file was declared in the mlocate package metadata as belonging to the "root" user and group, and having the "644" permissions. However, in reality, the file belonged to the "slocate" group and had the "640" permissions. This discrepancy caused problems reported by OpenSCAP compliance checking tools. With this update, the database file is declared correctly in the metadata, which allows the package in an unaltered state to pass OpenSCAP compliance checks. BZ# 1168301 The updatedb utility did not exclude GPFS cluster file systems, which can hold billions of files. As a consequence, updatedb caused very high I/O load on systems using GPFS. With this update, GPFS volumes are skipped by updatedb. As a result, files stored on this file system are no longer indexed, and running updatedb on systems with GPFS volumes does not cause too high I/O load. Users of mlocate are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.60. flex 8.60.1. RHBA-2014:1402 - flex bug fix update Updated flex packages that fix one bug are now available for Red Hat Enterprise Linux 6. The flex packages provide a utility for generating scanners. The scanners are programs that can recognize lexical patterns in text. Bug Fix BZ# 570661 Previously, the flex static libraries for 32-bit and 64-bit architectures were included in the same package. Consequently, an attempt to compile an i386 code on an x86_64 system failed unless the 64-bit version of the flex utility had been removed. With this update, the libraries have been moved to separate packages, and flex works as expected in the described scenario. Users of flex are advised to upgrade to these updated packages, which fix this bug.

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

Commands:
4.3.4. Scripting the v2v process The entire v2v process can be scripted, enabling the automated batch processing of a large number of virtual machines. The process is broken up into two steps, which must be run on separate hosts. Procedure 4.8. Scripting the v2v process Use virt-v2v to convert the virtual machines and copy them to the export storage domain. This step must be run on a Linux host. The process is detailed in Section 4.3.2, "Converting a virtual machine" . Once the conversion is complete, use the Red Hat Enterprise Virtualization Administration Portal to import the virtual machines from the export storage domain. This step must be run on the Red Hat Enterprise Virtualization Manager server. For more information on importing a virtual machine with the Red Hat Enterprise Virtualization Administration Portal, see the Red Hat Enterprise Virtualization Administration Guide . Figure 4.4. Importing a virtual machine with the Red Hat Enterprise Virtualization Administration Portal Alternatively, the Python SDK or the command line can also be used to import the virtual machines from the export storage domain: To import the virtual machines using the SDK, use the following: Example 4.3. Importing virtual machines from the export storage domain using the SDK Note When using the SDK method, entities can also be fetched and passed using name= . To import the virtual machines using the command line, connect to the Red Hat Enterprise Virtualization Manager shell and use the following command: Example 4.4. Importing virtual machines from the export storage domain using the command line Note When using the command line method, entities can also be fetched and passed using -name .

Commands:
api = API(url="http(s)://...:.../api", username="...", password="...", filter=False, debug=True) sd = api.storagedomains.get(id="from-sd-id") import_candidate = sd.vms.get(id="vm-to-import") import_candidate.import_vm(action=params.Action( cluster=api.clusters.get(id="to-cluster-id"), storage_domain=api.storagedomains.get(id="to-sd-id")))
action vm "vm-to-import" import_vm --storagedomain-identifier "from-sd-id" --cluster-id "to-cluster-id" --storage_domain-id "to-sd-id"
24.5. Setting Up a Host Logging Server Hosts generate and update log files, recording their actions and problems. Collecting these log files centrally simplifies debugging. This procedure should be used on your centralized log server. You could use a separate logging server, or use this procedure to enable host logging on the Red Hat Virtualization Manager. Setting up a Host Logging Server Check to see if the firewall allows traffic on the UDP 514 port, and is open to syslog service traffic: If the output is no , allow traffic on the UDP 514 port with: Create a new .conf file on the syslog server, for example, /etc/rsyslog.d/from_remote.conf , and add the following lines: Restart the rsyslog service: Log in to the hypervisor, and in the /etc/rsyslog.conf add the following line: Restart the rsyslog service on the hypervisor. Your centralized log server is now configured to receive and store the messages and secure logs from your virtualization hosts.

Commands:
firewall-cmd --query-service=syslog
firewall-cmd --add-service=syslog --permanent firewall-cmd --reload
template(name="DynFile" type="string" string="/var/log/%HOSTNAME%/%PROGRAMNAME%.log") RuleSet(name="RemoteMachine"){ action(type="omfile" dynaFile="DynFile") } Module(load="imudp") Input(type="imudp" port="514" ruleset="RemoteMachine")
systemctl restart rsyslog.service
*.info;mail.none;authpriv.none;cron.none @<syslog-FQDN>:514
systemctl restart rsyslog.service
B.78. qemu-kvm B.78.1. RHSA-2011:0345 - Moderate: qemu-kvm security update Updated qemu-kvm packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. KVM (Kernel-based Virtual Machine) is a full virtualization solution for Linux on AMD64 and Intel 64 systems. qemu-kvm is the user-space component for running virtual machines using KVM. Virtual Network Computing (VNC) is a remote display system. CVE-2011-0011 A flaw was found in the way the VNC "password" option was handled. Clearing a password disabled VNC authentication, allowing a remote user able to connect to the virtual machines' VNC ports to open a VNC session without authentication. All users of qemu-kvm should upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing this update, shut down all running virtual machines. Once all virtual machines have shut down, start them again for this update to take effect.

Commands:
Chapter 31. JmxPrometheusExporterMetrics schema reference Used in: CruiseControlSpec , KafkaClusterSpec , KafkaConnectSpec , KafkaMirrorMaker2Spec , KafkaMirrorMakerSpec , ZookeeperClusterSpec The type property is a discriminator that distinguishes use of the JmxPrometheusExporterMetrics type from other subtypes which may be added in the future. It must have the value jmxPrometheusExporter for the type JmxPrometheusExporterMetrics . Property Property type Description type string Must be jmxPrometheusExporter . valueFrom ExternalConfigurationReference ConfigMap entry where the Prometheus JMX Exporter configuration is stored.

Commands:
Chapter 4. Adding packages during image creation by using Insights image builder You can customize your images during the creation process by adding additional packages from the BaseOS and AppStream RHEL repositories, through the UI. With that, you do not need to install the desired packages on first boot, which can be error-prone. 4.1. Adding additional packages during the image creation When creating a customized image using Insights image builder, you can add additional packages from the BaseOS and AppStream repositories. For that, follow the steps: Prerequisites You have an account on Red Hat Customer Portal with an Insights subscription. Access to the Insights image builder dashboard. You have already completed the following steps: Image output Target cloud environment Optionally, Registration Procedure On the Packages page: Type the name of the package you want to add to your image in the Available packages search bar. Optionally, you can enter the first two letters of the package name to see the available package options. The packages are listed on the Available packages dual list box. Click the package or packages you want to add. Click the >> button to add all packages shown in the package search results to the Chosen packages dual list box. Optionally, you can click the > button to add only the selected packages. After you have finished adding the additional packages, click . On the Name image page, enter a name for your image and click . If you do not enter a name, you can find the image you created by its UUID. On the Review page, review the details about the image creation and click Create image . After you complete the steps in the Create image wizard, the Image Builder dashboard is displayed. Insights image builder starts the compose of a RHEL image for the x86_64 architecture. The Insights image builder Images dashboard opens. You can see details such as the Image UUID, the cloud target environment, the image operating system release and the status of the image creation. Note The image build, upload and cloud registration processes can take up to ten minutes to complete.

Commands:
Chapter 5. Upgrading the Red Hat build of Keycloak Client Libraries The client libraries are those artifacts: Java admin client - Maven artifact org.keycloak:keycloak-admin-client Java authorization client - Maven artifact org.keycloak:keycloak-authz-client Java policy enforcer - Maven artifact org.keycloak:keycloak-policy-enforcer The client libraries are supported with all the supported Red Hat build of Keycloak server versions. The fact that client libraries are supported with more server versions makes the update easier, so you may not need to update the server at the same time when you update client libraries of your application. It is possible that client libraries may work even with the older releases of the Red Hat build of Keycloak server, but it is not guaranteed and officially supported. It may be needed to consult the javadoc of the client libraries like Java admin-client to see what endpoints and parameters are supported with which Red Hat build of Keycloak server version.

Commands:
14.6. Samba Network Browsing Network browsing is a concept that enables Windows and Samba servers to appear in the Windows Network Neighborhood . Inside the Network Neighborhood , icons are represented as servers and if opened, the server's shares and printers that are available are displayed. Network browsing capabilities require NetBIOS over TCP/IP. NetBIOS-based networking uses broadcast (UDP) messaging to accomplish browse list management. Without NetBIOS and WINS as the primary method for TCP/IP hostname resolution, other methods such as static files ( /etc/hosts ) or DNS, must be used. A domain master browser collates the browse lists from local master browsers on all subnets so that browsing can occur between workgroups and subnets. Also, the domain master browser should preferably be the local master browser for its own subnet. 14.6.1. Workgroup Browsing For each workgroup, there must be one and only one domain master browser. You can have one local master browser per subnet without a domain master browser, but this results in isolated workgroups unable to see each other. To resolve NetBIOS names in cross-subnet workgroups, WINS is required. Note The Domain Master Browser can be the same machine as the WINS server. There can only be one domain master browser per workgroup name. Here is an example of the smb.conf file in which the Samba server is a domain master browser: is an example of the smb.conf file in which the Samba server is a local master browser: The os level directive operates as a priority system for master browsers in a subnet. Setting different values ensures master browsers do not conflict with each other for authority. Note Lowering the os level directive results in Samba conflicting with other master browsers on the same subnet. The higher the value, the higher the priority. The highest a Windows server can operate at is 32. This is a good way of tuning multiple local master browsers. There are instances when a Windows NT machine on the subnet could be the local master browser. The following is an example smb.conf configuration in which the Samba server is not serving in any browsing capacity: Warning Having multiple local master browsers result in each server competing for browsing election requests. Make sure there is only one local master browser per subnet.

Commands:
[global] domain master = Yes local master = Yes preferred master = Yes os level = 35
[global] domain master = no local master = Yes preferred master = Yes os level = 35
[global] domain master = no local master = no preferred master = no os level = 0
6.2. IPsec Red Hat Enterprise Linux supports IPsec for connecting remote hosts and networks to each other using a secure tunnel on a common carrier network such as the Internet. IPsec can be implemented using a host-to-host (one computer workstation to another) or network-to-network (one LAN/WAN to another). The IPsec implementation in Red Hat Enterprise Linux uses Internet Key Exchange ( IKE ), which is a protocol implemented by the Internet Engineering Task Force ( IETF ) to be used for mutual authentication and secure associations between connecting systems. An IPsec connection is split into two logical phases. In phase 1, an IPsec node initializes the connection with the remote node or network. The remote node/network checks the requesting node's credentials and both parties negotiate the authentication method for the connection. On Red Hat Enterprise Linux systems, an IPsec connection uses the pre-shared key method of IPsec node authentication. In a pre-shared key IPsec connection, both hosts must use the same key in order to move to the second phase of the IPsec connection. Phase 2 of the IPsec connection is where the security association ( SA ) is created between IPsec nodes. This phase establishes an SA database with configuration information, such as the encryption method, secret session key exchange parameters, and more. This phase manages the actual IPsec connection between remote nodes and networks. The Red Hat Enterprise Linux implementation of IPsec uses IKE for sharing keys between hosts across the Internet. The racoon keying daemon handles the IKE key distribution and exchange.

Commands:
4.7.2. GFS File Attribute The gfs_tool command can be used to assign (set) a direct I/O attribute flag, directio , to a GFS file. The directio flag can also be cleared. Usage Setting the directio Flag Clearing the directio Flag File Specifies the file where the directio flag is assigned. Example In this example, the command sets the directio flag on the file named datafile in directory /gfs1 .

Commands:
gfs_tool setflag directio File
gfs_tool clearflag directio File
gfs_tool setflag directio /gfs1/datafile
Chapter 7. Displaying and Raising the Domain Level The domain level indicates what operations and capabilities are available in the IdM topology. Domain level 1 Examples of available functionality: simplified ipa-replica-install (see Section 4.5, "Creating the Replica: Introduction" ) enhanced topology management (see Chapter 6, Managing Replication Topology ) Important Domain level 1 was introduced in Red Hat Enterprise Linux 7.3 with IdM version 4.4. To use the domain level 1 features, all your replicas must be running Red Hat Enterprise Linux 7.3 or later. If your first server was installed with Red Hat Enterprise Linux 7.3, the domain level for your domain is automatically set to 1. If you upgrade all servers to IdM version 4.4 from earlier versions, the domain level is not raised automatically. If you want to use domain level 1 features, raise the domain level manually, as described in Section 7.2, "Raising the Domain Level" . Domain level 0 Examples of available functionality: ipa-replica-install requires a more complicated process of creating a replica information file on the initial server and copying it to the replica (see Section D.2, "Creating Replicas" ) more complicated and error-prone topology management using ipa-replica-manage and ipa-csreplica-manage (see Section D.3, "Managing Replicas and Replication Agreements" ) 7.1. Displaying the Current Domain Level Command Line: Displaying the Current Domain Level Log in as the administrator: Run the ipa domainlevel-get command: Web UI: Displaying the Current Domain Level Select IPA Server Topology Domain Level .

Commands:
kinit admin
ipa domainlevel-get ----------------------- Current domain level: 0 -----------------------
B.38.10. RHBA-2011:1495 - kernel bug fix update Updated kernel packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The kernel packages contain the Linux kernel, the core of any Linux operating system. Bug Fix BZ# 751081 When a host was in recovery mode and a SCSI scan operation was initiated, the scan operation failed and provided no error output. With this update, the underlying code has been modified, and the SCSI layer now waits for recovery of the host to complete scan operations for devices. All users of kernel are advised to upgrade to these updated packages, which fix this bug. The system must be rebooted for this update to take effect.

Commands:
4.89. ibus-table-erbi 4.89.1. RHBA-2011:1274 - ibus-table-erbi bug fix update An updated ibus-table-erbi package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The ibus-table-erbi provides the Simplified Chinese input method, ErBi. Bug Fixes BZ# 712805 Prior to this update, the ibus-table-erbi spec file contained a redundant line which printed the debug message "/usr/share/ibus-table/tables" at the end of installation. The line indicated the working directory of the post-install script and has been removed to fix the problem. BZ# 729906 Previously, the table index was updated when running the post-install script of the ibus-table-erbi package. This modified the size of the files, the MD5 Message-Digest Algorithm checksum and the access time of database files. As a consequence, the "rpm -V" command failed with false positive warnings of the aforementioned changes due to the changes not matching the values in the package metadata. This has been fixed: files that are expected to be modified when running the post-install script are now specified with correct verify flags in the spec file. All users of ibus-table-erbi are advised to upgrade to this updated package, which resolves these bugs.

Commands:
B.2. Using RPM RPM has five basic modes of operation (not counting package building): installing, uninstalling, upgrading, querying, and verifying. This section contains an overview of each mode. For complete details and options, try rpm --help or man rpm . You can also see Section B.5, "Additional Resources" for more information on RPM. B.2.1. Finding RPM Packages Before using any RPM packages, you must know where to find them. An Internet search returns many RPM repositories, but if you are looking for Red Hat RPM packages, they can be found at the following locations: The Red Hat Enterprise Linux installation media contain many installable RPMs. The initial RPM repositories provided with the YUM package manager. See Chapter 8, Yum for details on how to use the official Red Hat Enterprise Linux package repositories. The Extra Packages for Enterprise Linux (EPEL) is a community effort to provide high-quality add-on packages for Red Hat Enterprise Linux. See http://fedoraproject.org/wiki/EPEL for details on EPEL RPM packages. Unofficial, third-party repositories not affiliated with Red Hat also provide RPM packages. Important When considering third-party repositories for use with your Red Hat Enterprise Linux system, pay close attention to the repository's web site with regard to package compatibility before adding the repository as a package source. Alternate package repositories may offer different, incompatible versions of the same software, including packages already included in the Red Hat Enterprise Linux repositories. The Red Hat Errata Page, available at http://www.redhat.com/apps/support/errata/ .

Commands: