mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 8. Improving the latency in a multi-supplier replication environment In certain multi-supplier replication environments, for example if the servers are connected over a wide area network (WAN), the replication latency can be high if multiple suppliers receive updates at the same time. This happens when one supplier exclusively accesses a replica without releasing it for a long time. In such situations, other suppliers cannot send updates to this consumer, which increases the replication latency. To release a replica after a fixed amount of time, set the nsds5ReplicaReleaseTimeout parameter on suppliers and hubs. Note The 60 seconds default value is ideal for most environments. A value set too high or too low can have a negative impact on the replication performance. If you set the value too low, replication servers are constantly reacquiring each other, and servers are not able to send many updates. In a high-traffic replication environment, a longer timeout can improve situations where one supplier exclusively accesses a replica. However, in most cases, a value higher than 120 seconds slows down replication. 8.1. Setting the replication release timeout using the command line To improve the replication efficiency in a multi-supplier replication environment, update the replication release timeout value on all hubs and suppliers. Prerequisites You configured replication between multiple suppliers and hubs. Procedure Set the timeout value for the suffix: # dsconf -D " cn=Directory Manager " ldap://supplier.example.com replication set --suffix=" dc=example,dc=com " --repl-release-timeout= 70 This command changes the replication timeout of the example,dc=com suffix to 70 seconds. Restart the instance: # dsctl instance_name restart 8.2. Setting the replication release timeout using the web console To improve the replication efficiency in a multi-supplier replication environment, update the replication release timeout value on all hubs and suppliers. Prerequisites You configured replication between multiple suppliers and hubs. Procedure On the Replication tab, select the suffix entry. Click Show Advanced Settings . Update the value in the Replication Release Timeout field. Click Save Configuration .

Commands:
dsconf -D " cn=Directory Manager " ldap://supplier.example.com replication set --suffix=" dc=example,dc=com " --repl-release-timeout= 70
dsctl instance_name restart
18.2.4. Moving a Mount Point To change the directory in which a file system is mounted, use the following command: See Example 18.8, "Moving an Existing NFS Mount Point" for an example usage. Example 18.8. Moving an Existing NFS Mount Point An NFS storage contains user directories and is already mounted in /mnt/userdirs/ . As root , move this mount point to /home by using the following command: To verify the mount point has been moved, list the content of both directories:

Commands:
mount --move old_directory new_directory
~]# mount --move /mnt/userdirs /home
~]# ls /mnt/userdirs ~]# ls /home jill joe
Chapter 1. Installing software in GNOME You can install applications and other software packages using several methods in GNOME. 1.1. Prerequisites You have administrator permissions on the system. 1.2. The GNOME Software application GNOME Software is an utility that enables you to install and update applications and software components in a graphical interface. GNOME Software provides a catalog of graphical applications, which are the applications that include a *.desktop file. The available applications are grouped into multiple categories according to their purpose. GNOME Software uses the PackageKit and Flatpak technologies as its back ends. 1.3. Installing an application using GNOME Software This procedure installs a graphical application using the GNOME Software utility. Procedure Launch the GNOME Software application. Find the application that you want to install using any of the following methods: Click the search button in the upper-left corner of the window and type the name of the application. Browse the application categories in the Explore tab. Click the selected application. Click Install . 1.4. Installing an application to open a file type This procedure installs an application that can open a given file type. Prerequisites You can access a file of the required file type in your file system. Procedure Try opening a file that is associated with an application that is currently not installed on your system. GNOME automatically identifies the suitable application that can open the file, and offers to download the application. 1.5. Installing an RPM package file in GNOME This procedure installs an RPM software package that you manually downloaded as a file. Prerequisites You have downloaded the required RPM package. Procedure In the Files application, open the directory that stores the downloaded RPM package. Note By default, downloaded files are stored in the /home/ user /Downloads/ directory. Double-click the RPM package file to install it. 1.6. Installing an application from the Activities Overview search This procedure installs a graphical application from search results on the GNOME Activities Overview screen. Procedure Open the Activities Overview screen. Type the name of the required application in the search entry. The search results display the application's icon, name, and description. Click the application's icon to open the Software application. Click Install to finish the installation in Software . Verification Click Open to launch the installed application. 1.7. Additional resources Managing software with the DNF tool Chapter 2, Installing applications using Flatpak

Commands:
Chapter 16. Configuring SSH to use RSA SSH is used to clone Git repositories. By default, the DSA encryption algorithm is provided by Business Central. However, some SSH clients, for example SSH clients in the Fedora 23 environment, use the RSA algorithm instead of the DSA algorithm. Business Central contains a system property that you can use to switch from DSA to RSA if required. Note SSH clients on supported configurations, for example Red Hat Enterprise Linux 7, are not affected by this issue. For a list of supported configurations, see Red Hat Process Automation Manager 7 Supported Configurations . Procedure Complete one of the following tasks to enable this system property: Modify the ~/.ssh/config file on the client side as follows to force the SSH client to accept the deprecated DSA algorithm: Include the -Dorg.uberfire.nio.git.ssh.algorithm=RSA parameter when you start Business Central, for example:

Commands:
Host <SERVER_IP> HostKeyAlgorithms +ssh-dss
./standalone.sh -c standalone-full.xml -Dorg.uberfire.nio.git.ssh.algorithm=RSA
15.6. Exposing GNOME Virtual File Systems to All Other Applications In addition to applications built with the GIO library being able to access GVFS mounts, GVFS also provides a FUSE daemon which exposes active GVFS mounts. This means that any application can access active GVFS mounts using the standard POSIX APIs as though they were regular filesystems. Nevertheless, there are applications in which additional library dependency and new VFS subsystem specifics may be unsuitable or too complex. For such reasons and to boost compatibility, GVFS provides a FUSE ( Filesystem in Userspace ) daemon, which exposes active mounts through its mount for standard POSIX (Portable Operating System Interface) access. This daemon transparently translates incoming requests to imitate a local file system for applications. Important The translation coming from the different design is not 100% feature-compatible and you may experience difficulties with certain combinations of applications and GVFS back ends. The FUSE daemon starts automatically with the GVFS master daemon and places its mount either in the /run/user/ UID /gvfs or ~/.gvfs files as a fallback. Manual browsing shows that there individual directories for each GVFS mount. When you are opening documents from GVFS locations with non-native applications, a transformed path is passed as an argument. Note that native GIO applications automatically translate this path back to a native URI .

Commands:
8.101. libwacom 8.101.1. RHBA-2013:1567 - libwacom bug fix update Updated libwacom packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libwacom packages contain a library that provides access to a tablet model database. The libwacom packages expose the contents of this database to applications, allowing for tablet-specific user interfaces. The libwacom packages allow the GNOME tools to automatically configure screen mappings and calibrations, and provide device-specific configurations. Bug Fix BZ# 847427 Previously, the Wacom Stylus pen was not supported on Lenovo ThinkPad X220 tablets by the libwacom database. Consequently, the pen was not recognized by the gnome-wacom-properties tool, and warning messages were returned. Support for the Wacom Stylus on Lenovo ThinkPad X220 tablets has been added and gnome-wacom-properties is now able to calibrate the tablet. Users of libwacom are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.2.23. /proc/mtrr This file refers to the current Memory Type Range Registers (MTRRs) in use with the system. If the system architecture supports MTRRs, then the /proc/mtrr file may look similar to the following: MTRRs are used with the Intel P6 family of processors (Pentium II and higher) and control processor access to memory ranges. When using a video card on a PCI or AGP bus, a properly configured /proc/mtrr file can increase performance more than 150%. Most of the time, this value is properly configured by default. More information on manually configuring this file can be found locally at the following location:

Commands:
reg00: base=0x00000000 ( 0MB), size= 256MB: write-back, count=1 reg01: base=0xe8000000 (3712MB), size= 32MB: write-combining, count=1
/usr/share/doc/kernel-doc- <version> /Documentation/mtrr.txt
3.3. Search Auto-Completion The Administration Portal provides auto-completion to help you create valid and powerful search queries. As you type each part of a search query, a drop-down list of choices for the part of the search opens below the Search Bar. You can either select from the list and then continue typing/selecting the part of the search, or ignore the options and continue entering your query manually. The following table specifies by example how the Administration Portal auto-completion assists in constructing a query: Hosts: Vms.status = down Table 3.2. Example Search Queries Using Auto-Completion Input List Items Displayed Action h Hosts (1 option only) Select Hosts or type Hosts Hosts: All host properties Type v Hosts: v host properties starting with a v Select Vms or type Vms Hosts: Vms All virtual machine properties Type s Hosts: Vms.s All virtual machine properties beginning with s Select status or type status Hosts: Vms.status = != Select or type = Hosts: Vms.status = All status values Select or type down

Commands:
Chapter 4. Updating Directory Server Red Hat frequently releases updated versions of Red Hat Directory Server 11. This section describes how to update the Directory Server packages. If you instead want to migrate Red Hat Directory Server 10 to version 11, see Chapter 5, Migrating Directory Server 10 to Directory Server 11 . Prerequisites Red Hat Directory Server 11 installed on the server. The system to update is registered to the Red Hat subscription management service. A valid Red Hat Directory Server subscription is attached to the server. 4.1. Updating the Directory Server packages Use the yum utility to update the module, which also automatically updates the related packages. The following procedure updates Directory Server from version 11.8 to 11.9. Disable the Directory Server 11.8 repository: Enable the Directory Server 11.9 repository: Update the Directory Server packages: This command updates Directory Server packages and their dependencies to version 11.9. During the update, the dirsrv service restarts automatically for all instances on the server. Additional resources For details about available Directory Server repositories, see What are the names of the Red Hat repositories that have to be enabled .

Commands:
subscription-manager repos --disable dirsrv-11.8-for-rhel-8-x86_64-rpms Repository 'dirsrv-11.8-for-rhel-8-x86_64-rpms' is disabled for this system.
subscription-manager repos --enable=dirsrv-11.9-for-rhel-8-x86_64-rpms Repository 'dirsrv-11.9-for-rhel-8-x86_64-rpms' is enabled for this system.
yum module update redhat-ds
4.342. vsftpd 4.342.1. RHBA-2012:0001 - vsftpd bug fix update An updated vsftpd package that fixes one bug is now available for Red Hat Enterprise Linux 6. The vsftpd package includes a Very Secure FTP (File Transfer Protocol) daemon. Bug Fix BZ# 767108 The vsftpd daemon sets a value of the RLIMIT_AS variable during its initialization phase. With Red Hat Enterprise Linux 6.1, the RLIMIT_AS value (100 MB) became insufficient which restricted LDAP users from authentication to the system using vsftpd. With this update, the initial RLIMIT_AS value has been increased to 200 MB, and vsftpd now can be used for LDAP authentication as expected. All users of vsftpd are advised to upgrade to this updated package, which fixes this bug.

Commands:
2.3. Directory Providers The following directory providers are supported in Infinispan Query: RAM Directory Provider Filesystem Directory Provider Infinispan Directory Provider Report a bug 2.3.1. RAM Directory Provider Storing the global index locally in Red Hat JBoss Data Grid's Query Module allows each node to maintain its own index. use Lucene 's in-memory or filesystem-based index directory. The following example demonstrates an in-memory, RAM-based index store: Report a bug 2.3.2. Filesystem Directory Provider To configure the storage of indexes, set the appropriate properties when enabling indexing in the JBoss Data Grid configuration. This example shows a disk-based index store: Example 2.1. Disk-based Index Store Report a bug 2.3.3. Infinispan Directory Provider In addition to the Lucene directory implementations, Red Hat JBoss Data Grid also ships with an infinispan-directory module. Note Red Hat JBoss Data Grid only supports infinispan-directory in the context of the Querying feature, not as a standalone feature. The infinispan-directory allows Lucene to store indexes within the distributed data grid. This allows the indexes to be distributed, stored in-memory, and optionally written to disk using the cache store for durability. Sharing the same index instance using the Infinispan Directory Provider introduces a write contention point, as only one instance can write on the same index at the same time. Important By default the exclusive_index_use is set to true , as this provides major performance increases; however, if external applications access the same index in use by Infinispan this property must be set to false . The default value is recommended for the majority of applications and use cases due to the performance increases, so only change this if absolutely necessary. InfinispanIndexManager provides a default back end that sends all updates to master node which later applies the updates to the index. In case of master node failure, the update can be lost, therefore keeping the cache and index non-synchronized. Non-default back ends are not supported. Example 2.2. Enable Shared Indexes When using an indexed, clustered cache ensure that the caches containing the index data are also clustered, as described in Section 2.5.2, "Tuning Infinispan Directory" . Report a bug

Commands:
<namedCache name="indexesInMemory"> <indexing enabled="true"> <properties> <property name="default.directory_provider" value="ram"/> </properties> </indexing> </namedCache>
<namedCache name="indexesOnDisk"> <indexing enabled="true"> <properties> <property name="default.directory_provider" value="filesystem"/> <property name="default.indexBase" value="/tmp/ispn_index"/> </properties> </indexing> </namedCache>
<namedCache name="globalSharedIndexes"> <clustering mode="local"/> <indexing enabled="true"> <properties> <property name="default.directory_provider" value="infinispan"/> <property name="default.indexmanager" value="org.infinispan.query.indexmanager.InfinispanIndexManager" /> </properties> </indexing> </namedCache>
Chapter 16. Configuring the loopback interface by using nmcli By default, NetworkManager does not manage the loopback ( lo ) interface. After creating a connection profile for the lo interface, you can configure this device by using NetworkManager. Some of the examples are as follows: Assign additional IP addresses to the lo interface Define DNS addresses Change the Maximum Transmission Unit (MTU) size of the lo interface Procedure Create a new connection of type loopback : Configure custom connection settings, for example: To assign an additional IP address to the interface, enter: Note NetworkManager manages the lo interface by always assigning the IP addresses 127.0.0.1 and ::1 that are persistent across the reboots. You can not override 127.0.0.1 and ::1 . However, you can assign additional IP addresses to the interface. To set a custom Maximum Transmission Unit (MTU), enter: To set an IP address to your DNS server, enter: If you set a DNS server in the loopback connection profile, this entry is always available in the /etc/resolv.conf file. The DNS server entry remains independent of whether or not the host roams between different networks. Activate the connection: Verification Display the settings of the lo interface: Verify the DNS address:

Commands:
nmcli connection add con-name example-loopback type loopback
nmcli connection modify example-loopback +ipv4.addresses 192.0.2.1/24
nmcli con mod example-loopback loopback.mtu 16384
nmcli connection modify example-loopback ipv4.dns 192.0.2.0
nmcli connection up example-loopback
ip address show lo 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16384 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet 192.0.2.1/24 brd 192.0.2.255 scope global lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever
cat /etc/resolv.conf nameserver 192.0.2.0
function::kernel_string_quoted Name function::kernel_string_quoted - Retrieves and quotes string from kernel memory Synopsis Arguments addr the kernel memory address to retrieve the string from Description Returns the null terminated C string from a given kernel memory address where any ASCII characters that are not printable are replaced by the corresponding escape sequence in the returned string. Note that the string will be surrounded by double quotes. If the kernel memory data is not accessible at the given address, the address itself is returned as a string, without double quotes.

Commands:
kernel_string_quoted:string(addr:long)
Chapter 14. Ensuring correct data displays in HawtIO If the display of the queues and connections in HawtIO 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 HawtIO, 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.64. gnome-settings-daemon 7.64.1. RHBA-2015:0658 - gnome-settings-daemon bug fix update Updated gnome-settings-daemon packages that fix one bug are now available for Red Hat Enterprise Linux 6. The gnome-settings-daemon packages contain a daemon to share settings from GNOME to other applications. It also handles global key bindings, as well as a number of desktop-wide settings. Bug Fix BZ# 1098370 Due to a memory leak in the "housekeeping" plug-in, gnome-settings-daemon did not correctly release certain memory segments that were not needed anymore. Consequently, the daemon could possibly exhaust all available memory, in which case the system encountered performance issues. With this update, the "housekeeping" plug-in has been fixed to properly free unused memory. As a result, the above-mentioned scenario is prevented. Users of gnome-settings-daemon are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 10. Using Collector runtime configuration Important Using Collector runtime configuration is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in 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 about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . Collector runtime configuration enables you to modify some collector behaviors without restarting Collector. Collector runtime configuration is set using a ConfigMap object called collector-config . When you create or update the ConfigMap object, Collector refreshes the runtime configuration. When you delete the ConfigMap object, the settings revert to the default runtime configuration values. Currently, only two settings are controlled by using Collector runtime configuration: networking.externalIps.enabled controls if the visualizing external entities feature is enabled or disabled. The default is DISABLED . In release 4.6, this setting was networking.externalIps.enable and was a boolean. For more information, see Visualizing external entities . networking.maxConnectionsPerMinute is the maximum number of open networking connections reported by Collector per container per minute. The default value is 2048. The following example enables the visualizing external entities feature and sets maxConnectionsPerMinute to 2048. apiVersion: v1 kind: ConfigMap metadata: name: collector-config namespace: stackrox data: runtime_config.yaml: | 1 networking: externalIps: enabled: ENABLED maxConnectionsPerMinute: 2048 1 RHACS mounts this file at /etc/stackrox/runtime_config.yaml .

Commands:
apiVersion: v1 kind: ConfigMap metadata: name: collector-config namespace: stackrox data: runtime_config.yaml: | 1 networking: externalIps: enabled: ENABLED maxConnectionsPerMinute: 2048