mtpti5iD/redhat-docs_dataset huggingface dataset:
10.8. Virtual Hosts The Apache HTTP Server's built in virtual hosting allows the server to provide different information based on which IP address, hostname, or port is being requested. A complete guide to using virtual hosts is available online at http://httpd.apache.org/docs-2.0/vhosts/ . 10.8.1. Setting Up Virtual Hosts To create a name-based virtual host, it is best to use the virtual host container provided in httpd.conf as an example. The virtual host example read as follows: To activate name-based virtual hosting, uncomment the NameVirtualHost line by removing the hash mark ( # ) and replace the asterisk ( * ) with the IP address assigned to the machine. , configure a virtual host by uncommenting and customizing the <VirtualHost> container. On the <VirtualHost> line, change the asterisk ( * ) to the server's IP address. Change the ServerName to a valid DNS name assigned to the machine, and configure the other directives as necessary. The <VirtualHost> container is highly customizable and accepts almost every directive available within the main server configuration. Note If configuring a virtual host to listen on a non-default port, that port must be added to the Listen directive in the global settings section of /etc/httpd/conf/httpd.conf file. To activate a newly created virtual host, the Apache HTTP Server must be reloaded or restarted. Refer to Section 10.4, "Starting and Stopping httpd " for further instructions. Comprehensive information about creating and configuring both name-based and IP address-based virtual hosts is provided online at http://httpd.apache.org/docs-2.0/vhosts/ .

Commands:
#NameVirtualHost *:80 # #<VirtualHost *:80> ServerAdmin webmaster@dummy-host.example.com DocumentRoot /www/docs/dummy-host.example.com ServerName dummy-host.example.com ErrorLog logs/dummy-host.example.com-error_log CustomLog logs/dummy-host.example.com-access_log common #</VirtualHost>
3.17. Host Networking Configurations Cluster Networking can be helpful to understand these networking configurations. Common types of networking configurations for virtualization hosts include: Bridge and NIC configuration. This configuration uses a Linux bridge to connect one or more virtual machines to the host's NIC. An example of this configuration is the automatic creation of the ovirtmgmt network when installing the Red Hat Virtualization Manager. Then, during host installation, the Red Hat Virtualization Manager installs VDSM on the host. The VDSM installation process creates the ovirtmgmt bridge which obtains the host's IP address to enable communication with the Manager. Important All hosts in a cluster must use either IPv4 or IPv6 as the IP stack for their management network. Dual stack is not supported. Bridge, VLAN, and NIC configuration. A VLAN can be included in the bridge and NIC configuration to provide a secure channel for data transfer over the network and supports connecting multiple bridges to a single NIC using multiple VLANs. Bridge, Bond, and VLAN configuration. A bond creates a logical link that combines the two (or more) physical Ethernet links. The resultant benefits include NIC fault tolerance and potential bandwidth extension, depending on the bonding mode. Multiple Bridge, Multiple VLAN, and NIC configuration. This configuration connects a NIC to multiple VLANs. For example, to connect a single NIC to two VLANs, the network switch can be configured to pass network traffic that has been tagged into one of the two VLANs to one NIC on the host. The host uses two vNICs to separate VLAN traffic, one for each VLAN. Traffic tagged into either VLAN then connects to a separate bridge by having the appropriate vNIC as a bridge member. Each bridge, in turn, connects to multiple virtual machines. Note You can also bond multiple NICs to facilitate a connection with multiple VLANs. Each VLAN in this configuration is defined over the bond comprising the multiple NICs. Each VLAN connects to an individual bridge and each bridge connects to one or more guests.

Commands:
5.4. Changing the LDAP Search Base for Users and Groups in a Trusted Active Directory Domain As an administrator, you can set a different search base for users and groups in the trusted Active Directory domain. For example, this enables you to filter out users from inactive organizational units so that only active Active Directory users and groups are visible to the SSSD client system. 5.4.1. Prerequisites To ensure that SSSD does not resolve all groups the users belongs to, consider disabling the support for the tokenGroups attribute on the Active Directory side. With tokenGroups enabled, SSSD resolves all groups the user belongs to because the attribute contains a flat list of SIDs. See Token-Groups attribute on Microsoft Developer Network for details about the attribute. 5.4.2. Configuring the LDAP Search Base to Restrict Searches This procedure describes restricting searches in SSSD to a specific subtree by editing the /etc/sssd/sssd.conf file. Considerations If your SSSD clients are directly joined to an Active Directory domain, perform this procedure on all the clients. If your SSSD clients are in an Identity Management domain that is in a trust with Active Directory, perform this procedure only on the Identity Management server. Procedure Make sure the trusted domain has a separate [domain] section in sssd.conf . The headings of trusted domain sections follow this template: For example: Edit the sssd.conf file to restrict the search base to a specific organizational unit (OU). For example, the ldap_search_base option changes the search base for all types of objects. You can also use the ldap_user_search_base , ldap_group_search_base , ldap_netgroup_search_base , and ldap_service_search_base options. For more details on these options, see the sssd-ldap (5) man page. Restart SSSD. To verify, resolve a few Active Directory users on the SSSD client. For example, to test a change to the user search base and group search base: If SSSD is configured correctly, you are able to resolve only objects from the configured search base. If you are able to resolve users from other search domains, troubleshoot the problem by inspecting the SSSD logs: Expire the SSSD caches. In the general [domain] section of sssd.conf , set the debug_level option to 9 . Repeat the command for resolving a user. In the SSSD logs at /var/log/sssd/ , look for messages from the sdap_get_generic_* functions. The functions log the filter and search base used in user searches. Additional Resources For a list of options you can use in trusted domain sections of sssd.conf , see TRUSTED DOMAIN SECTION in the sssd.conf (5) man page.

Commands:
[domain/ main_domain / trusted_domain ]
[domain/ idm.example.com / ad.example.com ]
[domain/ idm.example.com / ad.example.com ] ldap_search_base = ou= finance ,dc= ad ,dc= example ,dc= com
systemctl restart sssd.service
getent passwd ad_user @ ad.example.com # getent group ad_group @ ad.example.com
sss_cache --everything
7.14. bacula 7.14.1. RHBA-2015:0239 - bacula bug fix update Updated bacula packages that fix one bug are now available for Red Hat Enterprise Linux 6. Bacula is a set of programs that allow you to manage the backup, recovery, and verification of computer data across a network of different computers. Bug Fix BZ# 839249 Previously, the length of bacula daemon names was limited to 30 characters and any additional characters were automatically truncated without displaying an error message. The truncated name was passed to other applications that, as a consequence, did not work as expected. With this update, the limit has been exceeded to 64 characters, so the length of the name is no longer cut. Users of bacula are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 3. Viewing your reports on Red Hat Ansible Automation Platform The reports feature on the Red Hat Ansible Automation Platform provides users with a visual overview of their automation efforts across different teams using Ansible. Each report is designed to help users monitor the status of their automation environment, be it the frequency of playbook runs or the status of hosts affected by various job templates. For example, you can use your reports to: View the number of hosts affected by a job template View the number changes made to hosts by a job template View the frequency of a job template run, and the rate of job templates that succeed or fail to run 3.1. Reviewing your reports To view reports about your Ansible automation environment, proceed with the following steps: Procedure Log in to console.redhat.com and navigate to the Ansible Automation Platform. Click Reports on the side navigation panel. Select a report from the results to view it. Each report presents data to monitor your Ansible automation environment. Use the filter toolbar on each report to adjust your graph view. Note We are constantly adding new reports to the system. If you have ideas for new reports that would be helpful for your team, please contact your account representative or log a feature enhancement for automation analytics.

Commands:
B.68. pixman B.68.1. RHBA-2010:0905 - pixman bug fix update An updated pixman package is now available for Red Hat Enterprise Linux 6. Pixman is a pixel manipulation library for the X Window System and cairo. Bug Fix BZ# 644818 The pixman package has been updated to version 0.18, which provides new functionality that is required by SPICE, a remote display protocol used in Red Hat Enterprise Linux for viewing virtualized guests. All users requiring SPICE are advised to upgrade to this updated package, which resolves this issue.

Commands:
Chapter 14. Accessing runtime data from Business Central The following pages in Business Central allow you to view KIE Server runtime data : Process Reports Task Reports Process Definitions Process Instances Execution Errors Jobs Tasks These pages use the credentials of the currently logged in user to load data from KIE Server. Therefore, to be able to view the runtime data in Business Central, ensure that the following conditions are met: The user exists in the KIE container (deployment unit) running the Business Central application. This user must have admin , analyst , or developer roles assigned, in addition to the kie-server role, with full access to the runtime data. The manager and process_admin roles also allow access to runtime data pages in Business Central. The user exists in the KIE container (deployment unit) running KIE Server and has the kie-server role assigned. Communication between Business Central and KIE Server is established. That is, KIE Server is registered in the Process Automation Manager controller, which is part of Business Central.

Commands:
Chapter 1. Installation Overview Installing a standalone Manager environment with local databases involves the following steps: Install and configure the Red Hat Virtualization Manager: Install a Red Hat Enterprise Linux machine for the Manager. Register the Manager machine with the Content Delivery Network and enable the Red Hat Virtualization Manager repositories. Install and Configure the Red Hat Virtualization Manager using engine-setup . Connect to the Administration Portal to add hosts and storage domains. Install hosts to run virtual machines on: Use either host type, or both: Red Hat Virtualization Host Red Hat Enterprise Linux Add the hosts to the Manager. Prepare storage to use for storage domains. You can use one of the following storage types: NFS iSCSI Fibre Channel (FCP) POSIX-compliant file system Local storage Red Hat Gluster Storage Add storage domains to the Manager. Important Keep the environment up to date. See How do I update my Red Hat Virtualization system? for more information. Since bug fixes for known issues are frequently released, use scheduled tasks to update the hosts and the Manager.

Commands:
Chapter 2. Supported Eclipse Vert.x Runtime Component Configurations and Integrations The following resource defines the supported configurations and integrations of Red Hat products with Eclipse Vert.x: For a list of technologies that are supported for integration with Eclipse Vert.x in production environments see the Supported Eclipse Vert.x configurations and integrations. For a list of Eclipse Vert.x runtime artifacts and their versions see the component details page .

Commands:
Chapter 11. Validating schemas with the Red Hat build of Apicurio Registry You can use the Red Hat build of Apicurio Registry with AMQ Streams. Apicurio Registry is a datastore for sharing standard event schemas and API designs across API and event-driven architectures. You can use Apicurio Registry to decouple the structure of your data from your client applications, and to share and manage your data types and API descriptions at runtime using a REST interface. Apicurio Registry stores schemas used to serialize and deserialize messages, which can then be referenced from your client applications to ensure that the messages that they send and receive are compatible with those schemas. Apicurio Registry provides Kafka client serializers/deserializers for Kafka producer and consumer applications. Kafka producer applications use serializers to encode messages that conform to specific event schemas. Kafka consumer applications use deserializers, which validate that the messages have been serialized using the correct schema, based on a specific schema ID. You can enable your applications to use a schema from the registry. This ensures consistent schema usage and helps to prevent data errors at runtime. Additional resources Red Hat build of Apicurio Registry product documentation Red Hat build of Apicurio Registry is built on the Apicurio Registry open source community project available on GitHub: Apicurio/apicurio-registry

Commands:
Chapter 17. Red Hat Software Collections Red Hat Software Collections is a Red Hat content set that provides a set of dynamic programming languages, database servers, and related packages that you can install and use on all supported releases of Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 on AMD64 and Intel 64 architectures. Dynamic languages, database servers, and other tools distributed with Red Hat Software Collections do not replace the default system tools provided with Red Hat Enterprise Linux, nor are they used in preference to these tools. Red Hat Software Collections uses an alternative packaging mechanism based on the scl utility to provide a parallel set of packages. This set enables use of alternative package versions on Red Hat Enterprise Linux. By using the scl utility, users can choose at any time which package version they want to run. Important Red Hat Software Collections has a shorter life cycle and support term than Red Hat Enterprise Linux. For more information, see the Red Hat Software Collections Product Life Cycle . Red Hat Developer Toolset is now a part of Red Hat Software Collections, included as a separate Software Collection. Red Hat Developer Toolset is designed for developers working on the Red Hat Enterprise Linux platform. It provides the current versions of the GNU Compiler Collection, GNU Debugger, Eclipse development platform, and other development, debugging, and performance monitoring tools. See the Red Hat Software Collections documentation for the components included in the set, system requirements, known problems, usage, and specifics of individual Software Collections. See the Red Hat Developer Toolset documentation for more information about the components included in this Software Collection, installation, usage, known problems, and more.

Commands:
3.5. Red Hat OpenStack Platform 16 Developer Tools for RHEL 8 for Power, little endian (RPMs) The following table outlines the packages included in the openstack-16-devtools-for-rhel-8-ppc64le-rpms repository. Table 3.5. Red Hat OpenStack Platform 16 Developer Tools for RHEL 8 for Power, little endian (RPMs) Packages Name Version Advisory openstack-packstack 15.0.0-0.20200110015912.3be5458.el8ost RHEA-2020:0283 openstack-packstack-puppet 15.0.0-0.20200110015912.3be5458.el8ost RHEA-2020:0283 puppet-tempest 15.4.1-0.20191014141828.f74827b.el8ost RHEA-2020:0283 python3-junitxml 0.7-17.el8ost RHEA-2020:0283 subunit-filters 1.3.0-7.el8ost RHEA-2020:0283

Commands:
Chapter 3. Installing and configuring the JFrog Artifactory plugin JFrog Artifactory is a front-end plugin that displays the information about your container images stored in the JFrog Artifactory repository. The JFrog Artifactory plugin is preinstalled with Developer Hub and disabled by default. To use it, you need to enable and configure it first. Important The JFrog Artifactory plugin is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs), might not be functionally complete, and Red Hat does not recommend using them for production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information on Red Hat Technology Preview features, see Technology Preview Features Scope . Additional detail on how Red Hat provides support for bundled community dynamic plugins is available on the Red Hat Developer Support Policy page. 3.1. Installation The JFrog Artifactory plugin is preinstalled in Developer Hub with basic configuration properties. To enable it, set the disabled property to false as follows: global: dynamic: includes: - dynamic-plugins.default.yaml plugins: - package: ./dynamic-plugins/dist/backstage-community-plugin-jfrog-artifactory disabled: false 3.2. Configuration Set the proxy to the desired JFrog Artifactory server in the app-config.yaml file as follows: proxy: endpoints: '/jfrog-artifactory/api': target: http://<hostname>:8082 # or https://<customer>.jfrog.io headers: # Authorization: 'Bearer <YOUR TOKEN>' # Change to "false" in case of using a self-hosted Artifactory instance with a self-signed certificate secure: true Add the following annotation to the entity's catalog-info.yaml file to enable the JFrog Artifactory plugin features in RHDH components: metadata: annotations: 'jfrog-artifactory/image-name': '<IMAGE-NAME>'

Commands:
global: dynamic: includes: - dynamic-plugins.default.yaml plugins: - package: ./dynamic-plugins/dist/backstage-community-plugin-jfrog-artifactory disabled: false
proxy: endpoints: '/jfrog-artifactory/api': target: http://<hostname>:8082 # or https://<customer>.jfrog.io headers: # Authorization: 'Bearer <YOUR TOKEN>' # Change to "false" in case of using a self-hosted Artifactory instance with a self-signed certificate secure: true
metadata: annotations: 'jfrog-artifactory/image-name': '<IMAGE-NAME>'
3. Related Documentation For more information about using Red Hat Enterprise Linux, refer to the following resources: Red Hat Enterprise Linux Installation Guide - Provides information regarding installation of Red Hat Enterprise Linux. Red Hat Enterprise Linux Introduction to System Administration - Provides introductory information for new Red Hat Enterprise Linux system administrators. Red Hat Enterprise Linux System Administration Guide - Provides more detailed information about configuring Red Hat Enterprise Linux to suit your particular needs as a user. Red Hat Enterprise Linux Reference Guide - Provides detailed information suited for more experienced users to reference when needed, as opposed to step-by-step instructions. Red Hat Enterprise Linux Security Guide - Details the planning and the tools involved in creating a secured computing environment for the data center, workplace, and home. For more information about Red Hat Cluster Suite for Red Hat Enterprise Linux, refer to the following resources: Red Hat Cluster Suite Overview - Provides a high level overview of the Red Hat Cluster Suite. Configuring and Managing a Red Hat Cluster - Provides information about installing, configuring and managing Red Hat Cluster components. Global File System: Configuration and Administration - Provides information about installing, configuring, and maintaining Red Hat GFS (Red Hat Global File System). Using Device-Mapper Multipath - Provides information about using the Device-Mapper Multipath feature of Red Hat Enterprise Linux. Using GNBD with Global File System - Provides an overview on using Global Network Block Device (GNBD) with Red Hat GFS. Linux Virtual Server Administration - Provides information on configuring high-performance systems and services with the Linux Virtual Server (LVS). Red Hat Cluster Suite Release Notes - Provides information about the current release of Red Hat Cluster Suite. Red Hat Cluster Suite documentation and other Red Hat documents are available in HTML and PDF versions online at the following location: http://www.redhat.com/docs

Commands:
6.13. Tools ssh-keygen component The following example in the description of the -V option in the ssh-keygen(1) manual page is incorrect: If you set a date range in this format, the certificate is valid from four weeks ago until now. perl-WWW-curl component Attempting to access the CURLINFO_PRIVATE value can cause curl to terminate unexpectedly with a segmentation fault. freerpd component, BZ# 988277 The ALSA plug-in is not supported in Red Hat Enterprise Linux 6. Instead of the ALSA plug-in, use the pulseaudio plug-in. To enable it, use the --plugin rpdsnd option with the xfreerdp command without specifying which plug-in should be used; the pulseaudio plug-in will be used automatically in this case. coolkey component, BZ# 906537 Personal Identity Verification (PIV) Endpoint Cards which support both CAC and PIV interfaces might not work with the latest coolkey update; some signature operations like PKINIT can fail. To work around this problem, downgrade coolkey to the version shipped with Red Hat Enterprise Linux 6.3. libreport component Even if the stored credentials are used , the report-gtk utility can report the following error message: To work around this problem, close the dialog window; the Login=<rhn-user> and Password=<rhn-password> credentials in the /etc/libreport/plugins/rhtsupport.conf will be used in the same way they are used by report-rhtsupport . For more information, refer to this Knowledge Base article. vlock component When a user password is used to lock a console with vlock , the console can only be unlocked with the user password, not the root password. That is, even if the first inserted password is incorrect, and the user is prompted to provide the root password, entering the root password fails with an error message. libreoffice component Libreoffice contains a number of harmless files used for testing purposes. However, on Microsoft Windows system, these files can trigger false positive alerts on various anti-virus software, such as Microsoft Security Essentials. For example, the alerts can be triggered when scanning the Red Hat Enterprise Linux 6 ISO file. gnome-power-manager component When the computer runs on battery, custom brightness level is not remembered and restored if power saving features like "dim display when idle" or "reduce backlight brightness when idle" are enabled. rsyslog component rsyslog does not reload its configuration after a SIGHUP signal is issued. To reload the configuration, the rsyslog daemon needs to be restarted:

Commands:
"-4w:+4w" (valid from four weeks ago to four weeks from now)
Wrong settings detected for Red Hat Customer Support [..]
~]# service rsyslog restart