mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Booting the installation media You can boot the Red Hat Enterprise Linux installation using a USB or DVD. You can register RHEL using the Red Hat Content Delivery Network (CDN). CDN is a geographically distributed series of web servers. These servers provide, for example, packages and updates to RHEL hosts with a valid subscription. During the installation, registering and installing RHEL from the CDN offers following benefits: Utilizing the latest packages for an up-to-date system immediately after installation and Integrated support for connecting to Red Hat Insights and enabling System Purpose. Prerequisite You have created a bootable installation media (USB or DVD). Procedure Power off the system to which you are installing Red Hat Enterprise Linux. Disconnect any drives from the system. Power on the system. Insert the bootable installation media (USB, DVD, or CD). Power off the system but do not remove the boot media. Power on the system. You might need to press a specific key or combination of keys to boot from the media or configure the Basic Input/Output System (BIOS) of your system to boot from the media. For more information, see the documentation that came with your system. The Red Hat Enterprise Linux boot window opens and displays information about a variety of available boot options. Use the arrow keys on your keyboard to select the boot option that you require, and press Enter to select the boot option. The Welcome to Red Hat Enterprise Linux window opens and you can install Red Hat Enterprise Linux using the graphical user interface. The installation program automatically begins if no action is performed in the boot window within 60 seconds. Optional: Edit the available boot options: UEFI-based systems: Press E to enter edit mode. Change the predefined command line to add or remove boot options. Press Enter to confirm your choice. BIOS-based systems: Press the Tab key on your keyboard to enter edit mode. Change the predefined command line to add or remove boot options. Press Enter to confirm your choice. Additional Resources Customizing the system in the installer Boot options reference

Commands:
7.6. Removing Lost Physical Volumes from a Volume Group If you lose a physical volume, you can activate the remaining physical volumes in the volume group with the --partial argument of the vgchange command. You can remove all the logical volumes that used that physical volume from the volume group with the --removemissing argument of the vgreduce command. It is recommended that you run the vgreduce command with the --test argument to verify what you will be destroying. Like most LVM operations, the vgreduce command is reversible in a sense if you immediately use the vgcfgrestore command to restore the volume group metadata to its state. For example, if you used the --removemissing argument of the vgreduce command without the --test argument and find you have removed logical volumes you wanted to keep, you can still replace the physical volume and use another vgcfgrestore command to return the volume group to its state.

Commands:
Chapter 18. PersistentClaimStorage schema reference Used in: JbodStorage , KafkaClusterSpec , KafkaNodePoolSpec , ZookeeperClusterSpec The type property is a discriminator that distinguishes use of the PersistentClaimStorage type from EphemeralStorage . It must have the value persistent-claim for the type PersistentClaimStorage . Property Property type Description type string Must be persistent-claim . size string When type=persistent-claim , defines the size of the persistent volume claim, such as 100Gi. Mandatory when type=persistent-claim . selector map Specifies a specific persistent volume to use. It contains key:value pairs representing labels for selecting such a volume. deleteClaim boolean Specifies if the persistent volume claim has to be deleted when the cluster is un-deployed. class string The storage class to use for dynamic volume allocation. id integer Storage identification number. It is mandatory only for storage volumes defined in a storage of type 'jbod'. overrides PersistentClaimStorageOverride array Overrides for individual brokers. The overrides field allows to specify a different configuration for different brokers.

Commands:
5.10. Additional Resources This section includes various resources that can be used to learn more about storage technologies and the Red Hat Enterprise Linux-specific subject matter discussed in this chapter. 5.10.1. Installed Documentation The following resources are installed in the course of a typical Red Hat Enterprise Linux installation, and can help you learn more about the subject matter discussed in this chapter. exports(5) man page -- Learn about the NFS configuration file format. fstab(5) man page -- Learn about the file system information configuration file format. swapoff(8) man page -- Learn how to disable swap partitions. df(1) man page -- Learn how to display disk space usage on mounted file systems. fdisk(8) man page -- Learn about this partition table maintenance utility program. mkfs(8) , mke2fs(8) man pages -- Learn about these file system creation utility programs. badblocks(8) man page -- Learn how to test a device for bad blocks. quotacheck(8) man page -- Learn how to verify block and inode usage for users and groups and optionally creates disk quota files. edquota(8) man page -- Learn about this disk quota maintenance utility program. repquota(8) man page -- Learn about this disk quota reporting utility program. raidtab(5) man page -- Learn about the software RAID configuration file format. mdadm(8) man page -- Learn about this software RAID array management utility program. lvm(8) man page -- Learn about Logical Volume Management. devlabel(8) man page -- Learn about persistent storage device access.

Commands:
13.4. Registering a Job Module Custom job plug-ins can be registered through the Certificate Manager Console. Registering a new module involves specifying the name of the module and the full name of the Java TM class that implements the module. To register a new job module: Create the custom job class. For this example, the custom job plug-in is called MyJob.java . Compile the new class. Create a directory in the CA's WEB-INF web directory to hold the custom classes, so that the CA can access them. Copy the new plug-in files into the new classes directory, and set the owner to the Certificate System system user ( pkiuser ). Register the plug-in. Log into the Certificate Manager Console. In the Configuration tab, select Job Scheduler in the left navigation tree. Select Jobs . The Job Instance tab opens, which lists any currently configured jobs. Select the Job Plugin Registration tab. Click Register to add the new module. In the Register Job Scheduler Plugin Implementation window, supply the following information: Plugin name. Type a name for the plug-in module. Class name. Type the full name of the class for this module; this is the path to the implementing Java TM class. If this class is part of a package, include the package name. For example, to register a class named customJob that is in a package named com.customplugins , type com.customplugins.customJob . Click OK . Note It is also possible to delete job modules, but this is not recommended. If it is necessary to delete a module, open the Job Plugin Registration tab as when registering a new module, select the module to delete, and click Delete . When prompted, confirm the deletion. Note pkiconsole is being deprecated.

Commands:
javac -d . -classpath USDCLASSPATH MyJob.java
mkdir /var/lib/pki/ instance_name /ca/webapps/ca/WEB-INF/classes
cp -pr com /var/lib/pki/ instance_name /ca/webapps/ca/WEB-INF/classes chown -R pkiuser:pkiuser /var/lib/pki/ instance_name /ca/webapps/ca/WEB-INF/classes
pkiconsole https://server.example.com:8443/ca
Chapter 12. Configuring alert notifications In OpenShift Container Platform, an alert is fired when the conditions defined in an alerting rule are true. An alert provides a notification that a set of circumstances are apparent within a cluster. Firing alerts can be viewed in the Alerting UI in the OpenShift Container Platform web console by default. After an installation, you can configure OpenShift Container Platform to send alert notifications to external systems. 12.1. Sending notifications to external systems In OpenShift Container Platform 4.16, firing alerts can be viewed in the Alerting UI. Alerts are not configured by default to be sent to any notification systems. You can configure OpenShift Container Platform to send alerts to the following receiver types: PagerDuty Webhook Email Slack Microsoft Teams Routing alerts to receivers enables you to send timely notifications to the appropriate teams when failures occur. For example, critical alerts require immediate attention and are typically paged to an individual or a critical response team. Alerts that provide non-critical warning notifications might instead be routed to a ticketing system for non-immediate review. Checking that alerting is operational by using the watchdog alert OpenShift Container Platform monitoring includes a watchdog alert that fires continuously. Alertmanager repeatedly sends watchdog alert notifications to configured notification providers. The provider is usually configured to notify an administrator when it stops receiving the watchdog alert. This mechanism helps you quickly identify any communication issues between Alertmanager and the notification provider. 12.2. Additional resources About OpenShift Container Platform monitoring Configuring alert notifications

Commands:
20.2. Displaying the virsh Version The virsh version command displays the current libvirt version and displays information about the local virsh client. For example: The virsh version --daemon is useful for getting information about the libvirtd version and package information, including information about the libvirt daemon that is running on the host.

Commands:
USD virsh version Compiled against library: libvirt 1.2.8 Using library: libvirt 1.2.8 Using API: QEMU 1.2.8 Running hypervisor: QEMU 1.5.3
USD virsh version --daemon Compiled against library: libvirt 1.2.8 Using library: libvirt 1.2.8 Using API: QEMU 1.2.8 Running hypervisor: QEMU 1.5.3 Running against daemon: 1.2.8
11.4. Schema Updates See Red Hat JBoss Data Virtualization Development Guide: Reference Material for supported DDL statements. To make schema updates persistent implementations should be provided for the following methods: String getViewDefinition(String vdbName, int vdbVersion, Table table); void setViewDefinition(String vdbName, int vdbVersion, Table table, String viewDefinition); String getInsteadOfTriggerDefinition(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation); void setInsteadOfTriggerDefinition(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation, String triggerDefinition); boolean isInsteadOfTriggerEnabled(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation); void setInsteadOfTriggerEnabled(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation, boolean enabled); String getProcedureDefinition(String vdbName, int vdbVersion, Procedure procedure); void setProcedureDefinition(String vdbName, int vdbVersion, Procedure procedure, String procedureDefinition); LinkedHashMap<String, String> getProperties(String vdbName, int vdbVersion, AbstractMetadataRecord record); void setProperty(String vdbName, int vdbVersion, AbstractMetadataRecord record, String name, String value);

Commands:
String getViewDefinition(String vdbName, int vdbVersion, Table table); void setViewDefinition(String vdbName, int vdbVersion, Table table, String viewDefinition); String getInsteadOfTriggerDefinition(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation); void setInsteadOfTriggerDefinition(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation, String triggerDefinition); boolean isInsteadOfTriggerEnabled(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation); void setInsteadOfTriggerEnabled(String vdbName, int vdbVersion, Table table, Table.TriggerEvent triggerOperation, boolean enabled); String getProcedureDefinition(String vdbName, int vdbVersion, Procedure procedure); void setProcedureDefinition(String vdbName, int vdbVersion, Procedure procedure, String procedureDefinition); LinkedHashMap<String, String> getProperties(String vdbName, int vdbVersion, AbstractMetadataRecord record); void setProperty(String vdbName, int vdbVersion, AbstractMetadataRecord record, String name, String value);
Chapter 1. Introduction and goals of this article Now that you have installed Red Hat JBoss Data Virtualization successfully and explored the quick starts, you can look at the Dashboard Builder. Note that this article is aimed at more advanced users and it requires you to have a data source already configured. If you are a less advanced user, Red Hat recommends you read the Red Hat JBoss Data Virtualization Installation Guide and the Administration and Configuration Guide before proceeding to work through this article.

Commands:
5.20. byacc 5.20.1. RHBA-2012:0749 - byacc bug fix update An updated byacc package that fixes one bug is now available for Red Hat Enterprise Linux 6. Berkeley Yacc (byacc) is a public domain look-ahead left-to-right (LALR) parser generator used by many programs during their build process. Bug Fix BZ# 743343 Byacc's maximum stack depth was reduced from 10000 to 500 between byacc releases. If deep enough else-if structures were present in source code being compiled with byacc, this could lead to out-of-memory conditions, resulting in YACC Stack Overflow and build failure. This updated release restores the maximum stack depth to its original value, 10000. Note: the underlying LR algorithm still imposes a hard limit on the number of parsable else-if statements. Restoring the maximum stack depth to its original value means source code with deep else-if structures that previously compiled against byacc will again do so. All byacc users should upgrade to this updated package, which fixes this bug.

Commands:
Chapter 3. Registering and connecting systems to Red Hat Insights to execute tasks To work with Red Hat Insights, you need to register systems to Insights, and enable system communication with Insights. In addition to communicating with Insights, you need to enable and install dependencies on Satellite 6.11+, Remote Host Configuration (rhc), rhc-worker-playbook and ansible , so that you can use task services, and other services in the Automation Toolkit. For more information about enabling system communication with Insights, and addressing dependencies, see: Enabling host communication with Insights in the Red Hat Insights Remediations Guide . Additional resources Red Hat Insights data and application security

Commands:
5.30. conman 5.30.1. RHEA-2012:0401 - conman enhancement update An updated conman package that adds one enhancement is now available for Red Hat Enterprise Linux 6. ConMan is a serial console management program designed to support a large number of console devices and simultaneous users. ConMan currently supports local serial devices and remote terminal servers. Enhancement BZ# 738967 Users are now able to configure the maximum number of open files. This allows the conman daemon to easily manage a large number of nodes. All users of conman are advised to upgrade to this updated package, which adds this enhancement.

Commands:
9.2. Using Add/Remove Software To find and install a new package, on the GNOME panel click on System Administration Add/Remove Software , or run the gpk-application command at the shell prompt. Figure 9.4. PackageKit's Add/Remove Software window 9.2.1. Refreshing Software Sources (Yum Repositories) PackageKit refers to Yum repositories as software sources. It obtains all packages from enabled software sources. You can view the list of all configured and unfiltered (see below) Yum repositories by opening Add/Remove Software and clicking System Software sources . The Software Sources dialog shows the repository name, as written on the name= <My Repository Name> field of all [ repository ] sections in the /etc/yum.conf configuration file, and in all repository .repo files in the /etc/yum.repos.d/ directory. Entries which are checked in the Enabled column indicate that the corresponding repository will be used to locate packages to satisfy all update and installation requests (including dependency resolution). You can enable or disable any of the listed Yum repositories by selecting or clearing the check box. Note that doing so causes PolicyKit to prompt you for superuser authentication. The Enabled column corresponds to the enabled= <1 or 0> field in [ repository ] sections. When you click the check box, PackageKit inserts the enabled= <1 or 0> line into the correct [ repository ] section if it does not exist, or changes the value if it does. This means that enabling or disabling a repository through the Software Sources window causes that change to persist after closing the window or rebooting the system. Note that it is not possible to add or remove Yum repositories through PackageKit. Note Checking the box at the bottom of the Software Sources window causes PackageKit to display source RPM, testing and debuginfo repositories as well. This box is unchecked by default. After making a change to the available Yum repositories, click on System Refresh package lists to make sure your package list is up-to-date.

Commands:
B.3. Using KVM Virtualization on ARM Systems Important KVM virtualization is provided in Red Hat Enterprise Linux 7.5 and later for the 64-bit ARM architecture. As such, KVM virtualization on ARM systems is not supported by Red Hat, not intended for use in a production environment, and may not address known security vulnerabilities. In addition, because KVM virtualization on ARM is still in rapid development, the information below is not guaranteed to be accurate or complete. Installation To use install virtualization on Red Hat Enterprise Linux 7.5 for ARM: Install the host system from the bootable image on the Customer Portal . After the system is installed, install the virtualization stack on the system by using the following command: Make sure you have the Optional channel enabled for the installation to succeed. For more information, see Adding the Optional and Supplementary Repositories . Architecture Specifics KVM virtualization on Red Hat Enterprise Linux 7.5 for the 64-bit ARM architecture differs from KVM on AMD64 and Intel 64 systems in the following: PXE booting is only supported with the virtio-net-device and virtio-net-pci network interface controllers (NICs). In addition, the built-in VirtioNetDxe driver of the ARM Architecture Virtual Machine Firmware (AAVMF) needs to be used for PXE booting. Note that iPXE option ROMs are not supported. Only up to 123 virtual CPUs (vCPUs) can be allocated to a single guest.

Commands:
yum install qemu-kvm-ma libvirt libvirt-client virt-install AAVMF
7.123. libtdb 7.123.1. RHBA-2013:0353 - libtdb bug fix and enhancement update Updated libtdb packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6 The libtdb packages provide a library that implements the Trivial Database (TDB). TDB is a simple hashed database that uses internal locking to allow multiple simultaneous writers and readers. Note The libtdb packages have been upgraded to upstream version 1.2.10, which provides a number of bug fixes and enhancements over the version. These updated libtdb packages are compliant with requirements of Samba 4. (BZ# 766334 ) All users of libtdb are advised to upgrade to these updated packages, which fix these bugs and adds these enhancements.

Commands:
5.243. pidgin 5.243.1. RHSA-2012:1102 - Moderate: pidgin security update Updated pidgin packages that fix three security issues are now available for Red Hat Enterprise Linux 5 and 6. 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. Pidgin is an instant messaging program which can log in to multiple accounts on multiple instant messaging networks simultaneously. Security Fixes CVE-2012-1178 A flaw was found in the way the Pidgin MSN protocol plug-in processed text that was not encoded in UTF-8. A remote attacker could use this flaw to crash Pidgin by sending a specially-crafted MSN message. CVE-2012-2318 An input validation flaw was found in the way the Pidgin MSN protocol plug-in handled MSN notification messages. A malicious server or a remote attacker could use this flaw to crash Pidgin by sending a specially-crafted MSN notification message. CVE-2012-3374 A buffer overflow flaw was found in the Pidgin MXit protocol plug-in. A remote attacker could use this flaw to crash Pidgin by sending a MXit message containing specially-crafted emoticon tags. Red Hat would like to thank the Pidgin project for reporting the CVE-2012-3374 issue. Upstream acknowledges Ulf Harnhammar as the original reporter of CVE-2012-3374. All Pidgin users should upgrade to these updated packages, which contain backported patches to resolve these issues. Pidgin must be restarted for this update to take effect.

Commands:
Chapter 12. Invalid score detection If you use the environmentMode class and specify the value as FULL_ASSERT or FAST_ASSERT , the environment mode detects score corruption in the incremental score calculation. However, doing this will not verify that your score calculator implements your score constraints the way that your business wants. For example, one constraint might consistently match the wrong pattern. To verify the constraints against an independent implementation, configure an assertionScoreDirectorFactory class: <environmentMode>FAST_ASSERT</environmentMode> ... <scoreDirectorFactory> <constraintProviderClass>org.optaplanner.examples.nqueens.optional.score.NQueensConstraintProvider</constraintProviderClass> <assertionScoreDirectorFactory> <easyScoreCalculatorClass>org.optaplanner.examples.nqueens.optional.score.NQueensEasyScoreCalculator</easyScoreCalculatorClass> </assertionScoreDirectorFactory> </scoreDirectorFactory> In this example, the NQueensConstraintProvider implementation is validated by the EasyScoreCalculator . Note This technique works well to isolate score corruption, but to verify that the constraint implements the real business needs, a unit test with a ConstraintVerifier is usually better.

Commands:
<environmentMode>FAST_ASSERT</environmentMode> <scoreDirectorFactory> <constraintProviderClass>org.optaplanner.examples.nqueens.optional.score.NQueensConstraintProvider</constraintProviderClass> <assertionScoreDirectorFactory> <easyScoreCalculatorClass>org.optaplanner.examples.nqueens.optional.score.NQueensEasyScoreCalculator</easyScoreCalculatorClass> </assertionScoreDirectorFactory> </scoreDirectorFactory>