mtpti5iD/redhat-docs_dataset huggingface dataset:
5.113. iprutils 5.113.1. RHBA-2012:1183 - iprutils bug fix update An updated iprutils package that fixes a bug now available for Red Hat Enterprise Linux 6. The iprutils package provides utilities to manage and configure SCSI devices that are supported by the IBM Power RAID SCSI storage device driver. Bug Fix BZ# 849556 Previously, a buffer overflow bug caused the iprconfig utility to terminate unexpectedly with a segmentation fault when displaying detailed information of a disk device. A patch has been provided to address this issue and iprconfig no longer crashes in the described scenario. All users of iprutils are advised to upgrade to this updated package, which fixes this bug. 5.113.2. RHBA-2012:0792 - iprutils bug fix and enhancement update Updated iprutils packages that fix multiple bugs add various enhancements is now available for Red Hat Enterprise Linux 6. The iprutils package provides utilities to manage and configure SCSI devices that are supported by the IBM Power RAID SCSI storage device driver. The iprutils package has been upgraded to upstream version 2.3.9, which fixes multiple bugs and adds multiple enhancements. These packages also add support for the CRoC-based 6 GB Serial Attached SCSI (SAS) vRAID adapters on IBM POWER7. (BZ# 738890 , BZ# 817087 ) All users of iprutils are advised to upgrade to these updated packages, which add fix these enhancements and add these enhancements.

Commands:
6.5. Restore an ext2/3/4 File System Procedure 6.2. Restore an ext2/3/4 File System Example If you are restoring an operating system partition, bootup your system into Rescue Mode. This step is not required for ordinary data partitions. Rebuild sda1/sda2/sda3/sda4/sda5 by using the fdisk command. Note If necessary, create the partitions to contain the restored file systems. The new partitions must be large enough to contain the restored data. It is important to get the start and end numbers right; these are the starting and ending sector numbers of the partitions. Format the destination partitions by using the mkfs command, as shown below. Important DO NOT format /dev/sda6 in the above example because it saves backup files. If creating new partitions, re-label all the partitions so they match the fstab file. This step is not required if the partitions are not being recreated. Prepare the working directories. Restore the data. If you want to restore from a remote host or restore from a backup file on a remote host you can use either ssh or rsh. You will need to configure a password-less login for the following examples: Login into 10.0.0.87, and restore sda1 from local sda1.dump file: Login into 10.0.0.87, and restore sda1 from a remote 10.66.0.124 sda1.dump file: Reboot.

Commands:
mkfs.ext3 /dev/sda1 mkfs.ext3 /dev/sda2 mkfs.ext3 /dev/sda3
e2label /dev/sda1 /boot1 e2label /dev/sda2 / e2label /dev/sda3 /data mkswap -L SWAP-sda5 /dev/sda5
mkdir /mnt/sda1 mount -t ext3 /dev/sda1 /mnt/sda1 mkdir /mnt/sda2 mount -t ext3 /dev/sda2 /mnt/sda2 mkdir /mnt/sda3 mount -t ext3 /dev/sda3 /mnt/sda3 mkdir /backup-files mount -t ext3 /dev/sda6 /backup-files
cd /mnt/sda1 restore -rf /backup-files/sda1.dump cd /mnt/sda2 restore -rf /backup-files/sda2.dump cd /mnt/sda3 restore -rf /backup-files/sda3.dump
ssh 10.0.0.87 "cd /mnt/sda1 && cat /backup-files/sda1.dump | restore -rf -"
ssh 10.0.0.87 "cd /mnt/sda1 && RSH=/usr/bin/ssh restore -r -f 10.66.0.124:/tmp/sda1.dump"
1.10.2. Documentation and Communication In the areas of documentation and communication, there is little that is specific to Red Hat Enterprise Linux. Since documentation and communication can consist of anything from adding comments to a text-based configuration file to updating a webpage or sending an email, a system administrator using Red Hat Enterprise Linux must have access to text editors, HTML editors, and mail clients. Here is a small sample of the many text editors available under Red Hat Enterprise Linux: The gedit text editor The Emacs text editor The Vim text editor The gedit text editor is a strictly graphical application (in other words, it requires an active X Window System environment), while vim and Emacs are primarily text-based in nature. The subject of the best text editor has sparked debate for nearly as long as computers have existed and will continue to do so. Therefore, the best approach is to try each editor for yourself, and use what works best for you. For HTML editors, system administrators can use the Composer function of the Mozilla Web browser. Of course, some system administrators prefer to hand-code their HTML, making a regular text editor a perfectly acceptable tool as well. As far as email is concerned, Red Hat Enterprise Linux includes the Evolution graphical email client, the Mozilla email client (which is also graphical), and mutt , which is text-based. As with text editors, the choice of an email client tends to be a personal one; therefore, the best approach is to try each client for yourself, and use what works best for you.

Commands:
Chapter 4. Configuring authentication for the web console on Linux, Windows, or macOS You can configure the web console to require authentication for access. To enable authentication, you have to install Red Hat Single Sign-On (SSO). Enabling authentication Procedure Adjust the port number that the Red Hat SSO server opens to avoid conflicts with the port that the web console uses by entering the following: For Linux and macOS: For Windows: Open the Red Hat SSO administration console from http://localhost:8180 : Username: admin Password: admin Add a realm named mtr . In the realm, create a client named mtr-web . Check that Access Type is set to public . Set Valid Redirect URIs to http://localhost:8080/windup-ui/* . Set Web Origins to * and click Save . Create a role named user . Create a user with any name. Set the credentials of the user, disable Temporary , and assign the role "user" to the user. Switch the web console to Authentication required mode by doing the following: Export the following ENV variables: For Linux and macOS: For Windows: Note Environment variables that are set by the set command in CMD are local, available to the current CMD session only. Use the Windows Control Panel to permanently set the environment variables. Run the following script: For Linux and macOS: For Windows: Start the web console by entering the following: For Linux and macOS: For Windows: Open the browser at http://localhost:8080/windup-ui . Disabling authentication Procedure Run the following script: For Linux and macOS: For Windows: Revised on 2024-09-12 13:53:30 UTC

Commands:
./standalone.sh -Djboss.socket.binding.port-offset=<offset_value>
> ...\bin\standalone.bat -Djboss.socket.binding.port-offset=<offset_value>
export SSO_AUTH_SERVER_URL=http://localhost:8180/auth export SSO_REALM=windup export SSO_SSL_REQUIRED=EXTERNAL export SSO_CLIENT_ID=windup-web
set SSO_AUTH_SERVER_URL=http://localhost:8180/auth set SSO_REALM=windup set SSO_SSL_REQUIRED=EXTERNAL set SSO_CLIENT_ID=windup-web
<MTR_HOME>/switch_to_authentication_required.sh
C:\<MTR_HOME>\switch_to_authentication_required.bat
<MTR_HOME>/run_windup.sh
C:\<MTR_HOME>\run_windup.bat
<MTR_HOME>/switch_to_automatic_authentication.sh
C:\<MTR_HOME>\switch_to_automatic_authentication.bat
3.17. RHEA-2011:1590 - new package: sanlock A new sanlock package is now available for Red Hat Enterprise Linux 6. The sanlock package provides a shared disk lock manager that uses disk paxos to manage leases on shared storage. Hosts connected to a common Storage Area Network (SAN) can use sanlock to synchronize the access to the shared disks. Both libvirt and vdsm can use sanlock to synchronize access to shared virtual machine (VM) images. This enhancement update adds the sanlock package to Red Hat Enterprise Linux 6. (BZ# 658971 ) All users who require sanlock are advised to install this new package.

Commands:
3.2. Prerequisites for Using realmd To use the realmd system, install the realmd package. In addition, make sure that the oddjob , oddjob-mkhomedir , sssd , and adcli packages are installed. These packages are required to be able to manage the system using realmd . Note As mentioned in Section 3.4, "Discovering and Joining Identity Domains" , you can simply use realmd to find out which packages to install.

Commands:
yum install realmd
Chapter 101. KafkaUserTlsClientAuthentication schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserTlsClientAuthentication type from KafkaUserTlsExternalClientAuthentication , KafkaUserScramSha512ClientAuthentication . It must have the value tls for the type KafkaUserTlsClientAuthentication . Property Description type Must be tls . string

Commands:
Chapter 7. Known issues 7.1. Ansible Lightspeed not connecting to Ansible server There is a known issue with Ansible Lightspeed and connection to the Ansible server. If the OpenShift Dev Spaces environment is not under *.openshiftapps.com domain, Ansible Lightspeed can not connect to the Ansible server. There is no workaround available. Additional resources CRW-5691 7.2. FIPS compliance update There's a known issue with FIPS compliance that results in certain cryptographic modules not being FIPS-validated. Below is a list of requirements and limitations for using FIPS with OpenShift Dev Spaces: Required cluster and operator updates Update your Red Hat OpenShift Container Platform installation to the latest z-stream update for 4.11, 4.12, or 4.13 as appropriate. If you do not already have FIPS enabled, you will need to uninstall and reinstall. Once the cluster is up and running, install OpenShift Dev Spaces 3.7.1 (3.7-264) and verify that the latest DevWorkspace operator bundle 0.21.2 (0.21-7) or newer is also installed and updated. See https://catalog.redhat.com/software/containers/devworkspace/devworkspace-operator-bundle/60ec9f48744684587e2186a3 Golang compiler in UDI image The Universal Developer Image (UDI) container includes a golang compiler, which was built without the CGO_ENABLED=1 flag. The check-payload scanner ( https://github.com/openshift/check-payload ) will throw an error, but this can be safely ignored provided that anything you build with this compiler sets the correct flag CGO_ENABLED=1 and does NOT use extldflags -static or -tags no_openssl . The resulting binaries can be scanned and should pass without error. Statically linked binaries You can find statically linked binaries not related to cryptography in these two containers: code-rhel8 idea-rhel8. As they are not related to cryptography, they do not affect FIPS compliance. Helm support for FIPS The UDI container includes the helm binary, which was not compiled with FIPS support. If you are in a FIPS environment do not use helm . Additional resources CRW-4598 7.3. Debugger does not work in the .NET sample Currently, the debugger in Microsoft Visual Studio Code - Open Source does not work in the .NET sample. Workaround Use a different image from the following sources: Custom UBI-9 based Dockerfile devfile.yaml Additional resources CRW-3563

Commands:
4.5.2. Best Case Performance Scenario At best, the overhead from virtual memory support presents a minimal additional load to a well-configured system: RAM -- Sufficient RAM for all working sets with enough left over to handle any page faults [12] Disk -- Because of the limited page fault activity, disk I/O bandwidth would be minimally impacted CPU -- The majority of CPU cycles are dedicated to actually running applications, instead of running the operating system's memory management code From this, the overall point to keep in mind is that the performance impact of virtual memory is minimal when it is used as little as possible. This means the primary determinant of good virtual memory subsystem performance is having enough RAM. in line (but much lower in relative importance) are sufficient disk I/O and CPU capacity. However, keep in mind that these resources only help the system performance degrade more gracefully from heavy faulting and swapping; they do little to help the virtual memory subsystem performance (although they obviously can play a major role in overall system performance). [12] A reasonably active system always experiences some level of page fault activity, due to page faults incurred as newly-launched applications are brought into memory.

Commands:
6.9. Multiple Monitoring Operations You can configure a single resource with as many monitor operations as a resource agent supports. In this way you can do a superficial health check every minute and progressively more intense ones at higher intervals. Note When configuring multiple monitor operations, you must ensure that no two operations are performed at the same interval. To configure additional monitoring operations for a resource that supports more in-depth checks at different levels, you add an OCF_CHECK_LEVEL= n option. For example, if you configure the following IPaddr2 resource, by default this creates a monitoring operation with an interval of 10 seconds and a timeout value of 20 seconds. If the Virtual IP supports a different check with a depth of 10, the following command causes Pacemaker to perform the more advanced monitoring check every 60 seconds in addition to the normal Virtual IP check every 10 seconds. (As noted, you should not configure the additional monitoring operation with a 10-second interval as well.)

Commands:
pcs resource create VirtualIP ocf:heartbeat:IPaddr2 ip=192.168.0.99 cidr_netmask=24 nic=eth2
pcs resource op add VirtualIP monitor interval=60s OCF_CHECK_LEVEL=10
Chapter 22. Installation Phase 2: Configuring Language and Installation Source Before the graphical installation program starts, you need to configure the language and installation source. By default, if you are installing interactively (with the default parameter file generic.prm ) the loader program to select language and installation source starts in text mode. In your new ssh session, the following message is displayed: 22.1. Non-interactive Line-Mode Installation If the cmdline option was specified as boot option in your parameter file ( Section 26.6, "Parameters for Kickstart Installations" ) or in your kickstart file (refer to Section 32.3, "Creating the Kickstart File" , the loader starts up with line-mode oriented text output. In this mode, all necessary information must be provided in the kickstart file. The installer does not allow user interaction and stops if there is unspecified installation information.

Commands:
Welcome to the anaconda install environment 1.2 for zSeries
Chapter 2. Installing Datadog for Ceph integration After installing the Datadog agent, configure the Datadog agent to report Ceph metrics to Datadog. Prerequisites Root-level access to the Ceph monitor node. Appropriate Ceph key providing access to the Red Hat Ceph Storage cluster. Internet access. Procedure Install the Ceph integration. Log in to the Datadog App . The user interface will present navigation on the left side of the screen. Click Integrations . Either enter ceph into the search field or scroll to find the Ceph integration. The user interface will present whether the Ceph integration is available or already installed . If it is available , click the button to install it. Configuring the Datadog agent for Ceph Navigate to the Datadog Agent configuration directory: Create a ceph.yaml file from the ceph.yml.sample file: Modify the ceph.yaml file: Example The following is a sample of what the modified ceph.yaml file looks like. Uncomment the -tags , -name , ceph_command , ceph_cluster , and use_sudo: True lines. The default values for ceph_command and ceph_cluster are /usr/bin/ceph and ceph respectively. When complete, it will look like this: Modify the sudoers file: Add the following line: Enable the Datadog agent so that it will restart if the Ceph host reboots: Restart the Datadog agent:

Commands:
cd /etc/dd-agent/conf.d
cp ceph.yaml.example ceph.yaml
vim ceph.yaml
init_config: instances: - tags: - name:mars_cluster # ceph_cmd: /usr/bin/ceph ceph_cluster: ceph # If your environment requires sudo, please add a line like: dd-agent ALL=(ALL) NOPASSWD:/usr/bin/ceph to your sudoers file, and uncomment the below option. # use_sudo: True
init_config: instances: - tags: - name:ceph-RHEL # ceph_cmd: /usr/bin/ceph ceph_cluster: ceph # If your environment requires sudo, please add a line like: dd-agent ALL=(ALL) NOPASSWD:/usr/bin/ceph to your sudoers file, and uncomment the below option. # use_sudo: True
visudo
dd-agent ALL=(ALL) NOPASSWD:/usr/bin/ceph
systemctl enable datadog-agent
systemctl status datadog-agent
Preface Welcome to the Red Hat JBoss Core Services version 2.4.57 release. Red Hat JBoss Core Services Apache HTTP Server is an open source web server developed by the Apache Software Foundation . The Apache HTTP Server includes the following features: Implements the current HTTP standards, including HTTP/1.1 and HTTP/2 Supports Transport Layer Security (TLS) encryption through OpenSSL , which provides secure connections between the web server and web clients. Supports extensible functionality through the use of modules, some of which are included with the Red Hat JBoss Core Services Apache HTTP Server.

Commands:
4.5. Space Indicated as Used in Empty File System If you have an empty GFS2 file system, the df command will show that there is space being taken up. This is because GFS2 file system journals consume space (number of journals * journal size) on disk. If you created a GFS2 file system with a large number of journals or specified a large journal size then you will be see (number of journals * journal size) as already in use when you execute the df command. Even if you did not specify a large number of journals or large journals, small GFS2 file systems (in the 1GB or less range) will show a large amount of space as being in use with the default GFS2 journal size.

Commands:
40.7. Example Usage While OProfile can be used by developers to analyze application performance, it can also be used by system administrators to perform system analysis. For example: Determine which applications and services are used the most on a system - opreport can be used to determine how much processor time an application or service uses. If the system is used for multiple services but is under performing, the services consuming the most processor time can be moved to dedicated systems. Determine processor usage - The CPU_CLK_UNHALTED event can be monitored to determine the processor load over a given period of time. This data can then be used to determine if additional processors or a faster processor might improve system performance.

Commands:
Chapter 2. Insights for Red Hat Enterprise Linux advisor service data export Users of the advisor service can export a report (in either JSON or CSV format) that shows the recommendations affecting each of your registered systems. Exported reports include the following information: Host name Inventory UUID for the host RHEL version Date and time of the last data upload from this host to Insights for Red Hat Enterprise Linux Title of the recommendation impacting the host Link to the solution for this recommendation Total risk posed by this recommendation (from 1 to 4; 1 means low risk, 4 means high risk) Likelihood of this recommendation being active on your registered systems (from 1 to 4 = 1 means unlikely; 4 means highly probable) Date this recommendation was published Link to the scan results for this host 2.1. Exporting reports using the advisor service To export a report using the advisor service, complete the following steps: Navigate to the Operations > Advisor > Recommendations page and log in if necessary. Apply filters as needed to refine results. Click the Download icon located to the right of the Search box in the toolbar. Select either Export to CSV or Export to JSON depending on your preference. In the dialog box, select Open with and specify an application with which to open the file, or click Save File and click OK . 2.2. Exporting advisor service data using the API Use the advisor service API to export data in one of the following ways: For CSV file type Request URL: https://console.redhat.com/api/advisor/v1/export/hits.csv Curl For JSON file type Request URL: https://console.redhat.com/api/advisor/v1/export/hits.json Curl API documentation for all of the Insights for Red Hat Enterprise Linux services is available at Red Hat Insights for Red Hat Enterprise Linux API .

Commands:
curl -X GET "https://console.redhat.com/api/insights/v1/export/hits.csv" -H "accept: */*"
curl -X GET "https://console.redhat.com/api/insights/v1/export/hits.json" -H "accept: application/json"
Appendix A. Component Versions This appendix is a list of components and their versions in the Red Hat Enterprise Linux 7.3 release. Table A.1. Component Versions Component Version Kernel 3.10.0-514 QLogic qla2xxx driver 8.07.00.33.07.3-k1 QLogic qla4xxx driver 5.04.00.00.07.02-k0 Emulex lpfc driver 0:11.1.0.2 iSCSI initiator utils iscsi-initiator-utils-6.2.0.873-35 DM-Multipath device-mapper-multipath-0.4.9-99 LVM lvm2-2.02.166-1

Commands:
Chapter 152. KafkaMirrorMaker2MirrorSpec schema reference Used in: KafkaMirrorMaker2Spec Property Property type Description sourceCluster string The alias of the source cluster used by the Kafka MirrorMaker 2 connectors. The alias must match a cluster in the list at spec.clusters . targetCluster string The alias of the target cluster used by the Kafka MirrorMaker 2 connectors. The alias must match a cluster in the list at spec.clusters . sourceConnector KafkaMirrorMaker2ConnectorSpec The specification of the Kafka MirrorMaker 2 source connector. heartbeatConnector KafkaMirrorMaker2ConnectorSpec The specification of the Kafka MirrorMaker 2 heartbeat connector. checkpointConnector KafkaMirrorMaker2ConnectorSpec The specification of the Kafka MirrorMaker 2 checkpoint connector. topicsPattern string A regular expression matching the topics to be mirrored, for example, "topic1|topic2|topic3". Comma-separated lists are also supported. topicsBlacklistPattern string The topicsBlacklistPattern property has been deprecated, and should now be configured using .spec.mirrors.topicsExcludePattern . A regular expression matching the topics to exclude from mirroring. Comma-separated lists are also supported. topicsExcludePattern string A regular expression matching the topics to exclude from mirroring. Comma-separated lists are also supported. groupsPattern string A regular expression matching the consumer groups to be mirrored. Comma-separated lists are also supported. groupsBlacklistPattern string The groupsBlacklistPattern property has been deprecated, and should now be configured using .spec.mirrors.groupsExcludePattern . A regular expression matching the consumer groups to exclude from mirroring. Comma-separated lists are also supported. groupsExcludePattern string A regular expression matching the consumer groups to exclude from mirroring. Comma-separated lists are also supported.

Commands:
Getting Started Guide Red Hat JBoss Data Grid 6.6 For use with Red Hat JBoss Data Grid 6.6.1 Misha Husnain Ali Red Hat Engineering Content Services mhusnain@redhat.com Gemma Sheldon Red Hat Engineering Content Services gsheldon@redhat.com Rakesh Ghatvisave Red Hat Engineering Content Services rghatvis@redhat.com Christian Huffman Red Hat Engineering Content Services chuffman@redhat.com

Commands: