mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 5. Personal settings In Personal settings you can edit your preferences as a team member. If you are an admin, you will also be able to edit the account preferences. For that, check out the account configuration tutorial. To edit your personal settings: Click on the gear icon in the navigation bar. On the left panel, navigate to Personal . There are 3 types of settings you can edit from here: Personal Details Name, email, password, etc . Tokens Create access tokens to authenticate against the 3scale application programming interfaces (APIs) - Billing, Account Management, and Analytics - and try them out using our ActiveDocs. Learn more about 3scale tokens . Notification Preferences Select which notifications you would like to receive. Note: If you are an enterprise customer, and if you are a member, these are filtered by area and service. This means you will only be able to subscribe to notifications regarding areas and services you have been given access to. More on notification preferences here .

Commands:
8.61. gtk2 8.61.1. RHBA-2013:1544 - gtk2 and atk bug fix and enhancement update Updated gtk2 and atk packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The gtk2 packages provide a multi-platform toolkit for creating graphical user interfaces, GIMP Toolkit (GTK+). GTK+ offers a complete set of widgets and is suitable for small projects as well as complete application suites. Note The ATK library provides a set of interfaces for adding accessibility support to applications and graphical user interface toolkits. By supporting the ATK interfaces, an application or toolkit can be used with tools such as screen readers, magnifiers, and alternative input devices. The gtk2 packages have been upgraded to upstream version 2.20.1, which provides a number of bug fixes and enhancements over the version. (BZ# 883022 ) The atk packages have been upgraded to upstream version 1.30.0, which provides a number of bug fixes and enhancements over the version. (BZ# 883027 ) Bug Fixes BZ# 970594 When rendering the text in a combo box, the GTK+ cell renderer always rendered text that was rendered last time as the first item. Consequently, if the previously rendered text did not match any item in the name set, the first item in the "Categories" combo box in the Contacts view could have been rendered as empty, which affected accessibility and automated tests. This update ensures that the cell renderer is now properly updated and renders items for the current combo box call so the aforementioned problem no longer occurs. BZ# 979049 Due to a bug in the GtkTreeView interface, the expand arrows in a tree view in Evolution stopped functioning after clicking on an icon in the system tray. This update increases robustness of the tree expanding and collapsing code, which fixes this bug. Users of gtk2 and atk are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
7.73. gnutls 7.73.1. RHBA-2013:0425 - gnutls bug fix update Updated gnutls packages that fix four bugs are now available for Red Hat Enterprise Linux 6. The gnutls packages provide the GNU Transport Layer Security (GnuTLS) library, which implements cryptographic algorithms and protocols such as SSL, TLS, and DTLS. Bug Fixes BZ# 648297 Previously, the gnutls_priority_init.3 man page contained incorrect information on the gnutls-2.8.5-safe-renegotiation patch, particularly on special control keywords. The manual page has been updated to provide accurate information about the described subject. BZ# 745242 Prior to this update, the gnutls_x509_privkey_import() function failed to load private keys in the PKCS#8 format. Consequently, these keys were not processed by applications which use gnutls_x509_privkey_import(). This bug has been fixed, and gnutls_x509_privkey_import() now allows loading of private keys formatted in PKCS#8. BZ#771378 Multiple bugs were present in the implementation of the TLS-1.2 protocol in the gnutls package. Consequently, gnutls was incompatible with clients and servers conforming to the TLS-1.2 protocol standard. With this update, the TLS-1.2 implementation has been fixed. As a result, the compatibility of gnutls with other TLS-1.2 clients and servers is now assured. BZ# 807746 Previously, the gnutls-cli-debug man page contained typographical errors and incorrect information on the command-line options. The manual page has been updated, and no longer contains the aforementioned errors. All users of gnutls are advised to upgrade to these updated packages, which fix these bugs. 7.73.2. RHSA-2013:0883 - Important: gnutls security update Updated gnutls packages that fix one security issue are now available for Red Hat Enterprise Linux 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 associated with the description below. The GnuTLS library provides support for cryptographic algorithms and for protocols such as Transport Layer Security (TLS). Security Fix CVE-2013-2116 It was discovered that the fix for the CVE-2013-1619 issue released via RHSA-2013:0588 introduced a regression in the way GnuTLS decrypted TLS/SSL encrypted records when CBC-mode cipher suites were used. A remote attacker could possibly use this flaw to crash a server or client application that uses GnuTLS. Users of GnuTLS are advised to upgrade to these updated packages, which correct this issue. For the update to take effect, all applications linked to the GnuTLS library must be restarted.

Commands:
Preface The Package manifest document provides a package listing for Red Hat Enterprise Linux 8.9. Capabilities and limits of RHEL 8 as compared to other versions of the system are available in the Knowledgebase article Red Hat Enterprise Linux technology capabilities and limits . Information regarding the RHEL life cycle is provided in the Red Hat Enterprise Linux Life Cycle document. Detailed changes in each minor release of RHEL are documented in the Release notes . Changes to packages between RHEL 7 and RHEL 8, as well as changes between minor releases of RHEL 8, are listed in Considerations in adopting RHEL 8 .

Commands:
Chapter 3. Distribution selection Red Hat provides several distributions of Red Hat build of OpenJDK. This module helps you select the distribution that is right for your needs. All distributions of OpenJDK contain the JDK Flight Recorder (JFR) feature. This feature produces diagnostics and profiling data that can be consumed by other applications, such as JDK Mission Control (JMC). Red Hat build of OpenJDK RPMs for RHEL 8 RPM distributions of Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, and Red Hat build of OpenJDK 17 for RHEL 8. Red Hat build of OpenJDK 8 JRE portable archive for RHEL Portable Red Hat build of OpenJDK 8 JRE archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 8 portable archive for RHEL Portable Red Hat build of OpenJDK 8 archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 11 JRE portable archive for RHEL Portable Red Hat build of OpenJDK 11 JRE archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 11 portable archive for RHEL Portable Red Hat build of OpenJDK 11 archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 17 JRE portable archive for RHEL Portable Red Hat build of OpenJDK 17 JRE archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK 17 portable archive for RHEL Portable Red Hat build of OpenJDK 17 archive distribution for RHEL 7 and 8 hosts. Red Hat build of OpenJDK archive for Windows Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, and Red Hat build of OpenJDK 17 distributions for all supported Windows hosts. Recommended for cases where multiple Red Hat build of OpenJDK versions may be installed on a host. This distribution includes the following: Java Web Start Mission Control Red Hat build of OpenJDK installers for Windows Red Hat build of OpenJDK 8, Red Hat build of OpenJDK 11, and Red Hat build of OpenJDK 17 MSI installers for all supported Windows hosts. Optionally installs Java Web Start and sets environment variables. Suitable for system wide installs of a single Red Hat build of OpenJDK version. Additional resources For more information about the JDK Flight Recorder (JFR), see Introduction to JDK Flight Recorder . For more information about the JDK Flight Recorder (JFR), see Introduction to JDK Mission Control . JDK Mission Control is available for RHEL with Red Hat Software Collections 3.2 . Revised on 2024-05-03 15:35:00 UTC

Commands:
Chapter 7. Remote Querying Red Hat JBoss Data Grid's Hot Rod protocol allows remote, language neutral querying. Two features allow this to occur: The Infinispan Query Domain-specific Language (DSL) JBoss Data Grid uses its own query language based on an internal DSL. The Infinispan Query DSL provides a simplified way of writing queries, and is agnostic of the underlying query mechanisms. Querying via the Hot Rod client allows remote, language-neutral querying, and is implementable in all languages currently available for the Hot Rod client. The Infinispan Query DSL is essential for performing remote queries, but can be used in both embedded and remote mode. Protobuf Encoding Google's Protocol Buffers is used as an encoding format for both storing and querying data. The Infinispan Query DSL can be used remotely via the Hot Rod client that is configured to use the Protobuf marshaller. Protocol Buffers are used to adopt a common format for storing cache entries and marshalling them. Remote clients that need to index and query their stored entities must use the Protobuf encoding format. It is also possible to store Protobuf entities for the benefit of platform independence without indexing enabled if it is not required. Report a bug 7.1. Querying Comparison In Library mode, both Lucene Query-based and DSL querying is available. In Remote Client-Server mode, only Remote Querying using DSL is available. The following table is a feature comparison between Lucene Query-based querying, Infinispan Query DSL and Remote Querying. Table 7.1. Embedded querying and Remote querying Feature Library Mode/Lucene Query Library Mode/DSL Query Remote Client-Server Mode/DSL Query Indexing Mandatory Optional but highly recommended Optional but highly recommended Index contents Selected fields Selected fields Selected fields Data Storage Format Java objects Java objects Protocol buffers Keyword Queries Yes No No Range Queries Yes Yes Yes Fuzzy Queries Yes No No Wildcard Yes Limited to like queries (Matches a wildcard pattern that follows JPA rules). Limited to like queries (Matches a wildcard pattern that follows JPA rules). Phrase Queries Yes No No Combining Queries AND, OR, NOT, SHOULD AND, OR, NOT AND, OR, NOT Sorting Results Yes Yes Yes Filtering Results Yes, both within the query and as appended operator Within the query Within the query Pagination of Results Yes Yes Yes Continuous Queries No Yes Yes Query Aggregation Operations No Yes Yes Report a bug

Commands:
Chapter 1. Red Hat Advanced Cluster Security for Kubernetes 4.7 Documentation Welcome to the official Red Hat Advanced Cluster Security for Kubernetes documentation, where you can learn about Red Hat Advanced Cluster Security for Kubernetes and start exploring its features. To go to the Red Hat Advanced Cluster Security for Kubernetes documentation, you can use one of the following methods: Use the left navigation bar to browse the documentation. Select the task that interests you from the contents of this Welcome page. 1.1. Installation activities Understanding installation methods for different platforms : Determine the best installation method for your product and platform. 1.2. Operating Red Hat Advanced Cluster Security for Kubernetes Explore various activities you can perform by using Red Hat Advanced Cluster Security for Kubernetes: Viewing the dashboard : Find information about the Red Hat Advanced Cluster Security for Kubernetes real-time interactive dashboard. Learn how to use it to view key metrics from all your hosts, containers, and services. Compliance feature overview : Understand how to run automated checks and validate compliance based on industry standards, including CIS, NIST, PCI, and HIPAA. Managing vulnerabilities : Learn how to identify and prioritize vulnerabilities for remediation. Responding to violations : Learn how to view policy violations, drill down to the actual cause of the violation, and take corrective actions. 1.3. Configuring Red Hat Advanced Cluster Security for Kubernetes Explore the following typical configuration tasks in Red Hat Advanced Cluster Security for Kubernetes: Adding custom certificates : Learn how to use a custom TLS certificate with Red Hat Advanced Cluster Security for Kubernetes. After you set up a certificate, users and API clients do not have to bypass the certificate security warnings. Backing up Red Hat Advanced Cluster Security for Kubernetes : Learn how to perform manual and automated data backups for Red Hat Advanced Cluster Security for Kubernetes and use these backups for data restoration in the case of an infrastructure disaster or corrupt data. Configuring automatic upgrades for secured clusters : Stay up to date by automating the upgrade process for each secured cluster. 1.4. Integrating with other products Learn how to integrate Red Hat Advanced Cluster Security for Kubernetes with the following products: Integrating with PagerDuty : Learn how to integrate with PagerDuty and forward alerts from Red Hat Advanced Cluster Security for Kubernetes to PagerDuty. Integrating with Slack : Learn how to integrate with Slack and forward alerts from Red Hat Advanced Cluster Security for Kubernetes to Slack. Integrating with Sumo Logic : Learn how to integrate with Sumo Logic and forward alerts from Red Hat Advanced Cluster Security for Kubernetes to Sumo Logic. Integrating by using the syslog protocol : Learn how to integrate with a security information and event management (SIEM) system or a syslog collector for data retention and security investigations.

Commands:
5.355. wget 5.355.1. RHBA-2012:1353 - wget bug fix update Updated wget packages that fix one bug are now available for Red Hat Enterprise Linux 6. The wget packages provide the GNU Wget file retrieval utility for HTTP, HTTPS, and FTP protocols. Wget provides various useful features, such as the ability to work in the background while the user is logged out, recursive retrieval of directories, file name wildcard matching or updating files in dependency on file timestamp comparison. Bug Fixes BZ# 754168 Prior to this update, the wget package contained a redundant URL to the wget upstream project. This update modifies the specification file to list the correct http://www.gnu.org/software/wget/. BZ# 814208 Prior to this update, the wget utility did not previously work as intended with the "-T, --timeout" option set when http server did not answer the SSL handshake. Wget source code has been patched, to ensure that wget aborts the connection when using --timeout option correctly. BZ# 714893 Prior to this update, the wget utility source code was lacking check of the HTTP response parsing function return value. In some cases, when HTTP response header was malformed (fuzzed), the parsing function returned error. Because the returned value was not checked, it then resulted in Segmentation Fault. This update adds check of the HTTP response parsing function return value in the wget source code. Now when HTTP response header is malformed (fuzzed) and the parsing function returns error, the following error message is thrown and wget retries the request. All users of wget are advised to upgrade to these updated packages, which fix this bug.

Commands:
2012-10-01 10:13:44 ERROR -1: Malformed status line.
4.9. RHEA-2012:1038 - new packages: kmod-bnx2x, kmod-bnx2, kmod-bnx2i, kmod-bnx2fc New kmod-bnx2x, kmod-bnx2, kmod-bnx2i, kmod-bnx2fc packages are now available for Red Hat Enterprise Linux 6. The kmod-bnx2x packages provide temporary drivers for the following hardware beyond what was delivered in Red Hat Enterprise Linux 6.2: Broadcom NetXtreme II BCM57xx Gigabit Ethernet The kmod-bnxx packages provide temporary drivers for the following hardware beyond what was delivered in Red Hat Enterprise Linux 6.2: Broadcom NetXtreme II BCM5771x/578xx 10/20-Gigabit Ethernet The kmod-bnx2i packages provide temporary drivers for the following hardware beyond what was delivered in Red Hat Enterprise Linux 6.2: Broadcom NetXtreme II BCM570x/5771x/578xx iSCSI The kmod-bnx2fc packages provide temporary drivers for the following hardware beyond what was delivered in Red Hat Enterprise Linux 6.2: Broadcom NetXtreme II BCM5771x/578xx FCoE This enhancement update adds the kmod-bnx2x, kmod-bnx2, kmod-bnx2i and kmod-bnx2fc packages to Red Hat Enterprise Linux 6 as part of the Red Hat Enterprise Linux Driver Update Program (DUP). The packages introduced by the RHEA-2012:0503 advisory did not contain proper firmware for kmod-bnx2. In addition, the driver included in the kmod-bnx2x packages could, under certain circumstances, work incorrectly with Fibre Channel over Ethernet (FCoE). This update addresses these problems. (BZ# 818940 , BZ# 819566 , BZ# 819569 , BZ# 819567 ) Users encountering the aforementioned problems and users requiring temporary driver support for the specific hardware noted above should install these packages. Unless a system includes the exact hardware supported by kmod-bnx2x, kmod-bnx2, kmod-bnx2i, or kmod-bnx2fc, these packages must not be installed.

Commands:
Chapter 3. Samba Samba is an open-source implementation of the Server Message Block ( SMB ) and Common Internet File System ( CIFS ) protocols that provides file and print services between clients across various operating systems. [4] In Red Hat Enterprise Linux, the samba package provides the Samba server. Run the rpm -q samba command to see if the samba package is installed. If it is not installed and you want to use Samba, run the following command as the root user to install it: 3.1. Samba and SELinux When SELinux is enabled, the Samba server ( smbd ) runs confined by default. Confined services run in their own domains, and are separated from other confined services. The following example demonstrates the smbd process running in its own domain. This example assumes the samba package is installed: Run the getenforce command to confirm SELinux is running in enforcing mode: The getenforce command returns Enforcing when SELinux is running in enforcing mode. Run the service smbd start command as the root user to start smbd : Run the ps -eZ | grep smb command to view the smbd processes: The SELinux context associated with the smbd processes is unconfined_u:system_r:smbd_t:s0 . The second last part of the context, smbd_t , is the type. A type defines a domain for processes and a type for files. In this case, the smbd processes are running in the smbd_t domain. Files must be labeled correctly to allow smbd to access and share them. For example, smbd can read and write to files labeled with the samba_share_t type, but by default, cannot access files labeled with the httpd_sys_content_t type, which is intended for use by the Apache HTTP Server. Booleans must be enabled to allow certain behavior, such as allowing home directories and NFS volumes to be exported through Samba, as well as to allow Samba to act as a domain controller. [4] Refer to the official Samba website for more information.

Commands:
~]# yum install samba
~]USD getenforce Enforcing
~]# service smb start Starting SMB services: [ OK ]
~]USD ps -eZ | grep smb unconfined_u:system_r:smbd_t:s0 16420 ? 00:00:00 smbd unconfined_u:system_r:smbd_t:s0 16422 ? 00:00:00 smbd
Chapter 8. Migrating upstream Keycloak to Red Hat build of Keycloak 24.0 Starting with version 22, minimal differences exist between Red Hat build of Keycloak and upstream Keycloak. The following differences exist: For upstream Keycloak, the distribution artifacts are on keycloak.org ; for Red Hat build of Keycloak, the distribution artifacts are on the Red Hat customer portal . Oracle and MSSQL database drivers are bundled with upstream Keycloak, but not bundled with Red Hat build of Keycloak. See Configuring the database for detailed steps on how to install those drivers. The GELF log handler is not available in Red Hat build of Keycloak. The migration process depends on the version of Keycloak to be migrated and the type of Keycloak installation. See the following sections for details. 8.1. Matching Keycloak version The migration process depends on the version of Keycloak to be migrated. If your Keycloak project version matches the Red Hat build of Keycloak version, migrate Keycloak by using the Red Hat build of Keycloak artifacts on the Red Hat customer portal . If your Keycloak project version is an older version, use the Keycloak Upgrading Guide to upgrade Keycloak to match the Red Hat build of Keycloak version. Then, migrate Keycloak using the artifacts on the Red Hat customer portal . If your Keycloak project version is greater than the Red Hat build of Keycloak version, you cannot migrate to Red Hat build of Keycloak. Instead, create a new deployment of Red Hat build of Keycloak or wait for a future Red Hat build of Keycloak release. 8.2. Migration based on type of Keycloak installation Once you have a matching version of Keycloak, migrate Keycloak based on the type of installation. If you installed Keycloak from a ZIP distribution, migrate Keycloak by using the artifacts on the Red Hat customer portal . If you deployed the Keycloak Operator, uninstall it and install the Red Hat build of Keycloak Operator by using the Operator guide . The CRs are compatible between upstream Keycloak and Red Hat build of Keycloak. If you created a custom server container image, rebuild it by using the Red Hat build of Keycloak image. See Running Keycloak in a Container .

Commands:
11.3. The Transaction Manager Use the following to obtain the TransactionManager from the cache: To execute a sequence of operations within transaction, wrap these with calls to methods begin() and commit() or rollback() on the TransactionManager: Example 11.1. Performing Operations Note If a cache method returns a CacheException (or a subclass of the CacheException) within the scope of a JTA transaction, the transaction is automatically marked to be rolled back. To obtain a reference to a Red Hat JBoss Data Grid XAResource, use the following API: Report a bug

Commands:
TransactionManager tm = cache.getAdvancedCache().getTransactionManager();
tm.begin(); Object value = cache.get("A"); cache.remove("A"); Object prev = cache.put("B", value); if (prev == null) tm.commit(); else tm.rollback();
XAResource xar = cache.getAdvancedCache().getXAResource();
12.4. Translators in Red Hat JBoss Data Virtualization These are the non-JDBC translators you can use: accumulo amazon-s3 cassandra couchbase excel file google-spreadsheet infinispan-cache infinispan-cache-dsl infinispan-cache-hotrod jpa2 ldap loopback map-cache mongodb odata odata4 olap salesforce salesforce-34 sap-gateway sap-nw-gateway simpledb solr ws There is also a series of JDBC-based translator types you can use: jdbc-ansi jdbc-simple access actian-vector db2 derby hbase excel-odbc greenplum h2 hana hive hsql impala ingres ingres93 intersystems-cache informix metamatrix modeshape mysql5 netezza oracle osisoft-pi postgresql prestodb redshift sqlserver sybase teiid teradata vertica If none of these translators is suitable for your system then you can develop a custom one.

Commands: