mtpti5iD/redhat-docs_dataset huggingface dataset:
13.2.26. Creating Local System Users There can be times when it is useful to seed users into the SSSD database rather than waiting for users to login and be added. Note Adding user accounts manually requires the sssd-tools package to be installed. When creating new system users, it is possible to create a user within the SSSD local identity provider domain. This can be useful for creating new system users, for troubleshooting SSSD configuration, or for creating specialized or nested groups. New users can be added using the sss_useradd command. At its most basic, the sss_useradd command only requires the new user name. There are other options (listed in the sss_useradd(8) man page) which can be used to set attributes on the account, like the UID and GID, the home directory, or groups which the user belongs to.

Commands:
~]# sss_useradd jsmith
~]# sss_useradd --UID 501 --home /home/jsmith --groups admin,dev-group jsmith
Chapter 7. Templates 7.1. About Templates A template is a copy of a virtual machine that you can use to simplify the subsequent, repeated creation of similar virtual machines. Templates capture the configuration of software, configuration of hardware, and the software installed on the virtual machine on which the template is based. The virtual machine on which a template is based is known as the source virtual machine. When you create a template based on a virtual machine, a read-only copy of the virtual machine's disk is created. This read-only disk becomes the base disk image of the new template, and of any virtual machines created based on the template. As such, the template cannot be deleted while any virtual machines created based on the template exist in the environment. Virtual machines created based on a template use the same NIC type and driver as the original virtual machine, but are assigned separate, unique MAC addresses. You can create a virtual machine directly from Compute Templates , as well as from Compute Virtual Machines . In Compute Templates , select the required template and click New VM . For more information on selecting the settings and controls for the new virtual machine see Virtual Machine General settings explained .

Commands:
5.212. nspluginwrapper 5.212.1. RHSA-2012:1459 - Low: nspluginwrapper security and bug fix update Updated nspluginwrapper packages that fix one security issue and one bug are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. nspluginwrapper is a utility which allows 32-bit plug-ins to run in a 64-bit browser environment (a common example is Adobe's browser plug-in for presenting proprietary Flash files embedded in web pages). It includes the plug-in viewer and a tool for managing plug-in installations and updates. Security Fix CVE-2011-2486 It was not possible for plug-ins wrapped by nspluginwrapper to discover whether the browser was running in Private Browsing mode. This flaw could lead to plug-ins wrapped by nspluginwrapper using normal mode while they were expected to run in Private Browsing mode. Bug Fix BZ# 869554 When using the Adobe Reader web browser plug-in provided by the acroread-plugin package on a 64-bit system, opening Portable Document Format (PDF) files in Firefox could cause the plug-in to crash and a black window to be displayed where the PDF should be. Firefox had to be restarted to resolve the issue. This update implements a workaround in nspluginwrapper to automatically handle the plug-in crash, so that users no longer have to keep restarting Firefox. All users of nspluginwrapper are advised to upgrade to these updated packages, which upgrade nspluginwrapper to upstream version 1.4.4, and correct these issues. After installing the update, Firefox must be restarted for the changes to take effect.

Commands:
4.224. perl-Sys-Virt 4.224.1. RHBA-2011:1573 - perl-Sys-Virt bug fix and enhancement update An updated perl-Sys-Virt package that fixes one bug and adds one enhancement is now available for Red Hat Enterprise Linux 6. The perl-Sys-Virt package provides application programming interfaces (APIs) for managing virtual machines from Perl, using the libvirt library. Bug Fix BZ# 705792 Prior to this update, the flags argument was hardcoded to value 0 in virDomainGetXMLDesc. As a result, security sensitive domain information was not accessible using the libvirt perl bindings. This update adds the flags parameter to all get_xml_description methods. Now, the security sensitive domain information can be obtained as expected. Enhancement BZ# 717887 The Sys::Virt module has been updated to provide support for the new APIs introduced between version 0.8.7 and 0.9.3 of the libvirt library. All users of perl-Sys-Virt are advised to upgrade to this updated package, which fixes this bug and adds this enhancement.

Commands:
7.2. ImageMagick 7.2.1. RHBA-2015:1359 - ImageMagick bug fix and enhancement update Updated ImageMagick packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. ImageMagick is an image display and manipulation tool for the X Window System that can read and write multiple image formats. Note The ImageMagick packages have been upgraded to upstream version 6.7.2.7, which provides a number of bug fixes and enhancements over the version. Notably, it addresses a problem with conversion of Portable Network Graphics (PNG) images that caused the size of the converted file to be much larger than that of the original file. (BZ# 1158865 ) Users of ImageMagick are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 5. 20 June 2024 This release includes several enhancements, additions, and fixes that have been implemented in Red Hat Ansible Lightspeed. 5.1. New features and enhancements Red Hat Ansible Lightspeed on-premise deployment Red Hat Ansible Lightspeed is now available for on-premise deployments. This capability provides the Red Hat Ansible Automation Platform customers more control over their data and supports compliance with enterprise security policies. For example, organizations in sensitive industries with data privacy or air-gapped requirements can use on-premise deployments of both Red Hat Ansible Lightspeed and IBM watsonx Code Assistant for Red Hat Ansible Lightspeed on Cloud Pak for Data. Red Hat Ansible Lightspeed on-premise deployments are supported on Red Hat Ansible Automation Platform version 2.4. For more information, see Setting up Red Hat Ansible Lightspeed on-premise deployment . Note The following capabilities are not yet available on Red Hat Ansible Lightspeed on-premise deployments: Viewing telemetry data on the Admin dashboard Generating playbooks and viewing playbook explanations Playbook generation and explanations Using the Ansible VS Code extension, you can create Ansible playbooks using a natural language interface in English. Red Hat Ansible Lightspeed with IBM watsonx Code Assistant reads the natural language prompts and generates an entire playbook recommendation based on your intent. You can also view the explanations for new or existing playbooks. The playbook explanations describe what the playbook or task within the playbook does and contextualize its impact. For more information, see Creating playbooks and viewing playbook explanations .

Commands:
Chapter 2. Parameters \u00ad\u00ad\u00ad\u00adThese parameters of an existing two-node cluster are used to setup the third site: Parameter Example Description SID RH2 System ID of the HANA Database First SITE DC1 Name of the first datacenter /site Second SITE DC2 Name of the second datacenter / site Third SITE DC3 Name of the third datacenter / site InstanceNr 02 HANA Instance Number <sid>adm uid 1000 User-ID of sidadm user sapsys gid 980 Group ID of sapsys It is required that all three HANA instances use the same values for the following: SID InstanceNr <sid>adm uid sapsys gid

Commands:
14.9.3. Related Books The Official Samba-3 HOWTO-Collection by John H. Terpstra and Jelmer R. Vernooij; Prentice Hall - The official Samba-3 documentation as issued by the Samba development team. This is more of a reference guide than a step-by-step guide. Samba-3 by Example by John H. Terpstra; Prentice Hall - This is another official release issued by the Samba development team which discusses detailed examples of OpenLDAP, DNS, DHCP, and printing configuration files. This has step-by-step related information that helps in real-world implementations. Using Samba, 2nd Edition by Jay T's, Robert Eckstein, and David Collier-Brown; O'Reilly - A good resource for novice to advanced users, which includes comprehensive reference material.

Commands:
1.6. Enabling a Software Collection The scl tool is used to enable a Software Collection and to run applications in the Software Collection environment. General usage of the scl tool can be described using the following syntax: scl action software_collection_1 software_collection_2 command If you are running a command with multiple arguments, remember to enclose the command and its arguments in quotes: scl action software_collection_1 software_collection_2 'command --argument' Alternatively, use a -- command separator to run a command with multiple arguments: scl action software_collection_1 software_collection_2 -- command --argument Remember that: When you run the scl tool, it creates a child process (subshell) of the current shell. Running the command again then creates a subshell of the subshell. You can list enabled Software Collections for the current subshell. See Section 1.7, "Listing Enabled Software Collections" for more information. You have to disable an enabled Software Collection first to be able to enable it again. To disable the Software Collection, exit the subshell created when enabling the Software Collections. When using the scl tool to enable a Software Collection, you can only perform one action with the enabled Software Collection at a time. The enabled Software Collection must be disabled first before performing another action. 1.6.1. Running an Application Directly For example, to directly run Perl with the --version option in the Software Collection named software_collection_1 , execute the following command: scl enable software_collection_1 'perl --version' Alternatively, you can provide a syspaths subpackage that makes it more convenient to run commands in the Software Collection environment. For more information on syspaths subpackages, see Section 3.3, "Providing syspaths Subpackages" . 1.6.2. Running a Shell with Multiple Software Collections Enabled To run the Bash shell in the environment with multiple Software Collections enabled, execute the following command: scl enable software_collection_1 software_collection_2 bash The command above enables two Software Collections, named software_collection_1 and software_collection_2 . 1.6.3. Running Commands Stored in a File To execute a number of commands, which are stored in a file, in the Software Collection environment, run the following command: cat cmd | scl enable software_collection_1 - The command above executes commands, which are stored in the cmd file, in the environment of the Software Collection named software_collection_1 .

Commands:
11.4.2.2. Flags Flags are essential to determine how or if a recipe's conditions are compared to a message. The following flags are commonly used: A - Specifies that this recipe is only used if the recipe without an A or a flag also matched this message. a - Specifies that this recipe is only used if the recipe with an A or a flag also matched this message and was successfully completed. B - Parses the body of the message and looks for matching conditions. b - Uses the body in any resulting action, such as writing the message to a file or forwarding it. This is the default behavior. c - Generates a carbon copy of the email. This is useful with delivering recipes, since the required action can be performed on the message and a copy of the message can continue being processed in the rc files. D - Makes the egrep comparison case-sensitive. By default, the comparison process is not case-sensitive. E - While similar to the A flag, the conditions in the recipe are only compared to the message if the immediately preceding the recipe without an E flag did not match. This is comparable to an else action. e - The recipe is compared to the message only if the action specified in the immediately preceding recipe fails. f - Uses the pipe as a filter. H - Parses the header of the message and looks for matching conditions. This occurs by default. h - Uses the header in a resulting action. This is the default behavior. w - Tells Procmail to wait for the specified filter or program to finish, and reports whether or not it was successful before considering the message filtered. W - Is identical to w except that "Program failure" messages are suppressed. For a detailed list of additional flags, refer to the procmailrc man page.

Commands:
Chapter 2. Other installable plugins The following Technology Preview plugins are not preinstalled and must be installed from an external source: Name Plugin Version Installation Details Ansible Automation Platform Frontend @ansible/plugin-backstage-rhaap 1.0.0 Learn more Ansible Automation Platform @ansible/plugin-backstage-rhaap-backend 1.0.0 Ansible Automation Platform Scaffolder Backend @ansible/plugin-scaffolder-backend-module-backstage-rhaap 1.0.0 Orchestrator Frontend @janus-idp/backstage-plugin-orchestrator 1.22.6 Learn more Orchestrator Backend @janus-idp/backstage-plugin-orchestrator-backend-dynamic 1.22.9 Note The above Red Hat Ansible Automation Platform (RHAAP) plugins, can be used as a replacement for the older plugin listed in the Technology Preview plugins section of the Configuring plugins in Red Hat Developer Hub guide .

Commands:
8.169. pcp 8.169.1. RHEA-2014:1477 - pcp enhancement update New pcp packages are now available for Red Hat Enterprise Linux 6. Performance Co-Pilot (PCP) is a suite of tools, services, and libraries for acquisition, archiving, and analysis of system-level performance measurements. Its light-weight, distributed architecture makes it particularly well suited to centralized analysis of complex systems. This enhancement update adds the pcp packages to Red Hat Enterprise Linux 6. (BZ# 640150 ) All users who require pcp are advised to install these new packages.

Commands:
Chapter 24. Implementing Federation Red Hat supports federation using Red Hat Single Sign-on (RH-SSO) or Microsoft Active Directory Federation Services (AD FS) in combination with Red Hat OpenStack Platform (RHOSP). 24.1. Federate with IdM using Red Hat Single Sign-On You can use Red Hat Single Sign-On (RH-SSO) to federate your IdM users for OpenStack authentication (authN). Federation allows your IdM users to login to the OpenStack Dashboard without revealing their credentials to any OpenStack services. Instead, when Dashboard needs a user's credentials, it will forward the user to RH-SSO and allow them to enter their IdM credentials there. As a result, RH-SSO asserts back to Dashboard that the user has successfully authenticated, and Dashboard then allows the user to access the project. 24.2. The federation workflow This section describes how the Identity service (keystone), RH-SSO and IdM interact with each other. Federation in OpenStack uses the concept of Identity Providers and Service Providers: Identity Provider (IdP) - the service that stores the user accounts. In this case, the user accounts held in IdM, are presented to Keystone using RH-SSO. Service Provider (SP) - the service that requires authentication from the users in the IdP. In this case, keystone is the service provider that grants Dashboard access to IdM users. You can configure the Identity service (the SP) to communicate with RH-SSO (the IdP), which is also able to serve as a universal adapter for other IdPs. In this configuration, you can point keystone at RH-SSO, and RH-SSO will forward requests on to the Identity Providers that it supports (known as authentication modules), these currently include IdM and Active Directory. This is done by having the Service Provider (SP) and Identity Provider (IdP) exchange metadata, which each sysadmin then makes a decision to trust. The result is that the IdP can confidently make assertions, and the SP can then receive these assertions. Additional resources Federation using Red Hat OpenStack Platform and Red Hat Single Sign-On

Commands:
Chapter 3. Attaching a Host-based Subscription to Hypervisors Use this procedure to attach a host-based subscription, such as Red Hat Enterprise Linux for Virtual Datacenters , to hypervisors that are already registered to Red Hat Satellite. To register a new hypervisor, ensure your host activation key includes a host-based subscription, then see Registering Hosts to Satellite in Managing Hosts . You must register a hypervisor before configuring virt-who to query it. Prerequisites Import a Subscription Manifest that includes a host-based subscription into Satellite Server. Ensure you have sufficient entitlements for the host-based subscription to cover all of the hypervisors you plan to use. Procedure In the Satellite web UI, navigate to Hosts > Content Hosts . In the Content Hosts list, select the check box to the name of each hypervisor you want to attach the subscription to. From the Select Action list, select Manage Subscriptions . In the Content Host Bulk Subscriptions window, select a host-based subscription, then click Add Selected . For CLI Users On Satellite Server, list the available subscriptions to find the host-based subscription's ID: Attach the host-based subscription to a hypervisor: Repeat these steps for each hypervisor you plan to use.

Commands:
hammer subscription list --organization-id organization_id
hammer host subscription attach --host host_name --subscription-id subscription_id
7.151. pam_passwdqc 7.151.1. RHBA-2015:0712 - pam_passwdqc bug fix update Updated pam_passwdqc packages that fix one bug are now available for Red Hat Enterprise Linux 6. The pam_passwdqc packages provide a simple password strength checking module for PAM (Pluggable Authentication Module) aware password changing programs, such as passwd(1). In addition to checking regular passwords, the module offers support for passphrases and can provide randomly generated passwords. All the features of the module are optional and can be reconfigured without rebuilding. Bug Fix BZ# 889545 Previously, the pam_passwdqc man page contained an unclear description of the relationship between the minimum password length and complexity. Consequently, users of this PAM module reading the man page could misinterpret the actual requirements for sufficiently secure passwords. With this update, a detailed description of the required password complexity for various lengths has been provided in the man page, and as a result, the documentation is no longer ambiguous. Users of pam_passwdqc are advised to upgrade to these updated packages, which fix this bug.

Commands:
1.4. Installing a Software Collection To ensure that a Software Collection is on your system, install the so-called metapackage of the Software Collection. Thanks to Software Collections being fully compatible with the RPM Package Manager, you can use conventional tools like Yum or PackageKit for this task. For example, to install a Software Collection with the metapackage named software_collection_1 , run the following command: This command will automatically install all the packages in the Software Collection that are essential for the user to perform most common tasks with the Software Collection. Software Collections allow you to only install a subset of packages you intend to use. For example, to use the Ruby interpreter from the rh-ruby23 Software Collection, you only need to install a package rh-ruby23-ruby from that Software Collection. If you install an application that depends on a Software Collection, that Software Collection will be installed along with the rest of the application's dependencies. For detailed information on Software Collection metapackages, see Section 2.7.1, "Metapackage" . For detailed information on Yum and PackageKit usage, see the Red Hat Enterprise Linux 7 System Administrator's Guide , or the Red Hat Enterprise Linux 6 Deployment Guide .

Commands:
yum install software_collection_1
6.14. RHEA-2013:0284 - new package: cpupowerutils New cpupowerutils packages are now available for Red Hat Enterprise Linux 6. The cpupowerutils packages provide a suite of tools to manage power states on appropriately enabled central processing units (CPU). This enhancement update adds the cpupowerutils packages to Red Hat Enterprise Linux 6. (BZ#697418) All users who require cpupowerutils are advised to install these new packages.

Commands:
B.17.2. XML Syntax Errors Syntax errors are caught by the XML parser. The error message contains information for identifying the problem. This example error message from the XML parser consists of three lines - the first line denotes the error message, and the two following lines contain the context and location of the XML code containing the error. The third line contains an indicator showing approximately where the error lies on the line above it: Information contained in this message: ( name_of_guest.xml ) This is the file name of the document that contains the error. File names in parentheses are symbolic names to describe XML documents parsed from memory, and do not directly correspond to files on disk. File names that are not contained in parentheses are local files that reside on the target of the connection. 6 This is the line number in the XML file that contains the error. StartTag: invalid element name This is the error message from the libxml2 parser, which describes the specific XML error. B.17.2.1. Stray < in the document Symptom The following error occurs: Investigation This error message shows that the parser expects a new element name after the < symbol on line 6 of a guest's XML file. Ensure line number display is enabled in your text editor. Open the XML file, and locate the text on line 6: This snippet of a guest's XML file contains an extra < in the document: Solution Remove the extra < or finish the new element.

Commands:
error: ( name_of_guest.xml ):6: StartTag: invalid element name <vcpu>2</vcpu>< -----------------^
error: ( name_of_guest.xml ):6: StartTag: invalid element name <vcpu>2</vcpu>< -----------------^
<domain type='kvm'> <name> name_of_guest </name> <memory>524288</memory> <vcpu>2</vcpu><
5.2. Lock States A lock state indicates the current status of a lock request. A lock is always in one of three states: Granted - The lock request succeeded and attained the requested mode. Converting - A client attempted to change the lock mode and the new mode is incompatible with an existing lock. Blocked - The request for a new lock could not be granted because conflicting locks exist. A lock's state is determined by its requested mode and the modes of the other locks on the same resource.

Commands: