mtpti5iD/redhat-docs_dataset huggingface dataset:
28.4. Modifying Password Policy Attributes Important When you modify a password policy, the new rules apply to new passwords only. The changes are not applied retroactively to existing passwords. For the change to take effect, users must change their existing passwords, or the administrator must reset the passwords of other users. See Section 22.1.1, "Changing and Resetting User Passwords" . Note For recommendations on secure user passwords, see Password Security in the Security Guide . To modify a password policy using: the web UI, see the section called "Web UI: Modifying a Password Policy" the command line, see the section called "Command Line: Modifying a Password Policy" Note that setting a password policy attribute to 0 means no attribute restriction. For example, if you set maximum lifetime to 0 , user passwords never expire. Web UI: Modifying a Password Policy Select Policy Password Policies . Click the policy you want to change. Update the required attributes. For details on the available attributes, see Section 28.2.1, "Supported Password Policy Attributes" . Click Save to confirm the changes. Command Line: Modifying a Password Policy Use the ipa pwpolicy-mod command to change the policy's attributes. For example, to update the global password policy and set the minimum password length to 10 : To update a group policy, add the group name to ipa pwpolicy-mod . For example: Optional. Use the ipa pwpolicy-show command to display the new policy settings. To display the global policy: To display a group policy, add the group name to ipa pwpolicy-show :

Commands:
ipa pwpolicy-mod --minlength=10
ipa pwpolicy-mod group_name --minlength=10
ipa pwpolicy-show
ipa pwpolicy-show group_name
2.9. Runtime Metadata Once you have adequately modeled your enterprise information systems, including the necessary technical metadata that describes the physical structure of your sources, you can use the metadata for data access. To prepare the metadata for use in the JBoss Data Virtualization Server, you take a snapshot of a metadata model for the JBoss Data Virtualization Server to use when resolving queries from your client applications. This runtime metadata represents a static version of design-time metadata you created or imported. This snapshot is in the form of a Virtual Database definition, or VDB. As you create this runtime metadata, the Teiid Designer : derives the runtime metadata from a consistent set of metadata models. creates a subset of design-time metadata, focusing on the technical metadata that describes the access to underlying enterprise information systems. optimizes runtime metadata for data access performance. You can continue to work with the design-time metadata, but once you have created a runtime metadata model, it remains static.

Commands:
Chapter 9. Preparing a system with UEFI Secure Boot enabled to install and boot RHEL beta releases To enhance the security of your operating system, use the UEFI Secure Boot feature for signature verification when booting a Red Hat Enterprise Linux Beta release on systems having UEFI Secure Boot enabled. 9.1. UEFI Secure Boot and RHEL Beta releases UEFI Secure Boot requires that the operating system kernel is signed with a recognized private key. UEFI Secure Boot then verifies the signature using the corresponding public key. For Red Hat Enterprise Linux Beta releases, the kernel is signed with a Red Hat Beta-specific private key. UEFI Secure Boot attempts to verify the signature using the corresponding public key, but because the hardware does not recognize the Beta private key, Red Hat Enterprise Linux Beta release system fails to boot. Therefore, to use UEFI Secure Boot with a Beta release, add the Red Hat Beta public key to your system using the Machine Owner Key (MOK) facility. 9.2. Adding a Beta public key for UEFI Secure Boot This section contains information about how to add a Red Hat Enterprise Linux Beta public key for UEFI Secure Boot. Prerequisites The UEFI Secure Boot is disabled on the system. The Red Hat Enterprise Linux Beta release is installed, and Secure Boot is disabled even after system reboot. You are logged in to the system, and the tasks in the Initial Setup window are complete. Procedure Begin to enroll the Red Hat Beta public key in the system's Machine Owner Key (MOK) list: USD(uname -r) is replaced by the kernel version - for example, 4.18.0-80.el8.x86_64 . Enter a password when prompted. Reboot the system and press any key to continue the startup. The Shim UEFI key management utility starts during the system startup. Select Enroll MOK . Select Continue . Select Yes and enter the password. The key is imported into the system's firmware. Select Reboot . Enable Secure Boot on the system. 9.3. Removing a Beta public key If you plan to remove the Red Hat Enterprise Linux Beta release, and install a Red Hat Enterprise Linux General Availability (GA) release, or a different operating system, then remove the Beta public key. The procedure describes how to remove a Beta public key. Procedure Begin to remove the Red Hat Beta public key from the system's Machine Owner Key (MOK) list: Enter a password when prompted. Reboot the system and press any key to continue the startup. The Shim UEFI key management utility starts during the system startup. Select Reset MOK . Select Continue . Select Yes and enter the password that you had specified in step 2. The key is removed from the system's firmware. Select Reboot .

Commands:
mokutil --import /usr/share/doc/kernel-keys/USD(uname -r)/kernel-signing-ca.cer
mokutil --reset
7.11. RHEA-2014:1596 - new packages: ksm_preload New ksm_preload packages are now available for Red Hat Enterprise Linux 6. The ksm_preload packages provide the ksm_preload library that allows applications to share memory pages. It also enables "legacy" applications to leverage Linux's memory deduplication. This enhancement update adds the ksm_preload packages to Red Hat Enterprise Linux 6. (BZ# 1034763 ) All users who require ksm_preload are advised to install these new packages.

Commands:
5.326. system-config-users 5.326.1. RHBA-2012:1387 - system-config-users bug fix update Updated system-config-users packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The system-config-users packages provide a graphical utility for administrating users and groups. Bug Fixes BZ# 736037 Prior to this update, expiration dates at or before January 1, 1970 were not correctly calculated. As a consequence, the system-config-users utility stored expiration dates off by one day into /etc/shadow. This update modifies the underlying code so that account expiration dates are calculated and stored correctly. BZ# 801652 Prior to this update, a string in the user interface was not correctly localized into Japanese. This update modifies the string so that the text is now correct. BZ# 841886 Prior to this update, the system-config-users utility determined incorrectly whether to set an account as inactive if an expired password was not reset during a specified period. This update modifies the underlying code to check for this condition by hard-coding the value which indicates this condition. All users of system-config-users are advised to upgrade to these updated packages, which fix these bugs.

Commands:
34.2.2. Configuring Batch Jobs To execute a one-time task when the load average is below 0.8, use the batch command. After typing the batch command, the at> prompt is displayed. Type the command to execute, press Enter , and type Ctrl + D . Multiple commands can be specified by typing each command followed by the Enter key. After typing all the commands, press Enter to go to a blank line and type Ctrl + D . Alternatively, a shell script can be entered at the prompt, pressing Enter after each line in the script, and typing Ctrl + D on a blank line to exit. If a script is entered, the shell used is the shell set in the user's SHELL environment, the user's login shell, or /bin/sh (whichever is found first). As soon as the load average is below 0.8, the set of commands or script is executed. If the set of commands or script tries to display information to standard out, the output is emailed to the user. Use the command atq to view pending jobs. Refer to Section 34.2.3, "Viewing Pending Jobs" for more information. Usage of the batch command can be restricted. For more information, refer to Section 34.2.5, "Controlling Access to At and Batch" for details.

Commands:
7.133. lohit-telugu-fonts 7.133.1. RHBA-2012:1212 - lohit-telugu-fonts bug fix update An updated lohit-telugu-fonts package that fixes one bug is now available for Red Hat Enterprise Linux 6. The lohit-telugu-fonts package provides a free Telugu TrueType/OpenType font. Bug Fix BZ#640610 Due to a bug in the lohit-telugu-fonts package, four certain syllables were rendering incorrectly. This bug has been fixed and these syllables now render correctly. All users of lohit-telugu-fonts are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 8. Assigning a Puppet Class to an Individual Host Procedure In the Satellite web UI, navigate to Hosts > All hosts . Click on the Edit button of the host you want to add the ntp Puppet class to. Select the Puppet ENC tab and look for the ntp class. Click the + symbol to ntp to add the ntp submodule to the list of included classes . Click the Submit button at the bottom to save your changes. Tip If the Puppet classes tab of an individual host is empty, check if it is assigned to the proper Puppet environment. Verify the Puppet configuration. Navigate to Hosts > All Hosts and select the host. From the top overflow menu, select Legacy UI . Under Details , click the Puppet YAML button. This produces output similar as follows: --- parameters: // shortened YAML output classes: ntp: servers: '["0.de.pool.ntp.org","1.de.pool.ntp.org","2.de.pool.ntp.org","3.de.pool.ntp.org"]' environment: production ... Verify the ntp configuration. Connect to your host using SSH and check the content of /etc/ntp.conf . This example assumes your host is running CentOS 7 . Other operating systems may store the ntp config file in a different path. Tip You may need to run the Puppet agent on your host by executing the following command: Running the following command on the host checks which ntp servers are used for clock synchronization: This returns output similar as follows: You now have a working ntp module which you can add to a host or group of hosts to roll out your ntp configuration automatically.

Commands:
--- parameters: // shortened YAML output classes: ntp: servers: '["0.de.pool.ntp.org","1.de.pool.ntp.org","2.de.pool.ntp.org","3.de.pool.ntp.org"]' environment: production
puppet agent -t
cat /etc/ntp.conf
ntp.conf: Managed by puppet. server 0.de.pool.ntp.org server 1.de.pool.ntp.org server 2.de.pool.ntp.org server 3.de.pool.ntp.org
Chapter 9. Viewing and managing JMX domains and MBeans Java Management Extensions (JMX) is a Java technology that allows you to manage resources (services, devices, and applications) dynamically at runtime. The resources are represented by objects called MBeans (for Managed Bean). You can manage and monitor resources as soon as they are created, implemented, or installed. With the JMX plugin on the Fuse Console, you can view and manage JMX domains and MBeans. You can view MBean attributes, run commands, and create charts that show statistics for the MBeans. The JMX tab provides a tree view of the active JMX domains and MBeans organized in folders. You can view details and execute commands on the MBeans. Procedure To view and edit MBean attributes: In the tree view, select an MBean. Click the Attributes tab. Click an attribute to see its details. To perform operations: In the tree view, select an MBean. Click the Operations tab, expand one of the listed operations. Click Execute to run the operation. To view charts: In the tree view, select an item. Click the Chart tab.

Commands:
Chapter 2. Installing the Red Hat Quay Operator from the OperatorHub Use the following procedure to install the Red Hat Quay Operator from the OpenShift Container Platform OperatorHub. Procedure Using the OpenShift Container Platform console, select Operators OperatorHub . In the search box, type Red Hat Quay and select the official Red Hat Quay Operator provided by Red Hat. This directs you to the Installation page, which outlines the features, prerequisites, and deployment information. Select Install . This directs you to the Operator Installation page. The following choices are available for customizing the installation: Update Channel: Choose the update channel, for example, stable-3 for the latest release. Installation Mode: Choose All namespaces on the cluster if you want the Red Hat Quay Operator to be available cluster-wide. It is recommended that you install the Red Hat Quay Operator cluster-wide. If you choose a single namespace, the monitoring component will not be available by default. Choose A specific namespace on the cluster if you want it deployed only within a single namespace. Approval Strategy: Choose to approve either automatic or manual updates. Automatic update strategy is recommended. Select Install .

Commands:
5.374. rhn-client-tools 5.374.1. RHBA-2013:1384 - rhn-client-tools bug fix and enhancement update Updated rhn-client-tools packages that fix one bug and add one enhancement are now available for Red Hat Enterprise Linux 6 Extended Update Support. Red Hat Network Client Tools provide programs and libraries that allow systems to receive software updates from Red Hat Network (RHN). Bug Fix BZ# 993080 The RHN Proxy did not work properly if separated from a parent by a slow enough network. Consequently, users who attempted to download larger repodata files and RPMs experienced timeouts. This update changes both RHN Proxy and Red Hat Enterprise Linux RHN Client to allow all communications to obey a configured timeout value for connections. Enhancement BZ# 993073 While Satellite 5.3.0 now has the ability to get the number of CPUs via an API call, there was no function to obtain the number of sockets from the registered systems. This update adds a function to get the number of physical CPU sockets in a managed system from Satellite via an API call. Users of rhn-client-tools are advised to upgrade to these updated packages, which fix this bug and add this enhancement.

Commands:
1.4. Logging Into Directory Server Using the Web Console The web console is a browser-based graphical user interface (GUI) that enables users to perform administrative tasks. The Directory Server package automatically installs the Directory Server user interface for the web console. To open Directory Server in the web console: Use a browser and connect to the web console running on port 9090 on the Directory Server host. For example: Log in as the root user or as a user with sudo privileges. Select the Red Hat Directory Server entry.

Commands:
https:// server.example.com : 9090
2.2.2. Boost The boost package contains a large number of free peer-reviewed portable C++ source libraries. These libraries are suitable for tasks such as portable file-system access and time or date abstraction, serialization, unit testing, thread creation and multi-process synchronization, parsing, graphing, regular expression manipulation, and many others. Installing the boost package will provide just enough libraries to satisfy link dependencies (that is, only shared library files). To make full use of all available libraries and header files for C++ development, you must install boost-devel as well. The boost package is actually a meta-package, containing many library sub-packages. These sub-packages can also be installed individually to provide finer inter-package dependency tracking. The meta-package does not include dependencies for packages for static linking or packages that depend on the underlying Message Passing Interface (MPI) support. MPI support is provided in two forms: one for the default Open MPI implementation (package boost-openmpi ) and another for the alternate MPICH2 implementation (package boost-mpich2 ). The selection of the underlying MPI library in use is up to the user and depends on specific hardware details and user preferences. Please note that these packages can be installed in parallel because installed files have unique directory locations. If static linkage cannot be avoided, the boost-static package will install the necessary static libraries. Both thread-enabled and single-threaded libraries are provided. 2.2.2.1. Additional Information The boost-doc package provides manuals and reference information in HTML form located in the following directory: /usr/share/doc/boost-doc- version /index.html . The main site for the development of Boost is http://boost.org .

Commands:
6.3. Manually Setting the Entry Cache Size The entry cache is used to store directory entries that are used during search and read operations. Setting the entry cache to a size that enables Directory Server to store all records has the highest performance impact on search operations. If entry caching is not configured, Directory Server reads the entry from the id2entry.db database file and converts the DNs from the on-disk format to the in-memory format. Entries that are stored in the cache enable the server to skip the disk I/O and conversion steps. Note Instead of manually setting the entry cache size Red Hat recommends the auto-sizing feature for optimized settings based on the hardware resources. For details, see Section 6.1.1, "Manually Re-enabling the Database and Entry Cache Auto-sizing" . 6.3.1. Manually Setting the Entry Cache Size Using the Command Line To manually set the entry cache size using the command line: Disable automatic cache tuning: Display the suffixes and their corresponding back end: This command displays the name of the back end database to each suffix. You require the suffix's database name in the step. Set the entry cache size for the database: This command sets the entry cache to 2 gigabytes. Restart the Directory Service instance: 6.3.2. Manually Setting the Entry Cache Size Using the Web Console To manually set the entry cache size 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. On the Database tab, select Global Database Configuration . Disable Automatic Cache Tuning . Click Save Configuration . Click the Actions button, and select Restart Instance . Set the size of the database cache in the Entry Cache Size (bytes) field. Click Save Configuration . Click the Actions button, and select Restart Instance .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com backend config set --cache-autosize=0
dsconf -D "cn=Directory Manager" ldap://server.example.com suffix list dc=example,dc=com ( userroot )
dsconf -D "cn=Directory Manager" ldap://server.example.com backend suffix set --cache-memsize= 2147483648 userRoot
dsctl instance_name restart
22.3. Language Selection Use the arrow keys on your keyboard to select a language to use during the installation process (refer to Figure 22.3, "Language Selection" ). With your selected language highlighted, press the Tab key to move to the OK button and press the Enter key to confirm your choice. You can automate this choice in the parameter file with the parameter lang= (refer to Section 26.5, "Loader Parameters" ) or with the kickstart command lang (refer to Section 28.4, "Automating the Installation with Kickstart" ). The language you select here will become the default language for the operating system once it is installed. Selecting the appropriate language also helps target your time zone configuration later in the installation. The installation program tries to define the appropriate time zone based on what you specify on this screen. To add support for additional languages, customize the installation at the package selection stage. For more information, refer to Section 23.17.2, " Customizing the Software Selection " . Figure 22.3. Language Selection Once you select the appropriate language, click to continue.

Commands:
5.5.4. Enabling Storage Access Once a mass storage device has been properly partitioned, and a file system written to it, the storage is available for general use. For some operating systems, this is true; as soon as the operating system detects the new mass storage device, it can be formatted by the system administrator and may be accessed immediately with no additional effort. Other operating systems require an additional step. This step -- often referred to as mounting -- directs the operating system as to how the storage may be accessed. Mounting storage normally is done via a special utility program or command, and requires that the mass storage device (and possibly the partition as well) be explicitly identified.

Commands:
Chapter 4. Debug Parameters These parameters allow you to set debug mode on a per-service basis. The Debug parameter acts as a global parameter for all services and the per-service parameters can override the effects of global parameter on individual services. Parameter Description BarbicanDebug Set to True to enable debugging OpenStack Key Manager (barbican) service. The default value is false . CinderDebug Set to True to enable debugging on OpenStack Block Storage (cinder) services. The default value is false . ConfigDebug Whether to run configuration management (e.g. Puppet) in debug mode. The default value is false . Debug Set to True to enable debugging on all services. The default value is false . DesignateDebug Set to True to enable debugging Designate services. The default value is false . GlanceDebug Set to True to enable debugging OpenStack Image Storage (glance) service. The default value is false . HeatDebug Set to True to enable debugging OpenStack Orchestration (heat) services. The default value is false . HorizonDebug Set to True to enable debugging OpenStack Dashboard (horizon) service. The default value is false . IronicDebug Set to True to enable debugging OpenStack Bare Metal (ironic) services. The default value is false . KeystoneDebug Set to True to enable debugging OpenStack Identity (keystone) service. The default value is false . ManilaDebug Set to True to enable debugging OpenStack Shared File Systems (manila) services. The default value is false . MemcachedDebug Set to True to enable debugging Memcached service. The default value is false . NeutronDebug Set to True to enable debugging OpenStack Networking (neutron) services. The default value is false . NovaDebug Set to True to enable debugging OpenStack Compute (nova) services. The default value is false . OctaviaDebug Set to True to enable debugging OpenStack Load Balancing-as-a-Service (octavia) services. The default value is false .

Commands:
2.5. Tracking Tag History The ETL Service collects tag information as displayed in the Administration Portal every minute and stores this data in the tags historical tables. The ETL Service tracks five types of changes: A tag is created in the Administration Portal - the ETL Service copies the tag details, position in the tag tree and relation to other objects in the tag tree. A entity is attached to the tag tree in the Administration Portal - the ETL Service replicates the addition to the ovirt_engine_history database as a new entry. A tag is updated - the ETL Service replicates the change of tag details to the ovirt_engine_history database as a new entry. An entity or tag branch is removed from the Administration Portal - the ovirt_engine_history database flags the corresponding tag and relations as removed in new entries. Removed tags and relations are only flagged as removed or detached. A tag branch is moved - the corresponding tag and relations are updated as new entries. Moved tags and relations are only flagged as updated.

Commands: