mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix A. Using your subscription Service Registry 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 Red Hat Integration entries in the Integration and Automation category. Select the desired Service Registry product. The Software Downloads page opens. Click the Download link for your component. Revised on 2024-03-22 13:18:41 UTC

Commands:
8.202. rp-pppoe 8.202.1. RHEA-2014:0424 - rp-pppoe enhancement update Updated rp-pppoe packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The rp-pppoe packages provide the Roaring Penguin PPPoE (Point-to-Point Protocol over Ethernet) client, a user-mode program that does not require any kernel modifications. This client is fully compliant with RFC 2516, the official PPPoE specification. Enhancement BZ# 1009268 In Red Hat Enterprise Linux 6, the adsl-setup script in the rp-pppoe packages was renamed to pppoe-setup. To assist users migrating from Red Hat Enterprise Linux 5 to Red Hat Enterprise Linux 6, a symbolic link has been created to allow the old script name to continue to work. Users of rp-pppoe are advised to upgrade to these updated packages, which add this enhancement.

Commands:
Chapter 4. Application streams Red Hat Enterprise Linux 8 introduces the concept of Application Streams. Multiple versions of user space components are now delivered and updated more frequently than the core operating system packages. This provides greater flexibility to customize Red Hat Enterprise Linux without impacting the underlying stability of the platform or specific deployments. Components made available as Application Streams can be packaged as modules or RPM packages and are delivered through the AppStream repository in RHEL 8. Each Application Stream component has a given life cycle, either the same as RHEL 8 or shorter. For details, see Red Hat Enterprise Linux Life Cycle . Modules are collections of packages representing a logical unit: an application, a language stack, a database, or a set of tools. These packages are built, tested, and released together. Module streams represent versions of the Application Stream components. For example, several streams (versions) of the PostgreSQL database server are available in the postgresql module with the default postgresql:10 stream. Only one module stream can be installed on the system. Different versions can be used in separate containers. Detailed module commands are described in the Installing, managing, and removing user-space components document. For a list of modules available in AppStream, see the Package manifest .

Commands:
Chapter 1. OpenShift Service Mesh release notes 1.1. Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message . Important Red Hat OpenShift Service Mesh 3.0 is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope . 1.2. Red Hat OpenShift Service Mesh 3.0 Technology Preview This release of Red Hat OpenShift Service Mesh is Technology Preview. 1.2.1. Supported component versions for Technology Preview 2 Component Version OpenShift Container Platform 4.14 and later Istio 1.24.1 Envoy Proxy 1.32 Kiali Operator 2.1 Kiali Server 2.1 Important You need to remove the Kiali custom resources (CR) from Technology Preview 1 before you update to Kiali Operator provided by Red Hat 2.1. Kiali Operator provided by Red Hat 2.1 is available in the candidates channel. The candidate channel offers unsupported early access to releases as soon as they are built. Releases present only in candidate channels might not contain the full feature set of eventual GA releases, or features might be removed before GA. Additionally, these releases have not been subject to full Red Hat Quality Assurance and might not offer update paths to later GA releases. Given these caveats, the candidate channel is suitable only for testing purposes where deleting and re-creating a cluster is acceptable. 1.2.2. Unavailable features in Technology Preview 2 The following features are not supported in the Technology Preview 2 release: Ambient mode in Istio Virtual Machine support in Istio 1.2.3. Unavailable clusters in Technology Preview 2 The following clusters are not supported in the Technology Preview 2 release: Production clusters 1.2.4. Supported component versions for Technology Preview 1 Component Version OpenShift Container Platform 4.14+ Istio 1.23.0 Envoy Proxy 1.31 Kiali Operator 1.89 Kiali Server 1.89 1.2.5. Unavailable features in Technology Preview 1 The following features are not supported in the Technology Preview 1 release: OpenShift Service Mesh Console (OSSMC) plugin Ambient mode in Istio Virtual Machine support in Istio 1.2.6. Unavailable clusters in Technology Preview 1 The following clusters are not supported in the Technology Preview 1 release: Production clusters

Commands:
7.12. RHEA-2014:1518 - new packages: libee New libee packages are now available for Red Hat Enterprise Linux 6. The libee packages contain an event expression library inspired by the Common Event Expression (CEE), a standard proposed by the MITRE organization that is used to describe network events in a number of normalized formats. Its goal is to unify many different representations that exist in the industry. The core idea of libee is to provide a small API layer above the CEE standard. This enhancement update adds the libee packages to Red Hat Enterprise Linux 6. (BZ# 966972 ) All users who require libee are advised to install these new packages.

Commands:
10.2.4. Modules and Apache HTTP Server 2.0 In Apache HTTP Server 2.0, the module system has been changed to allow modules to be chained together or combined in new and interesting ways. Common Gateway Interface ( CGI ) scripts, for example, can generate server-parsed HTML documents which can then be processed by mod_include . This opens up a tremendous number of possibilities with regards to how modules can be combined to achieve a specific goal. The way this works is that each request is served by exactly one handler module followed by zero or more filter modules. Under Apache HTTP Server 1.3, for example, a Perl script would be handled in its entirety by the Perl module ( mod_perl ). Under Apache HTTP Server 2.0, the request is initially handled by the core module - which serves static files - and is then filtered by mod_perl . Exactly how to use this, and all other new features of Apache HTTP Server 2.0, is beyond the scope of this document; however, the change has ramifications if the PATH_INFO directive is used for a document which is handled by a module that is now implemented as a filter, as each contains trailing path information after the true file name. The core module, which initially handles the request, does not by default understand PATH_INFO and returns 404 Not Found errors for requests that contain such information. As an alternative, use the AcceptPathInfo directive to coerce the core module into accepting requests with PATH_INFO . The following is an example of this directive: For more on this topic, refer to the following documentation on the Apache Software Foundation's website: http://httpd.apache.org/docs-2.0/mod/core.html#acceptpathinfo http://httpd.apache.org/docs-2.0/handler.html http://httpd.apache.org/docs-2.0/filter.html 10.2.4.1. The suexec Module In Apache HTTP Server 2.0, the mod_suexec module uses the SuexecUserGroup directive, rather than the User and Group directives, which is used for configuring virtual hosts. The User and Group directives can still be used in general, but are deprecated for configuring virtual hosts. For example, the following is a sample Apache HTTP Server 1.3 directive: To migrate this setting to Apache HTTP Server 2.0, use the following structure:

Commands:
AcceptPathInfo on
<VirtualHost vhost.example.com:80> User someone Group somegroup </VirtualHost>
<VirtualHost vhost.example.com:80> SuexecUserGroup someone somegroup </VirtualHost>
function::user_char_warn Name function::user_char_warn - Retrieves a char value stored in user space. Synopsis Arguments addr The user space address to retrieve the char from. General Syntax user_char_warn:long(addr:long) Description Returns the char value from a given user space address. Returns zero when user space and warns (but does not abort) about the failure.

Commands:
function user_char_warn:long(addr:long)
Chapter 4. Deployment workflow The workflow for deploying Red Hat Hyperconverged Infrastructure for Virtualization is as follows: Check requirements. Verify that your planned deployment meets support requirements: Requirements , and fill in the installation checklist so that you can refer to it during the deployment process. Install operating systems. Install an operating system on each physical machine that will act as a hyperconverged host: Installing hyperconverged hosts . (Optional) Install an operating system on each physical or virtual machine that will act as an Network-Bound Disk Encryption (NBDE) key server: Installing NBDE key servers . Configure authentication between hyperconverged hosts. Configure key-based SSH authentication without a password to enable automated configuration of the hosts: Configure key-based SSH authentication . (Optional) Configure disk encryption. Configure NBDE key servers . Configure hyperconverged hosts as NBDE clients . Configure the hyperconverged cluster: Configure Red Hat Gluster Storage on hyperconverged hosts using the Web Console . Deploy the Hosted Engine virtual machine using the web console . Configure hyperconverged nodes using the RHV Administration Portal .

Commands:
Chapter 5. Advisories related to this release The following advisories are issued to document bug fixes and CVE fixes included in this release: RHSA-2023:4157 RHSA-2023:4158 RHSA-2023:4161 RHSA-2023:4162 RHSA-2023:4163 RHSA-2023:4164 RHSA-2023:4165 RHSA-2023:4175 RHSA-2023:4208 RHSA-2023:4233 Revised on 2024-05-09 16:47:39 UTC

Commands:
Chapter 7. Configuring the environment mode in KIE Server and Business Central You can set KIE Server to run in production mode or in development mode. Development mode provides a flexible deployment policy that enables you to update existing deployment units (KIE containers) while maintaining active process instances for small changes. It also enables you to reset the deployment unit state before updating active process instances for larger changes. Production mode is optimal for production environments, where each deployment creates a new deployment unit. In a development environment, you can click Deploy in Business Central to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option in Business Central is disabled and you can click only Deploy to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. Procedure To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. Note By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode.

Commands:
14.8. Starting, Suspending, Resuming, Saving, and Restoring a Guest Virtual Machine This section provides information on starting, suspending, resuming, saving, and restoring guest virtual machines. 14.8.1. Starting a Defined Domain The virsh start domain --console --paused --autodestroy --bypass-cache --force-boot --pass-fds command starts a inactive domain that was already defined but whose state is inactive since its last managed save state or a fresh boot. The command can take the following options: --console - will boot the domain attaching to the console --paused - If this is supported by the driver it will boot the domain and then put it into a paused state --autodestroy - the guest virtual machine is automatically destroyed when the virsh session closes or the connection to libvirt closes, or it otherwise exits --bypass-cache - used if the domain is in the managedsave state. If this is used, it will restore the guest virtual machine, avoiding the system cache. Note this will slow down the restore process. --force-boot - discards any managedsave options and causes a fresh boot to occur --pass-fds - is a list of additional options separated by commas, which are passed onto the guest virtual machine.

Commands:
Preface Depending on the type of your deployment, you can choose one of the following procedures to replace a storage device: For dynamically created storage clusters deployed on AWS, see: Section 1.1, "Replacing operational or failed storage devices on AWS user-provisioned infrastructure" . Section 1.2, "Replacing operational or failed storage devices on AWS installer-provisioned infrastructure" . For dynamically created storage clusters deployed on VMware, see Section 2.1, "Replacing operational or failed storage devices on VMware infrastructure" . For dynamically created storage clusters deployed on Red Hat Virtualization, see Section 3.1, "Replacing operational or failed storage devices on Red Hat Virtualization installer-provisioned infrastructure" . For dynamically created storage clusters deployed on Microsoft Azure, see Section 4.1, "Replacing operational or failed storage devices on Azure installer-provisioned infrastructure" . For storage clusters deployed using local storage devices, see: Section 5.1, "Replacing operational or failed storage devices on clusters backed by local storage devices" . Section 5.2, "Replacing operational or failed storage devices on IBM Power" . Section 5.3, "Replacing operational or failed storage devices on IBM Z or IBM LinuxONE infrastructure" . Note OpenShift Data Foundation does not support heterogeneous OSD sizes.

Commands:
B.31.3. RHSA-2011:0169 - Critical: java-1.5.0-ibm security and bug fix update Updated java-1.5.0-ibm packages that fix multiple security issues and one bug are now available for Red Hat Enterprise Linux 4 Extras, and Red Hat Enterprise Linux 5 and 6 Supplementary. The Red Hat Security Response Team has rated this update as having critical 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. The IBM 1.5.0 Java release includes the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. CVE-2010-3553 , CVE-2010-3557 , CVE-2010-3571 This update fixes multiple vulnerabilities in the IBM Java 2 Runtime Environment and the IBM Java 2 Software Development Kit. Detailed vulnerability descriptions are linked from the IBM "Security alerts" page. Bug Fix BZ# 659710 An error in the java-1.5.0-ibm RPM spec file caused an incorrect path to be included in HtmlConverter, preventing it from running. All users of java-1.5.0-ibm are advised to upgrade to these updated packages, containing the IBM 1.5.0 SR12-FP3 Java release. All running instances of IBM Java must be restarted for this update to take effect.

Commands:
15.3.4. Installing via NFS The NFS dialog applies only if you selected NFS Image in the Installation Method dialog. If you used the repo=nfs boot option, you already specified a server and path. Figure 15.10. NFS Setup Dialog Enter the domain name or IP address of your NFS server in the NFS server name field. For example, if you are installing from a host named eastcoast in the domain example.com , enter eastcoast.example.com . Enter the name of the exported directory in the Red Hat Enterprise Linux 6.9 directory field: If the NFS server is exporting a mirror of the Red Hat Enterprise Linux installation tree, enter the directory which contains the root of the installation tree. If everything was specified properly, a message appears indicating that the installation program for Red Hat Enterprise Linux is running. If the NFS server is exporting the ISO image of the Red Hat Enterprise Linux DVD, enter the directory which contains the ISO image. If you followed the setup described in Section 12.1.2, "Preparing for an NFS Installation" , the exported directory is the one that you specified as publicly_available_directory . Specify any NFS mount options that you require in the NFS mount options field. Refer to the man pages for mount and nfs for a comprehensive list of options. If you do not require any mount options, leave the field empty. Proceed with Chapter 16, Installing Using Anaconda .

Commands:
3.12. Network Labels You can use network labels to simplify several administrative tasks associated with creating and administering logical networks and associating those logical networks with physical host network interfaces and bonds. A network label is a plain text, human readable label that you can attach to a logical network or a physical host network interface. Follow these rules when creating a label: There is no limit on the length of a label. You must use a combination of lowercase and uppercase letters, underscores and hyphens. You cannot use use spaces or special characters. Attaching a label to a logical network or physical host network interface creates an association with other logical networks or physical host network interfaces to which the same label has been attached: Network Label Associations When you attach a label to a logical network, that logical network will be automatically associated with any physical host network interfaces with the given label. When you attach a label to a physical host network interface, any logical networks with the given label will be automatically associated with that physical host network interface. Changing the label attached to a logical network or physical host network interface is the same as removing a label and adding a new label. The association between related logical networks or physical host network interfaces is updated. Network Labels and Clusters When a labeled logical network is added to a cluster and there is a physical host network interface in that cluster with the same label, the logical network is automatically added to that physical host network interface. When a labeled logical network is detached from a cluster and there is a physical host network interface in that cluster with the same label, the logical network is automatically detached from that physical host network interface. Network Labels and Logical Networks With Roles When a labeled logical network is assigned to act as a display network or migration network, that logical network is then configured on the physical host network interface using DHCP so that the logical network can be assigned an IP address. Setting a label on a role network (for instance, "a migration network" or "a display network") causes a mass deployment of that network on all hosts. Such mass additions of networks are achieved through the use of DHCP. This method of mass deployment was chosen over a method of typing in static addresses, because of the unscalable nature of the task of typing in many static IP addresses.

Commands:
14.2.2. Starting an OpenSSH Server In order to run an OpenSSH server, you must have the openssh-server installed (see Section 8.2.4, "Installing Packages" for more information on how to install new packages in Red Hat Enterprise Linux 6). To start the sshd daemon, type the following at a shell prompt: To stop the running sshd daemon, use the following command: If you want the daemon to start automatically at the boot time, type: This will enable the service for levels 2, 3, 4, and 5. For more configuration options, see Chapter 12, Services and Daemons for the detailed information on how to manage services. Note that if you reinstall the system, a new set of identification keys will be created. As a result, clients who had connected to the system with any of the OpenSSH tools before the reinstall will see the following message: To prevent this, you can backup the relevant files from the /etc/ssh/ directory (see Table 14.1, "System-wide configuration files" for a complete list), and restore them whenever you reinstall the system.

Commands:
~]# service sshd start
~]# service sshd stop
~]# chkconfig sshd on
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY! Someone could be eavesdropping on you right now (man-in-the-middle attack)! It is also possible that the RSA host key has just been changed.