mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Installing automation hub with the setup script Run the installer setup script after you have configured the appropriate inventory variables. 4.1. Running the setup script You can run the setup script when you finish updating the inventory file with the required parameters for installing your private automation hub. Run the setup.sh script to begin installation: USD ./setup.sh 4.2. Verifying Red Hat Single Sign-On connection The installer uses the Red Hat Single Sign-On variables to setup a Keycloak realm and client. To verify that you have successfully connected to the existing Red Hat Single Sign-On installation, check that settings.py contains the Red Hat Single Sign-On host information, the realm name, the key, and the secret.

Commands:
./setup.sh
5.9.2. File System Basics Red Hat Enterprise Linux includes support for many popular file systems, making it possible to easily access the file systems of other operating systems. This is particularly useful in dual-boot scenarios and when migrating files from one operating system to another. The supported file systems include (but are not limited to): EXT2 EXT3 NFS ISO 9660 MSDOS VFAT The following sections explore the more popular file systems in greater detail. 5.9.2.1. EXT2 Until recently, the ext2 file system had been the standard file system for Linux. As such, it has received extensive testing and is considered one of the more robust file systems in use today. However, there is no perfect file system, and ext2 is no exception. One problem that is commonly reported is that an ext2 file system must undergo a lengthy file system integrity check if the system was not cleanly shut down. While this requirement is not unique to ext2, the popularity of ext2, combined with the advent of larger disk drives, meant that file system integrity checks were taking longer and longer. Something had to be done. The section describes the approach taken to resolve this issue under Red Hat Enterprise Linux.

Commands:
probe::vm.kmalloc Name probe::vm.kmalloc - Fires when kmalloc is requested Synopsis vm.kmalloc Values gfp_flags type of kmemory to allocate bytes_req requested Bytes name name of the probe point ptr pointer to the kmemory allocated bytes_alloc allocated Bytes caller_function name of the caller function gfp_flag_name type of kmemory to allocate (in String format) call_site address of the kmemory function

Commands:
Chapter 4. Exporting vulnerability data as JSON, CSV, or PDF file The vulnerability service enables you to export data for CVEs on systems in your RHEL infrastructure. After applying filters in the vulnerability service to view a specific set of CVEs or systems, you can export data based on those criteria. These reports are accessible through the Red Hat Insights for Red Hat Enterprise Linux application and can be exported and downloaded as .csv, .json, or PDF files. 4.1. Exporting CVE data from the vulnerability service Perform the following steps to export select data from the vulnerability service. Procedure Navigate to the Security > Vulnerability > CVEs page and log in if necessary. Apply filters and use the sorting functionality at the top of each column to locate specific CVEs. Above the list of CVEs and to the right of the Filters menu, click the Export icon, , and select Export to JSON , Export to CSV , or Export as PDF based on your download preferences. Select a download location and click Save .

Commands:
probe::vm.kmem_cache_alloc_node Name probe::vm.kmem_cache_alloc_node - Fires when \ Synopsis Values ptr Pointer to the kmemory allocated caller_function Name of the caller function. call_site Address of the function calling this kmemory function. gfp_flag_name Type of kmemory to allocate(in string format) name Name of the probe point bytes_req Requested Bytes bytes_alloc Allocated Bytes gfp_flags type of kmemory to allocate Description kmem_cache_alloc_node is requested.

Commands:
vm.kmem_cache_alloc_node
1.2. As Part of Planning Single Sign-On The thing about authentication as described in Section 1.1, "Confirming User Identities" is that every secure application requires at least a password to access it. Without a central identity store and every application maintaining its own set of users and credentials, a user has to enter a password for every single service or application he opens. This can require entering a password several times a day, maybe even every few minutes. Maintaining multiple passwords, and constantly being prompted to enter them, is a hassle for users and administrators. Single sign-on is a configuration which allows administrators to create a single password store so that users can log in once, using a single password, and be authenticated to all network resources. Red Hat Enterprise Linux supports single sign-on for several resources, including logging into workstations, unlocking screen savers, and accessing secured web pages using Mozilla Firefox. With other available system services such as PAM, NSS, and Kerberos, other system applications can be configured to use those identity sources. Single sign-on is both a convenience to users and another layer of security for the server and the network. Single sign-on hinges on secure and effective authentication. Red Hat Enterprise Linux provides two authentication mechanisms which can be used to enable single sign-on: Kerberos-based authentication, through both Kerberos realms and Active Directory domains Smart card-based authentication Both of these methods create a centralized identity store (either through a Kerberos realm or a certificate authority in a public key infrastructure), and the local system services then use those identity domains rather than maintaining multiple local stores.

Commands:
Chapter 13. Viewing diagnostics Use the Diagnostics tab to view diagnostic information about the JVM via the JVM DiagnosticCommand and HotspotDiangostic interfaces. Note The functionality is similar to the Diagnostic Commands view in Java Mission Control (jmc) or the command line tool jcmd. The plugin will provide corresponding jcmd commands in some scenarios. Procedure To retrieve the number of instances of loaded classes and the amount of bytes they take up, click Class Histogram . If the operation is repeated, the tab shows the difference since last run. To view the JVM diagnostic flag setting, click the JVM flags . For a running JVM, you can also modify the flag settings. Additional resources The supported JVM depends on the platform, for more information go to one of the following sources: http://www.oracle.com/technetwork/java/vmoptions-jsp-140102.html http://openjdk.java.net/groups/hotspot/docs/RuntimeOverview.html

Commands:
8.167. parted 8.167.1. RHBA-2014:1450 - parted bug fix and enhancement update Updated parted packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The parted packages provide tools to create, destroy, resize, move, and copy hard disk partitions. The parted program can be used for creating space for new operating systems, reorganizing disk usage, and copying data to new hard disks. Bug Fixes BZ# 1018075 Previously, parted wrongly assumed that a minor number of a device was always equal to its major number plus its partition number. However, this is not true with some devices, such as DM multipath devices. As a consequence, operations with parted on DM multipath devices were failing. With this update, parted verifies the mount status of a device by the path to the device instead of using the "minor:major" number. BZ# 929319 The parted program printed an unnecessary warning when used with disks that had the sector size of 4 KB. With this update, this confusing warning has been removed from parted. BZ# 975478 Previously, the align-check directive did not work correctly when used from parted in interactive mode. Users had to use parted in script mode in order to be able to utilize the align-check directive. This update corrects the relevant code, and align-check now works in interactive mode as expected. BZ# 1074069 The parted program could fail with an EBUSY error if it was rapidly called in a loop. To resolve this problem, this update modifies parted to keep retrying for up to 1 second when receiving an EBUSY error. BZ# 1139435 To prevent failures on systems that do not support partitioned loop devices, such as IBM S/390 systems, the t8000-loop.sh test has been modified to being no longer run on these systems. In addition, this update adds the following Enhancement BZ# 1054283 This update adds support for GUID Partition Table (GPT) disk labels on PreP partitions on the 64-bit PowerPC architectures. Users of parted are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
C.20. Statistics org.infinispan.interceptors.CacheMgmtInterceptor This component handles general statistics such as timings, hit/miss ratio, etc. Table C.31. Attributes Name Description Type Writable averageReadTime Average number of milliseconds for a read operation on the cache. long No averageWriteTime Average number of milliseconds for a write operation in the cache. long No elapsedTime Number of seconds since cache started. long No evictions Number of cache eviction operations. long No hitRatio Percentage hit/(hit+miss) ratio for the cache. double No hits Number of cache attribute hits. long No misses Number of cache attribute misses. long No numberOfEntries Number of entries currently in the cache. int No readWriteRatio Read/writes ratio for the cache. double No removeHits Number of cache removal hits. long No removeMisses Number of cache removals where keys were not found. long No stores Number of cache attribute PUT operations. long No timeSinceReset Number of seconds since the cache statistics were last reset. long No averageRemoveTime Average number of milliseconds for a remove operation in the cache long No Table C.32. Operations Name Description Signature resetStatistics Resets statistics gathered by this component. void resetStatistics() 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
Chapter 8. Enabling FIPS mode with RHEL image builder You can create a customized image and boot a FIPS-enabled RHEL image. Before you compose the image, you must change the value of the fips directive in your blueprint. Prerequisites You are logged in as the root user or a user who is a member of the weldr group. Procedure Create a plain text file in the Tom's Obvious, Minimal Language (TOML) format with the following content: Import the blueprint to the RHEL image builder server: List the existing blueprints to check whether the created blueprint is successfully imported and exists: Check whether the components and versions listed in the blueprint and their dependencies are valid: Build the customized RHEL image: Review the image status: Download the image: RHEL image builder downloads the image to the current directory path. The UUID number and the image size are displayed alongside: Verification Log in to the system image with the username and password that you configured in your blueprint. Check if FIPS mode is enabled:

Commands:
name = "system-fips-mode-enabled" description = "blueprint with FIPS enabled " version = "0.0.1" [customizations] fips = true [[customizations.user]] name = "admin" password = "admin" groups = ["users", "wheel"]
composer-cli blueprints push <blueprint-name> .toml
composer-cli blueprints show <blueprint-name>
composer-cli blueprints depsolve <blueprint-name>
composer-cli compose start \ <blueprint-name> \ <image-type> \
composer-cli compose status ... <UUID> FINISHED <date> <blueprint-name> <blueprint-version> <image-type> ...
composer-cli compose image <UUID>
<UUID-image-name.type> : <size> MB
fips-mode-setup --check FIPS mode is enabled.
8.161. python-beaker 8.161.1. RHBA-2013:1724 - python-beaker bug fix update Updated python-beaker packages that fix one bug and are now available for Red Hat Enterprise Linux 6. The python-beaker package provides Beaker, a web session and general caching library that includes Web Server Gateway Interface (WSGI) middleware for use in web applications. Bug Fix BZ# 983292 Previously, Beaker used the MD5 algorithm to produce a unique hex-encoded session identifier. However, this algorithm is not, by default, supported by Python's runtime in FIPS mode. Consequently, web applications that used Beaker failed to create new sessions in certain environments. With this update, MD5 has been replaced with the SHA1 algorithm and the subsequent hex encoding with the Base64 encoding scheme. As a result, Beaker works correctly in FIPS environment. Users of python-beaker are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Overview of model monitoring To ensure that machine-learning models are transparent, fair, and reliable, data scientists can use TrustyAI in OpenShift AI to monitor their data science models. Data scientists can monitor their data science models in OpenShift AI for the following metrics: Bias Check for unfair patterns or biases in data and model predictions to ensure your model's decisions are unbiased. Data drift Detect changes in input data distributions over time by comparing the latest real-world data to the original training data. Comparing the data identifies shifts or deviations that could impact model performance, ensuring that the model remains accurate and reliable.

Commands:
Appendix H. System Accounts H.1. Red Hat Virtualization Manager User Accounts A number of system user accounts are created to support Red Hat Virtualization when the rhevm package is installed. Each system user has a default user identifier (UID). The system user accounts created are: The vdsm user (UID 36 ). Required for support tools that mount and access NFS storage domains. The ovirt user (UID 108 ). Owner of the ovirt-engine Red Hat JBoss Enterprise Application Platform instance. The ovirt-vmconsole user (UID 498 ). Required for the guest serial console.

Commands:
Chapter 1. Installation Overview Installing a standalone Manager environment with local databases involves the following steps: Install and configure the Red Hat Virtualization Manager: Install a Red Hat Enterprise Linux machine for the Manager. Register the Manager machine with the Content Delivery Network and enable the Red Hat Virtualization Manager repositories. Install and Configure the Red Hat Virtualization Manager using engine-setup . Connect to the Administration Portal to add hosts and storage domains. Install hosts to run virtual machines on: Use either host type, or both: Red Hat Virtualization Host Red Hat Enterprise Linux Add the hosts to the Manager. Prepare storage to use for storage domains. You can use one of the following storage types: NFS iSCSI Fibre Channel (FCP) POSIX-compliant file system Local storage Red Hat Gluster Storage Add storage domains to the Manager. Important Keep the environment up to date. See https://access.redhat.com/articles/2974891 for more information. Since bug fixes for known issues are frequently released, Red Hat recommends using scheduled tasks to update the hosts and the Manager.

Commands:
21.9. virt-inspector: Inspecting Guest Virtual Machines This section provides information about inspecting guest virtual machines. 21.9.1. Introduction virt-inspector is a tool for inspecting a disk image to find out what operating system it contains. 21.9.2. Installation To install virt-inspector and the documentation, enter the following command: The documentation, including example XML output and a Relax-NG schema for the output, will be installed in /usr/share/doc/libguestfs-devel-*/ where * is replaced by the version number of libguestfs . 21.9.3. Running virt-inspector You can run virt-inspector against any disk image or libvirt guest virtual machine as shown in the following example: Or as shown here: The result will be an XML report ( report.xml ). The main components of the XML file are a top-level <operatingsytems> element containing usually a single <operatingsystem> element, similar to the following: Processing these reports is best done using W3C standard XPath queries. Red Hat Enterprise Linux 7 comes with the xpath command-line program, which can be used for simple instances. However, for long-term and advanced usage, you should consider using an XPath library along with your favorite programming language. As an example, you can list out all file system devices using the following XPath query: Or list the names of all applications installed by entering:

Commands:
yum install libguestfs-tools
virt-inspector -a disk.img > report.xml
virt-inspector -d GuestName > report.xml
<operatingsystems> <operatingsystem> <!-- the type of operating system and Linux distribution --> <name>linux</name> <distro>rhel</distro> <!-- the name, version and architecture --> <product_name>Red Hat Enterprise Linux Server release 6.4 </product_name> <major_version>6</major_version> <minor_version>4</minor_version> <package_format>rpm</package_format> <package_management>yum</package_management> <root>/dev/VolGroup/lv_root</root> <!-- how the filesystems would be mounted when live --> <mountpoints> <mountpoint dev="/dev/VolGroup/lv_root">/</mountpoint> <mountpoint dev="/dev/sda1">/boot</mountpoint> <mountpoint dev="/dev/VolGroup/lv_swap">swap</mountpoint> </mountpoints> < !-- filesystems--> <filesystem dev="/dev/VolGroup/lv_root"> <label></label> <uuid>b24d9161-5613-4ab8-8649-f27a8a8068d3</uuid> <type>ext4</type> <content>linux-root</content> <spec>/dev/mapper/VolGroup-lv_root</spec> </filesystem> <filesystem dev="/dev/VolGroup/lv_swap"> <type>swap</type> <spec>/dev/mapper/VolGroup-lv_swap</spec> </filesystem> <!-- packages installed --> <applications> <application> <name>firefox</name> <version>3.5.5</version> <release>1.fc12</release> </application> </applications> </operatingsystem> </operatingsystems>
virt-inspector GuestName | xpath //filesystem/@dev Found 3 nodes: -- NODE -- dev="/dev/sda1" -- NODE -- dev="/dev/vg_f12x64/lv_root" -- NODE -- dev="/dev/vg_f12x64/lv_swap"
virt-inspector GuestName | xpath //application/name [...long list...]
Chapter 4. Additional Configuration 4.1. Configuring Operating Systems with osinfo Red Hat Virtualization stores operating system configurations for virtual machines in /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties . This file contains default values such as os.other.devices.display.protocols.value = spice/qxl,vnc/vga,vnc/qxl . There are only a limited number of scenarios in which you would change these values: Adding an operating system that does not appear in the list of supported guest operating systems Adding a product key (for example, os.windows_10x64.productKey.value = ) Configuring the sysprep path for a Windows virtual machine (for example, os.windows_10x64.sysprepPath.value = USD{ENGINE_USR}/conf/sysprep/sysprep.w10x64 ) Important Do not edit the actual 00-defaults.properties file. Changes will be overwritten if you upgrade or restore the Manager. Do not change values that come directly from the operating system or the Manager, such as maximum memory size. To change the operating system configurations, create an override file in /etc/ovirt-engine/osinfo.conf.d/ . The file name must begin with a value greater than 00 , so that the file appears after /etc/ovirt-engine/osinfo.conf.d/00-defaults.properties , and ends with the extension, .properties . For example, 10-productkeys.properties overrides the default file, 00-defaults.properties . The last file in the file list has precedence over earlier files.

Commands:
B.28. gpxe B.28.1. RHBA-2011:0415 - gpxe bug fix update Updated gpxe packages that fix one bug are now available for Red Hat Enterprise Linux 6. The gpxe packages provide an open source Preboot Execution Environment (PXE) implementation and bootloader. gPXE also supports additional protocols such as DNS, HTTP, iSCSI and ATA over Ethernet. Bug Fix BZ# 680148 Previously, the virtIO gPXE driver padded all packets to maximum length. This could confuse some gateways because the Ethernet standard is to pad only packets of up to 64 bytes in length. Due to this issue, virtual machines with a virtIO NIC (network interface card) failed to connect to the PXE server behind a gateway. Subsequently, the PXE boot failed. This update pads only packets of up to 64 bytes in length. Now, virtual machines with a virtIO NIC connect to the same PXE server without further problems. All gPXE users are advised to upgrade to these updated packages which fix this bug.

Commands:
Chapter 2. Architectures Red Hat Enterprise Linux 8.5 is distributed with the kernel version 4.18.0-348, which provides support for the following architectures: AMD and Intel 64-bit architectures The 64-bit ARM architecture IBM Power Systems, Little Endian 64-bit IBM Z Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures . For a list of available subscriptions, see Subscription Utilization on the Customer Portal.

Commands:
Chapter 7. Disabling the Fuse Console You can disable the Fuse Console on Karaf so that it becomes inaccessible to all users without affecting any other component. Procedure To determine the hawtio-web bundle ID, use the following command to list the Fuse bundles that the Fuse Console uses: osgi:list | grep hawtio To stop the bundle, use the osgi:stop command. For example, if the hawtio :: Web console bundle has an ID of 246, type this command: osgi:stop 246 The bundle goes into the resolved state and you can no longer access the Fuse Console. Additional resources For more information about managing bundles, see the "Lifecycle Management" chapter of Deploying into Apache Karaf .

Commands: