mtpti5iD/redhat-docs_dataset huggingface dataset:
9.12.3. Updating the Boot Loader Configuration Your completed Red Hat Enterprise Linux installation must be registered in the boot loader to boot properly. A boot loader is software on your machine that locates and starts the operating system. Refer to Appendix E, The GRUB Boot Loader for more information about boot loaders. Figure 9.36. The Upgrade Boot Loader Dialog If the existing boot loader was installed by a Linux distribution, the installation system can modify it to load the new Red Hat Enterprise Linux system. To update the existing Linux boot loader, select Update boot loader configuration . This is the default behavior when you upgrade an existing Red Hat Enterprise Linux installation. GRUB is the standard boot loader for Red Hat Enterprise Linux on 32-bit and 64-bit x86 architectures. If your machine uses another boot loader, such as BootMagic, System Commander, or the loader installed by Microsoft Windows, then the Red Hat Enterprise Linux installation system cannot update it. In this case, select Skip boot loader updating . When the installation process completes, refer to the documentation for your product for assistance. Install a new boot loader as part of an upgrade process only if you are certain you want to replace the existing boot loader. If you install a new boot loader, you may not be able to boot other operating systems on the same machine until you have configured the new boot loader. Select Create new boot loader configuration to remove the existing boot loader and install GRUB. After you make your selection, click to continue. If you selected the Create new boot loader configuration option, refer to Section 9.18, "x86, AMD64, and Intel 64 Boot Loader Configuration" . If you chose to update or skip boot loader configuration, installation continues without further input from you.

Commands:
7.209. system-config-users 7.209.1. RHBA-2015:1433 - system-config-users bug fix update An updated system-config-users package that fixes one bug is now available for Red Hat Enterprise Linux 6. The system-config-users package provides a graphical utility for administrating users and groups. Bug Fix BZ# 981910 When the "INACTIVE" parameter was set in the /etc/default/useradd file, using the system-config-users utility to create or edit a user caused the user to be automatically expired. With this update, setting "INACTIVE" in /etc/default/useradd no longer gives users created or edited in system-config-users an incorrect expiration date, and thus no longer causes them to become unusable. Users of system-config-users are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 8. Creating a Keycloak instance When the Red Hat Single Sign-On Operator is installed you can create a Keycloak instance for use with Ansible Automation Platform. From here you provide an external Postgres or one will be created for you. Procedure Navigate to Operator Installed Operators . Select the rh-sso project. Select the Red Hat Single Sign-On Operator . On the Red Hat Single Sign-On Operator details page select Keycloak . Click Create instance . Click YAML view . The default Keycloak custom resource is as follows: apiVersion: keycloak.org/v1alpha1 kind: Keycloak metadata: name: example-keycloak labels: app: sso namespace: aap spec: externalAccess: enabled: true instances: 1 Click Create . When deployment is complete, you can use this credential to login to the administrative console. You can find the credentials for the administrator in the credential-<custom-resource> (example keycloak) secret in the namespace.

Commands:
apiVersion: keycloak.org/v1alpha1 kind: Keycloak metadata: name: example-keycloak labels: app: sso namespace: aap spec: externalAccess: enabled: true instances: 1
5.174. lohit-telugu-fonts 5.174.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:
7.78. gvfs 7.78.1. RHBA-2012:1124 - gvfs bug fix and enhancement update Updated gvfs packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. GVFS is the GNOME desktop's virtual file system layer, which allows users to easily access local and remote data, including via the FTP, SFTP, WebDAV, CIFS and SMB protocols, among others. GVFS integrates with the GIO (GNOME I/O) abstraction layer. Bug Fixes BZ#599055 Previously, rules for ignoring mounts were too restrictive. If the user clicked on an encrypted volume in the Nautilus' sidebar, an error message was displayed and the volume could not be accessed. The underlying source code now contains additional checks so that encrypted volumes have proper mounts associated (if available), and the file system can be browsed as expected. BZ#669526 Due to a bug in the kernel, a freshly formatted Blu-ray Disk Rewritable (BD-RE) medium contains a single track with invalid data that covers the whole medium. This empty track was previously incorrectly detected, causing the drive to be unusable for certain applications, such as Brasero. This update adds a workaround to detect the empty track, so that freshly formatted BD-RE media are properly recognized as blank. BZ#682799, BZ# 746977 , BZ# 746978 , BZ# 749369 , BZ# 749371 , BZ# 749372 The code of the gvfs-info, gvfs-open, gvfs-cat, gvfs-ls and gvfs-mount utilities contained hard-coded exit codes. This caused the utilities to always return zero on exit. The exit codes have been revised so that the mentioned gvfs utilities now return proper exit codes. BZ#746905 When running gvfs-set-attribute with an invalid command-line argument specified, the utility terminated unexpectedly with a segmentation fault. The underlying source code has been modified so that the utility now prints a proper error message when an invalid argument is specified. BZ#809708 Due to missing object cleanup calls, the gvfsd daemon could use excessive amount of memory, which caused the system to become unresponsive. Proper object cleanup calls have been added with this update, which ensures that the memory consumption is constant and the system does not hang in this scenario. All users of gvfs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
7.53. fcoe-target-utils 7.53.1. RHBA-2013:0457 - fcoe-target-utils bug fix and enhancement update Updated fcoe-target-utils packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The fcoe-target-utils packages provide a command-line interface for configuring FCoE LUNs (Fibre Channel over Ethernet Logical Unit Numbers) and backstores. Bug Fixes BZ# 819698 Prior to this update, stopping the fcoe-target daemon did not stop the target session when rebooting. This update improves the fcoe-target script and the fcoe-target daemon can now properly shut down the kernel target. BZ# 824227 Prior to this update, a delay in the FCoE interface initialization sometimes resulted in the target configuration not being loaded for that interface. This update permits target configuration for absent interfaces, allowing target and interface configuration in any order. BZ# 837730 Prior to this update, specifying a nonexistent backing file when creating a backstore resulted in the unhelpful Python error "ValueError: No such path". This update reports the error in a more helpful way. BZ#837992 Prior to this update, attempting to remove a storage object in a backstore resulted in a Python error. This update fixes the problem and storage objects can now be removed as expected. BZ# 838442 Prior to this update, attempting to redirect the output of targetcli resulted in a Python error. This update allows targetcli to be successfully redirected. BZ# 846670 Due to a regression, creating a backstore resulted in a Python error. This update allows backstore creation without error. Enhancements BZ# 828096 Prior to this update, backstore size listing abbreviations did not clearly specify between power of 10 (for example Gigabyte) and power of 2 (Gibibyte). This update lists backstore sizes using power-of-2 sizes and labels them as such. BZ# 828681 The caching characteristics of backstores are now exposed via the SCSI Write Cache Enable (WCE) bit to initiators, instead of being set opaquely via the "buffered-mode" backstore setting. The default setting for WCE is "on". All users of fcoe-target-utils are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Appendix C. Revision History Revision History Revision 6.6.0-1 Wed 7 Sep 2016 Christian Huffman Updating for 6.6.1. Revision 6.6.0-0 Thu 7 Jan 2016 Christian Huffman Initial draft for 6.6.0. Updated versions. BZ-1300709: Included note on Camel Quickstart for Fuse 6.2.1. BZ-1231129: Corrected the infinispan schema reference.

Commands:
Chapter 18. Changing a hostname The hostname of a system is the name on the system itself. You can set the name when you install RHEL, and you can change it afterwards. 18.1. Changing a hostname by using nmcli You can use the nmcli utility to update the system hostname. Note that other utilities might use a different term, such as static or persistent hostname. Procedure Optional: Display the current hostname setting: Set the new hostname: NetworkManager automatically restarts the systemd-hostnamed to activate the new name. For the changes to take effect, reboot the host: Alternatively, if you know which services use the hostname: Restart all services that only read the hostname when the service starts: Active shell users must re-login for the changes to take effect. Verification Display the hostname: 18.2. Changing a hostname by using hostnamectl You can use the hostnamectl utility to update the hostname. By default, this utility sets the following hostname types: Static hostname: Stored in the /etc/hostname file. Typically, services use this name as the hostname. Pretty hostname: A descriptive name, such as Proxy server in data center A . Transient hostname: A fall-back value that is typically received from the network configuration. Procedure Optional: Display the current hostname setting: Set the new hostname: This command sets the static, pretty, and transient hostname to the new value. To set only a specific type, pass the --static , --pretty , or --transient option to the command. The hostnamectl utility automatically restarts the systemd-hostnamed to activate the new name. For the changes to take effect, reboot the host: Alternatively, if you know which services use the hostname: Restart all services that only read the hostname when the service starts: Active shell users must re-login for the changes to take effect. Verification Display the hostname:

Commands:
nmcli general hostname old-hostname.example.com
nmcli general hostname new-hostname.example.com
reboot
systemctl restart <service_name>
nmcli general hostname new-hostname.example.com
hostnamectl status --static old-hostname.example.com
hostnamectl set-hostname new-hostname.example.com
reboot
systemctl restart <service_name>
hostnamectl status --static new-hostname.example.com
Chapter 11. Updating an RPM installation Before updating your current JBoss EAP instance by using the RPM installation method, check that your system meets certain setup prerequisites. Prerequisites You installed JBoss EAP server using RPM installation method. The base operating system is up to date, and you get updates from the standard Red Hat Enterprise Linux repositories. You are subscribed to the relevant JBoss EAP repository for the update. If you are subscribed to a minor JBoss EAP repository, you have changed to the latest minor repository to get the update. Important For a managed domain, update the JBoss EAP domain controller before you update to a newer release of JBoss EAP. An updated JBoss EAP 8.0 domain controller can still manage other JBoss EAP 8.0 hosts in a managed domain, as long as the domain controller is running the same or more recent version than the rest of the domain. Procedure Update your current JBoss EAP version to the newer JBoss EAP version by issuing the following command in your terminal: Enable new features in the updated release, such as new subsystems, by manually merging each .rpmnew file into your existing configuration files. The RPM update process does not replace any of your modified JBoss EAP configuration files, but it creates .rpmnew files based on the default configuration of your updated JBoss EAP instance. Additional resources For more information, see Installing JBoss EAP 8.0 using the RPM Installation installation method .

Commands:
dnf update
Chapter 12. Additional Installation Options All Red Hat Certificate System instances created with pkispawn make certain assumptions about the instances being installed, such as the default signing algorithm to use for CA signing certificates and whether to allow IPv6 addresses for hosts. This chapter describes additional configuration options that impact the installation and configuration for new instances, so many of these procedures occur before the instance is created. 12.1. Lightweight Sub-CAs Using the default settings, you are able to create lightweight sub-CAs. They enable you to configure services, like virtual private network (VPN) gateways, to accept only certificates issued by one sub-CA. At the same time, you can configure other services to accept only certificates issued by a different sub-CA or the root CA. If you revoke the intermediate certificate of a sub-CA, all certificates issued by this sub-CA are automatically invalid. If you set up the CA subsystem in Certificate System, it is automatically the root CA. All sub-CAs you create, are subordinated to this root CA. 12.1.1. Setting up a Lightweight Sub-CA Depending on your environment, the installation of a sub-CA differs between Internal CAs and External CAs. For more information, see Section 7.8, "Setting up Subsystems with an External CA" . 12.1.2. Disabling the Creation of Lightweight Sub-CAs In certain situations, administrators want to disable lightweight sub-CAs. To prevent adding, modifying, or removing sub-CAs, enter the following command on the Directory Server instance used by Certificate System: This command removes the default Access Control List (ACL) entries, which grant the permissions to manage sub-CAs. Note If any ACLs related to lightweight sub-CA creation have been modified or added, remove the relevant values. 12.1.3. Re-enabling the Creation of Lightweight Sub-CAs If you previously disabled the creation of lightweight sub-CAs, you can re-enable the feature by entering the following command on the Directory Server instance used by Certificate System: This command adds the Access Control List (ACL) entries, which grant the permissions to manage sub-CAs.

Commands:
ldapmodify -D "cn=Directory Manager" -W -x -h server.example.com dn: cn=aclResources,o= instance_name changetype: modify delete: resourceACLS resourceACLS: certServer.ca.authorities:create,modify:allow (create,modify) group="Administrators":Administrators may create and modify lightweight authorities delete: resourceACLS resourceACLS: certServer.ca.authorities:delete:allow (delete) group="Administrators":Administrators may delete lightweight authorities
ldapmodify -D "cn=Directory Manager" -W -x -h server.example.com dn: cn=aclResources,o= instance_name changetype: modify add: resourceACLS resourceACLS: certServer.ca.authorities:create,modify:allow (create,modify) group="Administrators":Administrators may create and modify lightweight authorities resourceACLS: certServer.ca.authorities:delete:allow (delete) group="Administrators":Administrators may delete lightweight authorities
Chapter 14. Idling applications Cluster administrators can idle applications to reduce resource consumption. This is useful when the cluster is deployed on a public cloud where cost is related to resource consumption. If any scalable resources are not in use, OpenShift Dedicated discovers and idles them by scaling their replicas to 0 . The time network traffic is directed to the resources, the resources are unidled by scaling up the replicas, and normal operation continues. Applications are made of services, as well as other scalable resources, such as deployment configs. The action of idling an application involves idling all associated resources. 14.1. Idling applications Idling an application involves finding the scalable resources (deployment configurations, replication controllers, and others) associated with a service. Idling an application finds the service and marks it as idled, scaling down the resources to zero replicas. You can use the oc idle command to idle a single service, or use the --resource-names-file option to idle multiple services. 14.1.1. Idling a single service Procedure To idle a single service, run: USD oc idle <service> 14.1.2. Idling multiple services Idling multiple services is helpful if an application spans across a set of services within a project, or when idling multiple services in conjunction with a script to idle multiple applications in bulk within the same project. Procedure Create a file containing a list of the services, each on their own line. Idle the services using the --resource-names-file option: USD oc idle --resource-names-file <filename> Note The idle command is limited to a single project. For idling applications across a cluster, run the idle command for each project individually. 14.2. Unidling applications Application services become active again when they receive network traffic and are scaled back up their state. This includes both traffic to the services and traffic passing through routes. Applications can also be manually unidled by scaling up the resources. Procedure To scale up a DeploymentConfig, run: USD oc scale --replicas=1 dc <dc_name> Note Automatic unidling by a router is currently only supported by the default HAProxy router.

Commands:
oc idle <service>
oc idle --resource-names-file <filename>
oc scale --replicas=1 dc <dc_name>
Preface The Package manifest document provides a package listing for Red Hat Enterprise Linux 9.0. Capabilities and limits of RHEL 9 as compared to other versions of the system are available in the Knowledgebase article Red Hat Enterprise Linux technology capabilities and limits . Information regarding the RHEL life cycle is provided in the Red Hat Enterprise Linux Life Cycle document. Detailed changes in each minor release of RHEL are documented in the Release notes . Changes to packages between RHEL 8 and RHEL 9, as well as changes between minor releases of RHEL 9, are listed in Considerations in adopting RHEL 9 . Application compatibility levels are explained in the Red Hat Enterprise Linux 9: Application Compatibility Guide document.

Commands:
Chapter 42. limits This chapter describes the commands under the limits command. 42.1. limits show Show compute and block storage limits Usage: Table 42.1. Command arguments Value Summary -h, --help Show this help message and exit --absolute Show absolute limits --rate Show rate limits --reserved Include reservations count [only valid with --absolute] --project <project> Show limits for a specific project (name or id) [only valid with --absolute] --domain <domain> Domain the project belongs to (name or id) [only valid with --absolute] Table 42.2. Output formatter options 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 to show multiple columns --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 --sort-ascending Sort the column(s) in ascending order --sort-descending Sort the column(s) in descending order Table 42.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 42.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 42.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack limits show [-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] [--sort-ascending | --sort-descending] (--absolute | --rate) [--reserved] [--project <project>] [--domain <domain>]
Chapter 17. Authentication and Interoperability SSSD fails to manage sudo rules from the IdM LDAP tree The System Security Services Daemon (SSSD) currently uses the IdM LDAP tree by default. As a consequence, it is not possible to assign sudo rules to non-POSIX groups. To work around this problem, modify the /etc/sssd/sssd.conf file to set your domain to use the compat tree again: As a result, SSSD will load sudo rules from the compat tree and you will be able to assign rules to non-POSIX groups. Note that Red Hat recommends to configure groups referenced in sudo rules as POSIX groups. (BZ#1336548) winbindd crashes when installing a new AD trust When configuring a new Active Directory (AD) trust on a newly installed system, the ipa-adtrust-install utility might report that the winbindd service terminated unexpectedly. Otherwise, ipa-adtrust-install completes successfully. If this problem occurs, restart the IdM services by using the ipactl restart command after running ipa-adtrust-install . This also restarts winbindd . Note that the full extent of the functional impact of this problem is still unknown. Some trust functionality might not work until winbindd is restarted. (BZ# 1399058 ) nslcd fails to resolve user or group identities when it is started before the network connection is fully up When nslcd , the local LDAP name service daemon, is started before the network connection is fully up, the daemon fails to connect to an LDAP server. As a consequence, resolving user or group identities does not work. To work around this problem, start nslcd after the network connection is up. (BZ# 1401632 )

Commands:
[domain/EXAMPLE] ldap_sudo_search_base = ou=sudoers,dc=example,dc=com
6.4. Additional Resources For more information on how to register your system using Red Hat Subscription Management and associate it with subscriptions, see the resources listed below. Installed Documentation subscription-manager (8) - the manual page for Red Hat Subscription Management provides a complete list of supported options and commands. Related Books Red Hat Subscription Management collection of guides - These guides contain detailed information how to use Red Hat Subscription Management. Installation Guide - see the Firstboot chapter for detailed information on how to register during the firstboot process. Online Resources Red Hat Access Labs - The Red Hat Access Labs includes a " Registration Assistant " . See Also Chapter 4, Gaining Privileges documents how to gain administrative privileges by using the su and sudo commands. Chapter 8, Yum provides information about using the yum packages manager to install and update software. Chapter 9, PackageKit provides information about using the PackageKit package manager to install and update software.

Commands: