mtpti5iD/redhat-docs_dataset huggingface dataset:
8.13. cifs-utils 8.13.1. RHBA-2013:1654 - cifs-utils bug fix update Updated cifs-utils packages that fix one bug are available for Red Hat Enterprise Linux 6. The SMB/CIFS protocol is a standard file sharing protocol widely deployed on Microsoft Windows machines. This package contains tools for mounting shares on Linux using the SMB/CIFS protocol. The tools in this package work in conjunction with support in the kernel to allow one to mount a SMB/CIFS share onto a client and use it as if it were a standard Linux file system. Users of cifs-utils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 5. Setting the load balancer for host registration You can configure Satellite to register clients through a load balancer when using the host registration feature. You will be able to register hosts to the load balancer instead of Capsule. The load balancer will decide through which Capsule to register the host at the time of request. Upon registration, the subscription manager on the host will be configured to manage content through the load balancer. Prerequisites You configured SSL certificates on all Capsule Servers. For more information, see Chapter 4, Configuring Capsule Servers for load balancing . You enabled Registration and Templates plugins on all Capsule Servers: Procedure On all Capsule Servers, set the registration and template URLs using satellite-installer : In the Satellite web UI, navigate to Infrastructure > Capsules . For each Capsule, click the dropdown menu in the Actions column and select Refresh .

Commands:
satellite-installer --foreman-proxy-registration true --foreman-proxy-templates true
satellite-installer --foreman-proxy-registration-url "https:// loadbalancer.example.com :9090" --foreman-proxy-template-url "http:// loadbalancer.example.com :8000"
8.91. libksba 8.91.1. RHBA-2013:0837 - libksba bug fix update Updated libksba packages that fix one bug are now available for Red Hat Enterprise Linux 6. KSBA is a library designed to build software based on the X.509 and CMS standards. It provides developers with a single API that handles the underlying details of the X.509 standard and presents data consistently. Bug Fix BZ#658058 Previously, contents of the /usr/bin/libksba-config script conflicted between 32-bit and 64-bit versions of libksba-devel packages. Consequently, these packages could not be installed simultaneously. This update amends the script to make its contents consistent for all architectures, thus fixing this bug. Users of libksba are advised to upgrade to these updated packages, which fix this bug.

Commands:
2.18. RHEA-2011:0629 - new package: mod_revocator A new mod_revocator package is now available for Red Hat Enterprise Linux 6. The mod_revocator module retrieves and installs remote Certificate Revocation Lists (CRLs) into an Apache web server without a need for a restart or user intervention. It can be configured to retrieve CRLs from remote servers at periodic intervals or when a CRL expires, and make them available to the Apache Secure Sockets Layer (SSL) module, mod_nss. Additionally, it can be configured to stop the Apache HTTP Server from accepting requests if a CRL retrieval fails. This enhancement update adds the mod_revocator package to Red Hat Enterprise Linux 6. (BZ# 584103 ) All users who require mod_revocator should install this new package.

Commands:
Chapter 2. Support policy for Eclipse Temurin Red Hat will support select major versions of Eclipse Temurin in its products. For consistency, these are the same versions that Oracle designates as long-term support (LTS) for the Oracle JDK. A major version of Eclipse Temurin will be supported for a minimum of six years from the time that version is first introduced. For more information, see the Eclipse Temurin Life Cycle and Support Policy . Note RHEL 6 reached the end of life in November 2020. Because of this, Eclipse Temurin does not support RHEL 6 as a supported configuration.

Commands:
A.10. Using the VDSM Hooking Module VDSM ships with a Python hooking module, providing helper functions for VDSM hook scripts. This module is provided as an example, and is only relevant to VDSM hooks written in Python. The hooking module supports reading of a virtual machine's libvirt XML into a DOM object. Hook scripts can then use Python's built in xml.dom library ( http://docs.python.org/release/2.6/library/xml.dom.html ) to manipulate the object. The modified object can then be saved back to libvirt XML using the hooking module. The hooking module provides the following functions to support hook development: Table A.2. Hooking module functions Name Argument Description tobool string Converts a string "true" or "false" to a Boolean value read_domxml - Reads the virtual machine's libvirt XML into a DOM object write_domxml DOM object Writes the virtual machine's libvirt XML from a DOM object

Commands:
4.4. Extending polkit Configuration Support for replacing the back-end authority implementation has been removed. A similar level of flexibility can be achieved by writing a JavaScript .rules file that calls an external program. Support for replacing the PolkitBackendActionLookup implementation (the interface used to provide data to authentication dialogs) has also been removed from polkit in Red Hat Enterprise Linux 7. For more information on polkit , see the polkit (8) man page.

Commands:
Chapter 6. About quick start tutorials If you are creating quick start tutorials for the OpenShift Dedicated web console, follow these guidelines to maintain a consistent user experience across all quick starts. 6.1. Understanding quick starts A quick start is a guided tutorial with user tasks. In the web console, you can access quick starts under the Help menu. They are especially useful for getting oriented with an application, Operator, or other product offering. A quick start primarily consists of tasks and steps. Each task has multiple steps, and each quick start has multiple tasks. For example: Task 1 Step 1 Step 2 Step 3 Task 2 Step 1 Step 2 Step 3 Task 3 Step 1 Step 2 Step 3 6.2. Quick start user workflow When you interact with an existing quick start tutorial, this is the expected workflow experience: In the Administrator or Developer perspective, click the Help icon and select Quick Starts . Click a quick start card. In the panel that appears, click Start . Complete the on-screen instructions, then click . In the Check your work module that appears, answer the question to confirm that you successfully completed the task. If you select Yes , click to continue to the task. If you select No , repeat the task instructions and check your work again. Repeat steps 1 through 6 above to complete the remaining tasks in the quick start. After completing the final task, click Close to close the quick start. 6.3. Quick start components A quick start consists of the following sections: Card : The catalog tile that provides the basic information of the quick start, including title, description, time commitment, and completion status Introduction : A brief overview of the goal and tasks of the quick start Task headings : Hyper-linked titles for each task in the quick start Check your work module : A module for a user to confirm that they completed a task successfully before advancing to the task in the quick start Hints : An animation to help users identify specific areas of the product Buttons and back buttons : Buttons for navigating the steps and modules within each task of a quick start Final screen buttons : Buttons for closing the quick start, going back to tasks within the quick start, and viewing all quick starts The main content area of a quick start includes the following sections: Card copy Introduction Task steps Modals and in-app messaging Check your work module

Commands:
Chapter 67. ListenerStatus schema reference Used in: KafkaStatus Property Property type Description type string The type property has been deprecated. The type property is not used anymore. Use the name property with the same value. The name of the listener. name string The name of the listener. addresses ListenerAddress array A list of the addresses for this listener. bootstrapServers string A comma-separated list of host:port pairs for connecting to the Kafka cluster using this listener. certificates string array A list of TLS certificates which can be used to verify the identity of the server when connecting to the given listener. Set only for tls and external listeners.

Commands:
Chapter 27. Storage Driver Updates The hpsa driver has been upgraded to version 3.4.4-1-RH1. The qla2xxx driver has been upgraded to version 8.07.00.08.07.1-k1. The qla4xxx driver has been upgraded to version 5.04.00.04.07.01-k0. The qlcnic driver has been upgraded to version 5.3.61. The netxen_nic driver has been upgraded to version 4.0.82. The qlge driver has been upgraded to version 1.00.00.34. The bnx2fc driver has been upgraded to version 2.4.2. The bnx2i driver has been upgraded to version 2.7.10.1. The cnic driver has been upgraded to version 2.5.20. The bnx2x driver has been upgraded to version 1.710.51-0. The bnx2 driver has been upgraded to version 2.2.5. The megaraid_sas driver has been upgraded to version 06.805.06.01-rc1. The mpt2sas driver has been upgraded to version 18.100.00.00. The ipr driver has been upgraded to version 2.6.0. The kmod-lpfc packages have been added to Red Hat Enterprise Linux 7, which ensures greater stability when using the lpfc driver with Fibre Channel (FC) and Fibre Channel over Ethernet (FCoE) adapters. The lpfc driver has been upgraded to version 0:10.2.8021.1. The be2iscsi driver has been upgraded to version 10.4.74.0r. The nvme driver has been upgraded to version 0.9.

Commands:
22.6. Authentication Options for NTP NTPv4 added support for the Autokey Security Architecture, which is based on public asymmetric cryptography while retaining support for symmetric key cryptography. The Autokey Security Architecture is described in RFC 5906 Network Time Protocol Version 4: Autokey Specification . The man page ntp_auth(5) describes the authentication options and commands for ntpd . An attacker on the network can attempt to disrupt a service by sending NTP packets with incorrect time information. On systems using the public pool of NTP servers, this risk is mitigated by having more than three NTP servers in the list of public NTP servers in /etc/ntp.conf . If only one time source is compromised or spoofed, ntpd will ignore that source. You should conduct a risk assessment and consider the impact of incorrect time on your applications and organization. If you have internal time sources you should consider steps to protect the network over which the NTP packets are distributed. If you conduct a risk assessment and conclude that the risk is acceptable, and the impact to your applications minimal, then you can choose not to use authentication. The broadcast and multicast modes require authentication by default. If you have decided to trust the network then you can disable authentication by using disable auth directive in the ntp.conf file. Alternatively, authentication needs to be configured by using SHA1 or MD5 symmetric keys, or by public (asymmetric) key cryptography using the Autokey scheme. The Autokey scheme for asymmetric cryptography is explained in the ntp_auth(8) man page and the generation of keys is explained in ntp-keygen(8 ). To implement symmetric key cryptography, see Section 22.16.12, "Configuring Symmetric Authentication Using a Key" for an explanation of the key option.

Commands:
1.4. Know Your Resources System administration is mostly a matter of balancing available resources against the people and programs that use those resources. Therefore, your career as a system administrator will be a short and stress-filled one unless you fully understand the resources you have at your disposal. Some of the resources are ones that seem pretty obvious: System resources, such as available processing power, memory, and disk space Network bandwidth Available money in the IT budget But some may not be so obvious: The services of operations personnel, other system administrators, or even an administrative assistant Time (often of critical importance when the time involves things such as the amount of time during which system backups may take place) Knowledge (whether it is stored in books, system documentation, or the brain of a person that has worked at the company for the past twenty years) It is important to note is that it is highly valuable to take a complete inventory of those resources available to you and to keep it current -- a lack of "situational awareness" when it comes to available resources can often be worse than no awareness at all.

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-06-24 11:20:34 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 7. Reviewing your Ansible configuration with Automation content navigator As a content creator, you can review your Ansible configuration with Automation content navigator and interactively delve into settings. 7.1. Reviewing your Ansible configuration from Automation content navigator You can review your Ansible configuration with the Automation content navigator text-based user interface in interactive mode and delve into the settings. Automation content navigator pulls in the results from an accessible Ansible configuration file, or returns the defaults if no configuration file is present. Prerequisites You have authenticated to the Red Hat registry if you need to access additional automation execution environments. See Red Hat Container Registry Authentication for details. Procedure Start Automation content navigator USD ansible-navigator Optional: type ansible-navigator config from the command line to access the Ansible configuration settings. Review the Ansible configuration. :config Some values reflect settings from within the automation execution environments needed for the automation execution environments to function. These display as non-default settings you cannot set in your Ansible configuration file. Type the number corresponding to the setting you want to delve into, or type :<number> for numbers greater than 9. ANSIBLE COW ACCEPTLIST (current: ['bud-frogs', 'bunny', 'cheese']) (default: 0│--- 1│current: 2│- bud-frogs 3│- bunny 4│- cheese 5│default: 6│- bud-frogs 7│- bunny 8│- cheese 9│- daemon The output shows the current setting as well as the default . Note the source in this example is env since the setting comes from the automation execution environments. Verification Review the configuration output. Additional resources ansible-config . Introduction to Ansible configuration .

Commands:
ansible-navigator
:config
ANSIBLE COW ACCEPTLIST (current: ['bud-frogs', 'bunny', 'cheese']) (default: 0│--- 1│current: 2│- bud-frogs 3│- bunny 4│- cheese 5│default: 6│- bud-frogs 7│- bunny 8│- cheese 9│- daemon
7.205. quota 7.205.1. RHBA-2012:1472 - quota bug fix update Updated quota packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The quota packages contain a suite of system administration tools for monitoring and limiting user and group disk usage on file systems. Bug Fixes BZ# 680919 Prior to this update, warnquota sent emails from <root@myhost.com> if the quota limit was exceeded and the warnquota tool was enabled to send warning emails and the default warnquota configuration was not changed. As a consequence, users could wrongly reply to this address and email bounces were delivered to the mailbox of <root@myhost.com>. This update modifies the default warnquota configuration to use the reserved domain "example.com". BZ# 683554 Prior to this update, the option "-r" for setquota and edquota failed to set the grace times for NFS-mounted file systems without reporting errors because the underlying remote procedure call protocol does not support this option. This update disables the option "-r". With this update, the option to set grace times over the network is disabled and error messages are sent when using the "-r" option. BZ#692390 Prior to this update, the quotacheck tool could mishandle UIDs in processed fsv1 quota files if a user's block limit was reached. This update zeroes uninitialized padding in the "v2r1 ddquot" structure before running subsequent checks. BZ# 704216 Prior to this update, the edquota tool could abort with a segmentation fault if the name server switch was configured to use the libdb back end. This update modifies the underlying code to make the "dirname" symbol in edquota sources static to avoid pollution of the symbol name space confusing the dynamic linker. Now, edquota runs on systems which use the Berkeley DB (BDB) database for storing user names, group names, or passwords. BZ# 730057 Prior to this update, the quota_nld service logged the error message "Failed to find tty of [UID] to report warning to" when users without an interactive session exceeded the disk quota limit while running quota_nld service. This update applies these warnings to non-daemon debugging mode of quota_nld only. BZ#770307 Prior to this update, the warnquota tool sent a badly worded email message. This update changes the wording and the text is now worded more representative.( All users of quota are advised to upgrade to these updated packages, which fix these bugs.

Commands:
26.2. The z/VM Configuration File This applies only if installing under z/VM. Under z/VM, you can use a configuration file on a CMS-formatted disk. The purpose of the CMS configuration file is to save space in the parameter file by moving the parameters that configure the initial network setup, the DASD, and the FCP specification out of the parameter file (refer to Section 26.3, "Installation Network Parameters" ). Each line of the CMS configuration file contains a single variable and its associated value, in the following shell-style syntax: variable = value . You must also add the CMSDASD and CMSCONFFILE parameters to the parameter file. These parameters point the installation program to the configuration file: CMSDASD= cmsdasd_address Where cmsdasd_address is the device number of a CMS-formatted disk that contains the configuration file. This is usually the CMS user"s A disk. For example: CMSDASD=191 CMSCONFFILE= configuration_file Where configuration_file is the name of the configuration file. This value must be specified in lower case. It is specified in a Linux file name format: CMS_file_name . CMS_file_type . The CMS file REDHAT CONF is specified as redhat.conf . The CMS file name and the file type can each be from one to eight characters that follow the CMS conventions. For example: CMSCONFFILE=redhat.conf

Commands:
3.3.5. Converting a VMware ESX / ESX(i) virtual machine Important When converting a Windows virtual machine from VMware ESX / ESX(i), ensure that VMware Tools is not installed on the virtual machine. The VMware Tools must be uninstalled prior to the conversion process. If a virtual machine is converted with the VMware Tools installed, it will not function correctly. Ensure that the virtual machine is stopped prior to running the v2v process. To convert the virtual machine, run: Where esx.example.com is the VMware ESX / ESX(i) server, pool is the local storage pool to hold the image, bridge_name is the name of a local network bridge to connect the converted virtual machine's network to, and guest_name is the name of the virtual machine. You may also use the --network parameter to connect to a locally managed network if your virtual machine only has a single network interface. If your virtual machine has multiple network interfaces, edit /etc/virt-v2v.conf to specify the network mapping for all interfaces. 3.3.5.1. Authenticating to the ESX / ESX(i) server Connecting to the ESX / ESX(i) server will require authentication. virt-v2v supports password authentication when connecting to ESX / ESX(i). It reads passwords from USDHOME/.netrc . The format of this file is described in the netrc(5) man page. An example entry is: Note The .netrc file must have a permission mask of 0600 to be read correctly by virt-v2v .

Commands:
virt-v2v -ic esx://esx.example.com/ -op pool --bridge bridge_name guest_name
machine esx.example.com login root password s3cr3t
Chapter 2. Architectures Red Hat Enterprise Linux 8.7 is distributed with the kernel version 4.18.0-425, which provides support for the following architectures: AMD and Intel 64-bit architectures The 64-bit ARM architecture IBM Power Systems, Little Endian 64-bit IBM Z Make sure you purchase the appropriate subscription for each architecture. For more information, see Get Started with Red Hat Enterprise Linux - additional architectures . For a list of available subscriptions, see Subscription Utilization on the Customer Portal.

Commands:
C.22. Transport org.infinispan.server.core.transport.NettyTransport The Transport component manages read and write operations to and from the server. Table C.35. Attributes Name Description Type Writable hostName Returns the host to which the transport binds. String No idleTimeout Returns the idle timeout. String No numberOfGlobalConnections Returns a count of active connections in the cluster. This operation will make remote calls to aggregate results, so latency may have an impact on the speed of calculation for this attribute. Integer false numberOfLocalConnections Returns a count of active connections this server. Integer No numberWorkerThreads Returns the number of worker threads. String No port Returns the port to which the transport binds. String receiveBufferSize Returns the receive buffer size. String No sendBufferSize Returns the send buffer size. String No totalBytesRead Returns the total number of bytes read by the server from clients, including both protocol and user information. String No totalBytesWritten Returns the total number of bytes written by the server back to clients, including both protocol and user information. String No tcpNoDelay Returns whether TCP no delay was configured or not. String No 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands: