mtpti5iD/redhat-docs_dataset huggingface dataset:
12.5. Removing an Object Class This section describes how to delete an object class using the command line and the web console. Warning Do not delete default schema elements. They are required by Directory Server. 12.5.1. Removing an Object Class Using the Command Line Use the ldapmodify utility to delete an object class entry. For example, to delete the examplePerson object class: Remove the unwanted attributes from any entries that use them. For details, see Section 12.8, "Removing an Attribute" . Delete the object class entry: For further details about object class definitions, see Section 12.1.2, "Object Classes" . 12.5.2. Removing an Object Class Using the Web Console To remove an object class using the web console: Open the Directory Server user interface in the web console. See Section 1.4, "Logging Into Directory Server Using the Web Console" . Select the instance. Select Schema Objectclasses . Click the Choose Action button to the object class entry you want to remove. Select Delete Objectclass . Click Yes to confirm.

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com schema objectclasses delete examplePerson
7.6.3. Related Books The Concise Guide to XFree86 for Linux by Aron Hsiao; Que - Provides an expert's view of the operation of XFree86 on Linux systems. The New XFree86 by Bill Ball; Prima Publishing - Discuses XFree86 and its relationship with the popular desktop environments, such as GNOME and KDE. Beginning GTK+ and GNOME by Peter Wright; Wrox Press, Inc. - Introduces programmers to the GNOME architecture, showing them how to get started with GTK+. GTK+/GNOME Application Development by Havoc Pennington; New Riders Publishing - An advanced look into the heart of GTK+ programming, focusing on sample code and a thorough look at the available APIs. KDE 2.0 Development by David Sweet and Matthias Ettrich; Sams Publishing - Instructs beginning and advanced developers on taking advantage of the many environment guidelines required to built QT applications for KDE.

Commands:
5.9.8. Creating RAID Arrays In addition to supporting hardware RAID solutions, Red Hat Enterprise Linux supports software RAID. There are two ways that software RAID arrays can be created: While installing Red Hat Enterprise Linux After Red Hat Enterprise Linux has been installed The following sections review these two methods. 5.9.8.1. While Installing Red Hat Enterprise Linux During the normal Red Hat Enterprise Linux installation process, RAID arrays can be created. This is done during the disk partitioning phase of the installation. To begin, you must manually partition your disk drives using Disk Druid . You must first create a new partition of the type "software RAID." , select the disk drives that you want to be part of the RAID array in the Allowable Drives field. Continue by selecting the desired size and whether you want the partition to be a primary partition. Once you have created all the partitions required for the RAID array(s) that you want to create, you must then use the RAID button to actually create the arrays. You are then presented with a dialog box where you can select the array's mount point, file system type, RAID device name, RAID level, and the "software RAID" partitions on which this array is to be based. Once the desired arrays have been created, the installation process continues as usual. Note For more information on creating software RAID arrays during the Red Hat Enterprise Linux installation process, refer to the System Administrators Guide .

Commands:
Chapter 11. OpenStack configuration test Starting with Red Hat OpenStack Platform (RHOSP) 15, OpenStack Configuration test will be the new test available for Partners. This test is for the Manila and Neutron plugin certification test plan, and is planned only for controller node. The OpenStack Configuration test includes and supports Open Virtual Network subtest. Open Virtual Network subtest Open Virtual Network (OVN) is an Open vSwitch-based software-defined networking (SDN) solution that supplies network services to instances. OVN is expected to be configured and operational. This subtest validates the status of OVN. Success criteria The status of the test depends on the OVN as follows: If OVN is ON, the test status is PASS. If OVN is OFF, the test status is FAIL. If OVN is unknown, the test status is REVIEW. 11.1. Additional resources For more information about OVN, see OVN Architecture .

Commands:
Chapter 12. Enable signup Configure developer signup by implementing self-service or manual mode. You can configure the workflow for developers to be self-service or by manual invite only. Self-service signups are done by developers through the Developer Portal, while manual invites are handled by your admins through the Admin Portal. By default, developers are enabled to sign up by themselves. If you enable developer self-service, you can require admin approval before the developer account can be activated. To do so, navigate to Audience > Accounts > Settings > Usage Rules .

Commands:
5.143. libcgroup 5.143.1. RHBA-2012:0867 - libcgroup bug fix update Updated libcgroup packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libcgroup packages provides tools and libraries to control and monitor control groups. Bug Fix BZ# 758493 Prior to this update, a bug in the libcgroup package caused admin_id and admin_gid to not be displayed correctly because cgroup control files were not differentiated from the 'tasks' file. This update fixes this problem by adding a check in the 'cgroup_fill_cgc()' function to see if a file is a 'tasks' file or not. All users are advised to upgrade to these updated libcgroup packages, which fix this bug.

Commands:
Appendix B. Fencing Policies for Red Hat Gluster Storage The following fencing policies are required for Red Hat Hyperconverged Infrastructure for Virtualization (RHHI for Virtualization) deployments. They ensure that hosts are not shut down in situations where brick processes are still running, or when shutting down the host would remove the volume's ability to reach a quorum. These policies can be set in the New Cluster or Edit Cluster window in the Administration Portal when Red Hat Gluster Storage functionality is enabled. Skip fencing if gluster bricks are up Fencing is skipped if bricks are running and can be reached from other peers. Skip fencing if gluster quorum not met Fencing is skipped if bricks are running and shutting down the host will cause loss of quorum These policies are checked after all other fencing policies when determining whether a node is fenced. Additional fencing policies may be useful for your deployment. For further details about fencing, see the Red Hat Virtualization Technical Reference : https://access.redhat.com/documentation/en-us/red_hat_virtualization/4.4/html/technical_reference/fencing .

Commands:
Chapter 118. KafkaUserAuthorizationSimple schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserAuthorizationSimple type from other subtypes which may be added in the future. It must have the value simple for the type KafkaUserAuthorizationSimple . Property Property type Description type string Must be simple . acls AclRule array List of ACL rules which should be applied to this user.

Commands:
Chapter 5. Kernel parameters You can modify the kernel behaviour with kernel parameters. Parameter Description BridgeNfCallArpTables Configures sysctl net.bridge.bridge-nf-call-arptables key. The default value is 1 . BridgeNfCallIp6Tables Configures sysctl net.bridge.bridge-nf-call-ip6tables key. The default value is 1 . BridgeNfCallIpTables Configures sysctl net.bridge.bridge-nf-call-iptables key. The default value is 1 . ExtraKernelModules Hash of extra kernel modules to load. ExtraKernelPackages List of extra kernel related packages to install. ExtraSysctlSettings Hash of extra sysctl settings to apply. FsAioMaxNumber The kernel allocates aio memory on demand, and this number limits the number of parallel aio requests; the only drawback of a larger limit is that a malicious guest could issue parallel requests to cause the kernel to set aside memory. Set this number at least as large as 128 * (number of virtual disks on the host) Libvirt uses a default of 1M requests to allow 8k disks, with at most 64M of kernel memory if all disks hit an aio request at the same time. The default value is 0 . InotifyIntancesMax Configures sysctl fs.inotify.max_user_instances key. The default value is 1024 . KernelDisableIPv6 Configures sysctl net.ipv6.{default/all}.disable_ipv6 keys. The default value is 0 . KernelIpForward Configures net.ipv4.ip_forward key. The default value is 1 . KernelIpNonLocalBind Configures net.ipv{4,6}.ip_nonlocal_bind key. The default value is 1 . KernelPidMax Configures sysctl kernel.pid_max key. The default value is 1048576 . NeighbourGcThreshold1 Configures sysctl net.ipv4.neigh.default.gc_thresh1 value. This is the minimum number of entries to keep in the ARP cache. The garbage collector will not run if there are fewer than this number of entries in the cache. The default value is 1024 . NeighbourGcThreshold2 Configures sysctl net.ipv4.neigh.default.gc_thresh2 value. This is the soft maximum number of entries to keep in the ARP cache. The garbage collector will allow the number of entries to exceed this for 5 seconds before collection will be performed. The default value is 2048 . NeighbourGcThreshold3 Configures sysctl net.ipv4.neigh.default.gc_thresh3 value. This is the hard maximum number of entries to keep in the ARP cache. The garbage collector will always run if there are more than this number of entries in the cache. The default value is 4096 .

Commands:
4.327. tomcat6 4.327.1. RHSA-2012:0475 - Moderate: tomcat6 security update Updated tomcat6 packages that fix two security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. 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. Apache Tomcat is a servlet container for the Java Servlet and JavaServer Pages (JSP) technologies. Security Fixes CVE-2011-4858 It was found that the Java hashCode() method implementation was susceptible to predictable hash collisions. A remote attacker could use this flaw to cause Tomcat to use an excessive amount of CPU time by sending an HTTP request with a large number of parameters whose names map to the same hash value. This update introduces a limit on the number of parameters processed per request to mitigate this issue. The default limit is 512 for parameters and 128 for headers. These defaults can be changed by setting the org.apache.tomcat.util.http.Parameters.MAX_COUNT and org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT system properties. CVE-2012-0022 It was found that Tomcat did not handle large numbers of parameters and large parameter values efficiently. A remote attacker could make Tomcat use an excessive amount of CPU time by sending an HTTP request containing a large number of parameters or large parameter values. This update introduces limits on the number of parameters and headers processed per request to address this issue. Refer to the CVE-2011-4858 description for information about the org.apache.tomcat.util.http.Parameters.MAX_COUNT and org.apache.tomcat.util.http.MimeHeaders.MAX_COUNT system properties. Red Hat would like to thank oCERT for reporting CVE-2011-4858. oCERT acknowledges Julian Walde and Alexander Klink as the original reporters of CVE-2011-4858. Users of Tomcat should upgrade to these updated packages, which correct these issues. Tomcat must be restarted for this update to take effect.

Commands:
Chapter 11. Managing container storage interface (CSI) component placements Each cluster consists of a number of dedicated nodes such as infra and storage nodes. However, an infra node with a custom taint will not be able to use OpenShift Data Foundation Persistent Volume Claims (PVCs) on the node. So, if you want to use such nodes, you can set tolerations to bring up csi-plugins on the nodes. For more information, see https://access.redhat.com/solutions/4827161 . Procedure Edit the configmap to add the toleration for the custom taint. Remember to save before exiting the editor. Display the configmap to check the added toleration. Example output of the added toleration for the taint, nodetype=infra:NoSchedule : Restart the rook-ceph-operator if the csi-cephfsplugin- * and csi-rbdplugin- * pods fail to come up on their own on the infra nodes. Example : Verification step Verify that the csi-cephfsplugin- * and csi-rbdplugin- * pods are running on the infra nodes.

Commands:
oc edit configmap rook-ceph-operator-config -n openshift-storage
oc get configmap rook-ceph-operator-config -n openshift-storage -o yaml
apiVersion: v1 data: [...] CSI_PLUGIN_TOLERATIONS: | - key: nodetype operator: Equal value: infra effect: NoSchedule - key: node.ocs.openshift.io/storage operator: Equal value: "true" effect: NoSchedule [...] kind: ConfigMap metadata: [...]
oc delete -n openshift-storage pod <name of the rook_ceph_operator pod>
oc delete -n openshift-storage pod rook-ceph-operator-5446f9b95b-jrn2j pod "rook-ceph-operator-5446f9b95b-jrn2j" deleted
12.2. Translators A translator acts as the bridge between JBoss Data Virtualization and an external system, which is most commonly accessed through a JCA resource adapter. Translators indicate what SQL constructs are supported and what import metadata can be read from particular datasources. A translator is typically paired with a particular JCA resource adapter. A JCA resource adapter is not needed in instances where features such as pooling, environment dependent configuration management, or advanced security handling are not needed. Note See Red Hat JBoss Data Virtualization Development Guide: Server Development for more information on developing custom translators and JCA resource adapters. See the Red Hat JBoss Data Virtualization Administration and Configuration Guide and the examples in EAP_HOME /docs/teiid/datasources for more information about configuring resource adapters.

Commands:
5.260. python-repoze-who 5.260.1. RHEA-2012:0982 - python-repoze-who enhancement update An updated python-repoze-who package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The python-repoze-who package provides an identification and authentication framework for arbitrary Python WSGI applications and acts as WSGI middleware. The python-repoze-who package has been upgraded to upstream version 1.0.18, which adds support for enforcing timeouts for cookies issued by the auth_tkt plugin via the "timeout" and "reissue_time" config parameters. (BZ# 639075 ) All users of python-repoze-who are advised to upgrade to this updated package, which adds this enhancement.

Commands:
probe::ioblock_trace.end Name probe::ioblock_trace.end - Fires whenever a block I/O transfer is complete. Synopsis Values None Description name - name of the probe point q - request queue on which this bio was queued. devname - block device name ino - i-node number of the mapped file bytes_done - number of bytes transferred sector - beginning sector for the entire bio flags - see below BIO_UPTODATE 0 ok after I/O completion BIO_RW_BLOCK 1 RW_AHEAD set, and read/write would block BIO_EOF 2 out-out-bounds error BIO_SEG_VALID 3 nr_hw_seg valid BIO_CLONED 4 doesn't own data BIO_BOUNCED 5 bio is a bounce bio BIO_USER_MAPPED 6 contains user pages BIO_EOPNOTSUPP 7 not supported rw - binary trace for read/write request vcnt - bio vector count which represents number of array element (page, offset, length) which makes up this I/O request idx - offset into the bio vector array phys_segments - number of segments in this bio after physical address coalescing is performed. size - total size in bytes bdev - target block device bdev_contains - points to the device object which contains the partition (when bio structure represents a partition) p_start_sect - points to the start sector of the partition structure of the device Context The process signals the transfer is done.

Commands:
ioblock_trace.end
Chapter 1. Interactively selecting a system-wide Red Hat build of OpenJDK version on RHEL If you have multiple versions of Red Hat build of OpenJDK installed on RHEL, you can interactively select the default Red Hat build of OpenJDK version to use system-wide. Note If you do not have root privileges, you can select a Red Hat build of OpenJDK version by configuring the JAVA_HOME environment variable. Prerequisites You must have root privileges on the system. Multiple versions of Red Hat build of OpenJDK were installed using the yum package manager. Procedure View the Red Hat build of OpenJDK versions installed on the system. USD yum list installed "java*" A list of installed Java packages appears. Display the Red Hat build of OpenJDK versions that can be used for a specific java command and select the one to use: The current system-wide Red Hat build of OpenJDK version is marked with an asterisk. The current Red Hat build of OpenJDK version for the specified java command is marked with a plus sign. Press Enter to keep the current selection or enter the Selection number of the Red Hat build of OpenJDK version you want to select followed by the Enter key. The default Red Hat build of OpenJDK version for the system is the selected version. Verify that the chosen binary is selected. Note This procedure configures the java command. Then javac command can be set up in a similar way, but it operates independently. If you have Red Hat build of OpenJDK installed, alternatives provides more possible selections. In particular, the javac master alternative switches many binaries provided by the -devel sub-package. Even if you have Red Hat build of OpenJDK installed, java (and other JRE masters) and javac (and other Red Hat build of OpenJDK masters) still operate separately, so you can have different selections for JRE and JDK. The alternatives --config java command affects the jre and its associated slaves. If you want to change Red Hat build of OpenJDK, use the javac alternatives command. The --config javac utility configures the SDK and related slaves. To see all possible masters, use alternatives --list and check all of the java , javac , jre , and sdk masters.

Commands:
Installed Packages java-1.8.0-openjdk.x86_64 1:1.8.0.242.b08-0.el8_1 @rhel-8-appstream-rpms java-1.8.0-openjdk-headless.x86_64 1:1.8.0.242.b08-0.el8_1 @rhel-8-appstream-rpms java-11-openjdk.x86_64 1:11.0.9.10-0.el8_1 @rhel-8-appstream-rpms java-11-openjdk-headless.x86_64 1:11.0.9.10-0.el8_1 @rhel-8-appstream-rpms javapackages-filesystem.noarch 5.3.0-1.module+el8+2447+6f56d9a6 @rhel-8-appstream-rpms
sudo alternatives --config java There are 2 programs which provide 'java'. Selection Command ----------------------------------------------- * 1 java-1.8.0-openjdk.x86_64 (/usr/lib/jvm/java-1.8.0-openjdk-1.8.0.232.b09-0.el8_0.x86_64/jre/bin/java) + 2 java-11-openjdk.x86_64 (/usr/lib/jvm/java-11-openjdk-11.0.9.10-0.el8_0.x86_64/bin/java) Enter to keep the current selection[+], or type selection number: 1
java -version openjdk version "11.0.9" 2020-10-15 LTS OpenJDK Runtime Environment 18.9 (build 11.0.9+10-LTS) OpenJDK 64-Bit Server VM 18.9 (build 11.0.9+10-LTS, mixed mode, sharing)
Chapter 7. Supported integration products AMQ Streams 1.8 supports integration with the following Red Hat products. Red Hat Single Sign-On 7.4 and later Provides OAuth 2.0 authentication and OAuth 2.0 authorization. For information on the functionality these products can introduce to your AMQ Streams deployment, refer to the AMQ Streams 1.8 documentation. Additional resources Red Hat Single Sign-On Supported Configurations

Commands:
E.9. Model Extension Definition Editor The MED Editor is a editor with multiple tabs and is used to create and edit user defined MEDs ( *.mxd files) in the workspace. The MED Editor has 3 sub-editors (Overview, Properties, and Source) which share a common header section. Here are the MED sub-editor tabs: Overview Sub-Editor - this editor is where the general MED information is managed. This information includes the namespace prefix, namespace URI, extended model class, and the description. The Overview sub-editor looks like this: Figure E.25. Overview Tab Properties Sub-Editor - this editor is where the MED extension properties are managed. Each extension property must be associated with a model object type. The Properties sub-editor is divided into 2 sections (Extended Model Objects and Extension Properties) and looks like this: Figure E.26. Properties Tab Source - this tab is a read-only XML source viewer to view the details of your MED. This source viewer is NOT editable. The GUI components on the Overview and Properties sub-editors will be decorated with an error icon when the data in that GUI component has a validation error. Hovering over an error decoration displays a tooltip with the specific error message. Those error message relate to the error messages shown in the common header section. Here is an example of the error decoration: Figure E.27. Text Field With Error The MED sub-editors share a header section. The header is composed of the following: Status Image - an image indicating the most severe validation message (error, warning, or info). If there are no validation messages the model extension image is shown. Title - the title of the sub-editor being shown. Menu - a drop-down menu containing actions for (1) adding to and updating the MED in the registry, and (2) for showing the Model Extension Registry View. Validation Message - this area will display an OK message or an error summary message. When a summary message is shown, the tooltip for that message will enumerate all the messages. Toolbar - contains the same actions as the drop-down menu. Below is an example of the shared header section which includes an error message tooltip. Figure E.28. Shared Header Example

Commands:
Chapter 9. Kafka clients The kafka-clients JAR file contains the Kafka Producer and Consumer APIs together with the Kafka AdminClient API. The Producer API allows applications to send data to a Kafka broker. The Consumer API allows applications to consume data from a Kafka broker. The AdminClient API provides functionality for managing Kafka clusters, including topics, brokers, and other components. 9.1. Adding Kafka clients as a dependency to your Maven project This procedure shows you how to add the AMQ Streams Java clients as a dependency to your Maven project. Prerequisites A Maven project with an existing pom.xml . Procedure Add the Red Hat Maven repository to the <repositories> section of your pom.xml file. Add the clients to the <dependencies> section of your pom.xml file. Build your Maven project.

Commands:
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <!-- ... --> <repositories> <repository> <id>redhat-maven</id> <url>https://maven.repository.redhat.com/ga/</url> </repository> </repositories> <!-- ... --> </project>
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <!-- ... --> <dependencies> <dependency> <groupId>org.apache.kafka</groupId> <artifactId>kafka-clients</artifactId> <version>3.1.0.redhat-00004</version> </dependency> </dependencies> <!-- ... --> </project>