mtpti5iD/redhat-docs_dataset huggingface dataset:
F.2.2. The Boot Loader F.2.2.1. The GRUB boot loader for x86 systems The system loads GRUB into memory, as directed by either a first-stage bootloader in the case of systems equipped with BIOS, or read directly from an EFI System Partition in the case of systems equipped with UEFI. GRUB has the advantage of being able to read ext2, ext3, and ext4 [17] partitions and load its configuration file - /boot/grub/grub.conf (for BIOS) or /boot/efi/EFI/redhat/grub.conf (for UEFI) - at boot time. Refer to Section E.8, "GRUB Menu Configuration File" for information on how to edit this file. Important The GRUB bootloader in Red Hat Enterprise Linux 6.9 supports ext2, ext3, and ext4 file systems. It does not support other file systems such as VFAT, Btrfs or XFS. Furthermore, GRUB does not support LVM. Once the second stage boot loader is in memory, it presents the user with a graphical screen showing the different operating systems or kernels it has been configured to boot (when you update the kernel, the boot loader configuration file is updated automatically). On this screen a user can use the arrow keys to choose which operating system or kernel they wish to boot and press Enter . If no key is pressed, the boot loader loads the default selection after a configurable period of time has passed. Once the second stage boot loader has determined which kernel to boot, it locates the corresponding kernel binary in the /boot/ directory. The kernel binary is named using the following format - /boot/vmlinuz- <kernel-version> file (where <kernel-version> corresponds to the kernel version specified in the boot loader's settings). For instructions on using the boot loader to supply command line arguments to the kernel, refer to Appendix E, The GRUB Boot Loader . For information on changing the runlevel at the boot loader prompt, refer Section E.9, "Changing Runlevels at Boot Time" . The boot loader then places one or more appropriate initramfs images into memory. The initramfs is used by the kernel to load drivers and modules necessary to boot the system. This is particularly important if SCSI hard drives are present or if the systems use the ext3 or ext4 file system. Once the kernel and the initramfs image(s) are loaded into memory, the boot loader hands control of the boot process to the kernel. For a more detailed overview of the GRUB boot loader, refer to Appendix E, The GRUB Boot Loader . [17] GRUB reads ext3 and ext4 file systems as ext2, disregarding the journal file.

Commands:
Chapter 1. Upgrading Red Hat build of Keycloak This guide describes how to upgrade Red Hat build of Keycloak from version 24.0.x to version 26.0.10. Use the following procedures in this order: Review the release-specific changes from the version of Red Hat build of Keycloak. Upgrade the Red Hat build of Keycloak server. Upgrade the Red Hat build of Keycloak adapters. Upgrade the Red Hat build of Keycloak Admin Client. For Red Hat Single Sign-On 7.6 customers, use the Migration Guide instead of this guide.

Commands:
7.149. oprofile 7.149.1. RHBA-2015:1367 - oprofile bug fix and enhancement update Updated oprofile packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. OProfile is a low-overhead, system-wide profiler that uses the performance monitoring hardware on the processor to retrieve information about the kernel and executables on the system. Bug Fixes BZ# 1180513 Previously, when profiling performance of Java just-in-time (JIT) compiled code with static huge pages enabled, OProfile's operf command recorded a large number of event samples to anonymous memory (in anon_hugepage) instead of to the appropriate Java method. With this update, operf recognizes the static huge page identifiers and correctly maps samples to Java methods when using statically allocated huge pages. BZ# 1199469 To properly select an event, some new Intel processors require not only the base event number but also additional bits to be set in the unit mask. Previously, the additional bits in the unit mask remained unset, thus being incorrectly set to zero. As a consequence, performance monitoring hardware was not measuring the desired event, and the operf utility returned zero for the LLC_REFS and LLC_MISSES events on the 2nd, 3rd, and 4th generation Intel Core and Intel Xeon processors. With this update, OProfile code has been fixed to set the unit mask bits as required. As a result, performance events on Intel processors that require non-zero unit masks now work as expected. BZ# 1200808 Previously, when a name of the default unit mask for an event was longer than 11 characters, OProfile truncated the name to 11 characters. Consequently, when the truncated unit mask name was used, OProfile could not find the unit mask and returned an error message. With this update, OProfile handles long unit mask names correctly, and the described problem no longer occurs. BZ# 1202727 The operf, ocount, and opjitconv utilities set the POSIXLY_CORRECT enviroment variable for their internal purposes. Prior to this update, OProfile did not return this environment variable to its state, thus potentially affecting profiled tasks. Consequently, profiled tasks that behaved differently when the variable was set, such as rpm rebuilds, did not work as expected. This bug has been fixed, and the OProfile use of POSIXLY_CORRECT now does not affect profiled tasks. Enhancement BZ# 1144235 The OProfile profiler tool now includes support for Intel Silvermont events for the Intel Atom C2XXX and Intel Atom E38XX systems on a chip (SoC). This allows users to investigate Intel Silvermont-specific performance issues using OProfile. Users of oprofile are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
Chapter 10. Compiler and Tools 10.1. GCC Toolchain In Red Hat Enterprise Linux 7, the gcc toolchain is based on the gcc-4.8.x release series, and includes numerous enhancements and bug fixes relative to the Red Hat Enterprise Linux 6 equivalent. Similarly, Red Hat Enterprise Linux 7 includes binutils-2.23.52.x . These versions correspond to the equivalent tools in Red Hat Developer Toolset 2.1; a detailed comparison of Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 gcc and binutils versions can be seen here: https://access.redhat.com/site/documentation/en-US/Red_Hat_Developer_Toolset/2/html/User_Guide/index.html Notable highlights of the Red Hat Enterprise Linux 7 toolchain are the following: As a Technology Preview, The GNU Compiler Collection ( GCC ) implements support for on-line patching of multi-threaded code for Linux on System z binaries. Selecting specific functions for hot-patching is enabled by using a "function attribute" and hot-patching for all functions can be enabled using the -mhotpatch command-line option. Enabling hot-patching has a negative impact on software size and performance. It is therefore recommended to use hot-patching for specific functions instead of enabling hot patch support for all functions. Experimental support for building applications compliant with C++11 (including full C++11 language support) and some experimental support for C11 features; Improved support for programming parallel applications, including OpenMP v3.1, C++11 Types and GCC Built-ins for Atomic Memory Access and experimental support for transactional memory (including Intel RTM/HLE intrinsics, built-ins, and code generation); A new local register allocator (LRA), improving code performance; DWARF4 is now used as the default debug format; A variety of new architecture-specific options; Support for AMD family 15h and 16h processors; Link-time optimization support; Enhanced warnings and diagnostics; A variety of new Fortran features.

Commands:
Chapter 6. Additional Resources This chapter provides references to other relevant sources of information about Red Hat Software Collections 3.2 and Red Hat Enterprise Linux. 6.1. Red Hat Product Documentation The following documents are directly or indirectly relevant to this book: Red Hat Software Collections 3.2 Packaging Guide - The Packaging Guide for Red Hat Software Collections explains the concept of Software Collections, documents the scl utility, and provides a detailed explanation of how to create a custom Software Collection or extend an existing one. Red Hat Developer Toolset 8.0 Release Notes - The Release Notes for Red Hat Developer Toolset document known problems, possible issues, changes, and other important information about this Software Collection. Red Hat Developer Toolset 8.0 User Guide - The User Guide for Red Hat Developer Toolset contains more information about installing and using this Software Collection. Using Red Hat Software Collections Container Images - This book provides information on how to use container images based on Red Hat Software Collections. The available container images include applications, daemons, databases, as well as the Red Hat Developer Toolset container images. The images can be run on Red Hat Enterprise Linux 7 Server and Red Hat Enterprise Linux Atomic Host. Getting Started with Containers - This guide contains a comprehensive overview of information about building and using container images on Red Hat Enterprise Linux 7 and Red Hat Enterprise Linux Atomic Host. Using and Configuring Red Hat Subscription Manager - The Using and Configuring Red Hat Subscription Manager book provides detailed information on how to register Red Hat Enterprise Linux systems, manage subscriptions, and view notifications for the registered systems. Red Hat Enterprise Linux 6 Deployment Guide - The Deployment Guide for Red Hat Enterprise Linux 6 provides relevant information regarding the deployment, configuration, and administration of this system. Red Hat Enterprise Linux 7 System Administrator's Guide - The System Administrator's Guide for Red Hat Enterprise Linux 7 provides information on deployment, configuration, and administration of this system. 6.2. Red Hat Developers Red Hat Developer Program - The Red Hat Developers community portal. Overview of Red Hat Software Collections on Red Hat Developers - The Red Hat Developers portal provides a number of tutorials to get you started with developing code using different development technologies. This includes the Node.js, Perl, PHP, Python, and Ruby Software Collections. Red Hat Developer Blog - The Red Hat Developer Blog contains up-to-date information, best practices, opinion, product and program announcements as well as pointers to sample code and other resources for those who are designing and developing applications based on Red Hat technologies.

Commands:
8.177. php 8.177.1. RHBA-2014:1465 - php bug fix update Updated php packages that fix several bugs are now available for Red Hat Enterprise Linux 6. PHP is an HTML-embedded scripting language commonly used with the Apache HTTP Server. Bug Fixes BZ# 1054953 Previously, an incorrect parameter type was used in internal calls. As a consequence, the execution of the php-mysql module requests did not work correctly on big-endian machines, such as 64-bit PowerPC and IBM System z. The parameter has been changed to match the expected type. As a result, php-mysql requests produce the expected output. BZ# 1069167 Prior to this update, a mysql link could be closed even when prepared statements still existed. Consequently, executing those statements caused a segmentation fault. With this update, a mysql link is only closed when all statements are freed, and the statements can be executed as expected. BZ# 1045019 Previously, the host HTTP header was missing from soap calls. As a consequence, HTTP requests were not RFC2616 compliant. This update adds the HTTP header to the soap calls. As a result, the requests are now RFC2616 compliant and can go through a proxy server. BZ# 1053982 Previously, the php packages contained a bug concerning the oci_lob_load() function. As a consequence, compiling the php OCI8 module failed. The underlying source code has been modified, and the OCI8 extension can now be compiled correctly. BZ# 954027 Prior to this update, dependency on the Spl extension for the Session extension was missing from the php packages. Consequently, Spl was uninitialized before Session, which made the autoload feature unavailable. With this update, Session requires Spl and the autoload feature is now available as expected. BZ# 953786 Previously, the php packages contained an inconsistency in the behavior of a static call in a non-static method. Consequently, a call from the context's class (name, static or self) inside a non-static method results in a static-call. This update restores the standard behavior. As a result, a call inside a non-static method is now non-static, and the called method inherits the USDthis variable. Users of php are advised to upgrade to these updated packages, which fix these bugs. After installing the updated packages, the httpd daemon must be restarted for the update to take effect.

Commands:
Chapter 66. request This chapter describes the commands under the request command. 66.1. request token authorize Authorize a request token Usage: Table 66.1. Optional Arguments Value Summary -h, --help Show this help message and exit --request-key <request-key> Request token to authorize (id only) (required) --role <role> Roles to authorize (name or id) (repeat option to set multiple values) (required) Table 66.2. Output Formatters Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 66.3. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 66.4. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 66.5. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show. 66.2. request token create Create a request token Usage: Table 66.6. Optional Arguments Value Summary -h, --help Show this help message and exit --consumer-key <consumer-key> Consumer key (required) --consumer-secret <consumer-secret> Consumer secret (required) --project <project> Project that consumer wants to access (name or id) (required) --domain <domain> Domain owning <project> (name or id) Table 66.7. Output Formatters Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 66.8. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 66.9. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 66.10. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack request token authorize [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --request-key <request-key> --role <role>
openstack request token create [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --consumer-key <consumer-key> --consumer-secret <consumer-secret> --project <project> [--domain <domain>]
3.6. Escaped Literal Syntax Rather than relying on implicit conversion, data type values may be expressed directly in SQL using escape syntax to define the type. Ensure the string value you supply matches the expected format exactly or an exception will occur. Table 3.5. Escaped Literal Syntax Data type Escaped Syntax Standard Literal BOOLEAN {b 'true'} TRUE DATE {d 'yyyy-mm-dd'} DATE 'yyyy-mm-dd' TIME {t 'hh-mm-ss'} TIME 'hh-mm-ss' TIMESTAMP {ts 'yyyy-mm-dd hh:mm:ss.[fff...]'} TIMESTAMP 'yyyy-mm-dd[ hh:mm:ss.[fff...]]'

Commands:
4.2.3. Upstart In Red Hat Enterprise Linux 6, init from the sysvinit package has been replaced with Upstart , an event-based init system. This system handles the starting of tasks and services during boot, stopping them during shutdown and supervising them while the system is running. For more information on Upstart itself, refer to the init(8) man page. Processes are known to Upstart as jobs and are defined by files in the /etc/init directory. Upstart is very well documented using man pages. Command overview is in init(8) and job syntax is described in init(5) . Upstart provides the following behavioral changes in Red Hat Enterprise Linux 6: The /etc/inittab file is deprecated, and is now used only for setting up the default runlevel using the initdefault line. Other configuration is done using upstart jobs in the /etc/init directory. The number of active tty consoles is now set by the ACTIVE_CONSOLES variable in /etc/sysconfig/init , which is read by the /etc/init/start-ttys.conf job. The default value is ACTIVE_CONSOLES=/dev/tty[1-6] , which starts a getty on tty1 through tty6. A serial getty is still automatically configured if the serial console is the primary system console. In prior releases, this was done by kudzu , which would edit /etc/inittab . In Red Hat Enterprise Linux 6, configuration of the primary serial console is handled by /etc/init/serial.conf . To configure a getty running on a non-default serial console, you must now write an Upstart job instead of editing /etc/inittab . For example, if a getty on ttyS1 is desired, the following job file ( /etc/init/serial-ttyS1.conf ) would work: As in prior releases, ttyS1 is required in /etc/securetty if you wish to allow root logins on this getty. Because of the move to Upstart, using /etc/shutdown.allow for defining who can shut the machine down is no longer supported.

Commands:
This service maintains a getty on /dev/ttyS1. start on stopped rc RUNLEVEL=[2345] stop on starting runlevel [016] respawn exec /sbin/agetty /dev/ttyS1 115200 vt100-nav
17.3. Callable and CDI Where DistributedCallable cannot be implemented or is not appropriate, and a reference to input cache used in DistributedExecutorService is still required, there is an option to inject the input cache by CDI mechanism. When the Callable task arrives at a Red Hat JBoss Data Grid executing node, JBoss Data Grid's CDI mechanism provides an appropriate cache reference, and injects it to the executing Callable . To use the JBoss Data Grid CDI with Callable : Declare a Cache field in Callable and annotate it with org.infinispan.cdi.Input Include the mandatory @Inject annotation. Example 17.2. Using Callable and the CDI Report a bug

Commands:
public class CallableWithInjectedCache implements Callable<Integer>, Serializable { @Inject @Input private Cache<String, String> cache; @Override public Integer call() throws Exception { //use injected cache reference return 1; } }
5.4.14.2. Extending a Mirrored Volume As of the Red Hat Enterprise Linux 6.3 release, it is possible to grow mirrored logical volumes with the lvextend command without performing a synchronization of the new mirror regions. If you specify the --nosync option when you create a mirrored logical volume with the lvcreate command, the mirror regions are not synchronized when the mirror is created, as described in Section 5.4.3, "Creating Mirrored Volumes" . If you later extend a mirror that you have created with the --nosync option, the mirror extensions are not synchronized at that time, either. You can determine whether an existing logical volume was created with the --nosync option by using the lvs command to display the volume's attributes. A logical volume will have an attribute bit 1 of "M" if it is a mirrored volume that was created without an initial synchronization, and it will have an attribute bit 1 of "m" if it was created with initial synchronization. The following command displays the attributes of a mirrored logical volume named lv that was created without initial synchronization, showing attribute bit 1 as "M". Attribute bit 7 is "m", indicating a target type of mirror . For information on the meaning of the attribute bits, see Table 5.4, "lvs Display Fields" . If you grow this mirrored logical volume with the lvextend command, the mirror extension will not be resynchronized. If you created a mirrored logical volume without specifying the --nosync option of the lvcreate command, you can grow the logical volume without resynchronizing the mirror by specifying the --nosync option of the lvextend command. The following example extends a logical volume that was created without the --nosync option, indicated that the mirror was synchronized when it was created. This example, however, specifies that the mirror not be synchronized when the volume is extended. Note that the volume has an attribute of "m", but after executing the lvextend commmand with the --nosync option the volume has an attribute of "M". If a mirror is inactive, it will not automatically skip synchronization when you extend the mirror, even if you create the mirror with the --nosync option specified. Instead, you will be prompted whether to do a full resync of the extended portion of the logical volume. Note If a mirror is performing recovery, you cannot extend the mirrored logical volume if you created or extended the volume with the --nosync option specified. If you did not specify the --nosync option, however, you can extend the mirror while it is recovering.

Commands:
lvs vg LV VG Attr LSize Pool Origin Snap% Move Log Copy% Convert lv vg Mwi-a-m- 5.00g lv_mlog 100.00
lvs vg LV VG Attr LSize Pool Origin Snap% Move Log Copy% Convert lv vg mwi-a-m- 20.00m lv_mlog 100.00 lvextend -L +5G vg/lv --nosync Extending 2 mirror images. Extending logical volume lv to 5.02 GiB Logical volume lv successfully resized lvs vg LV VG Attr LSize Pool Origin Snap% Move Log Copy% Convert lv vg Mwi-a-m- 5.02g lv_mlog 100.00