mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 18. Object Storage (swift) Parameters Parameter Description SwiftAccountWorkers Number of workers for Swift account service. The default value is 0 . SwiftCeilometerIgnoreProjects Comma-separated list of project names to ignore. The default value is ['service'] . SwiftCeilometerPipelineEnabled Set to False to disable the object storage proxy ceilometer pipeline. The default value is False . SwiftContainerSharderEnabled Set to True to enable Swift container sharder service. The default value is False . SwiftContainerWorkers Number of workers for Swift account service. The default value is 0 . SwiftCorsAllowedOrigin Indicate whether this resource may be shared with the domain received in the request "origin" header. SwiftEncryptionEnabled Set to True to enable data-at-rest encryption in Swift. The default value is False . SwiftHashSuffix A random string to be used as a salt when hashing to determine mappings in the ring. SwiftMinPartHours The minimum time (in hours) before a partition in a ring can be moved following a rebalance. The default value is 1 . SwiftMountCheck Check if the devices are mounted to prevent accidentally writing to the root device. The default value is False . SwiftObjectWorkers Number of workers for Swift account service. The default value is 0 . SwiftPartPower Partition power to use when building object storage rings. The default value is 10 . SwiftPassword The password for the object storage service account. SwiftProxyNodeTimeout Timeout for requests going from swift-proxy to account, container, and object services. The default value is 60 . SwiftRawDisks Additional raw devices to use for the object storage backend. For example: {sdb: {}} SwiftReplicas Number of replicas to use in the object storage rings. The default value is 3 . SwiftRingBuild Whether to manage object storage rings or not. The default value is True . SwiftRingGetTempurl A temporary Swift URL to download rings from. SwiftRingPutTempurl A temporary Swift URL to upload rings to. SwiftUseLocalDir Use a local directory for object storage services when building rings. The default value is True . SwiftWorkers Number of workers for object storage service. Note that more workers creates a larger number of processes on systems, which results in excess memory consumption. It is recommended to choose a suitable non-default value on systems with high CPU core counts. 0 sets to the OpenStack internal default, which is equal to the number of CPU cores on the node. The default value is 0 .

Commands:
Chapter 14. Typing emoji characters You can type emoji characters using several different methods in GNOME, depending on the type of the application. 14.1. Typing emoji characters in GTK applications This procedure inserts an emoji character in an application that uses the GTK graphical toolkit, such as in native GNOME applications. Prerequisites Make sure that the application is built on the GTK toolkit. Procedure Open a GTK application. Make sure that a text field is active. Press Ctrl + . . The emoji selection menu opens. Browse the emoji characters or type a keyword that identifies the emoji character that you want to insert, such as smile . For the full list of keywords associated with emoji characters, see the Other Keywords column on the Emoji List page. Click the selected character, or navigate to it using the cursor keys and press Enter . Verification Check that the intended emoji character now appears at your cursor. 14.2. Typing emoji characters in any applications This procedure inserts an emoji character in any application, regardless of the graphical toolkit that the application uses. Procedure Open an application. Make sure that a text field is active. Press Ctrl + Shift + e . The underscored letter e appears at your cursor. Type a keyword that identifies the emoji character that you want to insert, such as smile . For the full list of keywords associated with emoji characters, see the Other Keywords column on the Emoji List page. Repeatedly press Space to browse the emoji characters that match your keyword. Confirm the selected emoji character by pressing Enter . Verification Check that the intended emoji character now appears at your cursor.

Commands:
Appendix A. Using your subscription Apicurio Registry is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing your account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading ZIP and TAR files To access ZIP or TAR files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat Integration entries in the Integration and Automation category. Select the desired Apicurio Registry product. The Software Downloads page opens. Click the Download link for your component. Revised on 2024-10-14 11:17:07 UTC

Commands:
Chapter 3. Getting Started This chapter describes procedures for initial setup of GFS and contains the following sections: Section 3.1, "Prerequisite Tasks" Section 3.2, "Initial Setup Tasks" 3.1. Prerequisite Tasks Before setting up Red Hat GFS, make sure that you have noted the key characteristics of the GFS nodes (refer to Section 1.4, "Before Setting Up GFS" ) and have loaded the GFS modules into each GFS node.Also, make sure that the clocks on the GFS nodes are synchronized. It is recommended that you use the Network Time Protocol (NTP) software provided with your Red Hat Enterprise Linux distribution. In addition, if you are using GNBD multipath, make sure that you understand GNBD multipath considerations. For information on GNBD multipath, see the document Using GNBD with Global Filesystem . Note The system clocks in GFS nodes must be within a few minutes of each other to prevent unnecessary inode time-stamp updating. Unnecessary inode time-stamp updating severely impacts cluster performance.

Commands:
5.35. cpio 5.35.1. RHBA-2012:1414 - cpio bug fix update Updated cpio packages that fix one bug are now available for Red Hat Enterprise Linux 6. The cpio packages provide the GNU cpio utility for creating and extracting archives, or copying files from one place to another. Bug Fix BZ# 866467 Previously, the cpio command was unable to split file names longer than 155 bytes into two parts during the archiving operation. Consequently, cpio could terminate unexpectedly with a segmentation fault. This bug has been fixed and cpio now handles long file names without any crashes. Users of cpio are advised to upgrade to these updated packages, which fix this bug. 5.35.2. RHBA-2012:0444 - cpio bug fix update An updated cpio package that fixes one bug is now available for Red Hat Enterprise Linux 6. The cpio package provides the GNU cpio file archiver utility. GNU cpio can be used to copy and extract files into or from cpio and Tar archives. Bug Fix BZ# 746209 Prior to this update,the options --to-stdout and --no-absolute-filenames were not listed in the cpio (1) manual page. This update includes the missing options and corrects several misprints. All users of cpio are advised to upgrade to this updated package, which fixes this bug.

Commands:
16. Supportability and Maintenance 16.1. firstaidkit System Recovery Tool Red Hat Enterprise Linux 6 includes the new firstaidkit system recovery tool. By automating common recovery processes, firstaidkit provides an interactive environment to assists in the troubleshooting and recovery of a system that boots incorrectly. Additionally, system administrators are able to create custom automated recovery processes using the firstaidkit plugin infrastructure. Important firstaidkit is considered a Technology Preview in Red Hat Enterprise Linux 6. 16.2. Bug Reporting 16.2.1. Installation Crash Reporting Red Hat Enterprise Linux 6 features enhanced installation crash reporting in the installer. Refer to Section 2.4, "Installation Crash Reporting" 16.3. Automated Bug Reporting Tool Red Hat Enterprise Linux 6 features the new Automated Bug Reporting Tool (ABRT). ABRT logs details of software crashes on a local system, and provides interfaces (both graphical and command line based) to instantly open a ticket in the Red Hat Bugzilla bug tracking website . Figure 12. Automated Bug Reporting Tool

Commands:
Chapter 6. Directory Services 6.1. Directory Services The Red Hat Virtualization platform relies on directory services for user authentication and authorization. Interactions with all Manager interfaces, including the VM Portal, Administration Portal, and REST API are limited to authenticated, authorized users. Virtual machines within the Red Hat Virtualization environment can use the same directory services to provide authentication and authorization, however they must be configured to do so. The currently supported providers of directory services for use with the Red Hat Virtualization Manager are Identity Management (IdM), Red Hat Directory Server 9 (RHDS), Active Directory (AD), and OpenLDAP. The Red Hat Virtualization Manager interfaces with the directory server for: Portal logins (User, Power User, Administrator, REST API). Queries to display user information. Adding the Manager to a domain. Authentication is the verification and identification of a party who generated some data, and of the integrity of the generated data. A principal is the party whose identity is verified. The verifier is the party who demands assurance of the principal's identity. In the case of Red Hat Virtualization, the Manager is the verifier and a user is a principal. Data integrity is the assurance that the data received is the same as the data generated by the principal. Confidentiality and authorization are closely related to authentication. Confidentiality protects data from disclosure to those not intended to receive it. Strong authentication methods can optionally provide confidentiality. Authorization determines whether a principal is allowed to perform an operation. Red Hat Virtualization uses directory services to associate users with roles and provide authorization accordingly. Authorization is usually performed after the principal has been authenticated, and may be based on information local or remote to the verifier. During installation, a local, internal domain is automatically configured for administration of the Red Hat Virtualization environment. After the installation is complete, more domains can be added.

Commands:
11.16. Example DDL Metadata

Commands:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?> <vdb name="twitter" version="1"> <description>Shows how to call Web Services</description> <property name="UseConnectorMetadata" value="cached" /> <model name="twitter"> <source name="twitter" translator-name="rest" connection-jndi-name="java:/twitterDS"/> </model> <model name="twitterview" type="VIRTUAL"> <metadata type="DDL"><![CDATA[ CREATE VIRTUAL PROCEDURE getTweets(query varchar) RETURNS (created_on varchar(25), from_user varchar(25), to_user varchar(25), profile_image_url varchar(25), source varchar(25), text varchar(140)) AS select tweet.* from (call twitter.invokeHTTP(action => 'GET', endpoint =>querystring('',query as "q"))) w, XMLTABLE('results' passing JSONTOXML('myxml', w.result) columns created_on string PATH 'created_at', from_user string PATH 'from_user', to_user string PATH 'to_user', profile_image_url string PATH 'profile_image_url', source string PATH 'source', text string PATH 'text') tweet; CREATE VIEW Tweet AS select * FROM twitterview.getTweets; ]]> </metadata> </model> <translator name="rest" type="ws"> <property name="DefaultBinding" value="HTTP"/> <property name="DefaultServiceMode" value="MESSAGE"/> </translator> </vdb>
4.4.3. Synchronizing Quotas GFS stores all quota information in its own internal file on disk. A GFS node does not update this quota file for every file-system write; rather, it updates the quota file once every 60 seconds. This is necessary to avoid contention among nodes writing to the quota file, which would cause a slowdown in performance. As a user or group approaches their quota limit, GFS dynamically reduces the time between its quota-file updates to prevent the limit from being exceeded. The normal time period between quota synchronizations is a tunable parameter, quota_quantum , and can be changed using the gfs_tool command. By default, the time period is 60 seconds. Also, the quota_quantum parameter must be set on each node and each time the file system is mounted. (Changes to the quota_quantum parameter are not persistent across unmounts.) You can use the gfs_quota sync command to synchronize the quota information from a node to the on-disk quota file between the automatic updates performed by GFS. Usage Synchronizing Quota Information MountPoint Specifies the GFS file system to which the actions apply. Tuning the Time Between Synchronizations MountPoint Specifies the GFS file system to which the actions apply. Seconds Specifies the new time period between regular quota-file synchronizations by GFS. Smaller values may increase contention and slow down performance. Examples This example synchronizes the quota information from the node it is run on to file system /gfs . This example changes the default time period between regular quota-file updates to one hour (3600 seconds) for file system /gfs on a single node.

Commands:
gfs_quota sync -f MountPoint
gfs_tool settune MountPoint quota_quantum Seconds
gfs_quota sync -f /gfs
gfs_tool settune /gfs quota_quantum 3600
8.36. environment-modules 8.36.1. RHBA-2013:0844 - environment-modules bug fix update Updated environment-modules packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The environment-modules packages provide for the dynamic modification of a user's environment using modulefiles. Each modulefile contains the information needed to configure the shell for an application. Once the package is initialized, the environment can be modified on a per-module basis using the module command which interprets modulefiles. Bug Fixes BZ#918540 When updating the environment-modules package, changes to the /usr/share/Modules/init/.modulespath config file were being silently replaced by upgrades. The file is now set marked as %config(noreplace) in the spec file, thus it is preserved between updates. BZ#929007 The environment scripts of csh and tcsh used the "test" command without specifying the PATH variable. That could have possibly resulted in an unexpected behavior as a user binary called "test" could have been run instead. With this update, the "test" binary is called by its full path. Misbehavior caused by calling a random test binary is no longer possible. BZ# 953198 When updating the environment-modules package, changes to environment scripts in /etc/profile.d were not preserved. With this update, those scripts have been marked as configuration scripts, thus they are preserved between updates. All users of environment-modules are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 1. Configuring accounts for RHEL AI There are a few accounts you need to set up before interacting with RHEL AI. Creating a Red Hat account You can create a Red Hat account by registering on the Red Hat website. You can follow the procedure in Register for a Red Hat account . Creating a Red Hat registry account Before you can download models from the Red Hat registry, you need to create a registry account and login using the CLI. You can view your account username and password by selecting the Regenerate Token button on the webpage. You can create a Red Hat registry account by selecting the New Service Account button on the Registry Service Accounts page. There are several ways you can log into your registry account via the CLI. Follow the procedure in Red Hat Container Registry authentication to login on your machine. Configuring Red Hat Insights for hybrid cloud deployments Red Hat Insights is an offering that gives you visibility to the environments you are deploying. This platform can also help identify operational and vulnerability risks in your system. For more information about Red Hat Insights, see Red Hat Insights data and application security . You can create a Red Hat Insights account using an activation key and organization parameters by following the procedure in Viewing an activation key . You can then configure your account on your machine by running the following command: USD rhc connect --organization <org id> --activation-key <created key> To run RHEL AI in a disconnected environment, or opt out of Red Hat Insights, run the following commands: USD sudo mkdir -p /etc/ilab USD sudo touch /etc/ilab/insights-opt-out You can also enable persistent credentials and stay logged in to the registry by running the following commands: USD sudo podman login registry.redhat.io Then add the auth.json file to the the /etc/ostree/ USD cp run/containers/0/auth.json /etc/ostree/ This allows you to stay logged into the Red Hat registry after upgrading Red Hat Enterprise Linux AI

Commands:
rhc connect --organization <org id> --activation-key <created key>
sudo mkdir -p /etc/ilab sudo touch /etc/ilab/insights-opt-out
sudo podman login registry.redhat.io
cp run/containers/0/auth.json /etc/ostree/
7.175. pcsc-lite 7.175.1. RHSA-2013:0525 - Moderate: pcsc-lite security and bug fix update Updated pcsc-lite packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. PC/SC Lite provides a Windows SCard compatible interface for communicating with smart cards, smart card readers, and other security tokens. Security Fix CVE-2010-4531 A stack-based buffer overflow flaw was found in the way pcsc-lite decoded certain attribute values of Answer-to-Reset (ATR) messages. A local attacker could use this flaw to execute arbitrary code with the privileges of the user running the pcscd daemon (root, by default), by inserting a specially-crafted smart card. Bug Fixes BZ# 788474 , BZ# 814549 Due to an error in the init script, the chkconfig utility did not automatically place the pcscd init script after the start of the HAL daemon. Consequently, the pcscd service did not start automatically at boot time. With this update, the pcscd init script has been changed to explicitly start only after HAL is up, thus fixing this bug. BZ# 834803 Because the chkconfig settings and the startup files in the /etc/rc.d/ directory were not changed during the update described in the RHBA-2012:0990 advisory, the user had to update the chkconfig settings manually to fix the problem. Now, the chkconfig settings and the startup files in the /etc/rc.d/ directory are automatically updated as expected. BZ# 891852 Previously, the SCardGetAttrib() function did not work properly and always returned the "SCARD_E_INSUFFICIENT_BUFFER" error regardless of the actual buffer size. This update applies a patch to fix this bug and the SCardGetAttrib() function now works as expected. All users of pcsc-lite are advised to upgrade to these updated packages, which fix these issues. After installing this update, the pcscd daemon will be restarted automatically.

Commands:
Chapter 13. Uninstalling OpenShift Logging You can remove OpenShift Logging from your OpenShift Container Platform cluster. 13.1. Uninstalling OpenShift Logging from OpenShift Container Platform You can stop log aggregation by deleting the ClusterLogging custom resource (CR). After deleting the CR, there are other OpenShift Logging components that remain, which you can optionally remove. Deleting the ClusterLogging CR does not remove the persistent volume claims (PVCs). To preserve or delete the remaining PVCs, persistent volumes (PVs), and associated data, you must take further action. Prerequisites OpenShift Logging and Elasticsearch must be installed. Procedure To remove OpenShift Logging: Use the OpenShift Container Platform web console to remove the ClusterLogging CR: Switch to the Administration Custom Resource Definitions page. On the Custom Resource Definitions page, click ClusterLogging . On the Custom Resource Definition Details page, click Instances . Click the Options menu to the instance and select Delete ClusterLogging . Optional: Delete the custom resource definitions (CRD): Switch to the Administration Custom Resource Definitions page. Click the Options menu to ClusterLogForwarder and select Delete Custom Resource Definition . Click the Options menu to ClusterLogging and select Delete Custom Resource Definition . Click the Options menu to Elasticsearch and select Delete Custom Resource Definition . Optional: Remove the Red Hat OpenShift Logging Operator and OpenShift Elasticsearch Operator: Switch to the Operators Installed Operators page. Click the Options menu to the Red Hat OpenShift Logging Operator and select Uninstall Operator . Click the Options menu to the OpenShift Elasticsearch Operator and select Uninstall Operator . Optional: Remove the OpenShift Logging and Elasticsearch projects. Switch to the Home Projects page. Click the Options menu to the openshift-logging project and select Delete Project . Confirm the deletion by typing openshift-logging in the dialog box and click Delete . Click the Options menu to the openshift-operators-redhat project and select Delete Project . Important Do not delete the openshift-operators-redhat project if other global operators are installed in this namespace. Confirm the deletion by typing openshift-operators-redhat in the dialog box and click Delete . To keep the PVCs for reuse with other pods, keep the labels or PVC names that you need to reclaim the PVCs. Optional: If you do not want to keep the PVCs, you can delete them. Warning Releasing or deleting PVCs can delete PVs and cause data loss. Switch to the Storage Persistent Volume Claims page. Click the Options menu to each PVC and select Delete Persistent Volume Claim . If you want to recover storage space, you can delete the PVs. Additional resources Reclaiming a persistent volume manually

Commands:
Chapter 3. Security SCAP Security Guide The scap-security-guide package has been included in Red Hat Enterprise Linux 6.6 to provide security guidance, baselines, and associated validation mechanisms that use Security Content Automation Protocol (SCAP). SCAP Security Guide contains the necessary data to perform system security compliance scans regarding prescribed security policy requirements; both a written description and an automated test (probe) are included. By automating the testing, SCAP Security Guide provides a convenient and reliable way to verify system compliance on a regular basis.

Commands: