mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Enabling desktop icons You can enable the desktop icons functionality and move files to the desktop. 1.1. Desktop icons in RHEL 9 Desktop icons are provided by the Desktop icons GNOME Shell extension, which is available from the gnome-shell-extension-desktop-icons package. Desktop icons in GNOME Classic The GNOME Classic environment includes the gnome-shell-extension-desktop-icons package by default. Desktop icons are always on, and you cannot turn them off. Desktop icons in GNOME Standard In GNOME Standard, desktop icons are disabled by default. To enable desktop icons in the GNOME Standard environment, you must install the gnome-shell-extension-desktop-icons package. 1.2. Enabling desktop icons in GNOME Standard This procedure enables the desktop icons functionality in the GNOME Standard environment. Prerequisites The Extensions application is installed on the system: Procedure Open the Extensions application. Enable the Desktop Icons extension. 1.3. Creating a desktop icon for a file This procedure creates a desktop icon for an existing file. Prerequisites The Desktop icons extension is enabled. Procedure Move the selected file into the ~/Desktop/ directory. Verification Check that the icon for the file appears on the desktop.

Commands:
dnf install gnome-shell-extension-desktop-icons
8.7. About Replication Guarantees In a clustered cache, the user can receive synchronous replication guarantees as well as the parallelism associated with asynchronous replication. Red Hat JBoss Data Grid provides an asynchronous API for this purpose. The asynchronous methods used in the API return Futures, which can be queried. The queries block the thread until a confirmation is received about the success of any network calls used. Report a bug

Commands:
8.147. perl-Net-DNS 8.147.1. RHBA-2013:0785 - perl-Net-DNS bug fix update Updated perl-Net-DNS packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Perl packages provide the high-level programming language Perl, which is commonly used for system administration utilities and web programming. Bug Fix BZ#766357 Previously, dynamic update of an AAAA record caused the DNS module to return a FORMERR error on the prerequisite caused by the AAAA record creating the RDATA entry, even when the address was never specified. Consequently, removing an AAAA record from a DNS zone failed. This update adds a check to ensure that required data are defined and removing AAAA records now works as expected. Users of perl-Net-DNS are advised to upgrade to these updated packages, which fix this bug.

Commands:
Appendix B. Connecting with JConsole B.1. Connect to JDG via JConsole JConsole is a JMX GUI that allows a user to connect to a JVM, either local or remote, to monitor the JVM, its MBeans, and execute operations. Procedure B.1. Add Management User to JBoss Data Grid Before being able to connect to a remote JBoss Data Grid instance a user will need to be created; to add a user execute the following steps on the remote instance. Navigate to the bin directory Execute the add-user.sh script. Accept the default option of ManagementUser by pressing return. Accept the default option of ManagementRealm by pressing return. Enter the desired username. In this example jmxadmin will be used. Enter and confirm the password. Accept the default option of no groups by pressing return. Confirm that the desired user will be added to the ManagementRealm by entering yes . Enter no as this user will not be used for connections between processes. The following image shows an example execution run. Figure B.1. Execution of add-user.sh Binding the Management Interface By default JBoss Data Grid will start with the management interface binding to 127.0.0.1. In order to connect remotely this interface must be bound to an IP address that is visible by the network. Either of the following options will correct this: Option 1: Runtime - By adjusting the jboss.bind.address.management property on startup a new IP address can be specified. In the following example JBoss Data Grid is starting with this bound to 192.168.122.5: Option 2: Configuration - Adjust the jboss.bind.address.management in the configuration file. This is found in the interfaces subsystem. A snippet of the configuration file, with the IP adjusted to 192.168.122.5, is provided below: Running JConsole A jconsole.sh script is provided in the USDJDG_HOME/bin directory. Executing this script will launch JConsole. Procedure B.2. Connecting to a remote JBoss Data Grid instance using JConsole Execute the USDJDG_HOME/bin/jconsole.sh script. This will result in the following window appearing: Figure B.2. JConsole Select Remote Process . Enter service:jmx:remoting-jmx://USDIP:9999 in the text area. Enter the username and password, created from the add-user.sh script. Click Connect to initiate the connection. Once connected ensure that the cache-related nodes may be viewed. The following screenshot shows such a node. Figure B.3. JConsole: Showing a Cache Report a bug

Commands:
cd USDJDG_HOME/bin
./add-user.sh
./standalone.sh ... -Djboss.bind.address.management=192.168.122.5
<interfaces> <interface name="management"> <inet-address value="USD{jboss.bind.address.management:192.168.122.5}"/> </interface> [...] </interface>
function::kernel_string2_utf32 Name function::kernel_string2_utf32 - Retrieves UTF-32 string from kernel memory with alternative error string Synopsis Arguments addr The kernel address to retrieve the string from err_msg The error message to return when data isn't available Description This function returns a null terminated UTF-8 string converted from the UTF-32 string at a given kernel memory address. Reports the given error message on string copy fault or conversion error.

Commands:
kernel_string2_utf32:string(addr:long,err_msg:string)
Chapter 1. Red Hat Virtualization Architecture Red Hat Virtualization can be deployed as a self-hosted engine, or as a standalone Manager. A self-hosted engine is the recommended deployment option. 1.1. Self-Hosted Engine Architecture The Red Hat Virtualization Manager runs as a virtual machine on self-hosted engine nodes (specialized hosts) in the same environment it manages. A self-hosted engine environment requires one less physical server, but requires more administrative overhead to deploy and manage. The Manager is highly available without external HA management. The minimum setup of a self-hosted engine environment includes: One Red Hat Virtualization Manager virtual machine that is hosted on the self-hosted engine nodes. The RHV-M Appliance is used to automate the installation of a Red Hat Enterprise Linux 8 virtual machine, and the Manager on that virtual machine. A minimum of two self-hosted engine nodes for virtual machine high availability. You can use Red Hat Enterprise Linux hosts or Red Hat Virtualization Hosts (RHVH). VDSM (the host agent) runs on all hosts to facilitate communication with the Red Hat Virtualization Manager. The HA services run on all self-hosted engine nodes to manage the high availability of the Manager virtual machine. One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. Figure 1.1. Self-Hosted Engine Red Hat Virtualization Architecture 1.2. Standalone Manager Architecture The Red Hat Virtualization Manager runs on a physical server, or a virtual machine hosted in a separate virtualization environment. A standalone Manager is easier to deploy and manage, but requires an additional physical server. The Manager is only highly available when managed externally with a product such as Red Hat's High Availability Add-On. The minimum setup for a standalone Manager environment includes: One Red Hat Virtualization Manager machine. The Manager is typically deployed on a physical server. However, it can also be deployed on a virtual machine, as long as that virtual machine is hosted in a separate environment. The Manager must run on Red Hat Enterprise Linux 8. A minimum of two hosts for virtual machine high availability. You can use Red Hat Enterprise Linux hosts or Red Hat Virtualization Hosts (RHVH). VDSM (the host agent) runs on all hosts to facilitate communication with the Red Hat Virtualization Manager. One storage service, which can be hosted locally or on a remote server, depending on the storage type used. The storage service must be accessible to all hosts. Figure 1.2. Standalone Manager Red Hat Virtualization Architecture

Commands:
Chapter 15. Red Hat Enterprise Linux Atomic Host 7.6.3 15.1. Atomic Host OStree update : New Tree Version: 7.6.3 (hash: d3fc043862e78ecb2b4f3f16938414039bc0a29a069ab6b6dfb3d4ae3a1494e8) Changes since Tree Version 7.6.2 (hash: 50c320468370132958eeeffb90a23431a5bd1cc717aa68d969eb471d78879e66) Updated packages : microdnf-2-6.el7 15.2. Extras Updated packages : docker-1.13.1-94.gitb2f74b2.el7 dpdk-18.11-3.el7_6 15.2.1. Container Images New : Red Hat Universal Base Image 7 Container Image (rhel7/ubi7-container) Updated : Red Hat Enterprise Linux 7.6 Container Image (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux 7.6 Container Image for aarch64 (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd)

Commands:
7.2. Raising the Domain Level Important This is a non-reversible operation. If you raise the domain level from 0 to 1 , you cannot downgrade from 1 to 0 again. Command Line: Raising the Domain Level Log in as the administrator: Run the ipa domainlevel-set command and provide the required level: Web UI: Raising the Domain Level Select IPA Server Topology Domain Level . Click Set Domain Level .

Commands:
kinit admin
ipa domainlevel-set 1 ----------------------- Current domain level: 1 -----------------------
5.9.3. Checking the Default SELinux Context Use the matchpathcon command to check if files and directories have the correct SELinux context. From the matchpathcon (8) manual page: " matchpathcon queries the system policy and outputs the default security context associated with the file path." [10] . The following example demonstrates using the matchpathcon command to verify that files in /var/www/html/ directory are labeled correctly: As the Linux root user, run the touch /var/www/html/file{1,2,3} command to create three files ( file1 , file2 , and file3 ). These files inherit the httpd_sys_content_t type from the /var/www/html/ directory: As the Linux root user, run the chcon -t samba_share_t /var/www/html/file1 command to change the file1 type to samba_share_t . Note that the Apache HTTP Server cannot read files or directories labeled with the samba_share_t type. The matchpathcon -V option compares the current SELinux context to the correct, default context in SELinux policy. Run the matchpathcon -V /var/www/html/* command to check all files in the /var/www/html/ directory: The following output from the matchpathcon command explains that file1 is labeled with the samba_share_t type, but should be labeled with the httpd_sys_content_t type: To resolve the label problem and allow the Apache HTTP Server access to file1 , as the Linux root user, run the restorecon -v /var/www/html/file1 command: [10] The matchpathcon (8) manual page, as shipped with the libselinux-utils package in Red Hat Enterprise Linux, is written by Daniel Walsh. Any edits or changes in this version were done by Murray McAllister.

Commands:
~]# touch /var/www/html/file{1,2,3} ~]# ls -Z /var/www/html/ -rw-r--r-- root root unconfined_u:object_r:httpd_sys_content_t:s0 file1 -rw-r--r-- root root unconfined_u:object_r:httpd_sys_content_t:s0 file2 -rw-r--r-- root root unconfined_u:object_r:httpd_sys_content_t:s0 file3
~]USD matchpathcon -V /var/www/html/* /var/www/html/file1 has context unconfined_u:object_r:samba_share_t:s0, should be system_u:object_r:httpd_sys_content_t:s0 /var/www/html/file2 verified. /var/www/html/file3 verified.
/var/www/html/file1 has context unconfined_u:object_r:samba_share_t:s0, should be system_u:object_r:httpd_sys_content_t:s0
~]# restorecon -v /var/www/html/file1 restorecon reset /var/www/html/file1 context unconfined_u:object_r:samba_share_t:s0->system_u:object_r:httpd_sys_content_t:s0
Chapter 12. Allowing JavaScript-based access to the API server from additional hosts 12.1. Allowing JavaScript-based access to the API server from additional hosts The default OpenShift Container Platform configuration only allows the web console to send requests to the API server. If you need to access the API server or OAuth server from a JavaScript application using a different hostname, you can configure additional hostnames to allow. Prerequisites Access to the cluster as a user with the cluster-admin role. Procedure Edit the APIServer resource: USD oc edit apiserver.config.openshift.io cluster Add the additionalCORSAllowedOrigins field under the spec section and specify one or more additional hostnames: apiVersion: config.openshift.io/v1 kind: APIServer metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: "2019-07-11T17:35:37Z" generation: 1 name: cluster resourceVersion: "907" selfLink: /apis/config.openshift.io/v1/apiservers/cluster uid: 4b45a8dd-a402-11e9-91ec-0219944e0696 spec: additionalCORSAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) 1 1 The hostname is specified as a Golang regular expression that matches against CORS headers from HTTP requests against the API server and OAuth server. Note This example uses the following syntax: The (?i) makes it case-insensitive. The // pins to the beginning of the domain and matches the double slash following http: or https: . The \. escapes dots in the domain name. The (:|\z) matches the end of the domain name (\z) or a port separator (:) . Save the file to apply the changes.

Commands:
oc edit apiserver.config.openshift.io cluster
apiVersion: config.openshift.io/v1 kind: APIServer metadata: annotations: release.openshift.io/create-only: "true" creationTimestamp: "2019-07-11T17:35:37Z" generation: 1 name: cluster resourceVersion: "907" selfLink: /apis/config.openshift.io/v1/apiservers/cluster uid: 4b45a8dd-a402-11e9-91ec-0219944e0696 spec: additionalCORSAllowedOrigins: - (?i)//my\.subdomain\.domain\.com(:|\z) 1
14.2. Configure Locking (Library Mode) For Library mode, the locking element and its parameters are set within the default element and for each named cache, it occurs within the namedCache element. The following is an example of this configuration: Procedure 14.2. Configure Locking (Library Mode) The concurrencyLevel parameter specifies the concurrency level for the lock container. Set this value according to the number of concurrent threads interacting with the data grid. The isolationLevel parameter specifies the cache's isolation level. Valid isolation levels are READ_COMMITTED and REPEATABLE_READ . For details about isolation levels, see Section 16.1, "About Isolation Levels" The lockAcquisitionTimeout parameter specifies time (in milliseconds) after which a lock acquisition attempt times out. The useLockStriping parameter specifies whether a pool of shared locks are maintained for all entries that require locks. If set to FALSE , locks are created for each entry in the cache. For details, see Section 15.1, "About Lock Striping" The writeSkewCheck parameter is only valid if the isolationLevel is set to REPEATABLE_READ . If this parameter is set to FALSE , a disparity between a working entry and the underlying entry at write time results in the working entry overwriting the underlying entry. If the parameter is set to TRUE , such conflicts (namely write skews) throw an exception. The writeSkewCheck parameter can be only used with OPTIMISTIC transactions and it requires entry versioning to be enabled, with SIMPLE versioning scheme. Report a bug

Commands:
<infinispan> <!-- Other configuration elements here --> <default> <locking concurrencyLevel="USD{VALUE}" isolationLevel="USD{LEVEL}" lockAcquisitionTimeout="USD{TIME}" useLockStriping="USD{TRUE/FALSE}" writeSkewCheck="USD{TRUE/FALSE}" />
40.5.2. Using opreport on a Single Executable To retrieve more detailed profiled information about a specific executable, use opreport : <executable> must be the full path to the executable to be analyzed. <mode> must be one of the following: -l List sample data by symbols. For example, the following is part of the output from running the command opreport -l /lib/tls/libc- <version> .so : The first column is the number of samples for the symbol, the second column is the percentage of samples for this symbol relative to the overall samples for the executable, and the third column is the symbol name. To sort the output from the largest number of samples to the smallest (reverse order), use -r in conjunction with the -l option. -i <symbol-name> List sample data specific to a symbol name. For example, the following output is from the command opreport -l -i __gconv_transform_utf8_internal /lib/tls/libc- <version> .so : The first line is a summary for the symbol/executable combination. The first column is the number of samples for the memory symbol. The second column is the percentage of samples for the memory address relative to the total number of samples for the symbol. The third column is the symbol name. -d List sample data by symbols with more detail than -l . For example, the following output is from the command opreport -l -d __gconv_transform_utf8_internal /lib/tls/libc- <version> .so : The data is the same as the -l option except that for each symbol, each virtual memory address used is shown. For each virtual memory address, the number of samples and percentage of samples relative to the number of samples for the symbol is displayed. -x <symbol-name> Exclude the comma-separated list of symbols from the output. session : <name> Specify the full path to the session or a directory relative to the /var/lib/oprofile/samples/ directory.

Commands:
opreport <mode> <executable>
samples % symbol name 12 21.4286 __gconv_transform_utf8_internal 5 8.9286 _int_malloc 4 7.1429 malloc 3 5.3571 __i686.get_pc_thunk.bx 3 5.3571 _dl_mcount_wrapper_check 3 5.3571 mbrtowc 3 5.3571 memcpy 2 3.5714 _int_realloc 2 3.5714 _nl_intern_locale_data 2 3.5714 free 2 3.5714 strcmp 1 1.7857 __ctype_get_mb_cur_max 1 1.7857 __unregister_atfork 1 1.7857 __write_nocancel 1 1.7857 _dl_addr 1 1.7857 _int_free 1 1.7857 _itoa_word 1 1.7857 calc_eclosure_iter 1 1.7857 fopen@@GLIBC_2.1 1 1.7857 getpid 1 1.7857 memmove 1 1.7857 msort_with_tmp 1 1.7857 strcpy 1 1.7857 strlen 1 1.7857 vfprintf 1 1.7857 write
samples % symbol name 12 100.000 __gconv_transform_utf8_internal
vma samples % symbol name 00a98640 12 100.000 __gconv_transform_utf8_internal 00a98640 1 8.3333 00a9868c 2 16.6667 00a9869a 1 8.3333 00a986c1 1 8.3333 00a98720 1 8.3333 00a98749 1 8.3333 00a98753 1 8.3333 00a98789 1 8.3333 00a98864 1 8.3333 00a98869 1 8.3333 00a98b08 1 8.3333
Part VI. Installing and configuring KIE Server on Oracle WebLogic Server As a system administrator, you can configure your Oracle WebLogic Server for Red Hat KIE Server and install KIE Server on that Oracle server instance. Note Support for Red Hat Process Automation Manager on Oracle WebLogic Server is now in the maintenance phase. Red Hat will continue to support Red Hat Process Automation Manager on Oracle WebLogic Server with the following limitations: Red Hat will not release new certifications or software functionality. Red Hat will release only qualified security patches that have a critical impact and mission-critical bug fix patches. In the future, Red Hat might direct customers to migrate to new platforms and product components that are compatible with the Red Hat hybrid cloud strategy. Prerequisites An Oracle WebLogic Server instance version 12.2.1.3.0 or later is installed. For complete installation instructions, see the Oracle WebLogic Server product page . You have access to the Oracle WebLogic Server Administration Console, usually at http://<HOST>:7001/console .

Commands:
4.281. sblim-cmpi-fsvol 4.281.1. RHBA-2011:1549 - sblim-cmpi-fsvol bug fix and enhancement update An updated sblim-cmpi-fsvol package that fixes several bugs and provides various enhancements is now available for Red Hat Enterprise Linux 6. The sblim-cmpi-fsvol package provides the filesystem and volume management instrumentation allowing users to obtain information about mounted and unmounted file systems by use of CIMOM technology and infrastructure. The sblim-cmpi-fsvol package has been upgraded to upstream version 1.5.1, which includes the Linux_CSProcessor class registration fix, and provides a number of other bug fixes and enhancements over the version. (BZ# 694506 ) Bug Fix BZ# 663833 CIMOM did not collect any information about ext4 file systems because the Linux_Ext4FileSystem class was not defined. This class has been defined and information about ext4 file systems is now collected properly. All users of sblim-cmpi-fsvol are advised to upgrade to this updated sblim-cmpi-fsvol package, which resolves these issues and adds these enhancements.

Commands: