mtpti5iD/redhat-docs_dataset huggingface dataset:
A. Technology Previews Technology Preview features are currently not supported under Red Hat Enterprise Linux 4.9 subscription services, may not be functionally complete, and are generally not suitable for production use. However, these features are included as a customer convenience and to provide the feature with wider exposure. Customers may find these features useful in a non-production environment. Customers are also free to provide feedback and functionality suggestions for a technology preview feature before it becomes fully supported. Erratas will be provided for high-severity security issues. During the development of a technology preview feature, additional components may become available to the public for testing. It is the intention of Red Hat to fully support technology preview features in a future release. For more information on the scope of Technology Previews in Red Hat Enterprise Linux, please view the Technology Preview Features Support Scope page on the Red Hat website. OpenOffice 2.0 OpenOffice 2.0 is now included in this release as a Technology Preview. This suite features several improvements, including ODF and PDF functionalities, support for digital signatures and greater compatibility with open suites in terms of format and interface. In addition to this, the OpenOffice 2.0 spreadsheet has enhanced pivot table support, and can now handle up to 65,000 rows. For more information about OpenOffice 2.0 , please refer to http://www.openoffice.org/dev_docs/features/2.0/index.html .

Commands:
Chapter 1. Red Hat Enterprise Linux 6.9 International Languages Red Hat Enterprise Linux 6.9 supports installation of multiple languages and changing of languages based on your requirements. The following languages are supported in Red Hat Enterprise Linux 6.9: East Asian Languages - Japanese, Korean, Simplified Chinese, and Traditional Chinese European Languages - English, German, Spanish, French, Portuguese Brazilian, and Russian, The table below summarizes the currently supported languages, their locales, default fonts installed and packages required for some of the supported languages Table 1.1. Red Hat Enterprise Linux 6 International Languages Territory Language Locale Fonts Package Names China Simplified Chinese zh_CN.UTF-8 AR PL (ShanHeiSun and Zenkai) Uni fonts-chinese, scim-pinyin, scim-tables Japan Japanese ja_JP.UTF-8 Sazanami (Gothic and Mincho) fonts-japanese, scim-anthy Korea Hangul ko_KR.UTF-8 Baekmuk (Batang, Dotum, Gulim, Headline) fonts-korean, scim-hangul Taiwan Traditional Chinese zh_TW.UTF-8 AR PL (ShanHeiSun and Zenkai) Uni fonts-chinese, scim-chewing, scim-tables Brazil Portuguese pt_BR.UTF-8 standard latin fonts France French ft_FR.UTF-8 standard latin fonts Germany German de_DE.UTF-8 standard latin fonts Italy Italy it_IT.UTF-8 standard latin fonts Russia Russian ru_RU.UTF-8 Cyrillic dejavu-lgc-sans-fonts, dejavu-lgc-sans-mono-fonts, dejavu-lgc-serif-fonts, xorg-x11-fonts-cyrillic Spain Spanish es_ES.UTF-8 standard latin fonts

Commands:
Chapter 12. Database links and access control evaluation When a user binds to a server containing a database link, the database link sends the user's identity to the remote server. You can evaluate access control on the remote server. You can evaluate the LDAP operation on the remote server by using the original identity of the client application passed by using the proxied authorization control. Note You must have the correct access controls on the subtree present on the remote server for the operations to succeed on the remote server. You can add usual access controls to the remote server with the following restrictions: You cannot use all types of access control. For example, role-based or filter-based ACIs need access to the user entry, because the data is accessed through database links. Remote server views the client application in the same IP address and DNS domain as the database link. Because the original domain of the client is lost during chaining, all access controls based on the IP address or DNS domain of the client cannot work. Note Directory Server supports both IPv4 and IPv6 IP addresses. The following restrictions apply to the ACIs used with database links: You must locate ACIs with any groups they use. For the dynamic groups, all users in the group are located with the ACI and the group. For the static group, user links to remote server. You must locate ACIs with any role definitions they use and with any users who intend to use these roles. ACIs that link to values of a user's entry must work when the user is remote. Though evaluation of access controls is always done on the remote server, access controls can also be evaluated on both the server containing the database link and the remote server. This poses the following several limitations: When you evaluate the access control, for example, on the server containing the database link and when the entry is located on a remote server, the contents of user entries are not necessarily available. Note For performance reasons, clients cannot perform remote inquiries and evaluate access controls. When you perform modify operation, the database link does not have access to the full entry stored on the remote server and necessarily does not have access to the entries being modified by the client application. When you perform delete operation, the database link is only aware of the entry's DN . If an access control specifies a particular attribute, then delete operation must fail when conducted through a database link. Note By default, evaluation of access controls on the server containing the database link is not allowed. You can override this default setting by using the nsCheckLocalACI attribute in the cn=database_link , cn=chaining database , cn=plugins , and cn=config entry. However, evaluating access controls on the server containing the database link is not recommended except for cascading chaining.

Commands:
function::proc_mem_string Name function::proc_mem_string - Human readable string of current proc memory usage Synopsis Arguments None Description Returns a human readable string showing the size, rss, shr, txt and data of the memory used by the current process. For example " size: 301m, rss: 11m, shr: 8m, txt: 52k, data: 2248k " .

Commands:
function proc_mem_string:string()
1.2. About Authentication Authentication refers to identifying a subject and verifying the authenticity of the identification. The most common authentication mechanism is a username and password combination. Other common authentication mechanisms use shared keys, smart cards, or fingerprints. The outcome of a successful authentication is referred to as a principal, in terms of Java Enterprise Edition declarative security. JBoss EAP 6 uses a pluggable system of authentication modules to provide flexibility and integration with the authentication systems you already use in your organization. Each security domain may contain one or more configured authentication modules. Each module includes additional configuration parameters to customize its behavior. The easiest way to configure the authentication subsystem is within the web-based management console. Authentication is not the same as authorization, although they are often linked. Many of the included authentication modules can also handle authorization.

Commands:
B.96.2. RHSA-2010:0969 - Moderate: thunderbird security update An updated thunderbird package that fixes several security issues is now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Mozilla Thunderbird is a standalone mail and newsgroup client. CVE-2010-3776 , CVE-2010-3777 Several flaws were found in the processing of malformed HTML content. Malicious HTML content could cause Thunderbird to crash or, potentially, execute arbitrary code with the privileges of the user running Thunderbird. Note Note that JavaScript support is disabled in Thunderbird for mail messages. The above issues are believed to not be exploitable without JavaScript. CVE-2010-3768 This update adds support for the Sanitiser for OpenType (OTS) library to Thunderbird. This library helps prevent potential exploits in malformed OpenType fonts by verifying the font file prior to use. All Thunderbird users should upgrade to this updated package, which resolves these issues. All running instances of Thunderbird must be restarted for the update to take effect.

Commands:
B.101. vsftpd B.101.1. RHSA-2011:0337 - Important: vsftpd security update An updated vsftpd package that fixes one security issue is now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. vsftpd (Very Secure File Transfer Protocol (FTP) daemon) is a secure FTP server for Linux, UNIX, and similar operating systems. CVE-2011-0762 A flaw was discovered in the way vsftpd processed file name patterns. An FTP user could use this flaw to cause the vsftpd process to use an excessive amount of CPU time, when processing a request with a specially-crafted file name pattern. All vsftpd users should upgrade to this updated package, which contains a backported patch to correct this issue. The vsftpd daemon must be restarted for this update to take effect.

Commands:
Chapter 1. Overview Read this document to understand how to create, configure, and allocate storage to core services or hosted applications in Red Hat OpenShift Data Foundation. Chapter 2, Storage classes shows you how to create custom storage classes. Chapter 3, Block pools provides you with information on how to create, update and delete block pools. Chapter 4, Configure storage for OpenShift Container Platform services shows you how to use OpenShift Data Foundation for core OpenShift Container Platform services. Chapter 5, Backing OpenShift Container Platform applications with OpenShift Data Foundation provides information about how to configure OpenShift Container Platform applications to use OpenShift Data Foundation. Adding file and object storage to an existing external OpenShift Data Foundation cluster Chapter 7, How to use dedicated worker nodes for Red Hat OpenShift Data Foundation provides information about how to use dedicated worker nodes for Red Hat OpenShift Data Foundation. Chapter 8, Managing Persistent Volume Claims provides information about managing Persistent Volume Claim requests, and automating the fulfillment of those requests. Chapter 9, Volume Snapshots shows you how to create, restore, and delete volume snapshots. Chapter 10, Volume cloning shows you how to create volume clones. Chapter 11, Managing container storage interface (CSI) component placements provides information about setting tolerations to bring up container storage interface component on the nodes.

Commands:
4.238. procps 4.238.1. RHBA-2011:1554 - procps bug fix update An updated procps package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The procps package contains a set of system utilities that provide system information using the /proc file system. The procps package includes free, pgrep, pkill, pmap, ps, pwdx, skill, slabtop, snice, sysctl, tload, top, uptime, vmstat, w and watch. Bug Fixes BZ# 692397 There was a typo in the ps(1) manual page which caused the layout of the page to break. The typo has been fixed and the ps(1) manual page is now displayed correctly. BZ# 690078 Incorrectly declared variables may have led to a memory leak or caused the pmap, ps and vmstat utilities to misbehave. The variables are now nullified and declared in the correct place, fixing the problem. BZ# 697935 Prior to this update, the sysctl utility did not accept partial keys to display all the key pairs within a certain namespace of the /proc file system. The following error message appeared when running the "sysctl net.core" command: "Invalid argument" reading key "net.core" With this update, the sysctl utility accepts the partial keys and all the keys with the specified prefix are now displayed. BZ# 709684 Previously, the top utility displayed incorrect values in the SWAP field due to the values of the per-process swap being incorrectly calculated as a difference between virtual and physical memory used by a task. The /proc file system provided by kernel is now the main source of the swap information. BZ# 701710 Previously, the vmstat utility displayed incorrect values of the free page count on 8TB SGI (Silicon Graphics) systems. The vmstat utility has been modified to display the correct free page count. All users of procps are advised to upgrade to this updated package, which fixes these bugs.

Commands:
E.5.2. File Names and Blocklists When typing commands to GRUB that reference a file, such as a menu list, it is necessary to specify an absolute file path immediately after the device and partition numbers. The following illustrates the structure of such a command: ( <device-type><device-number> , <partition-number> ) </path/to/file> In this example, replace <device-type> with hd , fd , or nd . Replace <device-number> with the integer for the device. Replace </path/to/file> with an absolute path relative to the top-level of the device. It is also possible to specify files to GRUB that do not actually appear in the file system, such as a chain loader that appears in the first few blocks of a partition. To load such files, provide a blocklist that specifies block by block where the file is located in the partition. Since a file is often comprised of several different sets of blocks, blocklists use a special syntax. Each block containing the file is specified by an offset number of blocks, followed by the number of blocks from that offset point. Block offsets are listed sequentially in a comma-delimited list. The following is a sample blocklist: This sample blocklist specifies a file that starts at the first block on the partition and uses blocks 0 through 49, 100 through 124, and 200. Knowing how to write blocklists is useful when using GRUB to load operating systems which require chain loading. It is possible to leave off the offset number of blocks if starting at block 0. As an example, the chain loading file in the first partition of the first hard drive would have the following name: The following shows the chainloader command with a similar blocklist designation at the GRUB command line after setting the correct device and partition as root:

Commands:
0+50,100+25,200+1
(hd0,0)+1
chainloader +1
Part I. REST OpenApi Component Since Camel 3.1 Only producer is supported The REST OpenApi* configures rest producers from OpenApi (Open API) specification document and delegates to a component implementing the RestProducerFactory interface. Currently known working components are: http netty-http undertow Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-rest-openapi</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-rest-openapi</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
9.3. Audit Logging API If you want to build a custom appender for command logging that will have access to java.util.logging.LogRecord s to the "AUDIT_LOG" context, the handler will receive a message that is an instance of LogRecord . This object will contain a parameter of type org.teiid.logging.AuditMessage . The relevant Red Hat JBoss Data Virtualization classes are defined in the teiid-api-[versionNumber].jar . AuditMessages are logged at the DEBUG level. An example follows.

Commands:
package org.something; import java.util.logging.Handler; import java.util.logging.LogRecord; public class AuditHandler extends Handler { @Override public void publish(LogRecord record) { AuditMessage msg = (AuditMessage)record.getParameters()[0]; //log to a database, trigger an email, etc. } @Override public void flush() { } @Override public void close() throws SecurityException { } }
Chapter 15. Storage The multipath utility can now save data between prioritizer calls This feature has been implemented in the asymmetric logical unit access (ALUA) prioritizer, and reduces the number of commands sent to the target array. As a result, target arrays are no longer overloaded with commands if there is a large number of paths. (BZ#1081395) Asynchronous checkers can use the multipath checker_timeout option Asynchronous checkers now use the checker_timeout option in the multipath.conf file to determine when to stop waiting for a response from the array and fail the non-responsive path. This behavior for asynchronous checkers can be configured in the same way as for synchronous checkers. (BZ#1153704) nfsidmap -d option added The nfsidmap -d option has been added to display the system's effective NFSv4 domain name on stdout. (BZ#948680) Configurable connection timeout for mounted CIFS shares Idling CIFS clients send an echo call every 60 seconds. The echo interval is hard-coded, and is used to calculate the timeout value for an unreachable server. This timeout value is usually set to (2 * echo interval) + 17 seconds. With this feature, users can change the echo interval setting, which enables them to change the timeout interval for unresponsive servers. To change the echo interval, use the echo_interval=n mount option, where n is the echo interval in seconds. (BZ#1234960) Support for device-mapper statistics facility ( dmstats ) The Red Hat Enterprise Linux 6.8 release supports a device-mapper statistics facility, the dmstats program. The dmstats program displays and manages I/O statistics for user-defined regions of devices that use the device-mapper driver. The dmstats program provides a similar functionality to the iostats program, but at levels of finer granularity than a whole device. For information on the dmstats program, see the dmstats (8) man page. (BZ# 1267664 ) Support for raw format mode in multipathd formatted output commands The multipathd formatted ouput commands now offer a raw format mode that removes the headers and additional padding between fields. Support for additional format wildcards has been added as well. Raw format mode makes it easer to collect and parse information about multipath devices, particularly for use in scripting. For information on raw format mode, see the DM Multipath Guide. (BZ# 1145442 )

Commands:
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 Do not enable Instance HA when you deploy a Red Hat OpenStack Platform (RHOSP) HCI environment. Contact your Red Hat representative if you want to use Instance HA with hyperconverged RHOSP deployments with Red Hat Ceph Storage. For HCI configuration guidance, see Configuration guidance .

Commands:
Release notes Red Hat Satellite 6.16 New features, deprecated and removed features, Technology Previews, known issues, and bug fixes Red Hat Satellite Documentation Team satellite-doc-list@redhat.com

Commands:
SELECT rolname,rolpassword FROM pg_authid WHERE rolpassword != '';
hammer capsule content verify-checksum --id My_Capsule_ID
Unable to load certs Neither PUB key nor PRIV key
Unable to load certs Neither PUB key nor PRIV key
Chapter 13. Topology View Use the Topology View to view node type, node health, and specific details about each node if you already have a mesh topology deployed. To access the topology viewer from the automation controller UI, you must have System Administrator permissions. For more information about automation mesh on a VM-based installation, see the Automation mesh for VM environments . For more information about automation mesh on an operator-based installation, see the Automation mesh for managed cloud or operator environments . 13.1. Accessing the topology viewer Use the following procedure to access the topology viewer from the automation controller UI. Procedure From the navigation panel, select Automation Execution Infrastructure Topology View . The Topology View opens and displays a graphical representation of how each receptor node links together. To adjust the zoom levels, or manipulate the graphic views, use the control icons: zoom-in ( ), zoom-out ( ), expand ( ), and reset ( ) on the toolbar. You can also click and drag to pan around; and scroll using your mouse or trackpad to zoom. The fit-to-screen feature automatically scales the graphic to fit on the screen and repositions it in the center. It is particularly useful when you want to see a large mesh in its entirety. To reset the view to its default view, click the Reset view ( ) icon. Refer to the Legend to identify the type of nodes that are represented. For VM-based installations, see Control and execution planes . For operator-based installations, see Control and execution planes for more information about each type of node. The Legend shows the node status <node_statuses> by color, which is indicative of the health of the node. An Error status in the Legend includes the Unavailable state (as displayed in the Instances list view) plus any future error conditions encountered in later versions of automation controller. The following link statuses are also shown in the Legend: Established : This is a link state that indicates a peer connection between nodes that are either ready, unavailable, or disabled. Adding : This is a link state indicating a peer connection between nodes that were selected to be added to the mesh topology. Removing : This is a link state indicating a peer connection between nodes that were selected to be removed from the topology. Hover over a node and the connectors highlight to show its immediate connected nodes (peers) or click a node to retrieve details about it, such as its hostname, node type, and status. Click the link for instance hostname from the details displayed to be redirected to its Details page that provides more information about that node, most notably for information about an Error status, as in the following example. You can use the Details page to remove the instance, run a health check on the instance on an as-needed basis, or unassign jobs from the instance. By default, jobs can be assigned to each node. However, you can disable it to exclude the node from having any jobs running on it. Additional resources For more information about creating new nodes and scaling the mesh, see Managing capacity with Instances .

Commands: