mtpti5iD/redhat-docs_dataset huggingface dataset:
4.59. fence-virt 4.59.1. RHBA-2011:1566 - fence-virt bug fix and enhancement update Updated fence-virt packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The fence-virt packages provide a fencing agent for virtual machines as well as a host agent which processes fencing requests. Bug Fixes BZ# 719645 Prior to this update, the domain parameter was missing from the metadata. As a consequence, existing configurations utilizing the domain parameter did not function correctly when fencing. This update adds the domain parameter for compatibility. Now, existing configurations work as expected. BZ# 720767 Prior to this update, hash mismatches falsely returned successes for fencing. As a consequence, data corruption could occur in live-hang scenarios. This update corrects the hash handling of mismatches. Now, no more false successes are returned and the data integrity is preserved. Enhancement BZ# 691200 With this update, the libvirt-qpid plugin now operates using QMF version 2. All users of fence-virt are advised to upgrade to these updated packages, which fix these bugs and add this enhancement. 4.59.2. RHBA-2012:0485 - fence-virt bug fix update Updated fence-virt packages that fix one bug are now available for Red Hat Enterprise Linux 6. The fence-virt packages provide a fencing agent for virtual machines as well as a host agent which processes fencing requests. Bug Fix BZ# 807270 Previously, the libvirt-qpid plug-in was linked directly against Qpid libraries instead of being linked only against QMFv2 libraries. As a consequence, newer versions of Qpid libraries could not be used with the libvirt-qpid plug-in. This update modifies the appropriate makefile so that libvirt-qpid is no longer linked directly against the Qpid libraries. The libvirt-qpid plug-in does not have to be re-linked to work with the newer Qpid libraries. All users of fence-virt are advised to upgrade to these updated packages, which fix this bug.

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-05-30 17:23:09 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
9.12. Setting SASL Mechanisms Per default, Directory Server enables all mechanisms the simple authentication and security layer (SASL) library supports. These are listed in the root dse supportedSASLMechanisms parameter. To enable specific SASL mechanisms, set the nsslapd-allowed-sasl-mechanisms attribute in the cn=config entry. For example, to enable only the GSSAPI and DIGEST-MD5 mechanism, run: Note Even if EXTERNAL is not listed in the nsslapd-allowed-sasl-mechanisms parameter, this mechanism is always enabled. For further details, see the corresponding section in the Red Hat Directory Server Configuration, Command, and File Reference .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-allowed-sasl-mechanisms="GSSAPI, DIGEST-MD5" Successfully replaced "nsslapd-allowed-sasl-mechanisms"
5.72. fprintd 5.72.1. RHBA-2012:0912 - fprintd bug fix update Updated fprintd packages that fix one bug are now available for Red Hat Enterprise Linux 6. The fprintd packages contains a D-Bus service to access fingerprint readers. Bug Fix BZ# 665837 Previously, if no USB support was available on a machine (for example, virtual machines on a hypervisor that disabled USB support for guests), the fprintd daemon received the SIGABRT signal, and therefore terminated abnormally. Such crashes did not cause any system failure; however, the Automatic Bug Reporting Tool (ABRT) was alerted every time. With this update, the underlying code has been modified so that the fprintd daemon now exits gracefully on machines with no USB support. All users of fprintd are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. AMQ Streams installation methods You can install AMQ Streams on OpenShift 4.12 and later in two ways. Installation method Description Installation artifacts (YAML files) Download Red Hat AMQ Streams 2.5 OpenShift Installation and Example Files from the AMQ Streams software downloads page . Deploy the YAML installation artifacts to your OpenShift cluster using oc . You start by deploying the Cluster Operator from install/cluster-operator to a single namespace, multiple namespaces, or all namespaces. You can also use the install/ artifacts to deploy the following: AMQ Streams administrator roles ( strimzi-admin ) A standalone Topic Operator ( topic-operator ) A standalone User Operator ( user-operator ) AMQ Streams Drain Cleaner ( drain-cleaner ) OperatorHub Use the AMQ Streams operator in the OperatorHub to deploy AMQ Streams to a single namespace or all namespaces. For the greatest flexibility, choose the installation artifacts method. The OperatorHub method provides a standard configuration and allows you to take advantage of automatic updates. Note Installation of AMQ Streams using Helm is not supported.

Commands:
B.102. webkitgtk B.102.1. RHSA-2011:0177 - Moderate: webkitgtk security update Updated webkitgtk packages that fix several security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. WebKitGTK+ is the port of the portable web rendering engine WebKit to the GTK+ platform. CVE-2010-1782 , CVE-2010-1783 , CVE-2010-1784 , CVE-2010-1785 , CVE-2010-1787 , CVE-2010-1788 , CVE-2010-1790 , CVE-2010-1792 , CVE-2010-1807 , CVE-2010-1814 , CVE-2010-3114 , CVE-2010-3116 , CVE-2010-3119 , CVE-2010-3255 , CVE-2010-3812 , CVE-2010-4198 Multiple memory corruption flaws were found in WebKit. Malicious web content could cause an application using WebKitGTK+ to crash or, potentially, execute arbitrary code with the privileges of the user running the application. CVE-2010-1780 , CVE-2010-1786 , CVE-2010-1793 , CVE-2010-1812 , CVE-2010-1815 , CVE-2010-3113 , CVE-2010-3257 , CVE-2010-4197 , CVE-2010-4204 Multiple use-after-free flaws were found in WebKit. Malicious web content could cause an application using WebKitGTK+ to crash or, potentially, execute arbitrary code with the privileges of the user running the application. CVE-2010-4206 , CVE-2010-4577 Two array index errors, leading to out-of-bounds memory reads, were found in WebKit. Malicious web content could cause an application using WebKitGTK+ to crash. CVE-2010-3115 A flaw in WebKit could allow malicious web content to trick a user into thinking they are visiting the site reported by the location bar, when the page is actually content controlled by an attacker. CVE-2010-3259 It was found that WebKit did not correctly restrict read access to images created from the "canvas" element. Malicious web content could allow a remote attacker to bypass the same-origin policy and potentially access sensitive image data. CVE-2010-3813 A flaw was found in the way WebKit handled DNS prefetching. Even when it was disabled, web content containing certain "link" elements could cause WebKitGTK+ to perform DNS prefetching. Users of WebKitGTK+ should upgrade to these updated packages, which contain WebKitGTK+ version 1.2.6, and resolve these issues. All running applications that use WebKitGTK+ must be restarted for this update to take effect.

Commands:
Chapter 3. Updating Red Hat build of OpenJDK container images To ensure that an Red Hat build of OpenJDK container with Java applications includes the latest security updates, rebuild the container. Procedure Pull the base Red Hat build of OpenJDK image. Deploy the Red Hat build of OpenJDK application. For more information, see Deploying Red Hat build of OpenJDK applications in containers . The Red Hat build of OpenJDK container with the Red Hat build of OpenJDK application is updated. Additional resources For more information, see Red Hat OpenJDK Container images . Revised on 2024-05-09 14:48:54 UTC

Commands:
39.3. Replacing Red Hat Enterprise Linux with MS-DOS or Legacy Versions of Microsoft Windows In DOS and Windows, use the Windows fdisk utility to create a new MBR with the undocumented flag /mbr . This ONLY rewrites the MBR to boot the primary DOS partition. The command should look like the following: If you need to remove Linux from a hard drive and have attempted to do this with the default DOS (Windows) fdisk , you will experience the Partitions exist but they do not exist problem. The best way to remove non-DOS partitions is with a tool that understands partitions other than DOS. To begin, insert the Red Hat Enterprise Linux DVD and boot your system. When the boot prompt appears, type: linux rescue . This starts the rescue mode program. You are prompted for your keyboard and language requirements. Enter these values as you would during the installation of Red Hat Enterprise Linux. , a screen appears telling you that the program attempts to find a Red Hat Enterprise Linux install to rescue. Select Skip on this screen. After selecting Skip , you are given a command prompt where you can access the partitions you would like to remove. First, type the command list-harddrives . This command lists all hard drives on your system that are recognizable by the installation program, as well as their sizes in megabytes. Warning Be careful to remove only the necessary Red Hat Enterprise Linux partitions. Removing other partitions could result in data loss or a corrupted system environment. To remove partitions, use the partitioning utility parted . Start parted , where /dev/hda is the device on which to remove the partition: Using the print command, view the current partition table to determine the minor number of the partition to remove: The print command also displays the partition's type (such as linux-swap, ext2, ext3, ext4 and so on). Knowing the type of the partition helps you in determining whether to remove the partition. Remove the partition with the command rm . For example, to remove the partition with minor number 3: Important The changes start taking place as soon as you press [Enter], so review the command before committing to it. After removing the partition, use the print command to confirm that it is removed from the partition table. Once you have removed the Linux partitions and made all of the changes you need to make, type quit to quit parted . After quitting parted , type exit at the boot prompt to exit rescue mode and reboot your system, instead of continuing with the installation. The system should reboot automatically. If it does not, you can reboot your computer using Control + Alt + Delete .

Commands:
fdisk /mbr
parted /dev/hda
print
rm 3
14.15.2.4. snapshot-edit-domain This command is used to edit the snapshot that is currently in use. To use, run: If both snapshotname and --current are specified, it forces the edited snapshot to become the current snapshot. If snapshotname is omitted, then --current must be supplied, in order to edit the current snapshot. This is equivalent to the following command sequence below, but it also includes some error checking: If --rename is specified, then the resulting edited file gets saved in a different file name. If --clone is specified, then changing the snapshot name will create a clone of the snapshot metadata. If neither is specified, then the edits will not change the snapshot name. Note that changing a snapshot name must be done with care, since the contents of some snapshots, such as internal snapshots within a single qcow2 file, are accessible only from the original snapshot filename.

Commands:
virsh snapshot-edit domain [snapshotname] [--current] {[--rename] [--clone]}
virsh snapshot-dumpxml dom name > snapshot.xml vi snapshot.xml [note - this can be any editor] virsh snapshot-create dom snapshot.xml --redefine [--current]
B.6. chkconfig B.6.1. RHBA-2012:0417 - chkconfig bug fix update Updated chkconfig packages that fix two bugs are now available for Red Hat Enterprise Linux 6 Extended Update Support. The basic system utility chkconfig updates and queries runlevel information for system services. Bug Fixes BZ# 797840 When installing multiple Linux Standard Base (LSB) services which only had LSB headers, the stop priority of the related LSB init scripts could have been miscalculated and set to "-1". With this update, the LSB init script ordering mechanism has been fixed, and the stop priority of the LSB init scripts is now set correctly. BZ# 797839 When an LSB init script requiring the "USDlocal_fs" facility was installed with the "install_initd" command, the installation of the script could fail under certain circumstances. With this update, the underlying code has been modified to ignore this requirement because the "USDlocal_fs" facility is always implicitly provided. LSB init scripts with requirements on "USDlocal_fs" are now installed correctly. All users of chkconfig are advised to upgrade to these updated packages, which fix these bugs.

Commands:
7.302. cluster 7.302.1. RHBA-2013:1189 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market. Bug Fix BZ# 1001504 Prior to this update, if one of the gfs2_tool, gfs2_quota, gfs2_grow, or gfs2_jadd commands was killed unexpectedly, a temporary GFS2 metadata mount point used by those tools could be left mounted. The mount point was also not registered in the /etc/mtab file, and so the "umount -a -t gfs2" command would not unmount it. This mount point could prevent systems from rebooting properly, and cause the kernel to panic in cases where it was manually unmounted after the normal GFS2 mount point. This update corrects the problem by creating an mtab entry for the temporary mount point, which unmounts it before exiting when signals are received. Users of the Red Hat Cluster Manager and GFS2 are advised to upgrade to these updated packages, which fix this bug. 7.302.2. RHBA-2013:1055 - cluster and gfs2-utils bug fix update Updated cluster and gfs2-utils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Red Hat Cluster Manager is a collection of technologies working together to provide data integrity and the ability to maintain application availability in the event of a failure. Using redundant hardware, shared disk storage, power management, and robust cluster communication and application failover mechanisms, a cluster can meet the needs of the enterprise market. Bug Fix BZ# 982700 Previously, the cman init script did not handle its lock file correctly. During a node reboot, this could have caused the node itself to be evicted from the cluster by other members. With this update, the cman init script now handles the lock file correctly, and no fencing action is taken by other nodes of the cluster. Users of cluster and gfs2-utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
6.2. Creating an ext3 File System After installation, it is sometimes necessary to create a new ext3 file system. For example, if you add a new disk drive to the system, you may want to partition the drive and use the ext3 file system. The steps for creating an ext3 file system are as follows: Create the partition using parted or fdisk . Format the partition with the ext3 file system using mkfs . Label the partition using e2label . Create the mount point. Add the partition to the /etc/fstab file.

Commands:
32.8.3. Registering a System in RHN Classic The rhnreg_ks command is a utility for registering a system with the Red Hat Network. It is designed to be used in a non-interactive environment (a Kickstart style install, for example). All the information can be specified on the command line or standard input (stdin). This command should be used when you have created an activation key and you want to register a system using a key. For details about using rhnreg_ks to automatically register your system, see the Knowledgebase article at https://access.redhat.com/solutions/876433 .

Commands:
4.21. biosdevname 4.21.1. RHBA-2011:1608 - biosdevname bug fix and enhancement update An updated biosdevname package that fixes several bugs and adds various enhancements are now available for Red Hat Enterprise Linux 6. The biosdevname package contains an optional convention for naming network interfaces; it assigns names to network interfaces based on their physical location. The package is disabled by default, except for a limited set of Dell PowerEdge, C Series and Precision Workstation systems. The biosdevname package has been upgraded to upstream version 0.3.11, which provides a number of bug fixes and enhancements over the version. (BZ# 696203 ) Bug Fixes BZ# 700248 When NPAR (NIC Partitioning) is enabled, the partition number should be appended as a suffix to the interface name. Previously, biosdevname did not add partition numbers to interface names, for example, instead of naming an interface "em3_1", the interface was named "em3". Consequently, partitioned network interfaces were missing the suffix necessary to describe the partition. Now, biosdevname correctly recognizes the VPD (Vital Product Data) suffix and full interface names are created correctly. BZ# 700251 When biosdevname ran in a guest environment, it suggested names to new network interfaces as if it was in a host environment. Consequently, affected network interfaces were incorrectly renamed. Now, biosdevname no longer suggests names in the described scenario. BZ# 729591 When biosdevname was reading VPD information to retrieve NPAR-related data, the read operations failed or became unresponsive on certain RAID controllers. Additionally, biosdevname sometimes attempted to read beyond the VPD boundary in the sysfs VPD file, which also resulted in a hang. This bug has been fixed and biosdevname now performs the read operation correctly in the described scenarios. BZ# 739592 Previously, the "--smbios" and "--nopirq" command-line parameters were missing in the biosdevname binary. Consequently, consistent network device naming could not be enabled because biosdevname exited without suggesting a name. This update adds support for these parameters and enables the device naming. BZ# 740532 Previously, NICs (Network Interface Cards) on biosdevname-compatible machines were given traditional "eth*" names instead of "em*" or "p*p*" names. This bug has been fixed and biosdevname now provides correct names for the NICs. Enhancements BZ# 696252 With this update, "--smbios" and "--nopirq" command-line parameters have been added to biosdevname. BZ# 736442 The biosdevname man page has been updated to explain the functionality of the "--smbios" and "--nopirq" command-line parameters. Users of biosdevname are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
3.4. Configuring Profiles to Enable Renewal This section discusses how to set up profiles for certificate renewals. For more information on how to renew certificates, see Section 5.4, "Renewing Certificates" . A profile that allows renewal is often accompanied by the renewGracePeriodConstraint entry. For example: 3.4.1. Renewing Using the Same Key A profile that allows the same key to be submitted for renewal has the allowSameKeyRenewal parameter set to true in the uniqueKeyConstraint entry. For example: 3.4.2. Renewal Using a New Key To renew a certificate with a new key, use the same profile with a new key. Certificate System uses the subjectDN from the user signing certificate used to sign the request for the new certificate.

Commands:
policyset.cmcUserCertSet.10.constraint.class_id=renewGracePeriodConstraintImpl policyset.cmcUserCertSet.10.constraint.name=Renewal Grace Period Constraint policyset.cmcUserCertSet.10.constraint.params.renewal.graceBefore=30 policyset.cmcUserCertSet.10.constraint.params.renewal.graceAfter=30 policyset.cmcUserCertSet.10.default.class_id=noDefaultImpl policyset.cmcUserCertSet.10.default.name=No Default
policyset.cmcUserCertSet.9.constraint.class_id=uniqueKeyConstraintImpl policyset.cmcUserCertSet.9.constraint.name=Unique Key Constraint policyset.cmcUserCertSet.9.constraint.params.allowSameKeyRenewal=true policyset.cmcUserCertSet.9.default.class_id=noDefaultImpl policyset.cmcUserCertSet.9.default.name=No Default