mtpti5iD/redhat-docs_dataset huggingface dataset:
7.78. ibus 7.78.1. RHBA-2015:0657 - ibus bug fix update Updated ibus packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The Intelligent Input Bus (IBus) is an input method framework for multilingual input in Unix-like operating systems. Bug Fixes BZ# 1066075 Previously, Java applications generated by Lotus Sametime or Eclipse became unresponsive when the Korean language input engine platform for the IBus input method (ibus-hangul) was used in Red Hat Enterprise Linux 6. To fix this bug, asynchronous key events have been added to IBus. Now, IBus can switch to asynchronous mode which resolves the hang. BZ# 1043381 Prior to this update, the X11 application became unresponsive when the user was typing using IBus and switched input contexts between the parent and the child windows. This update resolves the race condition causing this bug. Now, IBus properly handles the situation and the application no longer hangs. Users of ibus are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 29. Customizing the process designer You can customize the process designer in Business Central by editing the properties of the diagram editor on the Business Central Settings page. Procedure In Business Central, select the Admin icon in the top-right corner of the screen and select Process Designer . In the Properties section, update any of the following properties: Select the Auto hide category panel check box to automatically hide a category toolbar panel. In the Drawing area width field, enter an integer value between 2800 and 5600 to set the width of the drawing area. In the Drawing area height field, enter an integer value between 1400 and 2800 to set the height of the drawing area. Select the Enable HiDPI check box if you are using a high resolution display and are seeing blurry text and objects. This option is disabled by default. Click Save .

Commands:
4.287. scsi-target-utils 4.287.1. RHBA-2011:1762 - scsi-target-utils bug fix and enhancement update An updated scsi-target-utils package that fixes two bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6. The scsi-target-utils package contains the daemon and tools used to set up iSCSI and The iSCSI Extensions for RDMA (iSER) targets. Bug Fixes BZ# 712807 Prior to this update, scsi-target-utils could under certain circumstances terminate unexpectedly with a segmentation fault when the tgt daemon was stopped. This update modifies the source code so that scsi-target-utils no longer terminates with a segmentation fault when tgtd is stopped. BZ# 736740 Prior to this update, the SCSI target configuration tool (tgt-admin) allowed only an insufficiently small number of targets to be updated. As a result, running tgt-admin with the option update ALL failed with an error message that the target already existed. With this update, tgt-admin has been modified so that it now successfully processes large numbers of targets. Enhancement BZ# 679046 This update increases the allowable lengths of scsi_sn and scsi_id to 36 characters to allow the use of globally unique identifiers (GUID) for these properties. All users of scsi-target-utils are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
Chapter 5. Multiple JFR recordings based on the same custom trigger definition The Cryostat 3.0 agent can dynamically start a JFR recording for each custom trigger definition only once. In this release, the Cryostat agent cannot start multiple JFR recordings for the same custom trigger condition on a recurring basis. Once the Cryostat agent starts a JFR recording for a specific custom trigger definition, the agent then ignores this trigger definition for the rest of the agent session. If you want to enable the Cryostat agent to start new JFR recordings for custom trigger conditions that previously triggered a recording, you must restart the JVM that the agent is attached to.

Commands:
12.2. Customizing Default Favorite Applications Favorite applications are those visible on the GNOME Shell dash in the Activities Overview . You can use dconf to set the favorite applications for an individual user, or to set the same favorite applications for all users. 12.2.1. Setting Different Favorite Applications for Individual Users You can set the default favorite applications for an individual user by modifying their user database file found in ~/.config/dconf/user . The following sample uses dconf to set gedit , Terminal , and Nautilus as the default favorites for a user. The example code allows users to modify the list later, if they wish to do so. Example 12.3. Contents of /etc/dconf/profile : Example 12.4. Contents of ~/.config/dconf/user : Note You can also lock down the above settings to prevent users from changing them. See Section 9.5.1, "Locking Down Specific Settings" for more information. 12.2.2. Setting the Same Favorite Applications for All Users In order to have the same favorites for all users, you must modify system database files using dconf keyfiles. The following sample edits the dconf profile and then create a keyfile to set the default favorite applications for all employees in the first floor of an organization. Example 12.5. Contents of /etc/dconf/profile : Note Settings from the user database file will take precedence over the settings in the first_floor database file, but locks introduced in the first_floor database file will take priority over those present in user . For more information about locks, see Section 9.5.1, "Locking Down Specific Settings" . Example 12.6. Contents of /etc/dconf/db/first_floor.d/00_floor1_settings : Incorporate your changes into the system databases by running the dconf update command. Users must log out and back in again before the system-wide settings take effect.

Commands:
This line allows the user to change the default favorites later user-db:user
Set gedit, terminal and nautilus as default favorites [org/gnome/shell] favorite-apps = [ 'gedit.desktop' , 'gnome-terminal.desktop' , 'nautilus.desktop' ]
user-db:user This line defines a system database called first_floor system-db:first_floor
This sample sets gedit, terminal and nautilus as default favorites for all users in the first floor [org/gnome/shell] favorite-apps = [ 'gedit.desktop' , 'gnome-terminal.desktop' , 'nautilus.desktop' ]
2.2. System Performance Monitoring As stated above, system performance monitoring is normally done in response to a performance problem. Either the system is running too slowly, or programs (and sometimes even the entire system) fail to run at all. In either case, performance monitoring is normally done as the first and last steps of a three-step process: Monitoring to identify the nature and scope of the resource shortages that are causing the performance problems The data produced from monitoring is analyzed and a course of action (normally performance tuning and/or the procurement of additional hardware) is taken to resolve the problem Monitoring to ensure that the performance problem has been resolved Because of this, performance monitoring tends to be relatively short-lived in duration and more detailed in scope. Note System performance monitoring is often an iterative process, with these steps being repeated several times to arrive at the best possible system performance. The primary reason for this is that system resources and their utilization tend to be highly interrelated, meaning that often the elimination of one resource bottleneck uncovers another one.

Commands:
8.4.4. Viewing the Current Configuration To display the current values of global Yum options (that is, the options specified in the [main] section of the /etc/yum.conf file), run the yum-config-manager with no command-line options: yum-config-manager To list the content of a different configuration section or sections, use the command in the following form: yum-config-manager section You can also use a glob expression to display the configuration of all matching sections: yum-config-manager glob_expression For example, to list all configuration options and their corresponding values, type the following at a shell prompt:

Commands:
~]USD yum-config-manager main \* Loaded plugins: product-id, refresh-packagekit, subscription-manager ================================== main =================================== [main] alwaysprompt = True assumeyes = False bandwith = 0 bugtracker_url = https://bugzilla.redhat.com/enter_bug.cgi?product=Red%20Hat%20Enterprise%20Linux%206&component=yum cache = 0 [output truncated]
5.6.3. Logical Volume Management One other advanced storage technology is that of logical volume management (LVM). LVM makes it possible to treat physical mass storage devices as low-level building blocks on which different storage configurations are built. The exact capabilities vary according to the specific implementation, but can include physical storage grouping, logical volume resizing, and data migration. 5.6.3.1. Physical Storage Grouping Although the name given to this capability may differ, physical storage grouping is the foundation for all LVM implementations. As the name implies, the physical mass storage devices can be grouped together in such a way as to create one or more logical mass storage devices. The logical mass storage devices (or logical volumes) can be larger in capacity than the capacity of any one of the underlying physical mass storage devices. For example, given two 100GB drives, a 200GB logical volume can be created. However, a 150GB and a 50GB logical volume could also be created. Any combination of logical volumes equal to or less than the total capacity (200GB in this example) is possible. The choices are limited only by your organization's needs. This makes it possible for a system administrator to treat all storage as being part of a single pool, available for use in any amount. In addition, drives can be added to the pool at a later time, making it a straightforward process to stay ahead of your users' demand for storage.

Commands:
10.7. Disk Space and Memory Requirements Red Hat Enterprise Linux, like most current operating systems, uses disk partitions . When you install Red Hat Enterprise Linux, you have to work with disk partitions. For more information about disk partitions, see Appendix A, An Introduction to Disk Partitions . The disk space used by Red Hat Enterprise Linux must be separate from the disk space used by other operating systems you might have installed on your system. Note For IBM Power Systems servers, at least three partitions ( / , swap and a PReP boot partition) must be dedicated to Red Hat Enterprise Linux. To install Red Hat Enterprise Linux you must have a minimum of 10 GB of space in either unpartitioned disk space or in partitions which can be deleted. For more information on partition and disk space recommendations, see the recommended partitioning sizes discussed in Section 13.15.4.4, "Recommended Partitioning Scheme" . Red Hat Enterprise Linux requires minimum the following amount of RAM: Installation type Minimum required RAM Local media installation (USB, DVD) 1,280 MiB NFS network installation 1,280 MiB HTTP, HTTPS, or FTP network installation 1,664 MiB Installing Red Hat Enterprise Linux using a Kickstart file has the same minimum RAM requirements as a manual installation. However, if you use a Kickstart file that runs commands which require additional memory or write data to the RAM disk, additional RAM might be necessary. For more information about the minimum requirements and technology limits of Red Hat Enterprise Linux 7, see the Red Hat Enterprise Linux technology capabilities and limits article on the Red Hat Customer Portal.

Commands:
Chapter 16. Managing container storage interface (CSI) component placements Each cluster consists of a number of dedicated nodes such as infra and storage nodes. However, an infra node with a custom taint will not be able to use OpenShift Data Foundation Persistent Volume Claims (PVCs) on the node. So, if you want to use such nodes, you can set tolerations to bring up csi-plugins on the nodes. Procedure Edit the configmap to add the toleration for the custom taint. Remember to save before exiting the editor. Display the configmap to check the added toleration. Example output of the added toleration for the taint, nodetype=infra:NoSchedule : Note Ensure that all non-string values in the Tolerations value field has double quotation marks. For example, the values true which is of type boolean, and 1 which is of type int must be input as "true" and "1". Restart the rook-ceph-operator if the csi-cephfsplugin- * and csi-rbdplugin- * pods fail to come up on their own on the infra nodes. Example : Verification step Verify that the csi-cephfsplugin- * and csi-rbdplugin- * pods are running on the infra nodes.

Commands:
oc edit configmap rook-ceph-operator-config -n openshift-storage
oc get configmap rook-ceph-operator-config -n openshift-storage -o yaml
apiVersion: v1 data: [...] CSI_PLUGIN_TOLERATIONS: | - key: nodetype operator: Equal value: infra effect: NoSchedule - key: node.ocs.openshift.io/storage operator: Equal value: "true" effect: NoSchedule [...] kind: ConfigMap metadata: [...]
oc delete -n openshift-storage pod <name of the rook_ceph_operator pod>
oc delete -n openshift-storage pod rook-ceph-operator-5446f9b95b-jrn2j pod "rook-ceph-operator-5446f9b95b-jrn2j" deleted
Chapter 9. Learning resources on the Red Hat Hybrid Cloud Console There are several ways to learn about using services in the Red Hat Hybrid Cloud Console: The Learning resources link on the left menu of most pages in the console can contain the following resources: In-depth documentation Interactive quick starts to help you complete specific tasks Learning paths to help you get a better understanding of the service or product set The Resource Center , accessed from the light bulb icon at the bottom right of the console, can contain the following resources: Updates and announcements about new features Webinars and blogs Service alerts Product tours Videos Resources in Learning Resources and the Resource Center change based on the collection of services that you are viewing. Resources are frequently added and removed to keep the content as relevant as possible. 9.1. Bookmarking learning resources Bookmark Hybrid Cloud Console learning resources that you might want to refer to later. Procedure On the Hybrid Cloud Console home page, click Add widgets and then drag the Bookmarked learning resources widget onto the page. Your changes are saved automatically. In the Bookmarked learning resources widget, click View all learning resources . Click the bookmark icon in any learning resource. On the Hybrid Cloud Console home page, scroll down to Bookmarked learning resources . Your bookmarked learning resources are listed. Additional resources For more information about adding widgets, see Cusomizing your Hybrid Cloud Console home page . 9.2. Using Hybrid Cloud Console API documentation You can use Hybrid Cloud Console API documentation to help you develop Red Hat services that are part of the Hybrid Cloud Console. You can easily find API code for the Hybrid Cloud Console services that you use. The documentation provides examples of each API in different coding languages. The API documentation is available in two places: The API Catalog and Documentation page on the Red Hat Developer web site: This is a new location for the API documentation that you can access without a Red Hat account. The API documentation page on the Red Hat Hybrid Cloud Console: The documentation available through this page has some useful features such as versioning that are not yet available on the Red Hat Developer web site. Procedure Use one of the following methods to view the Hybrid Cloud Console API documentation: View the API documentation on the Red Hat Developer web site. To view the API documentation on the Red Hat Hybrid Cloud Console , select Help ( ? icon) > API Documentation . The API documentation page opens. Perform any of the following tasks: To view the API documentation for an service, click the service name link. To download the API documentation for a specific service, click the Download icon on the service row (console only). To download the API documentation for more than one service, select the services then click Download selected (console only).

Commands:
8.148. netlabel_tools 8.148.1. RHBA-2014:0535 - netlabel_tools bug fix update Updated netlabel_tools packages that fix three bugs are now available for Red Hat Enterprise Linux 6. NetLabel is a kernel subsystem which implements explicit packet labeling protocols such as CIPSO. Packet labeling is used in secure networks to mark packets with the security attributes of the data they contain. This package provides the necessary user space tools to query and configure the kernel subsystem. Bug Fixes BZ# 918763 Prior to this update, netlabelctl, the NetLabel management tool, incorrectly handled multi-part netlink messages that limited the number of static labels displayed. Consequently, running the "netlabelctl unlbl list -p" command did not provide the correct output when a large number of static labels were configured. This bug has been fixed, and netlabelctl now works correctly and lists all the configured static labels as expected. BZ# 1000177 Previously, netlabelctl did not allocate enough buffer space for large configuration messages from the kernel. In addition, netlabelctl could not adjust the buffer size in the cases where the buffer was not large enough. As a consequence, a large number of CIPSO level and category translations could not be used. With this update, the default message buffer has been increased, and the buffer is now increased dynamically as necessary. As a result, a large number of CIPSO level and category translations can be used as expected in this scenario. BZ# 1098082 Prior to this update, the file with the licence text was not included in the binary packages. This update adds the license text in the packages. Users of netlabel_tools are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 37. MetadataTemplate schema reference Used in: BuildConfigTemplate , DeploymentTemplate , InternalServiceTemplate , PodDisruptionBudgetTemplate , PodTemplate , ResourceTemplate , StatefulSetTemplate Full list of MetadataTemplate schema properties Labels and Annotations are used to identify and organize resources, and are configured in the metadata property. For example: # ... template: pod: metadata: labels: label1: value1 label2: value2 annotations: annotation1: value1 annotation2: value2 # ... The labels and annotations fields can contain any labels or annotations that do not contain the reserved string strimzi.io . Labels and annotations containing strimzi.io are used internally by Streams for Apache Kafka and cannot be configured. 37.1. MetadataTemplate schema properties Property Property type Description labels map Labels added to the OpenShift resource. annotations map Annotations added to the OpenShift resource.

Commands:
template: pod: metadata: labels: label1: value1 label2: value2 annotations: annotation1: value1 annotation2: value2
Chapter 1. Scheduling fernet key rotation For security purposes, the fernet keys in your Red Hat OpenStack Services on OpenShift (RHOSO) environment are automatically rotated. To meet the unique security requirements of your environment, you can modify the frequency with which fernet key rotations occur as well as the number of old decryption keys kept after each rotation. 1.1. Updating fernet key rotation frequency As of Red Hat OpenStack Services on OpenShift (RHOSO), you can update the frequency with which the Identity service (keystone) rotates its fernet keys. Procedure Edit the OpenStackControlPlane custom resource (CR) for editing: Under the properties field under the Identity service (keystone) configuration, add the following: Replace <active_keys> with the number of keys to keep active. The default is 5 . Replace <days> with the frequency with which to rotate your fernet keys.

Commands:
edit openstackcontrolplane openstack-control-plane
fernetMaxActiveKeys: default: <active_keys> description: FernetMaxActiveKeys - Maximum number of fernet token keys after rotation type: int fernetRotationDays: default: <days>
5.157. libssh2 5.157.1. RHBA-2012:1048 - libssh2 bug fix update Updated libssh2 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libssh2 packages provide a library that implements the SSH2 protocol. Bug Fix BZ# 834211 Previously, libssh2 incorrectly returned the LIBSSH2_ERROR_EAGAIN error code when operating in blocking mode. The error code is used by libssh2 internally to initiate a blocking operation on a socket. The error code was, however, not properly cleared on success and leaked through the public API of libssh2. An upstream patch has been applied to clear the error code prior to initiating the blocking operation, and libssh2 no longer returns LIBSSH2_ERROR_EAGAIN when operating in blocking mode. All users of libssh2 are advised to upgrade to these updated packages, which fix this bug. After installing these updated packages, all running applications using libssh2 have to be restarted for this update to take effect.

Commands:
Part II. IBM Power Systems - Installation and Booting This part of the Red Hat Enterprise Linux Installation Guide includes information about installation and basic post-installation troubleshooting for IBM Power Systems servers. IBM Power Systems servers include IBM PowerLinux servers and POWER7, POWER8, and POWER9 Power Systems servers running Linux. For advanced installation options, see Part IV, "Advanced Installation Options" . Important releases of Red Hat Enterprise Linux supported 32-bit and 64-bit Power Systems servers ( ppc and ppc64 , respectively). Red Hat Enterprise Linux 7 supports only 64-bit Power Systems servers ( ppc64 ).

Commands:
2.5. NetworkManager Tools Table 2.1. A Summary of NetworkManager Tools and Applications Application or Tool Description nmcli A command-line tool which enables users and scripts to interact with NetworkManager . Note that nmcli can be used on systems without a GUI such as servers to control all aspects of NetworkManager . It has the same functionality as GUI tools. nmtui A simple curses-based text user interface (TUI) for NetworkManager nm-connection-editor A graphical user interface tool for certain tasks not yet handled by the control-center utility such as configuring bonds and teaming connections. You can add, remove, and modify network connections stored by NetworkManager . To start it, enter nm-connection-editor in a terminal: control-center A graphical user interface tool provided by the GNOME Shell, available for desktop users. It incorporates a Network settings tool. To start it, press the Super key to enter the Activities Overview, type Network and then press Enter . The Network settings tool appears. network connection icon A graphical user interface tool provided by the GNOME Shell representing network connection states as reported by NetworkManager . The icon has multiple states that serve as visual indicators for the type of connection you are currently using.

Commands:
~]USD nm-connection-editor
Chapter 31. Real-Time Kernel A race condition that prevented tasks from being scheduled properly has been fixed Previously, preemption was enabled too early after a context switch. If a task was migrated to another CPU after a context switch, a mismatch between CPU and runqueue during load balancing sometimes occurred. Consequently, a runnable task on an idle CPU failed to run, and the operating system became unresponsive. This update disables preemption in the schedule_tail() function. As a result, CPU migration during post-schedule processing no longer occurs, which prevents the above mismatch. The operating system no longer hangs due to this bug. (BZ# 1608672 , BZ#1541534)

Commands: