mtpti5iD/redhat-docs_dataset huggingface dataset:
8.182. ricci 8.182.1. RHBA-2013:1673 - ricci bug fix and enhancement update Updated ricci packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The ricci packages contain a daemon and a client for remote configuring and managing of clusters. Bug Fixes BZ# 853890 Prior to this update, the ccs_sync command, used to copy and synchronize the cluster configuration across different nodes, could terminate unexpectedly when pushing an external configuration file to selected nodes. With this update, ccs_syncd has been fixed and it no longer crashes in the aforementioned scenario. BZ# 883585 Prior to this update, the ricci, ccs, and ccs_sync man pages had file permissions incorrectly set to executable. With this update, the file permissions of these man pages have been corrected. BZ# 893574 Prior to this update, the ccs manager did not configure the fence_scsi agent properly. The missing configuration could cause an incorrect behavior of a cluster during recovery. This bug has been fixed and fence_scsi is now configured as expected. BZ# 918555 Due to an incorrect parsing of cluster configuration, the ccs manager did not display the fence_daemon options. With this update, the parsing has been fixed and fence_daemon options are now properly displayed. Enhancements BZ# 877863 With this update the "--lsresourceopts" command-line option has been added to the css manager. This option provides an intuitive way how to display and list all available resource types and agents from the shell prompt. BZ# 1009098 The cluster schema included in the ricci package has been updated to include new options in resource and fence agents packages. Users of ricci are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
7.140. matahari 7.140.1. RHBA-2013:0404 - removed packages: matahari The matahari packages have been removed from Red Hat Enterprise Linux 6. The matahari packages provide a set of APIs for operating system management that are exposed to remote access over the Qpid Management Framework (QMF). With this update, an empty package has been provided to ensure that the matahari packages are removed from Red Hat Enterprise Linux 6. (BZ#833109) All users of matahari are advised to remove these packages.

Commands:
Chapter 139. KafkaMirrorMaker2ConnectorSpec schema reference Used in: KafkaMirrorMaker2MirrorSpec Property Description tasksMax The maximum number of tasks for the Kafka Connector. integer config The Kafka Connector configuration. The following properties cannot be set: connector.class, tasks.max. map autoRestart Automatic restart of connector and tasks configuration. AutoRestart pause Whether the connector should be paused. Defaults to false. boolean

Commands:
13.7.2. Migrating Old Authentication Information to LDAP Format The /usr/share/openldap/migration/ directory contains a set of shell and Perl scripts for migrating authentication information into an LDAP format. Note Perl must be installed on the system to use these scripts. First, modify the migrate_common.ph file so that it reflects the correct domain. The default DNS domain should be changed from its default value to something like: The default base should also be changed, to something like: The job of migrating a user database into a format that is LDAP readable falls to a group of migration scripts installed in the same directory. Using Table 13.1, "LDAP Migration Scripts" , decide which script to run to migrate the user database. Run the appropriate script based on the existing name service. The README and the migration-tools.txt files in the /usr/share/openldap/migration/ directory provide more details on how to migrate the information. Table 13.1. LDAP Migration Scripts Existing name service Is LDAP running? Script to Use /etc flat files yes migrate_all_online.sh /etc flat files no migrate_all_offline.sh NetInfo yes migrate_all_netinfo_online.sh NetInfo no migrate_all_netinfo_offline.sh NIS (YP) yes migrate_all_nis_online.sh NIS (YP) no migrate_all_nis_offline.sh

Commands:
USDDEFAULT_MAIL_DOMAIN = " example ";
USDDEFAULT_BASE = "dc= example ,dc= com ";
2.2.7. Securing Postfix Postfix is a Mail Transfer Agent (MTA) that uses the Simple Mail Transfer Protocol (SMTP) to deliver electronic messages between other MTAs and to email clients or delivery agents. Although many MTAs are capable of encrypting traffic between one another, most do not, so sending email over any public networks is considered an inherently insecure form of communication. It is recommended that anyone planning to implement a Postfix server address the following issues. 2.2.7.1. Limiting a Denial of Service Attack Because of the nature of email, a determined attacker can flood the server with mail fairly easily and cause a denial of service. The effectiveness of such attacks can be limited by setting limits of the directives in the /etc/postfix/main.cf file. You can change the value of the directives which are already there or you can add the directives you need with the value you want in the following format: The following is a list of directives that can be used for limiting a denial of service attack: smtpd_client_connection_rate_limit - The maximum number of connection attempts any client is allowed to make to this service per time unit (described below). The default value is 0, which means a client can make as many connections per time unit as Postfix can accept. By default, clients in trusted networks are excluded. anvil_rate_time_unit - This time unit is used for rate limit calculations. The default value is 60 seconds. smtpd_client_event_limit_exceptions - Clients that are excluded from the connection and rate limit commands. By default, clients in trusted networks are excluded. smtpd_client_message_rate_limit - The maximum number of message deliveries a client is allowed to request per time unit (regardless of whether or not Postfix actually accepts those messages). default_process_limit - The default maximum number of Postfix child processes that provide a given service. This limit can be overruled for specific services in the master.cf file. By default the value is 100. queue_minfree - The minimum amount of free space in bytes in the queue file system that is needed to receive mail. This is currently used by the Postfix SMTP server to decide if it will accept any mail at all. By default, the Postfix SMTP server rejects MAIL FROM commands when the amount of free space is less than 1.5 times the message_size_limit. To specify a higher minimum free space limit, specify a queue_minfree value that is at least 1.5 times the message_size_limit. By default the queue_minfree value is 0. header_size_limit - The maximum amount of memory in bytes for storing a message header. If a header is larger, the excess is discarded. By default the value is 102400. message_size_limit - The maximum size in bytes of a message, including envelope information. By default the value is 10240000.

Commands:
<directive> = <value>
Part III. Integrating Red Hat Decision Manager with Red Hat Single Sign-On As a system administrator, you can integrate Red Hat Single Sign-On with Red Hat Decision Manager to secure your Red Hat Decision Manager browser applications with a single authentication method. Prerequisites Red Hat Decision Manager is installed on Red Hat JBoss EAP 7.4. For information, see Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.4 .

Commands:
Chapter 4. Preparing for data loss with VM snapshots Virtual machine (VM) snapshots are an integral component of a data recovery strategy, since they preserve the full state of an IdM server: Operating system software and settings IdM software and settings IdM customer data Preparing a VM snapshot of an IdM Certificate Authority (CA) replica allows you to rebuild an entire IdM deployment after a disaster. Warning If your environment uses the integrated CA, a snapshot of a replica without a CA will not be sufficient for rebuilding a deployment, because certificate data will not be preserved. Similarly, if your environment uses the IdM Key Recovery Authority (KRA), make sure you create snapshots of a KRA replica, or you might lose the storage key. Red Hat recommends creating snapshots of a VM that has all of the IdM server roles installed which are in use in your deployment: CA, KRA, DNS. Prerequisites A hypervisor capable of hosting RHEL VMs. Procedure Configure at least one CA replica in the deployment to run inside a VM. If IdM DNS or KRA are used in your environment, consider installing DNS and KRA services on this replica as well. Optional: Configure this VM replica as a hidden replica . Periodically shutdown this VM, take a full snapshot of it, and bring it back online so it continues to receive replication updates. If the VM is a hidden replica, IdM Clients will not be disrupted during this procedure. Additional resources Which hypervisors are certified to run Red Hat Enterprise Linux? The hidden replica mode

Commands:
Chapter 85. usage This chapter describes the commands under the usage command. 85.1. usage list List resource usage per project Usage: Table 85.1. Optional Arguments Value Summary -h, --help Show this help message and exit --start <start> Usage range start date, ex 2012-01-20 (default: 4 weeks ago) --end <end> Usage range end date, ex 2012-01-20 (default: tomorrow) Table 85.2. Output Formatters Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 85.3. CSV Formatter Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 85.4. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 85.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. 85.2. usage show Show resource usage for a single project Usage: Table 85.6. Optional Arguments Value Summary -h, --help Show this help message and exit --project <project> Name or id of project to show usage for --start <start> Usage range start date, ex 2012-01-20 (default: 4 weeks ago) --end <end> Usage range end date, ex 2012-01-20 (default: tomorrow) Table 85.7. 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 85.8. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 85.9. Shell Formatter Value Summary --prefix PREFIX Add a prefix to all variable names Table 85.10. 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 usage list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--start <start>] [--end <end>]
openstack usage show [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] [--project <project>] [--start <start>] [--end <end>]
function::substr Name function::substr - Returns a substring Synopsis Arguments str the string to take a substring from start starting position of the extracted string (first character is 0) length length of string to return Description Returns the substring of the given string at the given start position with the given length (or smaller if the length of the original string is less than start + length, or length is bigger than MAXSTRINGLEN).

Commands:
substr:string(str:string,start:long,length:long)
Chapter 2. Subscribing to software repositories for hyperconverged hosts Hyperconverged hosts require access to various repositories. New Red Hat Virtualization hosts are subscribed to these repositories during installation and setup, so no further action is necessary. New Red Hat Enterprise Linux hosts and virtualization hosts being converted to hyperconverged hosts need to subscribe to the repositories by running the following command.

Commands:
subscription-manager repos --enable="rhel-8-for-x86_64-baseos-rpms" --enable="rhel-8-for-x86_64-appstream-rpms" --enable="rhv-4.4-manager-for-rhel-8-x86_64-rpms" --enable="rhv-4-tools-for-rhel-8-x86_64-rpms" --enable="ansible-2.9-for-rhel-8-x86_64-rpms" --enable="jb-eap-7.3-for-rhel-8-x86_64-rpms"
Chapter 6. Installing a three-node cluster on vSphere In OpenShift Container Platform version 4.14, you can install a three-node cluster on VMware vSphere. A three-node cluster consists of three control plane machines, which also act as compute machines. This type of cluster provides a smaller, more resource efficient cluster, for cluster administrators and developers to use for testing, development, and production. You can install a three-node cluster using either installer-provisioned or user-provisioned infrastructure. 6.1. Configuring a three-node cluster You configure a three-node cluster by setting the number of worker nodes to 0 in the install-config.yaml file before deploying the cluster. Setting the number of worker nodes to 0 ensures that the control plane machines are schedulable. This allows application workloads to be scheduled to run from the control plane nodes. Note Because application workloads run from control plane nodes, additional subscriptions are required, as the control plane nodes are considered to be compute nodes. Prerequisites You have an existing install-config.yaml file. Procedure Set the number of compute replicas to 0 in your install-config.yaml file, as shown in the following compute stanza: Example install-config.yaml file for a three-node cluster apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0 # ... If you are deploying a cluster with user-provisioned infrastructure: Configure your application ingress load balancer to route HTTP and HTTPS traffic to the control plane nodes. In a three-node cluster, the Ingress Controller pods run on the control plane nodes. For more information, see the "Load balancing requirements for user-provisioned infrastructure". After you create the Kubernetes manifest files, make sure that the spec.mastersSchedulable parameter is set to true in cluster-scheduler-02-config.yml file. You can locate this file in <installation_directory>/manifests . For more information, see "Creating the Kubernetes manifest and Ignition config files" in "Installing a cluster on vSphere with user-provisioned infrastructure". Do not create additional worker nodes. Example cluster-scheduler-02-config.yml file for a three-node cluster apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {} 6.2. steps Installing a cluster on vSphere with customizations Installing a cluster on vSphere with user-provisioned infrastructure

Commands:
apiVersion: v1 baseDomain: example.com compute: - name: worker platform: {} replicas: 0
apiVersion: config.openshift.io/v1 kind: Scheduler metadata: creationTimestamp: null name: cluster spec: mastersSchedulable: true policy: name: "" status: {}
4.239. psacct 4.239.1. RHBA-2012:1051 - psacct bug fix update Updated psacct packages that fix two bugs are now available for Red Hat Enterprise Linux 6 Extended Update Support. The psacct packages contain utilities for monitoring process activities, including ac, lastcomm, accton, dump-acct, dump-utmp and sa. The "ac" command displays statistics about how long users have been logged on. The "lastcomm" command displays information about previously executed commands. The "accton" command turns process accounting on or off. The "dump-acct" command transforms the output file from the accton format to a human-readable format. The "dump-utmp" command prints utmp files in human-readable format. The "sa" command summarizes information about previously executed commands. Bug Fixes BZ# 828726 Previously, improper data type detection could have caused an arithmetic overflow. As a consequence, the dump-acct tool reported incorrect elapsed time values. A patch has been applied so that correct values are reported with this update. BZ# 834216 Previously, improper data type conversion caused the dump-utmp tool to report invalid timestamps. Consequently, mainly on the 64-bit PowerPC architecture, dump-utmp could have terminated unexpectedly with a segmentation fault. A patch has been applied so that correct values are reported and no crashes occur with this update. All users of psacct are advised to upgrade to these updated packages, which fix these bugs.

Commands:
4.5.3. Keeping Quotas Accurate If you enable quotas on your file system after a period of time when you have been running with quotas disabled, you should run the quotacheck command to create, check, and repair quota files. Additionally, you may want to run the quotacheck if you think your quota files may not be accurate, as may occur when a file system is not unmounted cleanly after a system crash. For more information about the quotacheck command, see the quotacheck man page. Note Run quotacheck when the file system is relatively idle on all nodes because disk activity may affect the computed quota values.

Commands:
Chapter 3. Editing a model registry You can edit the details of existing model registries, such as the model registry name, description, and database connection details. Prerequisites You have logged in to OpenShift AI as a user with OpenShift AI administrator privileges. A cluster administrator has configured and enabled the model registry component in your OpenShift AI deployment. For more information, see Configuring the model registry component . The model registry component is enabled for your OpenShift AI deployment, and contains at least 1 model registry. Procedure From the OpenShift AI dashboard, click Settings Model registry settings . Click the action menu ( ... ) beside the model registry that you want to edit, and then click Edit model registry . The Edit model registry dialog opens. Optional: In the Name field, edit the name of the model registry. Optional: In the Description field, edit the description of the model registry. Optional: In the Connect to external MySQL database section, edit the information for the external database where model data for the registry is stored. In the Host field, enter the database's host name. If the database is running in the rhoai-model-registries namespace, enter only the hostname for the database. If the database is running in a different namespace from rhoai-model-registries , enter the database hostname details in <host name>.<namespace>.svc.cluster.local format. In the Port field, enter the port number for the database. In the Username field, enter the default user name that is connected to the database. In the Password field, enter the password for the default user account. In the Database field, enter the database name. Optional: Select the Add CA certificate to secure database connection to use a certificate with your database connection. Click Use cluster-wide CA bundle to use the ca-bundle.crt bundle in the odh-trusted-ca-bundle ConfigMap. Click Use Red Hat OpenShift AI CA bundle to use the odh-ca-bundle.crt bundle in the odh-trusted-ca-bundle ConfigMap. Click Choose from existing certificates to select an existing certificate. You can select the key of any ConfigMap or secret in the rhoai-model-registries namespace. From the Resource list, select a ConfigMap or secret. From the Key list, select a key. Click Upload new certificate to upload a new certificate as a ConfigMap. Drag and drop the PEM file for your certificate into the Certificate field, or click Upload to select a file from your local machine's file system. Note Uploading a certificate creates the db-credential ConfigMap with the ca.crt key. To upload a certificate as a secret, you must create a secret in the OpenShift rhoai-model-registries namespace, and then select it as an existing certificate when you create your model registry. For more information about creating secrets in OpenShift, see OpenShift Dedicated: Providing sensitive data to pods by using secrets and Red Hat OpenShift Service on AWS: Providing sensitive data to pods by using secrets . Click Update . Verification The model registry appears with updated details on the Model Registry Settings page.

Commands:
1.5. Configure Authorization in a Security Domain To configure authorization settings for a security domain, log into the management console and follow this procedure. Procedure 1.2. Setup Authorization in a Security Domain Open the security domain's detailed view. Click the Configuration label at the top of the management console. In a managed domain, select the profile to modify from the Profile drop down box at the top left. Expand the Security menu item, and select Security Domains . Click the View link for the security domain you want to edit. Navigate to the Authorization subsystem configuration. Select the Authorization label at the top of the screen. The configuration area is divided into two areas: Policies and Details . The policy module is the basic unit of configuration. A security domain can include several authorization policies, each of which can include several attributes and options. Add a policy. Click Add to add a JAAS authorization policy module. Fill in the details for your module. The Code is the class name of the module. The Flag controls how the module relates to other authorization policy modules within the same security domain. Explanation of the Flags The Java Enterprise Edition 6 specification provides the following explanation of the flags for security modules. The following list is taken from https://docs.oracle.com/javase/6/docs/api/javax/security/auth/login/Configuration.html . Refer to that document for more detailed information. Flag Details required The policy module is required to succeed. If it succeeds or fails, authorization still continues to proceed down the policy module list. requisite The policy module is required to succeed. If it succeeds, authorization continues down the policy module list. If it fails, control immediately returns to the application (authorization does not proceed down the poicy module list). sufficient The policy module is not required to succeed. If it does succeed, control immediately returns to the application (authorization does not proceed down the policy module list). If it fails, authorization continues down the policy module list. optional The policy module is not required to succeed. If it succeeds or fails, authorization still continues to proceed down the policy module list. Edit authorization settings After you have added your module, you can modify its Code or Flags by clicking Edit in the Details section of the screen. Be sure the Attributes tab is selected. Optional: Add or remove module options. If you need to add options to your module, click its entry in the Policies list, and select the Module Options tab in the Details section of the page. Click Add and provide the key and value for the option. Use the Remove button to remove an option. Result Your authorization policy module is added to the security domain. Reload the server for it to become available.

Commands: