mtpti5iD/redhat-docs_dataset huggingface dataset:
2.9.2. Process Behavior in the Root Control Group Certain blkio and cpu configuration options affect processes (tasks) running in the root cgroup in a different way than those in a subgroup. Consider the following example: Create two subgroups under one root group: /rootgroup/red/ and /rootgroup/blue/ In each subgroup and in the root group, define the cpu.shares configuration option and set it to 1 . In the scenario configured above, one process placed in each group (that is, one task in /rootgroup/tasks , /rootgroup/red/tasks and /rootgroup/blue/tasks ) consumes 33.33% of the CPU: Any other processes placed in subgroups blue and red result in the 33.33% percent of the CPU assigned to that specific subgroup to be split among the multiple processes in that subgroup. However, multiple processes placed in the root group cause the CPU resource to be split per process, rather than per group. For example, if /rootgroup/ contains three processes, /rootgroup/red/ contains one process and /rootgroup/blue/ contains one process, and the cpu.shares option is set to 1 in all groups, the CPU resource is divided as follows: Therefore, it is recommended to move all processes from the root group to a specific subgroup when using the blkio and cpu configuration options which divide an available resource based on a weight or a share (for example, cpu.shares or blkio.weight ). To move all tasks from the root group into a specific subgroup, you can use the following commands:

Commands:
/rootgroup/ process: 33.33% /rootgroup/blue/ process: 33.33% /rootgroup/red/ process: 33.33%
/rootgroup/ processes: 20% + 20% + 20% /rootgroup/blue/ process: 20% /rootgroup/red/ process: 20%
rootgroup]# cat tasks >> red/tasks rootgroup]# echo > tasks
3.2.2.3. Other Ways of Securing SSH Protocol Version Even though the implementation of the SSH protocol supplied with Red Hat Enterprise Linux supports both the SSH-1 and SSH-2 versions of the protocol, only the latter should be used whenever possible. The SSH-2 version contains a number of improvements over the older SSH-1, and the majority of advanced configuration options is only available when using SSH-2. Users are encouraged to make use of SSH-2 in order to maximize the extent to which the SSH protocol protects the authentication and communication for which it is used. The version or versions of the protocol supported by the sshd daemon can be specified using the Protocol configuration directive in the /etc/ssh/sshd_config file. The default setting is 2 . Key Types While the ssh-keygen command generates a pair of SSH-2 RSA keys by default, using the -t option, it can be instructed to generate DSA or ECDSA keys as well. The ECDSA (Elliptic Curve Digital Signature Algorithm) offers better performance at the same symmetric key length. It also generates shorter keys. Non-Default Port By default, the sshd daemon listens on the 22 network port. Changing the port reduces the exposure of the system to attacks based on automated network scanning, thus increasing security through obscurity. The port can be specified using the Port directive in the /etc/ssh/sshd_config configuration file. Note also that the default SELinux policy must be changed to allow for the use of a non-default port. You can do this by modifying the ssh_port_t SELinux type by typing the following command as root : In the above command, replace port_number with the new port number specified using the Port directive. No Root Login Provided that your particular use case does not require the possibility of logging in as the root user, you should consider setting the PermitRootLogin configuration directive to no in the /etc/ssh/sshd_config file. By disabling the possibility of logging in as the root user, the administrator can audit which user runs what privileged command after they log in as regular users and then gain root rights. Important This section draws attention to the most common ways of securing an SSH setup. By no means should this list of suggested measures be considered exhaustive or definitive. Refer to sshd_config(5) for a description of all configuration directives available for modifying the behavior of the sshd daemon and to ssh(1) for an explanation of basic SSH concepts.

Commands:
~]# semanage -a -t ssh_port_t -p tcp port_number
Chapter 1. Prerequisites Red Hat Enterprise Linux (RHEL) 9 To obtain the latest version of Red Hat Enterprise Linux (RHEL) 9, see Download Red Hat Enterprise Linux . For installation instructions, see the Product Documentation for Red Hat Enterprise Linux 9 . An active subscription to Red Hat Two or more virtual CPUs 4 GB or more of RAM Approximately 30 GB of disk space on your test system, which can be broken down as follows: Approximately 10 GB of disk space for the Red Hat Enterprise Linux (RHEL) operating system. Approximately 10 GB of disk space for Docker storage for running three containers. Approximately 10 GB of disk space for Red Hat Quay local storage. Note CEPH or other local storage might require more memory. More information on sizing can be found at Quay 3.x Sizing Guidelines . The following architectures are supported for Red Hat Quay: amd64/x86_64 s390x ppc64le 1.1. Installing Podman This document uses Podman for creating and deploying containers. For more information on Podman and related technologies, see Building, running, and managing Linux containers on Red Hat Enterprise Linux 9 . Important If you do not have Podman installed on your system, the use of equivalent Docker commands might be possible, however this is not recommended. Docker has not been tested with Red Hat Quay 3.12, and will be deprecated in a future release. Podman is recommended for highly available, production quality deployments of Red Hat Quay 3.12. Use the following procedure to install Podman. Procedure Enter the following command to install Podman: USD sudo yum install -y podman Alternatively, you can install the container-tools module, which pulls in the full set of container software packages: USD sudo yum module install -y container-tools

Commands:
sudo yum install -y podman
sudo yum module install -y container-tools
Chapter 3. The Security Audit Logger Red Hat JBoss Data Grid includes a logger to audit security logs for the cache, specifically whether a cache or a cache manager operation was allowed or denied for various operations. The default audit logger is org.infinispan.security.impl.DefaultAuditLogger . This logger outputs audit logs using the available logging framework (for example, JBoss Logging) and provides results at the TRACE level and the AUDIT category. To send the AUDIT category to either a log file, a JMS queue, or a database, use the appropriate log appender. Report a bug 3.1. Configure the Security Audit Logger (Library Mode) Use the following to declaratively configure the audit logger in Red Hat JBoss Data Grid: Use the following to programatically configure the audit logger in JBoss Data Grid: Report a bug

Commands:
<infinispan> <global-security> <authorization audit-logger = "org.infinispan.security.impl.DefaultAuditLogger"> </authorization> </global-security> </infinispan>
GlobalConfigurationBuilder global = new GlobalConfigurationBuilder(); global.security() .authorization() .auditLogger(new DefaultAuditLogger());
7.2. RHBA-2013:1607 - new packages: gcc-libraries New gcc-libraries packages are now available for Red Hat Enterprise Linux 6. The new gcc-libraries packages contain various GCC runtime libraries, such as libatomic and libitm. In Red Hat Enterprise Linux 5.9, libitm was a separate package that included the libitm library. The libitm package is now deprecated and replaced by the gcc-libraries packages. This enhancement update adds the gcc-libraries packages to Red Hat Enterprise Linux 6. (BZ# 906241 ) All users who require gcc-libraries are advised to install these new packages.

Commands:
Chapter 8. Streams for Apache Kafka Console overview The Streams for Apache Kafka Console provides a user interface to facilitate the administration of Kafka clusters, delivering real-time insights for monitoring, managing, and optimizing each cluster from its user interface. Connect a Kafka cluster managed by Streams for Apache Kafka to gain real-time insights and optimize cluster performance from its user interface. The console's homepage displays connected Kafka clusters, allowing you to access detailed information on components such as brokers, topics, partitions, and consumer groups. From the console, you can view the status of a Kafka cluster before navigating to view information on the cluster's brokers and topics, or the consumer groups connected to the Kafka cluster.

Commands:
13.2.28. Managing the SSSD Cache SSSD can define multiple domains of the same type and different types of domain. SSSD maintains a separate database file for each domain, meaning each domain has its own cache. These cache files are stored in the /var/lib/sss/db/ directory. Purging the SSSD Cache As LDAP updates are made to the identity provider for the domains, it can be necessary to clear the cache to reload the new information quickly. The cache purge utility, sss_cache , invalidates records in the SSSD cache for a user, a domain, or a group. Invalidating the current records forces the cache to retrieve the updated records from the identity provider, so changes can be realized quickly. Note This utility is included with SSSD in the sssd package. Most commonly, this is used to clear the cache and update all records: The sss_cache command can also clear all cached entries for a particular domain: If the administrator knows that a specific record (user, group, or netgroup) has been updated, then sss_cache can purge the records for that specific account and leave the rest of the cache intact: Table 13.12. Common sss_cache Options Short Argument Long Argument Description -E --everything Invalidates all cached entries with the exception of sudo rules. -d name --domain name Invalidates cache entries for users, groups, and other entries only within the specified domain. -G --groups Invalidates all group records. If -g is also used, -G takes precedence and -g is ignored. -g name --group name Invalidates the cache entry for the specified group. -N --netgroups Invalidates cache entries for all netgroup cache records. If -n is also used, -N takes precedence and -n is ignored. -n name --netgroup name Invalidates the cache entry for the specified netgroup. -U --users Invalidates cache entries for all user records. If the -u option is also used, -U takes precedence and -u is ignored. -u name --user name Invalidates the cache entry for the specified user. Deleting Domain Cache Files All cache files are named for the domain. For example, for a domain named exampleldap , the cache file is named cache_exampleldap.ldb . Be careful when you delete a cache file. This operation has significant effects: Deleting the cache file deletes all user data, both identification and cached credentials. Consequently, do not delete a cache file unless the system is online and can authenticate with a user name against the domain's servers. Without a credentials cache, offline authentication will fail. If the configuration is changed to reference a different identity provider, SSSD will recognize users from both providers until the cached entries from the original provider time out. It is possible to avoid this by purging the cache, but the better option is to use a different domain name for the new provider. When SSSD is restarted, it creates a new cache file with the new name and the old file is ignored.

Commands:
~]# sss_cache -E
~]# sss_cache -Ed LDAP1
~]# sss_cache -u jsmith
7.129. libwacom 7.129.1. RHEA-2013:0333 - libwacom enhancement update Updated libwacom packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The libwacom packages contain a library that provides access to a tablet model database. The libwacom packages expose the contents of this database to applications, allowing for tablet-specific user interfaces. The libwacom packages allow the GNOME tools to automatically configure screen mappings and calibrations, and provide device-specific configurations. Enhancement BZ#857073 Previously, the Wacom Cintiq 22HD graphics tablet was not supported by the libwacom library. Consequently, this specific type of graphics tablet was not recognized by the system. This update adds the support for Wacom Cintiq 22HD, which can be now used without complications. All users of libwacom are advised to upgrade to these updated packages, which add this enhancement.

Commands:
3.5.7. Computing for Statistical Aggregates Statistical aggregates are used to collect statistics on numerical values where it is important to accumulate new data quickly and in large volume (that is storing only aggregated stream statistics). Statistical aggregates can be used in global variables or as elements in an array. To add value to a statistical aggregate, use the operator <<< value . Example 3.19. stat-aggregates.stp In Example 3.19, "stat-aggregates.stp" , the operator <<< count stores the amount returned by count to the associated value of the corresponding execname() in the reads array. Remember, these values are stored ; they are not added to the associated values of each unique key, nor are they used to replace the current associated values. In a manner of speaking, think of it as having each unique key ( execname() ) having multiple associated values, accumulating with each probe handler run. Note In the context of Example 3.19, "stat-aggregates.stp" , count returns the amount of data written by the returned execname() to the virtual file system. To extract data collected by statistical aggregates, use the syntax format @ extractor ( variable/array index expression ) . extractor can be any of the following integer extractors: count Returns the number of all values stored into the variable/array index expression. Given the sample probe in Example 3.19, "stat-aggregates.stp" , the expression @count(writes[execname()]) will return how many values are stored in each unique key in array writes . sum Returns the sum of all values stored into the variable/array index expression. Again, given sample probe in Example 3.19, "stat-aggregates.stp" , the expression @sum(writes[execname()]) will return the total of all values stored in each unique key in array writes . min Returns the smallest among all the values stored in the variable/array index expression. max Returns the largest among all the values stored in the variable/array index expression. avg Returns the average of all values stored in the variable/array index expression. When using statistical aggregates, you can also build array constructs that use multiple index expressions (to a maximum of 5). This is helpful in capturing additional contextual information during a probe. For example: Example 3.20. Multiple Array Indexes In Example 3.20, "Multiple Array Indexes" , the first probe tracks how many times each process performs a VFS read. What makes this different from earlier examples is that this array associates a performed read to both a process name and its corresponding process ID. The second probe in Example 3.20, "Multiple Array Indexes" demonstrates how to process and print the information collected by the array reads . Note how the foreach statement uses the same number of variables (that is var1 and var2 ) contained in the first instance of the array reads from the first probe.

Commands:
global reads probe vfs.read { reads[execname()] <<< count }
global reads probe vfs.read { reads[execname(),pid()] <<< 1 } probe timer.s(3) { foreach([var1,var2] in reads) printf("%s (%d) : %d \n", var1, var2, @count(reads[var1,var2])) }
7.6. authconfig 7.6.1. RHBA-2013:0486 - authconfig bug fix update Updated authconfig packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The authconfig packages provide a command line utility and a GUI application that can configure a workstation to be a client for certain network user information and authentication schemes, and other user information and authentication related options. Bug Fixes BZ# 862195 Prior to this update, the authconfig utility used old syntax for configuring the idmap mapping in the smb.conf file when started with the "--smbidmapuid" and "--smbidmapgid" command line options. Consequently, Samba 3.6 ignored the configuration. This update adapts authconfig to use the new syntax of the idmap range configuration so that Samba 3.6 can read it. BZ# 874527 Prior to this update, the authconfig utility could write an incomplete sssd.conf file when using the options "--enablesssd" or "--enablesssdauth". As a consequence, the sssd daemon did not start. With this update, authconfig no longer tries to create the sssd.conf file without complete information, and the sssd daemon can now start as expected. All users of authconfig are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 3. Bug fixes 3.1. Extension 'ms-python.python' CANNOT use API proposal: terminalShellIntegration Before this release, installing the latest Python extension (v2024.14.0) would fail with the following error message: "Extension 'ms-python.python' CANNOT use API proposal: terminalShellIntegration". With this release, the issue is fixed Additional resources CRW-7201 3.2. Opening links not possible in the Visual Studio Code - Open Source ("Code - OSS") Before this release, it was not possible to open links in Visual Studio Code - Open Source ("Code - OSS"). With this release, the issue has been fixed. Additional resources CRW-7247

Commands:
8.126. libvisual 8.126.1. RHBA-2014:0840 - libvisual bug fix update Updated libvisual packages that fix one bug are now available for Red Hat Enterprise Linux 6. Libvisual is an abstraction library that comes between applications and audio visualization plug-ins and provides a convenient API to enable the user to draw visualizations easily. Bug Fix BZ# 658064 Previously, due to multilib file conflicts between certain packages in the Optional repository on Red Hat Network, those packages could not have copies for both the primary and secondary architecture installed on the same machine. As a consequence, installation of the packages failed. A patch has been applied to resolve the file conflicts, and the packages can now be installed as expected in the described scenario. Users of libvisual are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 4. Updating Capsule Server Update Capsule Servers to the patch version. Procedure Synchronize the satellite-capsule-6.16-for-rhel-8-x86_64-rpms repository in the Satellite Server. Publish and promote a new version of the content view with which the Capsule is registered. Ensure that the Satellite Maintenance repository is enabled: On Red Hat Enterprise Linux 9: On Red Hat Enterprise Linux 8: Use the health check option to determine if the system is ready for update: Review the results and address any highlighted error conditions before performing the update. Because of the lengthy update time, use a utility such as tmux to suspend and reattach a communication session. You can then check the update progress without staying connected to the command shell continuously. If you lose connection to the command shell where the update command is running, you can see the logged messages in the /var/log/foreman-installer/capsule.log file to check if the process completed successfully. Perform the update: Determine if the system needs a reboot: If the command told you to reboot, then reboot the system:

Commands:
subscription-manager repos --enable satellite-maintenance-6.16-for-rhel-9-x86_64-rpms
subscription-manager repos --enable satellite-maintenance-6.16-for-rhel-8-x86_64-rpms
satellite-maintain update check
satellite-maintain update run
dnf needs-restarting --reboothint
reboot
Chapter 7. Supplemental certification Open supplemental certifications in the following scenarios: First time certification The bare-metal supplemental certification can be automatically created during a different certification process, for example, when you applied for the Red Hat Enterprise Linux System certification. If it was not automatically created, or if you need to apply for the certification at a later date, open a new supplemental certification above the Red Hat OpenShift Container Platform certification. Recertification Open a supplemental certification to update an existing RHOCP bare-metal certification. You may want to recertify your product, for example, to certify the same system on different versions of a Red Hat platform or because your product has received a significant update. You are responsible for initiating these certifications and notifying Red Hat of any material changes to your product.

Commands:
Appendix A. GFS2 Performance Analysis with Performance Co-Pilot Red Hat Enterprise Linux 7 supports Performance Co-Pilot (PCP) with GFS2 performance metrics. This allows you to monitor the performance of a GFS2 file system. This appendix describes the GFS2 performance metrics and how to use them. A.1. Overview of Performance Co-Pilot Performance Co-Pilot (PCP) is a open source toolkit for monitoring, visualizing, recording, and controlling the status, activities and performance of computers, applications and servers. PCP allows the monitoring and management of both real-time data and the logging and retrieval of historical data. Historical data can be used to analyze any patterns with issues by comparing live results over the archived data. PCP is designed with a client-server architecture. The PCP collector service is the Performance Metric Collector Daemon (PMCD), which can be installed and run on a server. Once it is started, PCMD begins collecting performance data from the installed Performance Metric Domain Agents (PMDAs). PMDAs can be individually loaded or unloaded on the system and are controlled by the PMCD on the same host. The GFS2 PMDA, which is part of the default PCP installation, is used. to gather performance metric data of GFS2 file systems in PCP. Table A.1, "PCP Tools" provides a brief list of some PCP tools in the PCP Toolkit that this chapter describes. For information about additional PCP tools, see the PCPIntro (1) man page and the additional PCP man pages. Table A.1. PCP Tools Tool Use pmcd Performance Metric Collector Service: collects the metric data from the PMDA and makes the metric data available for the other components in PCP pmlogger Allows the creation of archive logs of performance metric values which may be played back by other PCP tools pmproxy A protocol proxy for pmcd which allows PCP monitoring clients to connect to one or more instances of pmcd by means of pmproxy pminfo Displays information about performance metrics on the command line pmstore Allows the modification of performance metric values (re-initialize counters or assign new values) pmdumptext Exports performance metric data either live or from performance archives to an ASCII table pmchart Graphical utility that plots performance metric values into charts ( pcp-gui package)

Commands:
3.5.2. Disabling ACPI Soft-Off with chkconfig Management You can use chkconfig management to disable ACPI Soft-Off either by removing the ACPI daemon ( acpid ) from chkconfig management or by turning off acpid . Note This is the preferred method of disabling ACPI Soft-Off. Disable ACPI Soft-Off with chkconfig management at each cluster node as follows: Run either of the following commands: chkconfig --del acpid - This command removes acpid from chkconfig management. - OR - chkconfig --level 345 acpid off - This command turns off acpid . Reboot the node. When the cluster is configured and running, verify that the node turns off immediately when fenced. Note You can fence the node with the fence_node command or Conga .

Commands: