mtpti5iD/redhat-docs_dataset huggingface dataset:
4.83. grub 4.83.1. RHBA-2011:1720 - grub bug fix and enhancement update An updated grub package that fixes three bugs and adds two enhancements is now available for Red Hat Enterprise Linux 6. The GRUB utility is responsible for booting the operating system kernel. Bug Fixes BZ# 677468 Due to an error in the underlying source code, versions of GRUB may have failed to boot in Unified Extensible Firmware Interface (UEFI) mode. This happened, because GRUB was making UEFI calls without aligning the stack pointer to a 16-byte boundary. With this update, a patch has been applied to correct this error, and GRUB now boots in UEFI mode as expected. BZ# 736833 Prior to this update, an attempt to install GRUB on a CCISS device may have caused the grub-install utility to report the following error: When this happened, grub-install failed to install GRUB on this device, but incorrectly reported success and returned a zero exit status. This update applies a patch that ensures that GRUB can now be successfully installed on such devices. BZ# 746106 When looking for its configuration file, the versions of GRUB did not respect vendor-specific EFI device path. With this update, the underlying source code has been adapted to use the vendor-specific EFI-device path as expected. Enhancements BZ# 629408 Prior to this update, the GRUB boot loader was unable to boot from boot drives that were larger than 2.2 TB. This update adds support for such devices on UEFI systems. BZ# 671355 On BIOS-based systems, versions of GRUB were only able to boot from first eight disk drives. This update allows GRUB to boot from up to 128 disk drives on these systems. All users of grub are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
expr: non-numeric argument
8.45. ding-libs 8.45.1. RHBA-2014:1496 - ding-libs bug fix and enhancement update Updated ding-libs packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The ding-libs packages contain a set of libraries used by the System Security Services Daemon (SSSD) and other projects and provide functions to manipulate filesystem pathnames (libpath_utils), a hash table to manage storage and access time properties (libdhash), a data type to collect data in a hierarchical structure (libcollection), a dynamically growing, reference-counted array (libref_array), and a library to process configuration files in initialization format (INI) into a library collection data structure (libini_config). Note The ding-libs packages have been upgraded to upstream version 0.3.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1069287 ) Users of ding-libs are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Overview of JBoss Fuse on JBoss EAP Deployment You can deploy Fuse applications on Red Hat JBoss Enterprise Application Platform (JBoss EAP), after installing the Fuse on EAP package into the JBoss EAP container. This part describes the deployment model using the Camel on EAP subsystem. Apache Camel in Fuse enables you to select the container to run an integrated application. Note Red Hat JBoss EAP features a range of application deployment and configuration options to cater both administrators and developers. For more information about JBOSS EAP configuration and the deployment process, refer Red Hat JBoss EAP Configuration Guide. 1.1. Supported Product Versions To see the latest version of JBoss EAP that supports Fuse 7.13, refer to the Supported Configurations page. 1.2. Camel on EAP Subsystem The Camel on EAP subsystem integrates Apache Camel directly into the JBoss EAP container. This subsystem is available after you install the Fuse on EAP package into the JBoss EAP container. It offers many advantages for Camel deployment, including simplified deployment of Camel components and tighter integration with the underlying JBoss EAP container. Red Hat recommends you to use the Camel on EAP Subsystem deployment model for deployment of Apache Camel applications on JBoss EAP.

Commands:
Chapter 5. Creating sample applications with .NET 8.0 5.1. Creating the MVC sample application s2i-dotnetcore-ex is the default Model, View, Controller (MVC) template application for .NET. This application is used as the example application by the .NET S2I image and can be created directly from the OpenShift UI using the Try Example link. The application can also be created with the OpenShift client binary ( oc ). Procedure To create the sample application using oc : Add the .NET application: Make the application accessible externally: Obtain the sharable URL: Additional resources s2i-dotnetcore-ex application repository on GitHub 5.2. Creating the CRUD sample application s2i-dotnetcore-persistent-ex is a simple Create, Read, Update, Delete (CRUD) .NET web application that stores data in a PostgreSQL database. Procedure To create the sample application using oc : Add the database: Add the .NET application: Add environment variables from the postgresql secret and database service name environment variable: Make the application accessible externally: Obtain the sharable URL: Additional resources s2i-dotnetcore-ex application repository on GitHub

Commands:
oc new-app dotnet:8.0-ubi8~https://github.com/redhat-developer/s2i-dotnetcore-ex#dotnet-8.0 --context-dir=app
oc expose service s2i-dotnetcore-ex
oc get route s2i-dotnetcore-ex
oc new-app postgresql-ephemeral
oc new-app dotnet:8.0-ubi8~https://github.com/redhat-developer/s2i-dotnetcore-persistent-ex#dotnet-8.0 --context-dir app
oc set env dc/s2i-dotnetcore-persistent-ex --from=secret/postgresql -e database-service=postgresql
oc expose service s2i-dotnetcore-persistent-ex
oc get route s2i-dotnetcore-persistent-ex
Chapter 9. Additional resources Installation Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 Installing and configuring Red Hat Process Automation Manager in a Red Hat JBoss EAP clustered environment Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss Web Server Installing and configuring KIE Server on IBM WebSphere Application Server Installing and configuring KIE Server on Oracle WebLogic Server Integration Creating Red Hat Process Automation Manager business applications with Spring Boot Integrating Red Hat Fuse with Red Hat Process Automation Manager Integrating Red Hat Process Automation Manager with Red Hat Single Sign-On Red Hat build of OptaPlanner Developing Solvers with Red Hat Process Automation Manager OpenShift Deploying an Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 4 using Operators Deploying an Red Hat Process Automation Manager environment on Red Hat OpenShift Container Platform 3 using templates

Commands:
5.3. Pcre The pcre package has been updated to 7.8. It includes the following behavioral changes: UTF-8 checking now references RFC 3629 instead of RFC 2279. This makes it more restrictive in the strings that it accepts. For example, the UTF-8 character ordinal value is now limited to 0x0010FFFF: See the RFC for more details: http://tools.ietf.org/html/rfc3629#section-12 . Saved patterns that were compiled by earlier versions of PCRE must be recompiled. This affects applications that serialize pre-compiled PCRE expressions to external memory (for example, a file) and load them later. This is usually done for performance reasons, for example in large spam filters.

Commands:
echo -ne "\x00\x11\xff\xff" | recode UCS-4-BE..UTF8 | pcregrep --utf-8 '.' pcregrep: pcre_exec() error -10 while matching this line:
Chapter 4. Notifications on the Hybrid Cloud Console Services in the Hybrid Cloud Console send notifications when certain events occur. Your Organization Administrator configures which notifications you can receive. You can choose how to receive notifications or not to receive them at all. You can also view the types of events for which notifications can be sent. 4.1. Managing notifications in the Hybrid Cloud Console You can choose how to receive notifications that your Organization Administrator or Notifications administrator has configured. You can also choose not to receive some or all notifications. Note If you are an Organization Administrator or Notifications adminstrator, you configure the notifications for users in your organization from Settings > Notifications . For detailed information, see Configuring notifications on the Red Hat Hybrid Cloud Console with FedRAMP . Prerequisites You are logged in to the Hybrid Cloud Console. Events are configured in the console. A Notifications administrator or Organization Administrator has configured behavior groups to receive event notifications. Procedure Click your user avatar in the upper right of the Red Hat Hybrid Cloud Console window. A drop-down list appears. Click User Preferences . The My Notifications page opens. Select the service you want to configure your notifications for, such as Advisor or User Access. A list of the available event notifications for the selected service opens. At the top of the list, click Select all to enable all notifications for the service, or select one of the following options for each event listed: Weekly report : Receive an email that contains the Advisor Weekly Report. Click Save to confirm your changes. Email notifications are delivered in the format and frequency that you selected. Note If you decide to stop receiving notifications, select Deselect all or uncheck the boxes for the events you do not want to be notified about, and then click Save . You will no longer receive any email notifications unless you return to this screen and enable them once again.

Commands:
14.5.22. Creating a Dump File of a Domain's Core Sometimes it is necessary (especially in the cases of troubleshooting), to create a dump file containing the core of the domain so that it can be analyzed. In this case, running virsh dump domain corefilepath --bypass-cache --live |--crash |--reset --verbose --memory-only dumps the domain core to a file specified by the corefilepath Note that some hypervisors may gave restrictions on this action and may require the user to manually ensure proper permissions on the file and path specified in the corefilepath parameter. This command is supported with SR-IOV devices as well as other passthrough devices. The following options are supported and have the following effect: --bypass-cache the file saved will not contain the file system cache. Note that selecting this option may slow down dump operation. --live will save the file as the domain continues to run and will not pause or stop the domain. --crash puts the domain in a crashed status rather than leaving it in a paused state while the dump file is saved. --reset once the dump file is successfully saved, the domain will reset. --verbose displays the progress of the dump process --memory-only the only information that will be saved in the dump file will be the domain's memory and CPU common register file. Note that the entire process can be monitored using the domjobinfo command and can be canceled using the domjobabort command.

Commands:
Chapter 4. RHOSO memcached clusters By default, all the Red Hat OpenStack Services on OpenShift (RHOSO) services in the control plane target a single memcached cluster that contains three memcached servers. This cluster is configured using a single memcached resource created by the openstack operator. The infra-operator creates the pods that host the memcached servers and the OpenShift service objects that expose the memcached service. 4.1. Monitoring the startup of the memcached service and its pods You can use the following command to monitor the memcached startup, which displays the startup state in the MESSAGE column and the service availability in the READY column: In this example, because the READY column is True , the memcached service is ready, which means that its associated pods are started and ready to accept traffic. You can use the following command to determine the status of the memcached pods: You can use the following command to describe the type of the memcached service and which ports are open: The CLUSTER-IP column entry is None because the memcached pods are accessed directly by name through the Red Hat OpenStack Services on OpenShift (RHOSO) components. The memcached service is used only to maintain a list of DNS records for each memcached pod.

Commands:
oc get memcached NAME READY MESSAGE memcached True Setup complete
oc get pods -l memcached/name=memcached NAME READY STATUS RESTARTS AGE memcached-0 1/1 Running 0 2d4h memcached-1 1/1 Running 0 15m memcached-2 1/1 Running 0 15m
oc get service memcached NAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE memcached ClusterIP None <none> 11211/TCP,11212/TCP 2d4h
Chapter 5. Managing roles Red Hat OpenStack Services on OpenShift (RHOSO) uses secure role-based access control (SRBAC) to manage access to its resources. Roles define which actions users can perform. By default, there are three predefined roles: A reader role for viewing permissions on specificed projects. A member role for creating and managing resources within specified projects. An administrative role to enable non-admin users to administer the environment. You can also create custom roles specific to your environment. 5.1. Understanding OpenStack admin role When you assign a user the role of admin in an OpenStack project, this user has permissions to view, change, create, or delete any resource on any project. This user can create shared resources that are accessible across projects, such as publicly available glance images, or provider networks. Additionally, a user with the admin role can create or delete users and manage roles. The project to which you assign a user the admin role is the default project in which openstack commands are executed. For example, if an admin user in a project named development runs the following command, a network called internal-network is created in the development project: The admin user can create an internal-network in any project by using the --project parameter: 5.2. Viewing roles with the CLI As an administrator, you can view the details of existing roles. Procedure List the available predefined roles: View details for a specified role: Note To get detailed information on the permissions associated with each role, you must audit its access to each API call. 5.3. Assigning roles in Red Hat OpenStack Services on OpenShift With SRBAC on Red Hat OpenStack Services on OpenShift (RHOSO), you can assign users to the role of admin, member, or reader within either the project or system scope. Procedure Use syntax similar to the following to provide a user a role with a project scope: Example command Use syntax similar to the following to provide a user a role with a system scope: Example command Replace <role> with either reader, member, or admin.

Commands:
openstack network create internal-network
openstack network create internal-network --project testing
openstack role list
openstack role show admin
openstack role add --user user1 --user-domain Default --project demo --project-domain Default <role>
openstack role add --user user1 --user-domain Default --system all <role>
8.67. gettext 8.67.1. RHBA-2014:0586 - gettext bug fix update Updated gettext packages that fix one bug are now available for Red Hat Enterprise Linux 6. The GNU gettext packages provide a set of tools and documentation for producing multi-lingual messages in programs. Bug Fix BZ# 1024681 Previously, when the xgettext utility encountered an invalid file and generated a warning message it would exit with a fatal error if any additional files were supplied to be processed. Consequently, no output was generated. This update fixes the error-processing code and xgettext now works as expected in the described situation. Users of gettext are advised to upgrade to these updated packages, which fix this bug.

Commands:
Preface Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security and bug fix errata. The Red Hat Enterprise Linux 6.7 Release Notes documents the major changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications for this minor release. Detailed notes on changes (that is, bugs fixed and enhancements added) in this minor release are available in the Technical Notes . The Technical Notes document also contains a complete list of all currently available Technology Previews along with packages that provide them. Capabilities and limits of Red Hat Enterprise Linux 6 as compared to other versions of the system are available in the Knowledge Base article available at https://access.redhat.com/articles/rhel-limits . Should you require information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands:
Chapter 17. Performance tuning considerations with KIE Server The following key concepts or suggested practices can help you optimize KIE Server performance. These concepts are summarized in this section as a convenience and are explained in more detail in the cross-referenced documentation, where applicable. This section will expand or change as needed with new releases of Red Hat Decision Manager. Ensure that development mode is enabled during development You can set KIE Server or specific projects in Business Central to use production mode or development mode. By default, KIE Server and all new projects in Business Central are in development mode. This mode provides features that facilitate your development experience, such as flexible project deployment policies, and features that optimize KIE Server performance during development, such as disabled duplicate GAV detection. Use development mode until your Red Hat Decision Manager environment is established and completely ready for production mode. For more information about configuring the environment mode or duplicate GAV detection, see the following resources: Chapter 7, Configuring the environment mode in KIE Server and Business Central Packaging and deploying an Red Hat Decision Manager project Adapt KIE Server capabilities and extensions to your specific needs The capabilities in KIE Server are determined by plug-in extensions that you can enable, disable, or further extend to meet your business needs. By default, KIE Server extensions are exposed through REST or JMS data transports and use predefined client APIs. You can extend existing KIE Server capabilities with additional REST endpoints, extend supported transport methods beyond REST or JMS, or extend functionality in the KIE Server client. This flexibility in KIE Server functionality enables you to adapt your KIE Server instances to your business needs, instead of adapting your business needs to the default KIE Server capabilities. For information about enabling, disabling, or extending KIE Server capabilities, see Chapter 16, KIE Server capabilities and extensions .

Commands:
9.3. Configure Invalidation Mode (Library Mode) The following procedure shows an invalidation mode cache configuration in Red Hat JBoss Data Grid's Library mode. Procedure 9.2. Invalidation Mode Configuration Configure the Clustering Element The clustering element's mode parameter's value determines the clustering mode selected for the cache. The sync element's replTimeout parameter specifies the maximum time period in milliseconds for an acknowledgment after a remote call. If the time period ends without any acknowledgment, an exception is thrown. The stateTransfer element specifies how state is transferred when a node leaves or joins the cluster. It uses the following parameters: The chunkSize parameter specifies the size of cache entry state batches to be transferred. If this value is greater than 0 , the value set is the size of chunks sent. If the value is less than 0 , all states are transferred at the same time. The fetchInMemoryState parameter when set to true , requests state information from neighboring caches on start up. This impacts the start up time for the cache. The awaitInitialTransfer parameter causes the first call to method CacheManager.getCache() on the joiner node to block and wait until the joining is complete and the cache has finished receiving state from neighboring caches (if fetchInMemoryState is enabled). This option applies to distributed and replicated caches only and is enabled by default. The timeout parameter specifies the maximum time (in milliseconds) the cache waits for responses from neighboring caches with the requested states. If no response is received within the timeout period, the start up process aborts and an exception is thrown. Specify Transport Configuration The transport element defines the transport configuration for the cache container as follows: The clusterName parameter specifies the name of the cluster. Nodes can only connect to clusters that share the same name. The distributedSyncTimeout parameter specifies the time to wait to acquire a lock on the distributed lock. This distributed lock ensures that a single cache can transfer state or rehash state at a time. The transportClass parameter specifies a class that represents a network transport for the cache container. Report a bug

Commands:
<clustering mode="invalidation"> <sync replTimeout="USD{TIME}" /> <stateTransfer chunkSize="USD{SIZE}" fetchInMemoryState="{true/false}" awaitInitialTransfer="{true/false}" timeout="USD{TIME}" />
<global> <transport clusterName="USD{NAME}" distributedSyncTimeout="USD{TIME}" transportClass="USD{CLASS}" /> </global>
Chapter 9. Freeing space on thinly-provisioned logical volumes using fstrim You can manually run fstrim to return unused logical volume space to the thin pool, which can be available for other logical volumes. Red Hat recommends running fstrim daily. Prerequisites Verify that the thin pool logical volume supports discard behavior. Discard is supported if the output of the following command for the underlying device is not zero. Note If discard_max_bytes returns 0, you can still execute the fstrim command on the thin logical volume to reclaim unused blocks to the thin pool. However, the discard or trim will not be passed down to the block layer. Procedure Run fstrim to restore physical space to the thin pool. For example, the following command discards any unused space it finds on the logical volume mounted at /gluster_bricks/data/data , and provides verbose output ( -v ).

Commands:
cat /sys/block/<device>/queue/discard_max_bytes
fstrim -v <mountpoint>
fstrim -v /gluster_bricks/data/data
4.326. tog-pegasus 4.326.1. RHBA-2011:1563 - tog-pegasus bug fix and enhancement update Updated tog-pegasus packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. OpenPegasus WBEM Services for Linux enable management solutions that deliver increased control of enterprise resources. Web-Based Enterprise Management (WBEM) is a platform and resource independent Distributed Management Task Force (DMTF) standard that defines a common information model and communication protocol for monitoring and controlling resources from diverse sources. These updated packages upgrade tog-pegasus to the more recent upstream version 2.11.0, which provides a number of bug fixes and enhancements over the packaged version. (BZ# 633577 ) Bug Fixes BZ# 607722 Previously, tog-pegasus did not comply with Red Hat multilib policy. This update moves the runtime libraries into the new tog-pegasus-libs subpackage. Now, tog-pegasus is in complience with the multilib policy. BZ# 693389 Previously, binaries in tog-pegasus were stripped of their debuginfo files during the build process. As a consequence, the debuginfo files were missing and could prevent correct debugging of crashes. This update modifies the code and binaries are no longer stripped of the debug information. Enhancements BZ# 694513 This update adds the external SLP and Privilege Separation options to provide support for IBM Systems Director. BZ# 712525 This update adds OpenSLP support to tog-pegasus. All users of tog-pegasus are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: