mtpti5iD/redhat-docs_dataset huggingface dataset:
5.12. The multipathd Interactive Console and the multipathd Command The multipathd -k command is an interactive interface to the multipathd daemon. Executing this command brings up an interactive multipath console, from which you can issue a number of commands. After executing this command, you can enter help to get a list of available commands, you can enter an interactive command, or you can enter CTRL-D to quit. Note that you can issue any of the multipathd commands without entering interactive mode by using the following format. Some multipathd commands include a format option followed by a wildcard. You can display a list of available wildcards with the following command. The multipathd interactive console can be used to troubleshoot problems you may be having with your system. For example, the following command sequence displays the multipath configuration, including the defaults, before exiting the console. The following command sequence ensures that multipath has picked up any changes to the multipath.conf , Use the following command sequence to ensure that the path checker is working properly. As of Red Hat Enterprise Linux release 6.8, the multipathd command supports new format commands that show the status of multipath devices and paths in "raw" format versions. In raw format, no headers are printed and the fields are not padded to align the columns with the headers. Instead, the fields print exactly as specified in the format string. This output can then be more easily used for scripting. You can display the wildcards used in the format string with the multipathd show wildcards command. To following multipathd commands show the multipath devices that multipathd is monitoring, using a format string with multipath wildcards, in regular and raw format. To following multipathd commands show the paths that multipathd is monitoring, using a format string with multipath wildcards, in regular and raw format. The following commands show the difference between the non-raw and raw formats for the multipathd show maps . Note that in raw format there are no headers and only a single space between the columns.

Commands:
multipathd command argument
multipathd show wildcards
multipathd -k > > show config > > CTRL-D
multipathd -k > > reconfigure > > CTRL-D
multipathd -k > > show paths > > CTRL-D
list|show maps|multipaths format USDformat list|show maps|multipaths raw format USDformat
list|show paths format USDformat list|show paths raw format USDformat
multipathd show maps format "%n %w %d %s" name uuid sysfs vend/prod/rev mpathc 360a98000324669436c2b45666c567942 dm-0 NETAPP,LUN multipathd show maps raw format "%n %w %d %s" mpathc 360a98000324669436c2b45666c567942 dm-0 NETAPP,LUN
Chapter 15. Viewing log entries You can view log entries for Red Hat Fuse in the Logs tab. Prerequisite The Logs tab is available when the Java application includes the Log MBean. Procedure To view a list of the log entries, click the Log Entries tab. By default, the list shows log entries in ascending order. You can drill down to each log entry to view detailed information about the log entry. To filter the list of logs to show specific log types, click the Action Bar . You can filter the log entries section according to a text string or the logging level. To change the Fuse Console default settings: In the upper right corner of the Fuse Console, click the user icon and then click Preferences from the drop-down menu. To change the default sorting order, select Server Logs and then click the log entry link to drill down to details about the log entry, such as the bundle name, thread, and the full message text. Optionally, you can customize these settings for storing log messages: The number of log statements to keep in the Fuse Console (the default is 100). The global log level: INFO (the default), OFF, ERROR, WARN, and DEBUG. The child-level messages to include, such as hawtio-oauth and hawtio-core-utils . To reset the Fuse Console Logs settings to the default values, click Reset Reset settings .

Commands:
5.9. Using a Beta Release with UEFI Secure Boot Note This section only concerns Beta releases of Red Hat Enterprise Linux 7. The UEFI Secure Boot technology requires that the operating system kernel must be signed with a recognized private key in order to be able to boot. In every beta release of Red Hat Enterprise Linux 7, the kernel is signed with a Red Hat Beta-specific private key, which is different from the more common Red Hat key used to sign kernels in a General Availability (non-Beta) releases. The Beta private key will likely not be recognized by your hardware, which means that any Beta release of Red Hat Enterprise Linux 7 will not be able to boot. In order to use a Beta release with UEFI Secure Boot enabled, you need to add the Red Hat Beta public key to your system using the Machine Owner Key (MOK) facility. The procedure to add the Red Hat Beta key to your system is below. Procedure 5.1. Adding a Custom Private Key for UEFI Secure Boot First, disable UEFI Secure Boot on the system, and install Red Hat Enterprise Linux 7 normally. After the installation finishes, the system will reboot. Secure Boot should still be disabled at this point. Reboot the system, log in and, if applicable, go through the Initial Setup screens as described in Chapter 30, Initial Setup . After finishing the first boot and going through Initial Setup, install the kernel-doc package if not installed already: This package provides a certificate file which contains the Red Hat CA public Beta key, located in /usr/share/doc/kernel-keys/ kernel-version /kernel-signing-ca.cer , where kernel-version is the kernel version string without the platform architecture suffix - for example, 3.10.0-686.el7 . Execute the following commands to enroll the public key into the system Machine Owner Key (MOK) list: Enter a password of your choosing when prompted. Note Make sure to remember the password. It is required to finish this procedure as well as to remove the imported key when it is no longer needed. Reboot the system again. During startup you will be prompted to confirm that you want to complete the pending key enrollment request. Select yes, and provide the password which you set earlier using the mokutil command in the step. The system will reboot again after you do so, and the key will be imported into the system firmware. You can turn on Secure Boot on this or any subsequent reboot. Warning Remove the imported Beta public key when you no longer need it. If you install a final (General Availability) release of Red Hat Enterprise Linux 7, or when you install a different operating system, you should remove the imported key. If you have only imported this public key, you can use the following command to reset the MOK: After the reboot, the firmware will prompt you for a confirmation and the password you created when importing the key. The key will be removed from the MOK after providing the correct password, and the system will revert to its original state.

Commands:
yum install kernel-doc
kr=USD(uname -r) # mokutil --import /usr/share/doc/kernel-keys/USD{kr%.USD(uname -p)}/kernel-signing-ca.cer
mokutil --reset
24.4.7. Monitoring Files and Directories with gamin Starting with Red Hat Enterprise Linux 6.8, the GLib system library uses gamin for monitoring of files and directories, and detection of their modifications on NFS file systems. By default, gamin uses polling for NFS file systems instead of inotify . Changes on other file systems are monitored by the inotify monitor that is implemented in GLib directly. As a subset of the File Alteration Monitor (FAM) system, gamin re-implements the FAM specification with the inotify Linux kernel subsystem. It is a GNOME project, but without any GNOME dependencies. Both glib2 and gamin packages are installed by default. By default, gamin works without the need of any configuration and it reverts to using polling for all paths matching /mnt/* or /media/* on Linux. Users can override or extend these settings by modifying the content of one of the following configuration files: /etc/gamin/gaminrc USDHOME/.gaminrc /etc/gamin/mandatory_gaminrc The configuration file accepts only the following commands: Commands accepted by the configuration file notify To express that kernel monitoring should be used for matching paths. poll To express that polling should be used for matching paths. fsset To control what notification method is used on a filesystem type. An example of such configuration file can be seen here: The three configuration files are loaded in this order: /etc/gamin/gaminrc ~/.gaminrc /etc/gamin/mandatory_gaminrc The /etc/gamin/mandatory_gaminrc configuration file allows the system administrator to override any potentially dangerous preferences set by the user. When checking a path to guess whether polling or kernel notification should be used, gamin checks first the user-provided rules in their declaration order within the configuration file and then check the predefined rules. This way the first declaration for /mnt/local* in the example override the default one for /mnt/* . If gamin is not configured to use the poll notifications on a particular path, it decides based on the file system the path is located on.

Commands:
configuration for gamin Can be used to override the default behaviour. notify filepath(s) : indicate to use kernel notification poll filepath(s) : indicate to use polling instead fsset fsname method poll_limit : indicate what method of notification for the file system kernel - use the kernel for notification poll - use polling for notification none - don't use any notification the poll_limit is the number of seconds that must pass before a resource is polled again. It is optional, and if it is not present the previous value will be used or the default. notify /mnt/local* /mnt/pictures* # use kernel notification on these paths poll /temp/* # use poll notification on these paths fsset nfs poll 10 # use polling on nfs mounts and poll once every 10 seconds
8.114. libica 8.114.1. RHBA-2014:1497 - libica bug fix and enhancement update Updated libica packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libica library contains a set of functions and utilities for accessing the IBM eServer Cryptographic Accelerator (ICA) hardware on IBM System z. Note The libica packages have been upgraded to upstream version 2.3.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1053842 ) Users of libica are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 2. Updating RPMs on an OSTree system Updating MicroShift on an rpm-ostree system such as Red Hat Enterprise Linux for Edge (RHEL for Edge) requires building a new RHEL for Edge image containing the new version of MicroShift and any associated optional RPMs. After you have the rpm-ostree image with MicroShift embedded, direct your system to boot into that operating system image. The procedures are the same for minor-version and patch updates. For example, use the same steps to upgrade from 4.17 to 4.18 or from 4.18.2 to 4.18.3. Note Downgrades other than automatic rollbacks are not supported. The following procedure is for updates only. 2.1. Applying updates on an rpm-ostree system To update MicroShift on an rpm-ostree system such as Red Hat Enterprise Linux for Edge (RHEL for Edge), embed the new version of MicroShift on a new operating system image. Back up and system rollback are automatic with this update type. You can also use this workflow to update applications running in the MicroShift cluster. Ensure compatibility between the application and the adjacent versions of MicroShift and RHEL for Edge before starting an update. Important The steps you use depends on how your existing deployment is set up. The following procedure outlines the general steps you can take, with links to the RHEL for Edge documentation. The RHEL for Edge documentation is your resource for specific details on building an updated operating system image. Prerequisites The system requirements for installing MicroShift have been met. You have root user access to the host. The version of MicroShift you have is compatible with the RHEL for Edge image you are preparing to use. Important You cannot downgrade MicroShift with this process. Downgrades other than automatic rollbacks are not supported. Procedure Create an image builder configuration file for adding the rhocp-4.18 RPM repository source required to pull MicroShift RPMs by running the following command: USD cat > rhocp-4.18.toml <<EOF id = "rhocp-4.18" name = "Red Hat OpenShift Container Platform 4.18 for RHEL 9" type = "yum-baseurl" url = "https://cdn.redhat.com/content/dist/layered/rhel9/USD(uname -m)/rhocp/4.18/os" check_gpg = true check_ssl = true system = false rhsm = true EOF Add the update RPM source to the image builder by running the following command: USD sudo composer-cli sources add rhocp-4.18.toml Build a new image of RHEL for Edge that contains the new version of MicroShift. To determine the steps required, use the following documentation: Building a RHEL for Edge commit update Update the host to use the new image of RHEL for Edge. To determine the steps required, use the following documentation: Deploying RHEL for Edge image updates Reboot the host to apply updates by running the following command: USD sudo systemctl reboot

Commands:
cat > rhocp-4.18.toml <<EOF id = "rhocp-4.18" name = "Red Hat OpenShift Container Platform 4.18 for RHEL 9" type = "yum-baseurl" url = "https://cdn.redhat.com/content/dist/layered/rhel9/USD(uname -m)/rhocp/4.18/os" check_gpg = true check_ssl = true system = false rhsm = true EOF
sudo composer-cli sources add rhocp-4.18.toml
sudo systemctl reboot
Chapter 40. ResourceTemplate schema reference Used in: CruiseControlTemplate , EntityOperatorTemplate , JmxTransTemplate , KafkaBridgeTemplate , KafkaClusterTemplate , KafkaConnectTemplate , KafkaExporterTemplate , KafkaMirrorMakerTemplate , KafkaNodePoolTemplate , KafkaUserTemplate , ZookeeperClusterTemplate Property Description metadata Metadata applied to the resource. MetadataTemplate

Commands:
Preface In this guide, the terms upgrade, update, and migrate have the following meanings: Upgrading The process of advancing your Satellite Server and Capsule Server installations from a y-stream release to the , for example Satellite 6.10 to Satellite 6.11. For more information, see Chapter 1, Upgrading Overview . Updating The process of advancing your Satellite Server and Capsule Server installations from a z-stream release to the , for example Satellite 6.11.0 to Satellite 6.11.1. Migrating The process of moving an existing Satellite installation to a new instance. For more information, see Chapter 5, Migrating Satellite to a New Red Hat Enterprise Linux System .

Commands:
12.6.2. Deleting a Storage Pool Using virt-manager This procedure demonstrates how to delete a storage pool. To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window. Figure 12.28. Stop Icon Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.

Commands:
7.91. java-1.8.0-openjdk 7.91.1. RHBA-2015:1427 - java-1.8.0-openjdk bug fix and enhancement update Updated java-1.8.0-openjdk packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The java-1.8.0-openjdk packages contain the latest version of the Open Java Development Kit (OpenJDK), OpenJDK 8. These packages provide a fully compliant implementation of Java SE 8. Bug Fixes BZ# 1154143 In Red Hat Enterprise Linux 6, the java-1.8.0-openjdk packages mistakenly included the SunEC provider, which does not function properly on this system. With this update, SunEC has been removed from the Red Hat Enterprise Linux 6 version of java-1.8.0-openjdk. BZ# 1155783 Prior to this update, the java-1.8.0-openjdk packages incorrectly provided "java-devel", which could lead to their inclusion in inappropriate builds. As a consequence, the "yum install java-devel" command in some cases installed java-1.8.0-openjdk-devel instead of the intended Java package. This update removes the providing configuration, and java-1.8.0-openjdk-devel can now be installed only by using the "yum install java-1.8.0-openjdk-devel" command. BZ# 1182011 Previously, the OpenJDK utility displayed characters containing the umlaut diacritical mark (such as a, o, or u) and the eszett character (ss) in PostScript output incorrectly. A patch with support for umlaut and eszett characters has been applied, and OpenJDK now displays these characters correctly. BZ# 1189853 The java-1.8.0-openjdk package for Red Hat Enterprise Linux 6 did not provide the "java" virtual package. Consequently, when a package needed to use OpenJDK 8, it was necessary to require "java-1.8.0-openjdk" instead of commonly used "java". Now, it is sufficient to require "java" as expected. BZ# 1212592 OpenJDK used a copy of the system time zone data. This could cause a difference between OpenJDK time and the system time. Now, OpenJDK uses the system time zone data, and OpenJDK time and the system time are the same. Enhancement BZ# 1210007 Red Hat now provides debug builds of OpenJDK in optional channels. With installed debug builds and JVM or JDK switched to using them, it is possible to do detailed HotSpot debugging. The debug builds can be used via alternatives or direct execution, in the same way as regular Java builds. Note that debug builds are not suitable for use in production, as they operate at a slower rate. Users of java-1.8.0-openjdk are advised to upgrade to these updated packages, which fix these bugs and add this enhancement. All running instances of OpenJDK Java must be restarted for the update to take effect.

Commands:
9.8. Time Zone Configuration Set your time zone by selecting the city closest to your computer's physical location. Click on the map to zoom in to a particular geographical region of the world. Specify a time zone even if you plan to use NTP (Network Time Protocol) to maintain the accuracy of the system clock. From here there are two ways for you to select your time zone: Using your mouse, click on the interactive map to select a specific city (represented by a yellow dot). A red X appears indicating your selection. You can also scroll through the list at the bottom of the screen to select your time zone. Using your mouse, click on a location to highlight your selection. If Red Hat Enterprise Linux is the only operating system on your computer, select System clock uses UTC . The system clock is a piece of hardware on your computer system. Red Hat Enterprise Linux uses the timezone setting to determine the offset between the local time and UTC on the system clock. This behavior is standard for systems that use UNIX, Linux, and similar operating systems. Click to proceed. Warning Do not enable the System clock uses UTC option if your machine also runs Microsoft Windows. Microsoft operating systems change the BIOS clock to match local time rather than UTC. This may cause unexpected behavior under Red Hat Enterprise Linux. Note To change your time zone configuration after you have completed the installation, use the Time and Date Properties Tool . Type the system-config-date command in a shell prompt to launch the Time and Date Properties Tool . If you are not root, it prompts you for the root password to continue.

Commands:
3.8. net_cls The net_cls subsystem tags network packets with a class identifier (classid) that allows the Linux traffic controller ( tc ) to identify packets originating from a particular cgroup. The traffic controller can be configured to assign different priorities to packets from different cgroups. net_cls.classid net_cls.classid contains a single value that indicates a traffic control handle . The value of classid read from the net_cls.classid file is presented in the decimal format while the value to be written to the file is expected in the hexadecimal format. For example, 0x100001 represents the handle conventionally written as 10:1 in the format used by the ip utility. In the net_cls.classid file, it would be represented by the number 1048577 . The format for these handles is: 0x AAAA BBBB , where AAAA is the major number in hexadecimal and BBBB is the minor number in hexadecimal. You can omit any leading zeroes; 0x10001 is the same as 0x00010001 , and represents 1:1 . The following is an example of setting a 10:1 handle in the net_cls.classid file: Refer to the man page for tc to learn how to configure the traffic controller to use the handles that the net_cls adds to network packets.

Commands:
~]# echo 0x100001 > /cgroup/net_cls/red/net_cls.classid ~]# cat /cgroup/net_cls/red/net_cls.classid 1048577
Chapter 5. Ceph Object Gateway and the IAM API The Ceph Object Gateway supports RESTful management of account users, roles, and associated policies. This REST API is served by the same HTTP endpoint as the Ceph Object Gateway S3 API . By default, only Account Root Users are authorized to use the IAM API, and can only see the resources under their own account. The account root user can use policies to delegate these permissions to other users or roles in the account. 5.1. Feature support The following tables describe the currently supported IAM actions. Table 5.1. Users Action Remarks CreateUser GetUser UpdateUser DeleteUser ListUsers CreateAccessKey UpdateAccessKey DeleteAccessKey ListAccessKeys PutUserPolicy GetUserPolicy DeleteUserPolicy ListUserPolicies AttachUserPolicies DetachUserPolicy ListAttachedUserPolicies Table 5.2. Groups Action Remarks CreateGroup GetGroup UpdateGroup DeleteGroup ListGroups AddUserToGroup RemoveUserFromGroup ListGroupsForUser PutGroupPolicy GetGroupPolicy DeleteGroupPolicy ListGroupPolicies AttachGroupPolicies DetachGroupPolicy ListAttachedGroupPolicies Table 5.3. Roles CreateRole GetRole UpdateRole UpdateAssumeRolePolicy DeleteRole ListRoles TagRole UntagRole ListRoleTags PutRolePolicy GetRolePolicy DeleteRolePolicy ListRolePolicies AttachRolePolicies DetachRolePolicy ListAttachedRolePolicies Table 5.4. OpenIDConnectProvider CreateOpenIDConnectProvider GetOpenIDConnectProvider DeleteOpenIDConnectProvider ListOpenIDConnectProviders 5.2. Managed policies The following managed policies are available for use with AttachGroupPolicy , AttachRolePolicy , and AttachUserPolicy . IAMFullAccess Arn arn:aws:iam::aws:policy/IAMFullAccess Version v2 (default) IAMReadOnlyAccess Arn arn:aws:iam::aws:policy/IAMReadOnlyAccess Version v4 (default) AmazonSNSFullAccess Arn arn:aws:iam::aws:policy/AmazonSNSFullAccess Version v1 (default) AmazonSNSReadOnlyAccess Arn arn:aws:iam::aws:policy/AmazonSNSReadOnlyAccess Version v1 (default) AmazonS3FullAccess Arn arn:aws:iam::aws:policy/AmazonS3FullAccess Version v2 (default) AmazonS3ReadOnlyAccess Arn arn:aws:iam::aws:policy/AmazonS3ReadOnlyAccess Version v3 (default)

Commands: