mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Desktop Kate now retains printing preferences Previously, the Kate text editor did not retain printing preferences, which meant that the user was forced to set all the Header & Footer and Margin preferences after every print job or session. This bug has been fixed, and Kate again retains the printing preferences as expected. LibreOffice upgrade The libreoffice packages have been upgraded to upstream version 4.2.8.2, which provides a number of bug fixes and enhancements over the version, including: OpenXML interoperability has been improved. Additional statistics functions have been added to the Calc application, thus improving interoperability with Microsoft Excel and its Analysis ToolPak add-in. Various performance improvements have been implemented in Calc. This update adds new import filters for importing files from the Apple Keynote and Abiword applications. The export filter for the MathML markup language has been improved. This update adds a new start screen that includes thumbnails of recently opened documents. A visual clue is now displayed in the Slide Sorter window for slides with transitions or animations. This update improves trend lines in charts. LibreOffice now supports BCP 47 language tags. For a complete list of bug fixes and enhancements provided by this upgrade, refer to https://wiki.documentfoundation.org/ReleaseNotes/4.2 New package: libgovirt The libgovirt package has been added to this Red Hat Enterprise Linux release. The libgovirt package is a library that allows the remote-viewer tool to connect to virtual machines managed by oVirt and Red Hat Enterprise Virtualization. dejavu-fonts upgraded to upstream version 2.33 The dejavu-fonts packages have been upgraded to upstream version 2.33, which provides a number of bug fixes and enhancements over the version. Notably, this adds a number of new characters and symbols to the supported fonts. Support for transliteration from Latin to US-ASCII Prior to this update, icu in Red Hat Enterprise Linux 6 did not support transliteration from Latin to US-ASCII characters mode of the transliterator_transliterate() function. Consequently, the user could not, for example, easily remove non-ASCII characters from PHP code strings. With this update, the user can use transliterator_transliterate() to transliterate Latin characters to US-ASCII characters.

Commands:
8.9. Improving Guest Virtual Machine Response Time Guest virtual machines can sometimes be slow to respond with certain workloads and usage patterns. Examples of situations which may cause slow or unresponsive guest virtual machines: Severely overcommitted memory. Overcommitted memory with high processor usage Other (not qemu-kvm processes) busy or stalled processes on the host physical machine. KVM guest virtual machines function as Linux processes. Linux processes are not permanently kept in main memory (physical RAM) and will be placed into swap space (virtual memory) especially if they are not being used. If a guest virtual machine is inactive for long periods of time, the host physical machine kernel may move the guest virtual machine into swap. As swap is slower than physical memory it may appear that the guest is not responding. This changes once the guest is loaded into the main memory. Note that the process of loading a guest virtual machine from swap to main memory may take several seconds per gigabyte of RAM assigned to the guest virtual machine, depending on the type of storage used for swap and the performance of the components. KVM guest virtual machines processes may be moved to swap regardless of whether memory is overcommitted or overall memory usage. Using unsafe overcommit levels or overcommitting with swap turned off guest virtual machine processes or other critical processes is not recommended. Always ensure the host physical machine has sufficient swap space when overcommitting memory. For more information on overcommitting with KVM, refer to Chapter 6, Overcommitting with KVM . Warning Virtual memory allows a Linux system to use more memory than there is physical RAM on the system. Underused processes are swapped out which allows active processes to use memory, improving memory utilization. Disabling swap reduces memory utilization as all processes are stored in physical RAM. If swap is turned off, do not overcommit guest virtual machines. Overcommitting guest virtual machines without any swap can cause guest virtual machines or the host physical machine system to crash.

Commands:
23.3. Methods 23.3.1. Creating a MAC Address Pool Creation of a MAC address pool requires values for name and ranges . Example 23.2. Creating a MAC address pool 23.3.2. Updating a MAC Address Pool The name , description , allow_duplicates , and ranges elements are updatable post-creation. Example 23.3. Updating a MAC address pool 23.3.3. Removing a MAC Address Pool Removal of a MAC address pool requires a DELETE request. Example 23.4. Removing a MAC address pool

Commands:
POST /ovirt-engine/api/macpools HTTP/1.1 Accept: application/xml Content-type: application/xml <mac_pool> <name>MACPool</name> <description>A MAC address pool</description> <allow_duplicates>true</allow_duplicates> <default_pool>false</default_pool> <ranges> <range> <from>00:1A:4A:16:01:51</from> <to>00:1A:4A:16:01:e6</to> </range> </ranges> </mac_pool>
PUT /ovirt-engine/api/macpools/ab39bbc1-1d64-4737-9b20-ce081f99b0e1 HTTP/1.1 Accept: application/xml Content-type: application/xml <mac_pool> <name>UpdatedMACPool</name> <description>An updated MAC address pool</description> <allow_duplicates>false</allow_duplicates> <ranges> <range> <from>00:1A:4A:16:01:51</from> <to>00:1A:4A:16:01:e6</to> </range> <range> <from>02:1A:4A:01:00:00</from> <to>02:1A:4A:FF:FF:FF</to> </range> </ranges> </mac_pool>
DELETE /ovirt-engine/api/macpools/ab39bbc1-1d64-4737-9b20-ce081f99b0e1 HTTP/1.1 HTTP/1.1 204 No Content
5.230. parted 5.230.1. RHBA-2012:0773 - parted bug fix update Updated parted packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The parted packages allow you to create, destroy, resize, move, and copy hard disk partitions. The parted program can be used for creating space for new operating systems, reorganizing disk usage, and copying data to new hard disks. Bug Fixes BZ# 698121 , BZ# 751164 Prior to this update, editing partitions on a mpath device udev could, under certain circumstances, interfere with re-reading the partition table. This update adds the dm_udev_wait option so that udev now correctly synchronizes. BZ# 750395 Prior to this update, the libparted partition_duplicate() function did not correctly copy all GPT partition flags. This update modifies the underlying code so that all flags are correctly copied and adds a test to ensure correct operation. All parted users are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 5. Leveraging certification Leveraging allows you to request credit for successful certification tests when similar or substantially similar BMCs are used across a family of server systems. It is based on your internal qualification testing of the specific BMC on each system, confirming that any variations are not material and the solution matches a previously certified one. Leveraging can reduce the amount of official testing needed for certification. You can request leveraging when the solution includes a previously certified BMC with the same firmware branch and equal or fewer features. Note It is your responsibility to verify that any differences in BMC-to-server interaction do not affect the certification.

Commands:
Chapter 37. Virtualization Guests no longer shut down unexpectedly during reboot On a Red Hat Enterprise Linux 7.4 guest running on qemu-kvm-1.5.3-139.el7 , if the i6300esb watchdog was set to poweroff , the watchdog was triggered when shutting down due to the timeout being calculated incorrectly. Consequently, when rebooting the guest, it shut down instead. With this update, the timeout calculations in qemu-kvm have been corrected. As a result, the virtual machine reboots properly. (BZ# 1470244 ) Guests accessed using a serial console no longer become unresponsive Previously, if a client opened a host-side pseudoterminal device (pty) on a KVM guest pty serial console and did not read from it, the guest in some cases became unresponsive because because of blocking read/write calls. With this update, the host-side pty open mode was set to non-blocking. As a result, the guest machine does not become unresponsive in the described scenario. (BZ# 1455451 ) virt-v2v now warns about not converting PCI passthrough devices The virt-v2v utility currently cannot convert PCI passthrough devices and thus ignores them in the conversion process. Prior to this update, however, attempting to convert a guest virtual machine with a PCI passthrough device successfully converted the guest, but did not provide any warning about the ignored PCI passthrough device. Now, converting such a guest logs an appropriate warning message during the conversion. (BZ# 1472719 ) When importing OVAs, virt-v2v now parses MAC addresses Previously, the virt-v2v utility did not parse the MAC addresses of network interfaces when importing Open Virtual Appliances (OVAs). Consequently, the converted guest virtual machines had network interfaces with different MAC addresses, resulting in the network setup breaking. With this release, virt-v2v parses the MAC addresses, if available, of network interfaces when importing OVAs. As a result, network converted guests have the same MAC addresses as specified in the OVAs and the network setup does not break. (BZ# 1506572 )

Commands:
Chapter 10. Component details The following table shows the component versions for each AMQ Streams release. AMQ Streams Apache Kafka Strimzi Operators Kafka Bridge Oauth Cruise Control 2.5.2 3.5.0 (+ 3.5.2) 0.36.0 0.26 0.13.0 2.5.123 2.5.1 3.5.0 0.36.0 0.26 0.13.0 2.5.123 2.5.0 3.5.0 0.36.0 0.26 0.13.0 2.5.123 2.4.0 3.4.0 0.34.0 0.25.0 0.12.0 2.5.112 2.3.0 3.3.1 0.32.0 0.22.3 0.11.0 2.5.103 2.2.2 3.2.3 0.29.0 0.21.5 0.10.0 2.5.103 2.2.1 3.2.3 0.29.0 0.21.5 0.10.0 2.5.103 2.2.0 3.2.3 0.29.0 0.21.5 0.10.0 2.5.89 2.1.0 3.1.0 0.28.0 0.21.4 0.10.0 2.5.82 2.0.1 3.0.0 0.26.0 0.20.3 0.9.0 2.5.73 2.0.0 3.0.0 0.26.0 0.20.3 0.9.0 2.5.73 1.8.4 2.8.0 0.24.0 0.20.1 0.8.1 2.5.59 1.8.0 2.8.0 0.24.0 0.20.1 0.8.1 2.5.59 1.7.0 2.7.0 0.22.1 0.19.0 0.7.1 2.5.37 1.6.7 2.6.3 0.20.1 0.19.0 0.6.1 2.5.11 1.6.6 2.6.3 0.20.1 0.19.0 0.6.1 2.5.11 1.6.5 2.6.2 0.20.1 0.19.0 0.6.1 2.5.11 1.6.4 2.6.2 0.20.1 0.19.0 0.6.1 2.5.11 1.6.0 2.6.0 0.20.0 0.19.0 0.6.1 2.5.11 1.5.0 2.5.0 0.18.0 0.16.0 0.5.0 - 1.4.1 2.4.0 0.17.0 0.15.2 0.3.0 - 1.4.0 2.4.0 0.17.0 0.15.2 0.3.0 - 1.3.0 2.3.0 0.14.0 0.14.0 0.1.0 - 1.2.0 2.2.1 0.12.1 0.12.2 - - 1.1.1 2.1.1 0.11.4 - - - 1.1.0 2.1.1 0.11.1 - - - 1.0 2.0.0 0.8.1 - - - Note Strimzi 0.26.0 contains a Log4j vulnerability. The version included in the product has been updated to depend on versions that do not contain the vulnerability.

Commands:
6.7.6. Removing Fence Methods and Fence Instances To remove a fence method from your cluster configuration, execute the following command: For example, to remove a fence method that you have named APC that you have configured for node01.example.com from the cluster configuration file on cluster node node01.example.com , execute the following command: To remove all fence instances of a fence device from a fence method, execute the following command: For example, to remove all instances of the fence device named apc1 from the method named APC-dual configured for node01.example.com from the cluster configuration file on cluster node node01.example.com , execute the following command:

Commands:
ccs -h host --rmmethod method node
ccs -h node01.example.com --rmmethod APC node01.example.com
ccs -h host --rmfenceinst fencedevicename node method
ccs -h node01.example.com --rmfenceinst apc1 node01.example.com APC-dual
19.2. Basic Options This section provides information about the basic options. Emulated Machine -M <machine-type> -machine <machine-type> [,<property>[=<value>][,..]] Processor Type -cpu <model>[,<FEATURE>][...] Additional models are visible by running -cpu ? command. Opteron_G5 - AMD Opteron 63xx class CPU Opteron_G4 - AMD Opteron 62xx class CPU Opteron_G3 - AMD Opteron 23xx (AMD Opteron Gen 3) Opteron_G2 - AMD Opteron 22xx (AMD Opteron Gen 2) Opteron_G1 - AMD Opteron 240 (AMD Opteron Gen 1) Westmere - Westmere E56xx/L56xx/X56xx (Nehalem-C) Haswell - Intel Core Processor (Haswell) SandyBridge - Intel Xeon E312xx (Sandy Bridge) Nehalem - Intel Core i7 9xx (Nehalem Class Core i7) Penryn - Intel Core 2 Duo P9xxx (Penryn Class Core 2) Conroe - Intel Celeron_4x0 (Conroe/Merom Class Core 2) cpu64-rhel5 - Red Hat Enterprise Linux 5 supported QEMU Virtual CPU version cpu64-rhel6 - Red Hat Enterprise Linux 6 supported QEMU Virtual CPU version default - special option use default option from above. Processor Topology -smp <n>[,cores=<ncores>][,threads=<nthreads>][,sockets=<nsocks>][,maxcpus=<maxcpus>] Hypervisor and guest operating system limits on processor topology apply. NUMA System -numa <nodes>[,mem=<size>][,cpus=<cpu[-cpu>]][,nodeid=<node>] Hypervisor and guest operating system limits on processor topology apply. Memory Size -m <megs> Supported values are limited by guest minimal and maximal values and hypervisor limits. Keyboard Layout -k <language> Guest Name -name <name> Guest UUID -uuid <uuid>

Commands:
14.16. Guest Virtual Machine CPU Model Configuration This section provides information about guest virtual machine CPU model configuration. 14.16.1. Introduction Every hypervisor has its own policy for what a guest virtual machine will see for its CPUs by default. Whereas some hypervisors decide which CPU host physical machine features will be available for the guest virtual machine, QEMU/KVM presents the guest virtual machine with a generic model named qemu32 or qemu64 . These hypervisors perform more advanced filtering, classifying all physical CPUs into a handful of groups and have one baseline CPU model for each group that is presented to the guest virtual machine. Such behavior enables the safe migration of guest virtual machines between host physical machines, provided they all have physical CPUs that classify into the same group. libvirt does not typically enforce policy itself, rather it provides the mechanism on which the higher layers define their own desired policy. Understanding how to obtain CPU model information and define a suitable guest virtual machine CPU model is critical to ensure guest virtual machine migration is successful between host physical machines. Note that a hypervisor can only emulate features that it is aware of and features that were created after the hypervisor was released may not be emulated.

Commands:
Chapter 4. Introduction to devfile in Dev Spaces Devfiles are yaml text files used for development environment customization. Use them to configure a devfile to suit your specific needs and share the customized devfile across multiple workspaces to ensure identical user experience and build, run, and deploy behaviours across your team. Red Hat OpenShift Dev Spaces-specific devfile features Red Hat OpenShift Dev Spaces is expected to work with most of the popular images defined in the components section of devfile. For production purposes, it is recommended to use one of the Universal Base Images as a base image for defining the Cloud Development Environment. Warning Some images can not be used as-is for defining Cloud Development Environment since Visual Studio Code - Open Source ("Code - OSS") can not be started in the containers with missing openssl and libbrotli . Missing libraries should be explicitly installed on the Dockerfile level e.g. RUN yum install compat-openssl11 libbrotli Devfile and Universal Developer Image You do not need a devfile to start a workspace. If you do not include a devfile in your project repository, Red Hat OpenShift Dev Spaces automatically loads a default devfile with a Universal Developer Image (UDI). Devfile Registry {Devfile Registry contains ready-to-use community-supported devfiles for different languages and technologies. Devfiles included in the registry should be treated as samples rather than templates. Additional resources What is a devfile Benefits of devfile Devfile customization overview Devfile.io Customizing Cloud Development Environments

Commands:
Chapter 5. Managed KIE Server A managed instance requires an available Process Automation Manager controller to start KIE Server. A Process Automation Manager controller manages KIE Server configuration in a centralized way. Each Process Automation Manager controller can manage multiple configurations at once, and there can be multiple Process Automation Manager controllers in the environment. Managed KIE Server can be configured with a list of Process Automation Manager controllers, but will only connect to one at a time. Important All Process Automation Manager controllers should be synchronized to ensure that the same set of configuration is provided to the server, regardless of the Process Automation Manager controller to which it connects. When KIE Server is configured with a list of Process Automation Manager controllers, it will attempt to connect to each of them at startup until a connection is successfully established with one of them. If a connection cannot be established, the server will not start, even if there is a local storage available with configuration. This ensures consistency and prevents the server from running with redundant configuration. Note To run KIE Server in standalone mode without connecting to Process Automation Manager controllers, see Chapter 6, Unmanaged KIE Server .

Commands:
2.2.7.4. Disable Postfix Network Listening By default, Postfix is set up to only listen to the local loopback address. You can verify this by viewing the file /etc/postfix/main.cf . View the file /etc/postfix/main.cf to ensure that only the following inet_interfaces line appears: This ensures that Postfix only accepts mail messages (such as cron job reports) from the local system and not from the network. This is the default setting and protects Postfix from a network attack. For removal of the localhost restriction and allowing Postfix to listen on all interfaces the inet_interfaces = all setting can be used.

Commands:
inet_interfaces = localhost
Chapter 1. Long Term Support for AMQ Broker 7.8 AMQ Broker 7.8 has been designated as a Long Term Support (LTS) release version. Bug fixes and security advisories will be made available for AMQ Broker 7.8 in a series of micro releases (7.8.1, 7.8.2, and so on) for a period of at least 12 months. This means that you will be able to get recent bug fixes and security advisories for AMQ Broker without having to upgrade to a new minor release. Note the following important points about the LTS release stream: The LTS release stream provides only bug fixes. No new enhancements will be added to this stream. To remain in a supported configuration, you must upgrade to the latest micro release in the LTS release stream. The LTS version will be supported for at least 12 months from the time of the AMQ Broker 7.8.0 GA release. Support for Red Hat Enterprise Linux and OpenShift Container Platform The AMQ Broker 7.8 LTS version supports: Red Hat Enterprise Linux 6, 7, and 8 OpenShift Container Platform 3.11 and 4.5 and 4.6 Note the following important points about support for Red Hat Enterprise Linux and OpenShift Container Platform: AMQ Broker 7.8 is the last version that will support Red Hat Enterprise Linux 6 and OpenShift Container Platform 3.11. Red Hat does not guarantee that AMQ Broker 7.8 will be supported on future versions (that is, versions greater than 4.6) of OpenShift Container Platform. For information about issues resolved in AMQ Broker 7.8 LTS micro releases, see AMQ 7 Broker - 7.8.x Resolved Issues .

Commands:
Chapter 6. Red Hat Decision Manager roles and users To access Business Central or KIE Server, you must create users and assign them appropriate roles before the servers are started. You can create users and roles when you install Business Central or KIE Server. If both Business Central and KIE Server are running on a single instance, a user who is authenticated for Business Central can also access KIE Server. However, if Business Central and KIE Server are running on different instances, a user who is authenticated for Business Central must be authenticated separately to access KIE Server. For example, if a user who is authenticated on Business Central but not authenticated on KIE Server tries to view or manage process definitions in Business Central, a 401 error is logged in the log file and the Invalid credentials to load data from remote server. Contact your system administrator. message appears in Business Central. This section describes Red Hat Decision Manager user roles. Note The admin , analyst , and rest-all roles are reserved for Business Central. The kie-server role is reserved for KIE Server. For this reason, the available roles can differ depending on whether Business Central, KIE Server, or both are installed. admin : Users with the admin role are the Business Central administrators. They can manage users and create, clone, and manage repositories. They have full access to make required changes in the application. Users with the admin role have access to all areas within Red Hat Decision Manager. analyst : Users with the analyst role have access to all high-level features. They can model projects. However, these users cannot add contributors to spaces or delete spaces in the Design Projects view. Access to the Deploy Execution Servers view, which is intended for administrators, is not available to users with the analyst role. However, the Deploy button is available to these users when they access the Library perspective. rest-all : Users with the rest-all role can access Business Central REST capabilities. kie-server : Users with the kie-server role can access KIE Server REST capabilities.

Commands:
22.2. NTP Strata NTP servers are classified according to their synchronization distance from the atomic clocks which are the source of the time signals. The servers are thought of as being arranged in layers, or strata, from 1 at the top down to 15. Hence the word stratum is used when referring to a specific layer. Atomic clocks are referred to as Stratum 0 as this is the source, but no Stratum 0 packet is sent on the Internet, all stratum 0 atomic clocks are attached to a server which is referred to as stratum 1. These servers send out packets marked as Stratum 1. A server which is synchronized by means of packets marked stratum n belongs to the , lower, stratum and will mark its packets as stratum n+1 . Servers of the same stratum can exchange packets with each other but are still designated as belonging to just the one stratum, the stratum one below the best reference they are synchronized to. The designation Stratum 16 is used to indicate that the server is not currently synchronized to a reliable time source. Note that by default NTP clients act as servers for those systems in the stratum below them. Here is a summary of the NTP Strata: Stratum 0: Atomic Clocks and their signals broadcast over Radio and GPS GPS (Global Positioning System) Mobile Phone Systems Low Frequency Radio Broadcasts WWVB (Colorado, USA.), JJY-40 and JJY-60 (Japan), DCF77 (Germany), and MSF (United Kingdom) These signals can be received by dedicated devices and are usually connected by RS-232 to a system used as an organizational or site-wide time server. Stratum 1: Computer with radio clock, GPS clock, or atomic clock attached Stratum 2: Reads from stratum 1; Serves to lower strata Stratum 3: Reads from stratum 2; Serves to lower strata Stratum n+1 : Reads from stratum n ; Serves to lower strata Stratum 15: Reads from stratum 14; This is the lowest stratum. This process continues down to Stratum 15 which is the lowest valid stratum. The label Stratum 16 is used to indicated an unsynchronized state.

Commands: