mtpti5iD/redhat-docs_dataset huggingface dataset:
4.126. libarchive 4.126.1. RHBA-2012:0464 - libarchive bug fix update Updated libarchive packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libarchive programming library can create and read several different streaming archive formats, including GNU tar and cpio. The library can also read ISO 9660 CD-ROM images. Bug Fix BZ# 782008 A bug introduced by fixing the CVE-2011-1777 security vulnerability broke functionality of the ISO 9660 CD-ROM image reader and prevented users from opening ISO 9660 images. A patch has been applied to restore full functionality. All users of libarchive are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.172. logrotate 5.172.1. RHBA-2012:1172 - logrotate bug fix update Updated logrotate packages that fix one bug are now available for Red Hat Enterprise Linux 6. The logrotate utility simplifies the administration of multiple log files, allowing the automatic rotation, compression, removal, and mailing of log files. Bug Fix BZ# 827570 Attempting to send a file to a specific e-mail address failed if the "mailfirst" and "delaycompress" options were used at the same time. This was because logrotate searched for a file with the "gz" suffix, however the file had not yet been compressed. The underlying source code has been modified, and logrotate correctly finds and sends the file under these circumstances. All users of logrotate are advised to upgrade to these updated packages, which fix this bug. 5.172.2. RHBA-2012:0786 - logrotate bug fix and enhancement update An updated logrotate package that fixes various bugs and adds one enhancement is now available for Red Hat Enterprise Linux 6. The logrotate utility simplifies the administration of multiple log files, allowing the automatic rotation, compression, removal, and mailing of log files. Bug Fixes BZ# 659705 Prior to this update, the AUTHORS section of the logrotate(8) manual page contained invalid contact information for maintainers. This update modifies the manual page and adds this information to ensure that the contact information of the current maintainers is correct. BZ# 659173 Prior to this update, the definition of the "size" parameter in the logrotate(8) manual page was misleading. This update modifies the manual page and this definition is now easier to understand. BZ# 659720 Prior to this update, the logrotate(8) manual page did not list all options that the logrotate utility actually recognizes. This update adds the missing options and the manual list contains now all available options. BZ# 674864 Prior to this update, the logrotate(8) manual page contained several misprints. This update modifies the logrotate(8) manual page and corrects the misprints. BZ# 736053 Prior to this update, logrotate did not check the configuration file for correctly matched brackets. As a consequence, system files could be wrongly removed. This update modifies logrotate so that brackets are detected and checked for correct matching. Now, configuration files without matching brackets are skipped. Enhancement BZ# 683622 Prior to this update, logrotate removed the Access Control Lists (ACL) flags, which are used to permit selected groups to access all logs, when rotating logs. As a consequence, selected groups could not access all logs. With this update, ACL support has been added to logrotate. All users of logrotate are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
5.13. Setting and Controlling IP sets using iptables The essential differences between firewalld and the iptables (and ip6tables ) services are: The iptables service stores configuration in /etc/sysconfig/iptables and /etc/sysconfig/ip6tables , while firewalld stores it in various XML files in /usr/lib/firewalld/ and /etc/firewalld/ . Note that the /etc/sysconfig/iptables file does not exist as firewalld is installed by default on Red Hat Enterprise Linux. With the iptables service , every single change means flushing all the old rules and reading all the new rules from /etc/sysconfig/iptables , while with firewalld there is no recreating of all the rules. Only the differences are applied. Consequently, firewalld can change the settings during runtime without existing connections being lost. Both use iptables tool to talk to the kernel packet filter. To use the iptables and ip6tables services instead of firewalld , first disable firewalld by running the following command as root : Then install the iptables-services package by entering the following command as root : The iptables-services package contains the iptables service and the ip6tables service. Then, to start the iptables and ip6tables services, enter the following commands as root : To enable the services to start on every system start, enter the following commands: The ipset utility is used to administer IP sets in the Linux kernel. An IP set is a framework for storing IP addresses, port numbers, IP and MAC address pairs, or IP address and port number pairs. The sets are indexed in such a way that very fast matching can be made against a set even when the sets are very large. IP sets enable simpler and more manageable configurations as well as providing performance advantages when using iptables . The iptables matches and targets referring to sets create references which protect the given sets in the kernel. A set cannot be destroyed while there is a single reference pointing to it. The use of ipset enables iptables commands, such as those below, to be replaced by a set: The set is created as follows: The set is then referenced in an iptables command as follows: If the set is used more than once a saving in configuration time is made. If the set contains many entries a saving in processing time is made.

Commands:
~]# systemctl disable firewalld ~]# systemctl stop firewalld
~]# yum install iptables-services
~]# systemctl start iptables ~]# systemctl start ip6tables
~]# systemctl enable iptables ~]# systemctl enable ip6tables
~]# iptables -A INPUT -s 10.0.0.0/8 -j DROP ~]# iptables -A INPUT -s 172.16.0.0/12 -j DROP ~]# iptables -A INPUT -s 192.168.0.0/16 -j DROP
~]# ipset create my-block-set hash:net ~]# ipset add my-block-set 10.0.0.0/8 ~]# ipset add my-block-set 172.16.0.0/12 ~]# ipset add my-block-set 192.168.0.0/16
~]# iptables -A INPUT -m set --set my-block-set src -j DROP
10.4.2. Booting into a Graphical Environment If you have installed the X Window System but are not seeing a graphical desktop environment once you log into your system, you can start the X Window System graphical interface using the command startx . Once you enter this command and press Enter , the graphical desktop environment is displayed. Note, however, that this is just a one-time fix and does not change the log in process for future log ins. To set up your system so that you can log in at a graphical login screen, you must edit one file, /etc/inittab , by changing just one number in the runlevel section. When you are finished, reboot the computer. The time you log in, you are presented with a graphical login prompt. Open a shell prompt. If you are in your user account, become root by typing the su command. Now, type the following to edit the file with gedit . The file /etc/inittab opens. Within the first screen, a section of the file which looks like the following appears: To change from a console to a graphical login, you should change the number in the line id:3:initdefault: from a 3 to a 5 . Warning Change only the number of the default runlevel from 3 to 5 . Your changed line should look like the following: When you are satisfied with your change, save and exit the file using the Ctrl + Q keys. A window appears and asks if you would like to save the changes. Click Save . The time you log in after rebooting your system, you are presented with a graphical login prompt.

Commands:
gedit /etc/inittab
Default runlevel. The runlevels used are: 0 - halt (Do NOT set initdefault to this) 1 - Single user mode 2 - Multiuser, without NFS (The same as 3, if you do not have networking) 3 - Full multiuser mode 4 - unused 5 - X11 6 - reboot (Do NOT set initdefault to this) # id:3:initdefault:
id:5:initdefault:
Chapter 7. Memory This chapter outlines the memory management capabilities of Red Hat Enterprise Linux 7. Section 7.1, "Considerations" discusses memory related factors that affect performance. Section 7.2, "Monitoring and Diagnosing Performance Problems" teaches you how to use Red Hat Enterprise Linux 7 tools to diagnose performance problems related to memory utilization or configuration details. Section 7.5, "Configuring System Memory Capacity" and Section 7.3, "Configuring HugeTLB Huge Pages" discuss the tools and strategies you can use to solve memory related performance problems in Red Hat Enterprise Linux 7. 7.1. Considerations By default, Red Hat Enterprise Linux 7 is optimized for moderate workloads. If your application or workload requires a large amount of memory, changing the way your system manages virtual memory may improve the performance of your application. 7.1.1. Larger Page Size Physical memory is managed in chunks called pages. On most architectures supported by Red Hat Enterprise Linux 7, the default size of a memory page is 4 KB. This default page size has proved to be suitable for general-purpose operating systems, such as Red Hat Enterprise Linux 7, which support many different kinds of workloads. However, specific applications can benefit from using larger page sizes in certain cases. For example, an application that works with a large and relatively fixed data set of hundreds of megabytes or even dozens of gigabytes can have performance issues when using 4 KB pages. Such data sets can require hundreds of thousands of 4 KB pages, which can lead to overhead in the operating system and the CPU. Red Hat Enterprise Linux 7 enables the use of larger page sizes for applications working with big data sets. Using larger page sizes can improve the performance of such applications. Two different large page features are available in Red Hat Enterprise Linux 7: the HugeTLB feature, also called static huge pages in this guide, and the Transparent Huge Page feature. 7.1.2. Translation Lookaside Buffer Size Reading address mappings from the page table is time-consuming and resource-expensive, so CPUs are built with a cache for recently-used addresses: the Translation Lookaside Buffer (TLB). However, the default TLB can only cache a certain number of address mappings. If a requested address mapping is not in the TLB (that is, the TLB is missed ), the system still needs to read the page table to determine the physical to virtual address mapping. Because of the relationship between application memory requirements and the size of pages used to cache address mappings, applications with large memory requirements are more likely to suffer performance degradation from TLB misses than applications with minimal memory requirements. It is therefore important to avoid TLB misses wherever possible. Both HugeTLB and Transparent Huge Page features allow applications to use pages larger than 4 KB. This allows addresses stored in the TLB to reference more memory, which reduces TLB misses and improves application performance.

Commands:
Chapter 5. Managing volume groups using the Web Console 5.1. Creating a volume group using the Web Console Log in to the Web Console. Click the hostname Storage . Click the + button beside Volume Groups . Figure 5.1. Volume Groups section The Create Volume Group window opens. Specify a Name for the volume group. Check the Disks to use for the volume group. Click Create . 5.2. Adding physical volumes to a volume group using the Web Console Follow these instructions to expand a volume group using the Web Console. Log in to the Web Console. Click the hostname Storage . Click the volume group. The Volume Group Overview page opens. Click the + button beside Physical Volumes . Figure 5.2. Physical Volumes The Add Disks window opens. Check the Disks you want to add to the volume group. Click Add . The capacity of the volume group is extended automatically. Now that you've added new storage to the volume group, you may want to grow your thin pool or grow your logical volume . 5.3. Renaming a volume group using the Web Console Follow these instructions to rename a volume group using the Web Console. Log in to the Web Console. Click the hostname Storage . Click the volume group. The Volume Group Overview page opens. Click Rename . Figure 5.3. Volume group summary The Rename Volume Group window opens. .. Specify a new Name . .. Click Rename . The volume group is renamed, and the change is propagated to all logical volumes in the volume group. This does not affect the naming of thin pools. 5.4. Deleting a volume group using the Web Console Follow these instructions to delete a volume group using the Web Console. Log in to the Web Console. Click the hostname Storage . Click the volume group. The Volume Group Overview page opens. In the Volume Group summary, click Delete . Figure 5.4. Volume group summary The confirmation window opens. Click Delete to confirm deletion.

Commands:
Chapter 1. The Red Hat hardware certification program overview The Red Hat Hardware Certification Program ensures the compatibility of your hardware, software, and cloud products on the OpenStack Platform . The program has three main elements: Test suite : Comprises tests for hardware or software undergoing certification. Red Hat Certification Ecosystem : Helps to explore and find certified products including Hardware, Software, Cloud and service providers. Support : A joint support relationship between you and Red Hat. 1.1. Getting support and giving feedback For any questions related to the Red Hat certification toolset, certification process, or procedure described in this documentation, refer to the KB Articles , Red Hat Customer Portal , and Red Hat Partner Connect . You can also open a support case to get support or submit feedback. To open a support case see, How do I open and manage a support case on the Customer Portal? Questions During Certification If you have any questions or responses about a specific certification, record them in the Comments section of the Dialog Tab of the certification entry. Warning Issues that can block a certification and might require resolution must be resolved through your Engineering Partner Manager or other engineering engagements. Additional resources For more information about the requirements and policies for Red Hat OpenStack bare metal hardware and Red Hat OpenShift Container Platform bare metal hardware certification , see Red Hat OpenStack Hardware Bare Metal Certification Policy Guide .

Commands:
Chapter 7. Managing orders Orders are created once a user successfully submits the request and provides any required validation. The approval process then governs the user's order status. 7.1. Approving or denying requests Once a user places an order it is created and available for review on the orders page. Groups assigned the Approval Approver role can then approve or deny orders. Detailed information is provided for each request, with information on the ordered product and its associated requester and project. A stage transcript is also provided. Denied requests require justification and the approver must enter a reason. To approve or deny a request: Navigate to Approval . Click the Requests tab and then click on a request to expand it to detailed view. Click Approve or Deny . Provide a Reason when denying a request. Click Submit . 7.2. Commenting on requests Comment on requests as an administrator or approver. Comments are captured by the system and visible at each stage of approval. To comment on a request: Navigate to Approval . Click the Requests tab and then click on a request. Click Comment . Add a comment and click Submit .

Commands:
2.11. SystemTap SystemTap is a tracing and probing tool that lets you monitor and analyze operating system activities, especially kernel activities, in fine detail. It provides information similar to the output of tools like top, ps, netstat, and iostat, but includes additional options for filtering and analyzing collected data. SystemTap provides a deeper, more precise analysis of system activities and application behavior to allow you to pinpoint system and application bottlenecks. For more detailed information about SystemTap, see the Red Hat Enterprise Linux 7 SystemTap Beginners Guide and the Red Hat Enterprise Linux 7 SystemTap Tapset Reference .

Commands:
Chapter 16. command This chapter describes the commands under the command command. 16.1. command list List recognized commands by group Usage: Table 16.1. Command arguments Value Summary -h, --help Show this help message and exit --group <group-keyword> Show commands filtered by a command group, for example: identity, volume, compute, image, network and other keywords Table 16.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated --sort-ascending Sort the column(s) in ascending order --sort-descending Sort the column(s) in descending order Table 16.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 16.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 16.5. Table formatter options 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 command list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--sort-ascending | --sort-descending] [--group <group-keyword>]
Chapter 4. The DM-Multipath Configuration File By default, DM-Multipath provides configuration values for the most common uses of multipathing. In addition, DM-Multipath includes support for the most common storage arrays that support DM-Multipath. The default configuration values and the supported devices can be found in the /usr/share/doc/device-mapper-multipath-0.4.5/multipath.conf.defaults file. Note The location and contents of the multipath.conf.defaults file may differ slightly from the example shown in this chapter depending on the release of RHEL 4 that you are running. You can override the default configuration values for DM-Multipath by editing the /etc/multipath.conf configuration file. If necessary, you can also add a storage array that is not supported by default to the configuration file. This chapter provides information on parsing and modifying the multipath.conf file. It contains sections on the following topics: Configuration file overview Configuration file blacklist Configuration file defaults Configuration file multipaths Configuration file devices In the multipath configuration file, you need to specify only the sections that you need for your configuration, or that you wish to change from the default values specified in the multipath.conf.defaults file. If there are sections of the file that are not relevant to your environment or for which you do not need to override the default values, you can leave them commented out, as they are in the initial file. The configuration file allows regular expression description syntax. An annotated version of the configuration file can be found in /usr/share/doc/device-mapper-multipathd-0.4.5/multipath.conf.annotated . 4.1. Configuration File Overview The multipath configuration file is divided into the following sections: devnode_blacklist Listing of specific devices that will not be considered for multipath. By default all devices are blacklisted. Usually the default devnode_blacklist section is commented out. defaults General default settings for DM-Multipath. multipaths Settings for the characteristics of individual multipath devices. These values overwrite what is specified in the defaults and devices sections of the configuration file. devices Settings for the individual storage controllers. These values overwrite what is specified in the defaults section of the configuration file. If you are using a storage array that is not supported by default, you may need to create a devices subsection for your array. When the system determines the attributes of a multipath device, first it checks the multipath settings, then the per devices settings, then the multipath system defaults.

Commands:
D.3. Sample Metadata The following shows an example of LVM volume group metadata for a volume group called myvg .

Commands:
Generated by LVM2: Tue Jan 30 16:28:15 2007 contents = "Text Format Volume Group" version = 1 description = "Created *before* executing 'lvextend -L+5G /dev/myvg/mylv /dev/sdc'" creation_host = "tng3-1" # Linux tng3-1 2.6.18-8.el5 #1 SMP Fri Jan 26 14:15:21 EST 2007 i686 creation_time = 1170196095 # Tue Jan 30 16:28:15 2007 myvg { id = "0zd3UT-wbYT-lDHq-lMPs-EjoE-0o18-wL28X4" seqno = 3 status = ["RESIZEABLE", "READ", "WRITE"] extent_size = 8192 # 4 Megabytes max_lv = 0 max_pv = 0 physical_volumes { pv0 { id = "ZBW5qW-dXF2-0bGw-ZCad-2RlV-phwu-1c1RFt" device = "/dev/sda" # Hint only status = ["ALLOCATABLE"] dev_size = 35964301 # 17.1491 Gigabytes pe_start = 384 pe_count = 4390 # 17.1484 Gigabytes } pv1 { id = "ZHEZJW-MR64-D3QM-Rv7V-Hxsa-zU24-wztY19" device = "/dev/sdb" # Hint only status = ["ALLOCATABLE"] dev_size = 35964301 # 17.1491 Gigabytes pe_start = 384 pe_count = 4390 # 17.1484 Gigabytes } pv2 { id = "wCoG4p-55Ui-9tbp-VTEA-jO6s-RAVx-UREW0G" device = "/dev/sdc" # Hint only status = ["ALLOCATABLE"] dev_size = 35964301 # 17.1491 Gigabytes pe_start = 384 pe_count = 4390 # 17.1484 Gigabytes } pv3 { id = "hGlUwi-zsBg-39FF-do88-pHxY-8XA2-9WKIiA" device = "/dev/sdd" # Hint only status = ["ALLOCATABLE"] dev_size = 35964301 # 17.1491 Gigabytes pe_start = 384 pe_count = 4390 # 17.1484 Gigabytes } } logical_volumes { mylv { id = "GhUYSF-qVM3-rzQo-a6D2-o0aV-LQet-Ur9OF9" status = ["READ", "WRITE", "VISIBLE"] segment_count = 2 segment1 { start_extent = 0 extent_count = 1280 # 5 Gigabytes type = "striped" stripe_count = 1 # linear stripes = [ "pv0", 0 ] } segment2 { start_extent = 1280 extent_count = 1280 # 5 Gigabytes type = "striped" stripe_count = 1 # linear stripes = [ "pv1", 0 ] } } } }