mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 9. User statistics in Red Hat Developer Hub In Red Hat Developer Hub, the licensed-users-info-backend plugin provides statistical information about the logged-in users using the Web UI or REST API endpoints. The licensed-users-info-backend plugin enables administrators to monitor the number of active users on Developer Hub. Using this feature, organizations can compare their actual usage with the number of licenses they have purchased. Additionally, you can share the user metrics with Red Hat for transparency and accurate licensing. The licensed-users-info-backend plugin is enabled by default. This plugin enables a Download User List link at the bottom of the Administration RBAC tab. 9.1. Downloading active users list in Red Hat Developer Hub You can download the list of users in CSV format using the Developer Hub web interface. Prerequisites RBAC plugins ( @janus-idp/backstage-plugin-rbac and @janus-idp/backstage-plugin-rbac-backend ) must be enabled in Red Hat Developer Hub. An administrator role must be assigned. Procedure In Red Hat Developer Hub, navigate to Administration and select the RBAC tab. At the bottom of the RBAC page, click Download User List . Optional: Modify the file name in the Save as field and click Save . To access the downloaded users list, go to the Downloads folder on your local machine and open the CSV file.

Commands:
Chapter 9. Managing Directory Quotas Warning Quota is considered deprecated as of Red Hat Gluster Storage 3.5. Red Hat no longer recommends its use, and does not support Quota in new deployments and existing deployments that upgrade to Red Hat Gluster Storage 3.5.3. Quotas allow you to set limits on the disk space used by a directory. Storage administrators can control the disk space utilization at the directory and volume levels. This is particularly useful in cloud deployments to facilitate the use of utility billing models. 9.1. Enabling and Disabling Quotas To limit disk usage, you need to enable quota usage on a volume by running the following command: This command only enables quota behavior on the volume; it does not set any default disk usage limits. Note On a gluster volume with quota enabled, the CPU and memory consumption accelarates based on various factors. For example, complexity of the file system tree, number of bricks, nodes in the pool, number of quota limits placed across the filesystem, and the frequency of quota traversals across the filesystem. To disable quota behavior on a volume, including any set disk usage limits, run the following command: Important When you disable quotas on Red Hat Gluster Storage 3.1.1 and earlier, all previously configured limits are removed from the volume by a cleanup process, quota-remove-xattr.sh . If you re-enable quotas while the cleanup process is still running, the extended attributes that enable quotas may be removed by the cleanup process. This has negative effects on quota accounting.

Commands:
gluster volume quota VOLNAME enable
gluster volume quota VOLNAME disable
Chapter 4. Selecting a system-wide archive Red Hat build of OpenJDK version If you have multiple versions of Red Hat build of OpenJDK installed with the archive on RHEL, you can select a specific Red Hat build of OpenJDK version to use system-wide. Prerequisites Know the locations of the Red Hat build of OpenJDK versions installed using the archive. Procedure To specify the Red Hat build of OpenJDK version to use for a single session: Configure JAVA_HOME with the path to the Red Hat build of OpenJDK version you want used system-wide. USD export JAVA_HOME=/opt/jdk/jdk-11.0.9 Add USDJAVA_HOME/bin to the PATH environment variable. USD export PATH="USDJAVA_HOME/bin:USDPATH" To specify the Red Hat build of OpenJDK version to use permanently for a single user, add these commands into ~/.bashrc : To specify the Red Hat build of OpenJDK version to use permanently for all users, add these commands into /etc/bashrc : Note If you do not want to redefine JAVA_HOME , add only the PATH command to bashrc , specifying the path to the Java binary. For example, export PATH="/opt/jdk/jdk-11.0.3/bin:USDPATH" . Additional resources Be aware of the exact meaning of JAVA_HOME . For more information, see Changes/Decouple system java setting from java command setting .

Commands:
export JAVA_HOME=/opt/jdk/jdk-11.0.9 export PATH="USDJAVA_HOME/bin:USDPATH"
export JAVA_HOME=/opt/jdk/jdk-11.0.9 export PATH="USDJAVA_HOME/bin:USDPATH"
Chapter 13. Tuning the performance of a Samba server Learn what settings can improve the performance of Samba in certain situations, and which settings can have a negative performance impact. Parts of this section were adopted from the Performance Tuning documentation published in the Samba Wiki. License: CC BY 4.0 . Authors and contributors: See the history tab on the Wiki page. Prerequisites Samba is set up as a file or print server See Using Samba as a server . 13.1. Setting the SMB protocol version Each new SMB version adds features and improves the performance of the protocol. The recent Windows and Windows Server operating systems always supports the latest protocol version. If Samba also uses the latest protocol version, Windows clients connecting to Samba benefit from the performance improvements. In Samba, the default value of the server max protocol is set to the latest supported stable SMB protocol version. Note To always have the latest stable SMB protocol version enabled, do not set the server max protocol parameter. If you set the parameter manually, you will need to modify the setting with each new version of the SMB protocol, to have the latest protocol version enabled. The following procedure explains how to use the default value in the server max protocol parameter. Procedure Remove the server max protocol parameter from the [global] section in the /etc/samba/smb.conf file. Reload the Samba configuration 13.2. Tuning shares with directories that contain a large number of files Linux supports case-sensitive file names. For this reason, Samba needs to scan directories for uppercase and lowercase file names when searching or accessing a file. You can configure a share to create new files only in lowercase or uppercase, which improves the performance. Prerequisites Samba is configured as a file server Procedure Rename all files on the share to lowercase. Note Using the settings in this procedure, files with names other than in lowercase will no longer be displayed. Set the following parameters in the share's section: For details about the parameters, see their descriptions in the smb.conf(5) man page on your system. Verify the /etc/samba/smb.conf file: Reload the Samba configuration: After you applied these settings, the names of all newly created files on this share use lowercase. Because of these settings, Samba no longer needs to scan the directory for uppercase and lowercase, which improves the performance. 13.3. Settings that can have a negative performance impact By default, the kernel in Red Hat Enterprise Linux is tuned for high network performance. For example, the kernel uses an auto-tuning mechanism for buffer sizes. Setting the socket options parameter in the /etc/samba/smb.conf file overrides these kernel settings. As a result, setting this parameter decreases the Samba network performance in most cases. To use the optimized settings from the Kernel, remove the socket options parameter from the [global] section in the /etc/samba/smb.conf .

Commands:
smbcontrol all reload-config
case sensitive = true default case = lower preserve case = no short preserve case = no
testparm
smbcontrol all reload-config
Chapter 6. Device Drivers 6.1. New drivers Network drivers Maxlinear Ethernet GPY Driver ( mxl-gpy ) Realtek 802.11ax wireless 8852A driver ( rtw89_8852a ) Realtek 802.11ax wireless 8852AE driver ( rtw89_8852ae ) Graphics drivers and miscellaneous drivers MHI Host Interface ( mhi ) Modem Host Interface (MHI) PCI controller driver ( mhi_pci_generic ) IDXD driver dsa_bus_type driver ( idxd_bus ) AMD PassThru DMA driver ( ptdma ) Cirrus Logic DSP Support ( cs_dsp ) DRM DisplayPort helper ( drm_dp_helper ) DRM Buddy Allocator ( drm_buddy ) DRM SHMEM memory-management helpers ( drm_shmem_helper ) DRM driver using bochs dispi interface ( bochs ) Intel(R) PMT Class driver ( pmt_class ) Intel(R) PMT Crashlog driver ( pmt_crashlog ) Intel(R) PMT Telemetry driver ( pmt_telemetry ) Intel(R) speed select interface driver ( isst_if_common ) Intel(R) speed select interface mailbox driver ( isst_if_mbox_msr ) Intel(R) speed select interface pci mailbox driver ( isst_if_mbox_pci ) Intel(R) speed select interface mmio driver ( isst_if_mmio ) Intel(R) Software Defined Silicon driver ( intel_sdsi ) Intel(R) Extended Capabilities auxiliary bus driver ( intel_vsec ) ISH ISHTP eclite client opregion driver ( ishtp_eclite ) Serial multi instantiate pseudo device driver ( serial-multi-instantiate ) AMD(R) SPI Master Controller Driver ( spi-amd ) 6.2. Updated drivers Network drivers VMware vmxnet3 virtual NIC driver ( vmxnet3 ) has been updated to version 1.7.0.0-k. Intel(R) PRO/1000 Network Driver ( e1000e ) has been updated to version 4.18.0-425.3.1. Intel(R) Ethernet Switch Host Interface Driver ( fm10k ) has been updated to version 4.18.0-425.3.1. Intel(R) Ethernet Connection XL710 Network Driver ( i40e ) has been updated to version 4.18.0-425.3.1. Intel(R) Ethernet Adaptive Virtual Function Network Driver ( iavf ) has been updated to version 4.18.0-425.3.1. Intel(R) Gigabit Ethernet Network Driver ( igb ) has been updated to version 4.18.0-425.3.1. Intel(R) Gigabit Virtual Function Network Driver ( igbvf ) has been updated to version 4.18.0-425.3.1. Intel(R) 2.5G Ethernet Linux Driver ( igc ) has been updated to version 4.18.0-425.3.1. Intel(R) 10 Gigabit PCI Express Network Driver ( ixgbe ) has been updated to version 4.18.0-425.3.1. Intel(R) 10 Gigabit Virtual Function Network Driver ( ixgbevf ) has been updated to version 4.18.0-425.3.1. Mellanox 5th generation network adapters (ConnectX series) core driver ( mlx5_core ) has been updated to version 4.18.0-425.3.1. Storage drivers Emulex LightPulse Fibre Channel SCSI driver ( lpfc ) has been updated to version 14.0.0.15. MPI3 Storage Controller Device Driver ( mpi3mr ) has been updated to version 8.0.0.69.0. LSI MPT Fusion SAS 3.0 Device Driver ( mpt3sas ) has been updated to version 42.100.00.00. QLogic Fibre Channel HBA Driver ( qla2xxx ) has been updated to version 10.02.07.400-k. Driver for Microchip Smart Family Controller ( smartpqi ) has been updated to version 2.1.18-045. Graphics and miscellaneous driver updates Standalone drm driver for the VMware SVGA device ( vmwgfx ) has been updated to version 2.20.0.0.

Commands:
Chapter 5. Asset execution options with Red Hat Decision Manager After you build and deploy your Red Hat Decision Manager project to KIE Server or other environment, you can execute the deployed assets for testing or for runtime consumption. You can also execute assets locally in addition to or instead of executing them after deployment. The following options are the main methods for Red Hat Decision Manager asset execution: Table 5.1. Asset execution options Execution option Description Documentation Execution in KIE Server If you deployed Red Hat Decision Manager project assets to KIE Server, you can use the KIE Server REST API or Java client API to execute and interact with the deployed assets. You can also use Business Central or the headless Process Automation Manager controller outside of Business Central to manage the configurations and KIE containers in the KIE Server instances associated with your deployed assets. Interacting with Red Hat Decision Manager using KIE APIs Execution in an embedded Java application If you deployed Red Hat Decision Manager project assets in your own Java virtual machine (JVM) environment, microservice, or application server, you can use custom APIs or application interactions with core KIE APIs (not KIE Server APIs) to execute assets in the embedded engine. KIE Public API Execution in a local environment for extended testing As part of your development cycle, you can execute assets locally to ensure that the assets you have created in Red Hat Decision Manager function as intended. You can use local execution in addition to or instead of executing assets after deployment. "Executing rules" in Designing a decision service using DRL rules

Commands:
33.2. Installation Method Figure 33.2. Installation Method The Installation Method screen allows you to choose whether to perform a new installation or an upgrade. If you choose upgrade, the Partition Information and Package Selection options are disabled. They are not supported for kickstart upgrades. Choose the type of kickstart installation or upgrade from the following options: DVD - Choose this option to install or upgrade from the Red Hat Enterprise Linux DVD. NFS - Choose this option to install or upgrade from an NFS shared directory. In the text field for the NFS server, enter a fully-qualified domain name or IP address. For the NFS directory, enter the name of the NFS directory that contains the variant directory of the installation tree. For example, if the NFS server contains the directory /mirrors/redhat/i386/Server/ , enter /mirrors/redhat/i386/ for the NFS directory. FTP - Choose this option to install or upgrade from an FTP server. In the FTP server text field, enter a fully-qualified domain name or IP address. For the FTP directory, enter the name of the FTP directory that contains the variant directory. For example, if the FTP server contains the directory /mirrors/redhat/i386/Server/ , enter /mirrors/redhat/i386/Server/ for the FTP directory. If the FTP server requires a username and password, specify them as well. HTTP - Choose this option to install or upgrade from an HTTP server. In the text field for the HTTP server, enter the fully-qualified domain name or IP address. For the HTTP directory, enter the name of the HTTP directory that contains the variant directory. For example, if the HTTP server contains the directory /mirrors/redhat/i386/Server/ , enter /mirrors/redhat/i386/Server/ for the HTTP directory. Hard Drive - Choose this option to install or upgrade from a hard drive. Hard drive installations require the use of ISO images. Be sure to verify that the ISO images are intact before you start the installation. To verify them, use an md5sum program as well as the linux mediacheck boot option as discussed in Section 28.6.1, "Verifying Boot Media" . Enter the hard drive partition that contains the ISO images (for example, /dev/hda1 ) in the Hard Drive Partition text box. Enter the directory that contains the ISO images in the Hard Drive Directory text box.

Commands:
Chapter 20. configuration This chapter describes the commands under the configuration command. 20.1. configuration show Display configuration details Usage: Table 20.1. Optional Arguments Value Summary -h, --help Show this help message and exit --mask Attempt to mask passwords (default) --unmask Show password in clear text Table 20.2. Output Formatters Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated Table 20.3. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 20.4. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 20.5. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack configuration show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] [--mask | --unmask]
Appendix A. Tips for Developers Every good programming textbook covers problems with memory allocation and the performance of specific functions. As you develop your software, be aware of issues that might increase power consumption on the systems on which the software runs. Although these considerations do not affect every line of code, you can optimize your code in areas which are frequent bottlenecks for performance. Some techniques that are often problematic include: using threads. unnecessary CPU wake-ups and not using wake-ups efficiently. If you must wake up, do everything at once (race to idle) and as quickly as possible. using [f]sync() unnecessarily. unnecessary active polling or using short, regular timeouts. (React to events instead). not using wake-ups efficiently. inefficient disk access. Use large buffers to avoid frequent disk access. Write one large block at a time. inefficient use of timers. Group timers across applications (or even across systems) if possible. excessive I/O, power consumption, or memory usage (including memory leaks) performing unnecessary computation. The following sections examine some of these areas in greater detail. A.1. Using Threads It is widely believed that using threads makes applications perform better and faster, but this is not true in every case. Python Python uses the Global Lock Interpreter [1] , so threading is profitable only for larger I/O operations. Unladen-swallow [2] is a faster implementation of Python with which you might be able to optimize your code. Perl Perl threads were originally created for applications running on systems without forking (such as systems with 32-bit Windows operating systems). In Perl threads, the data is copied for every single thread (Copy On Write). Data is not shared by default, because users should be able to define the level of data sharing. For data sharing the threads::shared module has to be included. However, data is not only then copied (Copy On Write), but the module also creates tied variables for the data, which takes even more time and is even slower. [3] C C threads share the same memory, each thread has its own stack, and the kernel does not have to create new file descriptors and allocate new memory space. C can really use the support of more CPUs for more threads. Therefore, to maximize the performance of your threads, use a low-level language like C or C++. If you use a scripting language, consider writing a C binding. Use profilers to identify poorly performing parts of your code. [4] [1] http://docs.python.org/c-api/init.html#thread-state-and-the-global-interpreter-lock [2] http://code.google.com/p/unladen-swallow/ [3] http://www.perlmonks.org/?node_id=288022 [4] http://people.redhat.com/drepper/lt2009.pdf

Commands:
9.2. Before Setting a Quota on a Directory There are several things you should keep in mind when you set a quota on a directory. When specifying a directory to limit with the gluster volume quota command, the directory's path is relative to the Red Hat Gluster Storage volume mount point, not the root directory of the server or client on which the volume is mounted. That is, if the Red Hat Gluster Storage volume is mounted at /mnt/glusterfs and you want to place a limit on the /mnt/glusterfs/dir directory, use /dir as the path when you run the gluster volume quota command, like so: Ensure that at least one brick is available per replica set when you run the gluster volume quota command. A brick is available if a Y appears in the Online column of gluster volume status command output, like so:

Commands:
gluster volume quota VOLNAME limit-usage /dir hard_limit
gluster volume status VOLNAME Status of volume: VOLNAME Gluster process Port Online Pid ------------------------------------------------------------ Brick arch:/export/rep1 24010 Y 18474 Brick arch:/export/rep2 24011 Y 18479 NFS Server on localhost 38467 Y 18486 Self-heal Daemon on localhost N/A Y 18491
A.2. The dmsetup Command The dmsetup command is a command line wrapper for communication with the Device Mapper. For general system information about LVM devices, you may find the info , ls , status , and deps options of the dmsetup command to be useful, as described in the following subsections. For information about additional options and capabilities of the dmsetup command, see the dmsetup (8) man page. A.2.1. The dmsetup info Command The dmsetup info device command provides summary information about Device Mapper devices. If you do not specify a device name, the output is information about all of the currently configured Device Mapper devices. If you specify a device, then this command yields information for that device only. The dmsetup info command provides information in the following categories: Name The name of the device. An LVM device is expressed as the volume group name and the logical volume name separated by a hyphen. A hyphen in the original name is translated to two hyphens. During standard LVM operations, you should not use the name of an LVM device in this format to specify an LVM device directly, but instead you should use the vg / lv alternative. State Possible device states are SUSPENDED , ACTIVE , and READ-ONLY . The dmsetup suspend command sets a device state to SUSPENDED . When a device is suspended, all I/O operations to that device stop. The dmsetup resume command restores a device state to ACTIVE . Read Ahead The number of data blocks that the system reads ahead for any open file on which read operations are ongoing. By default, the kernel chooses a suitable value automatically. You can change this value with the --readahead option of the dmsetup command. Tables present Possible states for this category are LIVE and INACTIVE . An INACTIVE state indicates that a table has been loaded which will be swapped in when a dmsetup resume command restores a device state to ACTIVE , at which point the table's state becomes LIVE . For information, see the dmsetup man page. Open count The open reference count indicates how many times the device is opened. A mount command opens a device. Event number The current number of events received. Issuing a dmsetup wait n command allows the user to wait for the n'th event, blocking the call until it is received. Major, minor Major and minor device number Number of targets The number of fragments that make up a device. For example, a linear device spanning 3 disks would have 3 targets. A linear device composed of the beginning and end of a disk, but not the middle would have 2 targets. UUID UUID of the device. The following example shows partial output for the dmsetup info command.

Commands:
dmsetup info Name: testgfsvg-testgfslv1 State: ACTIVE Read Ahead: 256 Tables present: LIVE Open count: 0 Event number: 0 Major, minor: 253, 2 Number of targets: 2 UUID: LVM-K528WUGQgPadNXYcFrrf9LnPlUMswgkCkpgPIgYzSvigM7SfeWCypddNSWtNzc2N Name: VolGroup00-LogVol00 State: ACTIVE Read Ahead: 256 Tables present: LIVE Open count: 1 Event number: 0 Major, minor: 253, 0 Number of targets: 1 UUID: LVM-tOcS1kqFV9drb0X1Vr8sxeYP0tqcrpdegyqj5lZxe45JMGlmvtqLmbLpBcenh2L3