mtpti5iD/redhat-docs_dataset huggingface dataset:
10.3. IBM Installation Tools IBM Installation Toolkit is an optional utility that speeds up the installation of Linux on IBM Power Systems and is especially helpful for those unfamiliar with Linux. You can use the IBM Installation Toolkit to: [1] Install and configure Linux on a non-virtualized IBM Power Systems server. Install and configure Linux on servers with previously-configured logical partitions (LPARs, also known as virtualized servers). Install IBM service and productivity tools on a new or previously installed Linux system. The IBM service and productivity tools include dynamic logical partition (DLPAR) utilities. Upgrade system firmware level on IBM Power Systems servers. Perform diagnostics or maintenance operations on previously installed systems. Migrate a LAMP server (software stack) and application data from a System x to a System p system. A LAMP server is a bundle of open source software. LAMP is an acronym for Linux, Apache HTTP Server , MySQL relational database, and the PHP (or sometimes Perl, or Python) language. Documentation for the IBM Installation Toolkit for PowerLinux is available in the Linux Information Center at https://www.ibm.com/support/pages/ibm-installation-toolkit-powerlinux-version-52-now-available PowerLinux service and productivity tools is an optional set of tools that include hardware service diagnostic aids, productivity tools, and installation aids for Linux operating systems on IBM servers based on POWER7, POWER6, POWER5, and POWER4 technology. [1] Parts of this section were previously published at IBM's Linux information for IBM systems resource.

Commands:
Chapter 2. access This chapter describes the commands under the access command. 2.1. access token create Create an access token Usage: Table 2.1. Command arguments Value Summary -h, --help Show this help message and exit --consumer-key <consumer-key> Consumer key (required) --consumer-secret <consumer-secret> Consumer secret (required) --request-key <request-key> Request token to exchange for access token (required) --request-secret <request-secret> Secret associated with <request-key> (required) --verifier <verifier> Verifier associated with <request-key> (required) Table 2.2. Output formatter options 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 2.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 2.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 2.5. Table formatter options 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 access token create [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty] --consumer-key <consumer-key> --consumer-secret <consumer-secret> --request-key <request-key> --request-secret <request-secret> --verifier <verifier>
7.84. iprutils 7.84.1. RHBA-2015:1305 - iprutils bug fix and enhancement update Updated iprutils packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The iprutils packages provide utilities to manage and configure Small Computer System Interface (SCSI) devices that are supported by the ipr SCSI storage device driver. Note The iprutils packages have been upgraded to upstream version 2.4.5, which provides a number of bug fixes and enhancements over the version. Notably, this update adds support for reporting cache hits on the Serial Attached SCSI (SAS) disk drive, and increases the speed of array creation for an advanced function (AF) direct-access storage device (DASD). (BZ# 1148147 ) Bug Fix BZ# 1146701 Previously, the format of firmware files was case sensitive. As a consequence, device attributes were not saved correctly for SIS-64 adapters after updating firmware with the pci.xxx file format. With this update, the firmware format is case insensitive, and device attributes are saved correctly in the described situation. Users of iprutils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 5. Known Issues If you upgrade VMs on Azure cloud launched from the "RHEL for SAP" (a discontinued offer) image of "gen1", and see an error similar to below, please ensure that /etc/hosts doesn't contain a line X.X.X.X rhui*.microsoft.com . This is an artifact IP address of Azure RHUI Content Distribution Server (CDS) instance to fetch the content from. Error: Stderr: Host and machine ids are equal (hash): refusing to link journals Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-eus-rhui-rpms', ignoring this repo. Failed to synchronize cache for repo 'microsoft-azure-rhel8-sapapps', ignoring this repo. Error: Unable to find a match: rhui-azure-rhel8-sapapps or Stderr: Host and machine ids are equal (hash): refusing to link journals Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-e4s-rhui-rpms', ignoring this repo. Failed to synchronize cache for repo 'microsoft-azure-rhel8-sap-ha', ignoring this repo. Error: Unable to find a match: rhui-azure-rhel8-sap-ha

Commands:
Stderr: Host and machine ids are equal (hash): refusing to link journals Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-eus-rhui-rpms', ignoring this repo. Failed to synchronize cache for repo 'microsoft-azure-rhel8-sapapps', ignoring this repo. Error: Unable to find a match: rhui-azure-rhel8-sapapps
Stderr: Host and machine ids are equal (hash): refusing to link journals Failed to synchronize cache for repo 'rhel-8-for-x86_64-appstream-e4s-rhui-rpms', ignoring this repo. Failed to synchronize cache for repo 'microsoft-azure-rhel8-sap-ha', ignoring this repo. Error: Unable to find a match: rhui-azure-rhel8-sap-ha
3.7.4. Additional Information For more information about TLS configuration and related topics, see the resources listed below. Installed Documentation config (1) - Describes the format of the /etc/ssl/openssl.conf configuration file. ciphers (1) - Includes a list of available OpenSSL keywords and cipher strings. /usr/share/httpd/manual/mod/mod_ssl.html - Contains detailed descriptions of the directives available in the /etc/httpd/conf.d/ssl.conf configuration file used by the mod_ssl module for the Apache HTTP Server . /usr/share/httpd/manual/ssl/ssl_howto.html - Contains practical examples of real-world settings in the /etc/httpd/conf.d/ssl.conf configuration file used by the mod_ssl module for the Apache HTTP Server . Online Documentation Red Hat Enterprise Linux 6 Security-Enhanced Linux - The Security-Enhanced Linux guide for Red Hat Enterprise Linux 6 describes the basic principles of SELinux . http://tools.ietf.org/html/draft-ietf-uta-tls-bcp-00 - Recommendations for secure use of TLS and DTLS .

Commands:
5.175. lsof 5.175.1. RHBA-2012:0442 - lsof bug fix update An updated lsof package that fixes two bugs is now available for Red Hat Enterprise Linux 6. The lsof (LiSt Open Files) package provides a utility to list information about files that are open and running on Linux and UNIX systems. Bug Fixes BZ# 747375 Previously, only the first "+e" or "-e" option was processed and the rest were ignored. Consequently it was not possible to exclude more than one file system from being subjected to kernel function calls. This update fixes this issue and lsof now functions as expected with multiple +e or -e options. BZ# 795799 Prior to this update, the lsof utility ignored the "-w" option if both the "-b" and the "-w" options were specified. As a consequence, lsof failed to suppress warning messages. Now, the -w option successfully suppresses warning messages. All users of lsof are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Chapter 1. Overview The atomic command-line tool provides a way to interact and manage Atomic Host systems and containers. It provides a high level, coherent entrypoint to the system and makes it easier to interact with special kinds of containers, such as super-privileged containers, and debugging tools. The atomic command uses tools such as docker , ostree and skopeo to manage containers and container host systems. There are also a lot of features built into the atomic command that are not available in the docker command. These features allow you to use special commands for image signing, image verification, the ability to install a container - mounting file systems and opening privileges. Understanding LABELs : Dockerfiles support storing default values for some commands that atomic can read and execute. These are called "LABEL" instructions and they make it easy to ship images with their own suggested values, and simplifies running complex docker commands. For example, if a Dockerfile contains the LABEL RUN , running atomic run <image> executes its contents. The commands in atomic that use labels are install , uninstall , mount , unmount , run , and stop .

Commands:
2.3. The /proc Virtual File System Unlike most file systems, /proc contains neither text nor binary files. Because it houses virtual files , the /proc is referred to as a virtual file system. These virtual files are typically zero bytes in size, even if they contain a large amount of information. The /proc file system is not used for storage. Its main purpose is to provide a file-based interface to hardware, memory, running processes, and other system components. Real-time information can be retrieved on many system components by viewing the corresponding /proc file. Some of the files within /proc can also be manipulated (by both users and applications) to configure the kernel. The following /proc files are relevant in managing and monitoring system storage: /proc/devices Displays various character and block devices that are currently configured. /proc/filesystems Lists all file system types currently supported by the kernel. /proc/mdstat Contains current information on multiple-disk or RAID configurations on the system, if they exist. /proc/mounts Lists all mounts currently used by the system. /proc/partitions Contains partition block allocation information. For more information about the /proc file system, see the Red Hat Enterprise Linux 7 Deployment Guide .

Commands:
13.4. Disabling Command-Line Access To disable command-line access for your desktop user, you need to make configuration changes in a number of different contexts. Bear in mind that the following steps do not remove the desktop user's permissions to access a command line, but rather remove the ways that the desktop user could access command line. Set the org.gnome.desktop.lockdown.disable-command-line GSettings key, which prevents the user from accessing the terminal or specifying a command line to be executed (the Alt + F2 command prompt). Disable switching to virtual terminals (VTs) with the Ctrl + Alt + function key shortcuts by modifying the X server configuration. Remove Terminal and any other application that provides access to the terminal from the Applications menu and Activities Overview in GNOME Shell. This is done by removing menu items for those applications. For detailed information on how to remove a menu item, see Section 12.1.2, "Removing a Menu Item for All Users" . 13.4.1. Setting the org.gnome.desktop.lockdown.disable-command-line Key Create a local database for machine-wide settings in /etc/dconf/db/local.d/00-lockdown : Override the user's setting and prevent the user from changing it in /etc/dconf/db/local.d/locks/lockdown : Update the system databases: Users must log out and back in again before the system-wide settings take effect. 13.4.2. Disabling Virtual Terminal Switching Users can normally use the Ctrl + Alt + function key shortcuts (for example Ctrl + Alt + F2 ) to switch from the GNOME Desktop and X server to a virtual terminal. You can disable access to all virtual terminals by adding a DontVTSwitch option to the Serverflags section in an X configuration file in the /etc/X11/xorg.conf.d/ directory. Procedure 13.4. Disabling Access to Virtual Terminals Create or edit an X configuration file in the /etc/X11/xorg.conf.d/ directory: Note By convention, these host-specific configuration file names start with two digits and a hyphen and always have the .conf extension. Thus, the following file name can be /etc/X11/xorg.conf.d/10-xorg.conf . Section "Serverflags" Option "DontVTSwitch" "yes" EndSection Restart the X server for your changes to take effect.

Commands:
Disable command-line access disable-command-line=true
Lock the disabled command-line access /org/gnome/desktop/lockdown
dconf update
Section "Serverflags" Option "DontVTSwitch" "yes" EndSection
Chapter 20. Manipulating the Domain XML This section describes the XML format used to represent domains. Here the term domain refers to the root <domain> element required for all guest virtual machine. The domain XML has two attributes: type specifies the hypervisor used for running the domain. The allowed values are driver specific, but include KVM and others. id is a unique integer identifier for the running guest virtual machine. Inactive machines have no id value. The sections in this chapter will address the components of the domain XML. Additional chapters in this manual may refer to this chapter when manipulation of the domain XML is required. Note This chapter is based on the libvirt upstream documentation . 20.1. General Information and Metadata This information is in this part of the domain XML: <domain type='xen' id='3'> <name>fv0</name> <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid> <title>A short description - title - of the domain</title> <description>Some human readable description</description> <metadata> <app1:foo xmlns:app1="http://app1.org/app1/">..</app1:foo> <app2:bar xmlns:app2="http://app1.org/app2/">..</app2:bar> </metadata> ... </domain> Figure 20.1. Domain XML metadata The components of this section of the domain XML are as follows: Table 20.1. General metadata elements Element Description <name> Assigns a name for the virtual machine. This name should consist only of alpha-numeric characters and is required to be unique within the scope of a single host physical machine. It is often used to form the filename for storing the persistent configuration files. <uuid> assigns a globally unique identifier for the virtual machine. The format must be RFC 4122-compliant, eg 3e3fce45-4f53-4fa7-bb32-11f34168b82b . If omitted when defining/creating a new machine, a random UUID is generated. It is also possible to provide the UUID with a sysinfo specification. <title> title Creates space for a short description of the domain. The title should not contain any newlines. <description> Different from the title, This data is not used by libvirt in any way, it can contain any information the user wants to display. <metadata> Can be used by applications to store custom metadata in the form of XML nodes/trees. Applications must use custom namespaces on their XML nodes/trees, with only one top-level element per namespace (if the application needs structure, they should have sub-elements to their namespace element)

Commands:
<domain type='xen' id='3'> <name>fv0</name> <uuid>4dea22b31d52d8f32516782e98ab3fa0</uuid> <title>A short description - title - of the domain</title> <description>Some human readable description</description> <metadata> <app1:foo xmlns:app1="http://app1.org/app1/">..</app1:foo> <app2:bar xmlns:app2="http://app1.org/app2/">..</app2:bar> </metadata> </domain>
Chapter 3. Knative Serving Knative Serving supports developers who want to create, deploy, and manage cloud-native applications . It provides a set of objects as Kubernetes custom resource definitions (CRDs) that define and control the behavior of serverless workloads on an OpenShift Container Platform cluster. Developers use these CRDs to create custom resource (CR) instances that can be used as building blocks to address complex use cases. For example: Rapidly deploying serverless containers. Automatically scaling pods. 3.1. Knative Serving resources Service The service.serving.knative.dev CRD automatically manages the life cycle of your workload to ensure that the application is deployed and reachable through the network. It creates a route, a configuration, and a new revision for each change to a user created service, or custom resource. Most developer interactions in Knative are carried out by modifying services. Revision The revision.serving.knative.dev CRD is a point-in-time snapshot of the code and configuration for each modification made to the workload. Revisions are immutable objects and can be retained for as long as necessary. Route The route.serving.knative.dev CRD maps a network endpoint to one or more revisions. You can manage the traffic in several ways, including fractional traffic and named routes. Configuration The configuration.serving.knative.dev CRD maintains the desired state for your deployment. It provides a clean separation between code and configuration. Modifying a configuration creates a new revision.

Commands:
Chapter 19. Using the Eclipse IDE for C and C++ Application Development Some developers prefer using an IDE instead of an array of command line tools. Red Hat makes available the Eclipse IDE with support for development of C and C++ applications. Using Eclipse to Develop C and C++ Applications A detailed description of the Eclipse IDE and its use for developing C and C++ applications is out of the scope of this document. Please refer to the resources linked below. Additional Resources Using Eclipse Eclipse documentation - C/C++ Development User Guide

Commands:
Chapter 3. Viewing your subscription inventory The All subscriptions table on the Subscription Inventory page contains detailed information about all of the subscriptions that your organization owns for an account. The account number is displayed in the table title. For example, if your account number is 12345, the All subscriptions table title displays as All subscriptions for account 12345 . The table columns show the following information for each subscription in your account: Name The name of the subscription and the product it applies to. SKU The combination of letters and numbers that represent the subscription stock keeping unit (SKU). Quantity The number of active subscriptions for a SKU. Service level The type of service level agreement (SLA) for the subscription, as defined within the terms of the contract. Examples include Premium, Standard, Self-Support or Layered. Prerequisites You are logged in to your Red Hat Hybrid Cloud Console account at console.redhat.com. You have the Subscriptions user role in the role-based access control (RBAC) system for the Red Hat Hybrid Cloud Console. Procedure To view your subscription inventory, perform the following steps: From the Home page, locate Red Hat Insights and click RHEL . From the Red Hat Insights menu, click Business > Subscriptions > Subscription Inventory . From the Subscriptions Inventory page, scroll to the All subscriptions table. Note The table displays up to 10 rows per page by default. You can customize the table to show up to 100 rows per page. Optional: Click the rows per page arrow to select the number of rows that you want to view on each page. Note Your subscription inventory might span more than one page. Use the and arrows to move between pages, if applicable. 3.1. Filtering by subscription status You can use the tiles to filter the All subscriptions table by subscription status (Active, Expired, Expiring soon, or Future dated). To filter your subscriptions by status, click a tile. For example, clicking the Active tile displays only active subscriptions in the table. The applied filter displays in the table header. To clear the filter, click Clear filters or close the applied filter in the table header. Note Currently, you can apply only one status filter at a time. However, you can use a status filter in conjunction with the search filter in the All subscriptions table. 3.2. Filtering by subscription name or SKU You can use the search bar in the table header to filter the subscriptions in your inventory by name or SKU. For example, if you type "A" into the search bar, the table shows only the subscriptions in your inventory that contain the letter "A" in either the Name or SKU field. Note The search is not case sensitive. Optionally, you can use the search filter in conjunction with the tile filter to filter only subscriptions of the selected status by name or SKU. For example, you can apply the Active tile filter and then type a character into the search bar to view only active subscriptions that contain the typed character in the name, the SKU, or both.

Commands:
function::print_ubacktrace_brief Name function::print_ubacktrace_brief - Print stack back trace for current user-space task. Synopsis Arguments None Description Equivalent to print_ubacktrace , but output for each symbol is shorter (just name and offset, or just the hex address of no symbol could be found). Note To get (full) backtraces for user space applications and shared shared libraries not mentioned in the current script run stap with -d /path/to/exe-or-so and/or add --ldd to load all needed unwind data.

Commands:
print_ubacktrace_brief()
6.2. Plan and Configure Security Updates All software contains bugs. Often, these bugs can result in a vulnerability that can expose your system to malicious users. Unpatched systems are a common cause of computer intrusions. You should have a plan to install security patches in a timely manner to close those vulnerabilities so they cannot be exploited. For home users, security updates should be installed as soon as possible. Configuring automatic installation of security updates is one way to avoid having to remember, but does carry a slight risk that something can cause a conflict with your configuration or with other software on the system. For business or advanced home users, security updates should be tested and scheduled for installation. Additional controls will need to be used to protect the system during the time between the patch release and its installation on the system. These controls would depend on the exact vulnerability, but could include additional firewall rules, the use of external firewalls, or changes in software settings.

Commands:
4.360. xorg-x11-server-utils 4.360.1. RHBA-2011:1617 - xorg-x11-server-utils bug fix and enhancement update Updated xorg-x11-server-utils packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The xorg-x11-server-utils package contains a collection of utilities used to modify and query the runtime configuration of the X.Org server. X.Org is an open source implementation of the X Window System. The xorg-x11-server-utils packages have been upgraded to upstream version 7.1 which provides a number of bug fixes and enhancements over the version. (BZ# 713862 ) Bug Fixes BZ# 657554 Previously, the xrandr options --scale and -- transform caused a segmentation fault, because these options required an --output field but the utility didn't validate the command line properly check for existing output. With this update, xrandr displays a message informing that the --scale and -- transform options also require the --output option. BZ# 740146 Previously, xrandr wrongly assumed that a gamma ramp value of zero was a failure. When VNC was enabled, xrandr returned a zero value. With this update, xrandr is modified to allow for a gamma ramp value of zero. Now xrandr no longer fails when running VNC. All users of xorg-x11-server-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: