mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 46. Virtualization Nested virtualization As a Technology Preview, Red Hat Enterprise Linux 7 offers nested virtualization. This feature enables KVM to launch guests that can act as hypervisors and create their own guests. For more information, see the Red Hat Enterprise Linux 7 Virtualization Deployment and Administration Guide. (BZ#1187762) USB 3.0 support for KVM guests USB 3.0 host adapter (xHCI) emulation for KVM guests remains a Technology Preview in Red Hat Enterprise Linux 7.3. (BZ#1103193) Select Intel network adapters now support SR-IOV as a guest on Hyper-V In this update for Red Hat Enterprise Linux guest virtual machines running on Hyper-V, a new PCI passthrough driver adds the ability to use the single-root I/O virtualization (SR-IOV) feature for Intel network adapters supported by the ixgbevf driver. This ability is enabled when the following conditions are met: SR-IOV support is enabled for the network interface controller (NIC) SR-IOV support is enabled for the virtual NIC SR-IOV support is enabled for the virtual switch The virtual function (VF) from the NIC is attached to the virtual machine. The feature is currently supported with Microsoft Windows Server 2016 Technical Preview 5. (BZ#1348508) Driver added for devices that connect over a PCI Express bus in guest virtual machine under Hyper-V In this update, a new driver was added that exposes a root PCI bus when a devices that connects over a PCI Express bus is passed through to a Red Hat Enterprise Linux guest virtual machine running on the Hyper-V hypervisor. The feature is currently supported with Microsoft Windows Server 2016 Technical Preview 5. (BZ#1302147) Open Virtual Machine Firmware The Open Virtual Machine Firmware (OVMF) is available as a Technology Preview in Red Hat Enterprise Linux 7. OVMF is a UEFI secure boot environment for AMD64 and Intel 64 guests. However, OVMF is not bootable with virtualization components available in RHEL 7. Note that OVMF is fully supported in RHEL 8.

Commands:
Appendix A. The virt group profile The /var/lib/glusterd/groups/virt file defines a configuration that is used for all volumes in the virt group. Defining a group configuration and adding volumes to a group helps save time and effort when you want to update the settings on all volumes in the group. The default contents of the /var/lib/glusterd/groups/virt file are as follows: The majority of these settings prevent caching in the client stack. The cluster.eager-lock option optimizes write performance by using synchronous replication when there is a single writer to a file. The cluster.data-self-heal option specifies how self-heal operations are performed. The features.shard and features.shard-block-size options enable sharding behavior in the volume and set a block size appropriate for storing disk images. The cluster.quorum-type=auto and cluster.server-quorum-type options enable client and server-side quorum to help ensure consistency and to prevent split-brain scenarios. Note The default settings of cluster.quorum-type=auto and cluster.server-quorum-type=server provide consistency at the cost of fault tolerance. Using these settings, if server-side quorum is not met, virtual machines pause because volumes are not available. If client-side quorum is not met, virtual machines pause even though a read-only replica pair is available. Manual intervention is then required to make the VMs resume the operations after the quorum is restored. If fault tolerance is preferred over consistency, disable server-side and client-side quorum with the following commands: See Supported Volume Options in the Red Hat Gluster Storage 3.5 Administration Guide for more information about any of these settings.

Commands:
performance.quick-read=off performance.read-ahead=off performance.io-cache=off performance.low-prio-threads=32 network.remote-dio=enable cluster.eager-lock=enable cluster.quorum-type=auto cluster.server-quorum-type=server cluster.data-self-heal-algorithm=full cluster.locking-scheme=granular cluster.shd-max-threads=8 cluster.shd-wait-qlength=10000 features.shard=on user.cifs=off cluster.choose-local=off client.event-threads=4 server.event-threads=4 performance.client-io-threads=on
gluster volume reset volname server-quorum-type gluster volume reset volname quorum-type
2.2.6. NSS Shared Databases The NSS shared database format, introduced on NSS 3.12, is now available in Red Hat Enterprise Linux 6. This encompasses a number of new features and components to improve access and usability. Included, is the NSS certificate and key database which are now sqlite-based and allow for concurrent access. The legacy key3.db and cert8.db are also replaced with new SQL databases called key4.db and cert9.db . These new databases will store PKCS #11 token objects, which are the same as what is currently stored in cert8.db and key3.db . Having support for shared databases enables a system-wide NSS database. It resides in /etc/pki/nssdb where globally trusted CA certificates become accessible to all applications. The command rv = NSS_InitReadWrite("sql:/etc/pki/nssdb"); initializes NSS for applications. If the application is run with root privileges, then the system-wide database is available on a read and write basis. However, if it is run with normal user privileges it becomes read only. Additionally, a PEM PKCS #11 module for NSS allows applications to load into memory certificates and keys stored in PEM-formatted files (for example, those produced by openssl). 2.2.6.1. Backwards Compatibility The binary compatibility guarantees made by NSS upstream are preserved in NSS for Red Hat Enterprise Linux 6. This guarantee states that NSS used in Red Hat Enterprise Linux 6 is backwards compatible with all older NSS 3.x shared libraries. Therefore, a program linked with an older NSS 3.x shared library will work without recompiling or relinking, and any applications that restrict the use of NSS APIs to the NSS Public Functions remain compatible with future versions of the NSS shared libraries.

Commands:
8.4.3. Scanning the System The most important functionality of oscap is to perform configuration and vulnerability scans of a local system. The following is a general syntax of the respective command: oscap [ options ] module eval [ module_operation_options_and_arguments ] The oscap utility can scan systems against the SCAP content represented by both, an XCCDF (The eXtensible Configuration Checklist Description Format) benchmark and OVAL (Open Vulnerability and Assessment Language) definitions. The security policy can have a form of a single OVAL or XCCDF file or multiple separate XML files where each file represents a different component (XCCDF, OVAL, CPE, CVE, and others). The result of a scan can be printed to both, standard output and an XML file. The result file can be then further processed by oscap in order to generate a report in a human-readable format. The following examples illustrate the most common usage of the command. Example 8.6. Scanning the System Using the SSG OVAL definitions To scan your system against the SSG OVAL definition file while evaluating all definitions, run the following command: The results of the scan will be stored as the scan-oval-results.xml file in the current directory. Example 8.7. Scanning the System Using the SSG OVAL definitions To evaluate a particular OVAL definition from the security policy represented by the SSG data stream file, run the following command: The results of the scan will be stored as the scan-oval-results.xml file in the current directory. Example 8.8. Scanning the System Using the SSG XCCDF benchmark To perform the SSG XCCDF benchmark for the xccdf_org.ssgproject.content_profile_rht-ccp profile on your system, run the following command: The results of the scan will be stored as the scan-xccdf-results.xml file in the current directory. Note The --profile command-line argument selects the security profile from the given XCCDF or data stream file. The list of available profiles can be obtained by running the oscap info command. If the --profile command-line argument is omitted the default XCCDF profile is used as required by SCAP standard. Note that the default XCCDF profile may or may not be an appropriate security policy.

Commands:
~]USD oscap oval eval --results scan-oval-results.xml /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml
~]USD oscap oval eval --id oval:ssg:def:100 --results scan-oval-results.xml /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml
~]USD oscap xccdf eval --profile xccdf_org.ssgproject.content_profile_rht-ccp --results scan-xccdf-results.xml /usr/share/xml/scap/ssg/content/ssg-rhel6-ds.xml
8.22. cpupowerutils 8.22.1. RHBA-2013:1533 - cpupowerutils bug fix and enhancement update Updated cpupowerutils packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The cpupowerutils packages provide a suite of tools to manage power states on appropriately enabled central processing units (CPU). Bug Fixes BZ# 886225 Previously, some of the commands in the cpupowerutils packages were missing manual pages. Manual pages for the turbostat, x86_energy_perf_policy, cpufreq-bench, and cpufreq-bench_plot.sh commands have been added, thus fixing this bug. BZ# 886226 If a non-root user tried to run the cpufreq-bench utility, it terminated unexpectedly with a segmentation fault, and an ABRT notification appeared on the desktop. With this update, a warning message is displayed to the user instead, informing them that it is necessary to run the utility as root. BZ# 886227 Prior to this update, the x86_energy_perf_policy utility failed when it tried to open the /dev/cpu/*/msr/ directory. Consequently, a "permission denied" error message was returned. With this update, a new error message explains that the command needs root privileges and x86_energy_perf_policy cleanly exits. BZ# 886228 Previously, the interactive help for the x86_energy_perf_policy utility was short and confusing. The help text has been expanded to clarify the meaning of the command-line options. BZ# 914623 Due to the missing implementation for the "cpupower set -m" command, the error message is returned upon launching the command. Previously, this message wrongly implied that the sched-mc utility is not supported on the system. This update clarifies the message to clearly state that sched-mc is not yet implemented. BZ# 914787 Previously, running the "cpupower -v" or "cpupower --version" commands returned incorrect version information. This bug has been fixed and a selected component of cpupower now reports the correct version-release number. Enhancement BZ# 852831 Intel turbostat v3.0 utility has been included in Red Hat Enterprise Linux. The utility is used to read current CPU core frequency and active C-states. Users of cpupowerutils are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
B.93. system-config-users B.93.1. RHBA-2011:0221 - system-config-users bug fix update An updated system-config-users package that fixes a bug that caused new user creation to fail in some circumstances is now available. system-config-users is a graphical utility for administrating users and groups. It depends on the libuser library. Bug Fix BZ# 672822 When creating users, or more specifically their home directories, system-config-users relied on the access() system call to check if a directory was writable (and, consequently, whether a new home directory could be created in the requested location). The access() system call returns reliable information for POSIX-compliant (or mostly POSIX-compliant) file-systems only. In some cases, therefore, relying on the information returned by access() could result in user creation failing. If, for example, system-config-users was directed to create a user with a home folder in a directory managed by an auto-mounter (such as /net), access() returned inaccurate information and user creation subsequently failed. With this update, system-config-users no longer relies on access(), or other operating system functions, in such cases: it now attempts to create the home directory and checks whether it has succeeded in doing so. As well, if the chosen location is not writable, system-config-users returns an alert to this effect and requests 'a writable location' be chosen rather than simply writing errors to the terminal and failing. Users should upgrade to this updated package, which resolves this issue.

Commands:
7.76. gstreamer-plugins-base 7.76.1. RHEA-2012:1473 - gstreamer-plugins-base enhancement update Updated gstreamer-plugins-base packages thatadd one enhancement are now available for Red Hat Enterprise Linux 6. The gstreamer-plugins-base packages provide a collection of base plug-ins for the GStreamer streaming media framework. Enhancement BZ# 755777 This update adds color-matrix support for color conversions to the ffmpegcolorspace plugin. All users of gstreamer-plugins-base are advised to upgrade to these updated packages, which add this enhancement.

Commands:
11.2. Overview of Supported File Systems This section shows basic technical information on each file system supported by Red Hat Enterprise Linux 6. Table 11.1. Technical Specifications of Supported File Systems File System Max Supported Size Max File Offset Max Subdirectories (per directory) Max Depth of Symbolic Links ACL Support Details Ext2 8TB 2TB 32,000 8 Yes N/A Ext3 16TB 2TB 32,000 8 Yes Chapter 5, The Ext3 File System Ext4 16TB 16TB [a] Unlimited [b] 8 Yes Chapter 6, The Ext4 File System XFS 100TB 100TB [c] Unlimited 8 Yes Chapter 8, The XFS File System [a] This maximum file size is based on a 64-bit machine. On a 32-bit machine, the maximum files size is 8TB. [b] When the link count exceeds 65,000, it is reset to 1 and no longer increases. [c] This maximum file size is only on 64-bit machines. Red Hat Enterprise Linux does not support XFS on 32-bit machines. Note The listed maximum file and file system sizes are what Red Hat has tested and supports. This does not take into account the theoretical maximum limits. Both the maximum supported size and maximum file offset columns assume 4k blocks.

Commands:
5.10.3. Related Books The following books discuss various issues related to storage and are good resources for Red Hat Enterprise Linux system administrators. The Installation Guide ; Red Hat, Inc -- Contains instructions on partitioning hard drives during the Red Hat Enterprise Linux installation process as well as an overview of disk partitions. The Reference Guide ; Red Hat, Inc -- Contains detailed information on the directory structure used in Red Hat Enterprise Linux and an overview of NFS. The System Administrators Guide ; Red Hat, Inc -- Includes chapters on file systems, RAID, LVM, devlabel , partitioning, disk quotas, NFS, and Samba. Linux System Administration: A User's Guide by Marcel Gagne; Addison Wesley Professional -- Contains information on user and group permissions, file systems and disk quota, NFS and Samba. Linux Performance Tuning and Capacity Planning by Jason R. Fink and Matthew D. Sherer; Sams -- Contains information on disk, RAID, and NFS performance. Linux Administration Handbook by Evi Nemeth, Garth Snyder, and Trent R. Hein; Prentice Hall -- Contains information on file systems, handling disk drives, NFS, and Samba.

Commands:
Chapter 50. Exporting, importing, and deploying dashboards After you create a dashboard in Business Central, you can export the dashboard data and import it in another instance of Business Central, in Dashbuilder Runtime, or in Dashbuilder Standalone. Note This feature is only accessible by administrator users. 50.1. Exporting dashboard data You can export all the dashboard data such as datasets from Business Central as a ZIP file. Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Dashbuilder Data Transfer . On the Dashbuilder Data Transfer page, click Export all . An export.zip file containing all dashboard data is downloaded. The export.zip file structure is separated by data type, as shown in the following example: 50.2. Importing Business Central dashboards You can import Dashbuilder data to Business Central from a ZIP file if the archive is structured in the same way as the following example: Procedure In Business Central, select the Admin icon in the upper-right corner of the screen and select Dashbuilder Data Transfer . Warning You should only import dashboard data to a clean installation of Red Hat Decision Manager in order to avoid overwriting data on an existing system. On the Dashbuilder Data Transfer page, click the Choose File icon. Navigate to the ZIP file you want to import and select the file. Click the Upload icon. Click Import .

Commands:
dashbuilder/datasets/definitions/dataset-example1.dset dashbuilder/datasets/definitions/dataset-example2.dset dashbuilder/datasets/readme.md VERSION
dashbuilder/datasets/definitions/dataset-example1.dset dashbuilder/datasets/definitions/dataset-example2.dset dashbuilder/datasets/readme.md VERSION
22.4.5. Installing via FTP, HTTP, or HTTPS Important When you provide a URL to an installation source, you must explicitly specify http:// or https:// or ftp:// as the protocol. The URL dialog applies only if you are installing from a FTP, HTTP, or HTTPS server (if you selected URL in the Installation Method dialog). This dialog prompts you for information about the FTP, HTTP, or HTTPS server from which you are installing Red Hat Enterprise Linux. If you used the repo=ftp or repo=http boot options, you already specified a server and path. Enter the name or IP address of the FTP, HTTP, or HTTPS site from which you are installing, and the name of the directory that contains the /images directory for your architecture. For example: /mirrors/redhat/rhel-6.9/Server/s390x/ To install via a secure HTTPS connection, specify https:// as the protocol. Specify the address of a proxy server, and if necessary, provide a port number, username, and password. If everything was specified properly, a message box appears indicating that files are being retrieved from the server. If your FTP, HTTP, or HTTPS server requires user authentication, specify user and password as part of the URL as follows: {ftp|http|https}://<user>:<password>@<hostname>[:<port>]/<directory>/ For example: http://install:rhel6.9pw@name.example.com/mirrors/redhat/rhel-6.9/Server/s390x/ Figure 22.7. URL Setup Dialog Proceed with Chapter 23, Installation Phase 3: Installing Using Anaconda .

Commands:
12.4.3. Command Line Options An rndc command takes the following form: When executing rndc on a properly configured localhost, the following commands are available: halt - Stops the named service immediately. querylog - Logs all queries made to this nameserver. refresh - Refreshes the nameserver's database. reload - Reloads the zone files but keeps all other previously cached responses. This command also allows changes to zone files without losing all stored name resolutions. If changes only affected a specific zone, reload only that specific zone by adding the name of the zone after the reload command. stats - Dumps the current named statistics to the /var/named/named.stats file. stop - Stops the server gracefully, saving any dynamic update and Incremental Zone Transfers ( IXFR ) data before exiting. Occasionally, it may be necessary to override the default settings in the /etc/rndc.conf file. The following options are available: -c <configuration-file> - Specifies the alternate location of a configuration file. -p <port-number> - Specifies a port number to use for the rndc connection other than port 953, the default. -s <server> - Specifies a server other than the default-server listed in /etc/rndc.conf . -y <key-name> - Specifies a key other than the default-key option in /etc/rndc.conf . Additional information about these options can be found in the rndc man page.

Commands:
rndc <options> <command> <command-options>
Chapter 4. Deprecated components The components listed in this section have been deprecated. 4.1. Business Optimizer Business Optimizer (OptaPlanner) 8.13.x, included as part of Red Hat Process Automation Manager, is in maintenance support. For the latest supported versions of OptaPlanner (8.29 and later) upgrade to Red Hat build of OptaPlanner, the newest addition to Red Hat Application Foundations. For more info, see Red Hat build of OptaPlanner is now available in Red Hat Application Foundations . 4.2. OptaPlanner 7 Both OptaPlanner 7 and OptaPlanner 8 are included with Red Hat Process Automation Manager 7.13, but OptaPlanner 7 is deprecated and might be removed in a future release. For information about migrating your OptaPlanner 7 projects to OptaPlanner 8, see Upgrading your Red Hat build of OptaPlanner projects to OptaPlanner 8 . 4.3. OptaPlanner tooling components in Business Central The following OptaPlanner tooling in Business Central is part of OptaPlanner 7. They are deprecated and might be removed in a future release. Data modeler annotations Guided rule editor actions for OptaPlanner score modification Solver assets 4.4. Red Hat OpenShift Container Platform 3 Support for Red Hat OpenShift Container Platform 3 is removed in this release 4.5. Red Hat Enterprise Linux 7 Support for Red Hat Enterprise Linux 7 is deprecated in Red Hat Process Automation Manager and features and will be removed in a future release. 4.6. Support for JDK 8 Support for JDK 8 is deprecated in Red Hat Process Automation Manager and might be removed in a future release. For a complete list of supported JDK configurations, see Red Hat Process Automation Manager 7 Supported Configurations . 4.7. Legacy kie-pmml dependency The legacy kie-pmml dependency was deprecated with Red Hat Process Automation Manager 7.10.0 and will be replaced in a future Red Hat Process Automation Manager release. For more information, see Designing a decision service using PMML models . 4.8. Support for OSGi framework integration Support for integration with the OSGi framework is deprecated in Red Hat Process Automation Manager. It does not receive any new enhancements or features and will be removed in a future release. The decision and process engine integration with the OSGi framework is currently incompatible with Fuse version 7.8. If you intend to use the OSGi framework, continue to use Red Hat Process Automation Manager version 7.9 with Fuse version 7.7 until Fuse version 7.9 is available and certified. 4.9. Support for the RuleUnit API The Red Hat Process Automation Manager RuleUnit API is deprecated due to incompatibility with the Kogito RuleUnit API. 4.10. Legacy Test Scenarios tool The legacy Test Scenarios tool was deprecated in Red Hat Process Automation Manager version 7.3.0. It will be removed in a future Red Hat Process Automation Manager release. Use the new Test Scenarios designer instead. 4.11. Support for HACEP High available (HA) event-driven decisioning, including Complex Event Processing (CEP), is deprecated due to end of support for AMQ Streams 1.x.

Commands: