mtpti5iD/redhat-docs_dataset huggingface dataset:
5.295. SDL 5.295.1. RHBA-2012:0446 - SDL bug fix update An updated SDL package that fixes multiple bugs is now available for Red Hat Enterprise Linux 6. Simple DirectMedia Layer (SDL) is a cross-platform multimedia library designed to provide fast access to the graphics frame buffer and audio device. Bug Fixes BZ# 733605 If the SDL_VM_GrabInput() function was called when the window of an SDL application was not visible (for example, the window was displayed on a different workspace or outside of the screen borders), the SDL library, and therefore the current application thread, was unresponsive until the window became visible and the input could be grabbed. The SDL_VM_GrabInput() function has been adjusted to return immediately with the proper error code signaling that the grab failed. BZ# 678569 Previously, calling the SDL_BlitSurface() function on overlapping rectangles when running the Streaming SIMD Extensions 3 (SSE3) optimized standard C library caused the bitmap content on the screen to be corrupted. The internal SDL_BlitCopyOverlap() function has been fixed to copy bitmaps between overlapping areas correctly. The SDL_BlitSurface() function now performs correctly even if the standard C library does not implement the memcpy() function safely for operations on overlapping memory areas. BZ# 640682 When running an SDL application in window mode and using certain window managers (like Fluxbox), the left-button event was not reported to the application. This update fixes dispatching of notifications when a window is left and the parent window is not interested in grabbing or ungrabbing events to handle window focus changes. With this update, the event of pressing the mouse button is reported to the application even if the window manager handles grab events. BZ# 640694 When using a hat-type analog joystick in an SDL application, the application terminated unexpectedly with a segmentation fault when the user moved the hat. The data structure which defines the analog part of a joystick has been updated to match the data structure passed by the kernel to the SDL library. The state of the analog hat is now properly passed by the kernel to the SDL library and it is interpreted accurately by the library. BZ# 640687 Prior to this update, the SDL spec file contained two invalid configuration options. This update removes these unrecognized options from the spec file. All options defined in the spec file are now recognized by the SDL configure script. All users of SDL are advised to upgrade to this updated package, which fixes these bugs.

Commands:
5.4. guestfish guestfish is a shell and command-line tool for examining and modifying virtual machine disk images. This tool uses libguestfs and exposes all functionality provided by the guestfs API. Warning Using guestfish on running virtual machines may cause disk-image corruption. Use the guestfish command with the --ro (read-only) option if the disk image is being used by a running virtual machine. Note Refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information about guestfish .

Commands:
21.5. Other Commands This section describes tools that are simpler equivalents to using guestfish to view and edit guest virtual machine disk images. virt-cat is similar to the guestfish download command. It downloads and displays a single file to the guest virtual machine. For example: virt-edit is similar to the guestfish edit command. It can be used to interactively edit a single file within a guest virtual machine. For example, you may need to edit the grub.conf file in a Linux-based guest virtual machine that will not boot: virt-edit has another mode where it can be used to make simple non-interactive changes to a single file. For this, the -e option is used. For example, the following command changes the root password in a Linux guest virtual machine to having no password: virt-ls is similar to the guestfish ls , ll and find commands. It is used to list a directory or directories (recursively). For example, the following command would recursively list files and directories under /home in a Linux guest virtual machine:

Commands:
virt-cat RHEL3 /etc/ntp.conf | grep ^server server 127.127.1.0 # local clock
virt-edit LinuxGuest /boot/grub/grub.conf
virt-edit LinuxGuest /etc/passwd -e 's/^root:.*?:/root::/'
virt-ls -R LinuxGuest /home/ | less
Part I. About Messaging and JBoss EAP 7 The messaging broker in JBoss EAP 6 was called HornetQ, a JBoss community project. The HornetQ codebase was donated to the Apache ActiveMQ project, and the HornetQ community joined that project to enhance the donated codebase and create a -generation messaging broker. The result is Apache ActiveMQ Artemis, the messaging broker for JBoss EAP 7, providing messaging consolidation and backwards compatibility with JBoss EAP 6. While ActiveMQ Artemis retains protocol compatibility with the HornetQ broker in JBoss EAP 6, it also contains some smart new features. This guide will explore, and provide useful examples for, the many features of the ActiveMQ Artemis broker available in JBoss EAP 7.4.

Commands:
Chapter 1. OpenShift Container Platform CI/CD overview OpenShift Container Platform is an enterprise-ready Kubernetes platform for developers, which enables organizations to automate the application delivery process through DevOps practices, such as continuous integration (CI) and continuous delivery (CD). To meet your organizational needs, the OpenShift Container Platform provides the following CI/CD solutions: OpenShift Builds OpenShift Pipelines OpenShift GitOps 1.1. OpenShift Builds With OpenShift Builds, you can create cloud-native apps by using a declarative build process. You can define the build process in a YAML file that you use to create a BuildConfig object. This definition includes attributes such as build triggers, input parameters, and source code. When deployed, the BuildConfig object typically builds a runnable image and pushes it to a container image registry. OpenShift Builds provides the following extensible support for build strategies: Docker build Source-to-image (S2I) build Custom build For more information, see Understanding image builds 1.2. OpenShift Pipelines OpenShift Pipelines provides a Kubernetes-native CI/CD framework to design and run each step of the CI/CD pipeline in its own container. It can scale independently to meet the on-demand pipelines with predictable outcomes. For more information, see Understanding OpenShift Pipelines . 1.3. OpenShift GitOps OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles. For more information, see About Red Hat OpenShift GitOps . 1.4. Jenkins Jenkins automates the process of building, testing, and deploying applications and projects. OpenShift Developer Tools provides a Jenkins image that integrates directly with the OpenShift Container Platform. Jenkins can be deployed on OpenShift by using the Samples Operator templates or certified Helm chart.

Commands:
Chapter 12. Running the assisted installer tests The assisted installer tests verify that your bare-metal servers can be installed by using the assisted installer for OpenShift Container Platform. The tests are for bare-metal servers only. VMs are not supported. Important If you prefer using Cockpit instead of the command line for Assisted Installer certification testing, you must set up the Cockpit first. See Configuring the systems and running tests by using Cockpit for instructions. Prerequisites You have installed the HUT as a single-node OpenShift cluster by using the assisted installer for Red Hat OpenShift Container Platform. You have configured the kubeconfig file as explained in the assisted installer for Red Hat OpenShift Container Platform documentation . You have run rhcert-provision command by using either of the following methods: By following the steps while running rhcert-provision command, which downloads the test plan directly from connect portal , for which authentication is mandatory. By using the test plan downloaded from connect portal as explained in Creating a Bare Metal supplemental certification documentation. Procedure Log in to the single-node cluster. Install the following redhat-certification packages: redhat-certification redhat-certification-openshift For example: In the Red Hat Hybrid Cloud Console , generate an OpenShift Manager API token. Add the token to the OFFLINE_TOKEN variable and export it. For example, Confirm if the cluster is accessible by using the following command: Run the tests according to test plan: The similar set of tests get displayed as follows: Alternatively, you can use rhcert-cli to run the test as follows: Save the test result: Submit the results of both tests to the supplemental RHOCP certification for your server at the Red Hat Certification website .

Commands:
dnf install redhat-certification redhat-certification-openshift
export OFFLINE_TOKEN=<value_of_your_token>
oc status
rhcert-run
rhcert-cli plan
rhcert-cli run -test assisted_installer
rhcert-cli save
10.2.2.4. Content Negotiation The CacheNegotiatedDocs directive now takes the argument on or off . Existing instances of CacheNegotiatedDocs should be replaced with CacheNegotiatedDocs on . For more on this topic, refer to the following documentation on the Apache Software Foundation's website: http://httpd.apache.org/docs-2.0/mod/mod_negotiation.html#cachenegotiateddocs

Commands:
Chapter 2. Subscription management with Red Hat Satellite With Red Hat Satellite, you can track usage of software subscriptions and assign subscriptions according to your needs. 2.1. Simple content access (SCA) in Red Hat Satellite Simple Content Access (SCA) in Satellite simplifies management of software entitlements. With SCA, you can add valid subscriptions to a subscription allocation or manifest and refresh within Satellite. Therefore, with SCA enabled, you do not need to attach subscriptions individually to hosts. Note Simple Content Access (SCA) replaces the entitlement-based method of subscription management. New organizations default to having SCA enabled. Entitlement-based subscription management is deprecated. For more information, see Release notes . Additional resources See Simple Content Access - FAQ for more details on SCA. See Simple Content Access for details on enabling and using SCA. 2.2. Additional resources For more information about how to manage subscriptions with Satellite, see Managing content .

Commands:
13.2.3. Keeping Quotas Accurate Whenever a file system is not unmounted cleanly (due to a system crash, for example), it is necessary to run quotacheck . However, quotacheck can be run on a regular basis, even if the system has not crashed. Running the following command periodically keeps the quotas more accurate (the options used have been described in Section 13.1.1, "Enabling Quotas" ): The easiest way to run it periodically is to use cron . As root, either use the crontab -e command to schedule a periodic quotacheck or place a script that runs quotacheck in any one of the following directories (using whichever interval best matches your needs): /etc/cron.hourly /etc/cron.daily /etc/cron.weekly /etc/cron.monthly The most accurate quota statistics can be obtained when the file system(s) analyzed are not in active use. Thus, the cron task should be schedule during a time where the file system(s) are used the least. If this time is various for different file systems with quotas, run quotacheck for each file system at different times with multiple cron tasks. Refer to Chapter 34, Automated Tasks for more information about configuring cron .

Commands:
quotacheck -avug
Chapter 63. Storage No support for thin provisioning on top of RAID in a cluster While RAID logical volumes and thinly provisioned logical volumes can be used in a cluster when activated exclusively, there is currently no support for thin provisioning on top of RAID in a cluster. This is the case even if the combination is activated exclusively. Currently this combination is only supported in LVM's single machine non-clustered mode. (BZ# 1014758 ) Anaconda installation can fail when LVM or md device has metadata from a install During Red Hat Enetrprise Linux 7 installation on a machine where a disk to be multipathed already starts with LVM or md metadata on it from a install, multipath will not get set up on the device, and LVM/md will get set up on one of the path devices while Anaconda is starting up. This can create problems with Anaconda, and cause the installation to fail. The workaround for this issue is to add mpath.wwid=<WWID> to the kernel command line when booting up for the installation. <WWID> is the wwid of the device that multipath should claim. This value is also the same as the ID_SERIAL udev database value for scsi devices and ID_UID for DASD devices. (BZ#1378714)

Commands:
Chapter 52. Compiler and Tools Oprofile utilities cannot collect performance data in kernel code by default Kernel in Red Hat Enterprise Linux 7.3 changes the default value of /proc/sys/kernel/perf_event_paranoid from 1 to 2 . As a consequence, collection of performance event data of code in the kernel requires root privileges. When running the occount or operf utility as a normal user, the default performance event attempts to collect data for both kernel and user code and the setup of the performance event fails because of the default perf_event_paranoid setting. To work around this problem, change the value in /proc/sys/kernel/perf_event_paranoid to 1 . If unable to do that, instead determine the default event used on the machine by running the ophelp -d command, and then explicitly change the end of the event from :1:1 to :0:1 to disable data collection in the kernel space, for example: As a result, changing /proc/sys/kernel/perf_event_paranoid or explicitly disabling monitoring of kernel events for normal users allows collection of data, thus avoiding this issue. (BZ#1349077) The pesign key database requires manually changing permissions to enable improved access permission controls The pesign key database, which is used to sign UEFI binaries, now offers a more generalized method of setting database access permissions. You can now configure permissions using system-wide key databases, and means that any user or group can now be granted access. However, a known issue in permission settings in pesign currently prevents the aforementioned new feature from working. To enable the improved access control, you must change the permissions to pesign manually: After setting these permissions, the improved access control will become available. If you do not perform these steps, pesign behavior will be identical to releases. (BZ# 1141263 )

Commands:
operf -e CPU_CLK_UNHALTED:100000:0:0:1 true
chmod 0660 /etc/pki/pesign/* chmod 0770 /etc/pki/pesign
Chapter 9. Disconnected environment Disconnected environment is a network restricted environment where Operator Lifecycle Manager (OLM) cannot access the default Operator Hub and image registries, which require Internet connectivity. Red Hat supports deployment of OpenShift Data Foundation in disconnected environments where OpenShift Container Platform is installed in restricted networks. To install OpenShift Data Foundation in a disconnected environment, refer to the steps in the Using Operator Lifecycle Manager on restricted networks chapter of Operators guide in OpenShift Container Platform documentation. Note When you install OpenShift Data Foundation in a restricted network environment, apply a custom Network Time Protocol (NTP) configuration to the nodes, because by default, internet connectivity is assumed in OpenShift Container Platform and chronyd is configured to use *.rhel.pool.ntp.org servers. See Red Hat Knowledgebase article and Configuring chrony time service for more details. Packages to include for OpenShift Data Foundation At the time of pruning redhat-operator index image, include the following list of packages for OpenShift Data Foundation deployment: ocs-operator odf-operator mcg-operator (optional) local-storage-operator (only for local storage deployments) (optional) odf-multicluster-orchestrator (only for Regional disaster recovery configuration) Important CatalogSource must be named as redhat-operators .

Commands:
Chapter 5. CXF Configuration 5.1. CXF Configuration If your configuration uses CXF, you need to specify the data source configuration file and port configuration. The ConfigFile property, set in the server configuration file for the resource-adapter subsystem, specifies the Spring XML configuration file. (The system's default configuration is used if the configuration file is not specified.) The EndPointName property, also set in the server configuration file for the resource-adapter subsystem, specifies the port configuration. Set this to the local part of the desired port QName. The configuration file property is specified via this command:

Commands:
/subsystem=resource-adapters/resource-adapter=webservice/connection-definitions=wsDS/config-properties=ConfigFile:add(value=USD{jboss.server.home.dir}/standalone/configuration/xxx-jbossws-cxf.xml)
Chapter 1. OpenStack Integration Test Suite (tempest) validations Because Red Hat OpenStack Platform (RHOSP) consists of many different projects, it is important to test the interoperability of the projects within your RHOSP cluster. The OpenStack Integration Test Suite automates the integration testing of your RHOSP deployment. You can run tests to ensure that your cluster works as expected. Test output to provide early warning of potential problems, especially after an upgrade. The Integration Test Suite contains tests for OpenStack API validation and scenario testing, as well as unit testing for self-validation. The Integration Test Suite performs black box testing by using the OpenStack public APIs, with tempest as the test runner. The OpenStack Integration Test Suite (tempest) acts as a gate for commits to the Red Hat OpenStack Platform (RHOSP) core projects, it can stress test to generate load on a cloud deployment, and it can perform CLI tests to check the response formatting of the command line. You can run scenario tests and API tests against your RHOSP cloud deployment. Scenario tests Scenario tests simulate a typical end user action workflow to test the integration points between services. The testing framework conducts the configuration, tests the integration between services, and is then removed automatically. Tag the tests with the services that they relate to clarify, which client libraries the test uses. The following scenarios are based on a use case: Uploading an image to the Image Service Deploying an instance from the image Attaching a volume to the instance Creating a snapshot of the instance Detaching the volume from the instance API tests API tests validate the OpenStack API. Tests use the OpenStack Integration Test Suite implementation of the OpenStack API. You can use both valid and invalid JSON to ensure that error responses are valid. You can run tests independently and you do not have to rely on the test state.

Commands:
Chapter 24. The Object-Graph Navigation Language(OGNL) Overview OGNL is an expression language for getting and setting properties of Java objects. You use the same expression for both getting and setting the value of a property. The OGNL support is in the camel-ognl module. Camel on EAP deployment This component is supported by the Camel on EAP (Wildfly Camel) framework, which offers a simplified deployment model on the Red Hat JBoss Enterprise Application Platform (JBoss EAP) container. Adding the OGNL module To use OGNL in your routes you need to add a dependency on camel-ognl to your project as shown in Example 24.1, "Adding the camel-ognl dependency" . Example 24.1. Adding the camel-ognl dependency Static import To use the ognl() static method in your application code, include the following import statement in your Java source files: Built-in variables Table 24.1, "OGNL variables" lists the built-in variables that are accessible when using OGNL. Table 24.1. OGNL variables Name Type Description this org.apache.camel.Exchange The current Exchange exchange org.apache.camel.Exchange The current Exchange exception Throwable the Exchange exception (if any) exchangeID String the Exchange ID fault org.apache.camel.Message The Fault message(if any) request org.apache.camel.Message The IN message response org.apache.camel.Message The OUT message properties Map The Exchange properties property( name ) Object The value of the named Exchange property property( name , type ) Type The typed value of the named Exchange property Example Example 24.2, "Route using OGNL" shows a route that uses OGNL. Example 24.2. Route using OGNL

Commands:
<!-- Maven POM File --> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-ognl</artifactId> <version>USD{camel-version}</version> </dependency> </dependencies>
import static org.apache.camel.language.ognl.OgnlExpression.ognl;
<camelContext> <route> <from uri="seda:foo"/> <filter> <language langauge="ognl">request.headers.foo == 'bar'</language> <to uri="seda:bar"/> </filter> </route> </camelContext>
Chapter 2. Finding entries using the web console You can search for directory entries using the web console. 2.1. Finding entries using the LDAP Browser You can use the LDAP Browser in the web console to search for entries in the Directory Server databases. Directory Server searches for entries based on the attribute-value pairs stored in the entries, not based on the attributes used in the distinguished names (DN) of these entries. For example, if an entry has a DN of uid=user_name,ou=People,dc=example,dc=com , then a search for dc=example matches the entry only when dc:example attribute exists in this entry. Prerequisites You are logged into the Directory Server web console. You have root permissions. Procedure In the web console, navigate to LDAP Browser Search . Expand and select the search criteria to filter entries: Search parameter Description Search base Specifies the starting point of the search. It is a distinguished name (DN) that currently exists in the database. Note The Search tabs opens with pre-defined search base, when you open an entry details in the Tree View or Table View , click on the Options menu (⫶) and select Search . Search Scope Select Subtree to search entries in the whole subtree starting from the search base and including all child entries. Select One Level to search entries starting from the search base and including only the first level of child entries. Select Base to search for attribute values only in the entry specified as the search base. Size Limit Set the maximum number of entries to return from a search operation. Time Limit Set the time in seconds the search engine can look for entries. Show Locking Toggle the switch to on to see the lock status of the found entries. Search Attributes Select attributes that take part in the search. You can choose from the predefined attributes and add custom ones. Type the attribute value in the search text field and press Enter. Optional: To further refine your search, use search filters in the Filter tab to search for entries. Note Directory Server records all search requests to the access log file, which you can view at Monitoring Logging Access Log . Additional resources nsslapd-timelimit description nsslapd-sizelimit description

Commands: