mtpti5iD/redhat-docs_dataset huggingface dataset:
5.2. Adding Dependent Modules Add a MANIFEST.MF file in the META-INF directory, and the core API dependencies for resource adapter with the following line. If your translator depends upon any other third party jar files, ensure a module exists and add the module name to the above MANIFEST.MF file.

Commands:
Dependencies: org.jboss.teiid.common-core,org.jboss.teiid.api,javax.api
15.7. Password Management of GVFS Mounts A typical GVFS mount asks for credentials on its activation unless the resource allows anonymous authentication or does not require any at all. Presented in a standard GTK+ dialog, the user is able to choose whether the password should be saved or not. Procedure 15.5. Example: Authenticated Mount Process Open Files and activate the address bar by pressing Ctrl + L . Enter a well-formed URI string of a service that needs authentication (for example, sftp://localhost/ ). The credentials dialog is displayed, asking for a user name, password and password store options. Fill in the credentials and confirm. In case the persistent storage is selected, the password is saved in the user keyring. GNOME Keyring is a central place for secrets storage. It is encrypted and automatically unlocked on desktop session start using the password provided on login by default. If it is protected by a different password, the password is set at the first use. To manage the stored password and GNOME Keyring itself, the Seahorse application is provided. It allows individual records to be removed or passwords changed. For more information on Seahorse , consult the help manual for Seahorse embedded directly in the desktop.

Commands:
8.2.2. IPsec Interfaces With Red Hat Enterprise Linux it is possible to connect to other hosts or networks using a secure IP connection, known as IPsec. For instructions on setting up IPsec using the Network Administration Tool ( system-config-network ), refer to the chapter titled Network Configuration in the System Administrators Guide . For instructions on setting up IPsec manually, refer to the chapter titled Virtual Private Networks in the Security Guide . The following example shows the ifcfg file for a network-to-network IPsec connection for LAN A. The unique name to identify the connection in this example is ipsec1 , so the resulting file is named /etc/sysconfig/network-scripts/ifcfg-ipsec1 . In the example above, X.X.X.X is the publicly routable IP address of the destination IPsec router. Below is a listing of the configurable parameters for an IPsec interface: DST= <address> , where <address> is the IP address of the IPsec destination host or router. This is used for both host-to-host and network-to-network IPsec configurations. DSTNET= <network> , where <network> is the network address of the IPsec destination network. This is only used for network-to-network IPsec configurations. SRC= <address> , where <address> is the IP address of the IPsec source host or router. This setting is optional and is only used for host-to-host IPsec configurations. SRCNET= <network> , where <network> is the network address of the IPsec source network. This is only used for network-to-network IPsec configurations. TYPE= <interface-type> , where <interface-type> is IPSEC . Both applications are part of the ipsec-tools package. Refer to /usr/share/doc/initscripts- <version-number> /sysconfig.txt (replace <version-number> with the version of the initscripts package installed) for configuration parameters if using manual key encryption with IPsec. The racoon IKEv1 key management daemon negotiates and configures a set of parameters for IPSec. It can use preshared keys, RSA signatures, or GSS-API. If racoon is used to automatically manage key encryption, the following options are required: IKE_METHOD= <encryption-method> , where <encryption-method> is either PSK , X509 , or GSSAPI . If PSK is specified, the IKE_PSK parameter must also be set. If X509 is specified, the IKE_CERTFILE parameter must also be set. IKE_PSK= <shared-key> , where <shared-key> is the shared, secret value for the PSK (preshared keys) method. IKE_CERTFILE= <cert-file> , where <cert-file> is a valid X.509 certificate file for the host. IKE_PEER_CERTFILE= <cert-file> , where <cert-file> is a valid X.509 certificate file for the remote host. IKE_DNSSEC= <answer> , where <answer> is yes . The racoon daemon retrieves the remote host's X.509 certificate via DNS. If a IKE_PEER_CERTFILE is specified, do not include this parameter. For more information about the encryption algorithms available for IPsec, refer to the setkey man page. For more information about racoon , refer to the racoon and racoon.conf man pages.

Commands:
TYPE=IPsec ONBOOT=yes IKE_METHOD=PSK SRCNET=192.168.1.0/24 DSTNET=192.168.2.0/24 DST= X.X.X.X
Chapter 2. Eclipse Temurin 17.0.8.1 release notes Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. Review the following release note for an overview of the changes from the Eclipse Temurin 17.0.8.1 patch release. Note For all the other changes and security fixes, see OpenJDK 17.0.8.1 Released . Fixed Invalid CEN header error on valid .zip files OpenJDK 17.0.8 introduced additional validation checks on the ZIP64 fields of .zip files (JDK-8302483). However, these additional checks caused validation failures on some valid .zip files with the following error message: Invalid CEN header (invalid zip64 extra data field size) . To fix this issue, OpenJDK 17.0.8.1 supports zero-length headers and the additional padding that some ZIP64 creation tools produce. From OpenJDK 17.0.8 onward, you can disable these checks by setting the jdk.util.zip.disableZip64ExtraFieldValidation system property to true . See JDK-8313765 (JDK Bug System) Increased default value of jdk.jar.maxSignatureFileSize system property OpenJDK 17.0.8 introduced a jdk.jar.maxSignatureFileSize system property for configuring the maximum number of bytes that are allowed for the signature-related files in a Java archive (JAR) file ( JDK-8300596 ). By default, the jdk.jar.maxSignatureFileSize property was set to 8000000 bytes (8 MB), which was too small for some JAR files. OpenJDK 17.0.8.1 increases the default value of the jdk.jar.maxSignatureFileSize property to 16000000 bytes (16 MB). See JDK-8313216 (JDK Bug System)

Commands:
8.117. mobile-broadband-provider-info 8.117.1. RHBA-2013:0974 - mobile-broadband-provider-info bug fix update Updated mobile-broadband-provider-info packages that fix one bug are now available for Red Hat Enterprise Linux 6. The mobile-broadband-provider-info packages contain listings of mobile broadband (3G) providers, associated network, and plan information. Bug Fix BZ# 844288 Previously, in the serviceproviders.xml file located in the /usr/share/mobile-broadband-provider-info/ directory, "internet.saunalahti" was incorrectly specified as an APN (Access Point Name) value for the Sonera provider. This prevented the Sonera mobile broadband configuration from working. The stanza containing "internet.saunalahti" as an APN value for Sonera has been removed from the XML file, and the Sonera mobile broadband configuration now works as expected. Users of mobile-broadband-provider-info are advised to upgrade to these updated packages, which fix this bug.

Commands:
E.3.11. /proc/tty/ This directory contains information about the available and currently used tty devices on the system. Originally called teletype devices , any character-based data terminals are called tty devices. In Linux, there are three different kinds of tty devices. Serial devices are used with serial connections, such as over a modem or using a serial cable. Virtual terminals create the common console connection, such as the virtual consoles available when pressing Alt + <F-key> at the system console. Pseudo terminals create a two-way communication that is used by some higher level applications, such as XFree86. The drivers file is a list of the current tty devices in use, as in the following example: The /proc/tty/driver/serial file lists the usage statistics and status of each of the serial tty lines. In order for tty devices to be used as network devices, the Linux kernel enforces line discipline on the device. This allows the driver to place a specific type of header with every block of data transmitted over the device, making it possible for the remote end of the connection to treat a block of data as just one in a stream of data blocks. SLIP and PPP are common line disciplines, and each are commonly used to connect systems to one another over a serial link.

Commands:
serial /dev/cua 5 64-127 serial:callout serial /dev/ttyS 4 64-127 serial pty_slave /dev/pts 136 0-255 pty:slave pty_master /dev/ptm 128 0-255 pty:master pty_slave /dev/ttyp 3 0-255 pty:slave pty_master /dev/pty 2 0-255 pty:master /dev/vc/0 /dev/vc/0 4 0 system:vtmaster /dev/ptmx /dev/ptmx 5 2 system /dev/console /dev/console 5 1 system:console /dev/tty /dev/tty 5 0 system:/dev/tty unknown /dev/vc/%d 4 1-63 console
Chapter 1. Introduction Migration Toolkit for Runtimes product will be End of Life on September 30th, 2024 All customers using this product should start their transition to Migration Toolkit for Applications . Migration Toolkit for Applications is fully backwards compatible with all features and rulesets available in Migration Toolkit for Runtimes and will be maintained in the long term. Migration Toolkit for Runtimes (MTR) provides an extensible and customizable rule-based tool that simplifies the migration and modernization of Java applications, such as migrating JBoss Enterprise Application Platform (EAP) 7 to 8 or migrating from any other application server towards EAP at scale. MTR provides the same migration solution as provided in the Migration Toolkit for Applications 5 releases. These release notes cover all Z-stream releases of MTR 1.2 with the most recent release listed first.

Commands:
Chapter 92. LRA Since Camel 2.21 The LRA module provides bindings of the Saga EIP with any MicroProfile compatible LRA Coordinator . 92.1. Dependencies When using lra with Red Hat build of Camel Spring Boot make sure to use the following Maven dependency to have support for auto configuration: <dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-lra-starter</artifactId> </dependency> 92.2. Spring Boot Auto-Configuration The component supports 5 options, which are listed below. Name Description Default Type camel.lra.coordinator-context-path The context path of the LRA coordinator service. String camel.lra.coordinator-url The base URL of the LRA coordinator service (e.g. ). String camel.lra.enabled Global option to enable/disable component auto-configuration, default is true. true Boolean camel.lra.local-participant-context-path The context path of the local participant callback services. String camel.lra.local-participant-url The local URL where the coordinator should send callbacks to (e.g. ). String

Commands:
<dependency> <groupId>org.apache.camel.springboot</groupId> <artifactId>camel-lra-starter</artifactId> </dependency>
2.15. RHEA-2011:0777 - new package: libcxgb4 New libcxgb4 packages are available for Red Hat Enterprise Linux 6. libcxgb4 provides a userspace hardware driver for use with the libibverbs InfiniBand/iWARP verbs library. This driver enables Chelsio Internet Wide Area RDMA Protocol (iWARP) capable ethernet devices. This enhancement update adds the libcxgb4 package to Red Hat Enterprise Linux 6. (BZ# 675024 ) All users of Chelsio iWARP capable ethernet devices are advised to install these new packages.

Commands:
14.5.5. Displaying Device Block Statistics This command will display the block statistics for a running domain. You need to have both the domain name and the device name (use the virsh domblklist to list the devices.)In this case a block device is the unique target name (<target dev='name'/>) or a source file (< source file ='name'/>). Note that not every hypervisor can display every field. To make sure that the output is presented in its most legible form use the --human option, as shown:

Commands:
virsh domblklist rhel6 Target Source ------------------------------------------------ vda /VirtualMachines/rhel6.img hdc - virsh domblkstat --human rhel6 vda Device: vda number of read operations: 174670 number of bytes read: 3219440128 number of write operations: 23897 number of bytes written: 164849664 number of flush operations: 11577 total duration of reads (ns): 1005410244506 total duration of writes (ns): 1085306686457 total duration of flushes (ns): 340645193294
4.3. SQL Translation Extension The JDBCExcecutionFactory provides several methods to modify the command and the string form of the resulting syntax before it is sent to the JDBC driver, including: Change basic SQL syntax options. See the useXXX methods, e.g. useSelectLimit returns true for SQLServer to indicate that limits are applied in the SELECT clause. Register one or more FunctionModifiers that define how a scalar function is to be modified or transformed. Modify a LanguageObject (see the translate , translateXXX , and FunctionModifier.translate methods). Modify the passed in object and return null to indicate that the standard syntax output will be used. Change the way SQL strings are formed for a LanguageObject (see the translate , translateXXX , and FunctionModifier.translate methods). This returns a list of parts which can contain strings and LanguageObjects. These are appended to the SQL string in order. If the incoming LanguageObject appears in the returned list it is not translated again.

Commands:
Chapter 1. Overview The Ansible Automation Platform (AAP) 2.3 on Red Hat OpenShift reference architecture provides an opinionated setup of deploying an Ansible Automation Platform environment. It provides a step-by-step deployment procedure with the latest best practices to install and configure Ansible Automation Platform 2.3. It is best suited for system and platform administrators looking to deploy Ansible Automation Platform on Red Hat OpenShift. By utilizing the power of Red Hat OpenShift, we can streamline the deployment of Ansible Automation Platform and significantly reduce the time and effort required to set it up. Figure 1.1. automation controller architecture The Figure 1.1, "automation controller architecture" , shows the deployment process flow of the Ansible Automation Platform (AAP) operator deploying the automation controller component. The automation controller operator, one of the three operators that comprise the larger Ansible Automation Platform operator, is responsible for deploying the various pods including the controller, postgres and automation job pods. Figure 1.2. automation hub architecture Similarly, the Figure 1.2, "automation hub architecture" shows the AAP operator deploying the automation hub component. The automation hub operator deploys various pods that communicate with each other to deliver automation hub to share internally generated content, Red Hat Ansible Certified Content, execution environments, and Ansible Validated Content with your teams. In addition, this reference architecture highlights key steps involved in providing an efficient and scalable environment delivered by a solid foundation for any of your automation efforts.

Commands:
8.141. mobile-broadband-provider-info 8.141.1. RHBA-2014:0749 - mobile-broadband-provider-info bug fix update An updated mobile-broadband-provider-info package that fixes one bug is now available for Red Hat Enterprise Linux 6. The mobile-broadband-provider-info package contains a database of service provider specific settings of mobile broadband (3G) providers in various countries. Bug Fix BZ# 996599 Previously, the access point name (APN) string incorrectly contained a space at the end. As a consequence, a connection to the Israel Pelephone 3G provider could not be established. This update fixes the typographical error in the APN string, and the connection can now be established as expected. Users of mobile-broadband-provider-info are advised to upgrade to this updated package, which fixes this bug.

Commands:
B.76. python-dmidecode B.76.1. RHBA-2011:1157 - python-dmidecode bug fix update An updated python-dmidecode package that fixes a bug is now available for Red Hat Enterprise Linux 6 Extended Update Support. The python-dmidecode package provides a Python extension module that uses the code-base of the dmidecode utility and presents the data as Python data structures or as XML data using the libxml2 library. Bug Fix BZ# 726613 Previously, certain DMI (Direct Media Interface) tables did not report CPU information as a string and returned the NULL value instead. Consequently, Python terminated unexpectedly with a segmentation fault when trying to identify the CPU type by performing a string comparison. With this update, additional checks for NULL values, performed prior the string comparison, have been added to the code, thus fixing this bug. All users of python-dmidecode are advised to upgrade to this updated package, which fixes this bug.

Commands:
12.6. Geo-replication Logs The following log files are used for a geo-replication session: Master-log-file - log file for the process that monitors the master volume. Slave-log-file - log file for process that initiates changes on a slave. Master-gluster-log-file - log file for the maintenance mount point that the geo-replication module uses to monitor the master volume. Slave-gluster-log-file - If the slave is a Red Hat Gluster Storage Volume, this log file is the slave's counterpart of Master-gluster-log-file . 12.6.1. Viewing the Geo-replication Master Log Files To view the Master-log-file for geo-replication, use the following command: For example: 12.6.2. Viewing the Geo-replication Slave Log Files To view the log file for geo-replication on a slave, use the following procedure. glusterd must be running on slave machine. On the master, run the following command to display the session-owner details: For example: On the slave, run the following command with the session-owner value from the step: For example:

Commands:
gluster volume geo-replication MASTER_VOL SLAVE_HOST :: SLAVE_VOL config log-file
gluster volume geo-replication Volume1 example.com::slave-vol config log-file
gluster volume geo-replication MASTER_VOL SLAVE_HOST :: SLAVE_VOL config session-owner
gluster volume geo-replication Volume1 example.com::slave-vol config session-owner 5f6e5200-756f-11e0-a1f0-0800200c9a66
gluster volume geo-replication SLAVE_VOL config log-file /var/log/gluster/ SESSION_OWNER :remote-mirror.log
gluster volume geo-replication slave-vol config log-file /var/log/gluster/5f6e5200-756f-11e0-a1f0-0800200c9a66:remote-mirror.log
9.7.4. Hostname Formats The host(s) can be in the following forms: Single machine A fully-qualified domain name (that can be resolved by the server), hostname (that can be resolved by the server), or an IP address. Series of machines specified with wildcards Use the * or ? character to specify a string match. Wildcards are not to be used with IP addresses; however, they may accidentally work if reverse DNS lookups fail. When specifying wildcards in fully qualified domain names, dots ( . ) are not included in the wildcard. For example, *.example.com includes one.example.com but does not include one.two.example.com . IP networks Use a.b.c.d/ z , where a.b.c.d is the network and z is the number of bits in the netmask (for example 192.168.0.0/24). Another acceptable format is a.b.c.d/ netmask , where a.b.c.d is the network and netmask is the netmask (for example, 192.168.100.8/255.255.255.0). Netgroups Use the format @ group-name , where group-name is the NIS netgroup name.

Commands:
Appendix A. Using your subscription Apicurio Registry is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing your account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading ZIP and TAR files To access ZIP or TAR files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat Integration entries in the Integration and Automation category. Select the desired Apicurio Registry product. The Software Downloads page opens. Click the Download link for your component. Revised on 2025-02-11 14:03:23 UTC

Commands:
Chapter 72. KafkaClientAuthenticationScramSha256 schema reference Used in: KafkaBridgeSpec , KafkaConnectSpec , KafkaMirrorMaker2ClusterSpec , KafkaMirrorMakerConsumerSpec , KafkaMirrorMakerProducerSpec Full list of KafkaClientAuthenticationScramSha256 schema properties To configure SASL-based SCRAM-SHA-256 authentication, set the type property to scram-sha-256 . The SCRAM-SHA-256 authentication mechanism requires a username and password. 72.1. username Specify the username in the username property. 72.2. passwordSecret In the passwordSecret property, specify a link to a Secret containing the password. You can use the secrets created by the User Operator. If required, you can create a text file that contains the password, in cleartext, to use for authentication: echo -n PASSWORD > MY-PASSWORD .txt You can then create a Secret from the text file, setting your own field name (key) for the password: oc create secret generic MY-CONNECT-SECRET-NAME --from-file= MY-PASSWORD-FIELD-NAME =./ MY-PASSWORD .txt Example Secret for SCRAM-SHA-256 client authentication for Kafka Connect apiVersion: v1 kind: Secret metadata: name: my-connect-secret-name type: Opaque data: my-connect-password-field: LFTIyFRFlMmU2N2Tm The secretName property contains the name of the Secret , and the password property contains the name of the key under which the password is stored inside the Secret . Important Do not specify the actual password in the password property. Example SASL-based SCRAM-SHA-256 client authentication configuration for Kafka Connect authentication: type: scram-sha-256 username: my-connect-username passwordSecret: secretName: my-connect-secret-name password: my-connect-password-field 72.3. KafkaClientAuthenticationScramSha256 schema properties Property Description passwordSecret Reference to the Secret which holds the password. PasswordSecretSource type Must be scram-sha-256 . string username Username used for the authentication. string

Commands:
echo -n PASSWORD > MY-PASSWORD .txt
create secret generic MY-CONNECT-SECRET-NAME --from-file= MY-PASSWORD-FIELD-NAME =./ MY-PASSWORD .txt
apiVersion: v1 kind: Secret metadata: name: my-connect-secret-name type: Opaque data: my-connect-password-field: LFTIyFRFlMmU2N2Tm
authentication: type: scram-sha-256 username: my-connect-username passwordSecret: secretName: my-connect-secret-name password: my-connect-password-field