mtpti5iD/redhat-docs_dataset huggingface dataset:
3.7.3. Valgrind Valgrind provides a number of detection and profiling tools to help improve the performance and correctness of your applications. These tools can detect memory and thread-related errors as well as heap, stack and array overruns, allowing you to easily locate and correct errors in your application code. They can also profile the cache, the heap, and branch-prediction to identify factors that may increase application speed and minimize application memory use. Valgrind analyzes your application by running it on a synthetic CPU and instrumenting the existing application code as it is executed. It then prints "commentary" clearly identifying each process involved in application execution to a user-specified file descriptor, file, or network socket. The level of instrumentation varies depending on the Valgrind tool in use, and its settings, but it is important to note that executing the instrumented code can take 4-50 times longer than normal execution. Valgrind can be used on your application as-is, without recompiling. However, because Valgrind uses debugging information to pinpoint issues in your code, if your application and support libraries were not compiled with debugging information enabled, recompiling to include this information is highly recommended. As of Red Hat Enterprise Linux 6.4, Valgrind integrates with gdb (GNU Project Debugger) to improve debugging efficiency. More information about Valgrind is available from the Developer Guide , available from http://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/ , or by using the man valgrind command when the valgrind package is installed. Accompanying documentation can also be found in: /usr/share/doc/valgrind-<version>/valgrind_manual.pdf /usr/share/doc/valgrind-<version>/html/index.html For information about how Valgrind can be used to profile system memory, refer to Section 5.3, "Using Valgrind to Profile Memory Usage" .

Commands:
7.145. openscap 7.145.1. RHBA-2015:1317 - openscap bug fix and enhancement update Updated openscap packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. OpenSCAP is an open source project, which enables integration of the Security Content Automation Protocol (SCAP) line of standards. SCAP is a line of standards managed by the National Institute of Standards and Technology (NIST). It was created to provide a standardized approach to maintaining the security of enterprise systems, such as automatically verifying presence of patches, checking system security configuration settings, and examining systems for signs of compromise. Note The openscap packages have been upgraded to upstream version 1.0.10, which provides a number of bug fixes and enhancements over the version. Updated version is fully API/ABI compatible with 1.0.x version which has been certified by the National Institute of Standards and Technology (NIST). (BZ# 1152599 ) Bug Fixes BZ# 1036741 Previously, the has_extended_acl feature was missing in the scripts that build OpenSCAP, which caused the OpenSCAP auditing tool to be unable to assess extended file system properties. This update fixes the build process of OpenSCAP to include has_extended_acl, and OpenSCAP is now again able to assess extended file system properties as intended. BZ# 1092013 When the Extensible Configuration Checklist Description Format (XCCDF) input content included an instruction to use a certain XCCDF variable with an undefined variable value, the OpenSCAP scanner could crash. With this update, the NULL pointer causing this bug is handled correctly when binding the XCCDF value to the OVAL variable, and the security scan now proceeds smoothly. BZ# 1192428 The OVAL standard requires that the var_check content XML attribute be included within any XML elements that have the var_ref attribute, which the OpenSCAP scanner did not always observe. As a consequence, the schematron validation of OVAL results returned a warning message to the user. The OVAL module has been fixed to export var_check explicitly whenever exporting var_ref, and the schematron validation now passes as expected. Enhancement BZ# 1115114 To keep the installed package set to the minimum, the number of package dependencies of the OpenSCAP auditing tool has been reduced. With this update, the oscap tool is shipped within the newly created openscap-scanner package and the openscap-utils package remains to include miscellaneous tools. Users are advised to remove openscap-utils, if they no longer need other utilities except for the scanner. Users of openscap are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 3. Adding multiple systems to a group In the Insights Inventory application, you can add several systems to a group to manage them more easily. For example, you can easily mitigate vulnerabilities and update systems that are alike. Prerequisites You have a Red Hat Hybrid Cloud Console account. You have registered the systems you plan to group with the Insights Inventory application. Procedure Access Red Hat Hybrid Cloud Console platform and log in. From the console dashboard, navigate to Red Hat Insights > RHEL > Inventory > Systems . On the System page: Search for the systems you want to add from the Inventory and select the ones you want to add to your group. Click the options icon (...) and click Add to group . The Add to group window open: Add to an existing group: Select an existing group and click Add . Create a new group: Click the Create group button. Click Add . Verification If adding the multiple systems to the group was successful, you can see the systems added to the group on the page for your group.

Commands:
Preface Providing feedback on Red Hat build of Apache Camel documentation To report an error or to improve our documentation, log in to your Red Hat Jira account and submit an issue. If you do not have a Red Hat Jira account, then you will be prompted to create an account. Procedure Click the following link to create ticket Enter a brief description of the issue in the Summary. Provide a detailed description of the issue or enhancement in the Description. Include a URL to where the issue occurs in the documentation. Clicking Submit creates and routes the issue to the appropriate documentation team.

Commands:
B.72. postfix B.72.1. RHSA-2011:0423 - Moderate: postfix security update Updated postfix packages that fix one security issue are now available for Red Hat Enterprise Linux 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. Postfix is a Mail Transport Agent (MTA), supporting LDAP, SMTP AUTH (SASL), and TLS. CVE-2011-0411 It was discovered that Postfix did not flush the received SMTP commands buffer after switching to TLS encryption for an SMTP session. A man-in-the-middle attacker could use this flaw to inject SMTP commands into a victim's session during the plain text phase. This would lead to those commands being processed by Postfix after TLS encryption is enabled, possibly allowing the attacker to steal the victim's mail or authentication credentials. Red Hat would like to thank the CERT/CC for reporting CVE-2011-0411 . The CERT/CC acknowledges Wietse Venema as the original reporter. Users of Postfix are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue. After installing this update, the postfix service will be restarted automatically.

Commands:
Chapter 9. Creating a passthrough certification A passthrough certification is used when the same image is provided as a copy of an existing certified cloud certification and is listed under a different image name. You can create a passthrough regular or gold RHEL image from an originally certified regular or gold RHEL image. Prerequisites Ensure that the existing image is certified or published in the ecosystem catalog. Procedure Open Red Hat Partner Certification Tool in a browser. Or, In your test server, open the Red Hat Partner Certification Tool in a browser by using http://<machine-IP> . Navigate to the existing certified image certification. Click Related certification > New Certification . The New Passthrough Product page displays. Enter required details in the fields: Product name , Description , Product URL , Supported Regions , Supported Languages , 3rd Party Certifications , and then click Create . Click the Details tab and update the relevant Subscription Model .

Commands:
Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To provide feedback, you can highlight the text in a document and add comments. Follow the steps in the procedure to learn about submitting feedback on Red Hat documentation. Prerequisites Log in to the Red Hat Customer Portal. In the Red Hat Customer Portal, view the document in HTML format. Procedure Click the Feedback button to see existing reader comments. Note The feedback feature is enabled only in the HTML format. Highlight the section of the document where you want to provide feedback. In the prompt menu that opens near the text you selected, click Add Feedback . A text box opens in the feedback section on the right side of the page. Enter your feedback in the text box and click Submit . You have created a documentation issue. To view the issue, click the issue tracker link in the feedback view.

Commands:
Chapter 6. Using and Configuring the Token Management System: TPS and TKS This chapter provides procedures for using hardware security modules, also called HSMs or tokens , to generate and store Certificate System instance certificates and keys. This chapter only contains administration procedures. For general information on the concepts behind the Token Management System, see the Red Hat Certificate System Planning, Installation and Deployment Guide . 6.1. TPS Profiles Note See the TPS Profiles section of the Red Hat Certificate System Planning, Installation and Deployment Guide for general information. Unlike CA enrollment profiles, which are defined and stored in individual files or in LDAP, TPS profiles (also known as token types) are defined in the TPS configuration file, CS.cfg . TPS profile (token type) configuration parameters are set in the following format: In the above, <explicit op> and <implicit op> are one of the explicit and implicit operations discussed in the TPS Operations section below, and <key type> is the name given for each certificate type. An example configuration parameter may look like the following example:

Commands:
op. <explicit op> . <profile id> . <implicit op> . <key type> .*
op.enroll.userKey.keyGen.encryption.*
F.7. About Two Phase Commit (2PC) A Two Phase Commit protocol (2PC) is a consensus protocol used to atomically commit or roll back distributed transactions. It is successful when faced with cases of temporary system failures, including network node and communication failures, and is therefore widely utilized. 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
Chapter 5. Pools, placement groups, and CRUSH configuration As a storage administrator, you can choose to use the Red Hat Ceph Storage default options for pools, placement groups, and the CRUSH algorithm or customize them for the intended workload. 5.1. Prerequisites Installation of the Red Hat Ceph Storage software. 5.2. Pools placement groups and CRUSH When you create pools and set the number of placement groups for the pool, Ceph uses default values when you do not specifically override the defaults. Important Red Hat recommends overriding some of the defaults. Specifically, set a pool's replica size and override the default number of placement groups. You can set these values when running pool commands. You can also override the defaults by adding new ones in the [global] section of the Ceph configuration file. Example 5.3. Additional Resources See all the Red Hat Ceph Storage pool, placement group, and CRUSH configuration options in Appendix E for specific option descriptions and usage.

Commands:
By default, Ceph makes 3 replicas of objects. If you want to set 4 copies of an object as the default value--a primary copy and three replica copies--reset the default values as shown in 'osd pool default size'. If you want to allow Ceph to write a lesser number of copies in a degraded state, set 'osd pool default min size' to a number less than the 'osd pool default size' value. osd_pool_default_size = 4 # Write an object 4 times. osd_pool_default_min_size = 1 # Allow writing one copy in a degraded state. Ensure you have a realistic number of placement groups. We recommend approximately 100 per OSD. E.g., total number of OSDs multiplied by 100 divided by the number of replicas (i.e., osd pool default size). So for 10 OSDs and osd pool default size = 4, we'd recommend approximately (100 * 10) / 4 = 250. osd_pool_default_pg_num = 250 osd_pool_default_pgp_num = 250
Chapter 138. KafkaBridgeConsumerSpec schema reference Used in: KafkaBridgeSpec Full list of KafkaBridgeConsumerSpec schema properties Configures consumer options for the Kafka Bridge. Example Kafka Bridge consumer configuration apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # ... consumer: enabled: true timeoutSeconds: 60 config: auto.offset.reset: earliest enable.auto.commit: true # ... Use the consumer.config properties to configure Kafka options for the consumer as keys. The values can be one of the following JSON types: String Number Boolean Exceptions You can specify and configure the options listed in the Apache Kafka configuration documentation for consumers . However, Streams for Apache Kafka takes care of configuring and managing options related to the following, which cannot be changed: Kafka cluster bootstrap address Security (encryption, authentication, and authorization) Consumer group identifier Properties with the following prefixes cannot be set: bootstrap.servers group.id sasl. security. ssl. If the config property contains an option that cannot be changed, it is disregarded, and a warning message is logged to the Cluster Operator log file. All other supported options are forwarded to Kafka Bridge, including the following exceptions to the options configured by Streams for Apache Kafka: Any ssl configuration for supported TLS versions and cipher suites Important The Cluster Operator does not validate keys or values in the config object. If an invalid configuration is provided, the Kafka Bridge deployment might not start or might become unstable. In this case, fix the configuration so that the Cluster Operator can roll out the new configuration to all Kafka Bridge nodes. 138.1. KafkaBridgeConsumerSpec schema properties Property Property type Description enabled boolean Whether the HTTP consumer should be enabled or disabled. The default is enabled ( true ). timeoutSeconds integer The timeout in seconds for deleting inactive consumers, default is -1 (disabled). config map The Kafka consumer configuration used for consumer instances created by the bridge. Properties with the following prefixes cannot be set: ssl., bootstrap.servers, group.id, sasl., security. (with the exception of: ssl.endpoint.identification.algorithm, ssl.cipher.suites, ssl.protocol, ssl.enabled.protocols).

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: KafkaBridge metadata: name: my-bridge spec: # consumer: enabled: true timeoutSeconds: 60 config: auto.offset.reset: earliest enable.auto.commit: true #
7.92. jpackage-utils 7.92.1. RHEA-2015:1248 - jpackage-utils enhancement update An updated jpackage-utils package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The jpackage-utils package installs directory structures, RPM macros, configuration files, and scripts that provide support for jpackage.org Java packaging. It is required by all packages that follow the JPackage conventions. Enhancement BZ# 1149605 The support for OpenJDK8 has been added to the JPackage utilities, which enables Java system applications to be used with OpenJDK8. Users of jpackage-utils are advised to upgrade to this updated package, which adds this enhancement.

Commands:
Chapter 2. The GRUB Boot Loader When a computer with Red Hat Enterprise Linux is turned on, the operating system is loaded into memory by a special program called a boot loader . A boot loader usually exists on the system's primary hard drive (or other media device) and has the sole responsibility of loading the Linux kernel with its required files or (in some cases) other operating systems into memory. 2.1. Boot Loaders and System Architecture Each architecture capable of running Red Hat Enterprise Linux uses a different boot loader. The following table lists the boot loaders available for each architecture: Table 2.1. Boot Loaders by Architecture Architecture Boot Loaders AMD (R) AMD64 GRUB IBM (R) eServer TM iSeries TM OS/400 (R) IBM (R) eServer TM pSeries TM YABOOT IBM (R) S/390 (R) z/IPL IBM (R) eServer TM zSeries (R) z/IPL Intel (R) Itanium TM ELILO x86 GRUB This chapter discusses commands and configuration options for the GRUB boot loader included with Red Hat Enterprise Linux for the x86 architecture.

Commands:
17.7. Changing the Trust Settings of a CA Certificate Certificate System subsystems use the CA certificates in their certificate databases to validate certificates received during an SSL-enabled communication. It can be necessary to change the trust settings on a CA stored in the certificate database, temporarily or permanently. For example, if there is a problem with access or compromised certificates, marking the CA certificate as untrusted prevents entities with certificates signed by that CA from authenticating to the Certificate System. When the problem is resolved, the CA can be marked as trusted again. To untrust a CA permanently, consider removing its certificate from the trust database. For instructions, see Section 17.6.3, "Deleting Certificates from the Database" . 17.7.1. Changing Trust Settings through the Console Note pkiconsole is being deprecated. To change the trust setting of a CA certificate, do the following: Open the subsystem console. In the Configuration tab, System Keys and Certificates from the left navigation tree. Select the CA certificates tab. Select the CA certificate to modify, and click Edit . A prompt opens which reads The Certificate chain is (un)trusted, are you sure you want to (un)trust it? Clicking yes changes the trust setting of the certificate chain; pressing no preserves the original trust relationship. 17.7.2. Changing Trust Settings Using certutil To change the trust setting of a certificate using certutil , do the following: Open the instance's certificate databases directory. List the certificates in the database by running the certutil with the -L option. For example: Change the trust settings for the certificate by running the certutil with the -M option. For example: List the certificates again to confirm that the certificate trust was changed. For information about using the certutil command, see http://www.mozilla.org/projects/security/pki/nss/tools/certutil.html .

Commands:
pkiconsole https://server.example.com: secure_port / subsystem_type
cd /var/lib/pki/ instance_name /alias
certutil -L -d . Certificate Authority - Example Domain CT,c, subsystemCert cert- instance_name u,u,u Server-Cert cert- instance_name u,u,u
certutil -M -n cert_nickname -t trust -d .
certutil -M -n "Certificate Authority - Example Domain" -t TCu,TCu,TCu -d .
certutil -L -d . Certificate Authority - Example Domain CTu,CTu,CTu subsystemCert cert- instance_name u,u,u Server-Cert cert- instance_name u,u,u
Preface Welcome to the Red Hat Trusted Profile Analyzer (RHTPA) Deployment Guide! This guide helps you with deploying the Red Hat Trusted Profile Analyzer (RHTPA) software stack on Red Hat OpenShift Container Platform or on Red Hat Enterprise Linux. For new RHTPA deployments, start by choosing your target installation platform . Important If you are upgrading RHTPA to version 1.2, start with Chapter 1, Migrating your data before an upgrade .

Commands:
Appendix C. Using AMQ Broker with the examples The AMQ C++ 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 2020-10-08 11:23:41 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