mtpti5iD/redhat-docs_dataset huggingface dataset:
2.4. Monitoring the Local Disk for Graceful Shutdown When the disk space available on a system becomes too small, the Directory Server process terminates. As a consequence, there is a risk of corrupting the database or loosing data. To prevent this problem, you can configure Directory Server to monitor the free disk space. The monitoring thread checks the free space on the file systems that contain the configuration, transaction log, and database directories. Depending on the remaining free disk space, Directory Server behaves different: If the free disk space reaches the defined threshold, Directory Server: Disables verbose logging Disables access access logging Deletes archived log files Note Directory Server always continues writing error logs, even if the threshold is reached. If the free disk space is lower than the half of the configured threshold, Directory Server shuts down within a defined grace period. If the available disk space is ever lower than 4 KB, Directory Server shuts down immediately. If disk space is freed up, then Directory Server aborts the shutdown process and re-enables all of the previously disabled log settings. 2.4.1. Configuring Local Disk Monitoring Using the Command Line To configure local disk monitoring using the command line: Enable the disk monitoring feature, set a threshold value, and a grace period: This command sets the threshold of free disk space to 3 GB and the grace period to 60 seconds. Optionally, configure that Directory Server neither disables access logging nor deletes archived logs, by enabling the nsslapd-disk-monitoring-logging-critical parameter: Restart the Directory Server instance: 2.4.2. Configuring Local Disk Monitoring Using the Web Console To configure local disk monitoring using the Web Console: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. Open the Server Settings menu, and select Server Configuration . Enable Enable Disk Space Monitoring , and set the threshold in bytes and the grace period in minutes. This example sets the monitoring threshold to 3 GB (3,221,225,472 bytes) and the time before Directory Server shuts down the instance after reaching the threshold to 60 minutes. Optionally, configure that Directory Server neither disables access logging nor deletes archived logs by selecting Preserve Logs . Click Save Configuration . Click the Actions button, and select Restart Instance .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-disk-monitoring=on nsslapd-disk-monitoring-threshold=3000000000 nsslapd-disk-monitoring-grace-period=60
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace nsslapd-disk-monitoring-logging-critical=on
dsctl instance_name restart
Chapter 10. Groups Groups in Red Hat Single Sign-On allow you to manage a common set of attributes and role mappings for a set of users. Users can be members of zero or more groups. Users inherit the attributes and role mappings assigned to each group. To manage groups go to the Groups left menu item. Groups Groups are hierarchical. A group can have many subgroups, but a group can only have one parent. Subgroups inherit the attributes and role mappings from the parent. This applies to the user as well. So, if you have a parent group and a child group and a user that only belongs to the child group, the user inherits the attributes and role mappings of both the parent and child. In this example, we have a top level Sales group and a child North America subgroup. To add a group, click on the parent you want to add a new child to and click New button. Select the Groups icon in the tree to make a top-level group. Entering in a group name in the Create Group screen and hitting Save will bring you to the individual group management page. Group The Attributes and Role Mappings tab work exactly as the tabs with similar names under a user. Any attributes and role mappings you define will be inherited by the groups and users that are members of this group. To add a user to a group you need to go all the way back to the user detail page and click on the Groups tab there. User Groups Select a group from the Available Groups tree and hit the join button to add the user to a group. Vice versa to remove a group. Here we've added the user Jim to the North America sales group. If you go back to the detail page for that group and select the Membership tab, Jim is now displayed there. Group Membership 10.1. Groups vs. Roles In the IT world the concepts of Group and Role are often blurred and interchangeable. In Red Hat Single Sign-On, Groups are just a collection of users that you can apply roles and attributes to in one place. Roles define a type of user and applications assign permission and access control to roles. Aren't Composite Roles also similar to Groups? Logically they provide the same exact functionality, but the difference is conceptual. Composite roles should be used to apply the permission model to your set of services and applications. Groups should focus on collections of users and their roles in your organization. Use groups to manage users. Use composite roles to manage applications and services. 10.2. Default Groups Default groups allow you to automatically assign group membership whenever any new user is created or imported through Identity Brokering . To specify default groups go to the Groups left menu item, and click the Default Groups tab. Default Groups

Commands:
4.149. libtirpc 4.149.1. RHBA-2011:1745 - libtirpc bug fix update An updated libtirpc package that fixes one bug is now available for Red Hat Enterprise Linux 6. The libtirpc package contains SunLib's implementation of transport independent RPC (TI-RPC) documentation. This includes a library required by programs in the nfs-utils and rpcbind packages. Bug Fix BZ# 714015 Due to certain errors and missing code in libtirpc, user space NFS servers were not able to fully utilize the RPCSEC_GSS security protocol, which allows remote procedure call (RPC) protocols to access the Generic Security Services Application Programming Interface (GSS-API). With this update, the problems have been fixed in the libtirpc code. The RPCSEC_GSS protocol now can be used by NFS servers properly. All users of libtirpc are advised to upgrade to this updated package, which fixes this bug.

Commands:
4.272. ricci 4.272.1. RHBA-2011:1698 - ricci bug fix and enhancement update Updated ricci packages that fix multiple bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The ricci packages contain a daemon and a client for remote configuring and managing of clusters. Bug Fixes BZ# 697493 Prior to this update, the ccs_sync utility could not handle IPv6 addresses. This could prevent the cluster.conf file from being distributed to nodes. The ccs_sync utility has been modified to be able to recognize and use IPv6 addresses. Now, the cluster.conf file is distributed to all nodes correctly. BZ# 718230 The ccs tool did not add or list virtual machine services correctly when using the "ccs --addresource" command. This was caused by the virtual machine resource being incorrectly added in the "resources" tag instead of the "rm" tag. This problem has been fixed and virtual machine services are now added directly in the "rm" tag when using the ccs tool. BZ# 725722 Prior to this update, the /usr/share/ccs/cluster.rng schema file did not contain definition of the "suborg" option for the fence_cisco_ucs agent. As a consequence, the cluster.conf file was not changed when adding a fencing instance definition with the "suborg" option. With this update, the cluster.rng schema has been modified to match the schema present in the cman package. BZ# 721109 versions of ricci did not require the modcluster package even though it was needed for ricci to work correctly. With this update, ricci now requires modcluster to be installed. Enhancement BZ# 696901 The ccs utility can now parse metadata in /usr/share/cluster and lists all the services and fence devices available, as well as their options. All users of ricci are advised to upgrade to these updated ricci packages, which fix these bugs and add this enhancement.

Commands:
1.2. About this guide This guide describes how to import virtual machines from foreign hypervisors to Red Hat Enterprise Virtualization and KVM managed by libvirt. 1.2.1. Audience This guide is intended for system administrators who manage a virtualized environment using Red Hat Enterprise Virtualization or Red Hat Enterprise Linux. An advanced level of system administration, preferably including familiarity with virtual machine data center operations, is assumed. This document is not intended for beginners.

Commands:
8.88. i2c-tools 8.88.1. RHBA-2014:1520 - i2c-tools bug fix update Updated i2c-tools packages that fix one bug are now available for Red Hat Enterprise Linux 6. The i2c-tools packages contain a set of I2C tools for Linux: a bus probing tool, a chip dumper, register-level SMBus access helpers, EEPROM (Electrically Erasable Programmable Read-Only Memory) decoding scripts, EEPROM programming tools, and a python module for SMBus access. Note: EEPROM decoding scripts can render your system unusable. Make sure to use these tools wisely. This update fixes the following bug: Bug Fix BZ# 914728 The i2cdetect utility requires the i2c-dev module to be loaded so that it can detect devices present on a specified bus. Previously, this was not done automatically, and as a consequence, the user could be mistaken that no buses or devices existed when running i2cdetect. With this update, i2c-dev has been made automatically-loadable. Now, i2cdetect correctly scans an I2C bus for devices and outputs a table with detected devices as expected. Note: EEPROM decoding scripts can render your system unusable. Make sure to use these tools wisely. Users of i2c-tools are advised to upgrade to these updated packages, which fix this bug.

Commands:
20.3. Configuring Network Encryption for an existing Trusted Storage Pool Follow this section to configure I/O and management encryption for an existing Red Hat Gluster Storage Trusted Storage Pool. 20.3.1. Enabling I/O Encryption Follow this section to enable I/O encryption between servers and clients. Procedure 20.6. Enabling I/O encryption Unmount the volume from all clients Unmount the volume by running the following command on all clients. Stop the volume Stop the volume by running the following command from any server. Specify servers and clients to allow Provide a list of the common names of servers and clients that are allowed to access the volume. The common names provided must be exactly the same as the common name specified when you created the glusterfs.pem file for that server or client. This provides an additional check in case you want to leave keys in place, but temporarily restrict a client or server by removing it from this list, as shown in Section 20.7, "Deauthorizing a Client" . You can also use the default value of * , which indicates that any TLS authenticated machine can mount and access the volume. Enable TLS/SSL encryption on the volume Run the following command from any server to enable TLS/SSL encryption. Start the volume Verify Verify that the volume can be mounted only on authorized clients. The process for mounting a volume depends on the protocol your client is using. The following command mounts a volume using the native FUSE protocol. Ensure that this command works on authorized clients, and does not work on unauthorized clients.

Commands:
umount mountpoint
gluster volume stop VOLNAME
gluster volume set volname auth.ssl-allow ' server1 , server2 , client1 , client2 , client3 '
gluster volume set volname client.ssl on gluster volume set volname server.ssl on
gluster volume start volname
mount -t glusterfs server1:/testvolume /mnt/glusterfs
7.53. fence-agents 7.53.1. RHBA-2015:1350 - fence-agents bug fix and enhancement update Updated fence-agents packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The fence-agents packages provide a collection of scripts for handling remote power management for cluster devices. They allow failed or unreachable nodes to be forcibly restarted and removed from the cluster. Note The fence-agents packages have been upgraded to upstream version 4.0.15, which provides a number of bug fixes and enhancements over the version. Bug Fix BZ# 1049805 , BZ# 1094515 , BZ# 1099551 , BZ# 1111482 , BZ# 1118008 , BZ# 1123897 , BZ# 1171734 This update adds the "--tls1.0" option to the fence agent for HP Integrated Lights-Out 2 (iLO2) devices. With this option, iLO2 negotiation of the TLS protocol works as expected when using an iLO2 device with firmware version 2.27. The fence_kdump agent now supports the "monitor" action, making integration with a cluster stack easier. The fence-agents packages now support the fence_ilo_moonshot fence agent for HP Moonshot iLO devices. For information on the fence_ilo_moonshot parameters, see the fence_ilo_moonshot(8) man page. This update adds support for the fence_ilo_ssh fence agent. The agent logs into an iLO device using SSH and reboots a specified outlet. For information on the fence_ilo_ssh parameters, see the fence_ilo_ssh(8) man page. This update adds support for the fence_mpath fence agent. This agent is an I/O fencing agent that uses SCSI-3 persistent reservations to control access to multipath devices. For information on fence_mpath and its parameters, see the fence_mpath(8) man page. The fence agent for APC devices over Simple Network Management Protocol (SNMP) has been updated to support the latest versions of the APC firmware. This update adds support for the fence_emerson fencing agent for Emerson devices over Simple Network Management Protocol (SNMP). It is an I/O fencing agent that can be used with the MPX and MPH2 Emerson devices. For information on the parameters for the fence_emerson fencing agent, see the fence_emerson(8) man page. Users of fence-agents are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 19. Maven Indexer Plugin The Maven Indexer Plugin is required for the Maven plugin to enable it to quickly search Maven Central for artifacts. To Deploy the Maven Indexer plugin use the following commands: Prerequisites Before deploying the Maven Indexer Plugin, make sure that you have followed the instructions in the Installing on Apache Karaf Preparing to Use Maven section. Deploy the Maven Indexer Plugin Go to the Karaf console and enter the following command to install the Maven Indexer plugin: Enter the following commands to configure the Maven Indexer plugin: Wait for the Maven Indexer plugin to be deployed. This may take a few minutes. Look out for messages like those shown below to appear on the log tab. When the Maven Indexer plugin has been deployed, use the following commands to add further external Maven repositories to the Maven Indexer plugin configuration:

Commands:
features:install hawtio-maven-indexer
config:edit io.hawt.maven.indexer config:proplist config:propset repositories 'https://maven.oracle.com' config:proplist config:update
config:edit io.hawt.maven.indexer config:proplist config:propset repositories external repository config:proplist config:update
2.7. RHEA-2011:0579 - new package: hwloc A new hwloc package is now available for Red Hat Enterprise Linux 6. The hwloc package provides Portable Hardware Locality, which is a portable abstraction of the hierarchical topology of current architectures. This enhancement update adds the hwloc package to Red Hat Enterprise Linux 6. (BZ# 648593 ) All users who require hwloc are advised to install this new package.

Commands:
Chapter 10. availability This chapter describes the commands under the availability command. 10.1. availability zone list List availability zones and their status Usage: Table 10.1. Optional Arguments Value Summary -h, --help Show this help message and exit --compute List compute availability zones --network List network availability zones --volume List volume availability zones --long List additional fields in output Table 10.2. Output Formatters Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 10.3. CSV Formatter Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 10.4. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 10.5. Table Formatter 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 availability zone list [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--compute] [--network] [--volume] [--long]
Chapter 53. Installing and running Oracle WebLogic Server Oracle WebLogic Server must be installed and running for you to apply many of the configurations that accommodate KIE Server. This section describes how to install and start Oracle WebLogic Server in a standalone Oracle WebLogic Server domain. For the most up-to-date and detailed installation instructions, see the Oracle WebLogic Server product page . Note If you are already running an instance of Oracle WebLogic Server that uses the same listener port as the one to be used by the server you are starting, you must stop the first server before starting the second server. Procedure Download Oracle WebLogic Server 12.2.1.3.0 or later from the Oracle WebLogic Server Downloads page . Sign in to the target system and verify that a certified JDK already exists on your system. The installer requires a certified JDK. For system requirements, see Oracle Fusion Middleware Systems Requirements and Specifications . To download the JDK, see the "About JDK Requirements for an Oracle Fusion Middleware Installation" section in Planning an Installation of Oracle Fusion Middleware . Navigate to the directory where you downloaded the installation program. To launch the installation program, run java -jar from the JDK directory on your system, as shown in the following examples: On UNIX-based operating systems, enter the following command: On Windows operating systems, enter the following command: Replace the JDK location in these examples with the actual JDK location on your system. Follow the installation wizard prompts to complete the installation. After the installation is complete, navigate to the WLS_HOME /user_projects/<DOMAIN_NAME> directory where <DOMAIN_NAME> is the domain directory. In the following example, mydomain is the domain directory: Enter one of the following commands to start Oracle WebLogic Server: On UNIX-based operating systems, enter the following command: On Windows operating systems, enter the following command: The startup script displays a series of messages, and finally displays a message similar to the following: Open the following URL in a web browser: In this command, replace the following place holders: Replace <HOST> with the system name or IP address of the host server. Replace <PORT> with the number of the port on which the host server is listening for requests (7001 by default). For example, to start the Administration Console for a local instance of Oracle WebLogic Server running on your system, enter the following URL in a web browser: If you started the Administration Console using secure socket layer (SSL), you must add s after http , as follows: https://<HOST>:<PORT>/console When the login page of the WebLogic Administration Console appears, enter your administrative credentials.

Commands:
/home/Oracle/jdk/jdk1.8.0_131/bin/java -jar fmw_12.2.1.3.0_wls_generic.jar
C:\Program Files\Java\jdk1.8.0_131\bin\java -jar fmw_12.2.1.3.0_wls_generic.jar
WLS\user_projects\mydomain
startWebLogic.sh
startWebLogic.cmd
<Dec 8, 2017 3:50:42 PM PDT> <Notice> <WebLogicServer> <000360> <Server started in RUNNING mode>
http://<HOST>:<PORT>/console
http://localhost:7001/console/
13.2.6. Configuring Services: PAM Warning A mistake in the PAM configuration file can lock users out of the system completely. Always back up the configuration files before performing any changes, and keep a session open so that any changes can be reverted. SSSD provides a PAM module, sssd_pam , which instructs the system to use SSSD to retrieve user information. The PAM configuration must include a reference to the SSSD module, and then the SSSD configuration sets how SSSD interacts with PAM. Procedure 13.3. Configuring PAM Use authconfig to enable SSSD for system authentication. This automatically updates the PAM configuration to reference all of the SSSD modules: These modules can be set to include statements, as necessary. Open the sssd.conf file. Make sure that PAM is listed as one of the services that works with SSSD. In the [pam] section, change any of the PAM parameters. These are listed in Table 13.3, "SSSD [pam] Configuration Parameters" . Restart SSSD. Table 13.3. SSSD [pam] Configuration Parameters Parameter Value Format Description offline_credentials_expiration integer Sets how long, in days, to allow cached logins if the authentication provider is offline. This value is measured from the last successful online login. If not specified, this defaults to zero ( 0 ), which is unlimited. offline_failed_login_attempts integer Sets how many failed login attempts are allowed if the authentication provider is offline. If not specified, this defaults to zero ( 0 ), which is unlimited. offline_failed_login_delay integer Sets how long to prevent login attempts if a user hits the failed login attempt limit. If set to zero ( 0 ), the user cannot authenticate while the provider is offline once he hits the failed attempt limit. Only a successful online authentication can re-enable offline authentication. If not specified, this defaults to five ( 5 ).

Commands:
authconfig --update --enablesssd --enablesssdauth
#%PAM-1.0 This file is auto-generated. User changes will be destroyed the next time authconfig is run. auth required pam_env.so auth sufficient pam_unix.so nullok try_first_pass auth requisite pam_succeed_if.so uid >= 500 quiet auth sufficient pam_sss.so use_first_pass auth required pam_deny.so account required pam_unix.so account sufficient pam_localuser.so account sufficient pam_succeed_if.so uid < 500 quiet account [default=bad success=ok user_unknown=ignore] pam_sss.so account required pam_permit.so password requisite pam_cracklib.so try_first_pass retry=3 password sufficient pam_unix.so sha512 shadow nullok try_first_pass use_authtok password sufficient pam_sss.so use_authtok password required pam_deny.so session optional pam_keyinit.so revoke session required pam_limits.so session [success=1 default=ignore] pam_succeed_if.so service in crond quiet use_uid session sufficient pam_sss.so session required pam_unix.so
vim /etc/sssd/sssd.conf
[sssd] config_file_version = 2 reconnection_retries = 3 sbus_timeout = 30 services = nss, pam
[pam] reconnection_retries = 3 offline_credentials_expiration = 2 offline_failed_login_attempts = 3 offline_failed_login_delay = 5
~]# service sssd restart