mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 14. Starting and stopping a Directory Server instance You can start, stop, and restart a Directory Server instance by using the command line or the web console. 14.1. Starting and stopping a Directory Server instance by using the command line Use the dsctl utility to start, stop, or restart a Directory Server instance. Important The dsctl utility is the only correct way to stop the Directory Server instances. Do not use the kill command to terminate the ns-slapd process to avoid any data loss and corruption. Procedure To start the instance, run: To stop the instance, run: To restart the instance, run: Optionally, you can enable Directory Server instances to automatically start when the system boots: For a single instance, run: For all instances on a server, run: Verification You can check the instance status by using the dsctl or systemctl utility: To view the instance status by using the dsctl utility, run: To view the instance status by using the systemctl utility, run: Additional resources Managing system services with systemctl 14.2. Starting and stopping a Directory Server instance by using the web console You can use the web console to start, stop, or restart a Directory Server instance. Prerequisites You are logged in to the web console. For more details, see Logging in to the Directory Server by using the web console Procedure Select the Directory Server instance. Click the Actions button and select the action to execute: Start Instance Stop Instance Restart Instance Verification Ensure that the Directory Server instance is running. When the instance is not running, the web console displays the following message:

Commands:
dsctl instance_name start
dsctl instance_name stop
dsctl instance_name restart
systemctl enable dirsrv@ instance_name
systemctl enable dirsrv.target
dsctl instance_name status
systemctl status dirsrv@ instance_name
This server instance is not running, either start it from the Actions dropdown menu, or choose a different instance.
Chapter 5. Profiles There are features in Red Hat Single Sign-On that are not enabled by default, these include features that are not fully supported. In addition there are some features that are enabled by default, but that can be disabled. The features that can be enabled and disabled are: Name Description Enabled by default Support level account2 New Account Management Console No Preview account_api Account Management REST API No Preview admin_fine_grained_authz Fine-Grained Admin Permissions No Preview docker Docker Registry protocol No Supported impersonation Ability for admins to impersonate users Yes Supported openshift_integration Extension to enable securing OpenShift No Preview scripts Write custom authenticators using JavaScript No Preview token_exchange Token Exchange Service No Preview upload_scripts Upload scripts through the Red Hat Single Sign-On REST API No Deprecated web_authn W3C Web Authentication (WebAuthn) No Preview To enable all preview features start the server with: You can set this permanently by creating the file standalone/configuration/profile.properties (or domain/servers/server-one/configuration/profile.properties for server-one in domain mode). Add the following to the file: To enable a specific feature start the server with: For example to enable Docker use -Dkeycloak.profile.feature.docker=enabled . You can set this permanently in the profile.properties file by adding: To disable a specific feature start the server with: For example to disable Impersonation use -Dkeycloak.profile.feature.impersonation=disabled . You can set this permanently in the profile.properties file by adding:

Commands:
bin/standalone.sh|bat -Dkeycloak.profile=preview
profile=preview
bin/standalone.sh|bat -Dkeycloak.profile.feature.<feature name>=enabled
feature.docker=enabled
bin/standalone.sh|bat -Dkeycloak.profile.feature.<feature name>=disabled
feature.impersonation=disabled
Chapter 8. Installation and Booting The NO_DHCP_HOSTNAME option has been added The NO_DHCP_HOSTNAME option can now be specified in the /etc/sysconfig/network configuration file. Previously, in certain situations it was not possible to prevent initialization scripts from obtaining the host name through DHCP, even when using a static configuration. With this update, if the NO_DHCP_HOSTNAME option is set to yes , true , or 1 in the /etc/sysconfig/network file, initialization scripts are prevented from obtaining the host name through DHCP. (BZ# 1157856 )

Commands:
Chapter 12. Downloading the Red Hat Process Automation Manager installation files You can use the installer JAR file or deployable ZIP files to install Red Hat Process Automation Manager. You can run the installer in interactive or command line interface (CLI) mode. Alternatively, you can extract and configure the Business Central and KIE Server deployable ZIP files. If you want to run Business Central without deploying it to an application server, download the Business Central Standalone JAR file. Download a Red Hat Process Automation Manager distribution that meets your environment and installation requirements. Procedure Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options: Product: Process Automation Manager Version: 7.13.5 Download one of the following product distributions, depending on your preferred installation method: Note You only need to download one of these distributions. If you want to use the installer to install Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4, download Red Hat Process Automation Manager 7.13.5 Installer ( rhpam-installer-7.13.5.jar ). The installer graphical user interface guides you through the installation process. If you want to install Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 using the deployable ZIP files, download the following files: Red Hat Process Automation Manager 7.13.5 KIE Server for All Supported EE8 Containers ( rhpam-7.13.5-kie-server-ee8.zip ) Red Hat Process Automation Manager 7.13.5 Business Central Deployable for EAP 7 ( rhpam-7.13.5-business-central-eap7-deployable.zip ) Red Hat Process Automation Manager 7.13.5 Add Ons ( rhpam-7.13.5-add-ons.zip ) To run Business Central without needing to deploy it to an application server, download Red Hat Process Automation Manager 7.13.5 Business Central Standalone ( rhpam-7.13.5-business-central-standalone.jar ).

Commands:
Chapter 151. KafkaMirrorMaker2ClusterSpec schema reference Used in: KafkaMirrorMaker2Spec Full list of KafkaMirrorMaker2ClusterSpec schema properties Configures Kafka clusters for mirroring. Use the config properties to configure Kafka options, restricted to those properties not managed directly by Streams for Apache Kafka. For client connection using a specific cipher suite for a TLS version, you can configure allowed ssl properties . You can also configure the ssl.endpoint.identification.algorithm property to enable or disable hostname verification. 151.1. KafkaMirrorMaker2ClusterSpec schema properties Property Property type Description alias string Alias used to reference the Kafka cluster. bootstrapServers string A comma-separated list of host:port pairs for establishing the connection to the Kafka cluster. tls ClientTls TLS configuration for connecting MirrorMaker 2 connectors to a cluster. authentication KafkaClientAuthenticationTls , KafkaClientAuthenticationScramSha256 , KafkaClientAuthenticationScramSha512 , KafkaClientAuthenticationPlain , KafkaClientAuthenticationOAuth Authentication configuration for connecting to the cluster. config map The MirrorMaker 2 cluster config. Properties with the following prefixes cannot be set: ssl., sasl., security., listeners, plugin.path, rest., bootstrap.servers, consumer.interceptor.classes, producer.interceptor.classes (with the exception of: ssl.endpoint.identification.algorithm, ssl.cipher.suites, ssl.protocol, ssl.enabled.protocols).

Commands:
1.7. Issues with Live Migration of VMs in a RHEL cluster Information on support policies for RHEL high availability clusters with virtualized cluster members can be found in Support Policies for RHEL High Availability Clusters - General Conditions with Virtualized Cluster Members . As noted, Red Hat does not support live migration of active cluster nodes across hypervisors or hosts. If you need to perform a live migration, you will first need to stop the cluster services on the VM to remove the node from the cluster, and then start the cluster back up after performing the migration. The following steps outline the procedure for removing a VM from a cluster, migrating the VM, and restoring the VM to the cluster. Note Before performing this procedure, consider the effect on cluster quorum of removing a cluster node. For example, if you have a three node cluster and you remove one node, your cluster can withstand only one more node failure. If one node of a three node cluster is already down, removing a second node will lose quorum. If any preparations need to be made before stopping or moving the resources or software running on the VM to migrate, perform those steps. Move any managed resources off the VM. If there are specific requirements or preferences for where resources should be relocated, then consider creating new location constraints to place the resources on the correct node. Place the VM in standby mode to ensure it is not considered in service, and to cause any remaining resources to be relocated elsewhere or stopped. Run the following command on the VM to stop the cluster software on the VM. Perform the live migration of the VM. Start cluster services on the VM. Take the VM out of standby mode. If you created any temporary location constraints before putting the VM in standby mode, adjust or remove those constraints to allow resources to go back to their normally preferred locations.

Commands:
pcs cluster standby VM
pcs cluster stop
pcs cluster start
pcs cluster unstandby VM
Chapter 3. Edit the Environment File The environment file contains the back end settings that you must configure. It also contains settings relevant to the deployment of the Shared File Systems service. For more information about environment files, see Environment Files in the Advanced Overcloud Customization guide. This release includes an integrated environment file to define a native CephFS back end, and it contains default settings used to deploy the Shared File Systems service. This file is located in the following location on the undercloud node: /usr/share/openstack-tripleo-heat-templates/environments/manila-cephfsnative-config.yaml Procedure Create an environment file to contain the required environmental settings: The following code snippet shows the default values used by director when it deploys the Shared File Systems service: 1 The parameter_defaults header signifies the start of your configuration. Specifically, it allows you to override default values set in resource_registry . This includes values set by OS::Tripleo::Services::ManilaBackendCephFs , which sets defaults for a CephFS back end. 2 With ManilaCephFSNativeDriverHandlesShareServers set to false , the driver will not handle the lifecycle of the share server. 3 ManilaCephFSNativeCephFSConfPath: sets the path to the configuration file of the Ceph cluster. 4 ManilaCephFSNativeCephFSAuthId: is the Ceph auth ID that the director will create for share access.

Commands:
~/templates/manila-cephfsnative-config.yaml
./home/stack/templates/manila-cephfsnative-config.yaml
parameter_defaults: # 1 ManilaCephFSNativeBackendName: cephfsnative ManilaCephFSNativeDriverHandlesShareServers: false # 2 ManilaCephFSNativeCephFSConfPath: '/etc/ceph/ceph.conf' # 3 ManilaCephFSNativeCephFSAuthId: 'manila' # 4 ManilaCephFSNativeCephFSClusterName: 'ceph' ManilaCephFSNativeCephFSEnableSnapshots: true
9.3.3. Domain vCPU Threads In addition to tuning domain processes, libvirt also permits the setting of the pinning policy for each vcpu thread in XML configuration. This is done inside the <cputune> tags: <cputune> <vcpupin vcpu="0" cpuset="1-4,^2"/> <vcpupin vcpu="1" cpuset="0,1"/> <vcpupin vcpu="2" cpuset="2,3"/> <vcpupin vcpu="3" cpuset="0,4"/> </cputune> In this tag, libvirt uses either cgroup or sched_setaffinity(2) to pin the vcpu thread to the specified cpuset. Note For more details on cputune, refer to the following URL: http://libvirt.org/formatdomain.html#elementsCPUTuning In addition, if you need to set up a virtual machines with more vCPU than a single NUMA node, configure the host so that the guest detects a NUMA topology on the host. This allows for 1:1 mapping of CPUs, memory, and NUMA nodes. For example, this can be applied with a guest with 4 vCPUs and 6 GB memory, and a host with the following NUMA settings: In this scenario, use the following Domain XML setting: <cputune> <vcpupin vcpu="0" cpuset="1"/> <vcpupin vcpu="1" cpuset="5"/> <vcpupin vcpu="2" cpuset="2"/> <vcpupin vcpu="3" cpuset="6"/> </cputune> <numatune> <memory mode="strict" nodeset="1-2"/> </numatune> <cpu> <numa> <cell id="0" cpus="0-1" memory="3" unit="GiB"/> <cell id="1" cpus="2-3" memory="3" unit="GiB"/> </numa> </cpu>

Commands:
<cputune> <vcpupin vcpu="0" cpuset="1-4,^2"/> <vcpupin vcpu="1" cpuset="0,1"/> <vcpupin vcpu="2" cpuset="2,3"/> <vcpupin vcpu="3" cpuset="0,4"/> </cputune>
4 available nodes (0-3) Node 0: CPUs 0 4, size 4000 MiB Node 1: CPUs 1 5, size 3999 MiB Node 2: CPUs 2 6, size 4001 MiB Node 3: CPUs 0 4, size 4005 MiB
<cputune> <vcpupin vcpu="0" cpuset="1"/> <vcpupin vcpu="1" cpuset="5"/> <vcpupin vcpu="2" cpuset="2"/> <vcpupin vcpu="3" cpuset="6"/> </cputune> <numatune> <memory mode="strict" nodeset="1-2"/> </numatune> <cpu> <numa> <cell id="0" cpus="0-1" memory="3" unit="GiB"/> <cell id="1" cpus="2-3" memory="3" unit="GiB"/> </numa> </cpu>
2.5. Configuring a High Availability Application After creating a cluster and configuring fencing for the nodes in the cluster, you define and configure the components of the high availability service you will run on the cluster. To complete your cluster setup, perform the following steps. Configure shared storage and file systems required by your application. For information on high availability logical volumes, see Appendix F, High Availability LVM (HA-LVM) . For information on the GFS2 clustered file system, see the Global File System 2 manual. Optionally, you can customize your cluster's behavior by configuring a failover domain. A failover domain determines which cluster nodes an application will run on in what circumstances, determined by a set of failover domain configuration options. For information on failover domain options and how they determine a cluster's behavior, see the High Availability Add-On Overview . For information on configuring failover domains, see Section 4.8, "Configuring a Failover Domain" . Configure cluster resources for your system. Cluster resources are the individual components of the applications running on a cluster node. For information on configuring cluster resources, see Section 4.9, "Configuring Global Cluster Resources" . Configure the cluster services for your cluster. A cluster service is the collection of cluster resources required by an application running on a cluster node that can fail over to another node in a high availability cluster. You can configure the startup and recovery policies for a cluster service, and you can configure resource trees for the resources that constitute the service, which determine startup and shutdown order for the resources as well as the relationships between the resources. For information on service policies, resource trees, service operations, and resource actions, see the High Availability Add-On Overview . For information on configuring cluster services, see Section 4.10, "Adding a Cluster Service to the Cluster" .

Commands:
6. Security OpenSCAP OpenSCAP is a set of open source libraries that support the Security Content Automation Protocol (SCAP) standards from the National Institute of Standards and Technology (NIST). OpenSCAP supports the SCAP components: Common Vulnerabilities and Exposures (CVE) Common Platform Enumeration (CPE) Common Configuration Enumeration (CCE) Common Vulnerability Scoring System (CVSS) Open Vulnerability and Assessment Language (OVAL) Extensible Configuration Checklist Description Format (XCCDF) Additionally, the openSCAP package includes an application to generate SCAP reports about system configuration. openSCAP is now a fully supported package in Red Hat Enterprise Linux 6.1. Smartcard support for SPICE The Simple Protocol for Independent Computing Environments (SPICE) is a remote display protocol designed for virtual environments. SPICE users can view a virtualized desktop or server from the local system or any system with network access to the server. Red Hat Enterprise Linux 6.1 introduces support for smartcard passthough via the SPICE protocol. Note The Security Guide assists users and administrators in learning the processes and practices of securing workstations and servers against local and remote intrusion, exploitation and malicious activity.

Commands:
2.48. RHEA-2011:0604 - new package: virt-what A new virt-what package is now available for Red Hat Enterprise Linux 6. The virt-what tool is used to detect whether the operating system is running inside a virtual machine. This enhancement update adds a new virt-what package to Red Hat Enterprise Linux 6. The virt-what utility enables programs to detect if they are running in a virtual machine, as well as details about the type of hypervisor. (BZ# 627886 ) All users requiring virt-what should install this newly-released package, which adds this enhancement.

Commands:
12.29. SAP Gateway Translator Teiid provides a translator for SAP Gateway using the OData protocol. This translator is extension of OData Translator and uses Teiid WS resource adapter for making web service calls. This translator understands the most of the SAP specific OData extensions to the metadata. When the metadata is imported from SAP Gateway, the Teiid models are created to accordingly for SAP specific EntitySet and Property annotations. These "execution properties" are supported in this translator: Table 12.30. Execution Properties Property Description Default DatabaseTimeZone The time zone of the database. Used when fetchings date, time, or timestamp values The system default time zone SupportsOdataCount Supports USDcount True SupportsOdataFilter Supports USDfilter True SupportsOdataOrderBy Supports USDorderby True SupportsOdataSkip Supports USDskip True SupportsOdataTop Supports USDtop True Warning If metadata on your service defined "pagable" and/or "topable" as "false' on any table, you must turn off "SupportsOdataTop" and "SupportsOdataSkip" execution-properties in your translator, so that you will not end up with wrong results. SAP metadata has capability to control these in a fine grained fashion any on EnitySet, however Teiid can only control these at translator level. Warning Sample examples defined at http://scn.sap.com/docs/DOC-31221, we found to be lacking in full metadata in certain examples. For example, "filterable" clause never defined on some properties, but if you send a request USDfilter it will silently ignore it. You can verify this behavior by directly executing the REST service using a web browser with respective query. So, Make sure you have implemented your service correctly, or you can turn off certain features in this translator by using "execution properties" override.

Commands:
13.20. Installation Complete Congratulations! Your Red Hat Enterprise Linux installation is now complete! Click the Reboot button to reboot your system and begin using Red Hat Enterprise Linux. Remember to remove any installation media if it is not ejected automatically upon reboot. After your computer's normal power-up sequence has completed, Red Hat Enterprise Linux loads and starts. By default, the start process is hidden behind a graphical screen that displays a progress bar. Eventually, a GUI login screen (or if the X Window System is not installed, a login: prompt) appears. If your system was installed with the X Window System during this installation process, the first time you start your Red Hat Enterprise Linux system, applications to set up your system are launched. These applications guide you through initial configuration of Red Hat Enterprise Linux and allow you to set your system time and date, register your machine with Red Hat Network, and more. See Chapter 30, Initial Setup for information about the configuration process.

Commands:
8.217. shadow-utils 8.217.1. RHBA-2014:1522 - shadow-utils bug fix update Updated shadow-utils packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The shadow-utils packages include programs for converting UNIX password files to the shadow password format, as well as utilities for managing user and group accounts. Bug Fixes BZ# 787742 Previously, pwconv and grpconv utilities improperly parsed respective shadow and gshadow files with errors. Consequently, when writing corrected shadow and gshadow files, only the first error on two consecutive erroneous lines was corrected. With this update, pwconv and grpconv parse the files with errors correctly, and all lines are corrected in the newly written files. BZ# 890222 Due to a bug in code parsing in the /etc/group file, the useradd command could terminate unexpectedly with a segmentation fault when merging group entries. The parsing code has been fixed, and useradd now correctly merges group entries. BZ# 955769 Previously, the useradd command assigned the SELinux user to the new user being created after creating and populating the home directory of the user. Consequently, the SELinux contexts of the home directory files were incorrect. With this update, the SELinux user is assigned to the newly created user before populating the home directory, and the SELinux contexts on the home directory files for newly created users are now correct. BZ# 956742 Due to improper detection of invalid date specification in the chage command, chage did not fail when used with invalid date specification. With this update, the code of chage properly detects invalid date specification, and fails if an invalid date is specified. BZ# 957782 Prior to this update, the chage command incorrectly handled date in the format of "[month] DD YYYY" as "[month] DD hhmm". As a consequence, if chage was used with such date specification, the date was set to an unexpected value. The updated chage code correctly handles date in the aforementioned format. As a result, if chage is used with such date specification, the date is set to an expected value. BZ# 993049 Previously, the newgrp command always tried to find a group with a matching group ID (GID) within all the groups on the system. If the groups were stored on the LDAP server, it caused large data to be pulled from the LDAP server on each invocation of newgrp. The underlying source code has been fixed, and newgrp no longer tries to find a matching group among all the groups on the system if the user is a member of the group specified on the command line. Thus no extra data is pulled from the LDAP server. BZ# 1016516 The usermod code handled improperly the creation of a new entry in the /etc/shadow file. As a consequence, the "usermod -p" command failed to set the new password if the entry in the /etc/shadow file was missing. The updated usermod code properly creates a new entry in /etc/shadow if it is missing, and the "usermod -p" command sets the new password correctly even if the user's entry in /etc/shadow is missing. Users of shadow-utils are advised to upgrade to these updated packages, which fix these bugs.

Commands: