mtpti5iD/redhat-docs_dataset huggingface dataset:
4.55. esc 4.55.1. RHBA-2011:1718 - esc bug fix update An updated esc package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The esc package contains the Smart Card Manager GUI (Graphical User Interface), which allows the user to manage security smart cards. The primary function of the tool is to enroll smart cards, so that they can be used for common cryptographic operations, such as secure email and website access. Bug Fixes BZ# 253077 If the user resized an ESC window and closed it, the window did not preserve its size when opening it again. If the user wanted the window to be larger, for example, to make it easier to read, the user had to resize the window every single time when it was opened again. A patch has been applied to address this issue and the window size is now restored when opening ESC. BZ# 682216 Previously, during the shut down sequence of the escd daemon, the daemon reported a failure of certain instances. ESC terminated unexpectedly with a segmentation fault as a consequence. This update modifies the daemon to exit quietly. As a result, ESC no longer terminates unexpectedly. BZ# 702683 The esc-prefs.js file contains helpful commented settings designed to assist the user in trying rarely used settings if the situation warrants. A number of these settings in the file contained typos. The typos have been corrected with this update. BZ# 704281 Previously, ESC could have terminated with a segmentation fault after the user had inserted a new smart card into the reader. This was due to a bug in the code which helped to bring a pop-up window to the foreground. The code is no longer needed to assure window focus, therefore it is no longer being executed. As a result, ESC no longer terminates in the scenario described. All users of esc are advised to upgrade to this updated package, which fixes these bugs. 4.55.2. RHBA-2012:0472 - esc bug fix update An updated esc package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The esc packages contain the Smart Card Manager GUI, which allows user to manage security smart cards. The primary function of the tool is to enroll smart cards, so that they can be used for common cryptographic operations, such as secure e-mail and website access. Bug Fixes BZ# 807264 The ESC utility did not start when the latest 10 series release of the XULRunner runtime environment was installed on the system. This update includes necessary changes to ensure that ESC works as expected with the latest version of XULRunner. BZ# 807806 After removing and replacing an enrolled token, ESC could terminate unexpectedly followed by a traceback. A patch has been applied to address this issue and ESC now displays the enrolled smart card details as expected. All users of esc are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 3. Additional Resources For more information about Red Hat Developer Toolset 12.1 and Red Hat Enterprise Linux, see the resources listed below. 3.1. Red Hat Product Documentation The Red Hat Products and Documentation portal located at https://access.redhat.com/products serves as a central source of all product documentation. The following is a brief list of documents that are directly or indirectly relevant to this book: Red Hat Developer Toolset 12 User Guide - The User Guide for Red Hat Developer Toolset contains more information about installing and using this content set. Red Hat Software Collections Packaging Guide - The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the scl utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. Red Hat Software Collections 3.8 Release Notes - The Release Notes for Red Hat Software Collections document known problems, possible issues, and other important information available at the time of release of the content set. They also contain useful information on installing, rebuilding, migrating etc. Using Red Hat Software Collections Container Images - This book provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, databases, as well as the Red Hat Developer Toolset container images. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Red Hat Enterprise Linux 7 Developer Guide - The Developer Guide for Red Hat Enterprise Linux 7 provides an introduction to application development tools in Red Hat Enterprise Linux 7. Red Hat Developer Tools documentation - The Red Hat Developer Tools provides the Eclipse Integrated Development Environment and the following compiler toolsets: Clang and LLVM Toolset, Rust Toolset, and Go Toolset. 3.2. Red Hat Developers Red Hat Developer Program - The Red Hat Developers community portal. Overview of Red Hat Developer Toolset on Red Hat Developers - The Red Hat Developers portal provides a number of tutorials to get you started with developing code using different development technologies. This includes the Node.js, Perl, PHP, Python, and Ruby Software Collections. Red Hat Developer Blog - The Red Hat Developer Blog contains up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources for those who are designing and developing applications based on Red Hat technologies.

Commands:
Preface As a Red Hat Hybrid Cloud user, you can use services for the public cloud, private clouds, and on-premises infrastructure. Use this guide to learn how to configure global settings for your Red Hat account and to learn more about cloud services available in the Hybrid Cloud Console. Prerequisites You are logged in to the Hybrid Cloud Console with your Red Hat account. If you do not have a Red Hat account, click Register on the Hybrid Cloud Console login page. You are using a supported web browser. For details about web browser requirements, see the Browser Support link at the bottom of the Hybrid Cloud Console landing page.

Commands:
Appendix A. Revision History Revision History Revision 3.4-4 Wed Dec 20 2023 Lenka Spackova Fixed broken links and anchors. Revision 3.4-3 Fri Nov 12 2021 Lenka Spackova Updated Section 4.7, "Database Connectors" . Revision 3.4-2 Tue Mar 17 2020 Lenka Spackova Added a reference to container-specific upgrading instructions for PostgreSQL . Revision 3.4-1 Tue Dec 10 2019 Lenka Spackova Release of Red Hat Software Collections 3.4 Release Notes. Revision 3.4-0 Thu Nov 07 2019 Lenka Spackova Release of Red Hat Software Collections 3.4 Beta Release Notes.

Commands:
Chapter 11. Using the Red Hat Marketplace The Red Hat Marketplace is an open cloud marketplace that makes it easy to discover and access certified software for container-based environments that run on public clouds and on-premises. 11.1. Red Hat Marketplace features Cluster administrators can use the Red Hat Marketplace to manage software on OpenShift Container Platform, give developers self-service access to deploy application instances, and correlate application usage against a quota. 11.1.1. Connect OpenShift Container Platform clusters to the Marketplace Cluster administrators can install a common set of applications on OpenShift Container Platform clusters that connect to the Marketplace. They can also use the Marketplace to track cluster usage against subscriptions or quotas. Users that they add by using the Marketplace have their product usage tracked and billed to their organization. During the cluster connection process , a Marketplace Operator is installed that updates the image registry secret, manages the catalog, and reports application usage. 11.1.2. Install applications Cluster administrators can install Marketplace applications from within OperatorHub in OpenShift Container Platform, or from the Marketplace web application . You can access installed applications from the web console by clicking Operators > Installed Operators . 11.1.3. Deploy applications from different perspectives You can deploy Marketplace applications from the web console's Administrator and Developer perspectives. The Developer perspective Developers can access newly installed capabilities by using the Developer perspective. For example, after a database Operator is installed, a developer can create an instance from the catalog within their project. Database usage is aggregated and reported to the cluster administrator. This perspective does not include Operator installation and application usage tracking. The Administrator perspective Cluster administrators can access Operator installation and application usage information from the Administrator perspective. They can also launch application instances by browsing custom resource definitions (CRDs) in the Installed Operators list.

Commands:
Chapter 4. Configuring traffic ingress 4.1. Configuring SSL/TLS and Routes Support for OpenShift Container Platform edge termination routes have been added by way of a new managed component, tls . This separates the route component from SSL/TLS and allows users to configure both separately. EXTERNAL_TLS_TERMINATION: true is the opinionated setting. Note Managed tls means that the default cluster wildcard certificate is used. Unmanaged tls means that the user provided key and certificate pair is be injected into the route. The ssl.cert and ssl.key are now moved to a separate, persistent secret, which ensures that the key and certificate pair are not regenerated upon every reconcile. The key and certificate pair are now formatted as edge routes and mounted to the same directory in the Quay container. Multiple permutations are possible when configuring SSL/TLS and routes, but the following rules apply: If SSL/TLS is managed , then your route must also be managed . If SSL/TLS is unmanaged then you must supply certificates directly in the config bundle. The following table describes the valid options: Table 4.1. Valid configuration options for TLS and routes Option Route TLS Certs provided Result My own load balancer handles TLS Managed Managed No Edge route with default wildcard cert Red Hat Quay handles TLS Managed Unmanaged Yes Passthrough route with certs mounted inside the pod Red Hat Quay handles TLS Unmanaged Unmanaged Yes Certificates are set inside of the quay pod, but the route must be created manually 4.1.1. Creating the config bundle secret with the SSL/TLS cert and key pair Use the following procedure to create a config bundle secret that includes your own SSL/TLS certificate and key pair. Procedure Enter the following command to create config bundle secret that includes your own SSL/TLS certificate and key pair: USD oc create secret generic --from-file config.yaml=./config.yaml --from-file ssl.cert=./ssl.cert --from-file ssl.key=./ssl.key config-bundle-secret

Commands:
oc create secret generic --from-file config.yaml=./config.yaml --from-file ssl.cert=./ssl.cert --from-file ssl.key=./ssl.key config-bundle-secret
2.2. Identifiers 2.2.1. Identifiers SQL commands contain references to tables and columns. These references are in the form of identifiers, which uniquely identify the tables and columns in the context of the command. All queries are processed in the context of a virtual database (VDB). Because information can be federated across multiple sources, tables and columns must be scoped in some manner to avoid conflicts. This scoping is provided by schemas, which contain the information for each data source or set of views. Fully qualified table and column names are of the following form, where the separate 'parts' of the identifier are delimited by periods. TABLE: <schema_name>.<table_spec> COLUMN: <schema_name>.<table_spec>.<column_name> Syntax Rules: Identifiers can consist of alphanumeric characters, or the underscore (_) character, and must begin with an alphabetic character. Any Unicode character may be used in an identifier. Identifiers in double quotes can have any contents. The double quote character can be used if it is escaped with an additional double quote; for example, "some "" id" . Because different data sources organize tables in different ways (some prepending catalog or schema or user information) JBoss Data Virtualization allows table specification to be a dot delimited construct. Note When a table specification contains a dot, resolving will allow for the match of a partial name against any number of the end segments in the name. For example, a table with the fully qualified name vdbname."sourceschema.sourcetable" would match the partial name sourcetable . Columns, schemas, alias identifiers cannot contain a dot. Identifiers, even when quoted, are not case sensitive in JBoss Data Virtualization. Some examples of valid fully qualified table identifiers are: MySchema.Portfolios "MySchema.Portfolios" MySchema.MyCatalog.dbo.Authors Some examples of valid fully qualified column identifiers are: MySchema.Portfolios.portfolioID "MySchema.Portfolios"."portfolioID" MySchema.MyCatalog.dbo.Authors.lastName Fully qualified identifiers can always be used in SQL commands. Partial or unqualified forms can also be used, as long as the resulting names are unambiguous in the context of the command. Different forms of qualification can be mixed in the same query. 2.2.2. Reserved Words Reserved words in JBoss Data Virtualization include the standard SQL 2003 Foundation, SQL/MED, and SQL/XML reserved words, as well as JBoss Data Virtualization specific words such as BIGINTEGER, BIGDECIMAL, or MAKEDEP. See Also: Section A.2, "Reserved Keywords" Section A.4, "Reserved Keywords For Future Use"

Commands:
Chapter 3. Integrating Serverless with the cost management service Cost management is an OpenShift Container Platform service that enables you to better understand and track costs for clouds and containers. It is based on the open source Koku project. 3.1. Prerequisites You have cluster administrator permissions. You have set up cost management and added an OpenShift Container Platform source . 3.2. Using labels for cost management queries Labels, also known as tags in cost management, can be applied for nodes, namespaces or pods. Each label is a key and value pair. You can use a combination of multiple labels to generate reports. You can access reports about costs by using the Red Hat hybrid console . Labels are inherited from nodes to namespaces, and from namespaces to pods. However, labels are not overridden if they already exist on a resource. For example, Knative services have a default app=<revision_name> label: Example Knative service default label apiVersion: serving.knative.dev/v1 kind: Service metadata: name: showcase spec: ... labels: app: <revision_name> ... If you define a label for a namespace, such as app=my-domain , the cost management service does not take into account costs coming from a Knative service with the tag app=<revision_name> when querying the application using the app=my-domain tag. Costs for Knative services that have this tag must be queried under the app=<revision_name> tag. 3.3. Additional resources Configure tagging for your sources Use the Cost Explorer to visualize your costs

Commands:
apiVersion: serving.knative.dev/v1 kind: Service metadata: name: showcase spec: labels: app: <revision_name>
4.179. mingw32 4.179.1. RHEA-2011:1751 - mingw32 enhancement update Updated mingw32 packages that add two enhancements are now available for Red Hat Enterprise Linux 6. The mingw32 packages provide the MinGW (Minimalistic GNU for Windows) development environment. Enhancements BZ# 722878 The version of the mingw32 packages used GCC in version 4.4.3. This enhancement update upgrades base mingw32 packages and rebuilds all dependent packages to make sure they are in sync with the latest GCC version (4.4.6) that is available in Red Hat Enterprise Linux 6. BZ# 719866 In accordance with the latest packaging guidelines, all packages that contain debugging information now have the "mingw32-" prefix. All users of mingw32 are advised to upgrade to these updated packages, which add these enhancements.

Commands:
Chapter 2. New features and enhancements This section describes new features and enhancements in Red Hat OpenShift AI 2.18. 2.1. New features Support for OpenShift AI Self-Managed on Oracle Cloud Infrastructure (OCI) OpenShift AI Self-Managed is now supported on Red Hat OpenShift Container Platform on Oracle Cloud Infrastructure (OCI). For more information about OpenShift AI supported software platforms, see the Red Hat OpenShift AI: Supported Configurations Knowledgebase article. For more information about OpenShift Container Platform on OCI, see Installing on OCI . 2.2. Enhancements Additional training images tested and verified for distributed workloads The following additional training images are tested and verified: ROCm-compatible KFTO cluster image : A new ROCm-compatible KFTO cluster image, quay.io/modh/training:py311-rocm62-torch241 , is tested and verified. This image is compatible with AMD accelerators that are supported by ROCm 6.2. ROCm-compatible Ray cluster image : A new ROCm-compatible Ray cluster image, quay.io/modh/ray:2.35.0-py311-rocm62 , is tested and verified. This image is compatible with AMD accelerators that are supported by ROCm 6.2. For more information about the available training images in Red Hat OpenShift AI, see the Red Hat OpenShift AI: Supported Configurations Knowledgebase article. Updated Kueue version In OpenShift AI 2.18, the version of Kueue has been updated to 0.10.1. Note The minimum version of OpenShift AI that is compatible with Kueue 0.10.1 is OpenShift Container Platform 4.15. If you deploy OpenShift AI 2.18 on OpenShift Container Platform 4.14 or earlier, you must disable the API Priority and Fairness configuration for the Visibility API, as described in the Enabling/Disabling API Priority and Fairness section in the Kueue Cluster Administration guide. This modification is required because the PriorityLevelConfiguration API is incompatible with older OpenShift Container Platform versions.

Commands:
2.4. Restricting Network Connectivity During the Installation Process When installing Red Hat Enterprise Linux, the installation medium represents a snapshot of the system at a particular time. Because of this, it may not be up-to-date with the latest security fixes and may be vulnerable to certain issues that were fixed only after the system provided by the installation medium was released. When installing a potentially vulnerable operating system, always limit exposure only to the closest necessary network zone. The safest choice is the "no network" zone, which means to leave your machine disconnected during the installation process. In some cases, a LAN or intranet connection is sufficient while the Internet connection is the riskiest. To follow the best security practices, choose the closest zone with your repository while installing Red Hat Enterprise Linux from a network. For more information about configuring network connectivity, see the Network & Hostname chapter of the Red Hat Enterprise Linux 7 Installation Guide.

Commands:
4.3.2. Call Graph Tracing This section describes how to trace incoming and outgoing function calls. para-callgraph.stp para-callgraph.stp takes two command-line arguments: The function(s) whose entry or exit you would like to trace ( USD1 ). A second optional trigger function ( USD2 ), which enables or disables tracing on a per-thread basis. Tracing in each thread will continue as long as the trigger function has not exited yet. para-callgraph.stp uses thread_indent() ; as such, its output contains the timestamp, process name, and thread ID of USD1 (that is the probe function you are tracing). For more information about thread_indent() , refer to its entry in SystemTap Functions . The following example contains an excerpt from the output for stap para-callgraph.stp 'kernel.function("*@fs/*.c")' 'kernel.function("sys_read")' : Example 4.12. para-callgraph.stp Sample Output

Commands:
#! /usr/bin/env stap function trace(entry_p, extra) { %( USD# > 1 %? if (tid() in trace) %) printf("%s%s%s %s\n", thread_indent (entry_p), (entry_p>0?"->":"<-"), probefunc (), extra) } %( USD# > 1 %? global trace probe USD2.call { trace[tid()] = 1 } probe USD2.return { delete trace[tid()] } %) probe USD1.call { trace(1, USDUSDparms) } probe USD1.return { trace(-1, USDUSDreturn) }
[...] 267 gnome-terminal(2921): <-do_sync_read return=0xfffffffffffffff5 269 gnome-terminal(2921):<-vfs_read return=0xfffffffffffffff5 0 gnome-terminal(2921):->fput file=0xffff880111eebbc0 2 gnome-terminal(2921):<-fput 0 gnome-terminal(2921):->fget_light fd=0x3 fput_needed=0xffff88010544df54 3 gnome-terminal(2921):<-fget_light return=0xffff8801116ce980 0 gnome-terminal(2921):->vfs_read file=0xffff8801116ce980 buf=0xc86504 count=0x1000 pos=0xffff88010544df48 4 gnome-terminal(2921): ->rw_verify_area read_write=0x0 file=0xffff8801116ce980 ppos=0xffff88010544df48 count=0x1000 7 gnome-terminal(2921): <-rw_verify_area return=0x1000 12 gnome-terminal(2921): ->do_sync_read filp=0xffff8801116ce980 buf=0xc86504 len=0x1000 ppos=0xffff88010544df48 15 gnome-terminal(2921): <-do_sync_read return=0xfffffffffffffff5 18 gnome-terminal(2921):<-vfs_read return=0xfffffffffffffff5 0 gnome-terminal(2921):->fput file=0xffff8801116ce980
Chapter 13. Virtual Disks 13.1. Understanding Virtual Machine Storage Red Hat Virtualization supports three storage types: NFS, iSCSI and FCP. In each type, a host known as the Storage Pool Manager (SPM) manages access between hosts and storage. The SPM host is the only node that has full access within the storage pool; the SPM can modify the storage domain metadata, and the pool's metadata. All other hosts can only access virtual machine hard disk image data. By default in an NFS, local, or POSIX compliant data center, the SPM creates the virtual disk using a thin provisioned format as a file in a file system. In iSCSI and other block-based data centers, the SPM creates a volume group on top of the Logical Unit Numbers (LUNs) provided, and makes logical volumes to use as virtual disks. Virtual disks on block-based storage are preallocated by default. If the virtual disk is preallocated, a logical volume of the specified size in GB is created. The virtual machine can be mounted on a Red Hat Enterprise Linux server using kpartx , vgscan , vgchange or mount to investigate the virtual machine's processes or problems. If the virtual disk is thinly provisioned, a 1 GB logical volume is created. The logical volume is continuously monitored by the host on which the virtual machine is running. As soon as the usage nears a threshold the host notifies the SPM, and the SPM extends the logical volume by 1 GB. The host is responsible for resuming the virtual machine after the logical volume has been extended. If the virtual machine goes into a paused state it means that the SPM could not extend the disk in time. This occurs if the SPM is too busy or if there is not enough storage space. A virtual disk with a preallocated (raw) format has significantly faster write speeds than a virtual disk with a thin provisioning (QCOW2) format. Thin provisioning takes significantly less time to create a virtual disk. The thin provision format is suitable for non-I/O intensive virtual machines. The preallocated format is recommended for virtual machines with high I/O writes. If a virtual machine is able to write more than 1 GB every four seconds, use preallocated disks where possible.

Commands:
Chapter 1. Overview Red Hat(R) Enterprise Linux(R) for SAP Solutions combines the reliability, scalability, and performance of Linux with technologies that meet the specific requirements of SAP workloads. It is certified for integration with SAP S/4HANA(R) and built on the same foundation as the world's leading enterprise Linux platform, Red Hat Enterprise Linux (RHEL). For more information on RHEL for SAP Solutions, see the Red Hat Enterprise Linux for SAP Solutions product page.

Commands: