mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Shenandoah garbage collector Shenandoah is the low pause time garbage collector (GC) that reduces GC pause times by performing more garbage collection work concurrently with the running Java program. Concurrent Mark Sweep garbage collector (CMS) and G1, default garbage collector for Red Hat build of OpenJDK 11 perform concurrent marking of live objects. Shenandoah adds concurrent compaction. Shenandoah also reduces GC pause times by compacting objects concurrently with running Java threads. Pause times with Shenandoah are independent of the heap size, meaning you will have consistent pause time whether your heap is 200 MB or 200 GB. Shenandoah is an algorithm for applications which require responsiveness and predictable short pauses. Additional resources For more information about the Shenandoah garbage collector, see Shenandoah GC in the Oracle OpenJDK documentation.

Commands:
Chapter 1. Overview of machine management You can use machine management to flexibly work with underlying infrastructure like Amazon Web Services (AWS), Azure, Google Cloud Platform (GCP), OpenStack, Red Hat Virtualization (RHV), and vSphere to manage the OpenShift Container Platform cluster. You can control the cluster and perform auto-scaling, such as scaling up and down the cluster based on specific workload policies. The OpenShift Container Platform cluster can horizontally scale up and down when the load increases or decreases. It is important to have a cluster that adapts to changing workloads. Machine management is implemented as a Custom Resource Definition (CRD). A CRD object defines a new unique object Kind in the cluster and enables the Kubernetes API server to handle the object's entire lifecycle. The Machine API Operator provisions the following resources: MachineSet Machine Cluster Autoscaler Machine Autoscaler Machine Health Checks What you can do with machine sets As a cluster administrator you can: Create a machine set on: AWS Azure GCP OpenStack RHV vSphere Manually scale a machine set by adding or removing a machine from the machine set. Modify a machine set through the MachineSet YAML configuration file. Delete a machine. Create infrastructure machine sets . Configure and deploy a machine health check to automatically fix damaged machines in a machine pool. Autoscaler Autoscale your cluster to ensure flexibility to changing workloads. To autoscale your OpenShift Container Platform cluster, you must first deploy a cluster autoscaler, and then deploy a machine autoscaler for each machine set. The cluster autoscaler increases and decreases the size of the cluster based on deployment needs. The machine autoscaler adjusts the number of machines in the machine sets that you deploy in your OpenShift Container Platform cluster. User-provisioned infrastructure User-provisioned infrastructure is an environment where you can deploy infrastructure such as compute, network, and storage resources that host the OpenShift Container Platform. You can add compute machines to a cluster on user-provisioned infrastructure either as part of or after the installation process. What you can do with RHEL compute machines As a cluster administrator, you can: Add Red Hat Enterprise Linux (RHEL) compute machines , also known as worker machines, to a user-provisioned infrastructure cluster or an installation-provisioned infrastructure cluster. Add more Red Hat Enterprise Linux (RHEL) compute machines to an existing cluster.

Commands:
8.87. hwdata 8.87.1. RHEA-2014:1553 - hwdata enhancement update An updated hwdata package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The hwdata package contains tools for accessing and displaying hardware identification and configuration data. Enhancement BZ# 1064381 The PCI, USB, and vendor ID files have been updated with information about recently released hardware. Hardware utility tools that use these ID files are now able to correctly identify recently released hardware. Users of hwdata are advised to upgrade to this updated package, which adds this enhancement.

Commands:
C.2.2. Desktop Environments A desktop environment integrates various X clients to create a common graphical user environment and a development platform. Desktop environments have advanced features allowing X clients and other running processes to communicate with one another, while also allowing all applications written to work in that environment to perform advanced tasks, such as drag-and-drop operations. Red Hat Enterprise Linux provides two desktop environments: GNOME - The default desktop environment for Red Hat Enterprise Linux based on the GTK+ 2 graphical toolkit. KDE - An alternative desktop environment based on the Qt 4 graphical toolkit. Both GNOME and KDE have advanced-productivity applications, such as word processors, spreadsheets, and Web browsers; both also provide tools to customize the look and feel of the GUI. Additionally, if both the GTK+ 2 and the Qt libraries are present, KDE applications can run in GNOME and vice versa.

Commands:
Chapter 3. alt-java and java uses Depending on your needs, you can use either the alt-java binary or the java binary to run your application's code. 3.1. alt-java usage Use alt-java for any applications that run untrusted code. Be aware that using alt-java is not a solution to all speculative execution vulnerabilities. 3.2. java usage Use the java binary for performance-critical tasks in a secure environment. Additional resources See Java and Speculative Execution Vulnerabilities .

Commands:
11.4.2. Procmail Recipes New users often find the construction of recipes the most difficult part of learning to use Procmail. To some extent, this is understandable, as recipes do their message matching using regular expressions , which is a particular format used to specify qualifications for a matching string. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, refer to Section 11.4.2.5, "Recipe Examples" . Procmail recipes take the following form: The first two characters in a Procmail recipe are a colon and a zero. Various flags can be placed after the zero to control how Procmail processes the recipe. A colon after the <flags> section specifies that a lockfile is created for this message. If a lockfile is created, the name can be specified by replacing <lockfile-name> . A recipe can contain several conditions to match against the message. If it has no conditions, every message matches the recipe. Regular expressions are placed in some conditions to facilitate message matching. If multiple conditions are used, they must all match for the action to be performed. Conditions are checked based on the flags set in the recipe's first line. Optional special characters placed after the * character can further control the condition. The <action-to-perform> specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. Refer to Section 11.4.2.4, "Special Conditions and Actions" for more information. 11.4.2.1. Delivering vs. Non-Delivering Recipes The action used if the recipe matches a particular message determines whether it is considered a delivering or non-delivering recipe. A delivering recipe contains an action that writes the message to a file, sends the message to another program, or forwards the message to another email address. A non-delivering recipe covers any other actions, such as a nesting block . A nesting block is a set of actions, contained in braces { } , that are performed on messages which match the recipe's conditions. Nesting blocks can be nested inside one another, providing greater control for identifying and performing actions on messages. When messages match a delivering recipe, Procmail performs the specified action and stops comparing the message against any other recipes. Messages that match non-delivering recipes continue to be compared against other recipes.

Commands:
:0 <flags>: <lockfile-name> * <special-condition-character> <condition-1> * <special-condition-character> <condition-2> * <special-condition-character> <condition-N> <special-action-character> <action-to-perform>
E.2.3. /proc/cpuinfo This virtual file identifies the type of processor used by your system. The following is an example of the output typical of /proc/cpuinfo : processor - Provides each processor with an identifying number. On systems that have one processor, only a 0 is present. cpu family - Authoritatively identifies the type of processor in the system. For an Intel-based system, place the number in front of "86" to determine the value. This is particularly helpful for those attempting to identify the architecture of an older system such as a 586, 486, or 386. Because some RPM packages are compiled for each of these particular architectures, this value also helps users determine which packages to install. model name - Displays the common name of the processor, including its project name. cpu MHz - Shows the precise speed in megahertz for the processor to the thousandths decimal place. cache size - Displays the amount of level 2 memory cache available to the processor. siblings - Displays the total number of sibling CPUs on the same physical CPU for architectures which use hyper-threading. flags - Defines a number of different qualities about the processor, such as the presence of a floating point unit (FPU) and the ability to process MMX instructions.

Commands:
processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 2 model name : Intel(R) Xeon(TM) CPU 2.40GHz stepping : 7 cpu MHz : 2392.371 cache size : 512 KB physical id : 0 siblings : 2 runqueue : 0 fdiv_bug : no hlt_bug : no f00f_bug : no coma_bug : no fpu : yes fpu_exception : yes cpuid level : 2 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm bogomips : 4771.02
8.90. libibverbs-rocee 8.90.1. RHEA-2013:1740 - libibverbs-rocee and libmlx4-rocee bug fix and enhancement update Updated libibverbs-rocee and libmlx4-rocee packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. Red Hat Enterprise Linux includes a collection of InfiniBand and iWARP utilities, libraries, and development packages for writing applications that use Remote Direct Memory Access (RDMA) technology. Note The libibverbs-rocee packages have been upgraded to upstream version 1.1.7 and the libxml-rocee packages to upstream version 1.0.5, which provides a number of bug fixes and enhancements over the versions and keeps the HPN channel synchronized with the base Red Hat Enterprise Linux channel, where the sister versions of these packages (libibverbs and libmlx4) were also updated to the latest upstream release. All users of Remote Direct Memory Access (RDMA) technology are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 13. Component details The following table shows the component versions for each Streams for Apache Kafka release. Note Components like the operators, console, and proxy only apply to using Streams for Apache Kafka on OpenShift. Streams for Apache Kafka Apache Kafka Strimzi Operators Kafka Bridge Oauth Cruise Control Console Proxy 2.9.0 3.9.0 0.45.0 0.31 0.15.0 2.5.141 0.6 0.9.0 2.8.0 3.8.0 0.43.0 0.30 0.15.0 2.5.138 0.1 0.8.0 2.7.0 3.7.0 0.40.0 0.28 0.15.0 2.5.137 0.1 0.5.1 2.6.0 3.6.0 0.38.0 0.27 0.14.0 2.5.128 - - 2.5.2 3.5.0 (+3.5.2) 0.36.0 0.26 0.13.0 2.5.123 - - 2.5.1 3.5.0 0.36.0 0.26 0.13.0 2.5.123 - - 2.5.0 3.5.0 0.36.0 0.26 0.13.0 2.5.123 - - 2.4.0 3.4.0 0.34.0 0.25.0 0.12.0 2.5.112 - - 2.3.0 3.3.1 0.32.0 0.22.3 0.11.0 2.5.103 - - 2.2.2 3.2.3 0.29.0 0.21.5 0.10.0 2.5.103 - - 2.2.1 3.2.3 0.29.0 0.21.5 0.10.0 2.5.103 - - 2.2.0 3.2.3 0.29.0 0.21.5 0.10.0 2.5.89 - - 2.1.0 3.1.0 0.28.0 0.21.4 0.10.0 2.5.82 - - 2.0.1 3.0.0 0.26.0 0.20.3 0.9.0 2.5.73 - - 2.0.0 3.0.0 0.26.0 0.20.3 0.9.0 2.5.73 - - 1.8.4 2.8.0 0.24.0 0.20.1 0.8.1 2.5.59 - - 1.8.0 2.8.0 0.24.0 0.20.1 0.8.1 2.5.59 - - 1.7.0 2.7.0 0.22.1 0.19.0 0.7.1 2.5.37 - - 1.6.7 2.6.3 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.6 2.6.3 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.5 2.6.2 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.4 2.6.2 0.20.1 0.19.0 0.6.1 2.5.11 - - 1.6.0 2.6.0 0.20.0 0.19.0 0.6.1 2.5.11 - - 1.5.0 2.5.0 0.18.0 0.16.0 0.5.0 - - - 1.4.1 2.4.0 0.17.0 0.15.2 0.3.0 - - - 1.4.0 2.4.0 0.17.0 0.15.2 0.3.0 - - - 1.3.0 2.3.0 0.14.0 0.14.0 0.1.0 - - - 1.2.0 2.2.1 0.12.1 0.12.2 - - - - 1.1.1 2.1.1 0.11.4 - - - - - 1.1.0 2.1.1 0.11.1 - - - - - 1.0 2.0.0 0.8.1 - - - - -

Commands:
Chapter 1. What is the Red Hat Hybrid Cloud Console? You can use the Red Hat Hybrid Cloud Console to access a comprehensive set of hosted services from a single interface. The Hybrid Cloud Console provides the content, tooling, and visibility developers and IT administrators need to build, deploy, and optimize workloads across the hybrid cloud. From the Hybrid Cloud Console, you can connect with your various platforms and then centrally manage and automate your hybrid cloud and the deployments within it. Use the Hybrid Cloud Console to manage your Red Hat Enterprise Linux (RHEL) infrastructure, Red Hat OpenShift clusters, and application services. You can perform the following tasks from the Hybrid Cloud Console: Use Red Hat Insights to reduce risk and downtime, improve compliance, and optimize spend for your RHEL and Red Hat OpenShift resources. View information about your RHEL systems and Red Hat OpenShift clusters nodes from a single interface. Manage, update, and deploy different types of Red Hat OpenShift clusters and install cluster add-ons. Deploy applications on Red Hat OpenShift. Manage security policies and build pipelines. 1.1. Red Hat Enterprise Linux on the Hybrid Cloud Console The Red Hat Hybrid Cloud Console provides a centralized view into operations, security, and subscriptions for Red Hat Enterprise Linux (RHEL). Through tooling, rule-based analytical models, and the support of Red Hat, you can use the console to streamline many of the tasks and analysis required to build and deliver a stable and secure environment for applications on RHEL. Additional resources For more information about Red Hat Enterprise Linux, see the Cloud section on the Red Hat Enterprise Linux documentation page . For information about Red Hat Insights for Red Hat Enterprise Linux, see the Red Hat Insights documentation page . 1.2. Red Hat OpenShift on the Hybrid Cloud Console The Red Hat Hybrid Cloud Console provides centralized reporting and management for Red Hat OpenShift clusters. Using the OpenShift Cluster Manager service, you can streamline and simplify how operators create, register, and upgrade Red Hat OpenShift clusters across supported environments. Clusters contains your OpenShift cluster inventory, and provides the ability to create, manage, and delete OpenShift clusters.

Commands:
Appendix A. Supported Configurations A.1. Supported Data Sources and Translators The following table provides a list of data sources and translators that are supported by Red Hat. Table A.1. Supported Data Sources and Translators Data Source Translator Driver Apache Accumulo 1.6.5 accumulo - Apache Cassandra 2.2.4 cassandra - Apache Hive hive v2.0 Hive JDBC driver Apache Solr 4.9.0 solr - Cloudera Hadoop - - EDS 5.5.1 teiid current Teiid Driver Files - delimited, fixed length file - Generic Datasource-JDBC ansi jdbc-ansi - Generic Datasource-JDBC simple (postgresql84) jdbc-simple postgresql 8.4 Google Spreadsheet google-spreadsheet - Greenplum 4.1 greenplum postgresql 9.0 Hortonworks Hadoop - - Hortonworks Data Platform 2.4 hive 1.2.1 HPE Vertica 7.2.1 vertica 7.2.1-0 HSQL (for test/examples only) - - IBM DB2 9.7 db2 Universal Driver v4.x IBM DB2 10 db2 Universal Driver v4.x IBM DB2 11.1 db2 Universal Driver v4.x IBM Informix 12.10 informix 4.10.JC5DE Ingres 10 ingres 4.1.4 Intel Hadoop - - JBoss Data Grid 6.4 (remote client - hotrod) infinispan-cache-dsl Hot Rod Client JBoss Data Grid 6.4 (library mode) infinispan-cache - JBoss Data Grid 7.1.0 (hotrod) infinispan-hotrod Hot Rod Client LDAP/ActiveDirectory v3 ldap - Mainframe (CICS,IMS,VSAM) - - MariaDB mysql5 mysql 5.1.22 ModeShape/JCR 3.1 modeshape 3.8.4 MongoDB 2.2 mongodb - MongoDB 3.4 mongodb - MS Access 2010 - - MS Access 2013 - - MS Excel 2010 excel - MS Excel 2013 excel - MS SQL Server 2008 sqlserver Microsoft SQL Server JDBC Driver 4 MS SQL Server 2012 sqlserver Microsoft SQL Server JDBC Driver 4 MS SQL Server 2014 sqlserver Microsoft SQL Server JDBC Driver 4 MySQL 5.1 mysql5 v5.1 MySQL 5.5 mysql5 v5.5 Netezza 6.0.2 netezza - Oracle 10g R2 oracle Oracle JDBC Driver v10 Oracle 11g R2 oracle Oracle JDBC Driver v12 Oracle 12c oracle Oracle JDBC Driver v12 PostgreSQL 8.4 postgresql postgresql 8.4 PostgreSQL 9.2 postgresql postgresql 9.2 PostgreSQL 9.6 postgresql JDBC4 PostgreSQL Driver, Version 42.2.2.jre6 PostgreSQL 10.1 postgresql JDBC4 PostgreSQL Driver, Version 42.2.2.jre6 REST/JSON over HTTP ws - Red Hat Enterprise Linux 5.5/6 PostgreSQL config - - Red Hat Directory Server (RHDS) 9.0 ldap - Red Hat JBoss Data Virtualization teiid current Teiid Driver Salesforce.com API 22 salesforce - SAP Netweaver Gateway (OData) sap-nw-gateway - Support SAP Service Registry as a Data Source - - SAP HANA v1.0 SP 10+ hana ngdbc.jar v1.00 in-memory JDBC driver SAP IQ 16 sybaseiq jconn4 (JDBC 4.0) Sybase ASE 15 sybase jconn4 (JDBC 4.0) Teradata Express 12 teradata - Webservices ws - XML Files FILE - Note MS Excel is supported in so much as there is a write procedure.

Commands:
1.2. A Review of Certificate System Subsystems Red Hat Certificate System provides five different subsystems, each focusing on different aspects of a PKI deployment. These subsystems work together to create a public key infrastructure (PKI). Depending on what subsystems are installed, a PKI can function as a token management system (TMS) or a non token management system. For descriptions of the subsystems and TMS and non-TMS environments, see the A Review of Certificate System Subsystems section in the Red Hat Certificate System Planning, Installation, and Deployment Guide . Enterprise Security Client The Enterprise Security Client is not a subsystem since it does not perform any operations with certificates, keys, or tokens. The Enterprise Security Client is a user interface which allows people to manage certificates on smart cards very easily. The Enterprise Security Client sends all token operations, such as certificate requests, to the token processing system (TPS), which then sends them to the certificate authority (CA). For more information, see For more information, see Red Hat Certificate System Managing Smart Cards with the Enterprise Security Client .

Commands:
Chapter 4. Model management There are a various ways you can organize and manage your custom or downloaded models on RHEL AI 4.1. Uploading your models to a registry After you fine-tune a model, you can upload the model to an external registry. RHEL AI currently supports uploading models to AWS S3 buckets. Prerequisites You installed RHEL AI on your preferred platform. You initialized InstructLab. Log in to your preferred registry. Procedure You can upload your models to a specific registry with the following command USD ilab model upload --model <name-of-model> --destination <registry-location> --dest-type <registry-type> where: <name-of-model> Specify the checkpoint name you want to upload. For example, --model samples_0801 . You can also specify the path to the checkpoint. <registry-location> Specify where you want to upload the model. For example, --destination example-s3-bucket <registry-type> Specify the model type. Valid values include: s3 . Example ilab model upload command to an s3 bucket USD ilab model upload --model samples_0801 --destination example-s3-bucket --dest-type s3

Commands:
ilab model upload --model <name-of-model> --destination <registry-location> --dest-type <registry-type>
ilab model upload --model samples_0801 --destination example-s3-bucket --dest-type s3
7.273. wpa_supplicant 7.273.1. RHBA-2013:0431 - wpa_supplicant bug fix and enhancement update Updated wpa_supplicant packages that fix multiple bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The wpa_supplicant packages contain a WPA (Wi-Fi Protected Access) Supplicant utility for Linux, BSD, and Windows with support for WPA and WPA2 (IEEE 802.11i/RSN). The supplicant is an IEEE 802.1X/WPA component that is used in client workstations. It implements key negotiation with a WPA Authenticator and it controls the roaming and IEEE 802.11 authentication and association of the WLAN driver. Bug Fixes BZ#813579 When roaming from one Access Point (AP) to another and the connection was disrupted, NetworkManager did not always automatically reconnect. This update includes a number of backported upstream patches to improve Proactive Key Caching (PKC), also known as Opportunistic Key Caching (OKC). As a result, WPA connections now roam more reliably. BZ#837402 Previously, the supplicant would attempt to roam to slightly stronger access points, increasing the chance of a disconnection. This bug has been fixed and the supplicant now only attempts to roam to a stronger access point when the current signal is significantly degraded. Enhancement BZ#672976 The "wpa_gui" program was removed from "wpa_supplicant" in the 6.0 release as per BZ#553349, however, the man page was still being installed. This upgrade removes the man page. All users of wpa_supplicant are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
2.2. File System Fragmentation Red Hat Enterprise Linux 6.4 introduces improvements to file fragmentation management in GFS2. With Red Hat Enterprise Linux 6.4, simultaneous writes result in less file fragmentation and therefore better performance for these workloads. While there is no defragmentation tool for GFS2 on Red Hat Enterprise Linux, you can defragment individual files by identifying them with the filefrag tool, copying them to temporary files, and renaming the temporary files to replace the originals. (This procedure can also be done in versions prior to Red Hat Enterprise Linux 6.4 as long as the writing is done sequentially.)

Commands: