mtpti5iD/redhat-docs_dataset huggingface dataset:
1.10.2. GLOBAL SETTINGS The GLOBAL SETTINGS panel is where the LVS administrator defines the networking details for the primary LVS router's public and private network interfaces. Figure 1.32. The GLOBAL SETTINGS Panel The top half of this panel sets up the primary LVS router's public and private network interfaces. Primary server public IP The publicly routable real IP address for the primary LVS node. Primary server private IP The real IP address for an alternative network interface on the primary LVS node. This address is used solely as an alternative heartbeat channel for the backup router. Use network type Selects select NAT routing. The three fields are specifically for the NAT router's virtual network interface connected the private network with the real servers. NAT Router IP The private floating IP in this text field. This floating IP should be used as the gateway for the real servers. NAT Router netmask If the NAT router's floating IP needs a particular netmask, select it from drop-down list. NAT Router device Defines the device name of the network interface for the floating IP address, such as eth1:1 .

Commands:
Chapter 3. Importing Puppet classes and environments into Satellite Import Puppet classes and environments from the installed Puppet modules to Satellite Server or any attached Capsule Server before you assign any of the classes to hosts. Prerequisites Ensure to select Any Organization and Any Location as context, otherwise the import might fail. Procedure In the Satellite web UI, navigate to Configure > Puppet ENC > Classes or Configure > Puppet ENC > Environments . Click Import in the upper right corner and select which Capsule you want to import modules from. You may typically choose between your Satellite Server or any attached Capsule Server. Select the Puppet environments to import using checkboxes on the left. Click Update to import the Puppet environments and classes to Satellite. The import should result in a notification as follows:

Commands:
Successfully updated environments and Puppet classes from the on-disk Puppet installation
Chapter 3. Performing Batch Operations Process operations in groups, either interactively or using batch files. Prerequisites A running Data Grid cluster. 3.1. Performing Batch Operations with Files Create files that contain a set of operations and then pass them to the Data Grid CLI. Procedure Create a file that contains a set of operations. For example, create a file named batch that creates a cache named mybatch , adds two entries to the cache, and disconnects from the CLI. Tip Configure the CLI with the autoconnect-url property instead of using the connect command directly in your batch files. Run the CLI and specify the file as input. Note CLI batch files support system property expansion. Strings that use the USD{property} format are replaced with the value of the property system property. 3.2. Performing Batch Operations Interactively Use the standard input stream, stdin , to perform batch operations interactively. Procedure Start the Data Grid CLI in interactive mode. Tip You can configure the CLI connection with the autoconnect-url property instead of using the -c argument. Run batch operations, for example:

Commands:
connect --username=<username> --password=<password> <hostname>:11222 create cache --template=org.infinispan.DIST_SYNC mybatch put --cache=mybatch hello world put --cache=mybatch hola mundo ls caches/mybatch disconnect
bin/cli.sh -f batch
bin/cli.sh -c localhost:11222 -f -
create cache --template=org.infinispan.DIST_SYNC mybatch put --cache=mybatch hello world put --cache=mybatch hola mundo disconnect quit
Chapter 6. Typing emoji characters You can type emoji characters using several different methods in GNOME, depending on the type of the application. 6.1. Typing emoji characters in GTK applications This procedure inserts an emoji character in an application that uses the GTK graphical toolkit, such as in native GNOME applications. Prerequisites Make sure that the application is built on the GTK toolkit. Procedure Open a GTK application. Make sure that a text field is active. Press Ctrl + ; . The emoji selection menu opens. Browse the emoji characters or type a keyword that identifies the emoji character that you want to insert, such as smile . For the full list of keywords associated with emoji characters, see the Other Keywords column on the Emoji List page. Click the selected character, or navigate to it using the cursor keys and press Enter . Verification Check that the intended emoji character now appears at your cursor. 6.2. Typing emoji characters in any applications This procedure inserts an emoji character in any application, regardless of the graphical toolkit that the application uses. Procedure Open an application. Make sure that a text field is active. Press Ctrl + . . The underscored letter e appears at your cursor. Type a keyword that identifies the emoji character that you want to insert, such as smile . For the full list of keywords associated with emoji characters, see the Other Keywords column on the Emoji List page. Repeatedly press Space to browse the emoji characters that match your keyword. Confirm the selected emoji character by pressing Enter . Verification Check that the intended emoji character now appears at your cursor.

Commands:
Chapter 320. Spring Event Component Available as of Camel version 1.4 The spring-event: component provides access to the Spring ApplicationEvent objects. This allows you to publish ApplicationEvent objects to a Spring ApplicationContext or to consume them. You can then use Enterprise Integration Patterns to process them such as Message Filter . 320.1. URI format spring-event://default[?options] Note, at the moment there are no options for this component. That can easily change in future releases, so please check back. 320.2. Spring Event Options The Spring Event component has no options. The Spring Event endpoint is configured using URI syntax: with the following path and query parameters: 320.2.1. Path Parameters (1 parameters): Name Description Default Type name Name of endpoint String 320.2.2. Query Parameters (4 parameters): Name Description Default Type bridgeErrorHandler (consumer) Allows for bridging the consumer to the Camel routing Error Handler, which mean any exceptions occurred while the consumer is trying to pickup incoming messages, or the likes, will now be processed as a message and handled by the routing Error Handler. By default the consumer will use the org.apache.camel.spi.ExceptionHandler to deal with exceptions, that will be logged at WARN or ERROR level and ignored. false boolean exceptionHandler (consumer) To let the consumer use a custom ExceptionHandler. Notice if the option bridgeErrorHandler is enabled then this option is not in use. By default the consumer will deal with exceptions, that will be logged at WARN or ERROR level and ignored. ExceptionHandler exchangePattern (consumer) Sets the exchange pattern when the consumer creates an exchange. ExchangePattern synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean 320.3. Spring Boot Auto-Configuration The component supports 4 options, which are listed below. Name Description Default Type camel.component.spring-event.enabled Enable spring-event component true Boolean camel.component.spring-event.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean camel.language.spel.enabled Enable spel language true Boolean camel.language.spel.trim Whether to trim the value to remove leading and trailing whitespaces and line breaks true Boolean 320.4. See Also Configuring Camel Component Endpoint Getting Started

Commands:
spring-event://default[?options]
spring-event:name
Chapter 7. Logging statistics per search operation During some search operations, especially with filters such as (cn=user*) , the time the server spends for receiving the tasks and then sending the result back ( etime ) can be very long. Expanding the access log with information related to indexes used during search operation helps to diagnose why etime value is resource expensive. Use the nsslapd-statlog-level attribute to enable collecting statistics, such as a number of index lookups (database read operations) and overall duration of index lookups for each search operation, with minimal impact on the server. Prerequisites You enabled access logging. Procedure Enable search operation metrics: Restart the instance: Verification Perform a search operation: View the access log file and find the search statistics records: Additional resources nsslapd-statlog-level

Commands:
dsconf -D "cn=Directory Manager" instance_name config replace nsslapd-statlog-level=1
dsctl instance_name restart
ldapsearch -D "cn=Directory Manager" -H ldap:// server.example.com -b "dc=example,dc=com" -s sub -x "cn=user*"
cat /var/log/dirsrv/slapd- instance_name /access [16/Nov/2022:11:34:11.834135997 +0100] conn=1 op=73 SRCH base="dc=example,dc=com" scope=2 filter="(cn=user )"* attrs=ALL [16/Nov/2022:11:34:11.835750508 +0100] conn=1 op=73 STAT read index: attribute=objectclass key(eq)= referral --> count 0 [16/Nov/2022:11:34:11.836648697 +0100] conn=1 op=73 STAT read index: attribute=cn key(sub)= er_ --> count 25 [16/Nov/2022:11:34:11.837538489 +0100] conn=1 op=73 STAT read index: attribute=cn key(sub)= ser --> count 25 [16/Nov/2022:11:34:11.838814948 +0100] conn=1 op=73 STAT read index: attribute=cn key(sub)= use --> count 25 [16/Nov/2022:11:34:11.841241531 +0100] conn=1 op=73 STAT read index: attribute=cn key(sub)= ^us --> count 25 [16/Nov/2022:11:34:11.842230318 +0100] conn=1 op=73 STAT read index: duration 0.000010276 [16/Nov/2022:11:34:11.843185322 +0100] conn=1 op=73 RESULT err=0 tag=101 nentries=24 wtime=0.000078414 optime=0.001614101 etime=0.001690742
7.157. nfs-utils 7.157.1. RHBA-2013:0468 - nfs-utils bug fix update Updated nfs-utils packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The nfs-utils packages provide a daemon for the kernel Network File System (NFS) server, and related tools such as the mount.nfs, umount.nfs, and showmount. Bug Fixes BZ# 797209 Prior to this update, the rpc.mound daemon could cause NFS clients with already mounted NFSv3 shares to become suspended. This update modifies the underlying code to parse the IP address earlier. BZ# 802469 Prior to this update, nfs-utils allowed stronger encryption types than Single DES. As a consequence, mounts to legacy servers that used the "-o sec=krb5" option failed. This update adds the -l flag to allow only Single DES. Now, secure mounts work with legacy servers as expected. BZ# 815673 Prior to this update, NFS clients could fail to mount a share with the NFSv4 server if the server had a large amount of exports to netgroups. As a consequence, NFSv4 mounts could become suspended. This update modifies the use_ipaddr case so that NFSv4 now mounts as expected. BZ#849945 Prior to this update, the NFS idmapper failed to initialize as expected. As a consequence, file permissions were incorrect. This update modifies the underlying code so that the idmapper initializes correctly. Users of nfs-utils are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 5. Lock Management Lock management is a common cluster-infrastructure service that provides a mechanism for other cluster infrastructure components to synchronize their access to shared resources. In a Red Hat Enterprise Linux cluster, DLM (Distributed Lock Manager) is the lock manager. A lock manager is a traffic cop who controls access to resources in the cluster, such as access to a GFS file system. You need it because without a lock manager, there would be no control over access to your shared storage, and the nodes in the cluster would corrupt each other's data. As implied in its name, DLM is a distributed lock manager and runs in each cluster node; lock management is distributed across all nodes in the cluster. GFS2 and CLVM use locks from the lock manager. GFS2 uses locks from the lock manager to synchronize access to file system metadata (on shared storage). CLVM uses locks from the lock manager to synchronize updates to LVM volumes and volume groups (also on shared storage). In addition, rgmanager uses DLM to synchronize service states. 5.1. DLM Locking Model The DLM locking model provides a rich set of locking modes and both synchronous and asynchronous execution. An application acquires a lock on a lock resource. A one-to-many relationship exists between lock resources and locks: a single lock resource can have multiple locks associated with it. A lock resource can correspond to an actual object, such as a file, a data structure, a database, or an executable routine, but it does not have to correspond to one of these things. The object you associate with a lock resource determines the granularity of the lock. For example, locking an entire database is considered locking at coarse granularity. Locking each item in a database is considered locking at a fine granularity. The DLM locking model supports: Six locking modes that increasingly restrict access to a resource The promotion and demotion of locks through conversion Synchronous completion of lock requests Asynchronous completion Global data through lock value blocks The DLM provides its own mechanisms to support its locking features, such as inter-node communication to manage lock traffic and recovery protocols to re-master locks after a node failure or to migrate locks when a node joins the cluster. However, the DLM does not provide mechanisms to actually manage the cluster itself. Therefore the DLM expects to operate in a cluster in conjunction with another cluster infrastructure environment that provides the following minimum requirements: The node is a part of a cluster. All nodes agree on cluster membership and has quorum. An IP address must communicate with the DLM on a node. Normally the DLM uses TCP/IP for inter-node communications which restricts it to a single IP address per node (though this can be made more redundant using the bonding driver). The DLM can be configured to use SCTP as its inter-node transport which allows multiple IP addresses per node. The DLM works with any cluster infrastructure environments that provide the minimum requirements listed above. The choice of an open source or closed source environment is up to the user.

Commands:
B.17. Common XML Errors The libvirt tool uses XML documents to store structured data. A variety of common errors occur with XML documents when they are passed to libvirt through the API. Several common XML errors - including misformatted XML, inappropriate values, and missing elements - are detailed below. B.17.1. Editing Domain Definition Although it is not recommended, it is sometimes necessary to edit a guest virtual machine's (or a domain's) XML file manually. To access the guest's XML for editing, use the following command: This command opens the file in a text editor with the current definition of the guest virtual machine. After finishing the edits and saving the changes, the XML is reloaded and parsed by libvirt . If the XML is correct, the following message is displayed: Important When using the edit command in virsh to edit an XML document, save all changes before exiting the editor. After saving the XML file, use the xmllint command to validate that the XML is well-formed, or the virt-xml-validate command to check for usage problems: If no errors are returned, the XML description is well-formed and matches the libvirt schema. While the schema does not catch all constraints, fixing any reported errors will further troubleshooting. XML documents stored by libvirt These documents contain definitions of states and configurations for the guests. These documents are automatically generated and should not be edited manually. Errors in these documents contain the file name of the broken document. The file name is valid only on the host machine defined by the URI, which may refer to the machine the command was run on. Errors in files created by libvirt are rare. However, one possible source of these errors is a downgrade of libvirt - while newer versions of libvirt can always read XML generated by older versions, older versions of libvirt may be confused by XML elements added in a newer version.

Commands:
virsh edit name_of_guest.xml
virsh edit name_of_guest.xml Domain name_of_guest.xml XML configuration edited.
xmllint --noout config.xml
virt-xml-validate config.xml
8.142. mod_auth_kerb 8.142.1. RHBA-2014:1557 - mod_auth_kerb bug fix update Updated mod_auth_kerb packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The mod_auth_kerb packages provide a module for the Apache HTTP Server designed to provide Kerberos authentication over HTTP. The module supports the Negotiate authentication method, which performs full Kerberos authentication based on ticket exchanges. Bug Fixes BZ# 970678 This update adds the missing description of the "KrbLocalUserMapping" option to the README file. BZ# 981248 Previously, the mod_auth_kerb module was not compatible with the way certain browsers, such as Mozilla Firefox, handled an expired Kerberos ticket. As a consequence, opening a Kerberos-protected page in these browsers with an expired Kerberos ticket caused mod_auth_kerb to fail. With this update, the error in mod_auth_kerb has been addressed and the mentioned problem no longer occurs. BZ# 1050015 Due to a bug in the underlying source code, when the "S4U2Proxy" extension was configured, the mod_auth_kerb module did not renew tickets that were not valid yet. This update applies a patch to fix this bug and the tickets are now correctly renewed as expected. Users of mod_auth_kerb are advised to upgrade to these updated packages, which fix these bugs.

Commands:
10.2. GLIBC In Red Hat Enterprise Linux 7, the glibc libraries ( libc , libm , libpthread , NSS plug-ins, and others) are based on the glibc 2.17 release, which includes numerous enhancements and bug fixes relative to the Red Hat Enterprise Linux 6 equivalent. Notable highlights of the Red Hat Enterprise Linux 7 glibc libraries are the following: Experimental ISO C11 support; New Linux interfaces: prlimit , prlimit64 , fanotify_init , fanotify_mark , clock_adjtime , name_to_handle_at , open_by_handle_at , syncfs , setns , sendmmsg , process_vm_readv , process_vm_writev ; New optimized string functions for AMD64 and Intel 64 architectures using Streaming SIMD Extensions (SSE), Supplemental Streaming SIMD Extensions 3 (SSSE3), Streaming SIMD Extensions 4.2 (SSE4.2), and Advanced Vector Extensions (AVX); New optimized string functions for IBM PowerPC and IBM POWER7; New optimized string functions for IBM S/390 and IBM System z with specifically optimized routines for IBM System z10 and IBM zEnterprise 196; New locales: os_RU, bem_ZA, en_ZA, ff_SN, sw_KE, sw_TZ, lb_LU, wae_CH, yue_HK, lij_IT, mhr_RU, bho_IN, unm_US, es_CU, ta_LK, ayc_PE, doi_IN, ia_FR, mni_IN, nhn_MX, niu_NU, niu_NZ, sat_IN, szl_PL, mag_IN; New encodings: CP770, CP771, CP772, CP773, CP774; New interfaces: scandirat , scandirat64 ; Checking versions of the FD_SET, FD_CLR, FD_ISSET, poll, and ppoll file descriptors added; Caching of the netgroup database is now supported in the nscd daemon; The new function secure_getenv() allows secure access to the environment, returning NULL if running in a SUID or SGID process. This function replaces the internal function __secure_getenv() ; The crypt() function now fails if passed salt bytes that violate the specification for those values. On Linux, the crypt() function will consult the /proc/sys/crypto/fips_enabled file to determine if FIPS mode is enabled, and fail on encrypted strings using the Message-Digest algorithm 5 (MD5) or Data Encryption Standard (DES) algorithm when the mode is enabled; The clock_* suite of functions (declared in <time.h>) is now available directly in the main C library. Previously it was necessary to link with -lrt to use these functions. This change has the effect that a single-threaded program that uses a function such as clock_gettime() (and is not linked with -lrt ) will no longer implicitly load the pthreads library at runtime and so will not suffer the overheads associated with multi-thread support in other code such as the C++ runtime library; New header <sys/auxv.h> and function getauxval() allow easy access to the AT_* key-value pairs passed from the Linux kernel. The header also defines the HWCAP_* bits associated with the AT_HWCAP key; A new class of installed header has been documented for low-level platform-specific functionality. PowerPC added the first instance with a function to provide time base register access.

Commands:
2.13. Valgrind Valgrind provides a number of detection and profiling tools to help improve the performance of your applications. These tools can detect memory and thread-related errors, as well as heap, stack, and array overruns, letting you easily locate and correct errors in your application code. They can also profile the cache, the heap, and branch-prediction to identify factors that may increase application speed and minimize memory usage. Valgrind analyzes your application by running it on a synthetic CPU and instrumenting existing application code as it is executed. It then prints commentary that clearly identifies each process involved in application execution to a user-specified file, file descriptor, or network socket. Note that executing instrumented code can take between four and fifty times longer than normal execution. Valgrind can be used on your application as-is, without recompiling. However, because Valgrind uses debugging information to pinpoint issues in your code, if your application and support libraries were not compiled with debugging information enabled, Red Hat recommends recompiling to include this information. Valgrind also integrates with the GNU Project Debugger (gdb) to improve debugging efficiency. Valgrind and its subordinate tools are useful for memory profiling. For detailed information about using Valgrind to profile system memory, see Section 7.2.2, "Profiling Application Memory Usage with Valgrind" . For detailed information about Valgrind, see the Red Hat Enterprise Linux 7 Developer Guide . For detailed information about using Valgrind, see the man page: Accompanying documentation can also be found in /usr/share/doc/valgrind- version when the valgrind package is installed.

Commands:
man valgrind
A.14. Missing Characters on Guest Console with Japanese Keyboard On a Red Hat Enterprise Linux 7 host, connecting a Japanese keyboard locally to a machine may result in typed characters such as the underscore (the _ character) not being displayed correctly in guest consoles. This occurs because the required keymap is not set correctly by default. With Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 guests, there is usually no error message produced when pressing the associated key. However, Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 guests may display an error similar to the following: To fix this issue in virt-manager , perform the following steps: Open the affected guest in virt-manager . Click View Details . Select Display VNC in the list. Change Auto to ja in the Keymap pull-down menu. Click the Apply button. Alternatively, to fix this issue using the virsh edit command on the target guest: Run virsh edit guestname Add the following attribute to the <graphics> tag: keymap='ja' . For example:

Commands:
atkdb.c: Unknown key pressed (translated set 2, code 0x0 on isa0060/serio0). atkbd.c: Use 'setkeycodes 00 <keycode>' to make it known.
<graphics type='vnc' port='-1' autoport='yes' keymap='ja' />