mtpti5iD/redhat-docs_dataset huggingface dataset:
1.2. JBoss Data Virtualization and JDBC Red Hat JBoss Data Virtualization provides an API that builds on Java Database Connectivity (JDBC), allowing client applications to issue SQL queries against deployed virtual databases (VDBs). Note Your client applications must use Java JDK 1.6 or higher to connect to Red Hat JBoss Data Virtualization VDBs. Note The JBoss Data Virtualization JDBC API is compatible with the JDBC 4.0 specification but does not fully support all methods. Advanced features, such as updatable result sets and SQL3 data types are also not supported. See Section A.3, "Unsupported Classes and Methods in java.sql" and Section A.4, "Unsupported Classes and Methods in javax.sql" for more information about unsupported classes and methods. Important Support for earlier versions of JDK has been deprecated.

Commands:
7.7. Downgrading SSSD When downgrading - either downgrading the version of SSSD or downgrading the operating system itself - then the existing SSSD cache needs to be removed. If the cache is not removed, then SSSD process is dead but a PID file remains. The SSSD logs show that it cannot connect to any of its associated domains because the cache version is unrecognized. Users are then no longer recognized and are unable to authenticate to domain services and hosts. After downgrading the SSSD version: Delete the existing cache database files. Restart the SSSD process.

Commands:
(Wed Nov 28 21:25:50 2012) [sssd] [sysdb_domain_init_internal] (0x0010): Unknown DB version [0.14], expected [0.10] for domain AD!
rm -rf /var/lib/sss/db/*
systemctl restart sssd.service
Chapter 20. Internationalization 20.1. Red Hat Enterprise Linux 7 International Languages Red Hat Enterprise Linux 7 supports the installation of multiple languages and the changing of languages based on your requirements. The following languages are supported in Red Hat Enterprise Linux 7: East Asian Languages - Japanese, Korean, Simplified Chinese, and Traditional Chinese; European Languages - English, German, Spanish, French, Italian, Portuguese Brazilian, and Russian. Indic Languages - Assamese, Bengali, Gujarati, Hindi, Kannada, Malayalam, Marathi, Odia, Punjabi, Tamil, and Telugu. The table below summarizes the currently supported languages, their locales, default fonts installed, and packages required for some of the supported languages. For more information on font configuration, see Desktop Migration and Administration Guide . Table 20.1. Language Support Matrix Territory Language Locale Default Font (Font Package) Input Methods Brazil Portuguese pt_BR.UTF-8 DejaVu Sans (dejavu-sans-fonts) France French fr_FR.UTF-8 DejaVu Sans (dejavu-sans-fonts) Germany German de_DE.UTF-8 DejaVu Sans (dejavu-sans-fonts) Italy Italian it_IT.UTF-8 DejaVu Sans (dejavu-sans-fonts) Russia Russian ru_RU.UTF-8 DejaVu Sans (dejavu-sans-fonts) Spain Spanish es_ES.UTF-8 DejaVu Sans (dejavu-sans-fonts) USA English en_US.UTF-8 DejaVu Sans (dejavu-sans-fonts) China Simplified Chinese zh_CN.UTF-8 WenQuanYi Zen Hei Sharp (wqy-zenhei-fonts) ibus-libpinyin, ibus-table-chinese Japan Japanese ja_JP.UTF-8 VL PGothic (vlgothic-p-fonts) ibus-kkc Korea Korean ko_KR.UTF-8 NanumGothic (nhn-nanum-gothic-fonts) ibus-hangul Taiwan Traditional Chinese zh_TW.UTF-8 AR PL UMing TW (cjkuni-uming-fonts) ibus-chewing, ibus-table-chinese India Assamese as_IN.UTF-8 Lohit Assamese (lohit-assamese-fonts) ibus-m17n, m17n-db, m17n-contrib Bengali bn_IN.UTF-8 Lohit Bengali (lohit-bengali-fonts) ibus-m17n, m17n-db, m17n-contrib Gujarati gu_IN.UTF-8 Lohit Gujarati (lohit-gujarati-fonts) ibus-m17n, m17n-db, m17n-contrib Hindi hi_IN.UTF-8 Lohit Hindi (lohit-devanagari-fonts) ibus-m17n, m17n-db, m17n-contrib Kannada kn_IN.UTF-8 Lohit Kannada (lohit-kannada-fonts) ibus-m17n, m17n-db, m17n-contrib Malayalam ml_IN.UTF-8 Meera (smc-meera-fonts) ibus-m17n, m17n-db, m17n-contrib Marathi mr_IN.UTF-8 Lohit Marathi (lohit-marathi-fonts) ibus-m17n, m17n-db, m17n-contrib Odia or_IN.UTF-8 Lohit Oriya (lohit-oriya-fonts) ibus-m17n, m17n-db, m17n-contrib Punjabi pa_IN.UTF-8 Lohit Punjabi (lohit-punjabi-fonts) ibus-m17n, m17n-db, m17n-contrib Tamil ta_IN.UTF-8 Lohit Tamil (lohit-tamil-fonts) ibus-m17n, m17n-db, m17n-contrib Telugu te_IN.UTF-8 Lohit Telugu (lohit-telugu-fonts) ibus-m17n, m17n-db, m17n-contrib

Commands:
9.7. Large Objects (LOBs) Large Objects (LOBs) consist of data. The three main large object runtime data types used by JBoss are: Binary (BLOB) Contains multimedia objects such as images and audio. Character (CLOB) Contains ASCII characters. Extensible Markup Language (XML) Contains textual data. LOBs and JBoss The JBoss Data Services Connector API returns a reference to the LOB if allowed by the JBoss Data Services server. The JBoss Data Services server or JDBC driver can then access the data via a stream rather than retrieving the data all at once. This is useful for several reasons: Reduces memory usage when returning the result set to the user. Improves performance by passing less data in the result set. Enables access to LOBs when required rather than assuming that users will always use the LOB data. Enables handling of arbitrarily large data values within a fixed JBoss Data Services memory usage. These benefits are achieved if the Connector itself does not materialize an entire LOB all at once. For example, the JDBC API supports a streaming interface for BLOB and CLOB data. Source LOB values are typically accessed by reference, rather than having the value copied to a temporary location. Care must be taken to ensure that source LOBs are returned in a memory-safe manner. LOBs are broken into pieces when being created and streamed. The size of each piece when fetched by the client can be configured. Cached lobs will be copied rather than relying on the reference to the source lob. Temporary lobs created by Teiid will be cleaned up when the result set or statement is closed. To rely on implicit garbage collection based cleanup instead of statement close, the Teiid session variable clean_lobs_onclose can be set to false (by issuing the query "SELECT teiid_session_set('clean_lobs_onclose', false)" - which can be done for example via the new connection sql in the datasource definition). This can be used for local client scenarios that relied on the implicit behavior, such as Designer generated REST VDBs.

Commands:
3.9. Suspending Activity on a GFS2 File System You can suspend write activity to a file system by using the dmsetup suspend command. Suspending write activity allows hardware-based device snapshots to be used to capture the file system in a consistent state. The dmsetup resume command ends the suspension. Usage Start Suspension End Suspension MountPoint Specifies the file system. Examples This example suspends writes to file system /mygfs2 . This example ends suspension of writes to file system /mygfs2 .

Commands:
dmsetup suspend MountPoint
dmsetup resume MountPoint
dmsetup suspend /mygfs2
dmsetup resume /mygfs2
19.4. Virtual Machine Graphical Console This window displays a guest's graphical console. Guests can use several different protocols to export their graphical frame buffers: virt-manager supports VNC and SPICE . If your virtual machine is set to require authentication, the Virtual Machine graphical console prompts you for a password before the display appears. Figure 19.9. Graphical console window Note VNC is considered insecure by many security experts, however, several changes have been made to enable the secure usage of VNC for virtualization on Red Hat enterprise Linux. The guest machines only listen to the local host's loopback address ( 127.0.0.1 ). This ensures only those with shell privileges on the host can access virt-manager and the virtual machine through VNC. Although virt-manager is configured to listen to other public network interfaces and alternative methods can be configured, it is not recommended. Remote administration can be performed by tunneling over SSH which encrypts the traffic. Although VNC can be configured to access remotely without tunneling over SSH, for security reasons, it is not recommended. To remotely administer the guest follow the instructions in: Chapter 18, Remote Management of Guests . TLS can provide enterprise level security for managing guest and host systems. Your local desktop can intercept key combinations (for example, Ctrl+Alt+F1) to prevent them from being sent to the guest machine. You can use the Send key menu option to send these sequences. From the guest machine window, click the Send key menu and select the key sequence to send. In addition, from this menu you can also capture the screen output. SPICE is an alternative to VNC available for Red Hat Enterprise Linux.

Commands:
Chapter 10. Removing Windows nodes You can remove a Windows node by deleting its host Windows machine. 10.1. Deleting a specific machine You can delete a specific machine. Important Do not delete a control plane machine unless your cluster uses a control plane machine set. Prerequisites Install an OpenShift Container Platform cluster. Install the OpenShift CLI ( oc ). Log in to oc as a user with cluster-admin permission. Procedure View the machines that are in the cluster by running the following command: USD oc get machine -n openshift-machine-api The command output contains a list of machines in the <clusterid>-<role>-<cloud_region> format. Identify the machine that you want to delete. Delete the machine by running the following command: USD oc delete machine <machine> -n openshift-machine-api Important By default, the machine controller tries to drain the node that is backed by the machine until it succeeds. In some situations, such as with a misconfigured pod disruption budget, the drain operation might not be able to succeed. If the drain operation fails, the machine controller cannot proceed removing the machine. You can skip draining the node by annotating machine.openshift.io/exclude-node-draining in a specific machine. If the machine that you delete belongs to a machine set, a new machine is immediately created to satisfy the specified number of replicas.

Commands:
oc get machine -n openshift-machine-api
oc delete machine <machine> -n openshift-machine-api
Chapter 4. cxf 4.1. cxf:list-busses 4.1.1. Description Lists all CXF Busses. 4.1.2. Syntax cxf:list-busses [options] 4.1.3. Options Name Description --help Display this help message --no-format Disable table rendered output 4.2. cxf:list-endpoints 4.2.1. Description Lists all CXF Endpoints on a Bus. 4.2.2. Syntax cxf:list-endpoints [options] [bus] 4.2.3. Arguments Name Description bus The CXF bus name where to look for the Endpoints 4.2.4. Options Name Description --help Display this help message -f, --fulladdress Display full address of an endpoint --no-format Disable table rendered output 4.3. cxf:start-endpoint 4.3.1. Description Starts a CXF Endpoint on a Bus. 4.3.2. Syntax cxf:start-endpoint [options] bus endpoint 4.3.3. Arguments Name Description bus The CXF bus name where to look for the Endpoint endpoint The Endpoint name to start 4.3.4. Options Name Description --help Display this help message 4.4. cxf:stop-endpoint 4.4.1. Description Stops a CXF Endpoint on a Bus. 4.4.2. Syntax cxf:stop-endpoint [options] bus endpoint 4.4.3. Arguments Name Description bus The CXF bus name where to look for the Endpoint endpoint The Endpoint name to stop 4.4.4. Options Name Description --help Display this help message

Commands:
3.3. build-id Unique Identification of Binaries Each executable or shared library built with Red Hat Enterprise Linux Server 6 or later is assigned a unique identification 160-bit SHA-1 string, generated as a checksum of selected parts of the binary. This allows two builds of the same program on the same host to always produce consistent build-ids and binary content. Display the build-id of a binary with the following command: Unique identificators of binaries are useful in cases such as analysing core files, documented Section 4.2.1, "Installing Debuginfo Packages for Core Files Analysis" .

Commands:
eu-readelf -n /bin/bash [...] Note section [ 3] '.note.gnu.build-id' of 36 bytes at offset 0x274: Owner Data size Type GNU 20 GNU_BUILD_ID Build ID: efdd0b5e69b0742fa5e5bad0771df4d1df2459d1
10.8.2. The Secure Web Server Virtual Host By default, the Apache HTTP Server is configured as both a non-secure and a secure server. Both the non-secure and secure servers use the same IP address and hostname, but listen on different ports: 80 and 443 respectively. This enables both non-secure and secure communications to take place simultaneously. One aspect of SSL enhanced HTTP transmissions is that they are more resource intensive than the standard HTTP protocol, so a secure server cannot serve as many pages per second. For this reason, it is often a good idea to minimize the information available from the secure server, especially on a high traffic website. Important Do not use name-based virtual hosts in conjunction with a secure Web server as the SSL handshake occurs before the HTTP request identifies the appropriate name-based virtual host. Name-based virtual hosts only work with the non-secure Web server. The configuration directives for the secure server are contained within virtual host tags in the /etc/httpd/conf.d/ssl.conf file. By default, both the secure and the non-secure Web servers share the same DocumentRoot . It is recommended that a different DocumentRoot be made available for the secure Web server. To stop the non-secure Web server from accepting connections, comment out the line in httpd.conf which reads Listen 80 by placing a hash mark ( # ) at the beginning of the line. When finished, the line looks like the following example: For more information on configuring an SSL enhanced Web server, refer to the chapter titled Apache HTTP Secure Server Configuration in the System Administrators Guide . For advanced configuration tips, refer to the Apache Software Foundation documentation available online at the following URLs: http://httpd.apache.org/docs-2.0/ssl/ http://httpd.apache.org/docs-2.0/vhosts/

Commands:
#Listen 80
8.6. Additional Resources For more information on how to manage software packages on Red Hat Enterprise Linux, see the resources listed below. Installed Documentation yum (8) - The manual page for the yum command-line utility provides a complete list of supported options and commands. yumdb (8) - The manual page for the yumdb command-line utility documents how to use this tool to query and, if necessary, alter the yum database. yum.conf (5) - The manual page named yum.conf documents available yum configuration options. yum-utils (1) - The manual page named yum-utils lists and briefly describes additional utilities for managing yum configuration, manipulating repositories, and working with yum database. Online Resources Yum Guides - The Yum Guides page on the project home page provides links to further documentation. Red Hat Access Labs - The Red Hat Access Labs includes a " Yum Repository Configuration Helper " . See Also Chapter 4, Gaining Privileges documents how to gain administrative privileges by using the su and sudo commands. Appendix B, RPM describes the RPM Package Manager ( RPM ), the packaging system used by Red Hat Enterprise Linux.

Commands:
2. Related Documentation For more information about using Red Hat Enterprise Linux, see the following resources: Installation Guide - Documents relevant information regarding the installation of Red Hat Enterprise Linux 6. Deployment Guide - Documents relevant information regarding the deployment, configuration and administration of Red Hat Enterprise Linux 6. Storage Administration Guide - Provides instructions on how to effectively manage storage devices and file systems on Red Hat Enterprise Linux 6. For more information about the High Availability Add-On and the Resilient Storage Add-On for Red Hat Enterprise Linux 6, see the following resources: High Availability Add-On Overview - Provides a high-level overview of the Red Hat High Availability Add-On. Cluster Administration - Provides information about installing, configuring and managing the High Availability Add-On. Logical Volume Manager Administration - Provides a description of the Logical Volume Manager (LVM), including information on running LVM in a clustered environment. DM Multipath - Provides information about using the Device-Mapper Multipath feature of Red Hat Enterprise Linux. Load Balancer Administration - Provides information on configuring high-performance systems and services with the Load Balancer Add-On, a set of integrated software components that provide Linux Virtual Servers (LVS) for balancing IP load across a set of real servers. Release Notes - Provides information about the current release of Red Hat products. Red Hat documents are available in HTML, PDF, and RPM versions on the Red Hat Enterprise Linux Documentation CD and online at https://access.redhat.com/site/documentation/ .

Commands:
Chapter 6. Summarizing cluster specifications 6.1. Summarizing cluster specifications by using a cluster version object You can obtain a summary of OpenShift Container Platform cluster specifications by querying the clusterversion resource. Prerequisites You have access to the cluster as a user with the cluster-admin role. You have installed the OpenShift CLI ( oc ). Procedure Query cluster version, availability, uptime, and general status: USD oc get clusterversion Example output NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.8 True False 8h Cluster version is 4.13.8 Obtain a detailed summary of cluster specifications, update availability, and update history: USD oc describe clusterversion Example output Name: version Namespace: Labels: <none> Annotations: <none> API Version: config.openshift.io/v1 Kind: ClusterVersion # ... Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce URL: https://access.redhat.com/errata/RHSA-2023:4456 Version: 4.13.8 History: Completion Time: 2023-08-17T13:20:21Z Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce Started Time: 2023-08-17T12:59:45Z State: Completed Verified: false Version: 4.13.8 # ...

Commands:
oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.13.8 True False 8h Cluster version is 4.13.8
oc describe clusterversion
Name: version Namespace: Labels: <none> Annotations: <none> API Version: config.openshift.io/v1 Kind: ClusterVersion Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce URL: https://access.redhat.com/errata/RHSA-2023:4456 Version: 4.13.8 History: Completion Time: 2023-08-17T13:20:21Z Image: quay.io/openshift-release-dev/ocp-release@sha256:a956488d295fe5a59c8663a4d9992b9b5d0950f510a7387dbbfb8d20fc5970ce Started Time: 2023-08-17T12:59:45Z State: Completed Verified: false Version: 4.13.8
12.7. Detaching Virtual Machines from a Virtual Machine Pool You can detach virtual machines from a virtual machine pool. Detaching a virtual machine removes it from the pool to become an independent virtual machine. Detaching Virtual Machines from a Virtual Machine Pool Click Compute Pools . Click the pool's name to open the details view. Click the Virtual Machines tab to list the virtual machines in the pool. Ensure the virtual machine has a status of Down ; you cannot detach a running virtual machine. Select one or more virtual machines and click Detach . Click OK . Note The virtual machine still exists in the environment and can be viewed and accessed from Compute Virtual Machines . Note that the icon changes to denote that the detached virtual machine is an independent virtual machine.

Commands:
9.3. JSON Representation of a Data Center Example 9.2. A JSON representation of a data center

Commands:
{ "data_center" : [ { "local" : "false", "storage_format" : "v3", "version" : { "major" : "4", "minor" : "0" }, "supported_versions" : { "version" : [ { "major" : "4", "minor" : "0" } ] }, "status" : { "state" : "up" }, "mac_pool": { "href": "/ovirt-engine/api/macpools/00000000-0000-0000-0000-000000000000", "id": "00000000-0000-0000-0000-000000000000" }, "name" : "Default", "description" : "The default Data Center", "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255", "id" : "00000002-0002-0002-0002-000000000255", "link" : [ { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255/storagedomains", "rel" : "storagedomains" }, { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255/clusters", "rel" : "clusters" }, { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255/networks", "rel" : "networks" }, { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255/permissions", "rel" : "permissions" }, { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255/quotas", "rel" : "quotas" }, { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255/iscsibonds", "rel" : "iscsibonds" }, { "href" : "/ovirt-engine/api/datacenters/00000002-0002-0002-0002-000000000255/qoss", "rel" : "qoss" } ] } ] }
4.27. cifs-utils 4.27.1. RHBA-2011:1585 - cifs-utils bug fix update An updated cifs-utils package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The cifs-utils package contains utilities for mounting and managing CIFS shares. Bug Fixes BZ# 676439 Prior to this update, mount.cifs dropped the CAP_DAC_READ_SEARCH flag together with most of the other capability flags before it performed a mount. As a result, mounting onto a directory without execute permissions failed if mount.cifs was installed as a setuid program and the user mount was configured in the /etc/fstab file. This update reinstates the CAP_DAC_READ_SEARCH flag before calling mount. Now, mounting no longer fails. BZ# 719363 Prior to this update, several mount options were missing from the mount.cifs(8) man page. With this update, the man page documents all mount options. All users of cifs-utils are advised to upgrade to this updated cifs-utils package, which fixes these bugs.

Commands: