mtpti5iD/redhat-docs_dataset huggingface dataset:
Architecture Guide Red Hat Ceph Storage 8 Guide on Red Hat Ceph Storage Architecture Red Hat Ceph Storage Documentation Team

Commands:
rbd create --size 102400 mypool/myimage --image-feature 5
rbd -p mypool create myimage --size 102400 --image-features 13
epoch 1 fsid 50fcf227-be32-4bcb-8b41-34ca8370bd17 last_changed 2021-12-12 11:10:46.700821 created 2021-12-12 11:10:46.700821 min_mon_release 14 (nautilus) 0: [v2:10.0.0.10:3300/0,v1:10.0.0.10:6789/0] mon.a 1: [v2:10.0.0.11:3300/0,v1:10.0.0.11:6789/0] mon.b 2: [v2:10.0.0.12:3300/0,v1:10.0.0.12:6789/0] mon.c
4.3.2. Running GDB This section will describe a basic execution of GDB, using the following simple program: hello.c The following procedure illustrates the debugging process in its most basic form. Procedure 4.1. Debugging a 'Hello World' Program Compile hello.c into an executable with the debug flag set, as in: gcc -g -o hello hello.c Ensure that the resulting binary hello is in the same directory as hello.c . Run gdb on the hello binary, that is, gdb hello . After several introductory comments, gdb will display the default GDB prompt: The variable hello is global, so it can be seen even before the main procedure starts: Note that the print targets hello[0] and *hello require the evaluation of an expression, as does, for example, *(hello + 1) : , list the source: The list reveals that the fprintf call is on line 8. Apply a breakpoint on that line and resume the code: Finally, use the command to step past the fprintf call, executing it: The following sections describe more complex applications of GDB.

Commands:
#include <stdio.h> char hello[] = { "Hello, World!" }; int main() { fprintf (stdout, "%s\n", hello); return (0); }
(gdb)
gdb) p hello USD1 = "Hello, World!" (gdb) p hello[0] USD2 = 72 'H' (gdb) p *hello USD3 = 72 'H' (gdb)
(gdb) p *(hello + 1) USD4 = 101 'e'
(gdb) l 1 #include <stdio.h> 2 3 char hello[] = { "Hello, World!" }; 4 5 int 6 main() 7 { 8 fprintf (stdout, "%s\n", hello); 9 return (0); 10 }
(gdb) br 8 Breakpoint 1 at 0x80483ed: file hello.c, line 8. (gdb) r Starting program: /home/moller/tinkering/gdb-manual/hello Breakpoint 1, main () at hello.c:8 8 fprintf (stdout, "%s\n", hello);
(gdb) n Hello, World! 9 return (0);
Appendix A. Component Versions This appendix is a list of components and their versions in the Red Hat Enterprise Linux 6.8 release. Table A.1. Component Versions Component Version Kernel 2.6.32-642 QLogic qla2xxx driver 8.07.00.26.06.8-k QLogic ql2xxx firmware ql2100-firmware-1.19.38-3.1 ql2200-firmware-2.02.08-3.1 ql23xx-firmware-3.03.27-3.1 ql2400-firmware-7.03.00-1 ql2500-firmware-7.03.00-1 Emulex lpfc driver 0:11.0.0.4 iSCSI initiator utils iscsi-initiator-utils-6.2.0.873-21 DM-Multipath device-mapper-multipath-0.4.9-93 LVM lvm2-2.02.143-7

Commands:
2.2. ModeShape User Roles Before publishing files to a ModeShape repository, you must be sure that the ModeShape server has at least one user which has the connect and readwrite roles or the connect and admin roles. At the time of installation, a default user modeshapeUser with roles admin and connect is added to the ApplicationRealm. You can add multiple modeshape users using ./add-user.sh script. The roles specific to ModeShape are as follows: connect - required to access any of the ModeShape WAR applications in JBoss Data Virtualization (REST service, WebDAV service, CMIS service and Repository Explorer) and required to connect to ModeShape using the remote JDBC driver (which is the case for JBDS) admin - allows all repository operations, for example, read/write nodes, register/unregister node types, create/delete workspaces, backup/restore, reindex workspaces and unlock any locked nodes. readwrite - allows reading/writing nodes but does not allow any of the other operations mentioned for admin role. readonly - allows only the reading of nodes (that is navigating node paths).

Commands:
Chapter 3. Installing the all-in-one Red Hat OpenStack Platform environment Before you can begin configuring, deploying, and testing your all-in-one environment, you must configure a non-root user and install the necessary packages and dependencies: Create a non-root user on the all-in-one host: Set the password for the stack user: Disable password requirements when using sudo as the stack user: Log in as the non-root user on the all-in-one host: Register the machine with Red Hat Subscription Manager. Enter your Red Hat subscription credentials at the prompt: Attach your Red Hat subscription to the entitlement server: Note The --auto option might not subscribe you to the correct subscription pool. Ensure that you subscribe to the correct pool, otherwise you might not be able to enable all of the repositories necessary for this installation. Use the subscription-manager list --all --available command to identify the correct pool ID. Lock the undercloud to Red Hat Enterprise Linux 8.1: Run the following commands to install dnf-utils , disable all default repositories, and then enable the necessary repositories: Note The all-in-one environment is a Technology Preview feature in Red Hat OpenStack Platform 16. Install the TripleO command line interface (CLI):

Commands:
useradd stack
passwd stack
echo "stack ALL=(root) NOPASSWD:ALL" | tee -a /etc/sudoers.d/stack chmod 0440 /etc/sudoers.d/stack
ssh stack@<all-in-one>
[stack@all-in-one]USD sudo subscription-manager register
[stack@all-in-one]USD sudo subscription-manager attach --auto
sudo subscription-manager release --set=8.1
[stack@all-in-one]USD sudo dnf install -y dnf-utils [stack@all-in-one]USD sudo subscription-manager repos --disable=* [stack@all-in-one]USD sudo subscription-manager repos --enable=rhel-8-for-x86_64-baseos-rpms --enable=rhel-8-for-x86_64-appstream-eus-rpms --enable=rhel-8-for-x86_64-highavailability-eus-rpms --enable=ansible-2.8-for-rhel-8-x86_64-rpms --enable=openstack-16-for-rhel-8-x86_64-rpms --enable=fast-datapath-for-rhel-8-x86_64-rpms --enable=rhel-8-for-x86_64-highavailability-rpms
[stack@all-in-one]USD sudo dnf install -y python3-tripleoclient
Chapter 1. Troubleshooting Java Web Start The Red Hat build of OpenJDK 8 for Microsoft Windows distribution includes an implementation of the Java Web Start deployment protocol based on the IcedTea-Web open source project. Note This implementation of the Java Web Start protocol may not be fully compatible with the proprietary Java Web Start implementation included in the Oracle Java 8 distribution. To report an issue with your Web Start application, please include the appropriate details from the %LOCALAPPDATA%\RedHat\java-1.8.0-openjdk-[version]\webstart\javaws_last_log.txt log file. Note The log file captures the standard output of your Java Web Start application and may contain confidential information. 1.1. Java Web Start cookie support IcedTea-Web does not support sending cookie information (such as JSESSIONID ) when fetching JNLP specified files. As a result, some applications may not launch correctly.

Commands:
Appendix C. GFS2 tracepoints and the debugfs glocks File This appendix describes both the glock debugfs interface and the GFS2 tracepoints. It is intended for advanced users who are familiar with file system internals who would like to learn more about the design of GFS2 and how to debug GFS2-specific issues. C.1. GFS2 tracepoint Types There are currently three types of GFS2 tracepoints: glock (pronounced "gee-lock") tracepoints, bmap tracepoints and log tracepoints. These can be used to monitor a running GFS2 file system and give additional information to that which can be obtained with the debugging options supported in releases of Red Hat Enterprise Linux. Tracepoints are particularly useful when a problem, such as a hang or performance issue, is reproducible and thus the tracepoint output can be obtained during the problematic operation. In GFS2, glocks are the primary cache control mechanism and they are the key to understanding the performance of the core of GFS2. The bmap (block map) tracepoints can be used to monitor block allocations and block mapping (lookup of already allocated blocks in the on-disk metadata tree) as they happen and check for any issues relating to locality of access. The log tracepoints keep track of the data being written to and released from the journal and can provide useful information on that part of GFS2. The tracepoints are designed to be as generic as possible. This should mean that it will not be necessary to change the API during the course of Red Hat Enterprise Linux 6. On the other hand, users of this interface should be aware that this is a debugging interface and not part of the normal Red Hat Enterprise Linux 6 API set, and as such Red Hat makes no guarantees that changes in the GFS2 tracepoints interface will not occur. Tracepoints are a generic feature of Red Hat Enterprise Linux 6 and their scope goes well beyond GFS2. In particular they are used to implement the blktrace infrastructure and the blktrace tracepoints can be used in combination with those of GFS2 to gain a fuller picture of the system performance. Due to the level at which the tracepoints operate, they can produce large volumes of data in a very short period of time. They are designed to put a minimum load on the system when they are enabled, but it is inevitable that they will have some effect. Filtering events with a variety of means can help reduce the volume of data and help focus on obtaining just the information which is useful for understanding any particular situation.

Commands:
32.7. Additional Resources For more information about users and groups, and tools to manage them, refer to the following resources. 32.7.1. Installed Documentation Related man pages - There are a number of man pages for the various applications and configuration files involved with managing users and groups. Some of the more important man pages have been listed here: User and Group Administrative Applications man chage - A command to modify password aging policies and account expiration. man gpasswd - A command to administer the /etc/group file. man groupadd - A command to add groups. man grpck - A command to verify the /etc/group file. man groupdel - A command to remove groups. man groupmod - A command to modify group membership. man pwck - A command to verify the /etc/passwd and /etc/shadow files. man pwconv - A tool to convert standard passwords to shadow passwords. man pwunconv - A tool to convert shadow passwords to standard passwords. man useradd - A command to add users. man userdel - A command to remove users. man usermod - A command to modify users. Configuration Files man 5 group - The file containing group information for the system. man 5 passwd - The file containing user information for the system. man 5 shadow - The file containing passwords and account expiration information for the system.

Commands:
Chapter 288. RxJava2 Component Available as of Camel version 2.22 RxJava2 based back-end for Camel's reactive streams component. See more details in the camel-streams-component documentation. Maven users will need to add the following dependency to their pom.xml for this component: <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-rxjava2</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>

Commands:
<dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-rxjava2</artifactId> <version>x.x.x</version> <!-- use the same version as your Camel core version --> </dependency>
8.190. python-linux-procfs 8.190.1. RHBA-2014:1615 - python-linux-procfs bug fix update Updated python-linux-procfs packages that fix one bug are now available for Red Hat Enterprise Linux 6. The python-linux-procfs package enables the extraction of information from the /proc file system. Bug Fix BZ# 1133700 Previously, there was a bug in the tuna packages; when the scheduler priority was not specified, the "tuna -t USDPID -p OTHER" command failed with an error. Fixing this bug in tuna required an update of the python-linux-procfs package. Therefore, python-linux-procfs has been updated to the newer version with this update to address the tuna bug. Users of python-linux-procfs are advised to upgrade to these updated packages, which fix this bug.

Commands:
Appendix C. CLI help Satellite offers multiple user interfaces: Satellite web UI, Hammer CLI, API, and through Ansible collection redhat.satellite. If you want to administer Satellite on the command line, have a look at the following help output. Satellite services A set of services that Satellite Server and Capsule Servers use for operation. You can use the satellite-maintain tool to manage these services. To see the full list of services, enter the satellite-maintain service list command on the machine where Satellite or Capsule Server is installed. For more information, run satellite-maintain --help on your Satellite Server or Capsule Server. Satellite plugins You can extend Satellite by installing plugins. For more information, run satellite-installer --full-help on your Satellite Server or Capsule Server. Hammer CLI You can manage Satellite on the command line using hammer . For more information on using Hammer CLI, see Hammer CLI guide or run hammer --help on your Satellite Server or Capsule Server.

Commands:
7.177. redhat-release-server 7.177.1. RHBA-2015:1260 - redhat-release-server bug fix and enhancement update An updated redhat-release-server package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The redhat-release-server package contains the Red Hat Enterprise Linux Server release files. This updated redhat-release-server package reflects changes made for the release of Red Hat Enterprise Linux 6.7. Enhancement BZ# 1080012 The redhat-release-server package now includes default product certificates related to Beta, HTB, and GA product IDs. These certificates are consumed by the subscription-manager utility. Users of Red Hat Enterprise Linux 6 are advised to upgrade to this updated redhat-release-server package.

Commands:
Chapter 16. Disabling Multicloud Object Gateway external service after deploying OpenShift Data Foundation When you deploy OpenShift Data Foundation, public IPs are created even when OpenShift is installed as a private cluster. However, you can disable the Multicloud Object Gateway (MCG) load balancer usage by using the disableLoadBalancerService variable in the storagecluster CRD. This restricts MCG from creating any public resources for private clusters and helps to disable the NooBaa service EXTERNAL-IP . Procedure Run the following command and add the disableLoadBalancerService variable in the storagecluster YAML to set the service to ClusterIP: Note To undo the changes and set the service to LoadBalancer, set the disableLoadBalancerService variable to false or remove that line completely.

Commands:
oc edit storagecluster -n openshift-storage <storagecluster_name> [...] spec: arbiter: {} encryption: kms: {} externalStorage: {} managedResources: cephBlockPools: {} cephCluster: {} cephConfig: {} cephDashboard: {} cephFilesystems: {} cephNonResilientPools: {} cephObjectStoreUsers: {} cephObjectStores: {} cephRBDMirror: {} cephToolbox: {} mirroring: {} multiCloudGateway: disableLoadBalancerService: true <--------------- Add this endpoints: [...]
3.5. Suspend and Resume When a system is suspended, the kernel calls on drivers to store their states and then unloads them. When the system is resumed, it reloads these drivers, which attempt to reprogram their devices. The drivers' ability to accomplish this task determines whether the system can be resumed successfully. Video drivers are particularly problematic in this regard, because the Advanced Configuration and Power Interface (ACPI) specification does not require system firmware to be able to reprogram video hardware. Therefore, unless video drivers are able to program hardware from a completely uninitialized state, they may prevent the system from resuming. Red Hat Enterprise Linux 6 includes greater support for new graphics chipsets, which ensures that suspend and resume will work on a greater number of platforms. In particular, support for NVIDIA chipsets has been greatly improved; in particular for the GeForce 8800 series.

Commands:
6.3. Command Line: Managing Topology Using the ipa topology* Commands 6.3.1. Getting Help for Topology Management Commands To display all commands used to manage replication topology: To display detailed help for a particular command, run it with the --help option: 6.3.2. Setting up Replication Between Two Servers Use the ipa topologysegment-add command to create a topology segment for the two servers. When prompted, provide: the required topology suffix: domain or ca Note If you want to create a segment between ca suffixes, both servers must have a CA installed. See Section 26.8, "Installing a CA Into an Existing IdM Domain" . the left node and the right node, representing the two servers optionally, a custom name for the segment For example: Adding the new segment joins the servers in a replication agreement. Optional. Use the ipa topologysegment-show command to verify that the new segment is configured. 6.3.3. Stopping Replication Between Two Servers To stop replication, you must delete the corresponding replication segment between the servers. To do that, you need to know the segment name. If you do not know the name, use the ipa topologysegment-find command to display all segments, and locate the required segment in the output. When prompted, provide the required topology suffix: domain or ca . For example: Use the ipa topologysegment-del command to remove the topology segment joining the two servers. Deleting the segment removes the replication agreement. Optional. Use the ipa topologysegment-find command to verify that the segment is no longer listed.

Commands:
ipa help topology
ipa topologysuffix-show --help
ipa topologysegment-add Suffix name: domain Left node: server1.example.com Right node: server2.example.com Segment name [server1.example.com-to-server2.example.com]: new_segment --------------------------- Added segment "new_segment" --------------------------- Segment name: new_segment Left node: server1.example.com Right node: server2.example.com Connectivity: both
ipa topologysegment-show Suffix name: domain Segment name: new_segment Segment name: new_segment Left node: server1.example.com Right node: server2.example.com Connectivity: both
ipa topologysegment-find Suffix name: domain ------------------ 8 segments matched ------------------ Segment name: new_segment Left node: server1.example.com Right node: server2.example.com Connectivity: both ---------------------------- Number of entries returned 8 ----------------------------
ipa topologysegment-del Suffix name: domain Segment name: new_segment ----------------------------- Deleted segment "new_segment" -----------------------------
ipa topologysegment-find Suffix name: domain ------------------ 7 segments matched ------------------ Segment name: server2.example.com-to-server3.example.com Left node: server2.example.com Right node: server3.example.com Connectivity: both ---------------------------- Number of entries returned 7 ----------------------------
5.331. telnet 5.331.1. RHBA-2012:1312 - telnet bug fix update Updated telnet packages that fix one bug are now available for Red Hat Enterprise Linux 6. Telnet is a popular protocol for logging in to remote systems over the Internet. The telnet-server package includes a telnet service that supports remote logins into the host machine. The telnet service is disabled by default. Bug Fix BZ# 860012 Prior to this update, the telnetd daemon did not reuse previously created entries in the /var/run/utmp file. Consequently, /var/run/utmp grew and contained empty entries, eventually causing various other problems. With this update, telnetd has been fixed to reuse entries in /var/run/utmp and behave like other programs which use this file, thus preventing this bug. All users of telnet are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 6. Integration of dynamic JFR recordings with the agent harvester for archiving When you enable the Cryostat agent to start dynamic JFR recordings based on MBean custom triggers, you can also integrate these JFR recordings with the agent harvester system. This integration means that any JFR recording data resulting from MBean custom triggers is periodically captured in JFR snapshots and pushed to the Cryostat server for archiving, based on the harvester's configured schedule. MBean custom triggers with agent harvester periods The agent harvester is another configurable feature, which enables the Cryostat agent to start JFR recordings automatically at agent startup based on a given event template. The agent harvester includes a configurable property that you can use to define a schedule for capturing and uploading recording snapshots to the Cryostat server. By defining MBean custom triggers and an agent harvester period without a harvester template, you can achieve a setup where the agent does both of the following: Agent dynamically starts JFR recordings based on MBean custom triggers. Agent uses configured harvester periods to periodically capture snapshots of the recording data and upload this data to the Cryostat server. In this situation, the agent continues to capture recording data until you manually stop the dynamic JFR recording or the host JVM shuts down. Configuration of an agent harvester period When you configure your target application to load the Cryostat agent, you can also configure an agent harvester period to enable regular uploads of JFR recording data. You can specify the value of the harvester period in milliseconds. By default, the Cryostat agent is not enabled to perform any scheduled harvest uploading of JFR recording data. You can configure an agent harvester period in either of the following ways: Using a JVM system property flag The following example shows how to configure a harvester period by using a JVM system property flag: Using an environment variable The following example shows how to configure a harvester period by using an environment variable: The preceding examples show a harvester period value of 1000. Based on this example, the agent uploads JFR recording data for archiving every 1000 milliseconds (that is, at regular 1-second intervals). Note Cryostat supports each of the following different ways to start JFR recordings: You can start recordings manually from the Cryostat web console. The Cryostat agent can start recordings dynamically based on MBean custom triggers. The Cryostat agent can start recordings automatically at agent startup based on a given harvester template. The Cryostat server can send on-demand requests over JMX or an agent HTTP connection to start recordings based on automated rules. In this situation, agent harvester settings control the capture and upload of all JFR recording data regardless of which way JFR recordings are started in the system.

Commands:
-Dcryostat.agent.harvester.period-ms=1000
- name: CRYOSTAT_AGENT_HARVESTER_PERIOD_MS value: 1000
7.61. gawk 7.61.1. RHBA-2012:1146 - gawk bug fix update Updated gawk packages that fix one bug are now available for Red Hat Enterprise Linux 6. The gawk packages provide the GNU version of the text processing utility awk. Awk interprets a special-purpose programming language to do quick and easy text pattern matching and reformatting jobs. Bug Fix BZ#829558 Prior to this update, the "re_string_skip_chars" function incorrectly used the character count instead of the raw length to estimate the string length. As a consequence, any text in multi-byte encoding that did not use the UTF-8 format failed to be processed correctly. This update modifies the underlying code so that the correct string length is used. multi-byte encoding is processed correctly. All users of gawk requiring multi-byte encodings that do not use UTF-8 are advised to upgrade to these updated packages, which fix this bug.

Commands: