mtpti5iD/redhat-docs_dataset huggingface dataset:
D.2. Supported Locales When performing directory operations that require that a locale be specified, such as a search operation, use a language tag or a collation order object identifier (OID). A language tag is a string that begins with the two-character lowercase language code that identifies the language, as defined in ISO Standard 639. If necessary to distinguish regional differences in language, the language tag may also contain a two-character string for the country code, as defined in ISO Standard 3166. The language code and country code are separated by a hyphen. For example, the language tag used to identify the British English locale is en-GB . An object identifier (OID) is a decimal number used to uniquely identify an object, such as an attribute or object class. The OIDs for searching or indexing an internationalized directory identify specific collation orders supported by the Directory Server. For example, the OID 2.16.840.1.113730.3.3.2.17.1 identifies the Finnish collation order. When performing an international search in the directory, use either the language tag or the OID to identify the collation order to use. However, when setting up an international index, the OIDs must be used. For more information on indexing, see Chapter 13, Managing Indexes . For a list of language tags and OIDs supported by the Directory Server, see the /etc/dirsrv/config/slapd-collations.conf file.

Commands:
6.12. Affinity Labels You can create and modify affinity labels in the Administration Portal. Affinity labels are used to set hard (Enforced) positive affinity between virtual machines and hosts. See the Affinity Groups section for more information about affinity hardness and polarity. Labels function identically to a hard positive affinity group, but simplify configuration in certain use cases. For example, if you have virtual machines that require specific host hardware, you can use affinity labels to ensure that those virtual machines run on the required hosts. If you use software that is license-limited to a certain number of physical machines, you can use affinity labels to ensure that virtual machines running that software are limited to the required physical hosts. Warning Affinity labels are a subset of affinity groups and can conflict with them. If there is a conflict, the virtual machine will not start. 6.12.1. Creating an Affinity Label You can create affinity labels from the details view of a virtual machine, host, or cluster. This procedure uses the cluster details view. Creating an Affinity Label Click Compute Clusters and select the appropriate cluster. Click the cluster's name to go to the details view. Click the Affinity Labels tab. Click New . Enter a Name for the affinity label. Use the drop-down lists to select the virtual machines and hosts to be associated with the label. Use the + button to add additional virtual machines and hosts. Click OK . 6.12.2. Editing an Affinity Label You can edit affinity labels from the details view of a virtual machine, host, or cluster. This procedure uses the cluster details view. Editing an Affinity Label Click Compute Clusters and select the appropriate cluster. Click the cluster's name to go to the details view. Click the Affinity Labels tab. Select the label you want to edit. Click Edit . Use the + and - buttons to add or remove virtual machines and hosts to or from the affinity label. Click OK . 6.12.3. Removing an Affinity Label You can remove affinity labels only from the details view of a cluster. Removing an Affinity Label Click Compute Clusters and select the appropriate cluster. Click the cluster's name to go to the details view. Click the Affinity Labels tab. Select the label you want to remove. Click Edit . Use the - buttons to remove all virtual machines and hosts from the label. Click OK . Click Delete . Click OK .

Commands:
5.2.2. Creating the Volume Group The following command creates the volume group striped_vol_group . You can use the vgs command to display the attributes of the new volume group.

Commands:
vgcreate striped_vol_group /dev/sda1 /dev/sdb1 /dev/sdc1 Volume group "striped_vol_group" successfully created
vgs VG #PV #LV #SN Attr VSize VFree striped_vol_group 3 0 0 wz--n- 51.45G 51.45G
20.16.9.9. TCP tunnel Creating a TCP client/server architecture is another way to provide a virtual network where one guest virtual machine provides the server end of the network and all other guest virtual machines are configured as clients. All network traffic between the guest virtual machines is routed via the guest virtual machine that is configured as the server. This model is also available for use to unprivileged users. There is no default DNS or DHCP support and no outgoing network access. To provide outgoing network access, one of the guest virtual machines should have a second NIC which is connected to one of the first 4 network types thereby providing the appropriate routing. A TCP tunnel is created by manipulating the interface type using a management tool and setting/changing it to server or client , and providing a mac and source address. The result is shown in changes made to the domain XML: ... <devices> <interface type='server'> <mac address='52:54:00:22:c9:42'> <source address='192.168.0.1' port='5558'/> </interface> ... <interface type='client'> <mac address='52:54:00:8b:c9:51'> <source address='192.168.0.1' port='5558'/> </interface> </devices> ... Figure 20.46. Devices - network interfaces- TCP tunnel

Commands:
<devices> <interface type='server'> <mac address='52:54:00:22:c9:42'> <source address='192.168.0.1' port='5558'/> </interface> <interface type='client'> <mac address='52:54:00:8b:c9:51'> <source address='192.168.0.1' port='5558'/> </interface> </devices>
4.11. Creating Multiple Red Hat Gluster Storage Instances Using Images In this chapter, we are using 20 VM instances in the local region, US-CENTRAL1, and 10 VM instances in the remote region, EUROPE-WEST1. Creating an image of the rhgs-primary-n01 as Root persistent disk. In the Google Developers Console, click Compute > Compute Engine > Images > New image . The Create a new image window is displayed. Enter the following in Create a new image window and click Create . Name: rhgs-image01 Source disk: rhgs-primary-n01 Creating an image of the rhgs-primary-n01-data as Data persistent disk. In the Google Developers Console, click Compute > Compute Engine > Images > New image . Enter the following in Create a new image window and click Create . Name: rhgs-data-image01 Source disk: rhgs-primary-n01-data

Commands:
4.261. qt 4.261.1. RHSA-2011:1328 - Moderate: qt security update Updated qt packages that fix two security issues are now available for Red Hat Enterprise Linux 6 FasTrack. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Qt is a software toolkit that simplifies the task of writing and maintaining GUI (Graphical User Interface) applications for the X Window System. HarfBuzz is an OpenType text shaping engine. Security Fixes CVE-2011-3193 A buffer overflow flaw was found in the harfbuzz module in Qt. If a user loaded a specially-crafted font file with an application linked against Qt, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. CVE-2011-3194 A buffer overflow flaw was found in the way Qt handled certain gray-scale image files. If a user loaded a specially-crafted gray-scale image file with an application linked against Qt, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. Users of Qt should upgrade to these updated packages, which contain backported patches to correct these issues. All running applications linked against Qt libraries must be restarted for this update to take effect. 4.261.2. RHBA-2011:1170 - qt bug fix update Updated qt packages that resolve several issues are now available for Red Hat Enterprise Linux 6. Qt is a software toolkit that simplifies the task of writing and maintaining GUI (Graphical User Interface) applications for the X Window System. Bug Fixes BZ# 562132 While using the Lohit font in the Malayalam script, the ra-kar character combination (0D4D + 0D30 in Unicode) was rendered incorrectly. This issue has been fixed and this combination is now rendered correctly. BZ# 679759 Example binary files in the qt-examples package were missing execute permissions, which meant that normal users could not run them. This has been fixed: file permissions have been corrected and the example files now can be executed properly. BZ# 680088 Due to an issue in the qt buildroot, the complexpong example was incorrectly removed for the PowerPC architecture qt-examples package, which caused that missing files were reported when the qt-examples file list was verified. This issue has been fixed: the complexpong example is now correctly included for all supported architectures. BZ# 716694 Previously, the /etc/rpm/macros.qt4 file was part of the qt-x11 package, which was incorrect. This issue has been corrected: the file has been moved into the qt-devel package. All users of qt are advised to upgrade to these updated packages, which resolve these issues.

Commands:
5.6. KSM Kernel shared memory (KSM) enables the kernel to examine two or more already running programs and compare their memory. If any pages are identical, KSM merges multiple identical memory pages to a single page. This page is then marked as copy on write (COW), and can be shared among system processes. The ksm service starts and stops the KSM thread, and the ksmtuned service controls and tunes the ksm service. For information on KSM and its tuning, see the KSM chapter of the Red Hat Enterprise Linux 6 Virtualization Administration Guide .

Commands:
Appendix F. Additional Replication High Availability Configuration Elements The following table lists additional ha-policy configuration elements that are not described in the Configuring replication high availability section. These elements have default settings that are sufficient for most common use cases. Table F.1. Additional Configuration Elements Available when Using Replication High Availability Name Used in Description check-for-live-server Embedded broker coordination Applies only to brokers configured as master brokers. Specifies whether the original master broker checks the cluster for another live broker using its own server ID when starting up. Set to true to fail back to the original master broker and avoid a "split brain" situation in which two brokers become live at the same time. The default value of this property is false . cluster-name Embedded broker and ZooKeeper coordination Name of the cluster configuration to use for replication. This setting is only necessary if you configure multiple cluster connections. If configured, the the cluster configuration with this name will be used when connecting to the cluster. If unset, the first cluster connection defined in the configuration is used. initial-replication-sync-timeout Embedded broker and ZooKeeper coordination The amount of time the replicating broker will wait upon completion of the initial replication process for the replica to acknowledge that it has received all the necessary data. The default value of this property is 30,000 milliseconds. NOTE: During this interval, any other journal-related operations are blocked. max-saved-replicated-journals-size Embedded broker and ZooKeeper coordination Applies to backup brokers only. Specifies how many backup journal files the backup broker retains. Once this value has been reached, the broker makes space for each new backup journal file by deleting the oldest journal file. The default value of this property is 2 . Revised on 2024-06-10 15:28:05 UTC

Commands:
6.3. Standard Groups Table 6.2, "Standard Groups" lists the standard groups configured by an Everything installation. Groups are stored in the /etc/group file. Table 6.2. Standard Groups Group GID Members root 0 root bin 1 root, bin, daemon daemon 2 root, bin, daemon sys 3 root, bin, adm adm 4 root, adm, daemon tty 5 disk 6 root lp 7 daemon, lp mem 8 kmem 9 wheel 10 root mail 12 mail, postfix, exim news 13 news uucp 14 uucp man 15 games 20 gopher 30 dip 40 ftp 50 lock 54 nobody 99 users 100 rpm 37 utmp 22 floppy 19 vcsa 69 dbus 81 ntp 38 canna 39 nscd 28 rpc 32 postdrop 90 postfix 89 mailman 41 exim 93 named 25 postgres 26 sshd 74 rpcuser 29 nfsnobody 65534 pvm 24 apache 48 xfs 43 gdm 42 htt 101 mysql 27 webalizer 67 mailnull 47 smmsp 51 squid 23 ldap 55 netdump 34 pcap 77 quaggavt 102 quagga 92 radvd 75 slocate 21 wnn 49 dovecot 97 radiusd 95

Commands:
Chapter 1. About this release These release notes track the development of OpenShift sandboxed containers 1.8 alongside Red Hat OpenShift Container Platform 4.17. Release notes include links to the original tickets. Private tickets have no links. OpenShift Container Platform is designed for FIPS. When running Red Hat Enterprise Linux (RHEL) or Red Hat Enterprise Linux CoreOS (RHCOS) booted in FIPS mode, OpenShift Container Platform core components use the RHEL cryptographic libraries that have been submitted to NIST for FIPS 140-2/140-3 Validation on only the x86_64 , ppc64le , and s390x architectures. For more information about the NIST validation program, see Cryptographic Module Validation Program . For the latest NIST status for the individual versions of RHEL cryptographic libraries that have been submitted for validation, see Compliance Activities and Government Standards . You can view all advisories , including security and bug fixes, for major and minor versions of this release on the Red Hat Customer Portal.

Commands:
Chapter 6. Performing the upgrade from RHEL 7 to RHEL 8 Upgrade to RHEL 8 using the Leapp utility. Prerequisites The steps listed in Preparing for the upgrade have been completed, including a full system backup. The steps listed in Reviewing the pre-upgrade report have been completed and all reported issues resolved. Procedure On your RHEL 7 system, start the upgrade process: Replace <target_os_version> with the target operating system (OS) version, for example 8.10. If no target OS version is defined, Leapp uses the default target OS version specified in the table 1.1 in Supported upgrade paths . Note If you are using custom repositories from the /etc/yum.repos.d/ directory for the upgrade, enable the selected repositories as follows: If you are upgrading without RHSM or using RHUI, add the --no-rhsm option. If you are upgrading by using an ISO image, add the --no-rhsm and --iso <file_path> options. Replace <file_path> with the file path to the saved ISO image, for example /home/rhel8.iso . If you have an Extended Upgrade Support (EUS) , Advanced Update Support (AUS), or Update Services for SAP Solutions (E4S) (Red Hat Knowledgebase) subscription, add the --channel <channel> option: If you are upgrading to RHEL 8.8, replace channel with the value you used with the leapp preupgrade command, for example, eus , aus , or e4s . Note that you must use the same value with the --channel option in both the leapp preupgrade and leapp upgrade commands. If you are upgrading to RHEL 8.10, replace channel with ga . At the beginning of the upgrade process, Leapp performs the pre-upgrade phase described in Reviewing the pre-upgrade report . If the system is upgradable, Leapp downloads necessary data and prepares an RPM transaction for the upgrade. If your system does not meet the parameters for a reliable upgrade, Leapp terminates the upgrade process and provides a record describing the issue and a recommended solution in the /var/log/leapp/leapp-report.txt file. For more information, see Troubleshooting . Manually restart the system: In this phase, the system boots into a RHEL 8-based initial RAM disk image, initramfs. Leapp upgrades all packages and automatically reboots to the RHEL 8 system. Alternatively, you can enter the leapp upgrade command with the --reboot option and skip this manual step. If a failure occurs, investigate logs as described in Troubleshooting . Log in to the RHEL 8 system and verify its state as described in Verifying the post-upgrade state of the RHEL 8 system . Perform all post-upgrade tasks described in the upgrade report and in Performing post-upgrade tasks . Especially, re-evaluate and re-apply your security policies. In case of upgrading a system that was and will be running in FIPS mode , remove any RHEL 7 kernels. Then, regenerate and otherwise ensure the FIPS compliance of all cryptographic keys. See Locations of cryptographic keys in RHEL 8 for more information.

Commands:
leapp upgrade --target <target_os_version>
leapp upgrade --enablerepo <repository_id1> --enablerepo <repository_id2> ...
reboot
7.139. man 7.139.1. RHBA-2013:0392 - man bug fix update Updated man packages that fix one bug are now available for Red Hat Enterprise Linux 6. The man packages provide the man, apropos, and whatis tools to find information and documentation about the Linux system. Bug Fix BZ#815209 Previously, the patch for the man-pages-overrides package ignored localized man pages. Consequently, installing this package also overrode man pages localized in different languages. With this update, this bug has been fixed and man pages from the man-pages-overrides package now override only man pages in the same language. All users of man are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.21. cdrkit 7.21.1. RHBA-2012:1451 - cdrkit bug fix update Updated cdrkit packages that fix one bug are now available for Red Hat Enterprise Linux 6. The cdrkit packages contain a collection of CD/DVD utilities for generating the ISO9660 file-system and burning media. Bug Fix BZ#797990 Prior to this update, overlapping memory was handled incorrectly. As a consequence, newly created paths could be garbled when calling "genisoimage" with the "-graft-points" option to graft the paths at points other than the root directory. This update modifies the underlying code to generate graft paths as expected. All users of cdrkit are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.171. python 7.171.1. RHSA-2015:1330 - Moderate: python security, bug fix, and enhancement update Updated python packages that fix multiple security issues, several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. Python is an interpreted, interactive, object-oriented programming language often compared to Tcl, Perl, Scheme, or Java. Python includes modules, classes, exceptions, very high level dynamic data types and dynamic typing. Python supports interfaces to many system calls and libraries, as well as to various windowing systems (X11, Motif, Tk, Mac and MFC). Security Fixes CVE-2014-1912 It was discovered that the socket.recvfrom_into() function failed to check the size of the supplied buffer. This could lead to a buffer overflow when the function was called with an insufficiently sized buffer. CVE-2013-1752 It was discovered that multiple Python standard library modules implementing network protocols (such as httplib or smtplib) failed to restrict the sizes of server responses. A malicious server could cause a client using one of the affected modules to consume an excessive amount of memory. CVE-2014-4650 It was discovered that the CGIHTTPServer module incorrectly handled URL encoded paths. A remote attacker could use this flaw to execute scripts outside of the cgi-bin directory, or disclose the source code of the scripts in the cgi-bin directory. CVE-2014-7185 An integer overflow flaw was found in the way the buffer() function handled its offset and size arguments. An attacker able to control these arguments could use this flaw to disclose portions of the application memory or cause it to crash. These updated python packages also include numerous bug fixes and enhancements. Space precludes documenting all of these changes in this advisory. For information on the most significant of these changes, users are directed to the following article on the Red Hat Customer Portal: https://access.redhat.com/articles/1495363 All python users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add this enhancement.

Commands:
Chapter 2. Getting started with automation services catalog This guide provides instructions to begin using automation services catalog, including prerequisites and procedures for connecting your Ansible Tower provider, as well as configuring users and permissions. We also provide instructions for working with platforms, portfolios, and products. After completing the setup described and following the steps in this guide, you will have a portfolio of products, governed by an approval process, accessible to users. Note Entitlements To begin using Automation Service Catalog, you need: At least one Red Hat account user with Organization Administrator entitlements. The account number for this Red Hat corporate account.

Commands:
2.3. Creating PAM Modules New PAM modules can be created or added at any time for use by PAM-aware applications. PAM-aware programs can immediately use the new module and any methods it defines without being recompiled or otherwise modified. This allows developers and system administrators to mix-and-match, as well as test, authentication methods for different programs without recompiling them. Documentation on writing modules is included in the /usr/share/doc/pam- version# directory.

Commands:
33.8. Display Configuration If you are installing the X Window System, you can configure it during the kickstart installation by checking the Configure the X Window System option on the Display Configuration window as shown in Figure 33.11, "X Configuration" . If this option is not chosen, the X configuration options are disabled and the skipx option is written to the kickstart file. Figure 33.11. X Configuration Select whether to start the Setup Agent the first time the installed system boots. The Setup Agent is disabled by default, but the setting can be changed to enabled or enabled in reconfiguration mode. Reconfiguration mode enables the language, mouse, keyboard, root password, security level, time zone, and networking configuration options in addition to the default ones.

Commands:
20.7. Assigning a Quota to an Object Assigning a Quota to a Virtual Machine Click Compute Virtual Machines and select a virtual machine. Click Edit . Select the quota you want the virtual machine to consume from the Quota drop-down list. Click OK . Assigning a Quota to a Virtual Disk Click Compute Virtual Machines . Click a virtual machine's name to open the details view. Click the Disks tab and select the disk you plan to associate with a quota. Click Edit . Select the quota you want the virtual disk to consume from the Quota drop-down list. Click OK . Important Quota must be selected for all objects associated with a virtual machine, in order for that virtual machine to work. If you fail to select a quota for the objects associated with a virtual machine, the virtual machine will not work. The error that the Manager throws in this situation is generic, which makes it difficult to know if the error was thrown because you did not associate a quota with all of the objects associated with the virtual machine. It is not possible to take snapshots of virtual machines that do not have an assigned quota. It is not possible to create templates of virtual machines whose virtual disks do not have assigned quotas.

Commands: