mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. Getting started This chapter guides you through the steps to set up your environment and run a simple messaging program. 3.1. Prerequisites You must complete the installation procedure for your environment. You must have an AMQP 1.0 message broker listening for connections on interface localhost and port 5672 . It must have anonymous access enabled. For more information, see Starting the broker . You must have a queue named hello-world-example . For more information, see Creating a queue . Alternatively, you can specify above information using following environment variables: HOST , PORT , ADDRESS 3.2. Running HelloWorld on Red Hat Enterprise Linux The Hello World example creates a connection to the broker, sends a message containing a greeting to the hello-world-example queue, and receives it back. On success, it prints the received message to the console. Use maven to build the module, and additionally copy the dependencies alongside their output: cd <source-dir> mvn clean package dependency:copy-dependencies -DincludeScope=runtime -DskipTests Run the examples: USD java -cp "target/classes/:target/dependency/*" org.apache.qpid.protonj2.client.examples.HelloWorld 3.3. Running Hello World on Microsoft Windows The Hello World example creates a connection to the broker, sends a message containing a greeting to the hello-world-example queue, and receives it back. On success, it prints the received message to the console. Use maven to build the module, and additionally copy the dependencies alongside their output: cd <source-dir> mvn clean package dependency:copy-dependencies -DincludeScope=runtime -DskipTests Run the examples: USD java -cp "target\classes\;target\dependency\*" org.apache.qpid.protonj2.client.examples.HelloWorld

Commands:
cd <source-dir> mvn clean package dependency:copy-dependencies -DincludeScope=runtime -DskipTests
java -cp "target/classes/:target/dependency/*" org.apache.qpid.protonj2.client.examples.HelloWorld
cd <source-dir> mvn clean package dependency:copy-dependencies -DincludeScope=runtime -DskipTests
java -cp "target\classes\;target\dependency\*" org.apache.qpid.protonj2.client.examples.HelloWorld
Preface Welcome to the Red Hat JBoss Core Services version 2.4.57 Service Pack 2 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:
32.3.5. Displaying Virtual Memory Information To display basic virtual memory information, type the vm command at the interactive prompt. You can use vm pid to display information on the selected process. Example 32.6. Displaying virtual memory information of the current context Type help vm for more information on the command usage.

Commands:
crash> vm PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash" MM PGD RSS TOTAL_VM f19b5900 ef9c6000 1648k 5084k VMA START END FLAGS FILE f1bb0310 242000 260000 8000875 /lib/ld-2.12.so f26af0b8 260000 261000 8100871 /lib/ld-2.12.so efbc275c 261000 262000 8100873 /lib/ld-2.12.so efbc2a18 268000 3ed000 8000075 /lib/libc-2.12.so efbc23d8 3ed000 3ee000 8000070 /lib/libc-2.12.so efbc2888 3ee000 3f0000 8100071 /lib/libc-2.12.so efbc2cd4 3f0000 3f1000 8100073 /lib/libc-2.12.so efbc243c 3f1000 3f4000 100073 efbc28ec 3f6000 3f9000 8000075 /lib/libdl-2.12.so efbc2568 3f9000 3fa000 8100071 /lib/libdl-2.12.so efbc2f2c 3fa000 3fb000 8100073 /lib/libdl-2.12.so f26af888 7e6000 7fc000 8000075 /lib/libtinfo.so.5.7 f26aff2c 7fc000 7ff000 8100073 /lib/libtinfo.so.5.7 efbc211c d83000 d8f000 8000075 /lib/libnss_files-2.12.so efbc2504 d8f000 d90000 8100071 /lib/libnss_files-2.12.so efbc2950 d90000 d91000 8100073 /lib/libnss_files-2.12.so f26afe00 edc000 edd000 4040075 f1bb0a18 8047000 8118000 8001875 /bin/bash f1bb01e4 8118000 811d000 8101873 /bin/bash f1bb0c70 811d000 8122000 100073 f26afae0 9fd9000 9ffa000 100073 ... several lines omitted
Chapter 18. Virtual Machine Pools 18.1. Virtual Machine Pool Elements The vmpools collection provides information about the virtual machine pools in a Red Hat Virtualization environment. An API user accesses this information through the rel="vmpools" link obtained from the entry point URI. The following table shows specific elements contained in a virtual machine pool resource representation. Table 18.1. Virtual machine pool elements Element Type Description Properties name string A user-supplied, human readable name for the pool. The name is unique across all pool resources. description string A user-supplied, human readable description of the virtual machine pool. link rel="permissions" relationship A link to the permissions sub-collection for virtual machine pool permissions. size integer The number of virtual machines in the pool. cluster id= GUID A reference to the cluster resource in which virtual machines in this pool run. template id= GUID A reference to the template resource on which virtual machines in this pool are based. prestarted_vms integer The number of prestarted virtual machines in the virtual machine pool. max_user_vms integer The maximum number of virtual machines any one user can take from the virtual machine pool. Important The API as documented in this chapter is experimental and subject to change. It is not covered by the backwards compatibility statement.

Commands:
E.2.17. /proc/mdstat This file contains the current information for multiple-disk, RAID configurations. If the system does not contain such a configuration, then /proc/mdstat looks similar to the following: This file remains in the same state as seen above unless a software RAID or md device is present. In that case, view /proc/mdstat to find the current status of md X RAID devices. The /proc/mdstat file below shows a system with its md0 configured as a RAID 1 device, while it is currently re-syncing the disks:

Commands:
Personalities : read_ahead not set unused devices: <none>
Personalities : [linear] [raid1] read_ahead 1024 sectors md0: active raid1 sda2[1] sdb2[0] 9940 blocks [2/2] [UU] resync=1% finish=12.3min algorithm 2 [3/3] [UUU] unused devices: <none>
Chapter 6. Linter for Dockerfile Linter for Dockerfile is a utility that checks Dockerfiles for errors helping you build valid Dockerfiles. You need a Red Hat login and a valid subscription to access Linter for Dockerfile. Access the Linter for Dockerfile utility here: https://access.redhat.com/labs/linterfordockerfile/ To validate your Dockerfile: Upload a Dockerfile by either providing a URL to the Dockerfile or manually paste in the content of a Dockerfile Select a specific profile (for instance, "Red Hat ISV"). Select Check .

Commands:
1.2. Restore your repository Once you have a complete backup, you can restore it after upgrading your system by using the restoreRepository method provided by the org.modeshape.jcr.api.RepositoryManager interface. Run this code in your Apache JCR session: Warning Do not delete your old data and backups before verifying that your migration is a success.

Commands:
org.modeshape.jcr.api.RepositoryManager repoMgr = java.io.File backupDirectory = Problems problems = repoMgr.restoreRepository(backupDirectory); if ( problems.hasProblems() ) { System.out.println("Problems backing up the repository:"); // Report the problems (we'll just print them out) for ( Problem problem : problems ) { System.out.println(problem); } } else { System.out.println("The restoration was successful"); }
2.4. Define a Connection Extend the org.teiid.resource.spi.BasicConnection class, and provide an implementation based on your access of the Connection object in your translator. If your connection is stateful, override the isAlive() and cleanup() methods with suitable implementations. These methods are called to check if a connection is stale and needs flushing from the connection pool by the application server. public class MyConnection extends BasicConnection { public void doSomeOperation(Command command) { // do some operation with requesting application.. // This is method you use in the Translator, you should know // what need to be done here for your source.. } @Override public boolean isAlive() { return true; } @Override public void cleanUp() { } public void close() throws ResourceException { } }

Commands:
public class MyConnection extends BasicConnection { public void doSomeOperation(Command command) { // do some operation with requesting application.. // This is method you use in the Translator, you should know // what need to be done here for your source.. } @Override public boolean isAlive() { return true; } @Override public void cleanUp() { } public void close() throws ResourceException { } }
7.90. iproute 7.90.1. RHBA-2013:0417 - iproute bug fix and enhancement update Updated iproute packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6. The iproute packages contain networking utilities (ip and rtmon, for example) which are designed to use the advanced networking capabilities of the Linux kernel. Bug Fix BZ# 811219 Invoking the socket stat utility, ss, with the "-ul" arguments did not list open UDP sockets. Consequently, users could not list open or listening UPD sockets. A patch has been applied to the ss utility to list UDP sockets and now the utility correctly reports all open UDP sockets. Enhancement BZ# 821106 The iproute packages were distributed without the libnetlink library for accessing the netlink service. Consequently, it was not possible for users to utilize the libnetlink library features. The libnetlink library is now included in the newly introduced "iproute-devel" subpackage. As a result, users can now utilize libnetlink features. All users of iproute are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
Chapter 6. Known issues This section lists the known issues for AMQ Streams. Issue Number ENTMQST-2386 - Adding or removing JBOD volumes does not work Description and workaround AMQ Streams is not able to add or remove JBOD volumes for newer Kubernetes versions. Improved validation in the StatefulSet Controller means pods can only be deleted and recreated in sequence (pod-0, then pod-1, and so on). Currently, the AMQ Streams rolling update procedure does not trigger pod deletions in sequence. The current workaround is to manually delete all pods in sequence. After the pods are recreated, the StatefulSet Controller will not fail and operates as expected. Issue S2I cannot download source image in environment specified by SHA digest Description and workaround Kafka Connect S2I fails to build new connector plugins on disconnected clusters due to an Openshift imagestreams limitation. If the path to the image registry is changed by specifying an ImageContentSourcePolicy , it is ignored. Instead, imagestreams will try to download from the source repository. The current workaround is to deploy Kafka Connect manually.

Commands:
Chapter 14. Appendix: Getting the source code of container images You can find the source code for bootc image in the Red Hat Ecosystem Catalog . Procedure Access the Red Hat Ecosystem Catalog and search for rhel-bootc . In the Get this image tab, click Get the source and follow the instructions. After you extract the content, the input RPM package list and other content resources are available in the extra_src_dir directory. The .tar files are snapshots of the input git repository, and contain YAML files with the package lists.

Commands:
Chapter 5. Delegating 5.1. Delegating Translator In some instances, you may wish to extend multiple translators with the same functionality. Rather than create separate subclasses for each extension, functionality that is common to multiple extensions can be added to a subclass of BaseDelegatingExecutionFactory . Within this subclass, delegation methods can be overridden to perform the common functionality. @Translator(name="custom-delegator") public class MyTranslator extends BaseDelegatingExecutionFactory<Object, Object> { @Override public Execution createExecution(Command command, ExecutionContext executionContext, RuntimeMetadata metadata, Object connection) throws TranslatorException { if (command instanceof Select) { //modify the command or return a different execution ... } //the super call will be to the delegate instance return super.createExecution(command, executionContext, metadata, connection); } ... } You will bundle and deploy your custom delegating translator like any other custom translator development. To use your delegating translator in a VDB, you define a translator override that wires in the delegate. <translator type="custom-delegator" name="my-translator"> <property value="delegateName" name="name of the delegate instance"/> <!-- any custom properties you may have on your custom translator --> </translator> From the example the translator type is custom-delegator. Now my-translator can be used as a translator-name on a source and will proxy all calls to whatever delegate instance you assign. Note The delegate instance can be any translator instance whether configured by its own translator entry or only the name of a standard translator type. Using a BaseDelegatingExecutionFactory by default means that standard override translator property settings on your instance will have no effect, since the underlying delegate is called instead. You may also wish to use a different class hierarchy and instead make your custom translator only implement DelegatingExecutionFactory instead.

Commands:
@Translator(name="custom-delegator") public class MyTranslator extends BaseDelegatingExecutionFactory<Object, Object> { @Override public Execution createExecution(Command command, ExecutionContext executionContext, RuntimeMetadata metadata, Object connection) throws TranslatorException { if (command instanceof Select) { //modify the command or return a different execution } //the super call will be to the delegate instance return super.createExecution(command, executionContext, metadata, connection); } }
<translator type="custom-delegator" name="my-translator"> <property value="delegateName" name="name of the delegate instance"/> <!-- any custom properties you may have on your custom translator --> </translator>
Chapter 8. Login to your automation controller dashboard With a successful installation of automation controller, one can access the dashboard via the following steps: Within your Red Hat OpenShift web console, in the left navigation menu, select Operators-> Installed Operators . Select Ansible Automation Platform . Within Operator Details, select the Automation Controller tab. Select the Name of the installed automation controller. Within the Automation Controller overview , the details including URL, Admin user, and Admin password are provided.

Commands:
Chapter 5. Deleting a database of a suffix that is no longer needed When you need to reclaim disk space on your Directory Server host, you can delete databases of suffixes that are not in use anymore. 5.1. Deleting a database using the command line This procedure instructs you how to delete a Directory Server database on the command line. Procedure List suffixes and their corresponding databases: # dsconf -D " cn=Directory Manager " ldap://server.example.com backend suffix list dc=example,dc=com (userroot) o=test (test_database) Note the name of the database that you want to delete. Enter the dsconf backend delete command and specify the name of the database: # dsconf -D " cn=Directory Manager " ldap://server.example.com backend delete " test_database " Confirm the deletion by typing "Yes I am sure" in the prompt: Deleting Backend cn=test_database,cn=ldbm database,cn=plugins,cn=config : Type 'Yes I am sure' to continue: Yes I am sure Verification List the suffixes/databases: # dsconf -D " cn=Directory Manager " ldap://server.example.com backend suffix list dc=example,dc=com (userroot) 5.2. Deleting a database using the web console This procedure instructs you how to delete a Directory Server database in a browser. Prerequisites You are logged in to the instance in the web console. Procedure Under Database , select the suffix that you want to delete. Navigate to Suffix Tasks Delete Suffix . Select Yes, I am sure. . Click Delete Suffix . Verification Under Database , review the list of suffixes in the configuration tree.

Commands:
dsconf -D " cn=Directory Manager " ldap://server.example.com backend suffix list dc=example,dc=com (userroot) o=test (test_database)
dsconf -D " cn=Directory Manager " ldap://server.example.com backend delete " test_database "
Deleting Backend cn=test_database,cn=ldbm database,cn=plugins,cn=config : Type 'Yes I am sure' to continue: Yes I am sure
dsconf -D " cn=Directory Manager " ldap://server.example.com backend suffix list dc=example,dc=com (userroot)
8.30. cmake 8.30.1. RHBA-2014:1506 - cmake bug fix and enhancement update Updated cmake packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. CMake is used to control the software compilation process using simple platform and compiler independent configuration files. CMake generates native makefiles and workspaces that can be used in the compiler environment of your choice. CMake is quite sophisticated: it is possible to support complex environments requiring system configuration, preprocessor generation, code generation, and template instantiation. This update also fixes the following bugs: Note The cmake packages have been upgraded to upstream version 2.8.12, which provides a number of bug fixes and enhancements over the version. (BZ# 606892 ) This update also fixes the following bugs: Bug Fixes BZ# 611250 Previously, the FindGTK2.cmake module was missing from the cmake packages. As a consequence, building GTK2 applications failed. This update adds FindGTK2.cmake and GTK2 applications now build as expected. BZ# 752864 Prior to this update, CMake ignored some options when working with the rpmbuild-4.8 package. As a consequence, building RPM packages on an RPM-based system failed. With this update, CMake works with rpmbuild-4.8 correctly, and the above problem no longer occurs. BZ# 896116 Due to an error in the "add_custom_target" command, CMake previously did not detect a custom target after creating it. With this update "add_custom_target" works properly, and CMake detects a created custom target as expected. The cmake packages have been upgraded to upstream version 2.8.12, which provides a number of bug fixes and enhancements over the version. (BZ#606892) Users of CMake are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
11.3. Costing Updates See Red Hat JBoss Data Virtualization Development Guide: Reference Material for the system procedures SYSADMIN.setColumnStats and SYSADMIN.setTableStats . To make costing updates persistent MetadataRepository implementations should be provided for the following methods: TableStats getTableStats(String vdbName, int vdbVersion, Table table); void setTableStats(String vdbName, int vdbVersion, Table table, TableStats tableStats); ColumnStats getColumnStats(String vdbName, int vdbVersion, Column column); void setColumnStats(String vdbName, int vdbVersion, Column column, ColumnStats columnStats);

Commands:
TableStats getTableStats(String vdbName, int vdbVersion, Table table); void setTableStats(String vdbName, int vdbVersion, Table table, TableStats tableStats); ColumnStats getColumnStats(String vdbName, int vdbVersion, Column column); void setColumnStats(String vdbName, int vdbVersion, Column column, ColumnStats columnStats);
12.3.3. Example Zone File Seen individually, directives and resource records can be difficult to grasp. However, when placed together in a single file, they become easier to understand. The following example shows a very basic zone file. In this example, standard directives and SOA values are used. The authoritative nameservers are set as dns1.example.com and dns2.example.com , which have A records that tie them to 10.0.1.2 and 10.0.1.3 , respectively. The email servers configured with the MX records point to server1 and server2 via CNAME records. Since the server1 and server2 names do not end in a trailing period ( . ), the USDORIGIN domain is placed after them, expanding them to server1.example.com and server2.example.com . Through the related A resource records, their IP addresses can be determined. FTP and Web services, available at the standard ftp.example.com and www.example.com names, are pointed at the appropriate servers using CNAME records.

Commands:
USDORIGIN example.com. USDTTL 86400 @ IN SOA dns1.example.com. hostmaster.example.com. ( 2001062501 ; serial 21600 ; refresh after 6 hours 3600 ; retry after 1 hour 604800 ; expire after 1 week 86400 ) ; minimum TTL of 1 day IN NS dns1.example.com. IN NS dns2.example.com. IN MX 10 mail.example.com. IN MX 20 mail2.example.com. dns1 IN A 10.0.1.1 dns2 IN A 10.0.1.2 server1 IN A 10.0.1.5 server2 IN A 10.0.1.6 ftp IN A 10.0.1.3 IN A 10.0.1.4 mail IN CNAME server1 mail2 IN CNAME server2 www IN CNAME server1
5.5. ftrace The ftrace framework provides users with several tracing capabilities, accessible through an interface much simpler than SystemTap's. This framework uses a set of virtual files in the debugfs file system; these files enable specific tracers. The ftrace function tracer outputs each function called in the kernel in real time; other tracers within the ftrace framework can also be used to analyze wakeup latency, task switches, kernel events, and the like. You can also add new tracers for ftrace , making it a flexible solution for analyzing kernel events. The ftrace framework is useful for debugging or analyzing latencies and performance issues that take place outside of user-space. Unlike other profilers documented in this guide, ftrace is a built-in feature of the kernel. 5.5.1. Using ftrace The Red Hat Enterprise Linux 6 kernels have been configured with the CONFIG_FTRACE=y option. This option provides the interfaces required by ftrace . To use ftrace , mount the debugfs file system as follows: mount -t debugfs nodev /sys/kernel/debug All the ftrace utilities are located in /sys/kernel/debug/tracing/ . View the /sys/kernel/debug/tracing/available_tracers file to find out what tracers are available for your kernel: cat /sys/kernel/debug/tracing/available_tracers To use a specific tracer, write it to /sys/kernel/debug/tracing/current_tracer . For example, wakeup traces and records the maximum time it takes for the highest-priority task to be scheduled after the task wakes up. To use it: echo wakeup > /sys/kernel/debug/tracing/current_tracer To start or stop tracing, write to /sys/kernel/debug/tracing/tracing_on , as in: echo 1 > /sys/kernel/debug/tracing/tracing_on (enables tracing) echo 0 > /sys/kernel/debug/tracing/tracing_on (disables tracing) The results of the trace can be viewed from the following files: /sys/kernel/debug/tracing/trace This file contains human-readable trace output. /sys/kernel/debug/tracing/trace_pipe This file contains the same output as /sys/kernel/debug/tracing/trace , but is meant to be piped into a command. Unlike /sys/kernel/debug/tracing/trace , reading from this file consumes its output.

Commands:
power wakeup irqsoff function sysprof sched_switch initcall nop