mtpti5iD/redhat-docs_dataset huggingface dataset:
Migrating Apache Camel Red Hat build of Apache Camel 4.8 Migrating Apache Camel Red Hat build of Apache Camel Documentation Team fuse-docs-support@redhat.com Red Hat build of Apache Camel Support Team https://access.redhat.com/support

Commands:
<circuitBreaker> <resilience4jConfiguration> <timeoutEnabled>true</timeoutEnabled> <timeoutDuration>2000</timeoutDuration> </resilience4jConfiguration> </circuitBreaker>
<circuitBreaker> <resilience4jConfiguration timeoutEnabled="true" timeoutDuration="2000"/> </circuitBreaker>
<route id="myRoute" description="Something that this route do"> <from uri="kafka:cheese"/> </route>
camel.health.producers-enabled = true
- route: from: uri: "direct:info" steps: - log: "message"
"bean:myBean?method=foo(com.foo.MyOrder.class, true)"
"bean:myBean?method=bar(String.class, int.class)"
from("optaplanner:myProblemName") .to("...")
from("optaplanner:myProblemName?configFile=PATH/TO/CONFIG.FILE.xml") .to("...")
from("platform-http:myservice") .to("...")
<dependency> <groupId>javax.xml.bind</groupId> <artifactId>jaxb-api</artifactId> <version>2.3.1</version> </dependency> <dependency> <groupId>com.sun.xml.bind</groupId> <artifactId>jaxb-core</artifactId> <version>2.3.0.1</version> </dependency> <dependency> <groupId>com.sun.xml.bind</groupId> <artifactId>jaxb-impl</artifactId> <version>2.3.2</version> </dependency>
telegram:bots/myTokenHere
telegram:bots?authorizationToken=myTokenHere
ManagedCamelContext managed = camelContext.getExtension(ManagedCamelContext.class);
Installing Red Hat Virtualization as a standalone Manager with remote databases Red Hat Virtualization 4.3 ALTERNATIVE method - Installing the Red Hat Virtualization Manager on one server, and its databases on a second server Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to install a standalone Manager environment - where the Red Hat Virtualization Manager is installed on either a physical server or a virtual machine hosted in another environment - with the Manager database and the Data Warehouse service and database hosted on a remote server. Although you can choose to host one database locally and the other remotely, this document assumes that both databases will be hosted remotely. If this is not the configuration you want to use, see the other Installation Options in the Product Guide .

Commands:
1.2. Apache Subversion (SVN) Apache Subversion , commonly abbreviated as SVN , is a centralized version control system with a client-server architecture. It is a successor to the older Concurrent Versions System (CVS), preserves the same development model, and addresses problems often encountered with CVS. 1.2.1. Installing and Configuring Subversion Installing the subversion Package In Red Hat Enterprise Linux 6, Subversion is provided by the subversion package. To install the subversion package and all its dependencies on your system, type the following at a shell prompt as root : yum install subversion This installs a command line Subversion client, a Subversion server, and other related tools to the system. Setting Up the Default Editor When using Subversion on the command line, certain commands such as svn import or svn commit require the user to write a short log message. To determine which text editor to start, the svn client application first reads the contents of the environment variable USDSVN_EDITOR , then reads more general environment variables USDVISUAL and USDEDITOR , and if none of these is set, it reports an error. To persistently change the value of the USDSVN_EDITOR environment variable, run the following command: echo " export SVN_EDITOR= command " >> ~/.bashrc This adds the export SVN_EDITOR= command line to your ~/.bashrc file. Replace command with a command that runs the editor of your choice (for example, emacs ). Note that for this change to take effect in the current shell session, you must execute the commands in ~/.bashrc by typing the following at a shell prompt: . ~/.bashrc Example 1.3. Setting up the default text editor To configure the Subversion client to use Emacs as a text editor, type:

Commands:
~]USD echo "export SVN_EDITOR=emacs" >> ~/.bashrc ~]USD . ~/.bashrc
5.3. Device Assignment and SR-IOV The following diagram demonstrates the involvement of the kernel in the Device Assignment and SR-IOV architectures. Figure 5.2. Device assignment and SR-IOV Device assignment presents the entire device to the guest. SR-IOV needs support in drivers and hardware, including the NIC and the system board and allows multiple virtual devices to be created and passed into different guests. A vendor-specific driver is required in the guest, however, SR-IOV offers the lowest latency of any network option.

Commands:
Chapter 3. Configuring GitLab Webhooks for automated pipeline triggers Learn how to set up webhooks and secrets in GitLab to automatically trigger pipeline run in RHDH upon code updates. Prerequisites You have an existing GitLab project. You have administrator privileges on OpenShift web console. Procedure Retrieve Webhook URL and Secret Token: Log in to the OpenShift web console with Administrator privileges. Navigate to the rhtap project, expand Pipelines , and then select PipelineRuns . Locate the rhtap-pe-info-<> pipeline run, and then select the Logs tab. Note These logs contain the webhook URL and secret token required for GitLab configuration. Configure Webhook in GitLab: Within your GitLab repository, navigate to Settings > Webhooks . In the URL field, enter the webhook URL copied from Step 1. In the Secret Token field, enter the secret token copied from Step 1. In the Trigger section: Select Push events . Select Merge request events . Click Add Webhook . Verification Push your code changes to the GitLab repository. Navigate to the CI tab in RHDH. Verify that a pipeline run is triggered for your code push. Revised on 2024-07-15 21:00:30 UTC

Commands:
8.111. man-pages-ja 8.111.1. RHBA-2013:1094 - man-pages-ja bug fix update An updated man-pages-ja package that fixes two bugs is now available for Red Hat Enteprise Linux 6. The man-pages-ja package contains manual pages in Japanese. Bug Fixes BZ#949787 The shmat(2) man page in the release did not mention the EIDRM error code, which could have been returned by the shmat utility. With this update, the EIDRM error code is included in shmat. BZ#957937 The strtoul(3) man page in the release incorrectly mentioned the range of the return value. This update fixes the aforementioned problem. Users of man-pages-ja are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 7. Pulling images from a container repository Pull automation execution environments from the automation hub remote registry to make a copy to your local machine. Automation hub provides the podman pull command for each latest automation execution environments in the container repository. You can copy and paste this command into your terminal, or use podman pull to copy an automation execution environments based on an automation execution environments tag. 7.1. Pulling an image You can pull automation execution environments from the automation hub remote registry to make a copy to your local machine. Prerequisites You must have permission to view and pull from a private container repository. Procedure If you are pulling automation execution environments from a password or token-protected registry, create a credential before pulling the automation execution environments. From the navigation panel, select Automation Content Execution Environments . Select your automation execution environments. In the Pull this image entry, click Copy to clipboard . Paste and run the command in your terminal. Verification Run podman images to view images on your local machine. 7.2. Syncing images from a container repository You can pull automation execution environments from the automation hub remote registry to sync an image to your local machine. To sync an automation execution environment from a remote registry, you must first configure a remote registry. Prerequisites You must have permission to view and pull from a private container repository. Procedure From the navigation panel, select Automation Content Execution Environments . Add https://registry.redhat.io to the registry. Add any required credentials to authenticate. Note Some remote registries are aggressive with rate limiting. Set a rate limit under Advanced Options . From the navigation panel, select Automation Content Execution Environments . Click Create execution environment in the page header. Select the registry you want to pull from. The Name field displays the name of the automation execution environments displayed on your local registry. Note The Upstream name field is the name of the image on the remote server. For example, if the upstream name is set to "alpine" and the Name field is "local/alpine", the alpine image is downloaded from the remote and renamed to "local/alpine". Set a list of tags to include or exclude. Syncing automation execution environments with a large number of tags is time consuming and uses a lot of disk space. Additional resources See Red Hat Container Registry Authentication for a list of registries. See the What is Podman? documentation for options to use when pulling images.

Commands:
2.2. Logical Volumes Volume management creates a layer of abstraction over physical storage, allowing you to create logical storage volumes. This provides much greater flexibility in a number of ways than using physical storage directly. With a logical volume, you are not restricted to physical disk sizes. In addition, the hardware storage configuration is hidden from the software so it can be resized and moved without stopping applications or unmounting file systems. This can reduce operational costs. Logical volumes provide the following advantages over using physical storage directly: Flexible capacity When using logical volumes, file systems can extend across multiple disks, since you can aggregate disks and partitions into a single logical volume. Resizeable storage pools You can extend logical volumes or reduce logical volumes in size with simple software commands, without reformatting and repartitioning the underlying disk devices. Online data relocation To deploy newer, faster, or more resilient storage subsystems, you can move data while your system is active. Data can be rearranged on disks while the disks are in use. For example, you can empty a hot-swappable disk before removing it. Convenient device naming Logical storage volumes can be managed in user-defined groups, which you can name according to your convenience. Disk striping You can create a logical volume that stripes data across two or more disks. This can dramatically increase throughput. Mirroring volumes Logical volumes provide a convenient way to configure a mirror for your data. Volume Snapshots Using logical volumes, you can take device snapshots for consistent backups or to test the effect of changes without affecting the real data. The implementation of these features in LVM is described in the remainder of this document.

Commands:
4.4.10. Shrinking Logical Volumes To reduce the size of a logical volume, first unmount the file system. You can then use the lvreduce command to shrink the volume. After shrinking the volume, remount the file system. Warning It is important to reduce the size of the file system or whatever is residing in the volume before shrinking the volume itself, otherwise you risk losing data. Shrinking a logical volume frees some of the volume group to be allocated to other logical volumes in the volume group. The following example reduces the size of logical volume lvol1 in volume group vg00 by 3 logical extents.

Commands:
lvreduce -l -3 vg00/lvol1
3.2. Growing a File System on a Logical Volume To grow a file system on a logical volume, perform the following steps: Determine whether there is sufficient unallocated space in the existing volume group to extend the logical volume. If not, perform the following procedure: Create a new physical volume with the pvcreate command. Use the vgextend command to extend the volume group that contains the logical volume with the file system you are growing to include the new physical volume. Once the volume group is large enough to include the larger file system, extend the logical volume with the lvresize command. Resize the file system on the logical volume. Note that you can use the -r option of the lvresize command to extend the logical volume and resize the underlying file system with a single command

Commands:
13.5. The /etc/openldap/schema/ Directory The /etc/openldap/schema/ directory holds LDAP definitions, previously located in the slapd.at.conf and slapd.oc.conf files. The /etc/openldap/schema/redhat/ directory holds customized schemas distributed by Red Hat for Red Hat Enterprise Linux. All attribute syntax definitions and objectclass definitions are now located in the different schema files. The various schema files are referenced in /etc/openldap/slapd.conf using include lines, as shown in this example: Warning Do not modify schema items defined in the schema files installed by OpenLDAP. It is possible to extend the schema used by OpenLDAP to support additional attribute types and object classes using the default schema files as a guide. To do this, create a local.schema file in the /etc/openldap/schema/ directory. Reference this new schema within slapd.conf by adding the following line below the default include schema lines: , define new attribute types and object classes within the local.schema file. Many organizations use existing attribute types from the schema files installed by default and add new object classes to the local.schema file. Extending the schema to match certain specialized requirements is quite involved and beyond the scope of this chapter. Refer to http://www.openldap.org/doc/admin/schema.html for information.

Commands:
include /etc/openldap/schema/core.schema include /etc/openldap/schema/cosine.schema include /etc/openldap/schema/inetorgperson.schema include /etc/openldap/schema/nis.schema include /etc/openldap/schema/rfc822-MailMember.schema include /etc/openldap/schema/redhat/autofs.schema
include /etc/openldap/schema/local.schema
Appendix A. Revision History Revision History Revision 7-7 Mon Aug 5 2019 Vladimir Slavik Release for Red Hat Enterprise Linux 7.7 GA. Revision 7-6 Tue Oct 30 2018 Vladimir Slavik Release for Red Hat Enterprise Linux 7.6 GA. Revision 7-5.1 Mon Jun 18 2018 Radek Biba Use an id for the stap test screen. Revision 7-5 Tue Jan 09 2018 Vladimir Slavik Release for Red Hat Enterprise Linux 7.5 Beta. Revision 7-4 Wed Jul 26 2017 Vladimir Slavik Release for Red Hat Enterprise Linux 7.4. Revision 7-3.9 Tue May 16 2017 Robert Kratky Build for 7.4 Beta release. Revision 1-8 Wed Oct 19 2016 Robert Kratky Release for Red Hat Enterprise Linux 7.3. Revision 1-6 Wed Jan 20 2016 Robert Kratky Async release with many fixes. Revision 1-5 Thu Nov 11 2015 Robert Kratky Release for Red Hat Enterprise Linux 7.2. Revision 0-3 Fri Dec 6 2013 Jacquelynn East Release for Red Hat Enterprise Linux 7.0.

Commands:
Chapter 4. Advisories related to this release The following advisories are issued to document bug fixes and CVE fixes included in this release: RHBA-2025:0416 RHBA-2025:0417 RHBA-2025:0418 RHBA-2025:0419 RHBA-2025:0420 Revised on 2025-01-30 11:27:05 UTC

Commands:
8.46. fprintd 8.46.1. RHBA-2013:1738 - fprintd bug fix update Updated fprintd packages that fix one bug are now available for Red Hat Enterprise Linux 6. The fprintd packages contain a D-Bus service to access fingerprint readers. Bug Fix BZ# 1003940 When the Pluggable Authentication Module (PAM) configuration includes the pam_fprintd module, PAM uses the glib2 functions where the dlclose() function is executed to unload the glib2 libraries. However, this method is not designed for multi-threaded applications. When a PAM operation was made, Directory Server on Red Hat Enterprise Linux 6 terminated unexpectedly during the shutdown phase because it attempted to unload the glib2 destructor, which had been previously unloaded by the fprintd service. This update applies a patch to fix this bug so that fprintd no longer unloads glib2 when pam_fprintd closes. As a result, the glib2 libraries are unloaded when Directory Server is closed and therefore the server shuts down gracefully. Users of fprintd are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 38. Adding/Removing a Logical Unit Through rescan-scsi-bus.sh The sg3_utils package provides the rescan-scsi-bus.sh script, which can automatically update the logical unit configuration of the host as needed (after a device has been added to the system). The rescan-scsi-bus.sh script can also perform an issue_lip on supported devices. For more information about how to use this script, refer to rescan-scsi-bus.sh --help . To install the sg3_utils package, run yum install sg3_utils . Known Issues With rescan-scsi-bus.sh When using the rescan-scsi-bus.sh script, take note of the following known issues: In order for rescan-scsi-bus.sh to work properly, LUN0 must be the first mapped logical unit. The rescan-scsi-bus.sh can only detect the first mapped logical unit if it is LUN0 . The rescan-scsi-bus.sh will not be able to scan any other logical unit unless it detects the first mapped logical unit even if you use the --nooptscan option. A race condition requires that rescan-scsi-bus.sh be run twice if logical units are mapped for the first time. During the first scan, rescan-scsi-bus.sh only adds LUN0 ; all other logical units are added in the second scan. A bug in the rescan-scsi-bus.sh script incorrectly executes the functionality for recognizing a change in logical unit size when the --remove option is used. The rescan-scsi-bus.sh script does not recognize ISCSI logical unit removals.

Commands:
Chapter 3. Uninstalling OpenShift Serverless Knative Serving Before you can remove the OpenShift Serverless Operator, you must remove Knative Serving. To uninstall Knative Serving, you must remove the KnativeServing custom resource (CR) and delete the knative-serving namespace. 3.1. Uninstalling Knative Serving Prerequisites You have cluster administrator permissions on OpenShift Container Platform, or you have cluster or dedicated administrator permissions on OpenShift Dedicated. Install the OpenShift CLI ( oc ). Procedure Delete the KnativeServing CR: USD oc delete knativeservings.operator.knative.dev knative-serving -n knative-serving After the command has completed and all pods have been removed from the knative-serving namespace, delete the namespace: USD oc delete namespace knative-serving

Commands:
oc delete knativeservings.operator.knative.dev knative-serving -n knative-serving
oc delete namespace knative-serving
12.4. Storing Certificates in NSS Databases By default, certmonger uses .pem files to store the key and the certificate. To store the key and the certificate in an NSS database, specify the -d and -n with the command you use for requesting the certificate. -d sets the security database location -n gives the certificate nickname which is used for the certificate in the NSS database Note The -d and -n options are used instead of the -f and -k options that give the .pem file. For example: Requesting a certificate using ipa-getcert and local-getcert allows you to specify another two options: -F gives the file where the certificate of the CA is to be stored. -a gives the location of the NSS database where the certificate of the CA is to be stored. Note If you request a certificate using selfsign-getcert , there is no need to specify the -F and -a options because generating a self-signed certificate does not involve any CA. Supplying the -F option, the -a option, or both with local-getcert allows you to obtain a copy of the CA certificate that is required in order to verify a certificate issued by the local signer. For example:

Commands:
selfsign-getcert request -d /export/alias -n ServerCert
local-getcert request -F /etc/httpd/conf/ssl.crt/ca.crt -n ServerCert -f /etc/httpd/conf/ssl.crt/server.crt -k /etc/httpd/conf/ssl.key/server.key
3.2. Boot Loader Installation media for IBM Power Systems now use the GRUB2 boot loader instead of the previously offered yaboot . For the big endian variant of Red Hat Enterprise Linux for POWER, GRUB2 is preferred but yaboot can also be used. The newly introduced little endian variant requires GRUB2 to boot. The Installation Guide has been updated with instructions for setting up a network boot server for IBM Power Systems using GRUB2 .

Commands:
Chapter 4. Advisories related to this release The following advisories are issued to document bug fixes and CVE fixes included in this release: RHSA-2024:0240 RHSA-2024:0241 RHSA-2024:0242 RHSA-2024:0244 RHSA-2024:0246 RHSA-2024:0267 Revised on 2024-05-03 15:36:05 UTC

Commands:
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes that the latest OpenJDK 21 release of Eclipse Temurin includes, see OpenJDK 21.0.6 Released . New features and enhancements Eclipse Temurin 21.0.6 includes the following new features and enhancements. Option for jar command to avoid overwriting files when extracting an archive In earlier OpenJDK releases, when the jar tool extracted files from an archive, the jar tool overwrote any existing files with the same name in the target directory. OpenJDK 21.0.6 adds a new ‐k (or ‐‐keep-old-files ) option that you can use to ensure that the jar tool does not overwrite existing files. You can specify this new option in either short or long format. For example: jar xkf myfile.jar jar --extract ‐‐keep-old-files ‐‐file myfile.jar Note In OpenJDK 21.0.6, the jar tool retains the old behavior by default. If you do not explicitly specify the ‐k (or ‐‐keep-old-files ) option, the jar tool automatically overwrites any existing files with the same name. See JDK-8335912 (JDK Bug System) and JDK bug system reference ID: JDK-8337499. IANA time zone database updated to version 2024b In OpenJDK 21.0.6, the in-tree copy of the Internet Assigned Numbers Authority (IANA) time zone database is updated to version 2024b. This update is primarily concerned with improving historical data for Mexico, Mongolia, and Portugal. This update to the IANA database also includes the following changes: Asia/Choibalsan is an alias for Asia/Ulaanbaatar . The Middle European Time (MET) time zone is equal to Central European Time (CET). Some legacy time-zone IDs are mapped to geographical names rather than fixed offsets: Eastern Standard Time (EST) is mapped to America/Panama rather than -5:00 . Mountain Standard Time (MST) is mapped to America/Phoenix rather than -7:00 . Hawaii Standard Time (HST) is mapped to Pacific/Honolulu rather than -10:00 . OpenJDK overrides the change in the legacy time-zone ID mappings by retaining the existing fixed-offset mapping. See JDK-8339637 (JDK Bug System) . Revised on 2025-01-30 11:12:40 UTC

Commands:
Appendix A. Revision History Revision History Revision 0.0-28 Mon Oct 30 2017 Lenka Spackova Added information on changes in the ld linker behavior to Deprecated Functionality. Revision 0.0-27 Tue Feb 14 2017 Lenka Spackova Updated the Samba 4.1.0 description (Authentication and Interoperability). Revision 0.0-25 Mon Aug 08 2016 Lenka Spackova Added a note about limited support for Windows guest virtual machines to Deprecated Functionality. Revision 0.0-23 Fri Mar 13 2015 Milan Navratil Update of the Red Hat Enterprise Linux 7.0 Release Notes. Revision 0.0-21 Wed Jan 06 2015 Jiri Herrmann Update of the Red Hat Enterprise Linux 7.0 Release Notes. Revision 0.0-1 Thu Dec 11 2013 Eliska Slobodova Release of the Red Hat Enterprise Linux 7.0 Beta Release Notes.

Commands: