mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Known issues The known issues for running .NET on Red Hat Enterprise Linux (RHEL) include the following: There are no NuGet packages for ppc64le and s390x on nuget.org. Using the rhel.8-s390x , linux-s390x , rhel.8-ppc64le , or linux-ppc64le runtime identifier can cause some dotnet commands to fail when they try to obtain these packages. These commands are either not fully supported on ppc64le and s390x as described in the other known issues, or the issue can be fixed by not specifying the runtime identifier. Single file applications are not supported on ppc64le or s390x . PublishReadyToRun/crossgen is not supported on ppc64le or s390x . NativeAOT is not supported on ppc64le or s390x OmniSharp, the language server used by IDEs like Visual Studio Code, is not available on ppc64le and s390x . Several workloads can not be installed in the .NET 9.0 shipped by Red Hat: android macos maui-android maui-tizen maui-windows

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 7 is available on the following architectures: [1] 64-bit AMD 64-bit Intel IBM POWER7+ (big endian) IBM POWER8 (big endian) [2] IBM POWER8 (little endian) [3] IBM POWER9 (little endian) [4] [5] IBM Z [4] [6] 64-bit ARM [4] The Red Hat Enterprise Linux 7 is distributed with the kernel version 3.10.0-1127, which provides support for the following architectures: 64-bit AMD 64-bit Intel IBM POWER7+ (big endian) IBM POWER8 (big endian) IBM POWER8 (little endian) IBM Z (kernel version 3.10) The following architectures remain fully supported and continue to receive z-stream security and bug fix updates in accordance with the Red Hat Enterprise Linux Life Cycle : IBM POWER9 (little endian) IBM Z - Structure A (kernel version 4.14) 64-bit ARM [1] Note that the Red Hat Enterprise Linux 7 installation is supported only on 64-bit hardware. Red Hat Enterprise Linux 7 is able to run 32-bit operating systems, including versions of Red Hat Enterprise Linux, as virtual machines. [2] Red Hat Enterprise Linux 7 POWER8 (big endian) are currently supported as KVM guests on Red Hat Enterprise Linux 7 POWER8 systems that run the KVM hypervisor, and on PowerVM. [3] Red Hat Enterprise Linux 7 POWER8 (little endian) is currently supported as a KVM guest on Red Hat Enterprise Linux 7 POWER8 systems that run the KVM hypervisor, and on PowerVM. In addition, Red Hat Enterprise Linux 7 POWER8 (little endian) guests are supported on Red Hat Enterprise Linux 7 POWER9 systems that run the KVM hypervisor in POWER8-compatibility mode on version 4.14 kernel using the kernel-alt package. [4] This architecture is supported with the kernel version 4.14, provided by the kernel-alt packages. For details, see the Red Hat Enterprise Linux 7.5 Release Notes . [5] Red Hat Enterprise Linux 7 POWER9 (little endian) is currently supported as a KVM guest on Red Hat Enterprise Linux 7 POWER9 systems that run the KVM hypervisor on version 4.14 kernel using the kernel-alt package, and on PowerVM. [6] Red Hat Enterprise Linux 7 for IBM Z (both the 3.10 kernel version and the 4.14 kernel version) is currently supported as a KVM guest on Red Hat Enterprise Linux 7 for IBM Z hosts that run the KVM hypervisor on version 4.14 kernel using the kernel-alt package.

Commands:
7.295. zlib 7.295.1. RHBA-2013:0398 - zlib bug fix and enhancement update Updated zlib packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The zlib packages provide a general-purpose lossless data compression library that is used by many different programs. Bug Fix BZ# 754694 Due to missing information about the zlib version, some applications using zlib could not work properly. The zlib.map version script, which provides version information, has been added to the underlying source code and zlib now works as expected. Enhancement BZ#823007 This enhancement optimizes the zlib compression library for IBM System z. All users of zlib are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
5.2.3. Preventing Allocation on a Physical Volume You can prevent allocation of physical extents on the free space of one or more physical volumes with the pvchange command. This may be necessary if there are disk errors, or if you will be removing the physical volume. The following command disallows the allocation of physical extents on /dev/sdk1 . You can also use the -xy arguments of the pvchange command to allow allocation where it had previously been disallowed.

Commands:
pvchange -x n /dev/sdk1
18.12.3. Filtering Chain Priorities As previously mentioned, when creating a filtering rule, all chains are connected to the root chain. The order in which those chains are accessed is influenced by the priority of the chain. The following table shows the chains that can be assigned a priority and their default priorities. Table 18.1. Filtering chain default priorities values Chain (prefix) Default priority stp -810 mac -800 vlan -750 ipv4 -700 ipv6 -600 arp -500 rarp -400 Note A chain with a lower priority value is accessed before one with a higher value. The chains listed in Table 18.1, "Filtering chain default priorities values" can be also be assigned custom priorities by writing a value in the range [-1000 to 1000] into the priority (XML) attribute in the filter node. Section 18.12.2, "Filtering Chains" filter shows the default priority of -500 for arp chains, for example.

Commands:
Appendix F. Replication High Availability Configuration Elements The following tables list the valid ha-policy configuration elements when using a replication HA policy. Table F.1. Configuration Elements Available when Using Replication High Availability Name Description check-for-live-server Applies only to brokers configured as master brokers. Specifies whether the original master broker checks the cluster for another live broker using its own server ID when starting up. Set to true to fail back to the original master broker and avoid a "split brain" situation in which two brokers become live at the same time. The default value of this property is false . cluster-name Name of the cluster configuration to use for replication. This setting is only necessary if you configure multiple cluster connections. If configured, the the cluster configuration with this name will be used when connecting to the cluster. If unset, the first cluster connection defined in the configuration is used. group-name If set, backup brokers will only pair with live brokers that have a matching value for group-name . initial-replication-sync-timeout The amount of time the replicating broker will wait upon completion of the initial replication process for the replica to acknowledge that it has received all the necessary data. The default value of this property is 30,000 milliseconds. Note During this interval, any other journal-related operations are blocked. max-saved-replicated-journals-size Applies to backup brokers only. Specifies how many backup journal files the backup broker retains. Once this value has been reached, the broker makes space for each new backup journal file by deleting the oldest journal file. The default value of this property is 2 . allow-failback Applies to backup brokers only. Determines whether the backup broker resumes its original role when another broker such as the live broker makes a request to take its place. The default value of this property is true . restart-backup Applies to backup brokers only. Determines whether the backup broker automatically restarts after it fails back to another broker. The default value of this property is true . Revised on 2022-06-16 10:59:35 UTC

Commands:
Chapter 7. Desktop pdftops now generates valid PostScript files Previously, the pdftops utility of Poppler converted PDF files with embedded PostScript Type 1 fonts in the Printer Font Binary (PFB) format together with the PFB headers. As a consequence, incorrect PostScript files were produced from such conversions. Poppler has been fixed to recognize the PFB headers and exclude them from the conversion, and the described problem no longer occurs. (BZ# 1232210 ) Creating thumbnails with Nautilus works as expected Prior to this update, Nautilus was restricting the stack size for the thread that was creating thumbnails, and the libraries creating those thumbnails were at some point out of memory. As a consequence, Nautilus terminated unexpectedly when creating a thumbnail of big images, specially images of the jp2 type. This bug has been fixed, and Nautilus no longer crashes when creating thumbnails. (BZ#1268970) xfreerdp no longer crashes when connecting to a CA-signed RDP server Previously, the xfreerdp client terminated unexpectedly when connecting to a Certification Authority (CA)-signed Remote Desktop Protocol (RDP) server. With this update, the pointer dereference in CA verification code that caused the crash has been fixed, and connecting to a CA-signed RDP server works as expected. (BZ#1186916) Responsiveness fixes for gnome-vfs2 user interfaces Previously, the gnome-vfs2 service called the stat() function for every file on the Multiversion File System (MVFS), used for example by the IBM Rational ClearCase utilities. This behavior significantly slowed down file operations. With this update, the unnecessary stat() operations have been limited. As a result, gnome-vfs2 user interfaces, such as Nautilus, are more responsive on MVFS. (BZ#917810) gvfs correctly checks if the metadata database has been loaded Prior to this update, the gvfs metadata daemon or client applications such as Nautilus terminated unexpectedly when uninitialized internal structures were used for corrupted or unreadable metadata databases. This update adds a missing check that verifies that the metadata database has been loaded properly. As a result, in the described circumstances, an error is returned instead of a crash occurring. (BZ# 1110451 ) The gvfs archive backend no longer crashes due to certain archive file paths Mounting the gvfs archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. (BZ# 713179 )

Commands:
2.8.9.2.6. Listing Options The default list command, iptables -L [<chain-name>] , provides a very basic overview of the default filter table's current chains. Additional options provide more information: -v - Displays verbose output, such as the number of packets and bytes each chain has processed, the number of packets and bytes each rule has matched, and which interfaces apply to a particular rule. -x - Expands numbers into their exact values. On a busy system, the number of packets and bytes processed by a particular chain or rule may be abbreviated to Kilobytes , Megabytes , or Gigabytes . This option forces the full number to be displayed. -n - Displays IP addresses and port numbers in numeric format, rather than the default hostname and network service format. --line-numbers - Lists rules in each chain to their numeric order in the chain. This option is useful when attempting to delete the specific rule in a chain or to locate where to insert a rule within a chain. -t <table-name> - Specifies a table name. If omitted, defaults to the filter table.

Commands:
Appendix H. Revision History Note that revision numbers relate to the edition of this manual, not to version numbers of Red Hat Enterprise Linux. Revision History Revision 1.5-6 Wed Aug 07 2019 Eliane Pereira Revision 1.5-5 Thu Jul 11 2019 Eliane Pereira Image Builder has been removed and split to its own Guide Revision 1.5-4 Fri May 24 2019 Sharon Moroney Preparing document for 7.7 Beta publication. Revision 1.5-3 Tue Oct 30 2018 Vladimir Slavik Preparing document for 7.6 GA publication. Revision 1.5-2 Tue Aug 21 2018 Vladimir Slavik Preparing document for 7.6 Beta publication. Revision 1.5-1 Fri Apr 6 2018 Petr Bokoc Preparing document for 7.5 GA publication. Revision 1.5-0 Fri Dec 15 2017 Petr Bokoc Preparing document for 7.5 Beta publication. Revision 1.4-2 Thu Nov 23 2017 Petr Bokoc Asynchronous update. Revision 1.4-1 Fri Oct 13 2017 Petr Bokoc Asynchronous update. Revision 1.4-0 Tue Aug 1 2017 Petr Bokoc Preparing document for 7.4 GA publication. Revision 1.3-9 Mon May 15 2017 Petr Bokoc Preparing document for 7.4 Beta publication. Revision 1.3-8 Tue Apr 4 2017 Petr Bokoc Asynchronous update. Revision 1.3-7 Sun Nov 6 2016 Robert Kratky Version for 7.3 GA publication. Revision 1.3-4 Mon Nov 16 2015 Petr Bokoc Version for 7.2 GA publication. Revision 1.2-2 Wed Feb 18 2015 Petr Bokoc Version for 7.1 GA publication. Revision 1.0-0 Tue Jun 03 2014 Petr Bokoc Version for 7.0 GA publication.

Commands:
3.5. Basic Image Builder command-line commands The Image Builder command-line interface offers the following sub-commands. Blueprint manipulation List all available blueprints Show a blueprint contents in the TOML format Save (export) blueprint contents in the TOML format into a file BLUEPRINT-NAME.toml Remove a blueprint Push (import) a blueprint file in the TOML format into Image Builder Composing images from blueprints Start a compose Replace BLUEPRINT with name of the blueprint to build and COMPOSE-TYPE with the output image type. List all composes Cancel a running compose Delete a finished compose Show detailed information about a compose Download image file of a compose Related information The composer-cli(1) manual page provides a full list of the available sub-commands and options: The composer-cli tool provides help on the sub-commands and options:

Commands:
composer-cli blueprints list
composer-cli blueprints show BLUEPRINT-NAME
composer-cli blueprints save BLUEPRINT-NAME
composer-cli blueprints delete BLUEPRINT-NAME
composer-cli blueprints push BLUEPRINT-NAME
composer-cli compose start BLUEPRINT COMPOSE-TYPE
composer-cli compose list
composer-cli compose cancel COMPOSE-UUID
composer-cli compose delete COMPOSE-UUID
composer-cli compose info COMPOSE-UUID
composer-cli compose image COMPOSE-UUID
man composer-cli
composer-cli compose list
Chapter 1. Single sign-on in JBoss EAP Single sign-on (SSO) is a process of authenticating identities for multiple clients from a central identity provider. For example, a user needs only one set of login credentials to log in to different applications that use the same SSO provider. JBoss EAP supports the following SSO protocols: OpenID Connect (OIDC) OpenID Connect is an authentication protocol based on the OAuth 2.0 framework of specifications specified in RFC 6749 and RFC 6750 . Security Assertion Mark-up Language v2 (SAML v2) SAML is a data format and protocol that enables the exchange of authentication and authorization information between two parties, typically an identity provider and a service provider. This information is exchanged in the form of SAML tokens that contain assertions, and are issued by Identity Providers to subjects for authenticating with Service Providers. Subjects can reuse SAML tokens issued by an identity provider with multiple service providers, supporting browser-based Single Sign-On in SAML v2. You can use SSO to secure applications deployed on JBoss EAP running on bare metal as well as JBoss EAP running on Red Hat OpenShift Container Platform. For information about securing applications deployed on JBoss EAP running on Red Hat OpenShift Container Platform with SSO, see the Using JBoss EAP on OpenShift Container Platform .

Commands:
Chapter 13. Installing a three-node cluster on Azure In OpenShift Container Platform version 4.16, you can install a three-node cluster on Microsoft Azure. A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster using either installer-provisioned or user-provisioned infrastructure. Note Deploying a three-node cluster using an Azure Marketplace image is not supported. 13.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... If you are deploying a cluster with user-provisioned infrastructure: After you create the Kubernetes manifest files, make sure that the spec.mastersSchedulable parameter is set to true in cluster-scheduler-02-config.yml file. You can locate this file in <installation_directory>/manifests . For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on Azure using ARM templates". Do not create additional worker nodes. Example cluster-scheduler-02-config.yml file for a three-node cluster apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {} 13.2. steps Installing a cluster on Azure with customizations Installing a cluster on Azure using ARM templates

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {}
1.4. Additional Resources To find more information about resource control under systemd , the unit hierarchy, as well as the kernel resource controllers, see the materials listed below: Installed Documentation Cgroup-Related Systemd Documentation The following manual pages contain general information on unified cgroup hierarchy under systemd : systemd.resource-control (5) - describes the configuration options for resource control shared by system units. systemd.unit (5) - describes common options of all unit configuration files. systemd.slice (5) - provides general information about .slice units. systemd.scope (5) - provides general information about .scope units. systemd.service (5) - provides general information about .service units. Controller-Specific Kernel Documentation The kernel-doc package provides a detailed documentation of all resource controllers. This package is included in the Optional subscription channel. Before subscribing to the Optional channel, see the Scope of Coverage Details for Optional software, then follow the steps documented in the article called How to access Optional and Supplementary channels, and -devel packages using Red Hat Subscription Manager (RHSM)? on Red Hat Customer Portal. To install kernel-doc from the Optional channel, type as root : After the installation, the following files will appear under the /usr/share/doc/kernel-doc- <kernel_version> /Documentation/cgroups/ directory: blkio subsystem - blkio-controller.txt cpuacct subsystem - cpuacct.txt cpuset subsystem - cpusets.txt devices subsystem - devices.txt freezer subsystem - freezer-subsystem.txt memory subsystem - memory.txt net_cls subsystem - net_cls.txt Additionally, see the following files on further information about the cpu subsystem: Real-Time scheduling - /usr/share/doc/kernel-doc- <kernel_version> /Documentation/scheduler/sched-rt-group.txt CFS scheduling - /usr/share/doc/kernel-doc- <kernel_version> /Documentation/scheduler/sched-bwc.txt Online Documentation Red Hat Enterprise Linux 7 System Administrator's Guide - The System Administrator's Guide documents relevant information regarding the deployment, configuration, and administration of Red Hat Enterprise Linux 7. This guide contains a detailed explanation of the systemd concepts as well as instructions for service management with systemd . The D-Bus API of systemd - The reference material for D-Bus API commands used to interact with systemd .

Commands:
~]# yum install kernel-doc
9.4. System Devices System devices are critical for the guest to run and cannot be removed. Each system device attached to a guest also takes up an available PCI slot. The default system devices are: Host bridge ISA bridge and USB bridge (The USB and ISA bridges are the same device) Graphics card using the VGA or qxl driver Memory balloon device For information about how to use PCI Express and conventional PCI devices with Intel Q35-based virtual machines, see Using PCI Express and Conventional PCI Devices with the Q35 Virtual Machine .

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-06-26 07:26:18 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 4. Container images with LLVM Toolset on RHEL 8 On RHEL 8, you can build your own LLVM Toolset container images on top of Red Hat Universal Base Images (UBI) containers using Containerfiles. 4.1. Creating a container image of LLVM Toolset on RHEL 8 On RHEL 8, LLVM Toolset packages are part of the Red Hat Universal Base Images (UBIs) repositories. To keep the container image size small, install only individual packages instead of the entire LLVM Toolset. Prerequisites An existing Containerfile. For information on creating Containerfiles, see the Dockerfile reference page. Procedure Visit the Red Hat Container Catalog . Select a UBI. Click Get this image and follow the instructions. To create a container image containing LLVM Toolset, add the following lines to your Containerfile: To create a container image containing an individual package only, add the following lines to your Containerfile: Replace < package-name > with the name of the package you want to install. 4.2. Additional resources For more information on Red Hat UBI images, see Working with Container Images . For more information on Red Hat UBI repositories, see Universal Base Images (UBI): Images, repositories, packages, and source code .

Commands:
FROM registry.access.redhat.com/ubi8/ubi: latest RUN yum module install -y llvm-toolset
RUN yum install -y < package-name >
22.3.2. Mounting the Share Sometimes it is useful to mount a Samba share to a directory so that the files in the directory can be treated as if they are part of the local file system. To mount a Samba share to a directory, create the directory if it does not already exist, and execute the following command as root: This command mounts <sharename> from <servername> in the local directory /mnt/point/ .

Commands:
mount -t smbfs -o username= <username> // <servername> / <sharename> /mnt/point/