mtpti5iD/redhat-docs_dataset huggingface dataset:
5.100. gtk2 5.100.1. RHBA-2012:0809 - gtk2 bug fix and enhancement update Updated gtk2 packages that fix three bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. GTK+ is a multi-platform toolkit for creating graphical user interfaces. Bug Fixes BZ# 697437 Previously, the "Open Files" dialog box failed to show the "Size" column if it was previously used in "Search" mode. This update fixes the bug by ensuring that the "Size" column is always displayed accordingly to the "Show Size Column" context menu option. BZ# 750756 Previously, copying text from selectable labels, such as those displayed in message dialog boxes, using the Ctrl+Insert key combination did not work. This update adds the Ctrl+Insert key combination that copies selected text to clipboard when activated. BZ# 801620 Previously, certain GTK applications, such as virt-viewer, failed to properly initialize key bindings associated with menu items. This was due to a bug in the way properties associated with the menu items were parsed by the library. This update fixes the bug, rendering the menu items accessible again by key bindings for applications that use this feature. Enhancement BZ# 689188 Previously, the "Open Files" dialog box could appear with an abnormal width when the "file type" filter contained a very long string (as observed with certain image hosting websites), making the dialog unusable. With this update, the dialog box splits the filter string into multiple lines of text, so that the dialog keeps a reasonable width. All users of gtk2 are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
8.246. tsclient 8.246.1. RHBA-2014:0524 - tsclient bug fix update Updated tsclient packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The Terminal Server Client (tsclient) is a GTK2 front end that makes it easy to use the Remote Desktop Protocol client (rdesktop) and vncviewer utilities. Bug Fixes BZ# 798631 Previously, the tsclient user interface did not offer an option to set the 32-bit color depth in the "Advanced Options" menu for the "Windows Terminal Service" connection type. Consequently, the 32-bit color depth could not be selected even though it was supported on the system, and connection to Windows systems could not be established with more than 16-bit color depth. With this update, the error in the "Advanced Options" menu has been fixed, and the 32-bit color depth option now functions as intended. BZ# 848526 Prior to this update, tsclient was not fully compatible with the Remote Desktop Protocol (RDP). Consequently, tsclient could, under certain circumstances, terminate unexpectedly when the user was connected to a remote system over RDP. This update addresses the problems with RDP compatibility, and tsclient no longer crashes when using RDP for remote connection. Users of tsclient are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 2. Load balancing considerations Distributing load between several Capsule Servers prevents any one Capsule from becoming a single point of failure. Configuring Capsules to use a load balancer can provide resilience against planned and unplanned outages. This improves availability and responsiveness. Consider the following guidelines when configuring load balancing: If you use Puppet, Puppet certificate signing is assigned to the first Capsule that you configure. If the first Capsule is down, clients cannot obtain Puppet content. This solution does not use Pacemaker or other similar HA tools to maintain one state across all Capsules. To troubleshoot issues, reproduce the issue on each Capsule, bypassing the load balancer. Additional maintenance required for load balancing Configuring Capsules to use a load balancer results in a more complex environment and requires additional maintenance. The following additional steps are required for load balancing: You must ensure that all Capsules have the same content views and synchronize all Capsules to the same content view versions You must upgrade each Capsule in sequence You must backup each Capsule that you configure regularly Upgrading Capsule Servers in a load balancing configuration To upgrade Capsule Servers from 6.14 to 6.15, complete the Upgrading Capsule Servers procedure in Upgrading connected Red Hat Satellite to 6.15 . There are no additional steps required for Capsule Servers in a load balancing configuration.

Commands:
Network APIs OpenShift Container Platform 4.16 Reference guide for network APIs Red Hat OpenShift Documentation Team

Commands:
Name: "mysvc", Subsets: [ { Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { Addresses: [{"ip": "10.10.3.3"}], Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ]
type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
// other fields }
type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
// other fields }
type FooStatus struct{ // Represents the observations of a foo's current state. // Known .status.conditions.type are: "Available", "Progressing", and "Degraded" // +patchMergeKey=type // +patchStrategy=merge // +listType=map // +listMapKey=type Conditions []metav1.Condition `json:"conditions,omitempty" patchStrategy:"merge" patchMergeKey:"type" protobuf:"bytes,1,rep,name=conditions"`
// other fields }
Name: "mysvc", Subsets: [ { Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }, { Addresses: [{"ip": "10.10.3.3"}], Ports: [{"name": "a", "port": 93}, {"name": "b", "port": 76}] }, ]
{ Addresses: [{"ip": "10.10.1.1"}, {"ip": "10.10.2.2"}], Ports: [{"name": "a", "port": 8675}, {"name": "b", "port": 309}] }
a: [ 10.10.1.1:8675, 10.10.2.2:8675 ], b: [ 10.10.1.1:309, 10.10.2.2:309 ]
1.8. Uninstalling a Software Collection You can use conventional tools like Yum or PackageKit when uninstalling a Software Collection because Software Collections are fully compatible with the RPM Package Manager. For example, to uninstall all packages and subpackages that are part of a Software Collection named software_collection_1 , run the following command: yum remove software_collection_1\* You can also use the yum remove command to remove the scl utility. For detailed information on Yum and PackageKit usage, see the Red Hat Enterprise Linux 7 System Administrator's Guide , or the Red Hat Enterprise Linux 6 Deployment Guide .

Commands:
B.4. bind B.4.1. RHSA-2010:0975 - Important: bind security update Updated bind packages that fix two security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. 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 Berkeley Internet Name Domain (BIND) is an implementation of the Domain Name System (DNS) protocols. BIND includes a DNS server (named); a resolver library (routines for applications to use when interfacing with DNS); and tools for verifying that the DNS server is operating correctly. CVE-2010-3613 It was discovered that named did not invalidate previously cached RRSIG records when adding an NCACHE record for the same entry to the cache. A remote attacker allowed to send recursive DNS queries to named could use this flaw to crash named. CVE-2010-3614 It was discovered that, in certain cases, named did not properly perform DNSSEC validation of an NS RRset for zones in the middle of a DNSKEY algorithm rollover. This flaw could cause the validator to incorrectly determine that the zone is insecure and not protected by DNSSEC. All BIND users are advised to upgrade to these updated packages, which contain a backported patch to resolve these issues. After installing the update, the BIND daemon (named) will be restarted automatically.

Commands:
B.107. xorg-x11-server B.107.1. RHBA-2011:0340 - xorg-x11-server bug fix update Updated xorg-x11-server packages that fix a bug are now available for Red Hat Enterprise Linux 6. X.Org X11 is an open source implementation of the X Window System. It provides the basic low level functionality upon which full fledged graphical user interfaces such as GNOME and KDE are designed. Bug Fix BZ# 668514 Prior to this update, when the X Window System was unable to detect a monitor and obtain valid extended display identification data (EDID), it set the default resolution limit to 800x600. Consequent to this, users of the "mga" driver for Matrox video cards were unable to select a screen resolution higher than 800x600. This update increases the default limit to 1024x768, allowing users of Matrox video cards to select this resolution as expected. All users of xorg-x11-server are advised to upgrade to these updated packages, which resolve this issue.

Commands:
Chapter 2. Admin REST API Red Hat build of Keycloak comes with a fully functional Admin REST API with all features provided by the Admin Console. To invoke the API you need to obtain an access token with the appropriate permissions. The required permissions are described in the Server Administration Guide . You can obtain a token by enabling authentication for your application using Red Hat build of Keycloak; see the Securing Applications and Services Guide. You can also use direct access grant to obtain an access token. 2.1. Examples of using CURL 2.1.1. Authenticating with a username and password Note The following example assumes that you created the user admin with the password password in the master realm as shown in the Getting Started Guide tutorial. Procedure Obtain an access token for the user in the realm master with username admin and password password : curl \ -d "client_id=admin-cli" \ -d "username=admin" \ -d "password=password" \ -d "grant_type=password" \ "http://localhost:8080/realms/master/protocol/openid-connect/token" Note By default this token expires in 1 minute The result will be a JSON document. Invoke the API you need by extracting the value of the access_token property. Invoke the API by including the value in the Authorization header of requests to the API. The following example shows how to get the details of the master realm: curl \ -H "Authorization: bearer eyJhbGciOiJSUz..." \ "http://localhost:8080/admin/realms/master" 2.1.2. Authenticating with a service account To authenticate against the Admin REST API using a client_id and a client_secret , perform this procedure. Procedure Make sure the client is configured as follows: client_id is a confidential client that belongs to the realm master client_id has Service Accounts Enabled option enabled client_id has a custom "Audience" mapper Included Client Audience: security-admin-console Check that client_id has the role 'admin' assigned in the "Service Account Roles" tab. curl \ -d "client_id=<YOUR_CLIENT_ID>" \ -d "client_secret=<YOUR_CLIENT_SECRET>" \ -d "grant_type=client_credentials" \ "http://localhost:8080/realms/master/protocol/openid-connect/token" 2.2. Additional resources Server Administration Guide API Documentation

Commands:
curl -d "client_id=admin-cli" -d "username=admin" -d "password=password" -d "grant_type=password" "http://localhost:8080/realms/master/protocol/openid-connect/token"
curl -H "Authorization: bearer eyJhbGciOiJSUz..." "http://localhost:8080/admin/realms/master"
curl -d "client_id=<YOUR_CLIENT_ID>" -d "client_secret=<YOUR_CLIENT_SECRET>" -d "grant_type=client_credentials" "http://localhost:8080/realms/master/protocol/openid-connect/token"
probe::ioblock.request Name probe::ioblock.request - Fires whenever making a generic block I/O request. Synopsis Values None Description name - name of the probe point devname - block device name ino - i-node number of the mapped file sector - beginning sector for the entire bio flags - see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block BIO_EOF 2 out-out-bounds error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user pages BIO_EOPNOTSUPP 7 not supported rw - binary trace for read/write request vcnt - bio vector count which represents number of array element (page, offset, length) which make up this I/O request idx - offset into the bio vector array phys_segments - number of segments in this bio after physical address coalescing is performed hw_segments - number of segments after physical and DMA remapping hardware coalescing is performed size - total size in bytes bdev - target block device bdev_contains - points to the device object which contains the partition (when bio structure represents a partition) p_start_sect - points to the start sector of the partition structure of the device Context The process makes block I/O request

Commands:
ioblock.request
Chapter 1. Configuring and deploying a Red Hat OpenStack Platform hyperconverged infrastructure 1.1. Hyperconverged infrastructure overview Red Hat OpenStack Platform (RHOSP) hyperconverged infrastructures (HCI) consist of hyperconverged nodes. In RHOSP HCI, the Compute and Storage services are colocated on these hyperconverged nodes for optimized resource use. You can deploy an overcloud with only hyperconverged nodes, or a mixture of hyperconverged nodes with normal Compute and Red Hat Ceph Storage nodes. Note You must use Red Hat Ceph Storage as the storage provider. Tip Use BlueStore as the back end for HCI deployments to make use of the BlueStore memory handling features. Hyperconverged infrastructures are built using a variation of the deployment process described in Deploying Red Hat Ceph and OpenStack together with director . In this deployment scenario, RHOSP director deploys your cloud environment, which director calls the overcloud, and Red Hat Ceph Storage. You manage and scale the Ceph cluster itself separate from the overcloud configuration. Important Instance HA is not supported on RHOSP HCI environments. To use Instance HA in your RHOSP HCI environment, you must designate a subset of the Compute nodes with the ComputeInstanceHA role to use the Instance HA. Red Hat Ceph Storage services must not be hosted on the Compute nodes that host Instance HA. Red Hat OpenStack Platform 17.1 only supports Red Hat Ceph Storage 6 for new deployments. Red Hat Ceph Storage 5 is not supported in new deployment scenarios. Important All HCI nodes in supported Hyperconverged Infrastructure environments must use the same version of Red Hat Enterprise Linux as the version used by the Red Hat OpenStack Platform controllers. If you wish to use multiple Red Hat Enterprise versions in a hybrid state on HCI nodes in the same Hyperconverged Infrastructure environment, contact the Red Hat Customer Experience and Engagement team to discuss a support exception. For HCI configuration guidance, see Configuration guidance .

Commands:
1.3. Performance Features and Improvements CPU/Kernel NUMA - Non-Uniform Memory Access. See Chapter 9, NUMA for details on NUMA. CFS - Completely Fair Scheduler. A modern class-focused scheduler. RCU - Read Copy Update. Better handling of shared thread data. Up to 160 virtual CPUs (vCPUs). Memory Huge Pages and other optimizations for memory-intensive environments. See Chapter 8, Memory for details. Networking vhost-net - a fast, kernel-based VirtIO solution. SR-IOV - for near-native networking performance levels. Block I/O AIO - Support for a thread to overlap other I/O operations. MSI - PCI bus device interrupt generation. Scatter Gather - An improved I/O mode for data buffer handling. Note For more details on virtualization support, limits, and features, refer to the Red Hat Enterprise Linux 6 Virtualization Getting Started Guide and the following URLs: https://access.redhat.com/certified-hypervisors https://access.redhat.com/articles/rhel-kvm-limits

Commands:
B.3. Checking a Package's Signature If you want to verify that a package has not been corrupted or tampered with, examine only the md5sum by typing the following command at a shell prompt (where <rpm_file> is the file name of the RPM package): The message <rpm_file> : rsa sha1 (md5) pgp md5 OK (specifically the OK part of it) is displayed. This brief message means that the file was not corrupted during download. To see a more verbose message, replace -K with -Kvv in the command. On the other hand, how trustworthy is the developer who created the package? If the package is signed with the developer's GnuPG key , you know that the developer really is who they say they are. An RPM package can be signed using GNU Privacy Guard (or GnuPG), to help you make certain your downloaded package is trustworthy. GnuPG is a tool for secure communication; it is a complete and free replacement for the encryption technology of PGP, an electronic privacy program. With GnuPG, you can authenticate the validity of documents and encrypt/decrypt data to and from other recipients. GnuPG is capable of decrypting and verifying PGP 5. x files as well. During installation, GnuPG is installed by default. That way you can immediately start using GnuPG to verify any packages that you receive from Red Hat. Before doing so, you must first import Red Hat's public key. B.3.1. Importing Keys To verify Red Hat packages, you must import the Red Hat GnuPG key. To do so, execute the following command at a shell prompt: To display a list of all keys installed for RPM verification, execute the command: For the Red Hat key, the output includes: To display details about a specific key, use rpm -qi followed by the output from the command:

Commands:
-K --nosignature <rpm_file>
--import /usr/share/rhn/RPM-GPG-KEY
-qa gpg-pubkey*
gpg-pubkey-db42a60e-37ea5438
-qi gpg-pubkey-db42a60e-37ea5438
8.3. Cloning a Snapshot A clone or a writable snapshot is a new volume, which is created from a particular snapshot. To clone a snapshot, execute the following command. where, clonename: It is the name of the clone, ie, the new volume that will be created. snapname: It is the name of the snapshot that is being cloned. Note Unlike restoring a snapshot, the original snapshot is still retained, after it has been cloned. The snapshot should be in activated state and all the snapshot bricks should be in running state before taking clone. Also the server nodes should be in quorum. This is a space efficient clone therefore both the Clone (new volume) and the snapshot LVM share the same LVM backend. The space consumption of the LVM grow as the new volume (clone) diverge from the snapshot. For example: To check the status of the newly cloned snapshot execute the following command For example: In the example it is observed that clone is in Created state, similar to a newly created volume. This volume should be explicitly started to use this volume.

Commands:
gluster snapshot clone < clonename > < snapname >
gluster snapshot clone clone_vol snap1 snapshot clone: success: Clone clone_vol created successfully
gluster vol info < clonename >
gluster vol info clone_vol Volume Name: clone_vol Type: Distribute Volume ID: cdd59995-9811-4348-8e8d-988720db3ab9 Status: Created Number of Bricks: 1 Transport-type: tcp Bricks: Brick1: 10.00.00.01:/var/run/gluster/snaps/clone_vol/brick1/brick3 Options Reconfigured: performance.readdir-ahead: on
4.6. Online Data Relocation You can move data while the system is in use with the pvmove command. The pvmove command breaks up the data to be moved into sections and creates a temporary mirror to move each section. For more information on the operation of the pvmove command, see the pvmove (8) man page. Note In order to perform a pvmove operation in a cluster, you should ensure that the cmirror package is installed and the cmirrord service is running. The following command moves all allocated space off the physical volume /dev/sdc1 to other free physical volumes in the volume group: The following command moves just the extents of the logical volume MyLV . Since the pvmove command can take a long time to execute, you may want to run the command in the background to avoid display of progress updates in the foreground. The following command moves all extents allocated to the physical volume /dev/sdc1 over to /dev/sdf1 in the background. The following command reports the progress of the pvmove command as a percentage at five second intervals.

Commands:
pvmove /dev/sdc1
pvmove -n MyLV /dev/sdc1
pvmove -b /dev/sdc1 /dev/sdf1
pvmove -i5 /dev/sdd1
2. Related Documentation For more information about using Red Hat Enterprise Linux, refer to the following resources: Red Hat Enterprise Linux Installation Guide - Provides information regarding installation of Red Hat Enterprise Linux. Red Hat Enterprise Linux Introduction to System Administration - Provides introductory information for new Red Hat Enterprise Linux system administrators. Red Hat Enterprise Linux System Administration Guide - Provides more detailed information about configuring Red Hat Enterprise Linux to suit your particular needs as a user. Red Hat Enterprise Linux Reference Guide - Provides detailed information suited for more experienced users to reference when needed, as opposed to step-by-step instructions. Red Hat Enterprise Linux Security Guide - Details the planning and the tools involved in creating a secured computing environment for the data center, workplace, and home. For more information about Red Hat Cluster Suite for Red Hat Enterprise Linux, refer to the following resources: Red Hat Cluster Suite Overview - Provides a high level overview of the Red Hat Cluster Suite. Configuring and Managing a Red Hat Cluster - Provides information about installing, configuring and managing Red Hat Cluster components. LVM Administrator's Guide: Configuration and Administration - Provides a description of the Logical Volume Manager (LVM), including information on running LVM in a clustered environment. Using GNBD with Global File System - Provides an overview on using Global Network Block Device (GNBD) with Red Hat GFS. Using Device-Mapper Multipath - Provides information about using the Device-Mapper Multipath feature of Red Hat Enterprise Linux. Linux Virtual Server Administration - Provides information on configuring high-performance systems and services with the Linux Virtual Server (LVS). Red Hat Cluster Suite Release Notes - Provides information about the current release of Red Hat Cluster Suite. Red Hat Cluster Suite documentation and other Red Hat documents are available in HTML and PDF versions online at the following location: http://www.redhat.com/docs

Commands: