mtpti5iD/redhat-docs_dataset huggingface dataset:
4.12. RHEA-2012:0812 - new package: libqb A new libqb package is now available for Red Hat Enterprise Linux 6. The libqb package provides a library with the primary purpose of providing high performance client server reusable features, such as high performance logging, tracing, inter-process communication, and polling. This enhancement update adds the libqb package to Red Hat Enterprise Linux 6. This package is introduced as a dependency of the pacemaker package, and is considered a Technology Preview in Red Hat Enterprise Linux 6.3. (BZ# 782240 ) All users who require libqb are advised to install this new package.

Commands:
Chapter 4. Glossary Common terms and definitions for Red Hat's Trusted Profile Analyzer service. Exhort The backend endpoint of Trusted Profile Analyzer where all the API requests get sent, to retrieve the necessary data to analyze, including package dependencies and vulnerabilities. The Red Hat Dependency Analytics (RHDA) integrated development environment (IDE) plug-in uses this endpoint to generate vulnerability reports within the IDE framework. Software Bill of Materials Also known by the acronym, SBOM. A manifest of dependent software packages needed for a particular application. Single Pane of Glass Also known by the acronym, SPOG. The RESTful application programming interface (API) for the Trusted Profile Analyzer web dashboard, and notifications. Vulnerability Exploitability eXchange Also known by the acronym, VEX. A security advisory issued by a software provider for specific vulnerabilities within a product. Common Vulnerability and Exposures Also known by the acronym, CVE. A CVE indicates a product's exposure to attacks and malicious activities by giving it a score 1-10, where 1 is the lowest exposure level and 10 is the highest exposure level. Common Vulnerability Score System Also known by the acronym CVSS. The CVSS calculates CVE scores according to specific formulas when trying to calculate CVEs in a broad range of products and networks.

Commands:
Chapter 1. About hardware accelerators Specialized hardware accelerators play a key role in the emerging generative artificial intelligence and machine learning (AI/ML) industry. Specifically, hardware accelerators are essential to the training and serving of large language and other foundational models that power this new technology. Data scientists, data engineers, ML engineers, and developers can take advantage of the specialized hardware acceleration for data-intensive transformations and model development and serving. Much of that ecosystem is open source, with a number of contributing partners and open source foundations. Red Hat OpenShift Container Platform provides support for cards and peripheral hardware that add processing units that comprise hardware accelerators: Graphical processing units (GPUs) Neural processing units (NPUs) Application-specific integrated circuits (ASICs) Data processing units (DPUs) Specialized hardware accelerators provide a rich set of benefits for AI/ML development: One platform for all A collaborative environment for developers, data engineers, data scientists, and DevOps Extended capabilities with Operators Operators allow for bringing AI/ML capabilities to OpenShift Container Platform Hybrid-cloud support On-premise support for model development, delivery, and deployment Support for AI/ML workloads Model testing, iteration, integration, promotion, and serving into production as services Red Hat provides an optimized platform to enable these specialized hardware accelerators in Red Hat Enterprise Linux (RHEL) and OpenShift Container Platform platforms at the Linux (kernel and userspace) and Kubernetes layers. To do this, Red Hat combines the proven capabilities of Red Hat OpenShift AI and Red Hat OpenShift Container Platform in a single enterprise-ready AI application platform. Hardware Operators use the operating framework of a Kubernetes cluster to enable the required accelerator resources. You can also deploy the provided device plugin manually or as a daemon set. This plugin registers the GPU in the cluster. Certain specialized hardware accelerators are designed to work within disconnected environments where a secure environment must be maintained for development and testing. 1.1. Hardware accelerators Red Hat OpenShift Container Platform enables the following hardware accelerators: NVIDIA GPU AMD Instinct(R) GPU Intel(R) Gaudi(R) Additional resources Introduction to Red Hat OpenShift AI NVIDIA GPU Operator on Red Hat OpenShift Container Platform AMD Instinct Accelerators Intel Gaudi Al Accelerators

Commands:
5.341. upstart 5.341.1. RHBA-2012:0863 - upstart bug fix and enhancement update An updated upstart package that fixes two bug and adds two enhancements is now available for Red Hat Enterprise Linux 6. The upstart package contains an event-based replacement for the /sbin/init daemon that starts tasks and services during boot, stops them during shut down, and supervises them while the system is running. Bug Fixes BZ# 771736 Previously, the PACKAGE_BUGREPORT variable pointed to a Ubuntu mailing list. The mailing list was therefore presented in multiple manual pages, which was unwanted. With this update, the value of the PACKAGE_BUGREPORT variable has been modified to "https://launchpad.net/upstart/+bugs", and users are now directed to that website rather than to the Ubuntu mailing list. BZ# 798551 versions of upstart did not mount the proc and sys file systems. This was ensured by initscripts, which could, under certain circumstances, lead to race condition problems. With this update, upstart is used to mount the proc and sys file systems before launching anything else. Enhancements BZ# 663594 Files with the ".conf" suffix located in the /etc/init/ directory are not considered as configuration files. As a consequence, such files are not protected during a package update and can be overwritten by new files. This update adds support for "override" files that contain user-specified settings. Now, it is possible to alter parameters provided by the aforementioned ".conf" files by creating a corresponding file with the ".override" suffix. BZ# 735427 Previously, the initctl scripts returned error messages that did not tell users how to run the particular command correctly to get the required output. This update adds a new stanza, "usage", that can be used to provide users with detailed information on how to run the particular command correctly if the input has been incorrect. All users of upstart are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
2.9.2. Performance Tuning With GFS2 It is usually possible to alter the way in which a troublesome application stores its data in order to gain a considerable performance advantage. A typical example of a troublesome application is an email server. These are often laid out with a spool directory containing files for each user ( mbox ), or with a directory for each user containing a file for each message ( maildir ). When requests arrive over IMAP, the ideal arrangement is to give each user an affinity to a particular node. That way their requests to view and delete email messages will tend to be served from the cache on that one node. Obviously if that node fails, then the session can be restarted on a different node. When mail arrives by means of SMTP, then again the individual nodes can be set up so as to pass a certain user's mail to a particular node by default. If the default node is not up, then the message can be saved directly into the user's mail spool by the receiving node. Again this design is intended to keep particular sets of files cached on just one node in the normal case, but to allow direct access in the case of node failure. This setup allows the best use of GFS2's page cache and also makes failures transparent to the application, whether imap or smtp . Backup is often another tricky area. Again, if it is possible it is greatly preferable to back up the working set of each node directly from the node which is caching that particular set of inodes. If you have a backup script which runs at a regular point in time, and that seems to coincide with a spike in the response time of an application running on GFS2, then there is a good chance that the cluster may not be making the most efficient use of the page cache. Obviously, if you are in the (enviable) position of being able to stop the application in order to perform a backup, then this will not be a problem. On the other hand, if a backup is run from just one node, then after it has completed a large portion of the file system will be cached on that node, with a performance penalty for subsequent accesses from other nodes. This can be mitigated to a certain extent by dropping the VFS page cache on the backup node after the backup has completed with following command: However this is not as good a solution as taking care to ensure the working set on each node is either shared, mostly read only across the cluster, or accessed largely from a single node.

Commands:
echo -n 3 >/proc/sys/vm/drop_caches
Chapter 5. The sepolicy Suite The sepolicy utility provides a suite of features to query the installed SELinux policy. These features are either new or were previously provided by separate utilities, such as sepolgen or setrans . The suite allows you to generate transition reports, man pages, or even new policy modules, thus giving users easier access and better understanding of the SELinux policy. The policycoreutils-devel package provides sepolicy . Enter the following command as the root user to install sepolicy : The sepolicy suite provides the following features that are invoked as command-line parameters: Table 5.1. The sepolicy Features Feature Description booleans Query the SELinux Policy to see description of Booleans communicate Query the SELinux policy to see if domains can communicate with each other generate Generate an SELinux policy module template gui Graphical User Interface for SELinux Policy interface List SELinux Policy interfaces manpage Generate SELinux man pages network Query SELinux policy network information transition Query SELinux policy and generate a process transition report 5.1. The sepolicy Python Bindings In versions of Red Hat Enterprise Linux, the setools package included the sesearch and seinfo utilities. The sesearch utility is used for searching rules in a SELinux policy while the seinfo utility allows you to query various other components in the policy. In Red Hat Enterprise Linux 7, Python bindings for sesearch and seinfo have been added so that you can use the functionality of these utilities through the sepolicy suite. See the example below:

Commands:
~]# yum install policycoreutils-devel
> python >>> import sepolicy >>> sepolicy.info(sepolicy.ATTRIBUTE) Returns a dictionary of all information about SELinux Attributes >>>sepolicy.search([sepolicy.ALLOW]) Returns a dictionary of all allow rules in the policy.
10.2. About Host Entry Configuration Properties A host entry can contain information about the host that is outside its system configuration, such as its physical location, its MAC address, and keys and certificates. This information can be set when the host entry is created if it is created manually; otherwise, most of that information needs to be added to the host entry after the host is enrolled in the domain. Table 10.1. Host Configuration Properties UI Field Command-Line Option Description Description --desc= description A description of the host. Locality --locality= locality The geographic location of the host. Location --location= location The physical location of the host, such as its data center rack. Platform --platform= string The host hardware or architecture. Operating system --os= string The operating system and version for the host. MAC address --macaddress= address The MAC address for the host. This is a multi-valued attribute. The MAC address is used by the NIS plug-in to create a NIS ethers map for the host. SSH public keys --sshpubkey= string The full SSH public key for the host. This is a multi-valued attribute, so multiple keys can be set. Principal name (not editable) --principalname= principal The Kerberos principal name for the host. This defaults to the hostname during the client installation, unless a different principal is explicitly set in the -p . This can be changed using the command-line tools, but cannot be changed in the UI. Set One-Time Password --password= string Sets a password for the host which can be used in bulk enrollment. - --random Generates a random password to be used in bulk enrollment. - --certificate= string A certificate blob for the host. - --updatedns An attribute switch which sets whether the host can dynamically update its DNS entries if its IP address changes.

Commands:
5.6. Online Data Relocation You can move data while the system is in use with the pvmove command. The pvmove command breaks up the data to be moved into sections and creates a temporary mirror to move each section. For more information on the operation of the pvmove command, see the pvmove (8) man page. Note In order to perform a pvmove operation in a cluster, you should ensure that the cmirror package is installed and the cmirrord service is running. The following command moves all allocated space off the physical volume /dev/sdc1 to other free physical volumes in the volume group: The following command moves just the extents of the logical volume MyLV . Since the pvmove command can take a long time to execute, you may want to run the command in the background to avoid display of progress updates in the foreground. The following command moves all extents allocated to the physical volume /dev/sdc1 over to /dev/sdf1 in the background. The following command reports the progress of the move as a percentage at five second intervals.

Commands:
pvmove /dev/sdc1
pvmove -n MyLV /dev/sdc1
pvmove -b /dev/sdc1 /dev/sdf1
pvmove -i5 /dev/sdd1
2.8. Active Directory Authentication Using Kerberos (GSSAPI) When using Red Hat JBoss Data Grid with Microsoft Active Directory, data security can be enabled via Kerberos authentication. To configure Kerberos authentication for Microsoft Active Directory, use the following procedure. Procedure 2.6. Configure Kerberos Authentication for Active Directory (Library Mode) Configure JBoss EAP server to authenticate itself to Kerberos. This can be done by configuring a dedicated security domain, for example: The security domain for authentication must be configured correctly for JBoss EAP, an application must have a valid Kerberos ticket. To initiate the Kerberos ticket, you must reference another security domain using . This points to the standard Kerberos login module described in Step 3. The security domain authentication configuration described in the step points to the following standard Kerberos login module: Report a bug

Commands:
<security-domain name="ldap-service" cache-type="default"> <authentication> <login-module code="Kerberos" flag="required"> <module-option name="storeKey" value="true"/> <module-option name="useKeyTab" value="true"/> <module-option name="refreshKrb5Config" value="true"/> <module-option name="principal" value="ldap/localhost@INFINISPAN.ORG"/> <module-option name="keyTab" value="USD{basedir}/keytab/ldap.keytab"/> <module-option name="doNotPrompt" value="true"/> </login-module> </authentication> </security-domain>
<module-option name="usernamePasswordDomain" value="krb-admin"/>
<security-domain name="ispn-admin" cache-type="default"> <authentication> <login-module code="SPNEGO" flag="requisite"> <module-option name="password-stacking" value="useFirstPass"/> <module-option name="serverSecurityDomain" value="ldap-service"/> <module-option name="usernamePasswordDomain" value="krb-admin"/> </login-module> <login-module code="AdvancedAdLdap" flag="required"> <module-option name="password-stacking" value="useFirstPass"/> <module-option name="bindAuthentication" value="GSSAPI"/> <module-option name="jaasSecurityDomain" value="ldap-service"/> <module-option name="java.naming.provider.url" value="ldap://localhost:389"/> <module-option name="baseCtxDN" value="ou=People,dc=infinispan,dc=org"/> <module-option name="baseFilter" value="(krb5PrincipalName={0})"/> <module-option name="rolesCtxDN" value="ou=Roles,dc=infinispan,dc=org"/> <module-option name="roleFilter" value="(member={1})"/> <module-option name="roleAttributeID" value="cn"/> </login-module> </authentication> </security-domain>
<security-domain name="krb-admin" cache-type="default"> <authentication> <login-module code="Kerberos" flag="required"> <module-option name="useKeyTab" value="true"/> <module-option name="principal" value="admin@INFINISPAN.ORG"/> <module-option name="keyTab" value="USD{basedir}/keytab/admin.keytab"/> </login-module> </authentication> </security-domain>
C.9. DistributionManager org.infinispan.distribution.DistributionManagerImpl The DistributionManager component handles the distribution of content across a cluster. Note The DistrubutionManager component is only available in clustered mode. Table C.16. Operations Name Description Signature isAffectedByRehash Determines whether a given key is affected by an ongoing rehash. boolean isAffectedByRehash(Object p0) isLocatedLocally Indicates whether a given key is local to this instance of the cache. Only works with String keys. boolean isLocatedLocally(String p0) locateKey Locates an object in a cluster. Only works with String keys. List locateKey(String p0) 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
7.26. clustermon 7.26.1. RHBA-2015:1413 - clustermon bug fix update Updated clustermon packages that fix one bug are now available for Red Hat Enterprise Linux 6. The clustermon packages are used for remote cluster management. The modclusterd service provides an abstraction of cluster status used by the Conga architecture and by the Simple Network Management (SNMP) and Common Information Model (CIM) modules of clustermon. Bug Fix BZ# 1111249 , BZ# 1114622 The internal ricci API has been extended with an ability to temporarily stop a clustered resource, which was used to resolve the BZ#1111249 enhancement request in the luci packages, documented in the RHBA-2015:20054 erratum. Users of clustermon are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Storage overview MicroShift supports multiple types of storage, both for on-premise and cloud providers. You can manage container storage for persistent and non-persistent data in a Red Hat build of MicroShift cluster. 1.1. Storage types MicroShift storage is broadly classified into two categories, namely ephemeral storage and persistent storage. 1.1.1. Ephemeral storage Pods and containers are ephemeral or transient in nature and designed for stateless applications. Ephemeral storage allows administrators and developers to better manage the local storage for some of their operations. To read details about ephemeral storage, click Understanding ephemeral storage . 1.1.2. Persistent storage Stateful applications deployed in containers require persistent storage. MicroShift uses a pre-provisioned storage framework called persistent volumes (PV) to allow cluster administrators to provision persistent storage. The data inside these volumes can exist beyond the lifecycle of an individual pod. Developers can use persistent volume claims (PVCs) to request storage requirements. For persistent storage details, read Understanding persistent storage . 1.1.3. Dynamic storage provisioning Using dynamic provisioning allows you to create storage volumes on-demand, eliminating the need for pre-provisioned storage. For more information about how dynamic provisioning works in Red Hat build of MicroShift, read Dynamic provisioning .

Commands:
6.15. Using Different Applets for Different SCP Versions In Certificate System, the following parameter in the /var/lib/ instance_name /tps/conf/CS.cfg file specifies which applet should be loaded for all Secure Channel Protocol (SCP) versions for each token operation: However, you can also set individual applets for specific SCP versions, by adding the following parameter: Certificate System supports setting individual protocol versions for the following operations: format enroll pinReset Example 6.3. Setting Protocol Versions for Enrollment Operations To configure a specific applet for SCP03 and a different applet for all other protocols when performing enrollment operations for the userKey token: Edit the /var/lib/ instance_name /tps/conf/CS.cfg file: Set the op.enroll.userKey.update.applet.requiredVersion parameter to specify the applet used by default. For example: Set the op.enroll.userKey.update.applet.requiredVersion.prot.3 parameter to configure the applet Certificate System uses for the SCP03 protocol. For example: Restart Certificate System: For details about enabling SCP03 for Giesecke & Devrient (G&D) Smart Cafe 6 smart cards in a TKS, see Section 6.12, "Setting Up New Key Sets" .

Commands:
op. operation . token_type .update.applet.requiredVersion= version
op. operation . token_type .update.applet.requiredVersion.prot. protocol_version = version
op.enroll.userKey.update.applet.requiredVersion=1.4.58768072
op.enroll.userKey.update.applet.requiredVersion.prot. 3 =1.5.558cdcff
pki-server restart instance_name
6.2.2. Where Users Access Shared Data When sharing data among users, it is a common practice to have a central server (or group of servers) that make certain directories available to other machines on the network. This way data is stored in one place; synchronizing data between multiple machines is not necessary. Before taking this approach, you must first determine what systems are to access the centrally-stored data. As you do this, take note of the operating systems used by the systems. This information has a bearing on your ability to implement such an approach, as your storage server must be capable of serving its data to each of the operating systems in use at your organization. Unfortunately, once data is shared between multiple computers on a network, the potential for conflicts in file ownership can arise. 6.2.2.1. Global Ownership Issues There are benefits if data is stored centrally and is accessed by multiple computers over a network. However, assume for a moment that each of those computers has a locally-maintained list of user accounts. What if the list of users on each of these systems are not consistent with the list of users on the central server? Even worse, what if the list of users on each of these systems are not even consistent with each other? Much of this depends on how users and access permissions are implemented on each system, but in some cases it is possible that user A on one system may actually be known as user B on another system. This becomes a real problem when data is shared between these systems, as data that user A is allowed to access from one system can also be read by user B from another system. For this reason, many organizations use some sort of central user database. This assures that there are no overlaps between user lists on different systems.

Commands:
A. Revision History Revision History Revision 2.0-2 2022-03-23 Navinya Shende Updates examples with Hydra API Revision 2.0-1.400 2013-12-18 Rudiger Landmann Rebuild with publican 4.0.0 Revision 2.0-1 Fri Nov 1 2013 Zac Dover Publish for new site Revision 0.0-0 Tue Sep 24 2013 Misty Stanley-Jones Converted existing document to Docbook

Commands:
10.2. Memory Policy Elements The memory_policy element contains the following elements: Table 10.2. Memory policy elements Element Type Description Properties overcommit percent= complex The percentage of host memory allowed in use before no more virtual machines can start on a host. Virtual machines can use more than the available host memory due to memory sharing under KSM. Recommended values include 100 (None), 150 (Server Load) and 200 (Desktop Load). transparent_hugepages complex Define the enabled status of Transparent Hugepages. The status is either true or false. Check capabilities feature set to ensure your version supports transparent hugepages .

Commands: