mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix C. Using AMQ Broker with the examples The AMQ Ruby examples require a running message broker with a queue named examples . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named examples . USD <broker-instance-dir> /bin/artemis queue create --name examples --address examples --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-05-07 10:16:28 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name examples --address examples --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Chapter 14. Remotely accessing a Wayland-based application You can remotely launch a graphical Wayland-based application on a RHEL server and use it from the remote client on Wayland using waypipe . Note The desktop applications shipped with RHEL 9 support both the Wayland and X11 display protocols. However, Wayland is the preferred option when both are available. 14.1. Enabling waypipe on the client and server To be able to launch an individual application on Wayland, you need to install the waypipe package. Prerequisite Both the client and server use the RHEL 9 operating system. Procedure Install the waypipe package on the local system. Install the waypipe package on the remote system. 14.2. Launching an application remotely using waypipe You can access a graphical application on Wayland on a RHEL server from a remote client using SSH and waypipe . Note This procedure does not work for legacy X11 applications. For X11 applications, see Remotely accessing an individual application on X11 . Prerequisites A Wayland display server is running on your system. On RHEL 9, GNOME as a Wayland compositor is the default. The waypipe package is installed on both the client and the remote system. The application is capable of running natively on Wayland. Procedure Launch the application remotely through waypipe and SSH. Confirm that a server key is valid by checking its fingerprint. Continue connecting by typing yes . When prompted, type the server password. 14.3. Additional resources Remotely accessing an individual application on X11 . Key differences between the Wayland and X11 protocol .

Commands:
dnf install waypipe
dnf install waypipe
[local-user]USD waypipe -c lz4=9 ssh remote-server application-binary The authenticity of host ' remote-server ( 192.168.122.120 )' can't be established. ECDSA key fingerprint is SHA256: uYwFlgtP/2YABMHKv5BtN7nHK9SHRL4hdYxAPJVK/kY . Are you sure you want to continue connecting (yes/no/[fingerprint])?
Warning: Permanently added ' remote-server ' (ECDSA) to the list of known hosts.
remote-user's password: [remote-user]USD
9.7.3. Running NFS Behind a Firewall NFS requires rpcbind , which dynamically assigns ports for RPC services and can cause problems for configuring firewall rules. To allow clients to access NFS shares behind a firewall, edit the /etc/sysconfig/nfs configuration file to control which ports the required RPC services run on. The /etc/sysconfig/nfs may not exist by default on all systems. If it does not exist, create it and add the following variables, replacing port with an unused port number (alternatively, if the file exists, un-comment and change the default entries as required): MOUNTD_PORT= port Controls which TCP and UDP port mountd ( rpc.mountd ) uses. STATD_PORT= port Controls which TCP and UDP port status ( rpc.statd ) uses. LOCKD_TCPPORT= port Controls which TCP port nlockmgr ( lockd ) uses. LOCKD_UDPPORT= port Controls which UDP port nlockmgr ( lockd ) uses. If NFS fails to start, check /var/log/messages . Normally, NFS will fail to start if you specify a port number that is already in use. After editing /etc/sysconfig/nfs , restart the NFS service using service nfs restart . Run the rpcinfo -p command to confirm the changes. To configure a firewall to allow NFS, perform the following steps: Procedure 9.1. Configure a firewall to allow NFS Allow TCP and UDP port 2049 for NFS. Allow TCP and UDP port 111 ( rpcbind / sunrpc ). Allow the TCP and UDP port specified with MOUNTD_PORT=" port " Allow the TCP and UDP port specified with STATD_PORT=" port " Allow the TCP port specified with LOCKD_TCPPORT=" port " Allow the UDP port specified with LOCKD_UDPPORT=" port " Note To allow NFSv4.0 callbacks to pass through firewalls set /proc/sys/fs/nfs/nfs_callback_tcpport and allow the server to connect to that port on the client. This process is not needed for NFSv4.1 or higher, and the other ports for mountd , statd , and lockd are not required in a pure NFSv4 environment. For more information on configuring NFS behind a firewall, see the following Red Hat Knowledgebase articles: How to configure a system as an NFSv3 server which sits behind a firewall with NFS clients outside of the firewall? How can I configure a system as an NFSv4 server which sits behind a firewall with NFS clients outside the firewall? 9.7.3.1. Discovering NFS exports There are two ways to discover which file systems an NFS server exports. First, on any server that supports NFSv2 or NFSv3, use the showmount command: Second, on any server that supports NFSv4, mount / and look around. On servers that support both NFSv4 and either NFSv2 or NFSv3, both methods will work and give the same results. Note Before Red Hat Enterprise Linux 6 on older NFS servers, depending on how they are configured, it is possible to export filesystems to NFSv4 clients at different paths. Because these servers do not enable NFSv4 by default this should not normally be a problem.

Commands:
showmount -e myserver Export list for mysever /exports/ foo /exports/ bar
mount myserver :/ /mnt/ #cd /mnt/ exports ls exports foo bar
Chapter 2. Supported Migration Toolkit for Applications migration paths The Migration Toolkit for Applications (MTA) supports the following migrations: Migrating from third-party enterprise application servers, such as Oracle WebLogic Server, to JBoss Enterprise Application Platform (JBoss EAP). Upgrading to the latest release of JBoss EAP. Migrating from a Windows-only .NET 4.5+ Framework to cross-platform .NET 8.0. (Developer Preview) MTA provides a comprehensive set of rules to assess the suitability of your applications for containerization and deployment on Red Hat OpenShift Container Platform (RHOCP). You can run an MTA analysis to assess your applications' suitability for migration to multiple target platforms. Table 2.1. Supported Java migration paths: Source platform ⇒ Target platform Source platform ⇒ Migration to JBoss EAP 7 & 8 OpenShift (cloud readiness) OpenJDK 11, 17, and 21 Jakarta EE 9 Camel 3 & 4 Spring Boot in Red Hat Runtimes Quarkus Open Liberty Oracle WebLogic Server ✔ ✔ ✔ - - - - - IBM WebSphere Application Server ✔ ✔ ✔ - - - - ✔ JBoss EAP 4 ✘ [a] ✔ ✔ - - - - - JBoss EAP 5 ✔ ✔ ✔ - - - - - JBoss EAP 6 ✔ ✔ ✔ - - - - - JBoss EAP 7 ✔ ✔ ✔ - - - ✔ - Thorntail ✔ [b] - - - - - - - Oracle JDK - ✔ ✔ - - - - - Camel 2 - ✔ ✔ - ✔ - - - Spring Boot - ✔ ✔ ✔ - ✔ ✔ - Any Java application - ✔ ✔ - - - - - Any Java EE application - - - ✔ - - - - [a] Although MTA does not currently provide rules for this migration path, Red Hat Consulting can assist with migration from any source platform to JBoss EAP 7. [b] Requires JBoss Enterprise Application Platform expansion pack 2 (EAP XP 2) .NET migration paths: Source platform ⇒ Target platform (Developer Preview) Source platform ⇒ OpenShift (cloud readiness) Migration to .NET 8.0 .NET Framework 4.5+ (Windows only) ✔ ✔

Commands:
33.7.4. The Printer and Job OptionsTab The Printer Options tab contains various configuration options for the printer media and output. Figure 33.11. Printer Options Tab Page Size - Allows the paper size to be selected. The options include US Letter, US Legal, A3, and A4 Media Source - set to Automatic by default. Change this option to use paper from a different tray. Media Type - Allows you to change paper type. Options include: Plain, thick, bond, and transparency. Resolution - Configure the quality and detail of the printout (default is 300 dots per inch (dpi). Toner Saving - Choose whether the printer uses less toner to conserve resources. You can also configure printer job options using the Job Options tab. Use the drop-menu and choose the job options you wish to use, such as Landscape modes (horizontal or vertical printout), copies , or scaling (increase or decrease the size of the printable area, which can be used to fit an oversize print area onto a smaller physical sheet of print medium).

Commands:
8.33. e2fsprogs 8.33.1. RHBA-2013:1689 - e2fsprogs bug fix update Updated e2fsprogs packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The e2fsprogs packages provide a number of utilities for creating, checking, modifying, and correcting any inconsistencies in the ext2 file systems. Bug Fixes BZ# 922847 Previously, the e2fsck utility was unable to detect inconsistencies related to overlapping interior or leaf nodes in the extent tree. As a consequence, some of ext4 extent tree corruptions were not detected or repaired by e2fsck but they were detected by the kernel at run time. With this update, e2fsck is able to detect and repair the described problems as expected. BZ# 994615 Previously, the e2fsck utility incorrectly detected uninitialized extents past end of file (EOF) as invalid. Consequently, e2fsck identified pre-allocated blocks past EOF as corrupt. This bug has been fixed and e2fsck now identifies uninitialized extents past EOF correctly. BZ# 873201 The resize2fs utility did not properly handle resizing of an ext4 file system to a smaller size. As a consequence, files containing many extents could become corrupted if they were moved during the resize process. With this update, resize2fs maintains a consistent extent tree when moving files containing many extents, and such files no longer become corrupted in the described scenario. BZ# 974975 Previously, the resize2fs utility did not correctly relocate inode and block bitmaps when resizing an ext4 file system to a smaller size. Consequently, some file systems became corrupted when the bitmaps were not moved within the new file system size. A patch has been provided to address this bug and resize2fs now maintains a consistent file system in the described scenario. BZ# 885083 Previously, the e2fsck utility failed to store information about file system errors correctly. Consequently, entries in the journal were sometimes not properly propagated to the file system superblock. This bug has been fixed and e2fsck now handles all file system errors as expected. BZ# 895679 Previously, the e2fsck utility did not clear the error log when processing an ext4 file system. Consequently, e2fsck stored detailed error information in the ext4 file system superblock and returned it periodically upon mounting. With this update, the error log is cleared when e2fsck completes and the redundant error messages are no longer returned. BZ# 927541 Prior to this update, the filefrag utility occasionally reported incorrect extent counts. A patch has been applied to address this problem and extents are now counted correctly. Users of e2fsprogs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
7.194. python-nss 7.194.1. RHBA-2013:0405 - python-nss bug fix and enhancement update Updated python-nss packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The python-nss packages provide bindings for Network Security Services (NSS) that allow Python programs to use the NSS cryptographic libraries for SSL/TLS and PKI certificate management. Note The python-nss packages have been upgraded to upstream version 0.13, which provides a number of bug fixes and enhancements over the version. (BZ#827616) Bug Fixes BZ# 698663 On the 64-bit architecture, the setup_certs.py script contained an incorrect path to the libnssckbi.so library. As a consequence, the script attempted to run the "modutil -dbdir pki -add ca_certs -libfile /usr/lib/libnssckbi.so" command and failed with an error, because on this architecture, the libnssckbi.so library is located in the /usr/lib64/ directory. This update allows the modutil command-line utility to find the libnssckbi.so module based on its knowledge of the system. BZ# 796295 When setting Basic Constraints for a CA certificate, the python-nss package failed with the following message: This was because of an incorrect format specifier, which is now fixed and python-nss no longer fails in this scenario. Enhancement BZ# 642795 The python-nss package has been updated to add support for PKCS#12 files. Users of python-nss are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
cannot decode Basic Constraints
Chapter 11. Configuring kube-rbac-proxy for Eventing The kube-rbac-proxy component provides internal authentication and authorization capabilities for Knative Eventing. 11.1. Configuring kube-rbac-proxy resources for Eventing You can globally override resource allocation for the kube-rbac-proxy container by using the OpenShift Serverless Operator CR. Note You can also override resource allocation for a specific deployment. The following configuration sets Knative Eventing kube-rbac-proxy minimum and maximum CPU and memory allocation: KnativeEventing CR example apiVersion: operator.knative.dev/v1beta1 kind: KnativeEventing metadata: name: knative-eventing namespace: knative-eventing spec: config: deployment: "kube-rbac-proxy-cpu-request": "10m" 1 "kube-rbac-proxy-memory-request": "20Mi" 2 "kube-rbac-proxy-cpu-limit": "100m" 3 "kube-rbac-proxy-memory-limit": "100Mi" 4 1 Sets minimum CPU allocation. 2 Sets minimum RAM allocation. 3 Sets maximum CPU allocation. 4 Sets maximum RAM allocation.

Commands:
apiVersion: operator.knative.dev/v1beta1 kind: KnativeEventing metadata: name: knative-eventing namespace: knative-eventing spec: config: deployment: "kube-rbac-proxy-cpu-request": "10m" 1 "kube-rbac-proxy-memory-request": "20Mi" 2 "kube-rbac-proxy-cpu-limit": "100m" 3 "kube-rbac-proxy-memory-limit": "100Mi" 4
Chapter 4. Configuring Red Hat Ansible Automation Platform Service on AWS After you subscribe to Ansible Automation Platform Service on AWS and gain access to Ansible Automation Platform, you must configure your automation mesh nodes and set up your automation jobs. For help with configuring your automation mesh see Automation mesh for managed cloud or operator environments . Warning Do not change the "Gateway proxy URL" settings. Altering the gateway proxy might cause false outages on the status page.

Commands:
2.2. Hardware Recommendations A basic user entry is about 1 KB in size, as is a simple host entry with a certificate. The most important hardware feature to size properly is RAM. While all deployments are different, depending on the number of users and groups and the type of data stored, there is a rule of thumb to use to help determine how much RAM to use: For 10,000 users and 100 groups, have at least 2GB of RAM and 1GB swap space. For 100,000 users and 50,000 groups, have at least 16GB of RAM and 4GB of swap space. Note For larger deployments, it is more effective to increase the RAM than to increase disk space because much of the data are stored in cache. The underlying Directory Server instance used by the IdM server can be tuned to increase performance. For tuning information, see the Directory Server documentation .

Commands:
Chapter 2. Deployment Scenarios There are three deployment scenarios for Red Hat Satellite in Amazon Web Services: One-region setup Connecting on-premises and AWS region Connecting different regions Figure 2.1. Scenario 1: One-region setup The least complex configuration of Satellite Server in Amazon Web Services consists of both Satellite Server and the content hosts residing within the same region and within the Virtual Private Cloud (VPC). You can also use a different availability zone. Scenario 2: Connecting on-premises and AWS region Create a VPN connection between the on-premises location and the AWS region where the Capsule is located. It is also possible to use the external host name of Satellite Server when you register the instance that runs Capsule Server. Option 1: Site-to-site VPN connection between the AWS region and the on-premises datacenter Option 2: Direct connection using the external DNS host name Scenario 3: Connecting different regions Create a site-to-site VPN connection between different regions so that you can use the internal DNS host name when you register the instance that runs Capsule Server to Satellite Server. If you do not establish a site-to-site VPN connection, use the external DNS host name when you register the instance that runs Capsule Server to Satellite Server. Note Most public cloud providers do not charge for data being transferred into a region or between availability zones within a single region. However, they do charge for data leaving the region to the Internet. Option 1: Site-to-site VPN connection between AWS regions Option 2: Direct connection using the external DNS host name

Commands:
4.2. tuned and tuned-adm tuned is a tuning profile delivery mechanism that adapts Red Hat Enterprise Linux for certain workload characteristics, such as requirements for CPU-intensive tasks, or storage/network throughput responsiveness. It can react to changes in CPU and network use and adjust settings to improve performance in active devices, or reduce power consumption in inactive devices. The accompanying ktune partners with the tuned-adm tool to provide a number of tuning profiles that are pre-configured to enhance performance and reduce power consumption in a number of specific use cases. Edit these profiles or create new profiles to create performance solutions tailored to your environment. The virtualization-related profiles provided as part of tuned-adm include: virtual-guest Based on the enterprise-storage profile, virtual-guest also decreases the swappiness of virtual memory. This profile is available in Red Hat Enterprise Linux 6.3 and later, and is the recommended profile for guest machines. virtual-host Based on the enterprise-storage profile, virtual-host also decreases the swappiness of virtual memory and enables more aggressive writeback of dirty pages. This profile is available in Red Hat Enterprise Linux 6.3 and later, and is the recommended profile for virtualization hosts, including both KVM and Red Hat Enterprise Virtualization hosts. Install the tuned package and its associated systemtap scripts with the command: Installing the tuned package also sets up a sample configuration file at /etc/tuned.conf and activates the default profile. Start tuned by running: To start tuned every time the machine boots, run: To list all available profiles and identify the current active profile, run: To only display the currently active profile, run: To switch to one of the available profiles, run: For example, to switch to the virtual-host profile, run: Note It is possible to create custom tuned profiles to encapsulate a set of tuning parameters. For instructions on creating custom tuned profiles, refer to the tuned.conf man page. In some cases, it is preferable to disable tuned to use parameters set manually. To disable all tuning, run: Note Refer to the Red Hat Enterprise Linux 6 Power Management Guide for further information about tuned , tuned-adm and ktune .

Commands:
install tuned
service tuned start
chkconfig tuned on
tuned-adm list Available profiles: - latency-performance - sap - virtual-guest - laptop-battery-powersave - virtual-host - enterprise-storage - desktop-powersave - spindown-disk - default - throughput-performance - laptop-ac-powersave - server-powersave Current active profile: default
tuned-adm active
tuned-adm profile profile_name
tuned-adm profile virtual-host
tuned-adm off
Chapter 4. Performance impact of alt-java The alt-java binary contains the SSB mitigation, so the SSB mitigation performance impact no longer exists on java . Note Using alt-java might significantly reduce the performance of Java programs. You can find detailed information of some Java performance issues that might exist with using alt-java by selecting any of the Red Hat Bugzilla links listed in the Additional resources section. Additional resources (java-11-openjdk) Seccomp related performance regression in RHEL8 . (java-1.8.0-openjdk) Seccomp related performance regression in RHEL8 . CVE-2018-3639 Detail . CVE-2018-3639 hw: cpu: speculative store bypass . CVE-2018-3639 java-1.8.0-openjdk: hw: cpu: speculative store bypass (rhel-7.6) Revised on 2024-05-09 16:48:44 UTC

Commands:
16.2. Managing Disk Quotas If quotas are implemented, they need some maintenance - mostly in the form of watching to see if the quotas are exceeded and making sure the quotas are accurate. Of course, if users repeatedly exceed their quotas or consistently reach their soft limits, a system administrator has a few choices to make depending on what type of users they are and how much disk space impacts their work. The administrator can either help the user determine how to use less disk space or increase the user's disk quota. 16.2.1. Enabling and Disabling It is possible to disable quotas without setting them to 0. To turn all user and group quotas off, use the following command: If neither the -u or -g options are specified, only the user quotas are disabled. If only -g is specified, only group quotas are disabled. The -v switch causes verbose status information to display as the command executes. To enable quotas again, use the quotaon command with the same options. For example, to enable user and group quotas for all file systems, use the following command: To enable quotas for a specific file system, such as /home , use the following command: If neither the -u or -g options are specified, only the user quotas are enabled. If only -g is specified, only group quotas are enabled.

Commands:
quotaoff -vaug
quotaon -vaug
quotaon -vug /home