mtpti5iD/redhat-docs_dataset huggingface dataset:
7.2. Manually Setting the Number of Thread In certain situations, it can be necessary to manually set a fixed number of Directory Server threads instead of using the automatic thread tuning. Note If the number of hardware threads changes, for example, because you increased the CPU cores of the virtual machine that runs the Directory Server instance, you must manually update the number of threads. For details about using the optimized and automatic setting, see Section 7.1, "Automatic Thread Tuning" . 7.2.1. Manually Setting the Number of Threads Using the Command Line To manually set the number of threads using the command line: Set the number of threads: This command sets the number of threads to 64 . Restart the Directory Server instance: 7.2.2. Manually Setting the Number of Threads Using the Web Console To manually set the number of threads using the Web Console: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. Open the Server Settings menu, and select Tuning & Limits . Set the Number Of Worker Threads field to the number of threads. Click Save . Click the Actions button, and select Restart Instance .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-threadnumber=" 64 "
dsctl instance_name restart
5.2.27. /proc/stat This file keeps track of a variety of different statistics about the system since it was last restarted. The contents of /proc/stat , which can be quite long, usually begins like the following example: Some of the more commonly used statistics include: cpu - Measures the number of jiffies (1/100 of a second for x86 systems) that the system has been in user mode, user mode with low priority (nice), system mode, idle task, I/O wait, IRQ (hardirq), and softirq respectively. The IRQ (hardirq) is the direct response to a hardware event. The IRQ takes minimal work for queuing the "heavy" work up for the softirq to execute. The softirq runs at a lower priority than the IRQ and therefore may be interrupted more frequently. The total for all CPUs is given at the top, while each individual CPU is listed below with its own statistics. The following example is a 4-way Intel Pentium Xeon configuration with multi-threading enabled, therefore showing four physical processors and four virtual processors totaling eight processors. page - The number of memory pages the system has written in and out to disk. swap - The number of swap pages the system has brought in and out. intr - The number of interrupts the system has experienced. btime - The boot time, measured in the number of seconds since January 1, 1970, otherwise known as the epoch .

Commands:
cpu 259246 7001 60190 34250993 137517 772 0 cpu0 259246 7001 60190 34250993 137517 772 0 intr 354133732 347209999 2272 0 4 4 0 0 3 1 1249247 0 0 80143 0 422626 5169433 ctxt 12547729 btime 1093631447 processes 130523 procs_running 1 procs_blocked 0 preempt 5651840 cpu 209841 1554 21720 118519346 72939 154 27168 cpu0 42536 798 4841 14790880 14778 124 3117 cpu1 24184 569 3875 14794524 30209 29 3130 cpu2 28616 11 2182 14818198 4020 1 3493 cpu3 35350 6 2942 14811519 3045 0 3659 cpu4 18209 135 2263 14820076 12465 0 3373 cpu5 20795 35 1866 14825701 4508 0 3615 cpu6 21607 0 2201 14827053 2325 0 3334 cpu7 18544 0 1550 14831395 1589 0 3447 intr 15239682 14857833 6 0 6 6 0 5 0 1 0 0 0 29 0 2 0 0 0 0 0 0 0 94982 0 286812 ctxt 4209609 btime 1078711415 processes 21905 procs_running 1 procs_blocked 0
Chapter 4. Viewing additional subscription details The subscription details page lists the information in the All subscriptions table for the selected subscription and, additionally, shows the support type and capacity. Support type The team you contact for support, such as Red Hat support (L1-L3) or Partner support (L3). Capacity The units used to measure the usage of a Red Hat product, such as sockets, cores, or nodes, and the maximum number of units available for usage. The Subscription details table also provides additional details about the selected subscription. Contract number The 8-digit number used to uniquely identify the contract that the subscription is purchased under. Subscription quantity The number of active subscriptions for a contract. Start date The date that the subscription became active based on the terms of the contract. End date The date that the subscription expires based on the terms of the contract. Procedure To view the details about a selected subscription in your inventory, perform the following steps: From the All subscriptions table on the Subscription Inventory page, click on the name of the subscription that you want to view. The subscription details page opens. Note The table displays up to 10 rows per page by default. You can customize the table to show up to 100 rows per page. Optional: Click the rows per page arrow to select the number of rows that you want to view on each page. Note Your subscription details might span more than one page. Use the and arrows to move between pages, if applicable. 4.1. Filtering by contract number You can use the search bar in the Subscriptions details table header to filter the subscription details by contract number. For example, if you type "1" into the search bar, the table shows only the contracts that contain the number "1" in the Contract number field.

Commands:
Using Event-Driven Ansible 2.5 with Ansible Automation Platform 2.4 Red Hat Ansible Automation Platform 2.4 Configure the latest Event-Driven Ansible to work with an existing 2.4 automation controller Red Hat Customer Content Services

Commands:
This is the enterprise installer inventory file Please consult the docs if you are unsure what to add For all optional variables please consult the Red Hat documentation: https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation This section is for your platform gateway hosts ----------------------------------------------------- [automationgateway] gateway1.example.org gateway2.example.org This section is for your Event-Driven Ansible controller hosts ----------------------------------------------------- [automationedacontroller] eda1.example.org eda2.example.org Common variables https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#ref-general-inventory-variables ----------------------------------------------------- registry_username=<your RHN username> registry_password=<your RHN password> Platform gateway https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#ref-gateway-variables ----------------------------------------------------- automationgateway_admin_password=<set your own> automationgateway_pg_host=<set your own> automationgateway_pg_database=<set your own> automationgateway_pg_username=<set your own> automationgateway_pg_password=<set your own> Event-Driven Ansible controller https://docs.redhat.com/en/documentation/red_hat_ansible_automation_platform/2.5/html/rpm_installation/appendix-inventory-files-vars#event-driven-ansible-controller ----------------------------------------------------- automationedacontroller_admin_password=<set your own> automationedacontroller_pg_host=<set your own> automationedacontroller_pg_database=<set your own> automationedacontroller_pg_username=<set your own> automationedacontroller_pg_password=<set your own>
Chapter 10. Storage Support of Parallel NFS Parallel NFS (pNFS) is a part of the NFS v4.1 standard that allows clients to access storage devices directly and in parallel. The pNFS architecture can improve the scalability and performance of NFS servers for several common workloads. pNFS defines 3 different storage protocols or layouts: files, objects and blocks. The Red Hat Enterprise Linux 6.4 NFS client supports the files layout protocol. To enable the pNFS file-layout client in Red Hat Enterprise Linux, use the -o v4.1 option when mounting a file system on a pNFS-capable server. When the server is pNFS-enabled, the nfs_layout_nfsv41_files kernel module is automatically loaded on the first mount. Use the following command to verify that this module was loaded: For more information on pNFS, refer to http://www.pnfs.com/ . XFS Online Discard Support An online discard operation performed on a mounted file system discards blocks which are not in use by the file system. Online discard operations are now supported on XFS file systems. For more information, refer to the section Discard Unused Blocks in the Red Hat Enterprise Linux 6 Storage Administration Guide . LVM Support for Micron PCIe SSD In Red Hat Enterprise Linux 6.4, LVM adds support for Micron PCIe Solid State Drives (SSDs) as devices that may form a part of a Volume Group. LVM Support for 2-way Mirror RAID10 LVM is now capable of creating, removing, and resizing RAID10 logical volumes. To create a RAID10 logical volume, like the other RAID types, specify the segment type as follows: Note that the -m and -i arguments behave in the same way they would for other segment types. That is, -i is the total number of stripes while -m is the number of (additional) copies (that is, -m 1 -i 2 gives 2 stripes on top of 2-way mirrors). Set Up and Manage SCSI Persistent Reservations Through Device Mapper Devices Previously, to set up persistent reservations on multipath devices, it was necessary to set it up on all of the path devices. If a path device was later added, it was necessary to manually add reservations to that path. Red Hat Enterprise Linux 6.4 adds the ability to set up and manage SCSI persistent reservations through device mapper devices with the mpathpersist command. When path devices are added, persistent reservations are set up on those devices as well.

Commands:
~]USD lsmod | grep nfs_layout_nfsv41_files
~]# lvcreate --type raid10 -m 1 -i 2 -L 1G -n lv vg
Chapter 8. Internationalization 8.1. Red Hat Enterprise Linux 8 International Languages Red Hat Enterprise Linux 8 supports the installation of multiple languages and the changing of languages based on your requirements. East Asian Languages - Japanese, Korean, Simplified Chinese, and Traditional Chinese. European Languages - English, German, Spanish, French, Italian, Portuguese, and Russian. The following table lists the fonts and input methods provided for various major languages. Language Default Font (Font Package) Input Methods English dejavu-sans-fonts French dejavu-sans-fonts German dejavu-sans-fonts Italian dejavu-sans-fonts Russian dejavu-sans-fonts Spanish dejavu-sans-fonts Portuguese dejavu-sans-fonts Simplified Chinese google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-libpinyin, libpinyin Traditional Chinese google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-libzhuyin, libzhuyin Japanese google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-kkc, libkkc Korean google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-hangul, libhangu 8.2. Notable changes to internationalization in RHEL 8 RHEL 8 introduces the following changes to internationalization compared to RHEL 7: Support for the Unicode 11 computing industry standard has been added. Internationalization is distributed in multiple packages, which allows for smaller footprint installations. For more information, see Using langpacks . The glibc package updates for multiple locales are now synchronized with the Common Locale Data Repository (CLDR).

Commands:
11.4. Configuring ACME Realm This section describes how to configure a realm for PKI ACME responder . The realm configuration is located at /etc/pki/pki-tomcat/acme/realm.conf . You can configure ACME Realm realm via command line using the pki-server acme-realm-mod command. Invoking this command without any parameters launches an interactive mode, for example: Invoking the command with the --type parameter creates a new configuration based on the specified type. Invoking the command with other parameters updates the specified parameters. 11.4.1. Configuring DS Realm You can configure PKI ACME Responder to use a DS realm. A sample configuration for DS Realm is available at /usr/share/pki/acme/realm/ds/realm.conf . To configure a DS realm: Prepare subtrees for ACME users and groups in DS. A sample LDIF file is available at /usr/share/pki/acme/realm/ds/create.ldif] . This example uses dc=acme,dc=pki,dc=example,dc=com as the base DN. Import the LDIF file using the ldapadd command: Copy the sample configuration file from /usr/share/pki/acme/realm/ds/realm.conf into the /etc/pki/pki-tomcat/acme directory, or run the following command to customize some of the parameters: Customize the configuration as needed: In a standalone ACME deployment, the realm.conf file should look like the following: In a shared CA and ACME deployment, the realm.conf file should look like the following:

Commands:
pki-server acme-realm-mod The current value is displayed in the square brackets. To keep the current value, simply press Enter. To change the current value, enter the new value. To remove the current value, enter a blank space. Enter the type of the realm. Available types: ds. Database Type: ds Enter the location of the LDAP server (e.g. ldap://localhost.localdomain:389). Server URL [ldap://localhost.localdomain:389]: Enter the authentication type. Available types: BasicAuth, SslClientAuth. Authentication Type [BasicAuth]: Enter the bind DN. Bind DN [cn=Directory Manager]: Enter the bind password. Bind Password [********]: Enter the base DN for the ACME users subtree. Users DN [ou=people,dc=acme,dc=pki,dc=example,dc=com]: Enter the base DN for the ACME groups subtree. Groups DN [ou=groups,dc=acme,dc=pki,dc=example,dc=com]:
ldapadd -h USDHOSTNAME -x -D "cn=Directory Manager" -w Secret.123 -f /usr/share/pki/acme/realm/ds/create.ldif
pki-server acme-realm-mod --type ds -DbindPassword=Secret.123
class=org.example.acme.realm.DSRealm url=ldap://<hostname>:389 authType=BasicAuth bindDN=cn=Directory Manager bindPassword=Secret.123 usersDN=ou=people,dc=acme,dc=pki,dc=example,dc=com groupsDN=ou=groups,dc=acme,dc=pki,dc=example,dc=com
class=org.example.acme.realm.DSRealm configFile=conf/ca/CS.cfg usersDN=ou=people,dc=ca,dc=pki,dc=example,dc=com groupsDN=ou=groups,dc=ca,dc=pki,dc=example,dc=com
Chapter 51. KIE Server KIE Server is the server where the rules and other artifacts for Red Hat Process Automation Manager are stored and run. KIE Server is a standalone built-in component that can be used to instantiate and execute rules through interfaces available for REST, Java Message Service (JMS), or Java client-side applications, and Red Hat build of OptaPlanner functionality through solvers. Created as a web deployable WAR file, KIE Server can be deployed on any web container. The current version of KIE Server is included with default extensions for both Red Hat Decision Manager and Red Hat Process Automation Manager. KIE Server has a low footprint with minimal memory consumption and therefore can be deployed easily on a cloud instance. Each instance of this server can open and instantiate multiple containers, which enables you to execute multiple rule services in parallel. KIE Server can be integrated with other application servers, such as Oracle WebLogic Server or IBM WebSphere Application Server, to streamline Red Hat Process Automation Manager application management.

Commands:
5.3. Booting into Single-User Mode One of the advantages of single-user mode is that you do not need a boot CD-ROM; however, it does not give you the option to mount the file systems as read-only or not mount them at all. If your system boots, but does not allow you to log in when it has completed booting, try single-user mode. In single-user mode, your computer boots to runlevel 1. Your local file systems are mounted, but your network is not activated. You have a usable system maintenance shell. Unlike rescue mode, single-user mode automatically tries to mount your file system. Do not use single-user mode if your file system cannot be mounted successfully. You cannot use single-user mode if the runlevel 1 configuration on your system is corrupted. On an x86 system using GRUB, use the following steps to boot into single-user mode: At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu. Select Red Hat Enterprise Linux with the version of the kernel that you wish to boot and type a to append the line. Go to the end of the line and type single as a separate word (press the Spacebar and then type single ). Press Enter to exit edit mode.

Commands:
Chapter 14. Idling applications Cluster administrators can idle applications to reduce resource consumption. This is useful when the cluster is deployed on a public cloud where cost is related to resource consumption. If any scalable resources are not in use, Red Hat OpenShift Service on AWS discovers and idles them by scaling their replicas to 0 . The time network traffic is directed to the resources, the resources are unidled by scaling up the replicas, and normal operation continues. Applications are made of services, as well as other scalable resources, such as deployment configs. The action of idling an application involves idling all associated resources. 14.1. Idling applications Idling an application involves finding the scalable resources (deployment configurations, replication controllers, and others) associated with a service. Idling an application finds the service and marks it as idled, scaling down the resources to zero replicas. You can use the oc idle command to idle a single service, or use the --resource-names-file option to idle multiple services. 14.1.1. Idling a single service Procedure To idle a single service, run: USD oc idle <service> 14.1.2. Idling multiple services Idling multiple services is helpful if an application spans across a set of services within a project, or when idling multiple services in conjunction with a script to idle multiple applications in bulk within the same project. Procedure Create a file containing a list of the services, each on their own line. Idle the services using the --resource-names-file option: USD oc idle --resource-names-file <filename> Note The idle command is limited to a single project. For idling applications across a cluster, run the idle command for each project individually. 14.2. Unidling applications Application services become active again when they receive network traffic and are scaled back up their state. This includes both traffic to the services and traffic passing through routes. Applications can also be manually unidled by scaling up the resources. Procedure To scale up a DeploymentConfig, run: USD oc scale --replicas=1 dc <dc_name> Note Automatic unidling by a router is currently only supported by the default HAProxy router.

Commands:
oc idle <service>
oc idle --resource-names-file <filename>
oc scale --replicas=1 dc <dc_name>
Chapter 4. Managing usability analytics and data collection from automation controller You can change how you participate in usability analytics and data collection from automation controller by opting out or changing your settings in the automation controller user interface. 4.1. Usability analytics and data collection Usability data collection is included with automation controller to collect data to better understand how automation controller users specifically interact with automation controller, to help enhance future releases, and to continue streamlining your user experience. Only users installing a trial of automation controller or a fresh installation of automation controller are opted-in for this data collection. Additional resources For more information, see the Red Hat privacy policy . 4.1.1. Controlling data collection from automation controller You can control how automation controller collects data from the Settings System menu. Procedure Log in to your automation controller. From the navigation panel, select Settings System . Select Gather data for Automation Analytics to enable automation controller to gather data on automation and send it to Automation Analytics.

Commands:
Chapter 5. Advisories related to this release The following advisories have been issued to bugfixes and CVE fixes included in this release. RHSA-2022:0204 RHSA-2022:0185 RHSA-2022:0209 RHSA-2022:0211 RHSA-2022:0228 RHSA-2022:0229 Revised on 2024-05-09 16:46:44 UTC

Commands:
Chapter 9. Installing a Fully-virtualized Windows Guest This chapter describes how to create a fully-virtualized Windows guest using the command-line ( virt-install ), launch the operating system's installer inside the guest, and access the installer through virt-viewer . To install a Windows operating system on the guest, use the virt-viewer tool. This tool allows you to display the graphical console of a virtual machine (using the SPICE or VNC protocol). In doing so, virt-viewer allows you to install a fully-virtualized guest's operating system with that operating system's installer . Installing a Windows operating system involves two major steps: Creating the guest virtual machine, using either virt-install or virt-manager . Installing the Windows operating system on the guest virtual machine, using virt-viewer . Refer to Chapter 6, Guest Virtual Machine Installation Overview for details about creating a guest virtual machine with virt-install or virt-manager . Note that this chapter does not describe how to install a Windows operating system on a fully-virtualized guest. Rather, it only covers how to create the guest and launch the installer within the guest. For information on how to install a Windows operating system, refer to the relevant Microsoft installation documentation. 9.1. Using virt-install to Create a Guest The virt-install command allows you to create a fully-virtualized guest from a terminal, without the need for a GUI. Important Before creating the guest, consider first if the guest needs to use KVM Windows paravirtualized drivers. If it does, keep in mind that you can do so during or after installing the Windows operating system on the guest. For more information about paravirtualized drivers, refer to Chapter 10, KVM Paravirtualized (virtio) Drivers . For instructions on how to install KVM paravirtualized drivers, refer to Section 10.1, "Installing the KVM Windows virtio Drivers" . It is possible to create a fully-virtualized guest with only a single command. To do so, run the following program (replace the values accordingly): The path-to-disk must be a device (e.g. /dev/sda3 ) or image file ( /var/lib/libvirt/images/ name .img ). It must also have enough free space to support the disk-size . Important All image files are stored in /var/lib/libvirt/images/ by default. Other directory locations for file-based images are possible, but may require SELinux configuration. If you run SELinux in enforcing mode, refer to the Red Hat Enterprise Linux 6 Virtualization Administration Guide for more information on SELinux. You can also run virt-install interactively. To do so, use the --prompt command, as in: Once the fully-virtualized guest is created, virt-viewer will launch the guest and run the operating system's installer. Refer to the relevant Microsoft installation documentation for instructions on how to install the operating system.

Commands:
virt-install --name= guest-name --os-type= windows --network network=default --disk path= path-to-disk ,size= disk-size --cdrom= path-to-install-disk --graphics spice --ram=1024
virt-install --prompt