mtpti5iD/redhat-docs_dataset huggingface dataset:
8.74. iptables 8.74.1. RHBA-2013:1710 - iptables bug fix and enhancement update Updated iptables packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The iptables utility controls the network packet filtering code in the Linux kernel. The utility allows users to perform certain operations such as setting up firewalls or IP masquerading. Bug Fixes BZ# 924362 A version of iptables added the "alternatives" functionality support for the /lib/xtables/ or /lib64/xtables/ directory. However, iptables failed to replace the directory with the alternatives slave symbolic link when upgrading iptables with the "yum upgrade" command and the directory contained custom plug-in files. Consequently, some iptables modules became unavailable. This problem has been fixed by modifying the iptables spec file so that the /lib/xtables/ or /lib64/xtables/ directory is no longer managed by "alternatives". BZ# 983198 The iptables-save command previously supported only the "--modprobe=" option to specify the path to the modprobe executable. However, the iptables-save(8) man page incorrectly stated that this action could have been performed using an unsupported option, "-M", which could lead to confusion. The iptables-save command has been modified to support the "-M" option for specifying the path to modprobe, and corrects the iptables-save(8) man page, which now correctly mentions both the "-M" and "--modprobe=" option. BZ# 1007632 Due to a bug in the iptables init script, the system could become unresponsive during shutdown when using the network-based root device and the default filter for INPUT or OUTPUT policy was DROP. This problem has been fixed by setting the default chain policy to ACCEPT before flushing the iptables rules and deleting the iptables chains. Enhancements BZ# 845435 The iptables utility has been modified to support a new option, "--queue-bypass", which allows bypassing an NFQUEUE rule if the specified queue is not used. BZ# 928812 A new iptables service option,"reload", has been added to enable a refresh of the firewall rules without unloading netfilter kernel modules and a possible drop of connections. Users of iptables are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
8.58. file-roller 8.58.1. RHBA-2014:0642 - file-roller bug fix update Updated file-roller packages that fix one bug are now available for Red Hat Enterprise Linux 6. File Roller is an application for creating and viewing archives files, such as tar or zip files. Bug Fix BZ# 718338 Previously, the file-roller application did not correctly handle file names with spaces. As a consequence, an error could occur when adding files to an archive because names with spaces were not properly recognized by file-roller, for example when using the 'Compress' menu item in the Nautilus file manager. With this update, file-roller uses the correct API to handle file names. As a result, archives are created as expected and errors no longer occur in the described situation. Users of file-roller are advised to upgrade to these updated packages, which fix this bug.

Commands:
A.3. Using cURL cURL uses a command line interface to send requests to a HTTP server. Integrating a request requires the following command syntax: The uri refers to target HTTP address to send the request. This is a location on your Red Hat Virtualization Manager host within the API entry point path ( /ovirt-engine/api ). cURL options -X COMMAND , --request COMMAND The request command to use. In the context of the REST API, use GET , POST , PUT or DELETE . Example: -X GET -H LINE , --header LINE HTTP header to include with the request. Use multiple header options if more than one header is required. Example: -H "Accept: application/xml" -H "Content-Type: application/xml" -u USERNAME:PASSWORD , --user USERNAME:PASSWORD The user name and password of the Red Hat Virtualization user. This attribute acts as a convenient replacement for the Authorization: header. Example: -u admin@internal:p@55w0rd! --cacert CERTIFICATE The location of the certificate file for SSL communication to the REST API. The certificate file is saved locally on the client machine. Use the -k attribute to bypass SSL. Example: --cacert ~/Certificates/rhevm.cer -d BODY , --data BODY The body to send for requests. Use with POST , PUT and DELETE requests. Ensure to specify the Content-Type: application/xml header if a body exists in the request. Example: -d "<cdrom><file id='rhel-server-6.0-x86_64-dvd.iso'/></cdrom>"

Commands:
Usage: curl [options] uri
4.3.3. Conditional Breakpoints In many real-world cases, a program may perform its task well during the first few thousand times; it may then start crashing or encountering errors during its eight thousandth iteration of the task. Debugging programs like this can be difficult, as it is hard to imagine a programmer with the patience to issue a continue command thousands of times just to get to the iteration that crashed. Situations like this are common in real life, which is why GDB allows programmers to attach conditions to a breakpoint. For example, consider the following program: simple.c To set a conditional breakpoint at the GDB prompt: With this condition, the program execution will eventually stop with the following output: Inspect the breakpoint information (using info br ) to review the breakpoint status:

Commands:
#include <stdio.h> main() { int i; for (i = 0;; i++) { fprintf (stdout, "i = %d\n", i); } }
(gdb) br 8 if i == 8936 Breakpoint 1 at 0x80483f5: file iterations.c, line 8. (gdb) r
i = 8931 i = 8932 i = 8933 i = 8934 i = 8935 Breakpoint 1, main () at iterations.c:8 8 fprintf (stdout, "i = %d\n", i);
(gdb) info br Num Type Disp Enb Address What 1 breakpoint keep y 0x080483f5 in main at iterations.c:8 stop only if i == 8936 breakpoint already hit 1 time
5.79. gdm 5.79.1. RHBA-2012:1446 - gdm bug fix update Updated gdm packages that fix a bug are now available for Red Hat Enterprise Linux 6. The GNOME Display Manager (GDM) is a highly configurable reimplementation of XDM, the X Display Manager. GDM allows you to log into your system with the X Window System running and supports running several different X sessions on your local machine at the same time. Bug Fix BZ# 860646 When gdm was used to connect to a server via XDMCP (X Display Manager Control Protocol), another connection to a remote system using the "ssh -X" command resulted in wrong authorization with the X server. Consequently, applications such as xterm could not be displayed on the remote system. This update provides a compatible MIT-MAGIC-COOKIE-1 key in the described scenario, thus fixing this bug. All users of gdm are advised to upgrade to these updated packages, which fix this bug.

Commands:
2.4. The Software Collection Prefix When naming your Software Collection, you are advised to prefix the name of your Software Collection as described below in order to avoid possible name conflicts with the system versions of the packages that are part of your Software Collection. The Software Collection prefix consists of two parts: the provider part, which defines the provider's name, and the name of the Software Collection itself. These two parts of the Software Collection prefix are separated by a dash ( - ), as in the following example: In this example, myorganization is the provider's name, and ruby193 is the name of the Software Collection. While it is ultimately a vendor's or distributor's decision whether to specify the provider's name in the prefix or not, specifying it is highly recommended. A notable exception are Software Collections which were first shipped with Red Hat Software Collections 1.x, they do not specify the provider's name in their prefixes. Newer Software Collections added in Red Hat Software Collections 2.0 and later use rh as the provider's name. For example:

Commands:
myorganization-ruby193
rh-ruby23
16.3. ID Views on the Client Side Important ID views can only be used on Red Hat Enterprise Linux 6 clients running Red Hat Enterprise Linux 6.7 or later. The client must be enrolled with an IdM server based on Red Hat Enterprise Linux 7.1 or later to benefit from this functionality. On the client side, the client itself determines to which ID view it belongs after the client system is started or restarted. The client then begins to use the data defined by the applied ID view. Because ID views are applied on the client side, clients running Red Hat Enterprise Linux 7.0 and earlier versions of IdM only see the Default Trust View. If a client requires a different ID view, update SSSD on the client to a version with ID View support or have the client use the compat LDAP tree. Whenever the administrator applies another ID view on a client, the client and all the other clients applying this ID view must restart the SSSD service. Note Applying an ID view can have a negative impact on SSSD performance because certain optimizations and ID views cannot run at the same time. For example, ID views prevent SSSD from optimizing the process of looking up groups on the server. With ID views, SSSD must check every member on the returned list of group member names if the group name is overridden. Without ID views, SSSD can only collect the user names from the member attribute of the group object. This negative effect will most likely become apparent when the SSSD cache is empty or when all entries are invalid, that is, after clearing the cache.

Commands:
Framework for Upgrades (13 to 16.2) Red Hat OpenStack Platform 16.2 In-place upgrades from Red Hat OpenStack Platform 13 to 16.2 OpenStack Documentation Team rhos-docs@redhat.com Abstract This guide contains information on the framework for the in-place upgrades across long-life versions. This framework includes tools to upgrade your OpenStack Platform environment from one long life version to the long life version. In this case, the guide focuses on upgrading from Red Hat OpenStack Platform 13 (Queens) to 16.2 (Train).

Commands:
15.3.2. Verifying Signature of Packages To check the GnuPG signature of an RPM file after importing the builder's GnuPG key, use the following command (replace <rpm-file> with filename of the RPM package): If all goes well, the following message is displayed: md5 gpg OK . That means that the signature of the package has been verified and that it is not corrupt.

Commands:
-K <rpm-file>
7.29. Core X11 clients 7.29.1. RHSA-2013:0502 - Low: Core X11 clients security, bug fix, and enhancement update Updated core client packages for the X Window System that fix one security issue, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low 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. The Core X11 clients packages provide the xorg-x11-utils, xorg-x11-server-utils, and xorg-x11-apps clients that ship with the X Window System. Security Fix CVE-2011-2504 It was found that the x11perfcomp utility included the current working directory in its PATH environment variable. Running x11perfcomp in an attacker-controlled directory would cause arbitrary code execution with the privileges of the user running x11perfcomp. Note The xorg-x11-utils and xorg-x11-server-utils packages have been upgraded to upstream version 7.5, and the xorg-x11-apps package to upstream version 7.6, which provides a number of bug fixes and enhancements over the versions. (BZ# 835277 , BZ#835278, BZ#835281) All users of xorg-x11-utils, xorg-x11-server-utils, and xorg-x11-apps are advised to upgrade to these updated packages, which fix these issues and add these enhancements.

Commands:
Chapter 83. ExternalConfiguration schema reference Used in: KafkaConnectSpec , KafkaMirrorMaker2Spec Full list of ExternalConfiguration schema properties Configures external storage properties that define configuration options for Kafka Connect connectors. You can mount ConfigMaps or Secrets into a Kafka Connect pod as environment variables or volumes. Volumes and environment variables are configured in the externalConfiguration property in KafkaConnect.spec or KafkaMirrorMaker2.spec . When applied, the environment variables and volumes are available for use when developing your connectors. For more information, see Loading configuration values from external sources . 83.1. ExternalConfiguration schema properties Property Property type Description env ExternalConfigurationEnv array Makes data from a Secret or ConfigMap available in the Kafka Connect pods as environment variables. volumes ExternalConfigurationVolumeSource array Makes data from a Secret or ConfigMap available in the Kafka Connect pods as volumes.

Commands:
15.3. Using a VNC Viewer A VNC viewer is a program which shows the graphical user interface created by the VNC server and can control the VNC server remotely. The desktop that is shared is not by default the same as the desktop that is displayed to a user directly logged into the system. The VNC server creates a unique desktop for every display number. Any number of clients can connect to a VNC server. 15.3.1. Installing the VNC Viewer To install the TigerVNC client, vncviewer , as root , run the following command: ~]# yum install tigervnc The TigerVNC client has a graphical user interface ( GUI ) which can be started by entering the command vncviewer . Alternatively, you can operate vncviewer through the command-line interface ( CLI ). To view a list of parameters for vncviewer enter vncviewer -h on the command line.

Commands:
Part VII. Process engine in Red Hat Process Automation Manager As a business process analyst or developer, your understanding of the process engine in Red Hat Process Automation Manager can help you design more effective business assets and a more scalable process management architecture. The process engine implements the Business Process Management (BPM) paradigm in Red Hat Process Automation Manager and manages and executes business assets that comprise processes. This document describes concepts and functions of the process engine to consider as you create your business process management system and process services in Red Hat Process Automation Manager.

Commands:
7.28. Core X11 Libraries 7.28.1. RHBA-2013:0294 - Core X11 libraries bug fix and enhancement update Updated Core X11 libraries packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The Core X11 libraries contain the base protocol of the X Window System, which is a networked windowing system for bitmap displays used to build graphical user interfaces on Unix, Unix-like, and other operating systems. The pixman package has been upgraded to upstream version 0.18.4, which provides a number of bug fixes and enhancements over the version. (BZ#644296) The following packages have been upgraded to their upstream versions to conform to X Window System Test Suite (XTS5): Table 7.1. Upgraded packages Package name Upstream version BZ number libxcb 1.8.1 755654 libXcursor 1.1.13 755656 libX11 1.5.0 755657 libXi 1.6.1 755658 libXt 1.1.3 755659 libXfont 1.4.5 755661 libXrender 0.9.7 755662 libXtst 1.2.1 755663 libXext 1.3.1 755665 libXaw 1.0.11 755666 libXrandr 1.4.0 755667 libXft 2.3.1 755668 The following packages have been upgraded to their respective upstream versions, which provides a number of bug fixes and enhancements over the versions. Table 7.2. Upgraded packages Package name Upstream version BZ number libXau 1.0.6 835172 libXcomposite 0.4.3 835183 libXdmcp 1.1.1 835184 libXevie 1.0.3 835186 libXinerama 1.1.2 835187 libXmu 1.1.1 835188 libXpm 3.5.10 835190 libXres 1.0.6 835191 libXScrnSaver 1.2.2 835192 libXv 1.0.7 835193 libXvMC 1.0.7 835195 libXxf86dga 1.1.3 835196 libXxf86misc 1.0.3 835197 libXxf86vm 1.1.2 835198 libdrm 2.4.39 835202 libdmx 1.1.2 835203 pixman 0.26.2 835204 xorg-x11-proto-devel 7.6 835206 xorg-x11-util-macros 1.17 835207 xorg-x11-xtrans-devel 1.2.7 835276 xkeyboard-config 2.6 835284 libpciaccess 0.13.1 843585 xcb-proto 1.7 843593 libSM 1.2.1 843641 Bug Fixes BZ# 802559 Previously, in the xorg-x11-proto-devel package, the definition of the _X_NONNULL macro was incompatible with C89 compilers. Consequently, C89 applications could not be built in C89 mode if the X11/Xfuncproto.h file was included. This update fixes the macro definition to be compatible with C89 mode. BZ# 804907 Prior to this update, XI2 events were not properly initialized and could contain garbage values. A patch for the libXi package, which had been setting values to garbage, has been provided to fix this bug. Now, actual events no longer contain garbage values and are initialized as expected. BZ# 871460 Previously, the spec file of the xkeyboard-config package used the %{dist} macro in the Version tag. Although the standard Red Hat Enterprise Linux build environment defines this macro, it does not need to be defined. If it was not defined, %{dist} appeared literally in the resulting RPM package's version string when the package was rebuilt. The spec file has been corrected to use the conditional %{?dist} form, which expands to an empty string if %{dist} is not defined. Users of Core X11 libraries are advised to upgrade to these updated packages, which fix these bugs and add various enhancements.

Commands:
Chapter 4. Troubleshooting The following sections explain how to resolve issues that may occur in Metrics Store. 4.1. Information Is Missing from Kibana If Kibana is not displaying metric or log information as expected, use journalctl to investigate the collectd and rsyslog log files as follows: If only metrics information is missing, check the collectd log files. If only log information is missing, check the rsyslog log files. If both metrics and logs information are missing, check both log files. To investigate collectd log files, log in as root and run the following command: To investigate rsyslog log files, run the following command: To learn about additional journalctl options, see journalctl in Linux man pages . 4.2. Extracting Elasticsearch logs To extract Elasticsearch logs Log in to the Metrics Store virtual machine as root , and run the following command. Where openshift-logging is the namespace for the Elasticsearch pod: Optionally, you can use the use the OpenShift logging-dump tool located at logging dump tool script 4.3. Searching Elasticsearch Logs To search for all RHV/oVirt logs, ordered by timestamp from newest to oldest.Log in to the Metrics Store virtual machine as root , and run the following command, where openshift-logging is the namespace for the Elasticsearch pod: The output is presented in the human readable JSON format. 4.4. Searching log record results To search the log report results, you can use the get last rec from host search tool. The search tool shows how long it has been since the Metrics Store virtual machine received a record from each host that it knows about during a given time interval (last 3 hours by default). For each host that the Metrics Store virtual machine receives logs from over the defined duration (default 3h) duration, it prints out "green", "yellow", or "red", depending on whether the Metrics Store virtual machine received a record from that host recently or not. This is followed by the number of seconds it has been since the last record was received from that host, and the number of records received. Log in to the Metrics Store virtual machine as root , and clone the script repository: Run the script: To change the interval, change the OLDEST value to a longer or shorter interval in hours. For example, to go back 1 day (24 hours), use: Note Some hosts may not be listed, if no records were received from that host during the given time interval.

Commands:
journalctl -u collectd
journalctl -u rsyslog
for espod in USD(oc -n openshift-logging get pods -l component=es -o jsonpath='{.items[*].metadata.name}') ; do oc -n openshift-logging exec -c elasticsearch USDespod -- logs > USDespod.log 2>&1 done
-n opesnshift-logging exec -c elasticsearch USD(oc -n openshift-logging get pods -l component=es -o jsonpath='{.items[0].metadata.name}') -- es_util --query=project.ovirt-logs*/_search?sort=@timestamp:desc \&pretty | more
git clone https://github.com/jcantrill/cluster-logging-tools -b release-3.11
cd cluster-logging-tools/scripts [OLDEST=3h] ./get-last-rec-from-host
OLDEST=24h ./get-last-rec-from-host
Chapter 8. Internationalization 8.1. Input Methods The default input framework for the GNOME Desktop in Red Hat Enterprise Linux 7 is IBus (Intelligent Input Bus). It integrates with GNOME 3 and includes a user interface for input method selection. 8.1.1. Configuring and Switching Input Methods Users can use the Region & Language panel in the GNOME Settings to configure their input methods. More information on using input methods can be found in GNOME Help. To access it, press the Super key to enter the Activities Overview , type help , and then press Enter . For non-GNOME sessions, IBus can configure both XKB layouts and input methods in the ibus-setup tool and switch them with a shortcut. The default shortcut to switch input sources is Super + Space . In Red Hat Enterprise Linux 6, the shortcut was Ctrl + Space . 8.1.2. Predictive Input Method for IBus ibus-typing-booster is a predictive input method for the IBus platform. It predicts complete words based on partial input, allowing for faster and more accurate text input. Users can select the required word from a list of suggestions. ibus-typing-booster can also use Hunspell dictionaries to make suggestions for a language. 8.1.3. IBus in the GNOME Desktop Replaces im-chooser Because IBus is now integrated with the GNOME Desktop, im-chooser is deprecated except for using non-IBus input methods.

Commands:
Chapter 1. Overview of access management and authentication Ansible Automation Platform features a platform interface where you can set up centralized authentication, configure access management, and configure global and system level settings from a single location. The first time you log in to the Ansible Automation Platform, you must enter your subscription information to activate the platform. For more information about licensing and subscriptions, refer to Managing Ansible Automation Platform licensing, updates and support . A system administrator can configure access, permissions and system settings through the following tasks: Configuring authentication in the Ansible Automation Platform , where you set up simplified login for users by selecting from several authentication methods available and define permissions and assign them to users with authenticator maps. Configuring access to external applications with token-based authentication , where you can configure authentication of third-party tools and services with the platform through integrated OAuth 2 token support. Managing access with role based access control , where you configure user access based on their role within a platform organization. Configuring Ansible Automation Platform , where you can configure global and system level settings for the platform and services.

Commands: