mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Types of certification workflow 4.1. Single Instance Type certification A Single Instance Type Certification consists of bootable, installable, and operableable collection of physical or virtual hardware features, as defined by a specification provided by a Partner. The specification may define features as standard, or optional. The Instance Type is considered to provide all of the features from the complete collection of standard and optional components unless explicitly excluded by or from the specification. 4.2. SuperSet Instance Type certification The SuperSet Instance Type Certification covers a variety of different configurations of the same Instance Type. The SuperSet Instance Type is known by a unique name within a naming convention. Example compute_slow, compute_medium, compute_fast The certification is conducted as per the basic process where all of the configurations are reviewed. The test plan will consider multiple configurations in order to increase the testing and processing efficiency without creating risks. The certification publication in the catalog will be a combined entry where the sizes covered by the certification will be displayed on the Instance Type certification entry. 4.3. Supplemental certification A supplemental certification allows a certified Instance Type to extend or alter the configuration of the Instance Type. 4.4. Pass-Through Instance Type certification A Pass-Through Instance Type Certification refers to the ability of a third party system or component to be granted the same certification as Instance Type previously certified by the Original Provider. The Original Provider can extend a certification granted to their instance type to another Partner's Instance Type where the original provider: Has permission from the third party Has the mechanics to ensure the third party does not alter the hardware in such a way that it would no longer be considered a subset of the original model certified by Red Hat Extends their responsibilities of support and representative Instance Type to include situations involving the third party Instance Type The third party however cannot extend their pass-through certification to another Partner. Important Both Partners are required to be members of the CCSP program; only the original provider may request Pass-Through certifications. Note You may also utilize the pass-through process where the same Instance Type is available with multiple names.

Commands:
5.4.9. Persistent Device Numbers Major and minor device numbers are allocated dynamically at module load. Some applications work best if the block device always is activated with the same device (major and minor) number. You can specify these with the lvcreate and the lvchange commands by using the following arguments: Use a large minor number to be sure that it has not already been allocated to another device dynamically. If you are exporting a file system using NFS, specifying the fsid parameter in the exports file may avoid the need to set a persistent device number within LVM.

Commands:
--persistent y --major major --minor minor
Chapter 3. Downloading Eclipse Temurin distributions You can download Eclipse Temurin distribution from numerous sources, such as the Adoptium website. Both the Adoptium main web page and the Eclipse Temurin web page include several download buttons for downloading different Eclipse Temurin distribution. Procedure Choose one of the following options to download an Eclipse Temurin distribution: From the Adoptium home web page or from the Eclipse Temurin project page , click one of the following buttons from the web page: Latest LTS Release button that preselects Red Hat build of OpenJDK 17 for the platform that it detects you are using and immediately begins downloading that selection. Other platforms and versions button that directs to a selection of all platform and version options, where you can choose the distribution that best suits your needs from the various formats such as archives, JRE archives and installers. Release archive button that directs to a selection of latest releases, older releases, and nightly beta releases. Adoptium provides older releases and beta releases for development purposes only. Beta releases contain the most recent changes delivered into Red Hat build of OpenJDK, which you'll find useful for verifying fixes in development mode. Beta releases are not considered production ready and are not directly supported by Red Hat. Use the Adoptium API, see the Swagger UI v3 documentation Eclipse Temurin . From the Eclipse Temurin Docker Hub Official Images, see the eclipse-temurin documentation (docker hub ) . Use the Eclipse Temurin Marketplace and Marketplace API, by going to the Adoptium TM Marketplace web page. This web page lists various distributions, such as the Red Hat build of Red Hat build of OpenJDK and Eclipse Temurin distributions. Additionally, you can make a request to the Adoptium Marketplace API v1 to serve up these distributions. For Packages.adoptium.net , see the relevant steps outlined in Eclipse Temurin Linux (RPM/DEB) Installer Packages (Adoptium) . Additional resources Adoptium home web page (Adoptium) Eclipse Temurin (Adoptium)

Commands:
17.2.2.4. Expansions Expansions, when used in conjunction with the spawn and twist directives, provide information about the client, server, and processes involved. Below is a list of supported expansions: %a - Supplies the client's IP address. %A - Supplies the server's IP address. %c - Supplies a variety of client information, such as the username and hostname, or the username and IP address. %d - Supplies the daemon process name. %h - Supplies the client's hostname (or IP address, if the hostname is unavailable). %H - Supplies the server's hostname (or IP address, if the hostname is unavailable). %n - Supplies the client's hostname. If unavailable, unknown is printed. If the client's hostname and host address do not match, paranoid is printed. %N - Supplies the server's hostname. If unavailable, unknown is printed. If the server's hostname and host address do not match, paranoid is printed. %p - Supplies the daemon process ID. %s -Supplies various types of server information, such as the daemon process and the host or IP address of the server. %u - Supplies the client's username. If unavailable, unknown is printed. The following sample rule uses an expansion in conjunction with the spawn command to identify the client host in a customized log file. When connections to the SSH daemon ( sshd ) are attempted from a host in the example.com domain, execute the echo command to log the attempt, including the client hostname (by using the %h expansion), to a special file: Similarly, expansions can be used to personalize messages back to the client. In the following example, clients attempting to access FTP services from the example.com domain are informed that they have been banned from the server: For a full explanation of available expansions, as well as additional access control options, refer to section 5 of the man pages for hosts_access ( man 5 hosts_access ) and the man page for hosts_options . For additional information about TCP wrappers, refer to Section 17.5, "Additional Resources" . For more information about how to secure TCP wrappers, refer to the chapter titled Server Security in the Security Guide .

Commands:
sshd : .example.com : spawn /bin/echo `/bin/date` access denied to %h>>/var/log/sshd.log : deny
vsftpd : .example.com : twist /bin/echo "421 %h has been banned from this server!"
Chapter 338. ContextIdListing enabled When contextIdListing is enabled then its detecting all the running CamelContexts in the same JVM. These contexts are listed in the root path, eg /api-docs as a simple list of names in json format. To access the OpenApi documentation then the context-path must be appended with the Camel context id, such as api-docs/myCamel . The option apiContextIdPattern can be used to filter the names in this list.

Commands:
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes included in the latest OpenJDK 11.0.18 release of Eclipse Temurin, see OpenJDK 11.0.18 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements included with the Eclipse Temurin 11.0.18 release: Enhanced BMP bounds By default, OpenJDK 11.0.18 disables loading a linked International Color Consortium (ICC) profile in a BMP image. You can enable this functionality by setting the new sun.imageio.bmp.enabledLinkedProfiles property to true . This property replaces the old sun.imageio.plugins.bmp.disableLinkedProfiles property See JDK-8295687 (JDK Bug System) . Improved banking of sounds Previously, the SoundbankReader implementation, com.sun.media.sound.JARSoundbankReader , downloaded a JAR soundbank from a URL. For OpenJDK 11.0.18, this behavior is now disabled by default. To re-enable the behavior, set the new system property jdk.sound.jarsoundbank to true . See JDK-8293742 (JDK Bug System) . Enhanced Datagram Transport Layer Security (DTLS) performance OpenJDK now exchanges DTLS cookies for all new and resumed handshake communications. To re-enable the release behavior, set the new system property jdk.tls.enableDtlsResumeCookie to false . See JDK-8287411 (JDK Bug System) . SunMSCAPI provider supports new Microsoft Windows keystore types The SunMSCAPI provider supports the following Microsoft Windows keystore types where you must append your local namespace to Windows- : Windows-MY-LOCALMACHINE Windows-ROOT-LOCALMACHINE Windows-MY-CURRENTUSER Windows-ROOT-CURRENTUSER By specifying any of these types, you can provide access to your local computer's location for the Microsoft Windows keystore. Thereby providing the keystore access to certificates that are stored on your local system. See JDK-6782021 (JDK Bug System). Added note for LoginModule implementation The OpenJDK 9 release changed the Set implementation, which holds principals and credentials, so that the implementation can reject null values. Any attempts to call add(null) , contains(null) , or remove(null) would throw a NullPointerException message. The OpenJDK 9 release did not update the logout() method in the LoginModule implementation to check for null values. These values could occur because of a failed login attempt, which can cause a logout() call to throw a NullPointerException message. The OpenJDK 11.0.18 release updates the LoginModule implementations to check for null values. Additionally, the release adds an implementation note to the specification that states the change also applies to third-party modules. The note advises developers of third-party modules to verify that a logout() method does not throw a NullPointerException message. See JDK-8015081 (JDK Bug System). See JDK-8282730 (JDK Bug System). Revised on 2024-05-09 16:48:08 UTC

Commands:
7.74. hplip 7.74.1. RHBA-2015:1282 - hplip bug fix and enhancement update Updated hplip packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The hplip packages contain the Hewlett-Packard Linux Imaging and Printing Project (HPLIP), which provides drivers for Hewlett-Packard printers and multi-function peripherals. Note The hplip packages have been upgraded to upstream version 3.14.6, which provides a number of bug fixes and enhancements over the version, including hardware enablement and new functionality, such as the Service Location Protocol (SLP) discovery feature. (BZ# 1077121 ) Bug Fixes BZ# 682814 Previously, HPLIP did not correctly handle CUPS denying a requested operation, such enabling or disabling a printer. As a consequence, operating HP Device Manager as a non-root user did not prompt for the root password when the root password was required for an operation. With this update, the password callback is correctly implemented, and operating HP Device Manager as non-root user now always prompts for the root password when required. BZ# 876066 Prior to this update, the use of an uninitialized value could produce incorrect output from the hpcups driver. The underlying source code has been modified to initialize the value before it is used, and the described unexpected behavior is therefore prevented. Users of hplip are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
23.2. Userspace Access Always take care to use properly aligned and sized I/O. This is especially important for Direct I/O access. Direct I/O should be aligned on a logical_block_size boundary, and in multiples of the logical_block_size . With native 4K devices (i.e. logical_block_size is 4K) it is now critical that applications perform direct I/O in multiples of the device's logical_block_size . This means that applications will fail with native 4k devices that perform 512-byte aligned I/O rather than 4k-aligned I/O. To avoid this, an application should consult the I/O parameters of a device to ensure it is using the proper I/O alignment and size. As mentioned earlier, I/O parameters are exposed through the both sysfs and block device ioctl interfaces. For more information, see man libblkid . This man page is provided by the libblkid-devel package. sysfs Interface /sys/block/ disk /alignment_offset or /sys/block/ disk / partition /alignment_offset Note The file location depends on whether the disk is a physical disk (be that a local disk, local RAID, or a multipath LUN) or a virtual disk. The first file location is applicable to physical disks while the second file location is applicable to virtual disks. The reason for this is because virtio-blk will always report an alignment value for the partition. Physical disks may or may not report an alignment value. /sys/block/ disk /queue/physical_block_size /sys/block/ disk /queue/logical_block_size /sys/block/ disk /queue/minimum_io_size /sys/block/ disk /queue/optimal_io_size The kernel will still export these sysfs attributes for "legacy" devices that do not provide I/O parameters information, for example: Example 23.1. sysfs Interface Block Device ioctls BLKALIGNOFF : alignment_offset BLKPBSZGET : physical_block_size BLKSSZGET : logical_block_size BLKIOMIN : minimum_io_size BLKIOOPT : optimal_io_size

Commands:
alignment_offset: 0 physical_block_size: 512 logical_block_size: 512 minimum_io_size: 512 optimal_io_size: 0
9.2. Detecting Errors During Normal Processing Protect server performance by detecting errors during the normal chaining operation between the database link and the remote server. The database link has two attributes - nsMaxResponseDelay and nsMaxTestResponseDelay - which work together to determine if the remote server is no longer responding. The first attribute, nsMaxResponseDelay , sets a maximum duration for an LDAP operation to complete. If the operation takes more than the amount of time specified in this attribute, the database link's server suspects that the remote server is no longer online. Once the nsMaxResponseDelay period has been met, the database link pings the remote server. During the ping, the database link issues another LDAP request, a simple search request for an object that does not exist in the remote server. The duration of the ping is set using the nsMaxTestResponseDelay . If the remote server does not respond before the nsMaxTestResponseDelay period has passed, then an error is returned, and the connection is flagged as down. All connections between the database link and remote server will be blocked for 30 seconds, protecting the server from a performance degradation. After 30 seconds, operation requests made by the database link to the remote server continue as normal. Both attributes are stored in the cn=config,cn=chaining database,cn=plugins,cn=config entry. The following table describes the attributes in more detail: Table 9.1. Database Link Processing Error Detection Parameters Attribute Name Description nsMaxResponseDelay Maximum amount of time it can take a remote server to respond to an LDAP operation request made by a database link before an error is suspected. This period is given in seconds. The default delay period is 60 seconds. Once this delay period has been met, the database link tests the connection with the remote server. nsMaxTestResponseDelay Duration of the test issued by the database link to check whether the remote server is responding. If a response from the remote server is not returned before this period has passed, the database link assumes the remote server is down, and the connection is not used for subsequent operations. This period is given in seconds. The default test response delay period is 15 seconds.

Commands:
5.248. portreserve 5.248.1. RHBA-2012:0447 - portreserve bug fix update An updated portreserve package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The portreserve package helps services with well-known ports that lie in the portmap range. It prevents portmap from occupying a real service's port by occupying it itself, until the real service tells it to release the port, generally in the init script. Bug Fixes BZ# 614924 Prior to this update, the init script for the portreserve daemon did not always return the correct exit code. As a consequence, an incorrect error message was displayed. With this update, the init script is modified to return the correct exit codes, and also appropriate messages are now displayed. BZ# 712362 The portreserve package requires the "chkconfig" command because it is run in installation scriptlets. However, this was previously not reflected in the package metadata, and error messages could be displayed during installation. To prevent this issue, this update adds requirement tags for chkconfig. All users of portreserve are advised to upgrade to this updated package, which fixes these bugs.

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

Commands:
5.7. Customizing Hosts with Tags You can use tags to store information about your hosts. You can then search for hosts based on tags. For more information on searches, see Chapter 3, Searches . Customizing hosts with tags Click Compute Hosts and select a host. Click More Actions ( ), then click Assign Tags . Select the check boxes of applicable tags. Click OK . You have added extra, searchable information about your host as tags.

Commands:
Chapter 4. Migrating from Fabric8 Maven plugin to Openshift Maven plugin The fabric8-maven-plugin has been completely removed from Fuse 7.11. We recommend that you use the openshift-maven-plugin instead for building and deploying Maven projects in Fuse on OpenShift. Procedure Use the following instructions to update your application so that it can use the openshift-maven plugin. Rename the src/main/fabric8 directories in your applications to src/main/jkube . Locate the org.jboss.redhat-fuse:fabric8-maven-plugin dependency in your project's pom.xml and change it to org.jboss.redhat-fuse:openshift-maven-plugin . See the Sample pom.xml . Check the dependencies. For example, org.arquillian.cube:arquillian-cube-openshift , org.jboss.arquillian.junit:arquillian-junit-container , io.fabric8:kubernetes-assertions are no longer used in our examples and may no longer be needed. You can create some sample tests that can be used to reflect the API changes after the migration. For more information see the sample tests in the Spring Boot Camel quickstart . Additional resources OpenShift Maven plugin .

Commands:
7.77. hyperv-daemons 7.77.1. RHBA-2015:1311 - hyperv-daemons bug fix update Updated hyperv-daemons packages that fix one bug are now available for Red Hat Enterprise Linux 6. The hyperv-daemons packages provide a suite of daemons that are needed when a Red Hat Enterprise Linux guest is running on Microsoft Hyper-V. The following daemons are included: - hypervkvpd, the guest Hyper-V Key-Value Pair (KVP) daemon - hypervvssd, the implementation of Hyper-V VSS functionality - hypervfcopyd, the implementation of Hyper-V file copy service functionality Bug Fix BZ# 1161368 When mounting a read-only file system that does not support file system freezing (such as SquashFS) and using the online backup feature, the online backup previously failed with an "Operation not supported" error. This update fixes the hypervvssd daemon so that it handles the online backup correctly, and the described error no longer occurs. Users of hyperv-daemons are advised to upgrade to these updated packages, which fix this bug.

Commands:
3.3. Setting up errata viewing with Red Hat Satellite In the Administration Portal, you can configure Red Hat Virtualization to view errata from Red Hat Satellite in the Red Hat Virtualization Manager. After you associate your hosts, virtual machines, and the Manager with a Red Hat Satellite provider, you can receive updates about available errata and their importance, and decide when to apply them. For more information about Red Hat Satellite see the Red Hat Satellite Documentation . Red Hat Virtualization 4.4 supports viewing errata with Red Hat Satellite 6.6. Prerequisites The Satellite server must be added as an external provider. The Manager, hosts, and virtual machines must all be registered in the Satellite server by their respective FQDNs. This ensures that external content host IDs do not need to be maintained in Red Hat Virtualization. The Satellite account that manages the Manager, hosts and virtual machines must have Administrator permissions and a default organization set. Note The Katello agent is deprecated and will be removed in a future Satellite version. Migrate your processes to use the remote execution feature to update clients remotely. Configuring Red Hat Virtualization errata To associate the Manager, host, and virtual machine with a Red Hat Satellite provider, complete the following tasks: Add the required Satellite server to the Manager as an external provider . Configure the required hosts to display available errata . Configure the required virtual machines to display available errata . Viewing Red Hat Virtualization Manager errata Click Administration Errata . Select the Security , Bugs , or Enhancements check boxes to view only those errata types. Additional resources Configuring Satellite Errata Management for a Host Installing the Guest Agents, Tools, and Drivers on Linux in the Virtual Machine Management Guide for Red Hat Enterprise Linux virtual machines. Installing the Guest Agents, Tools, and Drivers on Windows in the Virtual Machine Management Guide for Windows virtual machines. Viewing Host Errata Configuring Satellite errata viewing for a virtual machine in the Virtual Machine Management Guide for more information. Viewing Red Hat Satellite errata for a virtual machine in the Virtual Machine Management Guide .

Commands: