mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Architectures Red Hat Enterprise Linux 9.3 is distributed with the kernel version 5.14.0-362.8.1, which provides support for the following architectures at the minimum required version (stated in parentheses): AMD and Intel 64-bit architectures (x86-64-v2) The 64-bit ARM architecture (ARMv8.0-A) IBM Power Systems, Little Endian (POWER9) 64-bit IBM Z (z14) Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures .

Commands:
Chapter 5. Managing Ceph daemons As a storage administrator, you can manage Ceph daemons on the Red Hat Ceph Storage dashboard. 5.1. Daemon actions The Red Hat Ceph Storage dashboard allows you to start, stop, restart, and redeploy daemons. Note These actions are supported on all daemons except monitor and manager daemons. Prerequisites A running Red Hat Ceph Storage cluster. Dashboard is installed. At least one daemon is configured in the storage cluster. Procedure You can manage daemons two ways. From the Services page: Log in to the dashboard. From the Cluster drop-down menu, select Services . View the details of the service with the daemon to perform the action on by clicking the Expand/Collapse icon on its row. In Details , select the drop down to the desired daemon to perform Start , Stop , Restart , or Redeploy . Figure 5.1. Managing daemons From the Hosts page: Log in to the dashboard. From the Cluster drop-down menu, select Hosts . From the Hosts List , select the host with the daemon to perform the action on. In the Daemon tab of the host, click the daemon. Use the drop down at the top to perform Start , Stop , Restart , or Redeploy . Figure 5.2. Managing daemons

Commands:
4.234. postgresql 4.234.1. RHSA-2012:0678 - Moderate: postgresql and postgresql84 security update Updated postgresql84 and postgresql packages that fix three security issues are now available for Red Hat Enterprise Linux 5 and 6 respectively. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. PostgreSQL is an advanced object-relational database management system (DBMS). Security Fixes CVE-2012-0868 The pg_dump utility inserted object names literally into comments in the SQL script it produces. An unprivileged database user could create an object whose name includes a newline followed by an SQL command. This SQL command might then be executed by a privileged user during later restore of the backup dump, allowing privilege escalation. CVE-2012-0867 When configured to do SSL certificate verification, PostgreSQL only checked the first 31 characters of the certificate's Common Name field. Depending on the configuration, this could allow an attacker to impersonate a server or a client using a certificate from a trusted Certificate Authority issued for a different name. CVE-2012-0866 CREATE TRIGGER did not do a permissions check on the trigger function to be called. This could possibly allow an authenticated database user to call a privileged trigger function on data of their choosing. These updated packages upgrade PostgreSQL to version 8.4.11, which fixes these issues as well as several data-corruption issues and lesser non-security issues. Refer to the PostgreSQL Release Notes for a full list of changes: http://www.postgresql.org/docs/8.4/static/release.html All PostgreSQL users are advised to upgrade to these updated packages, which correct these issues. If the postgresql service is running, it will be automatically restarted after installing this update.

Commands:
Chapter 56. CruiseControlTemplate schema reference Used in: CruiseControlSpec Property Property type Description deployment DeploymentTemplate Template for Cruise Control Deployment . pod PodTemplate Template for Cruise Control Pods . apiService InternalServiceTemplate Template for Cruise Control API Service . podDisruptionBudget PodDisruptionBudgetTemplate Template for Cruise Control PodDisruptionBudget . cruiseControlContainer ContainerTemplate Template for the Cruise Control container. tlsSidecarContainer ContainerTemplate The tlsSidecarContainer property has been deprecated. Template for the Cruise Control TLS sidecar container. serviceAccount ResourceTemplate Template for the Cruise Control service account.

Commands:
1.2. High Availability Add-On Introduction The High Availability Add-On is an integrated set of software components that can be deployed in a variety of configurations to suit your needs for performance, high availability, load balancing, scalability, file sharing, and economy. The High Availability Add-On consists of the following major components: Cluster infrastructure - Provides fundamental functions for nodes to work together as a cluster: configuration-file management, membership management, lock management, and fencing. High availability Service Management - Provides failover of services from one cluster node to another in case a node becomes inoperative. Cluster administration tools - Configuration and management tools for setting up, configuring, and managing the High Availability Add-On. The tools are for use with the Cluster Infrastructure components, the high availability and Service Management components, and storage. You can supplement the High Availability Add-On with the following components: Red Hat GFS2 (Global File System 2) - Part of the Resilient Storage Add-On, this provides a cluster file system for use with the High Availability Add-On. GFS2 allows multiple nodes to share storage at a block level as if the storage were connected locally to each cluster node. GFS2 cluster file system requires a cluster infrastructure. Cluster Logical Volume Manager (CLVM) - Part of the Resilient Storage Add-On, this provides volume management of cluster storage. CLVM support also requires cluster infrastructure. Load Balancer Add-On - Routing software that provides IP-Load-balancing. the Load Balancer Add-On runs in a pair of redundant virtual servers that distributes client requests evenly to real servers that are behind the virtual servers.

Commands:
Chapter 1. System Requirements 1.1. Installation Prerequisites Red Hat Developer Toolset 12.0 contains packages for Red Hat Enterprise Linux 7 and supports the following architectures: AMD64 and Intel 64 IBM POWER, big endian IBM POWER, little endian 64-bit IBM Z Generation and manipulation of 32-bit binaries is also supported on the AMD64 and Intel 64 architectures. Note In Red Hat Enterprise Linux 8, GCC Toolset is available, which provides tools similar to Red Hat Developer Toolset. For details, see Using GCC Toolset . Before installing Red Hat Developer Toolset 12.0, it is recommended to apply all available Red Hat Enterprise Linux errata updates. This will enable all Red Hat Developer Toolset features and apply fixes that can otherwise impact the tools or built code. Red Hat Developer Toolset 12.0 requires systems to be subscribed to the Optional repository in order to access all the necessary dependent packages required by the Red Hat Developer Toolset toolchain. Packages from the Optional repository are listed in the Red Hat Software Collections 3.8 Release Notes . If you use Red Hat Subscription Manager, you can add these repositories by navigating to Applications System Tools Red Hat Subscription Manager . Then enable the Optional repository for your system. For detailed information, see https://access.redhat.com/solutions/392003 . Users of Red Hat Satellite can enable the Optional repository by following the instructions at https://access.redhat.com/solutions/70019 . Since Red Hat Developer Toolset 4.1, the content is available also in the ISO format at https://access.redhat.com/downloads , specifically for Server and Workstation . Note Packages that require the Optional repository cannot be installed from the ISO image. A list of packages that require enabling of the Optional repository is provided in the Red Hat Software Collections Release Notes . Beta content is unavailable in the ISO format. 1.2. Installation and Upgrading Use of Red Hat Developer Toolset 12.0 requires the removal of any earlier pre-release versions, including Beta releases. If you have installed any version of Red Hat Developer Toolset, uninstall it from your system as described in the Uninstalling Red Hat Developer Toolset section of the Red Hat Developer Toolset User Guide . Note that installing Red Hat Developer Toolset 12.x in parallel with Red Hat Developer Toolset 11.x is supported. For detailed information on installation of Red Hat Developer Toolset 12.0 see the Installing Red Hat Developer Toolset chapter of the Red Hat Developer Toolset User Guide . The in-place upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 is not supported by Red Hat Developer Toolset. As a consequence, the installed components might not work correctly after the upgrade. If you want to upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7, it is strongly recommended to remove all Red Hat Developer Toolset packages, perform the in-place upgrade, update the Red Hat Developer Toolset repository, and install the Red Hat Developer Toolset packages again. It is advisable to back up all data before upgrading.

Commands:
Chapter 23. Postfix Postfix is an open-source Mail Transport Agent ( MTA ), which supports protocols like LDAP, SMTP AUTH (SASL), and TLS. [22] In Red Hat Enterprise Linux, the postfix package provides Postfix. Enter the following command to see if the postfix package is installed: If it is not installed, use the yum utility root to install it: 23.1. Postfix and SELinux When Postfix is enabled, it runs confined by default. Confined processes run in their own domains, and are separated from other confined processes. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited. The following example demonstrates the Postfix and related processes running in their own domain. This example assumes the postfix package is installed and that the Postfix service has been started: Run the getenforce command to confirm SELinux is running in enforcing mode: The command returns Enforcing when SELinux is running in enforcing mode. Enter the following command as the root user to start postfix : Confirm that the service is running. The output should include the information below (only the time stamp will differ): Run following command to view the postfix processes: In the output above, the SELinux context associated with the Postfix master process is system_u:system_r:postfix_master_t:s0 . The second last part of the context, postfix_master_t , is the type for this process. A type defines a domain for processes and a type for files. In this case, the master process is running in the postfix_master_t domain. [22] For more information, see the Postfix section in the System Administrator's Guide .

Commands:
~]USD rpm -q postfix package postfix is not installed
~]# yum install postfix
~]USD getenforce Enforcing
~]# systemctl start postfix.service
~]# systemctl status postfix.service postfix.service - Postfix Mail Transport Agent Loaded: loaded (/usr/lib/systemd/system/postfix.service; disabled) Active: active (running) since Mon 2013-08-05 11:38:48 CEST; 3h 25min ago
~]USD ps -eZ | grep postfix system_u:system_r:postfix_master_t:s0 1651 ? 00:00:00 master system_u:system_r:postfix_pickup_t:s0 1662 ? 00:00:00 pickup system_u:system_r:postfix_qmgr_t:s0 1663 ? 00:00:00 qmgr
probe::scsi.iodispatching Name probe::scsi.iodispatching - SCSI mid-layer dispatched low-level SCSI command Synopsis scsi.iodispatching Values device_state The current state of the device request_bufflen The request buffer length request_buffer The request buffer address dev_id The scsi device id data_direction_str Data direction, as a string req_addr The current struct request pointer, as a number device_state_str The current state of the device, as a string lun The lun number data_direction The data_direction specifies whether this command is from/to the device 0 (DMA_BIDIRECTIONAL), 1 (DMA_TO_DEVICE), 2 (DMA_FROM_DEVICE), 3 (DMA_NONE) channel The channel number host_no The host number

Commands:
6.2. Creating a Striped Logical Volume This example creates an LVM striped logical volume called striped_logical_volume that stripes data across the disks at /dev/sda1 , /dev/sdb1 , and /dev/sdc1 . 6.2.1. Creating the Physical Volumes Label the disks you will use in the volume groups as LVM physical volumes. Warning This command destroys any data on /dev/sda1 , /dev/sdb1 , and /dev/sdc1 .

Commands:
pvcreate /dev/sda1 /dev/sdb1 /dev/sdc1 Physical volume "/dev/sda1" successfully created Physical volume "/dev/sdb1" successfully created Physical volume "/dev/sdc1" successfully created
13.9. Additional Resources The following resources offer additional information on LDAP. It is highly recommended that you review these, especially the OpenLDAP website and the LDAP HOWTO, before configuring LDAP on your system(s). 13.9.1. Installed Documentation /usr/share/docs/openldap- <versionnumber> / directory - Contains a general README document and miscellaneous information. LDAP related man pages - There are a number of man pages for the various applications and configuration files involved with LDAP. The following is a list of some of the more important man pages. Client Applications man ldapadd - Describes how to add entries to an LDAP directory. man ldapdelete - Describes how to delete entries within an LDAP directory. man ldapmodify - Describes how to modify entries within an LDAP directory. man ldapsearch - Describes how to search for entries within an LDAP directory. man ldappasswd - Describes how to set or change the password of an LDAP user. Server Applications man slapd - Describes command line options for the LDAP server. man slurpd - Describes command line options for the LDAP replication server. Administrative Applications man slapadd - Describes command line options used to add entries to a slapd database. man slapcat - Describes command line options used to generate an LDIF file from a slapd database. man slapindex - Describes command line options used to regenerate an index based upon the contents of a slapd database. man slappasswd - Describes command line options used to generate user passwords for LDAP directories. Configuration Files man ldap.conf - Describes the format and options available within the configuration file for LDAP clients. man slapd.conf - Describes the format and options available within the configuration file referenced by both the LDAP server applications ( slapd and slurpd ) and the LDAP administrative tools ( slapadd , slapcat , and slapindex ).

Commands:
Chapter 5. Limiting access to cost management resources After you add and configure integrations in cost management, you can limit access to cost data and resources. You might not want users to have access to all of your cost data. Instead, you can grant users access only to data that is specific to their projects or organizations. With role-based access control, you can limit the visibility of resources in cost management reports. For example, you can restrict a user's view to only AWS integrations, rather than the entire environment. To learn how to limit access, see the more in-depth guide Limiting access to cost management resources .

Commands:
1.2. KVM Performance Architecture Overview The following points provide a brief overview of KVM as it pertains to system performance and process/thread management: When using KVM, guests run as a Linux process on the host. Virtual CPUs (vCPUs) are implemented as normal threads, handled by the Linux scheduler. Guests inherit features such as NUMA and Huge Pages from the kernel. Disk and network I/O settings in the host have a significant performance impact. Network traffic typically travels through a software-based bridge.

Commands:
5.277. redhat-release 5.277.1. RHEA-2012:0971 - redhat-release enhancement update for Red Hat Enterprise Linux 6.3 An enhanced redhat-release package is now available for Red Hat Enterprise Linux 6.3. The redhat-release package contains licensing information regarding, and identifies the installed version of, Red Hat Enterprise Linux. This updated redhat-release package reflects changes made for the release of Red Hat Enterprise Linux 6.3. Users of Red Hat Enterprise Linux 6 are advised to upgrade to this updated redhat-release package, which adds this enhancement.

Commands:
Chapter 4. Deprecated features This section describes features that are supported, but have been deprecated from AMQ Broker. queues configuration element Starting in 7.10, the <queues> configuration element is deprecated. You can use the <addresses> configuration element to create addresses and associated queues. The <queues> configuration element will be removed in a future release. getAddressesSettings method Starting in 7.10, the get Addresses Settings method, which is included in the org.apache.activemq.artemis.core.config.Configuration interface, is deprecated. Use the get Address Settings method to configure addresses and queues for the broker programatically. OpenWire protocol Starting in 7.9, the OpenWire protocol is a deprecated feature. If you are creating a new AMQ Broker-based system, use one of the other supported protocols. This feature will be removed in a future release. Adding users when broker instance is not running Starting in 7.8, when an AMQ Broker instance is not running, the ability to add users to the broker from the CLI interface is removed. Network pinger Starting in 7.5, network pinging is a deprecated feature. Network pinging cannot protect a broker cluster from network isolation issues that can lead to irrecoverable message loss. This feature will be removed in a future release. Red Hat continues to support existing AMQ Broker deployments that use network pinging. However, Red Hat no longer recommends use of network pinging in new deployments. For guidance on configuring a broker cluster for high availability and to avoid network isolation issues, see Implementing high availability in Configuring AMQ Broker . Hawtio dispatch console plugin Starting in 7.3, AMQ Broker no longer ships with the Hawtio dispatch console plugin, dispatch-hawtio-console.war . Previously, the dispatch console was used to manage AMQ Interconnect. However, AMQ Interconnect now uses its own, standalone web console.

Commands:
Chapter 2. Understanding update channels You can use update channels to specify which Red Hat OpenShift AI minor version you intend to update your Operator to. Update channels also allow you to choose the timing and level of support your updates have through the fast , stable , stable-x.y eus-x.y , and alpha channel options. The subscription of an installed Operator specifies the update channel, which is used to track and receive updates for the Operator. You can change the update channel to start tracking and receiving updates from a newer channel. For more information about the release frequency and the lifecycle associated with each of the available update channels, see the Red Hat OpenShift AI Self-Managed Life Cycle Knowledgebase article. Channel Support Release frequency Recommended environment fast One month of full support Every month Production environments with access to the latest product features. Select this streaming channel with automatic updates to avoid manually upgrading every month. stable Three months of full support Every three months Production environments with stability prioritized over new feature availability. Select this streaming channel with automatic updates to access the latest stable release and avoid manually upgrading. stable-x.y Seven months of full support Every three months Production environments with stability prioritized over new feature availability. Select numbered stable channels (such as stable-2.10 ) to plan and upgrade to the stable release while keeping your deployment under full support. eus-x.y Seven months of full support followed by Extended Update Support for eleven months Every nine months Enterprise-grade environments that cannot upgrade within a seven month window. Select this streaming channel if you prioritize stability over new feature availability. alpha One month of full support Every month Development environments with early-access features that might not be functionally complete. Select this channel to use early-access features to test functionality and provide feedback during the development process. Early-access features are not supported with Red Hat production service level agreements (SLAs). For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . For more information about the support scope of Red Hat Developer Preview features, see Developer Preview Features Support Scope . Note The embedded and beta channels are legacy channels that will be removed in a future release. Do not select the embedded or beta channels for a new Operator installation.

Commands:
Chapter 4. Resolved issues The following issues are resolved for this release: Issue Summary JBCS-1700 [RHEL9] Upgrade mod_jk to 1.2.49 to be in sync with the version used by all other JBCS releases JBCS-1678 [RHEL9] Upgrade mod_proxy_cluster to 1.3.20 to be in sync with the version used by all other JBCS releases JBCS-1642 mod_proxy_cluster returns 404 now instead of 503 when there's no matching context JBCS-1476 jbcs-httpd24-httpd has no dependency to jbcs-httpd24-brotli JBCS-1460 mod_cluster leaks memory with httpd 2.4.53+ JBCS-1369 mod_cluster returns rare but unexpected 404/503 JBCS-1179 [Doc] Review the prerequisite package for RHEL8 For details of any security fixes in this release, see the errata links in Advisories related to this release .

Commands:
28.6.3. Upgrading Your Computer A boot option, upgrade , has been superceded by a stage in the installation process where the installation program prompts you to upgrade or reinstall earlier versions of Red Hat Enterprise Linux that it detects on your system. However, the installation program may not correctly detect a version of Red Hat Enterprise Linux if the contents of the /etc/redhat-release file have changed. The boot option upgradeany relaxes the test that the installation program performs and allows you to upgrade a Red Hat Enterprise Linux installation that the installation program has not correctly identified.

Commands: