mtpti5iD/redhat-docs_dataset huggingface dataset:
18.2.3. Installation Phase 2 In installation phase 2, you need to specify what language to use and where phase 3 of the installation program and the software packages to be installed from the repository on the Red Hat installation medium can be found. On System z, the installation sources are usually transferred from the DVD to a network server. Phase 3 of the installation program and the repository can be accessed in one of the following ways: Over the network using one of the FTP, HTTP, HTTPS, or NFS protocols. A separate network server (FTP, HTTP, HTTPS, or NFS), which holds all the required installation sources, must be set up in advance. For details on how to set up a network server, refer to Section 19.1, "Preparing for a Network Installation" . Hard disk (DASD or a SCSI device attached through an FCP channel). You need to set up a disk that holds the required installation sources in advance. For details, Refer to Section 19.2, "Preparing for a Hard Drive Installation" . Through an FCP-attached SCSI DVD. This is handled automatically if booted from FCP-attached SCSI DVD. The interface you will use in installation phase 2 is the loader, which provides a full-screen text-based interface with a blue background by default. For unattended installations in cmdline mode, the loader offers line-mode, text-based output. (Refer to Chapter 22, Installation Phase 2: Configuring Language and Installation Source .)

Commands:
2.2.3. Networking This section describes what behaviors have changed in the graphical installer, relating to networking. Anaconda is now using NetworkManager for configuration of network interfaces during installation. The main network interface configuration screen in Anaconda has been removed. Users are only prompted for network configuration details if they are necessary during installation. The settings used during installation are then written to the system for later use. When PXE booting and using an .iso file mounted using NFS for the installation media, add repo=nfs:server:/path/ to the command line. The install.img and product.img files also need to be extracted and placed into the nfs:server:/path/images/ directory. The product.img file contains variant definitions and various install classes. Some systems with multiple network interfaces do not assign eth0 to the first network interface as recognized by the system BIOS. This can cause the installer to attempt to use a different network interface than was initially used by PXE. To change this behavior, use the following in pxelinux.cfg/* configuration files: This configuration option causes the installer to use the same network interface as the system BIOS and PXE use. You can also use the following option, which will cause the installer to use the first network device it finds that is linked to a network switch:

Commands:
IPAPPEND 2 APPEND ksdevice=bootif
ksdevice=link
Chapter 6. GitOps CLI for use with Red Hat OpenShift GitOps The GitOps argocd CLI is a tool for configuring and managing Red Hat OpenShift GitOps and Argo CD resources from a terminal. With the GitOps CLI, you can make GitOps computing tasks simple and concise. You can install this CLI tool on different platforms. 6.1. Installing the GitOps CLI See Installing the GitOps CLI . 6.2. Additional resources What is GitOps?

Commands:
Chapter 6. Inventories An inventory is a collection of hosts managed by automation controller. Organizations are assigned to inventories, while permissions to launch playbooks against inventories are controlled at the user or team level. For more information, see the following documentation: Adding and removing user permissions Adding or removing a user About the installer inventory file 6.1. Creating a new Inventory The Inventories window displays a list of the inventories that are currently available. You can sort the inventory list by name and searched type, organization, description, owners and modifiers of the inventory, or additional criteria. Procedure To view existing inventories, select Resources Inventories from the navigation panel. Automation controller provides a demonstration inventory for you to use as you learn how the controller works. You can use it as it is or edit it later. You can create another inventory, if necessary. To add another inventory, see Add a new inventory in the Automation controller User Guide for more information. Click Demo Inventory to view its details. As with organizations, inventories also have associated users and teams that you can view through the Access tab. For more information, see Inventories in the Automation controller User Guide . A user with the role of System Administrator has been automatically populated for this. 6.2. Managing groups and hosts Inventories are divided into groups and hosts. Groups can represent a particular environment (such as a "Datacenter 1" or "Stage Testing"), a server type (such as "Application Servers" or "DB Servers"), or any other representation of your environment. The groups and hosts that belong to the Demo inventory are shown in the Groups and Hosts tabs. 6.2.1. Adding new groups and hosts Groups are only applicable to standard inventories and are not configurable directly through a Smart Inventory. You can associate an existing group through hosts that are used with standard inventories. For more information, see Adding groups to inventories in the Automation controller User Guide . Procedure From the navigation panel, select Resources Inventories . To add new groups, select the Groups tab and click Add . To add new hosts to groups, select the Hosts tab and click Add . As part of the initial setup and to test that automation controller is set up properly, a local host is added for your use. Example If the organization that you created has a group of web server hosts supporting a particular application, complete the following steps: Create a group and add the web server hosts, to add these hosts to the inventory. Click Cancel (if you made no changes) or use the breadcrumb navigational links at the top of the automation controller browser to return to the Inventories list view. Clicking Save does not exit the Details dialog.

Commands:
11.3.3.5. Fetchmail Command Options Most Fetchmail options used on the command line when executing the fetchmail command mirror the .fetchmailrc configuration options. In this way, Fetchmail may be used with or without a configuration file. These options are not used on the command line by most users because it is easier to leave them in the .fetchmailrc file. There may be times when it is desirable to run the fetchmail command with other options for a particular purpose. It is possible to issue command options to temporarily override a .fetchmailrc setting that is causing an error, as any options specified at the command line override configuration file options.

Commands:
Chapter 1. Release Schedule The following table lists the dates of each Red Hat Virtualization 4.4 release: Table 1.1. Red Hat Virtualization release schedule Release Date Red Hat Virtualization 4.4 General Availability (ovirt-4.4.1) 2020-08-04 Red Hat Virtualization 4.4 Batch Update 1 (ovirt-4.4.2) 2020-09-23 Red Hat Virtualization 4.4 Batch Update 2 (ovirt-4.4.3) 2020-11-24 Red Hat Virtualization 4.4 Batch Update 3 (ovirt-4.4.4) 2021-02-02 Red Hat Virtualization 4.4 Batch Update 4 (ovirt-4.4.5) 2021-04-14 Red Hat Virtualization 4.4 Batch Update 5 (ovirt-4.4.6) 2021-06-01 Red Hat Virtualization 4.4 Batch Update 6 (ovirt-4.4.7) 2021-07-22 Red Hat Virtualization 4.4 Batch Update 7 (ovirt-4.4.8) 2021-09-08 Red Hat Virtualization 4.4 Batch Update 8 (ovirt-4.4.9) 2021-11-16

Commands:
Chapter 5. Known issues This section describes known issues in Red Hat Satellite 6.16. 5.1. Installation and upgrade Concurrently synchronizing many large repositories to a Capsule might cause core dumps for the pulpcore-api The pulpcore-api might experience core dumps when multiple large repositories are synchronized to a Capsule concurrently. When this problem occurs, the following error message is displayed in /var/log/messages : capsule systemd-coredump[16056]: Process 9867 (pulpcore-api) of user 988 dumped core . The synchronization completes successfully despite the errors. Jira:SAT-27979 5.2. Security and authentication Unable to upload an OpenSCAP report from hosts that run RHEL 9.3 or earlier with FIPS mode enabled On Satellite hosts that run RHEL 9.3 or earlier with FIPS mode enabled, uploading an OpenSCAP report fails with the following error: For more details, see a related Knowledgebase solution . Note that the problem has been fixed for hosts that run RHEL 9.4 or later. Jira:SAT-28297 [1] 5.3. Content management Repositories listed but not active The Red Hat Repositories page lists the Red Hat Satellite 6 Client 2 repositories as recommended repositories, but these repositories are not active yet. Continue using Red Hat Satellite Client 6 repositories. Jira:SAT-29303 Organization deletion fails If there are container push repositories among the organization's products, then organization deletion fails. To work around this problem, delete the container push repositories before deleting the organization. Jira:SAT-28387 5.4. Users and roles Newly created filters do not inherit organizations and locations associated with the role When an organization and location are defined for a role, these organizations and locations are not propagated to the filters created within the role. Consequently, users with a role assigned can access resources in any other organization or location that they have sufficient permissions to view instead of only organizations and locations defined for the role. To work around the problem: Create your filter. Start editing the filter. Save the filter without making any changes. This ensures that organizations and locations defined on the role level are propagated to filters correctly. This known issue does not affect cloned roles. If you clone an existing role and assign organizations and locations to the cloned role, the organizations and locations are propagated to filters correctly. Note that defining organizations and locations on the filter level is deprecated. See Overriding organizations and locations on the filter level . Jira:SAT-28731 [1]

Commands:
Unable to load certs Neither PUB key nor PRIV key
11.7. INSTEAD OF Triggers A view comprising multiple base tables must use an INSTEAD OF trigger to support inserts, updates and deletes that reference data in the tables. See "create trigger" in Section A.7, "Productions" . Based on the select transformation's complexity some times INSTEAD OF Triggers are automatically provided for the user when "UPDATABLE" OPTION on the view is set to "TRUE". However, using the CREATE TRIGGER mechanism user can provide/override the default behaviour. Example 11.4. Example:Define instead of trigger on View

Commands:
CREATE TRIGGER ON CustomerOrders INSTEAD OF INSERT AS FOR EACH ROW BEGIN ATOMIC INSERT INTO Customer (...) VALUES (NEW.value ...); END
3.2. pcs Usage Help Display You can use the -h option of pcs to display the parameters of a pcs command and a description of those parameters. For example, the following command displays the parameters of the pcs resource command. Only a portion of the output is shown.

Commands:
pcs resource -h Usage: pcs resource [commands] Manage pacemaker resources Commands: show [resource id] [--all] Show all currently configured resources or if a resource is specified show the options for the configured resource. If --all is specified resource options will be displayed start <resource id> Start resource specified by resource_id
11.2. Understanding the Device Renaming Procedure The device name procedure in detail is as follows: A rule in /usr/lib/udev/rules.d/60-net.rules instructs the udev helper utility, /lib/udev/rename_device , to look into all /etc/sysconfig/network-scripts/ifcfg- suffix files. If it finds an ifcfg file with a HWADDR entry matching the MAC address of an interface it renames the interface to the name given in the ifcfg file by the DEVICE directive. A rule in /usr/lib/udev/rules.d/71-biosdevname.rules instructs biosdevname to rename the interface according to its naming policy, provided that it was not renamed in a step, biosdevname is installed, and biosdevname=0 was not given as a kernel command on the boot command line. A rule in /lib/udev/rules.d/75-net-description.rules instructs udev to fill in the internal udev device property values ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH, ID_NET_NAME_MAC by examining the network interface device. Note, that some device properties might be undefined. A rule in /usr/lib/udev/rules.d/80-net-name-slot.rules instructs udev to rename the interface, provided that it was not renamed in step 1 or 2, and the kernel parameter net.ifnames=0 was not given, according to the following priority: ID_NET_NAME_ONBOARD, ID_NET_NAME_SLOT, ID_NET_NAME_PATH. It falls through to the in the list, if one is unset. If none of these are set, then the interface will not be renamed. Steps 3 and 4 are implementing the naming schemes 1, 2, 3, and optionally 4, described in Section 11.1, "Naming Schemes Hierarchy" . Step 2 is explained in more detail in Section 11.6, "Consistent Network Device Naming Using biosdevname" .

Commands:
Chapter 7. steps The following sections might be useful after deploying a proof of concept version of Red Hat Quay. Many of these procedures can be used on a proof of concept deployment, offering insights to Red Hat Quay's features. Using Red Hat Quay . The content in this guide explains the following concepts: Adding users and repositories Using image tags Building Dockerfiles with build workers Setting up build triggers Adding notifications for repository events and more Managing Red Hat Quay . The content in this guide explains the following concepts: Using SSL/TLS Configuring action log storage Configuring Clair security scanner Repository mirroring IPv6 and dual-stack deployments Configuring OIDC for Red Hat Quay Geo-replication and more

Commands:
20.8. NUMA Node Tuning Once NUMA node tuning is done using conventional management tools the following domain XML parameters are effected: > <domain> ... <numatune> <memory mode="strict" nodeset="1-4,^3"/> </numatune> ... </domain> Figure 20.10. NUMA node tuning Although all are optional, the components of this section of the domain XML are as follows: Table 20.7. NUMA node tuning elements Element Description <numatune> Provides details of how to tune the performance of a NUMA host physical machine through controlling NUMA policy for domain process. <memory> Specifies how to allocate memory for the domain process on a NUMA host physical machine. It contains several optional attributes. Attribute mode is either interleave , strict , or preferred . If no value is given it defaults to strict . Attribute nodeset specifies the NUMA nodes, using the same syntax as attribute cpuset of element <vcpu> . Attribute placement can be used to indicate the memory placement mode for the domain process. Its value can be either static or auto . If attribute <nodeset> is specified it defaults to the <placement> of <vcpu> , or static . auto indicates the domain process will only allocate memory from the advisory nodeset returned from querying numad and the value of attribute nodeset will be ignored if it is specified. If attribute placement of vcpu is auto , and attribute <numatune> is not specified, a default numatune with <placement> auto and mode strict will be added implicitly.

Commands:
> <domain> <numatune> <memory mode="strict" nodeset="1-4,^3"/> </numatune> </domain>
Chapter 18. Red Hat Enterprise Linux for Real Time Red Hat Enterprise Linux for Real Time is a new offering in Red Hat Enterprise Linux 7.1 comprised of a special kernel build and several user space utilities. With this kernel and appropriate system configuration, Red Hat Enterprise Linux for Real Time brings deterministic workloads, which allow users to rely on consistent response times and low and predictable latency. These capabilities are critical in strategic industries such as financial service marketplaces, telecommunications, or medical research. For instructions on how to install Red Hat Enterprise Linux for Real Time, and how to set up and tune the system so that you can take full advantage of this offering, refer to the Red Hat Enterprise Linux for Real Time 7 Installation Guide .

Commands:
Chapter 49. Using the standalone editor perspective You can use the standalone editor perspective of Business Central to access an asset's specific editor. By using this perspective, you can open an asset's editor and can modify the asset as required. The web address for accessing an asset's standalone editor perspective contains the standalone and path parameters. The path parameter must contain the complete path to the asset and the web address can end with #StandaloneEditorPerspective string. Also, by varying the path parameter, you can access a specific asset's editor in the standalone mode. Procedure Log in to Business Central. In a web browser, enter the appropriate web address as required, for example, For editing a process: http://localhost:8080/business-central/kie-wb.jsp?standalone&path=default://master@MySpace/Shop/src/main/resources/com/purchase.bpmn#StandaloneEditorPerspective The Process Designer opens in the standalone mode. For editing a form: http://localhost:8080/business-central/kie-wb.jsp?standalone&path=default://master@MySpace/Mortgage_Process/src/main/resources/ApplicationMortgage.frm#StandaloneEditorPerspective The Form Modeler opens in the standalone mode.

Commands:
Chapter 10. Revising project versions You can revise the version number of a project in Red Hat Decision Manager before you build and deploy a new instance of the project. Creating a new version of a project preserves the old version in case there is a problem with the new one and you need to revert back. Prerequisites KIE Server is deployed and connected to Business Central. Procedure In Business Central, go to Menu Design Projects . Click the project you want to deploy, for example Mortgages . Click Deploy . If there is no container with the project name, a container with default values is automatically created. If an older version of the project is already deployed, go to the project settings and change the project version. When finished, save the change and click Deploy . This will deploy a new version of the same project with the latest changes in place, alongside the older version(s). Note You can also select the Build & Install option to build the project and publish the KJAR file to the configured Maven repository without deploying to a KIE Server. In a development environment, you can click Deploy to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option is disabled and you can click Deploy only to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a corresponding project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode. To review project deployment details, click View deployment details in the deployment banner at the top of the screen or in the Deploy drop-down menu. This option directs you to the Menu Deploy Execution Servers page. To verify process definitions, click Menu Manage Process Definitions , and click . Click in the Actions column and select Start to start a new instance of the process.

Commands:
7.199. spice-vdagent 7.199.1. RHBA-2015:1392 - spice-vdagent bug fix update Updated spice-vdagent packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The spice-vdagent packages provide a SPICE agent for Linux guests. Bug Fixes BZ# 1117764 Previously, when using a SPICE client and the SPICE protocol to connect to a virtual machine, copying and pasting text to and from the client failed for certain applications running in the guest. This update ensures that the spice-vdagent utility properly handles the TIMESTAMP and STRING selection types, and the problem no longer occurs. BZ# 1209550 Prior to this update, SPICE agents in some cases did not properly store the resolution of the guest screen opened by virt viewer. Consequently, the resolution of the guest screen unintentionally changed in certain situations, such as after enabling and disabling a second guest screen. This update ensures that guest screen resolution is stored properly, and thus prevents the described problem. BZ# 1086657 Due to a race condition between the SPICE client and the guest's gnome-settings-daemon, using the SPICE client to re-enable a previously disabled guest display in some cases failed. This update ensures that gnome-settings-daemon no longer unintentionally attempts to enable or disable guest displays, which prevents the problem from occurring. BZ# 1206117 After disabling a guest display using the remote-viewer menu, the disabled display was in some cases immediately re-enabled. This update fixes the underlying code, and disabled guest displays no longer get automatically reactivated. Users of spice-vdagent are advised to upgrade to these updated packages, which fix these bugs.

Commands:
22.16.10. Configuring the Burst Option Using the burst option against a public server is considered abuse. Do not use this option with public NTP servers. Use it only for applications within your own organization. To increase the average quality of time offset statistics, add the following option to the end of a server command: burst At every poll interval, when the server responds, the system will send a burst of up to eight packets instead of the usual one packet. For use with the server command to improve the average quality of the time-offset calculations.

Commands: