mtpti5iD/redhat-docs_dataset huggingface dataset:
7.2. Using Multiple SSSD Configuration Files on a Per-client Basis The default configuration file for SSSD is /etc/sssd/sssd.conf . Apart from this file, SSSD can read its configuration from all *.conf files in the /etc/sssd/conf.d/ directory. For example, this allows you to use the default /etc/sssd/sssd.conf file on all clients and add additional settings in further configuration files to extend the functionality individually on a per-client basis. How SSSD Processes the Configuration Files SSSD reads the configuration files in this order: The primary /etc/sssd/sssd.conf file Other *.conf files in /etc/sssd/conf.d/ , in alphabetical order If the same parameter appears in multiple configuration files, SSSD uses the last read parameter. Note SSSD does not read hidden files (files starting with . ) in the conf.d directory.

Commands:
Chapter 40. InternalServiceTemplate schema reference Used in: CruiseControlTemplate , KafkaBridgeTemplate , KafkaClusterTemplate , KafkaConnectTemplate , ZookeeperClusterTemplate Property Property type Description metadata MetadataTemplate Metadata applied to the resource. ipFamilyPolicy string (one of [RequireDualStack, SingleStack, PreferDualStack]) Specifies the IP Family Policy used by the service. Available options are SingleStack , PreferDualStack and RequireDualStack . SingleStack is for a single IP family. PreferDualStack is for two IP families on dual-stack configured clusters or a single IP family on single-stack clusters. RequireDualStack fails unless there are two IP families on dual-stack configured clusters. If unspecified, OpenShift will choose the default value based on the service type. ipFamilies string (one or more of [IPv6, IPv4]) array Specifies the IP Families used by the service. Available options are IPv4 and IPv6 . If unspecified, OpenShift will choose the default value based on the ipFamilyPolicy setting.

Commands:
Chapter 103. KafkaUserSpec schema reference Used in: KafkaUser Property Property type Description authentication KafkaUserTlsClientAuthentication , KafkaUserTlsExternalClientAuthentication , KafkaUserScramSha512ClientAuthentication Authentication mechanism enabled for this Kafka user. The supported authentication mechanisms are scram-sha-512 , tls , and tls-external . scram-sha-512 generates a secret with SASL SCRAM-SHA-512 credentials. tls generates a secret with user certificate for mutual TLS authentication. tls-external does not generate a user certificate. But prepares the user for using mutual TLS authentication using a user certificate generated outside the User Operator. ACLs and quotas set for this user are configured in the CN=<username> format. Authentication is optional. If authentication is not configured, no credentials are generated. ACLs and quotas set for the user are configured in the <username> format suitable for SASL authentication. authorization KafkaUserAuthorizationSimple Authorization rules for this Kafka user. quotas KafkaUserQuotas Quotas on requests to control the broker resources used by clients. Network bandwidth and request rate quotas can be enforced.Kafka documentation for Kafka User quotas can be found at http://kafka.apache.org/documentation/#design_quotas . template KafkaUserTemplate Template to specify how Kafka User Secrets are generated.

Commands:
1.4. DM Multipath Components Table 1.1, "DM Multipath Components" . describes the components of DM Multipath. Table 1.1. DM Multipath Components Component Description dm_multipath kernel module Reroutes I/O and supports failover for paths and path groups. mpathconf utility Configures and enables device mapper multipathing. multipath command Lists and configures multipath devices. Normally started with /etc/rc.sysinit , it can also be started by a udev program whenever a block device is added. multipathd daemon Monitors paths; as paths fail and come back, it may initiate path group switches. Allows interactive changes to multipath devices. The daemon must be restarted following any changes to the /etc/multipath.conf file. kpartx command Creates device mapper devices for the partitions on a device. It is necessary to use this command for DOS-based partitions with DM Multipath. The kpartx command is provided in its own package, but the device-mapper-multipath package depends on it.

Commands:
function::tcpmib_filter_key Name function::tcpmib_filter_key - Default filter function for tcpmib.* probes Synopsis Arguments sk pointer to the struct sock being acted on op value to be counted if sk passes the filter Description This function is a default filter function. The user can replace this function with their own. The user-supplied filter function returns an index key based on the values in sk . A return value of 0 means this particular sk should be not be counted.

Commands:
tcpmib_filter_key:long(sk:long,op:long)
Chapter 1. Metadata APIs 1.1. APIRequestCount [apiserver.openshift.io/v1] Description APIRequestCount tracks requests made to an API. The instance name must be of the form resource.version.group , matching the resource. Compatibility level 1: Stable within a major release for a minimum of 12 months or 3 minor releases (whichever is longer). Type object 1.2. Binding [v1] Description Binding ties one object to another; for example, a pod is bound to a node by a scheduler. Deprecated in 1.7, please use the bindings subresource of pods instead. Type object 1.3. ComponentStatus [v1] Description ComponentStatus (and ComponentStatusList) holds the cluster validation info. Deprecated: This API is deprecated in v1.19+ Type object 1.4. ConfigMap [v1] Description ConfigMap holds configuration data for pods to consume. Type object 1.5. ControllerRevision [apps/v1] Description ControllerRevision implements an immutable snapshot of state data. Clients are responsible for serializing and deserializing the objects that contain their internal state. Once a ControllerRevision has been successfully created, it can not be updated. The API Server will fail validation of all requests that attempt to mutate the Data field. ControllerRevisions may, however, be deleted. Note that, due to its use by both the DaemonSet and StatefulSet controllers for update and rollback, this object is beta. However, it may be subject to name and representation changes in future releases, and clients should not depend on its stability. It is primarily for internal use by controllers. Type object 1.6. Event [events.k8s.io/v1] Description Event is a report of an event somewhere in the cluster. It generally denotes some state change in the system. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data. Type object 1.7. Event [v1] Description Event is a report of an event somewhere in the cluster. Events have a limited retention time and triggers and messages may evolve with time. Event consumers should not rely on the timing of an event with a given Reason reflecting a consistent underlying trigger, or the continued existence of events with that Reason. Events should be treated as informative, best-effort, supplemental data. Type object 1.8. Lease [coordination.k8s.io/v1] Description Lease defines a lease concept. Type object 1.9. Namespace [v1] Description Namespace provides a scope for Names. Use of multiple namespaces is optional. Type object

Commands:
Appendix B. Revision History Revision History Revision 0.2-0 Thu Aug 02 2018 Lenka Spackova Temporarily removed a known issue that needs to be verified and updated (Storage). Revision 0.1-9 Fri Jul 20 2018 Lenka Spackova Fixed a known issue related to I/O requests to the block device (Storage). Revision 0.1-8 Fri Mar 16 2018 Lenka Spackova Updated a life cycle note. Revision 0.1-7 Wed Nov 29 2017 Lenka Spackova Added an OpenSSL known issue. Revision 0.1-6 Mon Sep 04 2017 Lenka Spackova Added a known issue to General Updates. Revision 0.1-5 Mon Jul 03 2017 Jiri Herrmann Added a Virtualization known issue. Added a Kernel known issue. Revision 0.1-2 Thu Apr 27 2017 Lenka Spackova Red Hat Access Labs renamed to Red Hat Customer Portal Labs. Revision 0.1-1 Fri Mar 31 2017 Lenka Spackova Added a known issue to Virtualization. Revision 0.1-0 Tue Mar 28 2017 Lenka Spackova Added a feature and three known issues to Virtualization. Revision 0.0-8 Tue Mar 21 2017 Lenka Spackova Release of the Red Hat Enterprise Linux 6.9 Release Notes. Revision 0.0-4 Thu Jan 05 2017 Lenka Spackova Release of the Red Hat Enterprise Linux 6.9 Beta Release Notes.

Commands:
Preface The Red Hat Ansible Certified Content Collection for Red Hat JBoss Enterprise Application Platform is a prepackaged Ansible content collection that Red Hat provides. You can use the Red Hat Ansible Certified Content Collection to automate the installation and configuration of the Red Hat JBoss Enterprise Application Platform product. You can also add customized tasks to your playbook to automate the deployment of JBoss EAP applications either at the same time as the automated product installation or later. Note The rest of this document refers to the Red Hat Ansible Certified Content Collection for Red Hat JBoss Enterprise Application Platform as the JBoss EAP collection .

Commands:
Appendix J. BlueStore configuration options The following are Ceph BlueStore configuration options that can be configured during deployment. Note This list is not complete. rocksdb_cache_size Description The size of the RocksDB cache in MB. Type 32-bit Integer Default 512 bluestore_throttle_bytes Description Maximum bytes available before the user throttles the input or output (I/O) submission. Type Size Default 64 MB bluestore_throttle_deferred_bytes Description Maximum bytes for deferred writes before the user throttles the I/O submission. Type Size Default 128 MB bluestore_throttle_cost_per_io Description Overhead added to the transaction cost in bytes for each I/O. Type Size Default 0 B bluestore_throttle_cost_per_io_hdd Description The default bluestore_throttle_cost_per_io value for HDDs. Type Unsigned integer Default 67 000 bluestore_throttle_cost_per_io_ssd Description The default bluestore_throttle_cost_per_io value for SSDs. Type Unsigned integer Default 4 000

Commands:
Chapter 6. Troubleshooting notification failures The notifications service event log enables Notifications administrators to see when notifications are not working properly. The event log provides a list of all triggered events on the Red Hat Hybrid Cloud Console account, and actions taken (as configured in the associated behavior group) for the past 14 days. In the Action taken column, each event shows the notification method highlighted in green or red to indicate the status of the message transmission. The filterable event log is a useful troubleshooting tool to see a failed notification event and identify potential issues with endpoints. After seeing a failed action in the event log, the Notifications administrator can check the endpoint and the status of the last five connection attempts on the Integrations screen. In the integrations service, the following connection statuses are reflected by color: Green: Five transmissions were successful. Red: Five transmissions were unsuccessful (timeout, 404 error, etc). Yellow: Connection is degraded; at least two of the five transmissions were unsuccessful. Unknown: The integration has not yet been called, or is not associated with a behavior group. The event log can answer questions related to receipt of emails. By showing the email action for an event as green, the event log enables a Notifications administrator to confirm that emails were sent successfully. Even when notifications and integrations are configured properly, individual users on the Hybrid Cloud Console account must configure their user preferences to receive emails. Before users receive notifications using the webhook integration type, a Notifications administrator must configure endpoints for your organization's preferred webhook application. Prerequisites You are logged in to the Hybrid Cloud Console as a user with Notifications administrator or Organization Administrator permissions. Procedure In the Hybrid Cloud Console, navigate to Settings > Notifications > Event Log . Filter the events list by event, application, application bundle, action type, or action status. Select the time frame to show events from today, yesterday, the last seven days, the last 14 days (default), or set a custom range within the last 14 days. Sort the Date and time column in ascending or descending order. Navigate to Settings > Notifications > Configure Events , and verify or change settings by event. Ask users to check their user preferences for receiving email notifications. Even when notifications and integrations are configured properly, individual users on the Hybrid Cloud Console account must configure their user preferences to receive emails. Additional resources For more information about network and firewall configuration, see Firewall Configuration for accessing Red Hat Insights / Hybrid Cloud Console Integrations & Notifications . To configure your personal preferences for receiving notifications, see Configuring user preferences for email notifications .

Commands:
Chapter 143. XML Tokenize The XML Tokenize language is a built-in language in camel-xml-jaxp , which is a truly XML-aware tokenizer that can be used with the Split EIP as the conventional Tokenize to efficiently and effectively tokenize XML documents.. XML Tokenize is capable of not only recognizing XML namespaces and hierarchical structures of the document but also more efficiently tokenizing XML documents than the conventional Tokenize language. 143.1. Dependencies When using xtokenize with Red Hat build of Camel Spring Boot make sure to use the following Maven dependency to have support for auto configuration: <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-xml-jaxp-starter</artifactId> </dependency> Additional dependency In order to use this component, an additional dependency is required as follows: <dependency> <groupId>org.codehaus.woodstox</groupId> <artifactId>woodstox-core-asl</artifactId> <version>4.4.1</version> </dependency> or <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-stax-starter</artifactId> </dependency> 143.2. XML Tokenizer Options The XML Tokenize language supports 4 options, which are listed below. Name Default Java Type Description headerName String Name of header to tokenize instead of using the message body. mode Enum The extraction mode. The available extraction modes are: i - injecting the contextual namespace bindings into the extracted token (default) w - wrapping the extracted token in its ancestor context u - unwrapping the extracted token to its child content t - extracting the text content of the specified element. Enum values: i w u t group Integer To group N parts together. trim Boolean Whether to trim the value to remove leading and trailing whitespaces and line breaks. 143.3. Example See Split EIP which has examples using the XML Tokenize language. 143.4. Spring Boot Auto-Configuration The component supports 3 options, which are listed below. Name Description Default Type camel.language.xtokenize.enabled Whether to enable auto configuration of the xtokenize language. This is enabled by default. Boolean camel.language.xtokenize.mode The extraction mode. The available extraction modes are: i - injecting the contextual namespace bindings into the extracted token (default) w - wrapping the extracted token in its ancestor context u - unwrapping the extracted token to its child content t - extracting the text content of the specified element. String camel.language.xtokenize.trim Whether to trim the value to remove leading and trailing whitespaces and line breaks. true Boolean

Commands:
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-xml-jaxp-starter</artifactId> </dependency>
<dependency> <groupId>org.codehaus.woodstox</groupId> <artifactId>woodstox-core-asl</artifactId> <version>4.4.1</version> </dependency>
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-stax-starter</artifactId> </dependency>
Preface Open Java Development Kit (OpenJDK) is a free and open-source implementation of the Java Platform, Standard Edition (Java SE). Eclipse Temurin is available in three LTS versions: OpenJDK 8u, OpenJDK 11u, and OpenJDK 17u. Binary files for Eclipse Temurin are available for macOS, Microsoft Windows, and multiple Linux x86 Operating Systems including Red Hat Enterprise Linux and Ubuntu.

Commands:
Chapter 17. Network Configuration To communicate with each other, computers must have a network connection. This is accomplished by having the operating system recognize an interface card (such as Ethernet, ISDN modem, or token ring) and configuring the interface to connect to the network. The Network Administration Tool can be used to configure the following types of network interfaces: Ethernet ISDN modem xDSL token ring CIPE wireless devices It can also be used to configure IPsec connections, manage DNS settings, and manage the /etc/hosts file used to store additional hostnames and IP address combinations. To use the Network Administration Tool , you must have root privileges. To start the application, go to the Applications (the main menu on the panel) => System Settings => Network , or type the command system-config-network at a shell prompt (for example, in an XTerm or a GNOME terminal ). If you type the command, the graphical version is displayed if X is running; otherwise, the text-based version is displayed. To use the command line version, execute the command system-config-network-cmd --help as root to view all of the options. Figure 17.1. Network Administration Tool Note Use the Red Hat Hardware Compatibility List ( http://hardware.redhat.com/hcl/ ) to determine if Red Hat Enterprise Linux supports your hardware device. 17.1. Overview To configure a network connection with the Network Administration Tool , perform the following steps: Add a network device associated with the physical hardware device. Add the physical hardware device to the hardware list, if it does not already exist. Configure the hostname and DNS settings. Configure any hosts that cannot be looked up through DNS. This chapter discusses each of these steps for each type of network connection.

Commands:
18.18. Begin Installation When all required sections of the Installation Summary screen have been completed, the admonition at the bottom of the menu screen disappears and the Begin Installation button becomes available. Figure 18.36. Ready to Install Warning Up to this point in the installation process, no lasting changes have been made on your computer. When you click Begin Installation , the installation program will allocate space on your hard drive and start to transfer Red Hat Enterprise Linux into this space. Depending on the partitioning option that you chose, this process might include erasing data that already exists on your computer. To revise any of the choices that you made up to this point, return to the relevant section of the Installation Summary screen. To cancel installation completely, click Quit or switch off your computer. To switch off most computers at this stage, press the power button and hold it down for a few seconds. If you have finished customizing your installation and are certain that you want to proceed, click Begin Installation . After you click Begin Installation , allow the installation process to complete. If the process is interrupted, for example, by you switching off or resetting the computer, or by a power outage, you will probably not be able to use your computer until you restart and complete the Red Hat Enterprise Linux installation process, or install a different operating system.

Commands:
function::cmdline_args Name function::cmdline_args - Fetch command line arguments from current process Synopsis Arguments n First argument to get (zero is normally the program itself) m Last argument to get (or minus one for all arguments after n) delim String to use to separate arguments when more than one. Description Returns arguments from the current process starting with argument number n, up to argument m. If there are less than n arguments, or the arguments cannot be retrieved from the current process, the empty string is returned. If m is smaller than n then all arguments starting from argument n are returned. Argument zero is traditionally the command itself.

Commands:
cmdline_args:string(n:long,m:long,delim:string)
Chapter 11. Ensuring that data displays correctly in the Fuse Console If the display of the queues and connections in the Fuse Console is missing queues, missing connections, or displaying inconsistent icons, adjust the Jolokia collection size parameter that specifies the maximum number of elements in an array that Jolokia marshals in a response. Procedure In the upper right corner of the Fuse Console, click the user icon and then click Preferences . Increase the value of the Maximum collection size option (the default is 50,000). Click Close .

Commands:
7.130. mod_nss 7.130.1. RHBA-2015:1284 - mod_nss bug fix and enhancement update Updated mod_nss packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The mod_nss module provides strong cryptography for the Apache HTTP Server via the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, using the Network Security Services (NSS) security library. Note The mod_nss packages have been upgraded to upstream version 1.0.10, which provides a number of bug fixes and enhancements over the version. Most notably, this update adds support for TLS version 1.2 to mod_nss. (BZ# 1166316 ) Users of mod_nss are advised to upgrade to these updated packages, which fix these bugs and add these enhancements. The httpd service must be restarted for this update to take effect.

Commands:
4.40. curl 4.40.1. RHBA-2012:0430 - curl bug fix update Updated curl packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The curl packages provide the libcurl library and the cURL command line tool for transferring data using various protocols, including HTTP, FTP, FILE, LDAP, TELNET, TFTP, SCP. Both, libcurl and cURL, support many useful capabilities, such as user authentication, proxy support, FTP uploading, HTTP POST and PUT methods, SSL certificates, and file transfer resume. Bug Fixes BZ# 800903 Previously, SSL connections could not be established with libcurl if the selected Network Security Services (NSS) database was broken or invalid. This update modifies the code of libcurl to initialize NSS without a valid database, which allows applications to establish SSL connections as expected in this scenario. BZ# 800904 The OpenLDAP suite was recently modified to use NSS instead of OpenSSL as the SSL back end. This change led to collisions between libcurl and OpenLDAP on NSS initialization and shutdown. Consequently, applications that were using both, libcurl and OpenLDAP, failed to establish SSL connections. This update modifies libcurl to use the same NSS API as OpenLDAP, which prevents collisions from occurring. Applications using OpenLDAP and libcurl can now connect to the LDAP server over SSL as expected. All users of curl are advised to upgrade to these updated packages, which fix these bugs. All running applications that use libcurl have to be restarted for this update to take effect.

Commands: