mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 16. Red Hat Enterprise Linux Atomic Host 7.6.2 16.1. Atomic Host OStree update : New Tree Version: 7.6.2 (hash: 50c320468370132958eeeffb90a23431a5bd1cc717aa68d969eb471d78879e66) Changes since Tree Version 7.6.1 (hash: cbdf1df91ffb370cad574ad2bfdcf5e9999629437e23e620055af0dbef2c0cae) 16.2. Extras Updated packages : WALinuxAgent-2.2.32-1.el7 buildah-1.5-2.gite94b4f9.el7 container-selinux-2.77-1.el7_6 containernetworking-plugins-0.7.4-1.el7 docker-1.13.1-90.git07f3374.el7 dpdk-18.11-2.el7_6 etcd-3.3.11-2.el7 libdnf-0.22.5-1.el7_6 oci-systemd-hook-0.1.18-3.git8787307.el7_6 podman-0.12.1.2-2.git9551f6b.el7 python-docker-py-1.10.6-8.el7_6 skopeo-0.1.31-8.gitb0b750d.el7 16.2.1. Container Images Updated : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) Red Hat Enterprise Linux 7.6 Container Image (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux 7.6 Container Image for aarch64 (rhel7.6, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Net-SNMP Container Image (rhel7/net-snmp) Red Hat Enterprise Linux Atomic OpenSCAP Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Support Tools Container Image (rhel7/support-tools) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc)

Commands:
Preface Red Hat OpenStack Platform (RHOSP) provides the foundation to build a private or public Infrastructure-as-a-Service (IaaS) cloud on top of Red Hat Enterprise Linux. It offers a massively scalable, fault-tolerant platform for the development of cloud-enabled workloads. With the Shared File Systems service (manila) with Ceph File System (CephFS) through NFS, you can use the same Ceph cluster that you use for block and object storage to provide file shares through the NFS protocol. For more information, Shared File Systems service in the Storage Guide . Note For the complete suite of documentation for Red Hat OpenStack Platform, see Red Hat OpenStack Platform Documentation .

Commands:
4.2. Example - Laptop One other very common place where power management and savings can really make a difference are laptops. As laptops by design normally already use drastically less energy than workstations or servers the potential for absolute savings are less than for other machines. When in battery mode, though, any saving can help to get a few more minutes of battery life out of a laptop. Although this section focuses on laptops in battery mode, but you certainly can still use some or all of those tunings while running on AC power as well. Savings for single components usually make a bigger relative difference on laptops than they do on workstations. For example, a 1 Gbit/s network interface running at 100 Mbits/s saves around 3-4 watts. For a typical server with a total power consumption of around 400 watts, this saving is approximately 1 %. On a laptop with a total power consumption of around 40 watts, the power saving on just this one component amounts to 10 % of the total. Specific power-saving optimizations on a typical laptop include: Configure the system BIOS to disable all hardware that you do not use. For example, parallel or serial ports, card readers, webcams, WiFi, and Bluetooth just to name a few possible candidates. Dim the display in darker environments where you do not need full illumination to read the screen comfortably. Use System + Preferences Power Management on the GNOME desktop, Kickoff Application Launcher + Computer + System Settings + Advanced Power Management on the KDE desktop; or gnome-power-manager or xbacklight at the command line; or the function keys on your laptop. Additionally, (or alternatively) you can perform many small adjustments to various system settings: use the ondemand governor (enabled by default in Red Hat Enterprise Linux 7) enable AC97 audio power-saving (enabled by default in Red Hat Enterprise Linux 7): enable USB auto-suspend: Note that USB auto-suspend does not work correctly with all USB devices. mount file system using relatime (default in Red Hat Enterprise Linux 7): reduce screen brightness to 50 or less, for example: activate DPMS for screen idle: deactivate Wi-Fi:

Commands:
~]# echo Y > /sys/module/snd_ac97_codec/parameters/power_save
~]# for i in /sys/bus/usb/devices/*/power/autosuspend; do echo 1 > USDi; done
~]# mount -o remount,relatime mountpoint
~]USD xbacklight -set 50
~]USD xset +dpms; xset dpms 0 0 300
~]# echo 1 > /sys/bus/pci/devices/*/rf_kill
2.4.4. Monitoring Storage Monitoring storage normally takes place at two different levels: Monitoring for sufficient disk space Monitoring for storage-related performance problems The reason for this is that it is possible to have dire problems in one area and no problems whatsoever in the other. For example, it is possible to cause a disk drive to run out of disk space without once causing any kind of performance-related problems. Likewise, it is possible to have a disk drive that has 99% free space, yet is being pushed past its limits in terms of performance. However, it is more likely that the average system experiences varying degrees of resource shortages in both areas. Because of this, it is also likely that -- to some extent -- problems in one area impact the other. Most often this type of interaction takes the form of poorer and poorer I/O performance as a disk drive nears 0% free space although, in cases of extreme I/O loads, it might be possible to slow I/O throughput to such a level that applications no longer run properly. In any case, the following statistics are useful for monitoring storage: Free Space Free space is probably the one resource all system administrators watch closely; it would be a rare administrator that never checks on free space (or has some automated way of doing so). File System-Related Statistics These statistics (such as number of files/directories, average file size, etc.) provide additional detail over a single free space percentage. As such, these statistics make it possible for system administrators to configure the system to give the best performance, as the I/O load imposed by a file system full of many small files is not the same as that imposed by a file system filled with a single massive file. Transfers per Second This statistic is a good way of determining whether a particular device's bandwidth limitations are being reached. Reads/Writes per Second A slightly more detailed breakdown of transfers per second, these statistics allow the system administrator to more fully understand the nature of the I/O loads a storage device is experiencing. This can be critical, as some storage technologies have widely different performance characteristics for read versus write operations.

Commands:
13.2.29. Downgrading SSSD When downgrading - either downgrading the version of SSSD or downgrading the operating system itself - then the existing SSSD cache needs to be removed. If the cache is not removed, then SSSD process is dead but a PID file remains. The SSSD logs show that it cannot connect to any of its associated domains because the cache version is unrecognized. Users are then no longer recognized and are unable to authenticate to domain services and hosts. After downgrading the SSSD version: Delete the existing cache database files. Restart the SSSD process.

Commands:
(Wed Nov 28 21:25:50 2012) [sssd] [sysdb_domain_init_internal] (0x0010): Unknown DB version [0.14], expected [0.10] for domain AD!
~]# rm -rf /var/lib/sss/db/*
~]# service sssd restart Stopping sssd: [FAILED] Starting sssd: [ OK ]
Part II. Requirements and your responsibilities Before you start using the subscriptions service, review the hardware and software requirements and your responsibilities when you use the service. Learn more Review the general requirements for using the subscriptions service: Requirements Review information about the tools that you must use to supply the subscriptions service with data about your subscription usage: How to select the right data collection tool Review information about improving the subscriptions service results by setting the right subscription attributes: How to set subscription attributes Review information about your responsibilities when you use the subscriptions service: Your responsibilities

Commands:
Chapter 3. Compiler and Tools C exception handling no longer causes unexpected terminations Previously, an incorrect unwind routine was called on the 32-bit Intel architecture because of an erroneous check in the code handling C exceptions. As a consequence, the pthread_cond_wait() function from the glibc library could write data out of bounds and applications written in the C programming language using glibc sometimes terminated unexpectedly. The erroneous check has been fixed and the unexpected termination no longer occurs. (BZ#1104812) Executable files created using the -pie option now start correctly Previously, the linker included in the binutils package produced incorrect dynamic relocations for position-independent binaries for the 32-bit Intel architecture. As a consequence, building code with the -pie compiler option produced binary files that failed to start. The linker has been fixed and now generates position-independent executable files that run correctly. (BZ# 1427285 ) Thread cancellation support for APIs depending on /etc/hosts.conf A defect in thread-cancellation support for the setmntent() function could cause the function to fail and return an error where it was expected to succeed. Consequently, programs that rely on setmntent() could fail to start. The setmntent() function has been fixed, and now works as expected. In addition, the setttyent() and setnetgrent() functions, and all APIs that rely on the /etc/hosts.conf file, have been enhanced to provide improved support for thread cancellation. (BZ# 1437147 ) ld no longer produces invalid executable files with code after initialized data Previously, the binutils ld linker placed code at an incorrect location in memory when the code followed after data initialized to zero values. As a consequence, programs in the linked executable files terminated unexpectedly with a segmentation fault. The linker has been fixed to properly allocate space for the data and position the executable code at the correct starting address. As a result, the linked executable files now run correctly. (BZ#1476412) The ss program no longer stops when providing a long list of filters Previously, providing a long list of filters to the ss command caused an integer value overflow. As a consequence, the 'ss' tool could stop the program execution. With this update, faulty bits in the source code are corrected, and the described problem no longer occurs. (BZ# 1476664 ) SystemTap no longer causes kernel panic on systems under heavy load Previously, when probes of the SystemTap tool were added and removed at the same time by multiple processes, a kernel panic occurred. As a consequence, unloading SystemTap modules on systems under heavy load in some cases caused kernel panics. The procedure for removing probes has now been fixed and SystemTap no longer causes a kernel panic in the described situation. (BZ#1525651)

Commands:
7.2. Desktop Environments and Window Managers Once an X server is running, X client applications can connect to it and create a GUI for the user. A range of GUIs are possible with Red Hat Enterprise Linux, from the rudimentary Tab Window Manager to the highly developed and interactive GNOME desktop environment that most Red Hat Enterprise Linux users are familiar with. To create the latter, more advanced GUI, two main classes of X client applications must connect to the X server: a desktop environment and a window manager . 7.2.1. Desktop Environments A desktop environment brings together assorted X clients which, when used together, create a common graphical user environment and development platform. Desktop environments have advanced features allowing X clients and other running processes to communicate with one another, while also allowing all applications written to work in that environment to perform advanced tasks, such as drag and drop operations. Red Hat Enterprise Linux provides two desktop environments: GNOME - The default desktop environment for Red Hat Enterprise Linux based on the GTK+ 2 graphical toolkit. KDE - An alternative desktop environment based on the Qt 3 graphical toolkit. Both GNOME and KDE have advanced productivity applications, such as word processors, spreadsheets, and Web browsers, and provide tools to customize the look and feel of the GUI. Additionally, if both the GTK+ 2 and the Qt libraries are present, KDE applications can run in GNOME and visa versa.

Commands:
Chapter 37. Resizing an Online Logical Unit In most cases, fully resizing an online logical unit involves two things: resizing the logical unit itself and reflecting the size change in the corresponding multipath device (if multipathing is enabled on the system). To resize the online logical unit, start by modifying the logical unit size through the array management interface of your storage device. This procedure differs with each array; as such, consult your storage array vendor documentation for more information on this. Note In order to resize an online file system, the file system must not reside on a partitioned device. 37.1. Resizing Fibre Channel Logical Units After modifying the online logical unit size, re-scan the logical unit to ensure that the system detects the updated size. To do this for Fibre Channel logical units, use the following command: Important To re-scan fibre channel logical units on a system that uses multipathing, execute the aforementioned command for each sd device (i.e. sd1 , sd2 , and so on) that represents a path for the multipathed logical unit. To determine which devices are paths for a multipath logical unit, use multipath -ll ; then, find the entry that matches the logical unit being resized. It is advisable that you refer to the WWID of each entry to make it easier to find which one matches the logical unit being resized.

Commands:
echo 1 > /sys/block/sd X /device/rescan
Appendix B. Revision History Revision History Revision 0.1-5 Fri May 12 2017 Lenka Spackova Moved the fence_sanlock agent and checkquorum.wdmd from Technology Previews to Deprecated Functionality. Revision 0.1-3 Thu Apr 27 2017 Lenka Spackova Added the deprecated zerombr yes Kickstart command to Deprecated Functionality. Revision 0.1-2 Fri Mar 31 2017 Lenka Spackova Added a bug fix to Virtualization. Revision 0.1-1 Tue Mar 28 2017 Lenka Spackova Minor edits in accordance with the updated Red Hat Enterprise Linux 6.9 Release Notes. Revision 0.0-9 Tue Mar 21 2017 Lenka Spackova Release of the Red Hat Enterprise Linux 6.9 Technical Notes. Revision 0.0-5 Thu Jan 05 2017 Lenka Spackova Release of the Red Hat Enterprise Linux 6.9 Beta Technical Notes.

Commands:
Part III. Configuring and viewing your data After adding your OpenShift Container Platform and AWS data, cost management displays your cost data by integration, as well as the cost and usage associated with running your OpenShift Container Platform clusters. If you are using an AWS savings plan for the EC2 instances running OpenShift nodes, cost management defaults to using the savings plan cost. On the cost management Overview page, your cost data is sorted into OpenShift and Infrastructure tabs. Select Perspective to toggle through different views of your cost data. You can also use the global navigation menu to view additional details about your costs by cloud provider. To add other types of integrations, see: Integrating OpenShift Container Platform data into cost management Integrating Google Cloud data into cost management Integrating Microsoft Azure data into cost management Integrating Oracle Cloud data into cost management

Commands:
1.4. SELinux States and Modes SELinux can run in one of three modes: disabled, permissive, or enforcing. Disabled mode is strongly discouraged; not only does the system avoid enforcing the SELinux policy, it also avoids labeling any persistent objects such as files, making it difficult to enable SELinux in the future. In permissive mode, the system acts as if SELinux is enforcing the loaded security policy, including labeling objects and emitting access denial entries in the logs, but it does not actually deny any operations. While not recommended for production systems, permissive mode can be helpful for SELinux policy development. Enforcing mode is the default, and recommended, mode of operation; in enforcing mode SELinux operates normally, enforcing the loaded security policy on the entire system. Use the setenforce utility to change between enforcing and permissive mode. Changes made with setenforce do not persist across reboots. To change to enforcing mode, enter the setenforce 1 command as the Linux root user. To change to permissive mode, enter the setenforce 0 command. Use the getenforce utility to view the current SELinux mode: In Red Hat Enterprise Linux, you can set individual domains to permissive mode while the system runs in enforcing mode. For example, to make the httpd_t domain permissive: See Section 11.3.4, "Permissive Domains" for more information. Note Persistent states and modes changes are covered in Section 4.4, "Permanent Changes in SELinux States and Modes" .

Commands:
~]# getenforce Enforcing
~]# setenforce 0 ~]# getenforce Permissive
~]# setenforce 1 ~]# getenforce Enforcing
~]# semanage permissive -a httpd_t
Chapter 4. Creating the traffic violations project in Business Central For this example, create a new project called traffic-violation . A project is a container for assets such as data objects, DMN assets, and test scenarios. This example project that you are creating is similar to the existing Traffic_Violation sample project in Business Central. Procedure In Business Central, go to Menu Design Projects . Red Hat Process Automation Manager provides a default space called MySpace . You can use the default space to create and test example projects. Click Add Project . Enter traffic-violation in the Name field. Click Add . Figure 4.1. Add Project window The Assets view of the project opens.

Commands:
5.6. Load Balancing Policy: None If no load balancing policy is selected, virtual machines are started on the host within a cluster with the lowest CPU utilization and available memory. To determine CPU utilization a combined metric is used that takes into account the virtual CPU count and the CPU usage percent. This approach is the least dynamic, as the only host selection point is when a new virtual machine is started. Virtual machines are not automatically migrated to reflect increased demand on a host. An administrator must decide which host is an appropriate migration target for a given virtual machine. Virtual machines can also be associated with a particular host using pinning. Pinning prevents a virtual machine from being automatically migrated to other hosts. For environments where resources are highly consumed, manual migration is the best approach.

Commands:
4.5. Directory Tree Design Examples The following sections provide examples of directory trees designed to support a flat hierarchy as well as several examples of more complex hierarchies. 4.5.1. Directory Tree for an International Enterprise To support an international enterprise, use the Internet domain name as the root point for the directory tree, then branch the tree immediately below that root point for each country where the enterprise has operations. Avoid using a country designator as the root point for the directory tree, as mentioned in Section 4.2.1.1, "Suffix Naming Conventions" , especially if the enterprise is international. Because LDAP places no restrictions on the order of the attributes in the DNs, the c attribute can represent each country branch: Figure 4.17. Using the c Attribute to Represent Different Countries However, some administrators feel that this is stylistically awkward, so instead use the l attribute to represent different countries: Figure 4.18. Using the l Attribute to Represent Different Countries 4.5.2. Directory Tree for an ISP Internet service providers (ISPs) may support multiple enterprises with their directories. ISP should consider each of the customers as a unique enterprise and design their directory trees accordingly. For security reasons, each account should be provided a unique directory tree with a unique suffix and an independent security policy. An ISP should consider assigning each customer a separate database and storing these databases on separate servers. Placing each directory tree in its own database allows data to be backed up and restored for each directory tree without affecting the other customers. In addition, partitioning helps reduce performance problems caused by disk contention and reduces the number of accounts potentially affected by a disk outage. Figure 4.19. Directory tree for Example ISP

Commands:
Chapter 5. Multiple JFR recordings based on the same custom trigger definition The Cryostat 2.4 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. In this situation, if you want to enable the Cryostat agent to start new JFR recordings based on custom trigger conditions that previously triggered a recording, you must restart the Cryostat agent.

Commands: