mtpti5iD/redhat-docs_dataset huggingface dataset:
18.3.3. Installation using VNC Using VNC is recommended for slow or long-distance network connections. To use VNC, disable X11 forwarding in your SSH client prior to connecting to the temporary Linux installation system. The loader will then provide a choice between text-mode and VNC; choose VNC here. Alternatively, provide the vnc variable and optionally the vncpassword variable in your parameter file (refer to Section 26.4, "VNC and X11 Parameters" for details). A message on the workstation SSH terminal prompts you to start the VNC client viewer and provides details about the VNC display specifications. Enter the specifications from the SSH terminal into the VNC client viewer and connect to the temporary Linux installation system to begin the installation. Refer to Chapter 31, Installing Through VNC for details.

Commands:
Chapter 4. Configuring automation controller websocket connections You can configure automation controller in order to align the websocket configuration with your nginx or load balancer configuration. 4.1. Websocket configuration for automation controller Automation controller nodes are interconnected through websockets to distribute all websocket-emitted messages throughout your system. This configuration setup enables any browser client websocket to subscribe to any job that might be running on any automation controller node. Websocket clients are not routed to specific automation controller nodes. Instead, any automation controller node can handle any websocket request and each automation controller node must know about all websocket messages destined for all clients. You can configure websockets at /etc/tower/conf.d/websocket_config.py in all of your automation controller nodes and the changes will be effective after the service restarts. Automation controller automatically handles discovery of other automation controller nodes through the Instance record in the database. Important Your automation controller nodes are designed to broadcast websocket traffic across a private, trusted subnet (and not the open Internet). Therefore, if you turn off HTTPS for websocket broadcasting, the websocket traffic, composed mostly of Ansible playbook stdout, is sent unencrypted between automation controller nodes. 4.1.1. Configuring automatic discovery of other automation controller nodes You can configure websocket connections to enable automation controller to automatically handle discovery of other automation controller nodes through the Instance record in the database. Edit automation controller websocket information for port and protocol, and confirm whether to verify certificates with True or False when establishing the websocket connections: BROADCAST_WEBSOCKET_PROTOCOL = 'http' BROADCAST_WEBSOCKET_PORT = 80 BROADCAST_WEBSOCKET_VERIFY_CERT = False Restart automation controller with the following command: USD automation-controller-service restart

Commands:
BROADCAST_WEBSOCKET_PROTOCOL = 'http' BROADCAST_WEBSOCKET_PORT = 80 BROADCAST_WEBSOCKET_VERIFY_CERT = False
automation-controller-service restart
Appendix B. Revision History Revision History Revision 6-0.2 Mon Feb 18 2013 Martin Prpic Removed incorrect information about rt2800usb / rt2x00 being updated. Revision 1-0 Wed Jun 20 2012 Martin Prpic Release of the Red Hat Enterprise Linux 6.3 Release Notes. Revision 0-0 Tue Apr 24 2012 Martin Prpic Release of the Red Hat Enterprise Linux 6.3 Beta Release Notes.

Commands:
Chapter 1. Overview NET images are added to OpenShift by importing imagestream definitions from s2i-dotnetcore . The imagestream definitions include the dotnet imagestream which contains sdk images for different supported versions of .NET. Life Cycle and Support Policies for the .NET Program provides an up-to-date overview of supported versions. Version Tag Alias .NET 6.0 dotnet:6.0-ubi8 dotnet:6.0 .NET 7.0 dotnet:7.0-ubi8 dotnet:7.0 .NET 8.0 dotnet:8.0-ubi8 dotnet:8.0 The sdk images have corresponding runtime images which are defined under the dotnet-runtime imagestream. The container images work across different versions of Red Hat Enterprise Linux and OpenShift. The UBI-8 based images (suffix -ubi8) are hosted on the registry.access.redhat.com and do not require authentication.

Commands:
23.15.5. Recommended Partitioning Scheme Configuring efficient swap space for Linux on System z is a complex task. It very much depends on the specific environment and should be tuned to the actual system load. Refer to the following resources for more information and to guide your decision: 'Chapter 7. Linux Swapping' in the IBM Redbooks publication Linux on IBM System z: Performance Measurement and Tuning [ IBM Form Number SG24-6926-01 ], [ ISBN 0738485586 ], available from http://www.redbooks.ibm.com/abstracts/sg246926.html Linux Performance when running under VM , available from http://www.vm.ibm.com/perf/tips/linuxper.html

Commands:
4.266. redhat-release 4.266.1. RHEA-2011:1743 - redhat-release enhancement update for Red Hat Enterprise Linux 6.2 An enhanced redhat-release package is now available for Red Hat Enterprise Linux 6.2. The redhat-release package contains licensing information regarding, and identifies the installed version of, Red Hat Enterprise Linux. This updated redhat-release package reflects changes made for the release of Red Hat Enterprise Linux 6.2. Users of Red Hat Enterprise Linux 6 are advised to upgrade to this updated redhat-release package, which adds this enhancement.

Commands:
C.3. Opening a Perspective There are two ways to open a perspective: Using the Open Perspective button on the shortcut bar. Selecting a perspective from the Window > Perspective > Open Perspective menu. To open a perspective by using the shortcut bar button: Click the Open Perspective button . In the Select Perspective dialog, select Teiid Designer and click OK . Figure C.2. Select Perspective Dialog The Teiid Designer perspective is now displayed. There are few additional features of perspectives to take note of. The shortcut bar may contain multiple perspectives. The perspective button which is pressed in, indicates that it is the current perspective. To display the full name of the perspectives, right-click the perspective bar and click Show Text and conversely click Hide Text to only show icons. To quickly switch between open perspectives, select the desired perspective button. Notice that the set of views is different for each of the perspectives. Figure C.3. Workbench Window Title Bar

Commands:
10.3. Scheduling Policy Elements The scheduling_policy element contains the following elements: Table 10.3. Scheduling policy elements Element Type Description Properties policy enumerated The VM scheduling mode for hosts in the cluster. A list of enumerated types are listed in capabilities . thresholds low= high= duration= complex Defines CPU limits for the host. The high attribute controls the highest CPU usage percentage the host can have before being considered overloaded. The low attribute controls the lowest CPU usage percentage the host can have before being considered underutilized. The duration attribute refers to the number of seconds the host needs to be overloaded before the scheduler starts and moves the load to another host.

Commands:
1.12. Additional Data Source Connection Properties When using the driver class, various properties are derived from the URL. For the data source class, these properties are set using the following additional methods: Table 1.3. Data Source Connection Properties Method Name Type Description setAlternateServers String Optional delimited list of host:port entries. Refer to Section 2.1, "Using Multiple Hosts" for more information. setAdditionalProperties String Optional setting of properties that has the same format as the property string in a driver connection URL. Refer to Section 1.8, "Driver Connection URL Format" setDatabaseName String The name of a virtual database (VDB) deployed to JBoss Data Virtualization. Important VDB names can contain version information; for example, myvdb.2 . If such a name is used in the URL, this has the same effect as supplying a version=2 connection property. Note that if the VDB name contains version information, you cannot also use the version property in the same request. setDatabaseVersion String The VDB version. setDataSourceName String The name given to this data source setPortNumber int The port number on which the server process is listening. setServerName String The server hostname where the JBoss Data Virtualization runtime is installed. setSecure boolean Secure connection. Flag to indicate to use SSL (mms) based connection between client and server. Note All of the URL Connection Properties can be used on the data source. To do so, use the AdditionalProperties setter method if the corresponding setter method is not already available.

Commands:
28.2. GOOGLE_PING Configuration Red Hat JBoss Data Grid works with Google Compute Engine in the following way: In Library mode, use the JGroups' configuration file default-configs/default-jgroups-google.xml or use the GOOGLE_PING protocol in an existing configuration file. In Remote Client-Server mode, define the properties on the command line when you start the server to use the JGroups Google stack ( see example in Section 28.2.1, "Starting the Server in Google Compute Engine" ). To configure the GOOGLE_PING protocol to work in Google Compute Engine in Library and Remote Client-Server mode: Use JGroups bucket. These buckets use Google Compute Engine credentials. Use the access key. Use the secret access key. Note Only the TCP protocol is supported in Google Compute Engine since multicasts are not allowed. Report a bug 28.2.1. Starting the Server in Google Compute Engine This configuration requires access to a bucket that can only be accessed with the appropriate Google Compute Engine credentials. Ensure that the GOOGLE_PING configuration includes the following properties: the access_key and the secret_access_key properties for the Google Compute Engine user. Example 28.1. Start the Red Hat JBoss Data Grid Server with a Bucket Run the following command from the top level of the server directory to start the Red Hat JBoss Data Grid server using a bucket: Replace {server_ip_address} with the server's IP address. Replace {google_bucket_name} with the appropriate bucket name. Replace {access_key} with the user's access key. Replace {secret_access_key} with the user's secret access key. Report a bug

Commands:
bin/clustered.sh -Djboss.bind.address= {server_ip_address} -Djboss.bind.address.management= {server_ip_address} -Djboss.default.jgroups.stack=google -Djgroups.google.bucket= {google_bucket_name} -Djgroups.google.access_key= {access_key} -Djgroups.google.secret_access_key= {secret_access_key}
Chapter 10. RHEL Installations on IBM Power Servers You can install Red Hat Enterprise Linux on various IBM Power System servers. 10.1. Supported IBM Power Servers You can install Red Hat Enterprise Linux on IBM Power Systems. You can find the complete list of supported IBM Power servers on the Red Hat Ecosystem Catalog . 10.2. Overview of the installation process on PowerVM LPAR by using the HMC You can install RHEL on the PowerVM logical partition (LPAR) by using the Hardware Management Console. A Hardware Management Console (HMC) is a hardware appliance that you can use to administer IBM Power Systems servers. The installation workflow involves the following general steps: Download the RHEL installation ISO. Prepare a bootable physical installation medium based on your installation method. Verify that the Power System is added to the HMC. For more information, see add or remove connections to HMC in the IBM documentation. Configure VIOS and LPAR on the managed system or configure full system LPAR based on the requirements. Log in to the HMC console. Install Red Hat Enterprise Linux. For detailed instructions, see Installing Linux on PowerVM LPAR by using the HMC in the IBM documentation. 10.3. Overview of the installation process on IBM Power Servers with the graphics card You can install RHEL on IBM Power Systems servers with the graphics card. The installation workflow involves the following general steps: Download the RHEL installation ISO. Prepare a bootable physical installation medium based on your installation method. Prepare the machine for RHEL installation. Boot the installer kernel. Install Red Hat Enterprise Linux. Optional: Install IBM Tools Repository to use Service and Productivity tools, IBM Advance Toolchain for Linux on Power, and IBM SDK for PowerLinux. For detailed instructions, see Installing Linux on Power Systems servers with a graphics card in the IBM documentation. Additional resources For instructions to install hardware in a rack, see IBM Knowledge Center and search for your power hardware. 10.4. Overview of the installation process on IBM Power Servers by using the serial console You can install RHEL on IBM Power Systems servers by using the serial console. The installation workflow involves the following general steps: Download the RHEL installation ISO. Prepare a bootable physical installation medium based on your installation method. Prepare your machine for the RHEL installation. Boot the installer kernel. Start a VNC session. For more information, see Preparing a remote installation by using VNC . Install Red Hat Enterprise Linux. Optional: Install IBM Tools Repository to use additional software. For more information, see IBM Linux on Power tools repository . For detailed instructions, see Installing Linux on Power Systems servers by using the serial console in the IBM documentation.

Commands:
Appendix A. Using your subscription AMQ Streams 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 AMQ Streams entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Revised on 2021-04-30 09:47:31 UTC

Commands:
Chapter 1. Installing the client package Install the Insights client on each system. Procedure Enter the following command to install the current version of the Insights client: 1.1. Configuring authentication Once you have installed the client package, you need to configure authentication. Use one of two methods: Activation keys (recommended) Registering the Insights client with Red Hat Subscription Manager (RHSM) For more information about authentication, refer to Client Configuration Guide for Red Hat Insights .

Commands:
yum install insights-client
Chapter 1. Introduction to database servers A database server is a service that provides features of a database management system (DBMS). DBMS provides utilities for database administration and interacts with end users, applications, and databases. Red Hat Enterprise Linux 9 provides the following database management systems: MariaDB 10.5 MariaDB 10.11 - available since RHEL 9.4 MySQL 8.0 PostgreSQL 13 PostgreSQL 15 - available since RHEL 9.2 PostgreSQL 16 - available since RHEL 9.4 Redis 6

Commands:
Chapter 4. Performing maintenance on Compute nodes and Controller nodes with Instance HA To perform maintenance on a Compute node or a Controller node with Instance HA, stop the node by setting it in standby mode and disabling the Pacemaker resources on the node. After you complete the maintenance work, you start the node and check that the Pacemaker resources are healthy. Prerequisites A running overcloud with Instance HA enabled Procedure Log in to a Controller node and stop the Compute or Controller node: Important You must log in to a different node from the node you want to stop. Disable the Pacemaker resources on the node: Perform any maintenance work on the node. Restore the IPMI connection and start the node. Wait until the node is ready before proceeding. Enable the Pacemaker resources on the node and start the node: If you set the node to maintenance mode, source the credential file for your overcloud and unset the node from maintenance mode: Verification Check that the Pacemaker resources are active and healthy: If any Pacemaker resources fail to start during the startup process, run the pcs resource cleanup command to reset the status and the fail count of the resource. If you evacuated instances from a Compute node before you stopped the node, check that the instances are migrated to a different node:

Commands:
pcs node standby <node UUID>
pcs resource disable <ocf::pacemaker:remote on the node>
pcs resource enable <ocf::pacemaker:remote on the node> pcs node unstandby <node UUID>
source stackrc openstack baremetal node maintenance unset <baremetal node UUID>
pcs status
openstack server list --long nova migration-list
1.4. Bookmarks 1.4.1. Saving a Query String as a Bookmark A bookmark can be used to remember a search query, and shared with other users. Procedure Enter the desired search query in the search bar and perform the search. Click the star-shaped Bookmark button to the right of the search bar. This opens the New Bookmark window. Enter the Name of the bookmark. Edit the Search string field, if required. Click OK . Click the Bookmarks icon ( ) in the header bar to find and select the bookmark. 1.4.2. Editing a Bookmark You can modify the name and search string of a bookmark. Procedure Click the Bookmarks icon ( ) in the header bar. Select a bookmark and click Edit . Change the Name and Search string fields as necessary. Click OK . 1.4.3. Deleting a Bookmark When a bookmark is no longer needed, remove it. Procedure Click the Bookmarks icon ( ) in the header bar. Select a bookmark and click Remove . Click OK .

Commands:
7.20. boost 7.20.1. RHBA-2015:1269 - boost bug update Updated boost packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The boost packages contain a large number of free peer-reviewed portable C++ source libraries. These libraries are suitable for tasks such as portable file-systems and time/date abstraction, serialization, unit testing, thread creation and multi-process synchronization, parsing, graphing, regular expression manipulation, and many others. Bug Fixes BZ# 1169501 When compiling a C++ program using the Boost.MPI library, the compiling process previously failed to find the "boost::mpi::environment::environment(bool)" symbol and terminated with an "undefined reference" error. This update adds the missing symbol, and the described compiling process now successfully creates an executable. BZ# 1128313 Previously, the boost packages could use packages for different architectures as their dependencies, which in some cases led to a variety of problems with the functionality of the Boost clients. With this update, dependency declarations specify the architecture of the package where relevant, and all packages necessary for correct operation of the Boost clients are downloaded properly. BZ# 1167383 , BZ# 1170010 Prior to this update, a number of Boost libraries were not compatible with the GNU Compiler Collection (GCC) provided with Red Hat Developer Toolset. A fix has been implemented to address this problem, and the affected libraries now properly work with Red Hat Developer Toolset GCC. Users of Boost are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 4. Physical and Virtual Memory All present-day, general-purpose computers are of the type known as stored program computers . As the name implies, stored program computers load instructions (the building blocks of programs) into some type of internal storage, where they subsequently execute those instructions. Stored program computers also use the same storage for data. This is in contrast to computers that use their hardware configuration to control their operation (such as older plugboard-based computers). The place where programs were stored on the first stored program computers went by a variety of names and used a variety of different technologies, from spots on a cathode ray tube, to pressure pulses in columns of mercury. Fortunately, present-day computers use technologies with greater storage capacity and much smaller size than ever before. 4.1. Storage Access Patterns One thing to keep in mind throughout this chapter is that computers tend to access storage in certain ways. In fact, most storage access tends to exhibit one (or both) of the following attributes: Access tends to be sequential Access tends to be localized Sequential access means that, if address N is accessed by the CPU, it is highly likely that address N +1 will be accessed . This makes sense, as most programs consist of large sections of instructions that execute -- in order -- one after the other. Localized access means that, if address X is accessed, it is likely that other addresses surrounding X will also be accessed in the future. These attributes are crucial, because it allows smaller, faster storage to effectively buffer larger, slower storage. This is the basis for implementing virtual memory. But before we can discuss virtual memory, we must examine the various storage technologies currently in use.

Commands:
B.103. wireshark B.103.1. RHSA-2010:0924 - Moderate: wireshark security update Updated wireshark packages that fix two security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Wireshark is a program for monitoring network traffic. Wireshark was previously known as Ethereal. CVE-2010-4300 A heap-based buffer overflow flaw was found in the Wireshark Local Download Sharing Service (LDSS) dissector. If Wireshark read a malformed packet off a network or opened a malicious dump file, it could crash or, possibly, execute arbitrary code as the user running Wireshark. CVE-2010-3445 A denial of service flaw was found in Wireshark. Wireshark could crash or stop responding if it read a malformed packet off a network, or opened a malicious dump file. Users of Wireshark should upgrade to these updated packages, which contain Wireshark version 1.2.13, and resolve these issues. All running instances of Wireshark must be restarted for the update to take effect.

Commands: