mtpti5iD/redhat-docs_dataset huggingface dataset:
Appendix C. Using AMQ Broker with the examples The AMQ Ruby examples require a running message broker with a queue named examples . Use the procedures below to install and start the broker and define the queue. C.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . C.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... C.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named examples . USD <broker-instance-dir> /bin/artemis queue create --name examples --address examples --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. C.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-08-24 14:29:17 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name examples --address examples --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
5.2. Multipath Queries with multipath Command You can use the -l and -ll options of the multipath command to display the current multipath configuration. The -l option displays multipath topology gathered from information in sysfs and the device mapper. The -ll option displays the information the -l displays in addition to all other available components of the system. When displaying the multipath configuration, there are three verbosity levels you can specify with the -v option of the multipath command. Specifying -v0 yields no output. Specifying -v1 outputs the created or updated multipath names only, which you can then feed to other tools such as kpartx . Specifying -v2 prints all detected paths, multipaths, and device maps. The following example shows the output of a multipath -l command.

Commands:
multipath -l mpath1 (3600d0230003228bc000339414edb8101) [size=10 GB][features="0"][hwhandler="0"] \_ round-robin 0 [prio=1][active] \_ 2:0:0:6 sdb 8:16 [active][ready] \_ round-robin 0 [prio=1][enabled] \_ 3:0:0:6 sdc 8:64 [active][ready]
5.258. python-memcached 5.258.1. RHBA-2012:0889 - python-memcached bug fix update Updated python-memcached packages that fix one bug are now available for Red Hat Enterprise Linux 6. The python-memcached packages provide a python interface to the memcached memory cache daemon. Bug Fix BZ# 789494 Prior to this update, python-memcached failed to get statistics for the memcached server and the "get_stats()" function returned a warning message. This update modifies the "get_stats()" method so that python-memcached can now get the statistics as expected. All users of python-memcached are advised to upgrade to these updated packages, which fix this bug.

Commands:
24.2.2. Using the System Monitor Tool The Resources tab of the System Monitor tool allows you to view the amount of free and used memory on the system. To start the System Monitor tool, either select Applications System Tools System Monitor from the panel, or type gnome-system-monitor at a shell prompt. Then click the Resources tab to view the system's memory usage. Figure 24.2. System Monitor - Resources In the Memory and Swap History section, the System Monitor tool displays a graphical representation of the memory and swap usage history, as well as the total amount of the physical memory ( Memory ) and swap space ( Swap ) and how much of it is in use.

Commands:
4.352. xorg-x11-drv-ati 4.352.1. RHBA-2011:1553 - xorg-x11-drv-ati bug fix and enhancement update Updated xorg-x11-drv-ati packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-ati packages provide a driver for ATI graphics cards for the X.Org implementation of the X Window System. The xorg-x11-drv-ati packages have been upgraded to upstream version 6.14.2, which provides a number of bug fixes and enhancements over the version. (BZ# 713766 , BZ# 634238 ) Bug Fixes BZ# 588918 The ATI ES1000 graphics devices had limited Video RAM (VRAM) and were restricted to an 8-bit color depth for the text console. As a consequence, the graphical boot screen was unavailable on systems using these graphics devices. Such systems could become unresponsive afterward and had to be rebooted. With this update, the source code is modified and the installation with graphical user interface (GUI) can be successfully completed. BZ# 615550 Due to the driver being too verbose, error messages about failed write attempts could incorrectly appear when booting the system on i386 architectures. The messages could be safely ignored and the system eventually booted successfully. To avoid user confusion, these messages are removed with this update. Enhancements BZ# 675297 This update adds support for the AMD FirePro M5950, AMD FirePro M8900, AMD FirePro V5900, and AMD FirePro V7900 graphics cards. BZ# 713622 This update provides the firmware files which are required by AMD Radeon HD 6000-series and AMD's Accelerated Processing Unit (APU) platforms. All users of xorg-x11-drv-ati are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

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-06-04 11:11:03 UTC

Commands:
Planning your deployment Red Hat OpenStack Services on OpenShift 18.0 Planning a Red Hat OpenStack Services on OpenShift environment on a Red Hat OpenShift Container Platform cluster OpenStack Documentation Team rhos-docs@redhat.com

Commands:
oc describe crd openstackcontrolplane Name: openstackcontrolplane.openstack.org Namespace: Labels: operators.coreos.com/operator.openstack= Annotations: cert-manager.io/inject-ca-from: USD(CERTIFICATE_NAMESPACE)/USD(CERTIFICATE_NAME) controller-gen.kubebuilder.io/version: v0.3.0 API Version: apiextensions.k8s.io/v1 Kind: CustomResourceDefinition
oc explain openstackcontrolplane.spec KIND: OpenStackControlPlane VERSION: core.openstack.org/v1beta1 RESOURCE: spec <Object> DESCRIPTION: <empty> FIELDS: ceilometer <Object> cinder <Object> dns <Object> extraMounts <[]Object>
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane
oc describe openstackcontrolplane/compute
oc get nodes
NAME STATUS ROLES AGE VERSION master1 Ready control-plane,master 7d1h v1.28.6+6216ea1 master2 Ready control-plane,master 7d1h v1.28.6+6216ea1 master3 Ready control-plane,master 7d1h v1.28.6+6216ea1 worker1 Ready worker 7d1h v1.28.6+6216ea1 worker2 Ready worker 7d1h v1.28.6+6216ea1 worker3 Ready worker
oc debug node/worker2
Temporary namespace openshift-debug-rq2m8 is created for debugging node Starting pod/worker2-debug-5shqt To use host binaries, run `chroot /host` Pod IP: 192.168.50.112 If you don't see a command prompt, try pressing enter. sh-5.1#
sh-5.1# cat /proc/sys/crypto/fips_enabled
1
apiVersion: core.openstack.org/v1beta1 kind: OpenStackControlPlane metadata: name: openstack spec: cinder: template: cinderVolumes: iscsi: networkAttachments: - storage - storageMgmt
default: storage: external: true extraMounts: - extraVol: - extraVolType: NFS mounts: - mountPath: /var/lib/glance/os_glance_staging_store name: nfs volumes: - name: nfs nfs: path: <nfs_export_path> server: <nfs_ip_address>
default: replicas: 3 storage: storageRequest: 10G
5.83. ghostscript 5.83.1. RHSA-2012:1256 - Moderate: ghostscript security update Updated ghostscript packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Ghostscript is a set of software that provides a PostScript interpreter, a set of C procedures (the Ghostscript library, which implements the graphics capabilities in the PostScript language) and an interpreter for Portable Document Format (PDF) files. Security Fix CVE-2012-4405 An integer overflow flaw, leading to a heap-based buffer overflow, was found in Ghostscript's International Color Consortium Format library (icclib). An attacker could create a specially-crafted PostScript or PDF file with embedded images that would cause Ghostscript to crash or, potentially, execute arbitrary code with the privileges of the user running Ghostscript. Red Hat would like to thank Marc Schonefeld for reporting this issue. Users of Ghostscript are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. 5.83.2. RHBA-2012:0938 - ghostscript bug fix update Updated ghostscript packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The Ghostscript suite contains utilities for rendering PostScript and PDF documents. Ghostscript translates PostScript code to common, bitmap formats so that the code can be displayed or printed. Bug Fixes BZ# 643105 Prior to this update, the gdevcups driver, which produces CUPS Raster output, handled memory allocations incorrectly. This could cause the ghostscript program to terminate unexpectedly in some situations. This update applies backported fixes for handling the memory allocations to this version of ghostscript and the crash no longer occurs. BZ# 695766 Prior to this update, certain input files containing CID Type2 fonts were rendered with incorrect character spacing. This update modifies the code so that all input files with CID Type2 fonts are rendered correctly. BZ# 697488 Prior to this update, the page orientation was incorrect when pages in the landscape orientation were converted to the PXL raster format. This update matches landscape-page sizes as well as portrait-page sizes, and sets the orientation parameter correctly when a match is found. All users of ghostscript are advised to upgrade to these updated packages, which fix these bugs.

Commands:
function::ansi_set_color3 Name function::ansi_set_color3 - Set the ansi Select Graphic Rendition mode. Synopsis Arguments fg Foreground color to set. bg Background color to set. attr Color attribute to set. General Syntax ansi_set_color3(fg:long, bg:long, attr:long) Description Sends ansi code for Select Graphic Rendition mode for the given forground color, Black (30), Blue (34), Green (32), Cyan (36), Red (31), Purple (35), Brown (33), Light Gray (37), the given background color, Black (40), Red (41), Green (42), Yellow (43), Blue (44), Magenta (45), Cyan (46), White (47) and the color attribute All attributes off (0), Intensity Bold (1), Underline Single (4), Blink Slow (5), Blink Rapid (6), Image Negative (7).

Commands:
function ansi_set_color3(fg:long,bg:long,attr:long)
Chapter 11. Uninstalling SSSD Containers This chapter describes how you can uninstall a System Security Services Daemon (SSSD) container. 11.1. Uninstalling an SSSD Container Enrolled in an Identity Management Domain This procedure describes how to uninstall the System Security Services Daemon (SSSD) container from an Atomic Host system and unenroll the Atomic Host system from the Identity Management domain. Procedure Use the atomic uninstall command, and include the image name: Remove the Atomic Host system's host entry on an Identity Management server. For example, from the command line: To prevent the sssd service on the Atomic Host from attempting to start the container that is now unconfigured, remove the systemd unit file for the service and reload the systemd process: 11.2. Uninstalling an SSSD Container Joined to an Active Directory Domain This procedure describes how to uninstall the System Security Services Daemon (SSSD) container from an Atomic Host system and unenroll the Atomic Host system from the Active Directory domain. Procedure Use the atomic uninstall command, include the image name, and specify the realm that you want to leave. If you are using the default Administrator user account for the operation: If you are using another user account, specify it with the --user option:

Commands:
atomic uninstall rhel7/sssd [... output truncated ...] Unenrolling client from IPA server [... output truncated ...] Client uninstall complete [... output truncated ...]
ipa host-del <atomic.example.com>
rm /etc/systemd/system/sssd.service systemctl daemon-reload
atomic uninstall rhel7/sssd realm leave <ad.example.com>
atomic uninstall rhel7/sssd realm leave --user <user_name> <ad.example.com>
4.178. mingetty 4.178.1. RHBA-2011:1177 - mingetty bug fix update An updated mingetty package that fixes three bugs is now available for Red Hat Enterprise Linux 6. The mingetty program is a lightweight, minimalist getty program for use only on virtual consoles. The mingetty program is not suitable for serial lines (the mgetty program should be used in that case). Bug Fixes BZ# 640933 Prior to this update, when mingetty was invoked with the "--chroot" option, mingetty did not change the working directory to the new root. Furthermore, mingetty continued even if setting constraints specified by the "--chroot", "--chdir", and "--nice" options failed. As a result, a user was able to escape from the changed root by using relative paths. Also, it was possible for a user to obtain a process with a different process priority. These problems have been resolved in this update so that the working directory is now changed to the new root directory, all failures are now recognized, and mingetty terminates with an error reported to the system log. BZ# 640940 Prior to this update, when invoking mingetty with a TTY name (a non-option position argument) that was longer than 39 ASCII characters, a buffer overflow occurred and the mingetty stack content could have become corrupted. This bug has been fixed in this update so that only the first 39 bytes (34 bytes in case of a relative path) from the TTY name are now copied. BZ# 651955 Prior to this update, when using a login name longer than 39 characters, such login name was silently refused and mingetty terminated. With this update, login names with the length up to the current runtime limit are now accepted; login names that are above the limit are refused, an error is reported to the system log, and mingetty terminates. All users of mingetty should upgrade to this updated package, which fixes these bugs.

Commands:
8.2. Checking the Status of PKI ACME Responder To check the status of the ACME responder, run the following command: If the services are disabled, the command will show the following result: Note The actual output depends on what is configured in the metadata.conf configuration file.

Commands:
pki acme-info Status: Available Terms of Service: https://www.example.com/acme/tos.pdf Website: https://www.example.com CAA Identities: example.com External Account Required:false
pki acme-info Status: Unavailable
23.2.2. Installing PTP The kernel in Red Hat Enterprise Linux 6 now includes support for PTP . User space support is provided by the tools in the linuxptp package. To install linuxptp , issue the following command as root : This will install ptp4l and phc2sys . Do not run more than one service to set the system clock's time at the same time. If you intend to serve PTP time using NTP , see Section 23.7, "Serving PTP Time With NTP" .

Commands:
~]# yum install linuxptp
8.7. Practical Examples This section demonstrates practical usage of certain security content provided for Red Hat products. 8.7.1. Auditing Security Vulnerabilities of Red Hat Products Red Hat continuously provides OVAL definitions for their products. These definitions allow for fully automated audit of vulnerabilities in the installed software. To find out more information about this project, see http://www.redhat.com/security/data/metrics/ . To download these definitions, run the following command: The users of Red Hat Satellite 5 may find useful the XCCDF part of the patch definitions. To download these definitions, run the following command: To audit security vulnerabilities for the software installed on the system, run the following command: The oscap utility maps Red Hat Security Advisories to CVE identifiers that are linked to the National Vulnerability Database and reports which security advisories are not applied. Note Note that these OVAL definitions are designed to only cover software and updates released by Red Hat. You need to provide additional definitions in order to detect the patch status of third-party software.

Commands:
~]USD wget http://www.redhat.com/security/data/oval/com.redhat.rhsa-all.xml
~]USD wget http://www.redhat.com/security/data/metrics/com.redhat.rhsa-all.xccdf.xml
~]USD oscap oval eval --results rhsa-results-oval.xml --report oval-report.html com.redhat.rhsa-all.xml
C.3. Controlling Activation with Tags You can specify in the configuration file that only certain logical volumes should be activated on that host. For example, the following entry acts as a filter for activation requests (such as vgchange -ay ) and only activates vg1/lvol0 and any logical volumes or volume groups with the database tag in the metadata on that host. There is a special match "@*" that causes a match only if any metadata tag matches any host tag on that machine. As another example, consider a situation where every machine in the cluster has the following entry in the configuration file: If you want to activate vg1/lvol2 only on host db2 , do the following: Run lvchange --addtag @db2 vg1/lvol2 from any host in the cluster. Run lvchange -ay vg1/lvol2 . This solution involves storing hostnames inside the volume group metadata.

Commands:
activation { volume_list = ["vg1/lvol0", "@database" ] }
tags { hosttags = 1 }
Preface Open Java Development Kit (OpenJDK) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of Red Hat build of OpenJDK is available in three versions: Red Hat build of OpenJDK 8u, Red Hat build of OpenJDK 11u, and Red Hat build of OpenJDK 17u. Packages for the Red Hat build of Red Hat build of OpenJDK are made available on Red Hat Enterprise Linux and Microsoft Windows and shipped as a JDK and JRE in the Red Hat Ecosystem Catalog.

Commands:
11.2. XML Representation of a Network Resource Example 11.1. An XML representation of a network resource

Commands:
<network href="/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"> <name>ovirtmgmt</name> <description>Management Network</description> <link href="/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000/permissions" rel="permissions"/> <link href="/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000/vnicprofiles" rel="vnicprofiles"/> <link href="/ovirt-engine/api/networks/00000000-0000-0000-0000-000000000000/labels" rel="labels"/> <data_center href="/ovirt-engine/api/datacenters/00000000-0000-0000-0000-000000000000" id="00000000-0000-0000-0000-000000000000"/> <stp>false</stp> <mtu>0</mtu> <usages> <usage>vm</usage> </usages> </network>
Chapter 3. Installing Connectivity Link on OpenShift from the command line Note You must perform these steps on each OpenShift cluster that you want to use Connectivity Link on. Prerequisites See Chapter 1, Connectivity Link prerequisites and permissions . Procedure Create the namespace where you want to install the Operator as follows, for example, kuadrant-system : To install the Connectivity Link Operator, enter the following command: Wait for the Connectivity Link Operators to be installed as follows: After some time, this command will return Complete when ready. To create your Connectivity Link deployment, enter the following command: Wait for Kuadrant to be ready as follows: This command will return Complete when ready. Additional resources OpenShift Operators documentation .

Commands:
create ns kuadrant-system
apply -f - <<EOF apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: rhcl-operator namespace: kuadrant-system spec: channel: stable installPlanApproval: Automatic name: rhcl-operator source: redhat-operators sourceNamespace: openshift-marketplace --- kind: OperatorGroup apiVersion: operators.coreos.com/v1 metadata: name: kuadrant namespace: kuadrant-system spec: upgradeStrategy: Default EOF
get installplan -n kuadrant-system -o=jsonpath='{.items[0].status.phase}'
apply -f - <<EOF apiVersion: kuadrant.io/v1beta1 kind: Kuadrant metadata: name: kuadrant namespace: kuadrant-system EOF
wait kuadrant/kuadrant --for="condition=Ready=true" -n kuadrant-system --timeout=300s