mtpti5iD/redhat-docs_dataset huggingface dataset:
7.85. icedtea-web 7.85.1. RHBA-2013:0491 - icedtea-web bug fix update Updated icedtea-web packages that fix one bug are now available for Red Hat Enterprise Linux 6. The IcedTea-Web project provides a Java web browser plug-in and an implementation of Java Web Start, which is based on the Netx project. It also contains a configuration tool for managing deployment settings for the plug-in and Web Start implementations. Bug Fix BZ# 838084 Previously, the IcedTea-Web plug-in was built against JDK 6, but in runtime it was possible to use it with JDK 7. Consequently, IcedTea-Web sometimes failed to run. With this update, the icedtea-web package is built against JDK 7 and IcedTea-Web is using JDK 7 in runtime, thus preventing this bug. Note that the end of public updates for JDK 6 is scheduled to go into effect in upcoming weeks. Users of icedtea-web are advised to upgrade to these updated packages, which fix this bug. 7.85.2. RHBA-2013:0959 - icedtea-web bug fix update Updated icedtea-web packages that fix one bug are now available for Red Hat Enterprise Linux 6. The IcedTea-Web project provides a Java web browser plug-in and an implementation of Java Web Start, which is based on the Netx project. It also contains a configuration tool for managing deployment settings for the plug-in and Web Start implementations. Bug Fix BZ# 975426 A java-1.7.0-openjdk package change released via RHSA-2013:0957 caused the icedtea-web browser plug-in and the javaws application to exit with a NullPointerException. This update fixes icedtea-web to work correctly with the updated java-1.7.0-openjdk packages. Users of icedtea-web are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 8. Using realmd to Connect to an Identity Domain The realmd system provides a clear and simple way to discover and join identity domains. It does not connect to the domain itself but configures underlying Linux system services, such as SSSD or Winbind, to connect to the domain. The Windows Integration Guide describes using realmd to connect to a Microsoft Active Directory (AD) domain. The same procedures apply to using realmd to connect to non-AD identity domains. See Using realmd to Connect to an Active Directory Domain in the Windows Integration Guide .

Commands:
6.5. RHEA-2015:1421 - new package: redhat-access-insights A new redhat-access-insights package is now available for Red Hat Enterprise Linux 6. The redhat-access-insights package allows Red Hat subscribers to enroll in a powerful analytics toolchain that allows them to proactively discover and triage problems that have been detected in their Red Hat Enterprise Linux. The information and schedule for analysis upload can be set by the user. This enhancement update adds the redhat-access-insights package to Red Hat Enterprise Linux 6. (BZ# 1176237 ) All users who require redhat-access-insights are advised to install this new package.

Commands:
Chapter 134. KafkaConnectorSpec schema reference Used in: KafkaConnector Property Property type Description class string The Class for the Kafka Connector. tasksMax integer The maximum number of tasks for the Kafka Connector. autoRestart AutoRestart Automatic restart of connector and tasks configuration. config map The Kafka Connector configuration. The following properties cannot be set: connector.class, tasks.max. pause boolean The pause property has been deprecated. Deprecated in Streams for Apache Kafka 2.6, use state instead. Whether the connector should be paused. Defaults to false. state string (one of [running, paused, stopped]) The state the connector should be in. Defaults to running.

Commands:
8.44. dhcp 8.44.1. RHBA-2014:1406 - dhcp bug fix update Updated dhcp packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. The dhcp packages provide a relay agent and ISC DHCP service required to enable and administer DHCP on a network. Bug Fixes BZ# 1015997 When a packet with checksum having the value of 0xffff was received by the dhcpd daemon, the packet was discarded. With this update, checksum with value 0xffff is perceived as correct, and the packet is now processed as intended. BZ# 1053155 Previously, the user could not run IPv6 version of the dhcrelay service, because there was no such initiation script. To fix this bug, the initiation script of dhcrelay has been added, and the user can now run service for IPv6 version of dhcrelay. BZ# 1053431 When IPv6 version of the dhcpd daemon served too many requests, the /var/lib/dhcpd/dhcpd.leases file grew uncontrollably in size. As a consequence, dhcpd refused to restart with the following error message: file is too long to buffer An upstream patch has been backported to fix this bug, and dhcpd for IPv6 now rotates /var/lib/dhcpd/dhcpd.leases to prevent it from growing. BZ# 1064416 When using ISC DHCP server and clients on Infiniband cards (IPoIB), the hardware address, called GUID, did not appear in logs. This update adds GUIDs to the logs for IPoIB. BZ# 1067142 Every time the dhcpd daemon started, the ownership of the /var/lib/dhcpd/dhcpd.leases file was changed from dhcpd:dhcpd to root:root. A Fedora patch has been backported to fix this bug, and the ownership of /var/lib/dhcpd/dhcpd.leases no longer changes. BZ# 1099698 When having failover configuration of the dhcpd daemon and using very long lease times for clients, the following error was returned when starting dhcpd: unable to write lease A patch has been applied to fix this bug, and error messages no longer appear in logs. BZ# 1102662 Previously, when starting the dhcpd daemon or the dhcrelay agent, the user specified the name of the network interface. If longer than 15 characters, dhcpd or dhcrelay terminated unexpectedly with the following error message: *** buffer overflow detected *** A patch has been backported to fix this bug, and dhcpd or dhcrelay now exit gracefully with a new error message informing the user that the interface name is too long. Users of dhcp are advised to upgrade to these updated packages, which fix these bugs.

Commands:
3.8. Re-enrolling a Client into the IdM Domain If a client virtual machine has been destroyed and you still have its keytab, you can re-enroll the client: Interactively, using administrator credentials. See Section 3.8.1, "Re-enrolling a Client Interactively Using the Administrator Account" . Non-interactively, using a previously backed-up keytab file. See Section 3.8.2, "Re-enrolling a Client Non-interactively Using the Client Keytab" . Note You can only re-enroll clients whose domain entry is still active. If you uninstalled a client (using ipa-client-install --uninstall ) or disabled its host entry (using ipa host-disable ), you cannot re-enroll it. During re-enrollment, IdM performs the following: Revokes the original host certificate Generates a new host certificate Creates new SSH keys Generates a new keytab 3.8.1. Re-enrolling a Client Interactively Using the Administrator Account Re-create the client machine with the same host name. Run the ipa-client-install --force-join command on the client machine: The script prompts for a user whose identity will be used to enroll the client. By default, this is the admin user: 3.8.2. Re-enrolling a Client Non-interactively Using the Client Keytab Re-enrollment using the client keytab is appropriate for automated installation or in other situations when using the administrator password is not feasible. Back up the original client's keytab file, for example in the /tmp or /root directory. Re-create the client machine with the same host name. Re-enroll the client, and specify the keytab location using the --keytab option: Note The keytab specified in the --keytab option is only used when authenticating to initiate the enrollment. During the re-enrollment, IdM generates a new keytab for the client.

Commands:
ipa-client-install --force-join
User authorized to enroll computers: admin Password for admin@EXAMPLE.COM
ipa-client-install --keytab /tmp/krb5.keytab
probe::ioblock_trace.end Name probe::ioblock_trace.end - Fires whenever a block I/O transfer is complete. Synopsis ioblock_trace.end Values bdev_contains points to the device object which contains the partition (when bio structure represents a partition) flags see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block BIO_EOF 2 out-out-bounds error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user pages BIO_EOPNOTSUPP 7 not supported devname block device name bytes_done number of bytes transferred name name of the probe point sector beginning sector for the entire bio ino i-node number of the mapped file rw binary trace for read/write request size total size in bytes q request queue on which this bio was queued. idx offset into the bio vector array phys_segments - number of segments in this bio after physical address coalescing is performed. vcnt bio vector count which represents number of array element (page, offset, length) which makes up this I/O request bdev target block device p_start_sect points to the start sector of the partition structure of the device Context The process signals the transfer is done.

Commands:
8.5. Welcome Screen and Language Selection The first screen of the installation program is the Welcome to Red Hat Enterprise Linux screen. Here you select the language that Anaconda will use for the rest of the installation. This selection will also become the default for the installated system, unless changed later. In the left panel, select your language of choice, for example English . Then you can select a locale specific to your region in the right panel, for example English (United States) . Note One language is pre-selected by default on top of the list. If network access is configured at this point (for example, if you booted from a network server instead of local media), the pre-selected language will be determined based on automatic location detection using the GeoIP module. Alternatively, type your preferred language into the search box as shown below. Once you have made your selection, click the Continue button to proceed to the Installation Summary screen. Figure 8.3. Language Configuration After you click the Continue button, the unsupported hardware dialog may appear. This happens if you are using hardware that the kernel does not support.

Commands:
Chapter 7. Container Security Practices This chapter describes measures that you can take to protect the security of your containers. 7.1. Dropping Kernel Capabilities Kernel capabilities can be dropped from the CLI of Docker and in the .json file of Kubernetes. Start with nothing and add what you need - this is the safest method of determining which kernel capabilities you need. 7.2. Dropping Root Never have long-running containers running as root, with the exception of systemd . There are a couple of approaches for doing this: if you don't need systemd, you can use exec to become root and drop your user privileges. Or you can use systemd to launch the application you want inside the container with a unit file, and the unit file can be used to designate the desired services as non-root. 7.3. Exercise care in using the --privileged flag. Unless your container needs access to the host's hardware, you should not use --privileged . 7.4. suid Content Sticky-bit content (sticky UID content). This is a word-to-the-wise-type note. It is possible to make use of suid content without a privileged container, but it is not easy to create suid content without a privileged container because marking something as suid is a privileged operation. 7.5. tmpfile A tmpfile is a file that gets created in /tmp . This section refers to tmpfile attacks. Containers are susceptible to the same race conditions and attacks that non-container tmpfiles are susceptible to. Make sure that tmpfile content ownership is properly restricted. 7.6. Do not bind the docker service to a TCP port Binding the docker service to a TCP port allows non-root users to gain root access on the host. Hence, anyone with access to that port can then run arbitrary code as the root user. To prevent this type of vulnerability, do not expose docker through a TCP port. Keep the default binding.

Commands:
Chapter 20. JbodStorage schema reference Used in: KafkaClusterSpec , KafkaNodePoolSpec The type property is a discriminator that distinguishes use of the JbodStorage type from EphemeralStorage , PersistentClaimStorage . It must have the value jbod for the type JbodStorage . Property Property type Description type string Must be jbod . volumes EphemeralStorage , PersistentClaimStorage array List of volumes as Storage objects representing the JBOD disks array.

Commands:
Chapter 1. Overview Red Hat Ansible Lightspeed with IBM watsonx Code Assistant is a generative AI service that helps automation teams create, adopt, and maintain Ansible content more efficiently. It uses natural language prompts to generate code recommendations for automation tasks based on Ansible best practices. Red Hat Ansible Lightspeed is also the cloud service that enables the integration of generative AI into Ansible Automation Platform. To use the Red Hat Ansible Lightspeed cloud service, you must meet one of the following requirements: Your organization has a trial or paid subscription to both the Red Hat Ansible Automation Platform and IBM watsonx Code Assistant. Your organization has a trial or paid subscription to the Red Hat Ansible Automation Platform, and you have a Red Hat Ansible Lightspeed trial account. Note A Red Hat Ansible Lightspeed trial account does not require an IBM watsonx Code Assistant subscription. To use an on-premise deployment of Red Hat Ansible Lightspeed, your organization must have the following subscriptions: A trial or paid subscription to the Red Hat Ansible Automation Platform An installation of IBM watsonx Code Assistant for Red Hat Ansible Lightspeed on Cloud Pak for Data

Commands:
Chapter 4. Trim options on an LVM-VDO volume The following are different available trim options for an LVM-VDO volume: discard Performs online block discard operations to automatically discard unused blocks. For immediate discarding, use the mount -o discard command. fstrim Performs periodic discarding. The admin needs to schedule and monitor an additional process. Note It is currently recommended to use fstrim application to discard unused blocks rather than the discard mount option because the performance impact of this option can be quite severe. For this reason, nodiscard is the default. 4.1. Enabling discard mount option on an LVM-VDO volume You can enable the discard option on your LVM-VDO volume. Prerequisites An LVM-VDO volume exists on your system. Procedure Enable the discard option on your volume: Additional resources xfs(5) , mount(8) , and lvmvdo(7) man pages on your system 4.2. Setting up periodic TRIM operation You can enable a scheduled TRIM operation on your system. Prerequisites An LVM-VDO volume exists on your system. Procedure Enable and start the timer: Verification Verify that the timer is enabled: Note You will not see any reference to a VDO volume, because the fstrim.timer runs across all mounted file systems. Additional resources fstrim(8) man page on your system

Commands:
mount -o discard /dev/ vg-name/vdo-name mount-point
systemctl enable --now fstrim.timer
systemctl list-timers fstrim.timer NEXT LEFT LAST PASSED UNIT ACTIVATES Mon 2021-05-10 00:00:00 EDT 5 days left n/a n/a fstrim.timer fstrim.service
Chapter 20. Using early kdump to capture boot time crashes Early kdump is a feature of the kdump mechanism that captures the vmcore file if a system or kernel crash occurs during the early phases of the boot process before the system services start. Early kdump loads the crash kernel and the initramfs of crash kernel in the memory much earlier. A kernel crash can sometimes occur during the early boot phase before the kdump service starts and is able to capture and save the contents of the crashed kernel memory. Therefore, crucial information related to the crash that is important for troubleshooting is lost. To address this problem, you can use the early kdump feature, which is a part of the kdump service. 20.1. Enabling early kdump The early kdump feature sets up the crash kernel and the initial RAM disk image ( initramfs ) to load early enough to capture the vmcore information for an early crash. This helps to eliminate the risk of losing information about the early boot kernel crashes. Prerequisites An active RHEL subscription. A repository containing the kexec-tools package for your system CPU architecture. Fulfilled kdump configuration and targets requirements. For more information see, Supported kdump configurations and targets . Procedure Verify that the kdump service is enabled and active: If kdump is not enabled and running, set all required configurations and verify that kdump service is enabled. Rebuild the initramfs image of the booting kernel with the early kdump functionality: Add the rd.earlykdump kernel command line parameter: Reboot the system to reflect the changes: Verification Verify that rd.earlykdump is successfully added and early kdump feature is enabled: Additional resources The /usr/share/doc/kexec-tools/early-kdump-howto.txt file What is early kdump support and how do I configure it? (Red Hat Knowledgebase)

Commands:
systemctl is-enabled kdump.service && systemctl is-active kdump.service enabled active
dracut -f --add earlykdump
grubby --update-kernel=/boot/vmlinuz-USD(uname -r) --args="rd.earlykdump"
reboot
cat /proc/cmdline BOOT_IMAGE=(hd0,msdos1)/vmlinuz-5.14.0-1.el9.x86_64 root=/dev/mapper/rhel-root ro crashkernel=auto resume=/dev/mapper/rhel-swap rd.lvm.lv=rhel/root rd.lvm.lv=rhel/swap rhgb quiet rd.earlykdump journalctl -x | grep early-kdump Sep 13 15:46:11 redhat dracut-cmdline[304]: early-kdump is enabled. Sep 13 15:46:12 redhat dracut-cmdline[304]: kexec: loaded early-kdump kernel
Chapter 1. Red Hat Enterprise Linux 9 content 1.1. Repositories Content in Red Hat Enterprise Linux 9 is made available through the following content repositories: BaseOS AppStream CodeReady Linux Builder Supplementary In addition, specific content is available through the Red Hat Enterprise Linux Add-on repositories: High Availability Resilient Storage 1.2. Types of Content There are two primary types of Red Hat Enterprise Linux 9 content. 1.2.1. Traditional content Traditional content is released as RPMs and is, unless specified otherwise, supported for the life of the release in accordance with the Red Hat Enterprise Linux Life Cycle . 1.2.2. Application Streams Certain user space components distributed in the AppStream repository are Application Streams. Application Streams are delivered on a cadence that is suitable for each package, which makes the distribution diversified. Application Streams offer multiple versions of a single package for installation within RHEL 9, which is an improvement over methods of making multiple versions of packages available. RHEL 9 also consolidates distribution channels to a single place. Depending on the needs of the individual Application Stream, packaging for these components is implemented in a number of forms: RPMs Modules Software Collections. For detailed information on the length of Application Streams support, see the Red Hat Enterprise Linux Application Streams Life Cycle . For information about the other components or packages in the AppStream repository, see the Scope of Coverage Details document.

Commands:
2.39. RHEA-2011:0670 - new package: sigar A new sigar package is now available for Red Hat Enterprise Linux 6. The System Information Gatherer and Reporter (SIGAR) is a library and command line tool for accessing operating system and hardware level information across multiple platforms and programming languages. This enhancement update adds the sigar package to Red Hat Enterprise Linux 6. Note that this package is included as a Technology Preview. (BZ# 658887 ) All users who require sigar should install this new package.

Commands:
5.11. The multipathd Commands The multipathd commands can be used to administer the multipathd daemon. For information on the available multipathd commands, see the multipathd (8) man page. The following command shows the standard default format for the output of the multipathd show maps command. Some multipathd commands include a format option followed by a wildcard. You can display a list of available wildcards with the following command. As of Red Hat Enterprise Linux release 7.3, the multipathd command supports new format commands that show the status of multipath devices and paths in "raw" format versions. In raw format, no headers are printed and the fields are not padded to align the columns with the headers. Instead, the fields print exactly as specified in the format string. This output can then be more easily used for scripting. You can display the wildcards used in the format string with the multipathd show wildcards command. The following multipathd commands show the multipath devices that multipathd is monitoring, using a format string with multipath wildcards, in regular and raw format. The following multipathd commands show the paths that multipathd is monitoring, using a format string with multipath wildcards, in regular and raw format. The following commands show the difference between the non-raw and raw formats for the multipathd show maps . Note that in raw format there are no headers and only a single space between the columns.

Commands:
multipathd show maps name sysfs uuid mpathc dm-0 360a98000324669436c2b45666c567942
multipathd show wildcards
list|show maps|multipaths format USDformat list|show maps|multipaths raw format USDformat
list|show paths format USDformat list|show paths raw format USDformat
multipathd show maps format "%n %w %d %s" name uuid sysfs vend/prod/rev mpathc 360a98000324669436c2b45666c567942 dm-0 NETAPP,LUN multipathd show maps raw format "%n %w %d %s" mpathc 360a98000324669436c2b45666c567942 dm-0 NETAPP,LUN
Chapter 2. Why Use Virtualization? Virtualization can be useful both for server deployments and individual desktop stations. Desktop virtualization offers cost-efficient centralized management and better disaster recovery. In addition, by using connection tools such as ssh , it is possible to connect to a desktop remotely. When used for servers, virtualization can benefit not only larger networks, but also deployments with more than a single server. Virtualization provides live migration, high availability, fault tolerance, and streamlined backups. 2.1. Virtualization Costs Virtualization can be expensive to introduce, but it often saves money in the long term. Consider the following benefits: Less power Using virtualization negates much of the need for multiple physical platforms. This equates to less power being drawn for machine operation and cooling, resulting in reduced energy costs. The initial cost of purchasing multiple physical platforms, combined with the machines' power consumption and required cooling, is drastically cut by using virtualization. Less maintenance Provided that adequate planning is performed before migrating physical systems to virtualized ones, less time is spent maintaining them. This means less money needs to be spent on parts and labor. Extended life for installed software Older versions of software may not be able to run directly on more recent physical machines. By running older software virtually on a larger, faster system, the life of the software may be extended while taking advantage of better performance from a newer system. Predictable costs A Red Hat Enterprise Linux subscription provides support for virtualization at a fixed rate, making it easy to predict costs. Less space Consolidating servers onto fewer machines means less physical space is required for computer systems.

Commands: