mtpti5iD/redhat-docs_dataset huggingface dataset:
E.2.15. /proc/loadavg This file provides a look at the load average in regard to both the CPU and IO over time, as well as additional data used by uptime and other commands. A sample /proc/loadavg file looks similar to the following: The first three columns measure CPU and IO utilization of the last one, five, and 15 minute periods. The fourth column shows the number of currently running processes and the total number of processes. The last column displays the last process ID used. In addition, load average also refers to the number of processes ready to run (i.e. in the run queue, waiting for a CPU share.

Commands:
0.20 0.18 0.12 1/80 11206
Chapter 33. Database connection Business Central provides a dedicated UserGroupCallback implementation for database server with Red Hat Decision Manager to enable the user task service. The user task service helps in retrieving information on users and groups (roles) directly from databases. You can configure the following database UserGroupCallback implementation properties: Table 33.1. Database UserGroupCallback properties Property Description db.ds.jndi.name JNDI name of the data source used for connections db.user.query Verifies the user existence db.user.roles.query Collects the groups for a given user db.roles.query Verifies the group existence 33.1. Database UserGroupCallback implementation In database UserGroupCallback implementation, you must create the required database. You can use this implementation by configuring the respective database properties in one of the following ways: Programmatically: Build a properties object with the respective DBUserGroupCallbackImpl properties and create DBUserGroupCallbackImpl using the same properties object as its parameter. For example: Declaratively: Create the jbpm.usergroup.callback.properties file in the root of your application or specify the file location as a system property. For example: -Djbpm.usergroup.callback.properties=FILE_LOCATION_ON_CLASSPATH Ensure that you register the database callback when starting the user task server. For example: Additional resources Roles and users

Commands:
import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.DS_JNDI_NAME; import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.PRINCIPAL_QUERY; import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.ROLES_QUERY; import static org.jbpm.services.task.identity.DBUserGroupCallbackImpl.USER_ROLES_QUERY; props = new Properties(); props.setProperty(DS_JNDI_NAME, "jdbc/jbpm-ds"); props.setProperty(PRINCIPAL_QUERY, "select userId from Users where userId = ?"); props.setProperty(ROLES_QUERY, "select groupId from UserGroups where groupId = ?"); props.setProperty(USER_ROLES_QUERY, "select groupId from UserGroups where userId = ?"); callback = new DBUserGroupCallbackImpl(props);
System.setProperty("jbpm.usergroup.callback.properties", "/jbpm.usergroup.callback.db.properties"); callback = new DBUserGroupCallbackImpl(true); db.ds.jndi.name = jdbc/jbpm-ds db.user.query = select userId from Users where userId = ? db.roles.query = select groupId from UserGroups where groupId = ? db.user.roles.query = select groupId from UserGroups where userId = ?
Chapter 1. Introduction Migration Toolkit for Runtimes product will be End of Life on September 30th, 2024 All customers using this product should start their transition to Migration Toolkit for Applications . Migration Toolkit for Applications is fully backwards compatible with all features and rulesets available in Migration Toolkit for Runtimes and will be maintained in the long term. 1.1. About the MTR plugin for IntelliJ IDEA You can migrate and modernize applications by using the Migration Toolkit for Runtimes (MTR) plugin for IntelliJ IDEA. The MTR plugin analyzes your projects using customizable rulesets, marks issues in the source code, provides guidance to fix the issues, and offers automatic code replacement, if possible. The plugin supports both the Community Edition and the Ultimate version of IntelliJ IDEA. 1.2. About the Migration Toolkit for Runtimes What is the Migration Toolkit for Runtimes? The Migration Toolkit for Runtimes (MTR) is an extensible and customizable rule-based tool that simplifies the migration and modernization of Java applications. MTR examines application artifacts, including project source directories and application archives, and then produces an HTML report highlighting areas needing changes. MTR supports many migration paths, including the following examples: Upgrading to the latest release of Red Hat JBoss Enterprise Application Platform Migrating from Oracle WebLogic or IBM WebSphere Application Server to Red Hat JBoss Enterprise Application Platform Containerizing applications and making them cloud-ready Migrating from Java Spring Boot to Quarkus Updating from Oracle JDK to OpenJDK Upgrading from OpenJDK 8 to OpenJDK 11 Upgrading from OpenJDK 11 to OpenJDK 17 Upgrading from OpenJDK 17 to OpenJDK 21 Migrating EAP Java applications to Azure Migrating Spring Boot Java applications to Azure For more information about use cases and migration paths, see the MTR for developers web page. How does the Migration Toolkit for Runtimes simplify migration? The Migration Toolkit for Runtimes looks for common resources and known trouble spots when migrating applications. It provides a high-level view of the technologies used by the application. MTR generates a detailed report evaluating a migration or modernization path. This report can help you to estimate the effort required for large-scale projects and to reduce the work involved. How do I learn more? See the Introduction to the Migration Toolkit for Runtimes to learn more about the features, supported configurations, system requirements, and available tools in the Migration Toolkit for Runtimes.

Commands:
function::probefunc Name function::probefunc - Return the probe point's function name, if known Synopsis Arguments None Description This function returns the name of the function being probed based on the current address, as computed by symname( addr ) or usymname( uaddr ) depending on probe context (whether the probe is a user probe or a kernel probe). Please note this function's behaviour differs between SystemTap 2.0 and earlier versions. Prior to 2.0, probefunc obtained the function name from the probe point string as returned by pp , and used the current address as a fallback. Consider using ppfunc instead.

Commands:
probefunc:string()
Chapter 1. Shenandoah garbage collector Shenandoah is the low pause time garbage collector (GC) that reduces GC pause times by performing more garbage collection work concurrently with the running Java program. Concurrent Mark Sweep garbage collector (CMS) and G1, default garbage collector for Red Hat build of OpenJDK 21 perform concurrent marking of live objects. Shenandoah adds concurrent compaction. Shenandoah also reduces GC pause times by compacting objects concurrently with running Java threads. Pause times with Shenandoah are independent of the heap size, meaning you will have consistent pause time whether your heap is 200 MB or 200 GB. Shenandoah is an algorithm for applications which require responsiveness and predictable short pauses. Additional resources For more information about the Shenandoah garbage collector, see Shenandoah GC in the Oracle OpenJDK documentation.

Commands:
function::qsq_print Name function::qsq_print - Prints a line of statistics for the given queue Synopsis Arguments qname queue name Description This function prints a line containing the following statistics for the given queue the queue name, the average rate of requests per second, the average wait queue length, the average time on the wait queue, the average time to service a request, the percentage of time the wait queue was used, and the percentage of time request was being serviced.

Commands:
qsq_print(qname:string)
25.10. Additional Resources For more information on how to configure the rsyslog daemon and how to locate, view, and monitor log files, see the resources listed below. Installed Documentation rsyslogd (8) - The manual page for the rsyslogd daemon documents its usage. rsyslog.conf (5) - The manual page named rsyslog.conf documents available configuration options. logrotate (8) - The manual page for the logrotate utility explains in greater detail how to configure and use it. Online Documentation The rsyslog home page offers additional documentation, configuration examples, and video tutorials. Make sure to consult the documents relevant to the version you are using: rsyslog version 5 documentation on the rsyslog home page - The default version of rsyslog in Red Hat Enterprise Linux 6 is version 5. rsyslog version 7 documentation on the rsyslog home page - Version 7 of rsyslog is available for Red Hat Enterprise Linux 6 in the rsyslog7 package. Description of queues on the rsyslog Home Page - General information on various types of message queues and their usage. See Also Chapter 4, Gaining Privileges documents how to gain administrative privileges by using the su and sudo commands.

Commands:
Appendix A. Component Versions This appendix provides a list of key components and their versions in the Red Hat Enterprise Linux 7.5 release. Table A.1. Component Versions Component Version kernel 3.10.0-862 kernel-alt 4.14.0-49 QLogic qla2xxx driver 9.00.00.00.07.5-k1 QLogic qla4xxx driver 5.04.00.00.07.02-k0 Emulex lpfc driver 0:11.4.0.4 iSCSI initiator utils ( iscsi-initiator-utils ) 6.2.0.874-7 DM-Multipath ( device-mapper-multipath ) 0.4.9-119 LVM ( lvm2 ) 2.02.177-4 qemu-kvm [a] 1.5.3-156 qemu-kvm-ma [b] 2.10.0-21 [a] The qemu-kvm packages provide KVM virtualization on AMD64 and Intel 64 systems. [b] The qemu-kvm-ma packages provide KVM virtualization on IBM POWER8, IBM POWER9, and IBM Z. Note that KVM virtualization on IBM POWER9 and IBM Z also requires using the kernel-alt packages.

Commands:
12.7. Parameterizable Native Queries In some situations the teiid_rel:native-query property and native procedures accept parameterizable strings that can positionally reference IN parameters. A parameter reference has the form USD integer , for example, USD1. Note that one-based indexing is used and that only IN parameters may be referenced. USD integer is reserved, but may be escaped with another USD, for example, USDUSD1. The value will be bound as a prepared value or a literal in a source specific manner. The native query must return a result set that matches the expectation of the calling procedure. For example, the native query "select c from g where c1 = USD1 and c2 = 'USDUSD1'" results in a JDBC source query of "select c from g where c1 = ? and c2 = 'USD1'", where ? will be replaced with the actual value bound to parameter 1.

Commands:
4.153. libvorbis 4.153.1. RHSA-2012:0136 - Important: libvorbis security update Updated libvorbis packages that fix one security issue are now available for Red Hat Enterprise Linux 4, 5, and 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. The libvorbis packages contain runtime libraries for use in programs that support Ogg Vorbis. Ogg Vorbis is a fully open, non-proprietary, patent-and royalty-free, general-purpose compressed audio format. Security Fix CVE-2012-0444 A heap-based buffer overflow flaw was found in the way the libvorbis library parsed Ogg Vorbis media files. If a specially-crafted Ogg Vorbis media file was opened by an application using libvorbis, it could cause the application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. Users of libvorbis should upgrade to these updated packages, which contain a backported patch to correct this issue. The desktop must be restarted (log out, then log back in) for this update to take effect.

Commands:
Chapter 4. General Updates In-place upgrade from Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7 An in-place upgrade offers a way of upgrading a system to a new major release of Red Hat Enterprise Linux by replacing the existing operating system. To perform an in-place upgrade, use the Preupgrade Assistant , a utility that checks the system for upgrade issues before running the actual upgrade, and that also provides additional scripts for the Red Hat Upgrade Tool . When you have solved all the problems reported by the Preupgrade Assistant , use the Red Hat Upgrade Tool to upgrade the system. For details regarding procedures and supported scenarios, see https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Migration_Planning_Guide/chap-Red_Hat_Enterprise_Linux-Migration_Planning_Guide-Upgrading.html and https://access.redhat.com/solutions/637583 . Note that the Preupgrade Assistant and the Red Hat Upgrade Tool are available in the Red Hat Enterprise Linux 6 Extras channel, see https://access.redhat.com/support/policy/updates/extras . (BZ#1432080) The setup package now provides a way to override unpredictable environment settings The setup package now provides and sources the sh.local and csh.local files for overrides of environment variables from the /etc/profile.d directory, which is sourced last. Previously, an undefined order could result in unpredictable environment settings, especially when multiple scripts changed the same environment variable. (BZ# 1344007 )

Commands:
5.2. General Properties of Fencing Devices Any cluster node can fence any other cluster node with any fence device, regardless of whether the fence resource is started or stopped. Whether the resource is started controls only the recurring monitor for the device, not whether it can be used, with the following exceptions: You can disable a fencing device by running the pcs stonith disable stonith_id command. This will prevent any node from using that device To prevent a specific node from using a fencing device, you can configure location constraints for the fencing resource with the pcs constraint location ... avoids command. Configuring stonith-enabled=false will disable fencing altogether. Note, however, that Red Hat does not support clusters when fencing is disabled, as it is not suitable for a production environment. Table 5.1, "General Properties of Fencing Devices" describes the general properties you can set for fencing devices. Refer to Section 5.3, "Displaying Device-Specific Fencing Options" for information on fencing properties you can set for specific fencing devices. Note For information on more advanced fencing configuration properties, see Section 5.8, "Additional Fencing Configuration Options" Table 5.1. General Properties of Fencing Devices Field Type Default Description pcmk_host_map string A mapping of host names to port numbers for devices that do not support host names. For example: node1:1;node2:2,3 tells the cluster to use port 1 for node1 and ports 2 and 3 for node2 pcmk_host_list string A list of machines controlled by this device (Optional unless pcmk_host_check=static-list ). pcmk_host_check string dynamic-list How to determine which machines are controlled by the device. Allowed values: dynamic-list (query the device), static-list (check the pcmk_host_list attribute), none (assume every device can fence every machine)

Commands:
6.2.2. Preparing a Driver Disc You can create a driver update disc on CD or DVD. 6.2.2.1. Creating a driver update disc on CD or DVD Important CD/DVD Creator is part of the GNOME desktop. If you use a different Linux desktop, or a different operating system altogether, you will need to use another piece of software to create the CD or DVD. The steps will be generally similar. Make sure that the software that you choose can create CDs or DVDs from image files. While this is true of most CD and DVD burning software, exceptions exist. Look for a button or menu entry labeled burn from image or similar. If your software lacks this feature, or you do not select it, the resulting disc will hold only the image file itself, instead of the contents of the image file. Use the desktop file manager to locate the ISO image file of the driver disc, supplied to you by Red Hat or your hardware vendor. Figure 6.2. A typical .iso file displayed in a file manager window Right-click on this file and choose Write to disc . You will see a window similar to the following: Figure 6.3. CD/DVD Creator's Write to Disc dialog Click the Write button. If a blank disc is not already in the drive, CD/DVD Creator will prompt you to insert one. After you burn a driver update disc CD or DVD, verify that the disc was created successfully by inserting it into your system and browsing to it using the file manager. You should see a single file named rhdd3 and a directory named rpms : Figure 6.4. Contents of a typical driver update disc on CD or DVD If you see only a single file ending in .iso , then you have not created the disc correctly and should try again. Ensure that you choose an option similar to burn from image if you use a Linux desktop other than GNOME or if you use a different operating system. Refer to Section 6.3.2, "Let the Installer Prompt You for a Driver Update" and Section 6.3.3, "Use a Boot Option to Specify a Driver Update Disk" to learn how to use the driver update disc during installation.

Commands:
19.2.2. Mail Delivery Agent A Mail Delivery Agent ( MDA ) is invoked by the MTA to file incoming email in the proper user's mailbox. In many cases, the MDA is actually a Local Delivery Agent ( LDA ), such as mail or Procmail. Any program that actually handles a message for delivery to the point where it can be read by an email client application can be considered an MDA. For this reason, some MTAs (such as Sendmail and Postfix) can fill the role of an MDA when they append new email messages to a local user's mail spool file. In general, MDAs do not transport messages between systems nor do they provide a user interface; MDAs distribute and sort messages on the local machine for an email client application to access.

Commands:
Chapter 4. The Supplementary repository The Supplementary repository includes proprietary-licensed packages that are not included in the open source Red Hat Enterprise Linux repositories. Software packages in the Supplementary repository are not supported, nor are the ABIs guaranteed. Issues arising from packages belonging to the Supplementary repository are not supported. For more information, see the Support policy of the optional and supplementary channels in Red Hat Enterprise Linux . The following table lists all the packages in the Supplementary repository along with their license. Package License dptfxtract Intel java-1.8.0-ibm IBM Binary Code License java-1.8.0-ibm-demo IBM Binary Code License java-1.8.0-ibm-devel IBM Binary Code License java-1.8.0-ibm-headless IBM Binary Code License java-1.8.0-ibm-jdbc IBM Binary Code License java-1.8.0-ibm-plugin IBM Binary Code License java-1.8.0-ibm-src IBM Binary Code License java-1.8.0-ibm-webstart IBM Binary Code License

Commands:
24.4.3. Using the findmnt Command The findmnt command allows you to display a list of currently mounted file systems. To do so, type the following at a shell prompt: findmnt For each listed file system, the findmnt command displays the target mount point ( TARGET ), source device ( SOURCE ), file system type ( FSTYPE ), and relevant mount options ( OPTIONS ). For example: By default, findmnt lists file systems in a tree-like format. To display the information as an ordinary list, add the -l command-line option: findmnt -l For instance: You can also choose to list only file systems of a particular type. To do so, add the -t command-line option followed by a file system type: findmnt -t type For example, to list all ext4 file systems, type: For a complete list of available command-line options, see the findmnt (8) manual page.

Commands:
~]USD findmnt TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/vg_kvm-lv_root ext4 rw,relatime,sec |-/proc /proc proc rw,relatime | |-/proc/bus/usb /proc/bus/usb usbfs rw,relatime | `-/proc/sys/fs/binfmt_misc binfmt_m rw,relatime |-/sys /sys sysfs rw,relatime,sec |-/selinux selinuxf rw,relatime |-/dev udev devtmpfs rw,relatime,sec | `-/dev udev devtmpfs rw,relatime,sec | |-/dev/pts devpts devpts rw,relatime,sec | `-/dev/shm tmpfs tmpfs rw,relatime,sec |-/boot /dev/vda1 ext4 rw,relatime,sec |-/var/lib/nfs/rpc_pipefs sunrpc rpc_pipe rw,relatime |-/misc /etc/auto.misc autofs rw,relatime,fd= `-/net -hosts autofs rw,relatime,fd= [output truncated]
~]USD findmnt -l TARGET SOURCE FSTYPE OPTIONS /proc /proc proc rw,relatime /sys /sys sysfs rw,relatime,seclabe /dev udev devtmpfs rw,relatime,seclabe /dev/pts devpts devpts rw,relatime,seclabe /dev/shm tmpfs tmpfs rw,relatime,seclabe / /dev/mapper/vg_kvm-lv_root ext4 rw,relatime,seclabe /selinux selinuxf rw,relatime /dev udev devtmpfs rw,relatime,seclabe /proc/bus/usb /proc/bus/usb usbfs rw,relatime /boot /dev/vda1 ext4 rw,relatime,seclabe /proc/sys/fs/binfmt_misc binfmt_m rw,relatime /var/lib/nfs/rpc_pipefs sunrpc rpc_pipe rw,relatime /misc /etc/auto.misc autofs rw,relatime,fd=7,pg /net -hosts autofs rw,relatime,fd=13,p [output truncated]
~]USD findmnt -t ext4 TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/vg_kvm-lv_root ext4 rw,relatime,seclabel,barrier=1,data=ord /boot /dev/vda1 ext4 rw,relatime,seclabel,barrier=1,data=ord
Chapter 116. KafkaUserScramSha512ClientAuthentication schema reference Used in: KafkaUserSpec The type property is a discriminator that distinguishes use of the KafkaUserScramSha512ClientAuthentication type from KafkaUserTlsClientAuthentication , KafkaUserTlsExternalClientAuthentication . It must have the value scram-sha-512 for the type KafkaUserScramSha512ClientAuthentication . Property Property type Description type string Must be scram-sha-512 . password Password Specify the password for the user. If not set, a new password is generated by the User Operator.

Commands:
Chapter 2. Accessing the web console The OpenShift Container Platform web console is a user interface accessible from a web browser. Developers can use the web console to visualize, browse, and manage the contents of projects. 2.1. Prerequisites JavaScript must be enabled to use the web console. For the best experience, use a web browser that supports WebSockets . Review the OpenShift Container Platform 4.x Tested Integrations page before you create the supporting infrastructure for your cluster. 2.2. Understanding and accessing the web console The web console runs as a pod on the master. The static assets required to run the web console are served by the pod. Once OpenShift Container Platform is successfully installed using openshift-install create cluster , find the URL for the web console and login credentials for your installed cluster in the CLI output of the installation program. For example: Example output INFO Install complete! INFO Run 'export KUBECONFIG=<your working directory>/auth/kubeconfig' to manage the cluster with 'oc', the OpenShift CLI. INFO The cluster is ready when 'oc login -u kubeadmin -p <provided>' succeeds (wait a few minutes). INFO Access the OpenShift web-console here: https://console-openshift-console.apps.demo1.openshift4-beta-abcorp.com INFO Login to the console with user: kubeadmin, password: <provided> Use those details to log in and access the web console. For existing clusters that you did not install, you can use oc whoami --show-console to see the web console URL.

Commands:
INFO Install complete! INFO Run 'export KUBECONFIG=<your working directory>/auth/kubeconfig' to manage the cluster with 'oc', the OpenShift CLI. INFO The cluster is ready when 'oc login -u kubeadmin -p <provided>' succeeds (wait a few minutes). INFO Access the OpenShift web-console here: https://console-openshift-console.apps.demo1.openshift4-beta-abcorp.com INFO Login to the console with user: kubeadmin, password: <provided>