mtpti5iD/redhat-docs_dataset huggingface dataset:
3.5. Suspend and Resume When a system is suspended, the kernel calls on drivers to store their states and then unloads them. When the system is resumed, it reloads these drivers, which attempt to reprogram their devices. The drivers' ability to accomplish this task determines whether the system can be resumed successfully. Video drivers are particularly problematic in this regard, because the Advanced Configuration and Power Interface (ACPI) specification does not require system firmware to be able to reprogram video hardware. Therefore, unless video drivers are able to program hardware from a completely uninitialized state, they may prevent the system from resuming. Red Hat Enterprise Linux 7 includes greater support for new graphics chipsets, which ensures that suspend and resume will work on a greater number of platforms. In particular, support for NVIDIA chipsets has been greatly improved; in particular for the GeForce 8800 series.

Commands:
Chapter 19. Forms in Business Central A form is a layout definition for a page, defined as HTML, that is displayed as a dialog window to the user during process and task instantiation. Task forms acquire data from a user for both the process and task instance execution, whereas process forms take input and output from process variables. The input is then mapped to the task using the data input assignment, which you can use inside of a task. When the task is completed, the data is mapped as a data output assignment to provide the data to the parent process instance. 19.1. Viewing the Mortgage_Process forms The goal of this chapter is to introduce you to the Mortgage_Process sample project's predefined forms which are used for collecting user data for the mortgage application business process. For this tutorial, you do not create and modify the Mortgage_Process forms. Instead, review the predefined sample forms. For information about creating forms, see Designing business processes using BPMN models . Procedure In Business Central, go to Menu Design Projects Mortgage_Process . From the asset list, click the right arrow to view the second page of the asset list and select the Applicant form. Figure 19.1. Applicant sample form Click Menu Design Projects Mortgage_Process . From the asset list, select the Property form. The Property form is shown in the following screenshot: Figure 19.2. Property sample form Click Menu Design Projects Mortgage_Process . From the asset list, select the Application form. The Application form is shown in the following screenshot: Figure 19.3. Application sample form Click the X icon in the upper-right corner to close the editor.

Commands:
Appendix B. ConnectionBuilder Methods The following table outlines the key methods available to the ConnectionBuilder class used in V4 of the Java software development kit. Table B.1. ConnectionBuilder Methods Method Argument Type Description user String The name of the user with which to connect to the Manager. You must specify both the user name and domain, such as admin@internal . This method must be used together with the password method. password String The password of the user with which to connect to the Manager. compress Boolean Specifies whether responses from the server where the Manager is hosted should be compressed. This option is disabled by default, so this method is only required to enable this option. timeout Integer The timeout, in seconds, to wait for responses to requests. If a request takes longer than this value to respond, the request is cancelled, and an exception is thrown. This argument is optional. ssoUrl String The base URL of the server where the Manager is hosted. For example, https://server.example.com/ovirt-engine/sso/oauth/token?\grant_type=password&scope=ovirt-app-api for password authentication. ssoRevokeUrl String The base URL of the SSO revoke service. This option only needs to be specified when you use an external authentication service. By default, this URL is automatically calculated from the value of the url option so that SSO token revoke is performed using the SSO service that is part of the engine. ssoTokenName String The token name in the JSON SSO response returned from the SSO server. By default, this value is access_token . insecure Boolean Enables or disables verification of the host name in the SSL certificate presented by the server where the Manager is hosted. By default, the identity of host names is verified, and the connection is rejected if the host name is not correct, so this method is only required to disable this option. trustStoreFile String Specifies the location of a file containing the CA certificate used to verify the certificate presented by the server where the Manager is hosted. This method must be used together with the trustStorePassword method. trustStorePassword String The password used to access the keystore file specified in the trustStorePath method.

Commands:
Chapter 10. Disabling Windows container workloads You can disable the capability to run Windows container workloads by uninstalling the Windows Machine Config Operator (WMCO) and deleting the namespace that was added by default when you installed the WMCO. 10.1. Uninstalling the Windows Machine Config Operator You can uninstall the Windows Machine Config Operator (WMCO) from your cluster. Prerequisites Delete the Windows Machine objects hosting your Windows workloads. Procedure From the Operators OperatorHub page, use the Filter by keyword box to search for Red Hat Windows Machine Config Operator . Click the Red Hat Windows Machine Config Operator tile. The Operator tile indicates it is installed. In the Windows Machine Config Operator descriptor page, click Uninstall . 10.2. Deleting the Windows Machine Config Operator namespace You can delete the namespace that was generated for the Windows Machine Config Operator (WMCO) by default. Prerequisites The WMCO is removed from your cluster. Procedure Remove all Windows workloads that were created in the openshift-windows-machine-config-operator namespace: USD oc delete --all pods --namespace=openshift-windows-machine-config-operator Verify that all pods in the openshift-windows-machine-config-operator namespace are deleted or are reporting a terminating state: USD oc get pods --namespace openshift-windows-machine-config-operator Delete the openshift-windows-machine-config-operator namespace: USD oc delete namespace openshift-windows-machine-config-operator Additional resources Deleting Operators from a cluster Removing Windows nodes

Commands:
oc delete --all pods --namespace=openshift-windows-machine-config-operator
oc get pods --namespace openshift-windows-machine-config-operator
oc delete namespace openshift-windows-machine-config-operator
Chapter 154. KafkaMirrorMaker2Status schema reference Used in: KafkaMirrorMaker2 Property Property type Description conditions Condition array List of status conditions. observedGeneration integer The generation of the CRD that was last reconciled by the operator. url string The URL of the REST API endpoint for managing and monitoring Kafka Connect connectors. connectors map array List of MirrorMaker 2 connector statuses, as reported by the Kafka Connect REST API. autoRestartStatuses AutoRestartStatus array List of MirrorMaker 2 connector auto restart statuses. connectorPlugins ConnectorPlugin array The list of connector plugins available in this Kafka Connect deployment. labelSelector string Label selector for pods providing this resource. replicas integer The current number of pods being used to provide this resource.

Commands:
Chapter 3. Importing Puppet Classes and Environments into Satellite Import Puppet classes and environments from the installed Puppet modules to Satellite Server or any attached Capsule Server before you assign any of the classes to managed hosts. Prerequisite Ensure to select Any Organization and Any Location as context, otherwise the import might fail. Procedure In the Satellite web UI, navigate to Configure > Classes or Configure > Environments . Click the Import button in the upper right corner and select which Capsule you want to import modules from. You may typically choose between your Satellite Server or any attached Capsule Server. Select the Puppet environments to import using checkboxes on the left. Click the Update button to import the Puppet environments and classes to Satellite. The import should result in a notification as follows:

Commands:
Successfully updated environments and Puppet classes from the on-disk Puppet installation
Chapter 83. ExternalConfigurationEnvVarSource schema reference Used in: ExternalConfigurationEnv Property Description configMapKeyRef Reference to a key in a ConfigMap. For more information, see the external documentation for core/v1 configmapkeyselector . ConfigMapKeySelector secretKeyRef Reference to a key in a Secret. For more information, see the external documentation for core/v1 secretkeyselector . SecretKeySelector

Commands:
Chapter 6. Performing Cross-Site Replication Operations Data Grid clusters running in different locations can discover and communicate with each other to backup data. Prerequisites Start the Data Grid CLI. Connect to a running Data Grid cluster. 6.1. Bringing backup locations offline and online Take backup locations offline manually and bring them back online. Prerequisites Create a CLI connection to Data Grid. Procedure Check if backup locations are online or offline with the site status command: Note --site is an optional argument. If not set, the CLI returns all backup locations. Tip Use the --all-caches option to get the backup location status for all caches. Manage backup locations as follows: Bring backup locations online with the bring-online command: Take backup locations offline with the take-offline command: Tip Use the --all-caches option to bring a backup location online, or take a backup location offline, for all caches. For more information and examples, run the help site command. 6.2. Configuring cross-site state transfer modes You can configure cross-site state transfer operations to happen automatically when Data Grid detects that backup locations come online. Alternatively you can use the default mode, which is to manually perform state transfer. Prerequisites Create a CLI connection to Data Grid. Procedure Use the site command to configure state transfer modes, as in the following examples: Retrieve the current state transfer mode. Configure automatic state transfer operations for a cache and backup location. Tip Run the help site command for more information and examples. 6.3. Pushing state to backup locations Transfer cache state to backup locations. Prerequisites Create a CLI connection to Data Grid. Procedure Use the site push-site-state command to push state transfer, as in the following example: Tip Use the --all-caches option to push state transfer for all caches. For more information and examples, run the help site command.

Commands:
site status --cache=cacheName --site=NYC
site bring-online --cache=customers --site=NYC
site take-offline --cache=customers --site=NYC
site state-transfer-mode get --cache=cacheName --site=NYC
site state-transfer-mode set --cache=cacheName --site=NYC --mode=AUTO
site push-site-state --cache=cacheName --site=NYC
5.214. nss-pam-ldapd 5.214.1. RHBA-2012:1487 - nss-pam-ldapd bug fix update Updated nss-pam-ldapd packages that fix a bug is now available for Red Hat Enterprise Linux 6. The nss-pam-ldapd provides the nss-pam-ldapd daemon (nslcd) which uses a directory server to look up name service information on behalf of a lightweight nsswitch module. Bug Fix BZ# 864365 When the nslcd daemon requested access to a large group, a buffer provided by the glibc library could not contain such a group and retried again with a larger buffer to process the operation successfully. However, confusing and redundant error messages were written to the /var/log/message file. This update makes sure that even when glibc provides a buffer that is too small on first attempt in the described scenario, no redundant error messages are returned. All users of nss-pam-ldapd are advised to upgrade to this updated package, which fixes this bug.

Commands:
5.176. lsvpd 5.176.1. RHBA-2012:0795 - lsvpd bug fix update Updated lsvpd packages that fix four bugs are now available for Red Hat Enterprise Linux 6. The lsvpd package provides the lsvpd command to list device Vital Product Data (VPD), the lscfg command to display configuration, diagnostic, and vital product data (VPD) information, and the lsmcode command to display the microcode and firmware levels. Bug Fixes BZ# 684646 Prior to this update, the vpdupdate tool tried to collect additional information about the SCSI devices. As a consequence, vpdupdate sent irrelevant messages to the syslog file. This update modifies the sysfs layout in lsvpd. Now, no more unwanted messages are sent to the syslog file. BZ# 688574 Prior to this update, the lsvpd man page did not correctly describe the "-p" option. With this update, the man page correctly states that the "-p" option prints the designed output. BZ# 714086 Prior to this update, the lscfg(8), lsmcode(8), lsmsr(8), lsvio(8), and vpdupdate(8) man pages missed to document several lsvpd options. This update adds all missing options to the man pages. BZ# 741899 Prior to this update, the lsmcode tool did not contain the build requirement "librtas-devel". As a consequence, the firmware version was not displayed. This update modifies lsmcode file so that the missing build requirement is added to the spec file. All users of lsvpd are advised to upgrade to this updated package, which adds this enhancement.

Commands:
7.9. RHEA-2013:1622 - new packages: xorg-x11-glamor New xorg-x11-glamor packages are now available for Red Hat Enterprise Linux 6. The glamor module is an open-source 2D graphics common driver for the X Window System as implemented by X.org. It supports a variety of graphics chip sets which have OpenGL, EGL or GBM support. This enhancement update adds the xorg-x11-glamor packages to Red Hat Enterprise Linux 6. The glamor library is provided to support new AMD GPU hardware and can be used by the DDX driver to implement acceleration using the OpenGL driver. Some new hardware, such as AMD HD7xxx Series, needs glamor for acceleration. (BZ# 962832 ) All users who require xorg-x11-glamor are advised to install these new packages.

Commands:
10.5. Restoring and Recovering Resources While an incident response is in progress, the CERT team should be investigating while working toward data and system recovery. Unfortunately, it is the nature of the breach which dictates the course of recovery. Having backups or offline, redundant systems during this time is invaluable. To recover systems, the response team must bring any downed systems or applications back online, such as authentication servers, database servers, and any other production resources. Having production backup hardware ready for use is highly recommended, such as extra hard drives, hot-spare servers, and the like. Ready-made systems should have all production software loaded and ready for immediate use. Only the most recent and pertinent data needs to be imported. This ready-made system should be kept isolated from the rest of the network. If a compromise occurs and the backup system is a part of the network, then the purpose of having a backup system is defeated. System recovery can be a tedious process. In many instances there are two courses of action from which to choose. Administrators can perform a clean re-installation of the operating system on each affected system followed by restoration of all applications and data. Alternatively, administrators can patch the offending vulnerabilities and bring the affected system back into production. 10.5.1. Reinstalling the System Performing a clean re-installation ensures that the affected system is cleansed of any trojans, backdoors, or malicious processes. Re-installation also ensures that any data (if restored from a trusted backup source) is cleared of any malicious modifications. The drawback to total system recovery is the time involved in rebuilding systems from scratch. However, if there is a hot backup system available for use where the only action to take is to dump the most recent data, system downtime is greatly reduced.

Commands:
Chapter 5. Installing Tcl/Tk 5.1. Introduction to Tcl/Tk Tcl is a dynamic programming language, while Tk is a graphical user interface (GUI) toolkit. They provide a powerful and easy-to-use platform for developing cross-platform applications with graphical interfaces. As a dynamic programming language, 'Tcl' provides simple and flexible syntax for writing scripts. The tcl package provides the interpreter for this language and the C library. You can use Tk as GUI toolkit that provides a set of tools and widgets for creating graphical interfaces. You can use various user interface elements such as buttons, menus, dialog boxes, text boxes, and canvas for drawing graphics. Tk is the GUI for many dynamic programming languages. For more information about Tcl/Tk, see the Tcl/Tk manual or Tcl/Tk documentation web page . 5.2. Installing Tcl The default Tcl implementation is usually installed by default. To install it manually, use the following procedure. Procedure To install Tcl , use: Verification steps To verify the Tcl version installed on your system, run the interpreter tclsh . In the interpreter run this command: You can exit the interpreter interface by pressing Ctrl + C 5.3. Installing Tk The default Tk implementation is usually installed by default. To install it manually, use the following procedure. Procedure To install Tk , use: Verification steps To verify the Tk version installed on your system, run the window shell wish . You need to be running a graphical display. In the shell run this command: You can exit the interpreter interface by pressing Ctrl + C

Commands:
dnf install tcl
tclsh
% info patchlevel 8.6
dnf install tk
wish
% puts USDtk_version 8.6
Chapter 1. Introduction The Metrics Store collects logs and metrics from Red Hat Virtualization. The data is transferred from Red Hat Virtualization to OpenShift where it is stored and aggregated in Elasticsearch and saved in indexes . Elasticsearch is a distributed, RESTful search and analytics engine that lets you perform and combine many types of searches. Use Kibana to search, view, and interact with real-time data stored in Elasticsearch indexes. Kibana is an open source analytics and visualization platform designed to work with Elasticsearch. You can easily perform advanced data analysis and visualize your data in a variety of charts and tables. Kibana enables you to view and preempt critical problems, track system usage and resources, and even plan for future growth. 1.1. Accessing Kibana Access Kibana at https://kibana. FQDN . Log in by entering your username and password.

Commands:
24.3. Listing and Displaying Certificates Listing and Displaying Certificates in the Web UI To list certificates assigned to a user, host, or service entry: Open the Identity tab, and select the Users , Hosts , or Services subtab. Click on the name of the user, host, or service to open its configuration page. Figure 24.5. List of Hosts The configuration page lists all certificates assigned to the entry. Additionally, clicking Show displays a particular certificate. To list all certificates registered on the IdM server: Open the Authentication tab, and select the Certificates subtab. A list of all certificates is displayed in the Certificates section. To display a particular certificate, click on its serial number. Figure 24.6. List of Certificates Listing Certificates from the Command Line To list all certificates in the IdM database, run the ipa cert-find command. You can filter the search results by specifying certain certificate properties, such as issue date or validity date. For example, to search by an issue date interval, use the --issuedon-from or --issuedon-to options to specify the start and end points or a period of time. For a complete list of options used to filter the search for a certificate, run ipa cert-find with the --help option added. Displaying Certificates from the Command Line To display a certificate, use the ipa cert-show command and specify the serial number. To display the certificates assigned to a user, host, or service entry, use ipa cert-show and specify the entry. For example, to display the certificate assigned to a user: You can also save a certificate to a file by adding the --out option to ipa cert-show . Note that if the user, host, or service has more than one certificate, the --out option exports all of them. The certificate or certificates are exported as PEM objects.

Commands:
ipa cert-find ----------------------- 10 certificates matched ----------------------- Serial number (hex): 0x1 Serial number: 1 Status: VALID Subject: CN=Certificate Authority,O=EXAMPLE.COM ----------------------------- Number of entries returned 10 -----------------------------
ipa cert-find --issuedon-from=2020-01-07 --issuedon-to=2020-02-07
ipa cert-show 132 Serial number: 132 Certificate: MIIDtzCCAp+gAwIBAgIBATANBgkqhkiG9w0BAQsFADBBMR8wHQYDVQQKExZMQUIu LxIQjrEFtJmoBGb/TWRlwGEWy1ayr4iTEf1ayZ+RGNylLalEAtk9RLjEjg== Subject: CN=Certificate Authority,O=EXAMPLE.COM Issuer: CN=Certificate Authority,O=EXAMPLE.COM Not Before: Sun Jun 08 05:51:11 2014 UTC Not After: Thu Jun 08 05:51:11 2034 UTC Serial number (hex): 0x132 Serial number: 132
ipa user-show user User login: user Certificate: MIICfzCCAWcCAQA
ipa cert-show certificate_serial_number --out= path_to_file
4.103. iwl1000-firmware 4.103.1. RHBA-2011:1558 - iwl1000-firmware bug fix and enhancement update An updated iwl1000-firmware package that fixes various bugs and adds several enhancements is now available for Red Hat Enterprise Linux 6. The iwl1000-firmware package provides the firmware required by the iwglan driver for Linux to support Intel Wireless WiFi Link 1000 series adapters. The iwl1000-firmware package has been upgraded to upstream version 39.31.5.1, which provides a number of bug fixes and enhancements over the version. (BZ# 694245 ) All users of the iwlagn driver are advised to upgrade to this updated iwl1000-firmware package, which resolves these issues and adds these enhancements.

Commands:
Chapter 2. Networking Changes to HPN Add-On Starting with Red Hat Enterprise Linux 6.6, the High Performance Networking (HPN) Add-On is no longer be available as a separate product. Instead, the functionality found in the HPN Add-On has been integrated into the base product and delivered as part of the Red Hat Enterprise Linux base channel. In addition to including the HPN functionality into the base Red Hat Enterprise Linux 6 product, the RDMA over Converged Ethernet (RoCE) implementation has also been updated. RoCE uses Global Identifier or GID-based addressing for node-to-node communication. Previously, GIDs were encoded based on the Ethernet interface's MAC address along with the VLAN ID (if used). Under certain circumstances, the compute entity that runs the RoCE protocol is not aware that its traffic is VLAN-tagged. The compute entity can then sometimes create or assume a wrong GID, which can result in connectivity problems. The updated RoCE implementation resolves this problem by changing the way the RoCE GIDs are encoded, and instead bases them off the IP addresses of the Ethernet interface. All systems that use the RoCE protocol need to be upgraded to Red Hat Enterprise Linux 6.6 to ensure connection reliability due to this change in the wire protocol format. Please refer to this Red Hat Knowledge Base article for additional information: https://access.redhat.com/site/articles/971333 .

Commands: