mtpti5iD/redhat-docs_dataset huggingface dataset:
6.5. Offline mode 6.5.1. Using a Custom Offline Repository When you move from the development phase of a project to the deployment phase, it is typically more convenient to pre-install all of the artifacts required by your application, rather than downloading them from the Internet on demand. In this case, the ideal solution is to create a custom offline repository, which contains the artifacts needed for your deployment. Creating a custom offline repository by hand, however, would be difficult, because it would need to include all of the transitive dependencies associated with your application bundles and features. The ideal way to create a custom offline repository is to generate it, with the help of the Apache Karaf features-maven-plugin plug-in. If you have a Maven project and you need to create an offline repository for building this project and its runtime dependencies, you can use the maven dependency plugin . For example, from the top-level directory of a Maven project (such that the current directory has a pom.xml file), you should be able to run the following Maven command: This downloads all the Maven dependencies and plug-ins required to build the project to the /tmp/cheese directory. To generate the custom offline repository, open a new command prompt, change directory to ProjectDir /custom-repo , and enter the following Maven command: Assuming that the Maven build completes successfully, the custom offline repository should now be available in the following location:

Commands:
mvn org.apache.maven.plugins:maven-dependency-plugin:2.8:go-offline -Dmaven.repo.local=/tmp/cheese
mvn generate-resources
ProjectDir /custom-repo/target/features-repo
Chapter 36. Verifying the KIE Server installation Verify that KIE Server is installed correctly. Prerequisites KIE Server is installed and configured. Procedure To start KIE Server, enter one of the following commands in the JWS_HOME /tomcat/bin directory: On Linux or UNIX-based systems: USD ./startup.sh On Windows: startup.bat After a few minutes, review the files in the JWS_HOME /tomcat/logs directory and correct any errors. To verify that KIE Server is working correctly, enter http://localhost:8080/kie-server/services/rest/server in a web browser. Enter the user name and password stored in the tomcat-users.xml file.

Commands:
./startup.sh
startup.bat
Chapter 6. Configuring Applications for Single Sign-On After a smart card is enrolled, the smart card can be used for SSL client authentication and S/MIME email applications. The PKCS #11 module used by these applications, by default, is located in /usr/lib/libcoolkeypk11.so . 6.1. Configuring Firefox to Use Kerberos for Single Sign-On Firefox can use Kerberos for single sign-on to intranet sites and other protected websites. For Firefox to use Kerberos, it first has to be configured to send Kerberos credentials to the appropriate KDC. In the address bar of Firefox, type about:config to display the list of current configuration options. In the Filter field, type negotiate to restrict the list of options. Double-click the network.negotiate-auth.trusted-uris entry. Enter the name of the domain against which to authenticate. , configure the network.negotiate-auth.delegation-uris entry, using the same domain as for network.negotiate-auth.trusted-uris . Note Even after Firefox is configured to pass Kerberos credentials, it still requires a valid Kerberos ticket to use. To generate a Kerberos ticket, use the kinit command and supply the user password for the user on the KDC. If Kerberos authentication is not working, turn on verbose logging for the authentication process. Close all instances of Firefox. In a command prompt, export values for the NSPR_LOG_* variables: Restart Firefox from that shell , and visit the website where Kerberos authentication is failing. Check the /tmp/moz.log file for error messages with nsNegotiateAuth in the message. There are several common errors that occur with Kerberos authentication. The first error says that no credentials have been found. This means that there are no Kerberos tickets (meaning that they expired or were not generated). To fix this, run kinit to generate the Kerberos ticket and then open the website again. The second potential error is if the browser is unable to contact the KDC, with the message Server not found in Kerberos database . This is usually a Kerberos configuration problem. The correct entries must be in the [domain_realm] section of the /etc/krb5.conf file to identify the domain. For example: If there are no errors in the log, then the problem could be that an HTTP proxy server is stripping off the HTTP headers required for Kerberos authentication. Try to connect to the site using HTTPS, which allows the request to pass through unmodified.

Commands:
[jsmith@host ~] USD kinit Password for jsmith@EXAMPLE.COM:
export NSPR_LOG_MODULES=negotiateauth:5 export NSPR_LOG_FILE=/tmp/moz.log
-1208550944[90039d0]: entering nsNegotiateAuth::GetNextToken() -1208550944[90039d0]: gss_init_sec_context() failed: Miscellaneous failure No credentials cache found
-1208994096[8d683d8]: entering nsAuthGSSAPI::GetNextToken() -1208994096[8d683d8]: gss_init_sec_context() failed: Miscellaneous failure Server not found in Kerberos database
.example.com = EXAMPLE.COM example.com = EXAMPLE.COM
4.259. qpid-tests 4.259.1. RHBA-2011:1667 - qpid-tests bug fix update An updated qpid-tests package is now available for Red Hat Enterprise Linux 6. The qpid-tests package contains conformance tests for Apache Qpid. The qpid-tests package has been upgraded to upstream version 0.12, which provides a number of bug fixes and enhancements over the version. (BZ# 706991 ) All users of qpid-tests are advised to upgrade to this updated package.

Commands:
Chapter 5. Changing the update approval strategy To ensure that the storage system gets updated automatically when a new update is available in the same channel, we recommend keeping the update approval strategy to Automatic . Changing the update approval strategy to Manual will need manual approval for each upgrade. Procedure Navigate to Operators Installed Operators . Select openshift-storage from the Project drop-down list. Note If the Show default projects option is disabled, use the toggle button to list all the default projects. Click on OpenShift Data Foundation operator name Go to the Subscription tab. Click on the pencil icon for changing the Update approval . Select the update approval strategy and click Save . Verification steps Verify that the Update approval shows the newly selected approval strategy below it.

Commands:
Chapter 1. Overview AMQ Broker is a high-performance messaging implementation based on ActiveMQ Artemis. It uses an asynchronous journal for fast message persistence, and supports multiple languages, protocols, and platforms. 1.1. Key features AMQ Broker provides the following features: Clustering and high availability options Fast, native-IO persistence Supports local transactions Supports XA transactions when using AMQ Core Protocol JMS and AMQ OpenWire JMS clients Written in Java for broad platform support Multiple management interfaces: AMQ Management Console, Management APIs, and JMX 1.2. Supported standards and protocols AMQ Broker supports the following standards and protocols: Wire protocols: Core Protocol AMQP 1.0 MQTT OpenWire (Used by A-MQ 6 clients) STOMP JMS 2.0 Note The details of distributed transactions (XA) within AMQP are not provided in the 1.0 version of the specification. If your environment requires support for distributed transactions, it is recommended that you use the AMQ Core Protocol JMS. 1.3. Supported configurations Refer to the article " Red Hat AMQ 7 Supported Configurations " on the Red Hat Customer Portal for current information regarding AMQ Broker supported configurations. 1.4. Document conventions This document uses the following conventions for the sudo command and file paths. The sudo command In this document, sudo is used for any command that requires root privileges. You should always exercise caution when using sudo , as any changes can affect the entire system. For more information about using sudo , see The sudo Command . About the use of file paths in this document In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example, /home/... ). If you are using Microsoft Windows, you should use the equivalent Microsoft Windows paths (for example, C:\Users\... ).

Commands:
18.4. mount Command References The following resources provide an in-depth documentation on the subject. 18.4.1. Manual Page Documentation man 8 mount - The manual page for the mount command that provides a full documentation on its usage. man 8 umount - The manual page for the umount command that provides a full documentation on its usage. man 8 findmnt - The manual page for the findmnt command that provides a full documentation on its usage. man 5 fstab - The manual page providing a thorough description of the /etc/fstab file format.

Commands:
Chapter 1. Installing and Configuring Data Warehouse 1.1. Overview of Configuring Data Warehouse You can install and configure Data Warehouse on the same machine as the Manager, or on a separate machine with access to the Manager: Install and configure Data Warehouse on the Manager machine This configuration requires only a single registered machine, and is the simplest to configure, but it increases the demand on the Manager machine. Users who require access to the Data Warehouse service require access to the Manager machine itself. See Configuring the Red Hat Virtualization Manager in Installing Red Hat Virtualization as a standalone Manager with local databases . Install and configure Data Warehouse on a separate machine This configuration requires two registered machines. It reduces the load on the Manager machine and avoids potential CPU and memory-sharing conflicts on that machine. Administrators can also allow user access to the Data Warehouse machine, without the need to grant access to the Manager machine. See Section 1.2, "Installing and Configuring Data Warehouse on a Separate Machine" for more information on this configuration. It is recommended that you set the system time zone for all machines in your Data Warehouse deployment to UTC. This ensures that data collection is not interrupted by variations in your local time zone: for example, a change from summer time to winter time. To calculate an estimate of the space and resources the ovirt_engine_history database will use, use the RHV Manager History Database Size Calculator tool. The estimate is based on the number of entities and the length of time you have chosen to retain the history records. Important The following behavior is expected in engine-setup : Install the Data Warehouse package, run engine-setup , and answer No to configuring Data Warehouse: Run engine-setup again; setup no longer presents the option to configure Data Warehouse. To force engine-setup to present the option again, run engine-setup --reconfigure-optional-components . To configure only the currently installed Data Warehouse packages, and prevent setup from applying package updates found in enabled repositories, add the --offline option .

Commands:
Configure Data Warehouse on this host (Yes, No) [Yes]: No
Configuring your Red Hat build of Quarkus applications by using a YAML file Red Hat build of Quarkus 3.8 Red Hat Customer Content Services

Commands:
<dependency> <groupId>io.quarkus</groupId> <artifactId>quarkus-config-yaml</artifactId> </dependency>
./mvnw quarkus:add-extension -Dextensions="quarkus-config-yaml"
Properties that configure the JDBC data source driver of your PostgreSQL data source quarkus: datasource: db-kind: postgresql jdbc: url: jdbc:postgresql://localhost:5432/quarkus_test username: quarkus_test password: quarkus_test Property that configures the URL of the endpoint to which the REST client sends requests quarkus: rest-client: org.acme.rest.client.ExtensionsService: url: https://stage.code.quarkus.io/api Property that configures the log message level for your application For configuration property names that use quotes, do not split the string inside the quotes quarkus: log: category: "io.quarkus.category": level: INFO
"%dev": quarkus: datasource: db-kind: postgresql jdbc: url: jdbc:postgresql://localhost:5432/quarkus_test username: quarkus_test password: quarkus_test
mach: 3 x: factor: 2.23694 display: mach: USD{mach} unit: name: "mph" factor: USD{x.factor}
├── config │ └── application.yaml ├── my-app-runner
quarkus: http: cors: ~: true methods: GET,PUT,POST
./mvnw quarkus:dev
11.3.3.4. User Options User options may be placed on their own lines beneath a server option or on the same line as the server option. In either case, the defined options must follow the user option (defined below). fetchall - Orders Fetchmail to download all messages in the queue, including messages that have already been viewed. By default, Fetchmail only pulls down new messages. fetchlimit <number> - Replace <number> with the number of messages to be retrieved before stopping. flush - Deletes all previously viewed messages in the queue before retrieving new messages. limit <max-number-bytes> - Replace <max-number-bytes> with the maximum size in bytes that messages are allowed to be when retrieved by Fetchmail. This option is useful with slow network links, when a large message takes too long to download. password ' <password> ' - Replace <password> with the user's password. preconnect " <command> " - Replace <command> with a command to be executed before retrieving messages for the user. postconnect " <command> " - Replace <command> with a command to be executed after retrieving messages for the user. ssl - Activates SSL encryption. user " <username> " - Replace <username> with the username used by Fetchmail to retrieve messages. This option must precede all other user options.

Commands:
2.19. RHEA-2011:0625 - new package: netxen-firmware A new netxen-firmware package is now available. netxen_nic is a kernel driver module for the QLogic netxen P3 devices. It works with the netxen_nic driver in the latest Red Hat Enterprise Linux kernels to enable support for QLogic Intelligent Ethernet (3000 and 3100 Series) netxen P3 adapters. This new netxen-firmware package provides the firmware required by netxen_nic to enable QLogic Linux Intelligent Ethernet (3000 and 3100 Series) Adapter. (BZ# 562940 ) All users of the netxen_nic driver should install this new package, which provides this enhancement.

Commands:
10.3. Trouble During the Installation 10.3.1. The " No devices found to install Red Hat Enterprise Linux " Error Message If you receive an error message stating No devices found to install Red Hat Enterprise Linux , there is probably a SCSI controller that is not being recognized by the installation program. Check your hardware vendor's website to determine if a driver update is available that fixes your problem. For more general information on driver updates, refer to Chapter 6, Updating Drivers During Installation on Intel and AMD Systems . You can also refer to the Red Hat Hardware Compatibility List , available online at: https://hardware.redhat.com/

Commands:
Chapter 12. Subscription Management subscription-manager supports AUS subscription migration Subscription Manager now includes certificates and maps for Advanced Mission Critical Update Support (AUS). This enables migration from RHN Classic to RHSM for AUS subscriptions. subscription-manager supports activation keys for automated migration The rhn-migrate-classic-to-rhsm tool now supports activation keys when registering to Red Hat Subscription Management (RHSM). This simplifies automated migration. subscription-manager supports migrating without RHN Classic credentials New --keep option for rhn-migrate-classic-to-rhsm The rhn-migrate-classic-to-rhsm tool no longer requires RHN Classic credentials if the new --keep option is used. This functionality can help simplify automated migration.

Commands:
4.2. Converting to an ext3 File System The tune2fs command converts an ext2 file system to ext3 . Note To convert ext2 to ext3, always use the e2fsck utility to check your file system before and after using tune2fs . Before trying to convert ext2 to ext3, back up all file systems in case any errors occur. In addition, Red Hat recommends creating a new ext3 file system and migrating data to it, instead of converting from ext2 to ext3 whenever possible. To convert an ext2 file system to ext3 , log in as root and type the following command in a terminal: block_device contains the ext2 file system to be converted. Issue the df command to display mounted file systems.

Commands:
tune2fs -j block_device
Chapter 2. Starting a trial of Red Hat Ansible Lightspeed Red Hat Ansible Lightspeed cloud service provides a free 90-day trial for existing Ansible users. To start a free trial, you need a trial or paid subscription to the Red Hat Ansible Automation Platform, but you do not need a trial or paid subscription to IBM watsonx Code Assistant. This means that you do not need to configure the API key or model ID when setting up a trial account. Using the trial account, you can create single-task and multitask recommendations, generate playbooks, and view playbook explanations. Prerequisites You must have a trial or paid subscription to the Red Hat Ansible Automation Platform. You must have installed the Ansible VS Code extension. For the steps, see Installing the Ansible VS Code extension . You must have configured the Ansible VS Code extension to enable Red Hat Ansible Lightspeed. For the steps, see Configuring the Ansible VS Code extension . Procedure Open the VS Code application. From the VS Code activity bar, click the Ansible icon to open the left panel. Ensure that you have configured the Ansible VS Code extension to enable Red Hat Ansible Lightspeed. For the steps, see Configuring the Ansible VS Code extension . In the Ansible Lightspeed view, click Connect . Enter your Red Hat account username and password. In the Ansible Lightspeed view, click Start trial . The Ansible Lightspeed portal login page opens. On the Ansible Lightspeed Portal, select the checkbox to accept the IBM terms and conditions before proceeding. You can also select to receive notifications about Red Hat products, services, and events. You can unsubscribe anytime if you no longer wish to receive the marketing emails. Click Start trial . Your Red Hat Ansible Lightspeed trial has started. View the time remaining on your trial account: From the VS Code activity bar, click the Ansible icon. In the Ansible Lightspeed view, verify that you are logged in using your trial account and view the expiration date of your trial account.

Commands:
2.2. Partitioning the Disk Red Hat recommends creating separate partitions for the /boot , / , /home , /tmp , and /var/tmp/ directories. The reasons for each are different, and we will address each partition. /boot This partition is the first partition that is read by the system during boot up. The boot loader and kernel images that are used to boot your system into Red Hat Enterprise Linux 7 are stored in this partition. This partition should not be encrypted. If this partition is included in / and that partition is encrypted or otherwise becomes unavailable then your system will not be able to boot. /home When user data ( /home ) is stored in / instead of in a separate partition, the partition can fill up causing the operating system to become unstable. Also, when upgrading your system to the version of Red Hat Enterprise Linux 7 it is a lot easier when you can keep your data in the /home partition as it will not be overwritten during installation. If the root partition ( / ) becomes corrupt your data could be lost forever. By using a separate partition there is slightly more protection against data loss. You can also target this partition for frequent backups. /tmp and /var/tmp/ Both the /tmp and /var/tmp/ directories are used to store data that does not need to be stored for a long period of time. However, if a lot of data floods one of these directories it can consume all of your storage space. If this happens and these directories are stored within / then your system could become unstable and crash. For this reason, moving these directories into their own partitions is a good idea. Note During the installation process, you have an option to encrypt partitions. You must supply a passphrase. This passphrase serves as a key to unlock the bulk encryption key, which is used to secure the partition's data. For more information, see Section 4.9.1, "Using LUKS Disk Encryption" .

Commands:
6.4. Removing a Disk from a Logical Volume This example shows how you can remove a disk from an existing logical volume, either to replace the disk or to use the disk as part of a different volume. In order to remove a disk, you must first move the extents on the LVM physical volume to a different disk or set of disks. 6.4.1. Moving Extents to Existing Physical Volumes In this example, the logical volume is distributed across four physical volumes in the volume group myvg . We want to move the extents off of /dev/sdb1 so that we can remove it from the volume group. If there are enough free extents on the other physical volumes in the volume group, you can execute the pvmove command on the device you want to remove with no other options and the extents will be distributed to the other devices. After the pvmove command has finished executing, the distribution of extents is as follows: Use the vgreduce command to remove the physical volume /dev/sdb1 from the volume group. The disk can now be physically removed or allocated to other users.

Commands:
pvs -o+pv_used PV VG Fmt Attr PSize PFree Used /dev/sda1 myvg lvm2 a- 17.15G 12.15G 5.00G /dev/sdb1 myvg lvm2 a- 17.15G 12.15G 5.00G /dev/sdc1 myvg lvm2 a- 17.15G 12.15G 5.00G /dev/sdd1 myvg lvm2 a- 17.15G 2.15G 15.00G
pvmove /dev/sdb1 /dev/sdb1: Moved: 2.0% /dev/sdb1: Moved: 79.2% /dev/sdb1: Moved: 100.0%
pvs -o+pv_used PV VG Fmt Attr PSize PFree Used /dev/sda1 myvg lvm2 a- 17.15G 7.15G 10.00G /dev/sdb1 myvg lvm2 a- 17.15G 17.15G 0 /dev/sdc1 myvg lvm2 a- 17.15G 12.15G 5.00G /dev/sdd1 myvg lvm2 a- 17.15G 2.15G 15.00G
vgreduce myvg /dev/sdb1 Removed "/dev/sdb1" from volume group "myvg" pvs PV VG Fmt Attr PSize PFree /dev/sda1 myvg lvm2 a- 17.15G 7.15G /dev/sdb1 lvm2 -- 17.15G 17.15G /dev/sdc1 myvg lvm2 a- 17.15G 12.15G /dev/sdd1 myvg lvm2 a- 17.15G 2.15G
Appendix A. KDE Plasma Workspaces As an alternative to the default GNOME desktop environment, Red Hat Enterprise Linux 7 provides version 4 of KDE Plasma Workspaces (previously known as K Desktop Environment) to match different work styles and preferences. Refer to the Red Hat Enterprise Linux 7 Installation Guide on setting KDE Plasma Workspaces as the default desktop during the installation process or changing your current desktop environment to KDE Plasma Workspaces . For more information on KDE Plasma Workspaces , see its upstream websites, such as https://www.kde.org/ and https://docs.kde.org/ .

Commands:
4.6. Using Multiple Power Management Fencing Agents Single agents are treated as primary agents. The secondary agent is valid when there are two fencing agents, for example for dual-power hosts in which each power switch has two agents connected to the same power switch. Agents can be of the same or different types. Having multiple fencing agents on a host increases the reliability of the fencing procedure. For example, when the sole fencing agent on a host fails, the host will remain in a non-operational state until it is manually rebooted. The virtual machines previously running on the host will be suspended, and only fail over to another host in the cluster after the original host is manually fenced. With multiple agents, if the first agent fails, the agent can be called. When two fencing agents are defined on a host, they can be configured to use a concurrent or sequential flow: Concurrent : Both primary and secondary agents have to respond to the Stop command for the host to be stopped. If one agent responds to the Start command, the host will go up. Sequential : To stop or start a host, the primary agent is used first, and if it fails, the secondary agent is used.

Commands: