mtpti5iD/redhat-docs_dataset huggingface dataset:
22.2. Download JBoss Operations Network (JON) 22.2.1. Prerequisites for Installing JBoss Operations Network (JON) In order to install JBoss Operations Network in Red Hat JBoss Data Grid, the following is required: A Linux, Windows, or Mac OSX operating system, and an x86_64, i686, or ia64 processor. Java 6 or higher is required to run both the JBoss Operations Network Server and the JBoss Operations Network Agent. Synchronized clocks on JBoss Operations Network Servers and Agents. An external database must be installed. Report a bug 22.2.2. Download JBoss Operations Network Use the following procedure to download Red Hat JBoss Operations Network (JON) from the Customer Portal: Procedure 22.1. Download JBoss Operations Network To access the Red Hat Customer Portal, navigate to https://access.redhat.com/home in a browser. Click Downloads . In the section labeled JBoss Development and Management , click Red Hat JBoss Data Grid . Enter the relevant credentials in the Red Hat Login and Password fields and click Log In . Select the appropriate version in the Version drop down menu list. Click the Download button to the desired download file. Report a bug 22.2.3. Remote JMX Port Values A port value must be provided to allow Red Hat JBoss Data Grid instances to be located. The value itself can be any available port. Provide unique (and available) remote JMX ports to run multiple JBoss Data Grid instances on a single machine. A locally running JBoss Operations Network agent can discover each instance using the remote port values. Report a bug 22.2.4. Download JBoss Operations Network (JON) Plugin Complete this task to download the JBoss Operations Network (JON) plugin for Red Hat JBoss Data Grid from the Red Hat Customer Portal. Procedure 22.2. Download Installation Files Open http://access.redhat.com in a web browser. Click Downloads in the menu across the top of the page. Click Red Hat JBoss Operations Network in the list under JBoss Development and Management . Enter your login information. You are taken to the Software Downloads page. Download the JBoss Operations Network Plugin If you intend to use the JBoss Operations Network plugin for JBoss Data Grid, select JBoss ON for Data Grid from either the Product drop-down box, or the menu on the left. Click the Red Hat JBoss Operations Network VERSION Base Distribution Download button. Repeat the steps to download the Data Grid Management Plugin Pack for JBoss ON VERSION Report a bug

Commands:
B.10. corosync B.10.1. RHBA-2012:1216 - corosync bug fix update Updated corosync packages that fix a bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The corosync packages provide the Corosync Cluster Engine and C Application Programming Interfaces (APIs) for Red Hat Enterprise Linux cluster software. Bug Fix BZ# 850681 Previously, a bug in the Corosync server caused that when an IPC (inter-process communication) connection exited or was terminated, Corosync failed to free the memory for this connection. Consequently, Corosync memory could grow. This update fixes this bug and Corosync now always frees IPC memory as expected in the described scenario. Users of corosync are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. MTA 7.2.1 2.1. Resolved issues This section provides highlighted issues that have been resolved in Migration Toolkit for Applications (MTA) 7.2.1. OpenRewrite CMD now properly mounts the settings file The Migration Toolkit for Applications (MTA) CLI not only analyzes source code but also transforms it to adopt a particular technology. To transform the code, MTA can use an external settings file, for example, to access the Maven repository. In such cases, this file must be mounted to a running container where the analysis engine will run. Previously, this file could not be mounted. As a result, the transformation operation failed. With this update, the issue has been resolved, and the file is now properly mounted to the running container. (MTA-4553) The application analysis no longer fails on RHEL 8 Previously, when you ran the application analysis with the MTA 7.2.0 version on RHEL 8 systems, the analysis failed with the version `GLIBC_2.32' not found error. With this update, the issue has been resolved, and the application analysis no longer fails for RHEL 8. (MTA-4634) 2.2. Known issues This section provides highlighted known issues in Migration Toolkit for Applications (MTA) version 7.2.1. Application analysis might fail to resolve dependencies When you run application analysis by using the MTA user interface (UI) for any target application, the dependencies list might be shown as empty after the analysis is complete. Currently, there is no workaround for this issue. (MTA-4598)

Commands:
Chapter 7. Evaluating and Testing Policies When designing your policies, you can simulate authorization requests to test how your policies are being evaluated. You can access the Policy Evaluation Tool by clicking the Evaluate tab when editing a resource server. There you can specify different inputs to simulate real authorization requests and test the effect of your policies. 7.1. Providing Identity Information The Identity Information filters can be used to specify the user requesting permissions. 7.2. Providing Contextual Information The Contextual Information filters can be used to define additional attributes to the evaluation context, so that policies can obtain these same attributes. 7.3. Providing the Permissions The Permissions filters can be used to build an authorization request. You can request permissions for a set of one or more resources and scopes. If you want to simulate authorization requests based on all protected resources and scopes, click Add without specifying any Resources or Scopes . When you've specified your desired values, click Evaluate .

Commands:
18.12.10.3. STP (Spanning Tree Protocol) Protocol ID: stp Rules of this type should go either into the root or stp chain. Table 18.5. STP protocol types Attribute Name Datatype Definition srcmacaddr MAC_ADDR MAC address of sender srcmacmask MAC_MASK Mask applied to MAC address of sender type UINT8 Bridge Protocol Data Unit (BPDU) type flags UINT8 BPDU flagdstmacmask root-priority UINT16 Root priority range start root-priority-hi UINT16 (0x0-0xfff, 0 - 4095) Root priority range end root-address MAC _ADDRESS root MAC Address root-address-mask MAC _MASK root MAC Address mask roor-cost UINT32 Root path cost (range start) root-cost-hi UINT32 Root path cost range end sender-priority-hi UINT16 Sender priority range end sender-address MAC_ADDRESS BPDU sender MAC address sender-address-mask MAC_MASK BPDU sender MAC address mask port UINT16 Port identifier (range start) port_hi UINT16 Port identifier range end msg-age UINT16 Message age timer (range start) msg-age-hi UINT16 Message age timer range end max-age-hi UINT16 Maximum age time range end hello-time UINT16 Hello time timer (range start) hello-time-hi UINT16 Hello time timer range end forward-delay UINT16 Forward delay (range start) forward-delay-hi UINT16 Forward delay range end comment STRING text string up to 256 characters

Commands:
B.38.8. RHBA-2012:0362 - kernel bug fix update Updated kernel packages that fix two bugs are now available for Red Hat Enterprise Linux 6 Extended Update Support. The kernel packages contain the Linux kernel, the core of any Linux operating system. Bug Fixes BZ# 771868 A bug in the splice code caused the file position on the write side of the sendfile() system call to be incorrectly set to the read-side file position. This could result in data being written to an incorrect offset of the destination file descriptor. With this update, sendfile() has been modified to correctly use the current file position for the write-side file descriptor. Note that the bug did not occur in the following sendfile() scenarios: when both read and write file positions were identical and when the file position was not important (for example if the write side was a socket). BZ# 786028 Previously, the sendfile(2) function was reimplemented to use splice infrastructure, but the function still checked for the f_op.sendpage() method call instead of the f_op.splice_write() method call. Because splice infrastructure was used for the sendfile(2) function, the check for sendpage infrastructure always failed. This problem has been fixed by removing the deprecated check and using f_op.sendpage() instead. All users of kernel are advised to upgrade to these updated packages, which fix these bugs. Note that the system must be rebooted for this update to take effect.

Commands:
7.8. Red Hat Enterprise Linux-Specific Information The following describes the various features specific to Red Hat Enterprise Linux that relate to printers and printing. The Printer Configuration Tool allows users to configure a printer. This tool helps maintain the printer configuration file, print spool directories, and print filters. Red Hat Enterprise Linux 4 uses the CUPS printing system. If a system was upgraded from a Red Hat Enterprise Linux version that used CUPS, the upgrade process preserved the configured queues. Using the Printer Configuration Tool requires root privileges. To start the application, select Main Menu Button (on the Panel) => System Settings => Printing , or type the command system-config-printer . This command automatically determines whether to run the graphical or text-based version depending on whether the command is executed in the graphical desktop environment or from a text-based console. To force the Printer Configuration Tool to run as a text-based application, execute the command system-config-printer-tui from a shell prompt. Important Do not edit the /etc/printcap file or the files in the /etc/cups/ directory. Each time the printer daemon ( cups ) is started or restarted, new configuration files are dynamically created. The files are dynamically created when changes are applied with the Printer Configuration Tool as well. The following types of print queues can be configured: Locally-connected - a printer attached directly to the computer through a parallel or USB port. Networked CUPS (IPP) - a printer that can be accessed over a TCP/IP network via the Internet Printing Protocol, also known as IPP (for example, a printer attached to another Red Hat Enterprise Linux system running CUPS on the network). Networked UNIX (LPD) - a printer attached to a different UNIX system that can be accessed over a TCP/IP network (for example, a printer attached to another Red Hat Enterprise Linux system running LPD on the network). Networked Windows (SMB) - a printer attached to a different system which is sharing a printer over a SMB network (for example, a printer attached to a Microsoft Windows TM machine). Networked Novell (NCP) - a printer attached to a different system which uses Novell's NetWare network technology. Networked JetDirect - a printer connected directly to the network through HP JetDirect instead of to a computer. Important If you add a new print queue or modify an existing one, you must apply the changes to them to take effect. Clicking the Apply button saves any changes that you have made and restarts the printer daemon. The changes are not written to the configuration file until the printer daemon is restarted. Alternatively, you can choose Action => Apply . For more information on the configuration of printers under Red Hat Enterprise Linux refer to the System Administrators Guide .

Commands:
17.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. The following types are used with BIND. Different types allow you to configure flexible access: named_zone_t Used for master zone files. Other services cannot modify files of this type. The named daemon can only modify files of this type if the named_write_master_zones Boolean is enabled. named_cache_t By default, named can write to files labeled with this type, without additional Booleans being set. Files copied or created in the /var/named/slaves/ , /var/named/dynamic/ and /var/named/data/ directories are automatically labeled with the named_cache_t type. named_var_run_t Files copied or created in the /var/run/bind/ , /var/run/named/ , and /var/run/unbound/ directories are automatically labeled with the named_var_run_t type. named_conf_t BIND-related configuration files, usually stored in the /etc directory, are automatically labeled with the named_conf_t type. named_exec_t BIND-related executable files, usually stored in the /usr/sbin/ directory, are automatically labeled with the named_exec_t type. named_log_t BIND-related log files, usually stored in the /var/log/ directory, are automatically labeled with the named_log_t type. named_unit_file_t Executable BIND-related files in the /usr/lib/systemd/system/ directory are automatically labeled with the named_unit_file_t type.

Commands:
8.190. samba4 8.190.1. RHSA-2013:1543 - Moderate: samba4 security and bug fix update Updated samba4 packages that fix one security issue and two bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links associated with each description below. Samba is an open-source implementation of the Server Message Block (SMB) or Common Internet File System (CIFS) protocol, which allows PC-compatible machines to share files, printers, and other information. Security Fix CVE-2013-4124 An integer overflow flaw was found in the way Samba handled an Extended Attribute (EA) list provided by a client. A malicious client could send a specially crafted EA list that triggered an overflow, causing the server to loop and reprocess the list using an excessive amount of memory. Note: This issue did not affect the default configuration of the Samba server. Bug Fixes BZ# 882338 When Samba was installed in the build root directory, the RPM target might not have existed. Consequently, the find-debuginfo.sh script did not create symbolic links for the libwbclient.so.debug module associated with the target. With this update, the paths to the symbolic links are relative so that the symbolic links are now created correctly. BZ# 911264 Previously, the samba4 packages were missing a dependency for the libreplace.so module which could lead to installation failures. With this update, the missing dependency has been added to the dependency list of the samba4 packages and installation now proceeds as expected. All samba4 users are advised to upgrade to these updated packages, which contain a backported patch to correct these issues.

Commands:
7.109. librtas 7.109.1. RHBA-2015:1304 - librtas bug fix and enhancement update Updated librtas packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The librtas packages contain a set of libraries that allow access to the Run-Time Abstraction Services (RTAS) on 64-bit PowerPC architectures. The librtasevent library contains definitions and routines for analyzing RTAS events. Note The librtas packages have been upgraded to upstream version 1.3.13, which provides a number of bug fixes and enhancements over the version. (BZ# 1148742 ) Users of librtas are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
13.6. Remove the Application Use the following procedure to remove the Hello World application: Procedure 13.5. Remove the Application Start the Application Servers Ensure that both server instances are running. Navigate to the Root In the command line terminal, navigate to the root directory of the quickstart. Remove the Archive Use the following commands to remove the archive from both the server instances. Remove the archive from the first server as follows: Remove the archive from the second server as follows: Report a bug

Commands:
mvn jboss-as:undeploy
mvn jboss-as:undeploy -Djboss-as.port=10099
8.147. netcf 8.147.1. RHBA-2014:1475 - netcf bug fix and enhancement update Updated netcf packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The netcf packages contain a library for modifying the network configuration of a system. Network configuration is expressed in a platform-independent XML format, which the netcf library translates into changes to the system's "native" network configuration files. This update also fixes the following bugs: Note The netcf package has been upgraded to upstream version 0.2.4, which provides a number of bug fixes and enhancements over the version. This includes a change ensuring that an interface with unplugged cable is not considered to be active. (BZ# 851748 ) This update also fixes the following bugs: Bug Fixes BZ# 879055 The libvirtd service could terminate unexpectedly when retrieving a MAC address. This happened because the netcf code contained uninitialized data that could be accessed by libvirtd. With this update, netcf properly initializes this data and libvirtd no longer crashes in this case. BZ# 1052156 Previously, netcf added an additional set of quotes to the value of the BONDING_OPTS parameter while attempting to create a bond interface. Consequently, the attempt failed with an error similar to the following: Error creating interface: 'Could not create interface: internal error failed to create (start) interface bond0: failed to execute external program - Running 'ifup bond0' failed with exit code 1: ./network-functions: line 457: /sys/class/net/bond0/bonding/'mode: No such file or directory With this update, additional quotes are no longer added to BONDING_OPTS and bonding devices can now be created as expected with this parameter specified. The netcf package has been upgraded to upstream version 0.2.4, which provides a number of bug fixes and enhancements over the version. This includes a change ensuring that an interface with unplugged cable is not considered to be active. (BZ#851748) Users of netcf are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
3.8. XML Schema Validation The PROP_XML_VALIDATION execution property, defined in org.teiid.jdbc.ExecutionProperties , can be set using the SET statement to indicate that the server should validate XML document model documents against their schema before returning them to the client. If schema validation is on, then the server sends an SQLWarning if the document does not conform to the schema it is associated with. Note Using schema validation will reduce the performance of your XML queries.

Commands:
Chapter 7. Using Red Hat Single Sign-On Operator with automation hub Private automation hub uses Red Hat Single Sign-On for authentication. The Red Hat Single Sign-On Operator creates and manages resources. Use this Operator to create custom resources to automate Red Hat Single Sign-On administration in Openshift. When installing Ansible Automation Platform on Virtual Machines (VMs) the installer can automatically install and configure Red Hat Single Sign-On for use with private automation hub. When installing Ansible Automation Platform on Red Hat OpenShift Container Platform you must install Single Sign-On separately. This chapter describes the process to configure Red Hat Single Sign-On and integrate it with private automation hub when Ansible Automation Platform is installed on OpenShift Container Platform. Prerequisites You have access to Red Hat OpenShift Container Platform using an account with operator installation permissions. You have installed the catalog containing the Red Hat Ansible Automation Platform operators. You have installed the Red Hat Single Sign-On Operator. To install the Red Hat Single Sign-On Operator, follow the procedure in Installing Red Hat Single Sign-On using a custom resource in the Red Hat Single Sign-On documentation.

Commands:
2.2. Special Red Hat Enterprise Linux File Locations Red Hat Enterprise Linux extends the FHS structure slightly to accommodate special files. Most files pertaining to RPM are kept in the /var/lib/rpm/ directory. For more information on RPM, refer to man rpm . The /var/cache/yum/ directory contains files used by the Package Updater , including RPM header information for the system. This location may also be used to temporarily store RPMs downloaded while updating the system. For more information about the Red Hat Network, refer to the documentation online at https://rhn.redhat.com/ . Another location specific to Red Hat Enterprise Linux is the /etc/sysconfig/ directory. This directory stores a variety of configuration information. Many scripts that run at boot time use the files in this directory.

Commands:
Chapter 2. Customizing the dashboard The Red Hat OpenStack Platform (RHOSP) dashboard (horizon) uses a default theme (RCUE), which is stored inside the horizon container. You can add your own theme to the container image and customize certain parameters to change the look and feel of the following dashboard elements: Logo Site colors Stylesheets HTML title Site branding link Help URL Note To ensure continued support for modified RHOSP container images, the resulting images must comply with the Red Hat Container Support Policy . 2.1. Obtaining the horizon container image To obtain a copy of the horizon container image, pull the image either into the undercloud or a separate client system that is running podman. Procedure Pull the horizon container image: You can use this image as a basis for a modified image. 2.2. Obtaining the RCUE theme The horizon container image uses the Red Hat branded RCUE theme by default. You can use this theme as a basis for your own theme and extract a copy from the container image. Procedure Create a directory for your theme: Start a container that executes a null loop. For example, run the following command: Copy the RCUE theme from the container to your local directory: Terminate the container: Result: You now have a local copy of the RCUE theme. 2.3. Creating your own theme based on RCUE To use RCUE as a basis, copy the entire RCUE theme directory rcue to a new location. This procedure uses mytheme as an example name. Procedure Copy the theme: To change the colors, graphics, fonts, and other elements of a theme, edit the files in mytheme. When you edit this theme, check for all instances of rcue including paths, files, and directories to ensure that you change them to the new mytheme name. 2.4. Creating a file to enable your theme and customize the dashboard To enable your theme in the dashboard container, you must create a file to override the AVAILABLE_THEMES parameter. Procedure Create a new file called _12_mytheme_theme.py in the horizon-themes directory and add the following content: The 12 in the file name ensures this file is loaded after the RCUE file, which uses 11 , and overrides the AVAILABLE_THEMES parameter. Optional: You can also set custom parameters in the _12_mytheme_theme.py file. Use the following examples as a guide: SITE_BRANDING Set the HTML title that appears at the top of the browser window. SITE_BRANDING_LINK Changes the hyperlink of the theme logo, which normally redirects to horizon:user_home by default.

Commands:
sudo podman pull registry.redhat.io/rhosp-rhel8/openstack-horizon:18.0
mkdir ~/horizon-themes cd ~/horizon-themes
sudo podman run --rm -d --name horizon-temp registry.redhat.io/rhosp-rhel8/openstack-horizon /usr/bin/sleep infinity
sudo podman cp horizon-temp:/usr/share/openstack-dashboard/openstack_dashboard/themes/rcue .
sudo podman kill horizon-temp
cp -r rcue mytheme
AVAILABLE_THEMES = [('mytheme', 'My Custom Theme', 'themes/mytheme')]
SITE_BRANDING = "Example, Inc. Cloud"
SITE_BRANDING_LINK = "http://example.com"