mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 2. Packaging Software Collections This chapter introduces you to packaging Software Collections. 2.1. Creating Your Own Software Collections In general, you can use one of the following two approaches to deploy an application that depends on an existing Software Collection: install all required Software Collections and packages manually and then deploy your application, or create a new Software Collection for your application. When creating a new Software Collection for your application: Create a Software Collection metapackage Each Software Collection includes a metapackage, which installs a subset of the Software Collection's packages that are essential for the user to perform most common tasks with the Software Collection. See Section 2.7.1, "Metapackage" for more information on creating metapackages. Consider specifying the location of the Software Collection root directory You are advised to specify the location of the Software Collection root directory by setting the %_scl_prefix macro in the Software Collection spec file. For more information, see Section 2.3, "The Software Collection Root Directory" . Consider prefixing the name of your Software Collection packages You are advised to prefix the name of your Software Collection packages with the vendor and Software Collection's name. For more information, see Section 2.4, "The Software Collection Prefix" . Specify all Software Collections and other packages required by your application as dependencies Ensure that all Software Collections and other packages required by your application are specified as dependencies of your Software Collection. For more information, see Section 2.10.8, "Making a Software Collection Depend on Another Software Collection" . Convert existing conventional packages or create new Software Collection packages Ensure that all macros in your Software Collection package spec files use conditionals. See Section 2.10, "Converting a Conventional Spec File" for more information on how to convert an existing package spec file. Build your Software Collection After you create the Software Collection metapackage and convert or create packages for your Software Collection, you can build the Software Collection with the rpmbuild utility. For more information, see Section 2.12, "Building a Software Collection" .

Commands:
7.234. xorg-x11-drv-mach64 7.234.1. RHBA-2015:1434 - xorg-x11-drv-mach64 bug fix update Updated xorg-x11-drv-mach64 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-mach64 packages provide the X.Org X11 Mach64 video driver. Bug Fix BZ# 1182124 Upgrading the xorg-x11-drv-mach64 packages on a Red Hat Enterprise Linux 6 system with the ATI Rage XL VGA video card to Red Hat Enterprise Linux 6.6 introduced a bug. As a consequence, after booting the system in GUI mode, X.Org X11 terminated with a segmentation fault with the Mach64 accelerator. A patch has been applied to address this bug, and X.Org X11 no longer crashes in the described situation. Users of xorg-x11-drv-mach64 are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Customizing storage in Red Hat OpenStack Services on OpenShift When you have planned and configured the storage solution for your Red Hat OpenStack Services on OpenShift (RHOSO) deployment, you can make post-deployment configurations and customizations for functionality, scaling, and security in the following storage services: Block Storage service (cinder) Image service (glance) Object Storage service (swift) Shared File Systems service (manila) For information about planning the storage solution and related requirements for your RHOSO deployment, for example, networking and security, see Planning storage and shared file systems in Planning your deployment . For information about configuring storage services, see Configuring persistent storage . For information about performing operations with the storage services, see Performing storage operations .

Commands:
14.6.6. Sending Process Signal Names to Virtual Processes Using the virsh send-process-signal domain-ID PID signame command sends the specified signal (identified by its signame ) to a process running in a virtual domain (specified by the domain ID ) and identified by its process ID ( PID ). Either an integer signal constant number or a symbolic signal name can be sent this way. Thus, for example, both of the following commands send the kill signal to process ID 187 on the rhel6 domain: For the full list of available signals and their uses, see the virsh(1) and signal(7) manual pages.

Commands:
virsh send-process-signal rhel6 187 kill virsh send-process-signal rhel6 187 9
Installing Red Hat Virtualization as a self-hosted engine using the command line Red Hat Virtualization 4.3 ALTERNATIVE method - Using the command line to install the Red Hat Virtualization Manager as a virtual machine running on the same hosts it manages Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract This document describes how to install a self-hosted engine environment - where the Red Hat Virtualization Manager (or "engine") is installed on a virtual machine that runs on specialized hosts in the same environment it manages - using the command line to configure and run an automated installation. If this is not the configuration you want to use, see the other Installation Options in the Product Guide .

Commands:
3.2. RHEA-2011:1729 - new package: fcoe-target-utils A new fcoe-target-utils package is now available as a Technology Preview for Red Hat Enterprise Linux 6. The fcoe-target-utils package is a command line interface for configuring FCoE LUNs (Fibre Channel over Ethernet Logical Unit Numbers) and backstores. This enhancement update adds a new fcoe-target-utils package to Red Hat Enterprise Linux 6 as a Technology Preview. (BZ# 724035 ) More information about Red Hat Technology Previews is available here: https://access.redhat.com/support/offerings/techpreview/ All users who want to use the fcoe-target-utils Technology Preview should install this newly-released package, which adds this enhancement.

Commands:
4.4.2. Dynamic Configuration Dynamic label configuration is the default labeling option when using sVirt with SELinux. Refer to the following example which demonstrates dynamic labeling: In this example, the qemu-kvm process has a base label of system_u:system_r:svirt_t:s0 . The libvirt system has generated a unique MCS label of c87,c520 for this process. The base label and the MCS label are combined to form the complete security label for the process. Likewise, libvirt takes the same MCS label and base label to form the image label. This image label is then automatically applied to all host files that the VM is required to access, such as disk images, disk devices, PCI devices, USB devices, and kernel/initrd files. Each process is isolated from other virtual machines with different labels. The following example shows the virtual machine's unique security label (with a corresponding MCS label of c87,c520 in this case) as applied to the guest disk image file in /var/lib/libvirt/images : The following example shows dynamic labeling in the XML configuration for the guest:

Commands:
ps -eZ | grep qemu-kvm system_u:system_r:svirt_t:s0:c87,c520 27950 ? 00:00:17 qemu-kvm
ls -lZ /var/lib/libvirt/images/* system_u:object_r:svirt_image_t:s0:c87,c520 image1
<seclabel type='dynamic' model='selinux' relabel='yes'> <label>system_u:system_r:svirt_t:s0:c87,c520</label> <imagelabel>system_u:object_r:svirt_image_t:s0:c87,c520</imagelabel> </seclabel>
10.5.41. ScriptAlias The ScriptAlias directive defines where CGI scripts are located. Generally, it is not good practice to leave CGI scripts within the DocumentRoot , where they can potentially be viewed as text documents. For this reason, a special directory outside of the DocumentRoot directory containing server-side executables and scripts is designated by the ScriptAlias directive. This directory is known as a cgi-bin and is set to /var/www/cgi-bin/ by default. It is possible to establish directories for storing executables outside of the cgi-bin/ directory. For instructions on doing so, refer to Section 10.5.56, " AddHandler " and Section 10.5.22, " Directory " .

Commands:
8.205. rsync 8.205.1. RHBA-2014:0451 - rsync bug fix update Updated rsync packages that fix one bug are now available for Red Hat Enterprise Linux 6. The rsync tool is used to copy and synchronize files locally or across a network. The rsync tool works very fast because it uses delta encoding and sends just differences in files instead of whole files. Also, rsync can be used as a powerful mirroring tool. Bug Fix BZ# 981797 Previously, the rsync tool changed the file ownership after, not before, setting security attributes. As a consequence, the security attributes on the target were missing, and running the "rsync -X" command did not work correctly under certain circumstances. With this update, the order of the operations has been switched, and rsync now changes the ownerships before setting the security attributes. As a result, the security attributes are present as expected in the described situation. Users of rsync are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 8. GNOME Screen Recording GNOME Screen Recording is a built-in feature in the GNOME desktop environment that allows users to record their desktop or specific application activities. The recordings are saved as video files in the WebM format. Procedure To start the recording, press the Ctrl + Alt + Shift + R keyboard shortcut. Once the recording begins, a red circle indicator appears in the upper-right corner of the screen, indicating that the recording is active. To stop the recording, press the same Ctrl + Alt + Shift + R keyboard shortcut again. The red circle indicator disappears, signaling the end of the recording. The recorded video files are saved in the ~/Videos directory. The filenames of recorded videos start with Screencast and include the date and time of the recording.

Commands:
8.143. mod_nss 8.143.1. RHBA-2014:1548 - mod_nss bug fix update Updated mod_nss packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The mod_nss module provides strong cryptography for the Apache HTTP Server via the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols, using the Network Security Services (NSS) security library. Bug Fixes BZ# 866703 Previously, the nss_var_lookup_nss_cert_PEM() function from the nss_engine_vars.c file occasionally caused a memory error. This bug has been fixed and the memory error no longer occurs. BZ# 1002733 Due to a bug in the nss-softokn package that is a dependency of the mod_nss package, the root process of the httpd daemon was occasionally terminated by a SIGTRAP signal. With this update, mod_nss has been updated to depend on a corrected version of nss-softokn and the root httpd process is no longer terminated by SIGTRAP. BZ# 1016628 Due to a bug in the nss-softokn package that is a dependency of the mod_nss package, the httpd daemon sometimes terminated unexpectedly with a segmentation fault and the following message was returned: NSS_Initialize failed. Certificate database: /etc/httpd/alias With this update, mod_nss has been updated to depend on a corrected version of nss-softokn and httpd no longer crashes in the described case. Users of mod_nss are advised to upgrade to these updated packages, which fix these bugs. The httpd service must be restarted for this update to take effect.

Commands:
8.3.4. Installing via NFS The NFS dialog applies only if you selected NFS Image in the Installation Method dialog. If you used the repo=nfs boot option, you already specified a server and path. Figure 8.10. NFS Setup Dialog Enter the domain name or IP address of your NFS server in the NFS server name field. For example, if you are installing from a host named eastcoast in the domain example.com , enter eastcoast.example.com . Enter the name of the exported directory in the Red Hat Enterprise Linux 6.9 directory field: If the NFS server is exporting a mirror of the Red Hat Enterprise Linux installation tree, enter the directory which contains the root of the installation tree. If everything was specified properly, a message appears indicating that the installation program for Red Hat Enterprise Linux is running. If the NFS server is exporting the ISO image of the Red Hat Enterprise Linux DVD, enter the directory which contains the ISO image. If you followed the setup described in Section 4.1.2, "Preparing for an NFS Installation" , the exported directory is the one that you specified as publicly_available_directory . Specify any NFS mount options that you require in the NFS mount options field. Refer to the man pages for mount and nfs for a comprehensive list of options. If you do not require any mount options, leave the field empty. Proceed with Chapter 9, Installing Using Anaconda .

Commands:
17.3. Establishing an ISDN Connection An ISDN connection is an Internet connection established with a ISDN modem card through a special phone line installed by the phone company. ISDN connections are popular in Europe. To add an ISDN connection, follow these steps: Click the Devices tab. Click the New button on the toolbar. Select ISDN connection from the Device Type list, and click Forward . Select the ISDN adapter from the pulldown menu. Then configure the resources and D channel protocol for the adapter. Click Forward to continue. Figure 17.4. ISDN Settings If your Internet Service Provider (ISP) is in the pre-configured list, select it. Otherwise, enter the required information about your ISP account. If you do not know the values, contact your ISP. Click Forward . In the IP Settings window, select the Encapsulation Mode and whether to obtain an IP address automatically or to set a static IP instead. Click Forward when finished. On the Create Dialup Connection page, click Apply . After configuring the ISDN device, it appears in the device list as a device with type ISDN as shown in Figure 17.5, "ISDN Device" . Be sure to select File => Save to save the changes. After adding the ISDN device, you can edit its configuration by selecting the device from the device list and clicking Edit . For example, when the device is added, it is configured not to start at boot time by default. Edit its configuration to modify this setting. Compression, PPP options, login name, password, and more can be changed. When the device is added, it is not activated immediately, as seen by its Inactive status. To activate the device, select it from the device list, and click the Activate button. If the system is configured to activate the device when the computer starts (the default), this step does not have to be performed again. Figure 17.5. ISDN Device

Commands:
Chapter 4. Basic configuration options of Shenandoah garbage collector Shenandoah garbage collector (GC) has the following basic configuration options: -Xlog:gc Print the individual GC timing. -Xlog:gc+ergo Print the heuristics decisions, which might shed light on outliers, if any. -Xlog:gc+stats Print the summary table on Shenandoah internal timings at the end of the run. It is best to run this with logging enabled. This summary table conveys important information about GC performance. Heuristics logs are useful to figure out GC outliers. -XX:+AlwaysPreTouch Commit heap pages into memory and helps to reduce latency hiccups. -Xms and -Xmx Making the heap non-resizeable with -Xms = -Xmx reduces difficulties with heap management. Along with AlwaysPreTouch , the -Xms = -Xmx commit all memory on startup, which avoids difficulties when memory is finally used. -Xms also defines the low boundary for memory uncommit, so with -Xms = -Xmx all memory stays committed. If you want to configure Shenandoah for a lower footprint, then setting lower -Xms is recommended. You need to decide how low to set it to balance the commit/uncommit overhead versus memory footprint. In many cases, you can set -Xms arbitrarily low. -XX:+UseLargePages Enables hugetlbfs Linux support. -XX:+UseTransparentHugePages Enables huge pages transparently. With transparent huge pages, it is recommended to set /sys/kernel/mm/transparent_hugepage/enabled and /sys/kernel/mm/transparent_hugepage/defrag to madvise . When running with AlwaysPreTouch , it will also pay the defrag tool costs upfront at startup. -XX:+UseNUMA While Shenandoah does not support NUMA explicitly yet, it is a good idea to enable NUMA interleaving on multi-socket hosts. Coupled with AlwaysPreTouch , it provides better performance than the default out-of-the-box configuration. -XX:-UseBiasedLocking There is a tradeoff between uncontended (biased) locking throughput, and the safepoints JVM does to enable and disable them. For latency-oriented workloads, turn biased locking off. -XX:+DisableExplicitGC Invoking System.gc() from user code forces Shenandoah to perform additional GC cycle. It usually does not harm, as -XX:+ExplicitGCInvokesConcurrent gets enabled by default, which means the concurrent GC cycle would be invoked, not the STW Full GC. Revised on 2024-05-09 16:49:03 UTC

Commands:
Chapter 39. Mail Microsoft Oauth Since Camel 3.18.4 . The Mail Microsoft OAuth2 provides an implementation of org.apache.camel.component.mail.MailAuthenticator to authenticate IMAP/POP/SMTP connections and access to Email via Spring's Mail support and the underlying JavaMail system. Add the following dependency to your pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-mail-microsoft-oauth</artifactId> <version>3.20.1.redhat-00056</version> <!-- use the same version as your Camel core version --> </dependency> Importing camel-mail-microsoft-oauth will automatically import camel-mail component. 39.1. Microsoft Exchange Online OAuth2 Mail Authenticator IMAP sample To use OAuth, an application must be registered with Azure Active Directory. Follow the instructions to register a new application. Procedure Enable the application to access Exchange mailboxes via client credentials flow. For more information, see Authenticate an IMAP, POP or SMTP connection using OAuth Once everything is set up, declare and register in the registry, an instance of org.apache.camel.component.mail.MicrosoftExchangeOnlineOAuth2MailAuthenticator . For Example, in a Spring Boot application: @BindToRegistry("auth") public MicrosoftExchangeOnlineOAuth2MailAuthenticator exchangeAuthenticator(){ return new MicrosoftExchangeOnlineOAuth2MailAuthenticator(tenantId, clientId, clientSecret, "jon@doe.com"); } Then reference it in the Camel URI as follows: from("imaps://outlook.office365.com:993" + "?authenticator=#auth" + "&mail.imaps.auth.mechanisms=XOAUTH2" + "&debugMode=true" + "&delete=false")

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-mail-microsoft-oauth</artifactId> <version>3.20.1.redhat-00056</version> <!-- use the same version as your Camel core version --> </dependency>
@BindToRegistry("auth") public MicrosoftExchangeOnlineOAuth2MailAuthenticator exchangeAuthenticator(){ return new MicrosoftExchangeOnlineOAuth2MailAuthenticator(tenantId, clientId, clientSecret, "jon@doe.com"); }
from("imaps://outlook.office365.com:993" + "?authenticator=#auth" + "&mail.imaps.auth.mechanisms=XOAUTH2" + "&debugMode=true" + "&delete=false")
B.38.7. RHBA-2012:0540 - kernel bug fix update Updated kernel packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6 Extended Update Support. [Updated 12 June 2012] This advisory has been updated with the correct description for bug 811297. The packages included in this revised update have not been changed in any way from the packages included in the original advisory. The kernel packages contain the Linux kernel, the core of any Linux operating system. Bug Fix BZ# 811297 Due to incorrect use of the list_for_each_entry_safe() macro, the enumeration of remote procedure calls (RPCs) priority wait queue tasks stored in the tk_wait.links list failed. As a consequence, the rpc_wake_up() and rpc_wake_up_status() functions failed to wake up all tasks. This caused the system to become unresponsive and could significantly decrease system performance. Now, the list_for_each_entry_safe() macro is no longer used in rpc_wake_up(), ensuring reasonable system performance. Enhancement BZ# 806904 The Intelligent Platform Management Interface (IPMI) specification requires a minimum communication timeout of five seconds. Previously, the kernel incorrectly used a timeout of 1 second. This could result in failures to communicate with Baseboard Management Controllers (BMC) under certain circumstances. With this update, the timeout has been increased to five seconds to prevent such problems. All users of kernel are advised to upgrade to these updated packages, which fix this bug and add this enhancement. The system must be rebooted for this update to take effect.

Commands:
8.2. Sample Configuration for a Node without Endpoints Red Hat JBoss Data Grid provides a sample configuration to configure a node without an endpoint: Procedure 8.1. Find the JBoss Data Grid Sample Configuration for a Node Without Endpoints Extract the JBoss Data Grid ZIP 1. Extract the ZIP file for JBoss Data Grid Remote Client-Server mode. This is named jboss-datagrid-server- USD{version} . Add the relevant version to the file name. Navigate to the Appropriate Folder In the extracted folder, navigate to the USDJDG_HOME/docs/examples/config folder. Find the Configuration Sample File View the clustered-storage-only.xml file, which contains the configuration for a node with no endpoints. Report a bug

Commands:
Chapter 7. March 2024 7.1. IBM Power(R), IBM Z, IBM LinuxONE, and ARM Support The Cost Management Metrics Operator is now supported on IBM Power(R) ( ppc64le ), IBM Z(R) ( s390x ), IBM(R) LinuxONE ( s390x ), and ARM (aarch64) architectures. Cost management for OpenShift on IBM Z(R) is not IFL aware.

Commands: