mtpti5iD/redhat-docs_dataset huggingface dataset:
7.3. Booting from the Network Using PXE To boot with PXE, you need a properly configured server, and a network interface in your computer that supports PXE. For information on how to configure a PXE server, refer to Chapter 30, Setting Up an Installation Server . Configure the computer to boot from the network interface. This option is in the BIOS, and may be labeled Network Boot or Boot Services . Once you properly configure PXE booting, the computer can boot the Red Hat Enterprise Linux installation system without any other media. To boot a computer from a PXE server: Ensure that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on. Switch on the computer. A menu screen appears. Press the number key that corresponds to the desired option. If your PC does not boot from the netboot server, ensure that the BIOS is configured to boot first from the correct network interface. Some BIOS systems specify the network interface as a possible boot device, but do not support the PXE standard. Refer to your hardware documentation for more information. Note Some servers with multiple network interfaces might not assign eth0 to the first network interface as the firmware interface knows it, which can cause the installer to try to use a different network interface from the one that was used by PXE. To change this behavior, use the following in pxelinux.cfg/* config files: These configuration options above cause the installer to use the same network interface the firmware interface and PXE use. You can also use the following option: This option causes the installer to use the first network device it finds that is linked to a network switch.

Commands:
IPAPPEND 2 APPEND ksdevice=bootif
ksdevice=link
probe::nfs.aop.write_begin Name probe::nfs.aop.write_begin - NFS client begin to write data Synopsis nfs.aop.write_begin Values __page the address of page page_index offset within mapping, can used a page identifier and position identifier in the page frame size write bytes to end address of this write operation ino inode number offset start address of this write operation dev device identifier Description Occurs when write operation occurs on nfs. It prepare a page for writing, look for a request corresponding to the page. If there is one, and it belongs to another file, it flush it out before it tries to copy anything into the page. Also do the same if it finds a request from an existing dropped page

Commands:
1.5.2. Firewall Marks Firewall marks are an easy and efficient way to group ports used for a protocol or group of related protocols. For instance, if Load Balancer Add-On is deployed to run an e-commerce site, firewall marks can be used to bundle HTTP connections on port 80 and secure, HTTPS connections on port 443. By assigning the same firewall mark to the virtual server for each protocol, state information for the transaction can be preserved because the LVS router forwards all requests to the same real server after a connection is opened. Because of its efficiency and ease-of-use, administrators of Load Balancer Add-On should use firewall marks instead of persistence whenever possible for grouping connections. However, administrators should still add persistence to the virtual servers in conjunction with firewall marks to ensure the clients are reconnected to the same server for an adequate period of time.

Commands:
20.4. Caching Kerberos Passwords A machine may not always be on the same network as the IdM domain; for example, a machine may need to be logged into a VPN before it can access the IdM domain. If a user logs into a system when it is offline and then later attempts to connect to IdM services, then the user is blocked because there is no IdM Kerberos ticket for that user. IdM works around that limitation by using SSSD to store the Kerberos passwords in the SSSD cache. This is configured by default by the ipa-client-install script. A configuration parameter is added to the /etc/sssd/sssd.conf file which specifically instructs SSSD to store those Kerberos passwords for the IdM domain: [domain/example.com] cache_credentials = True ipa_domain = example.com id_provider = ipa auth_provider = ipa access_provider = ipa chpass_provider = ipa ipa_server = _srv_, server.example.com krb5_store_password_if_offline = true This default behavior can be disabled during the client installation by using the --no-krb5-offline-passwords option. This behavior can also be disabled by editing the /etc/sssd/sssd.conf file and removing the krb5_store_password_if_offline line or changing its value to false. [domain/example.com] ... krb5_store_password_if_offline = false The SSSD configuration options for Kerberos authentication is covered in the "Configuring Domains" section of the SSSD chapter in the Red Hat Enterprise Linux Deployment Guide .

Commands:
[domain/example.com] cache_credentials = True ipa_domain = example.com id_provider = ipa auth_provider = ipa access_provider = ipa chpass_provider = ipa ipa_server = _srv_, server.example.com krb5_store_password_if_offline = true
[domain/example.com] krb5_store_password_if_offline = false
Preface Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security, and bug fix errata. The Red Hat Enterprise Linux 7.1 Release Notes document the major changes, features, and enhancements introduced in the Red Hat Enterprise Linux 7 operating system and its accompanying applications for this minor release. In addition, the Red Hat Enterprise Linux 7.1 Release Notes document the known issues in Red Hat Enterprise Linux 7.1. For information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands:
Chapter 1. Introduction Directory Server is based on an open-systems server protocol called the Lightweight Directory Access Protocol (LDAP). The Directory Server is a robust, scalable server designed to manage large scale directories to support an enterprise-wide directory of users and resources, extranets, and e-commerce applications over the Internet. The Directory Server runs as the ns-slapd process or service on the machine. The server manages the directory databases and responds to client requests. Most Directory Server administrative tasks can be performed through the Directory Server Console, the graphical user interface provided with the Directory Server. For information on the use of the Directory Server Console, see the Red Hat Directory Server Administration Guide . This reference deals with the other methods of managing the Directory Server by altering the server configuration attributes using the command line and using command-line utilities and scripts. 1.1. Directory Server Configuration The format and method for storing configuration information for Directory Server and a listing for all server attributes are found in two chapters, Chapter 3, Core Server Configuration Reference and Chapter 4, Plug-in Implemented Server Functionality Reference . 1.2. Directory Server Instance File Reference Section 2.1, "Directory Server Instance-independent Files and Directories" has an overview of the files and configuration information stored in each instance of Directory Server. This is useful reference to helps administrators understand the changes or absence of changes in the course of directory activity. From a security standpoint, this also helps users detect errors and intrusion by highlighting normal changes and abnormal behavior. 1.3. Using Directory Server Command-Line Utilities Directory Server comes with a set of configurable command-line utilities that can search and modify entries in the directory and administer the server. Chapter 9, Command-Line Utilities describes these command-line utilities and contains information on where the utilities are stored and how to access them.

Commands:
15.3. The Virtual Hardware Details Window The virtual hardware details window displays information about the virtual hardware configured for the guest. Virtual hardware resources can be added, removed and modified in this window. To access the virtual hardware details window, click on the icon in the toolbar. Figure 15.3. The virtual hardware details icon Clicking the icon displays the virtual hardware details window. Figure 15.4. The virtual hardware details window 15.3.1. Attaching USB Devices to a Guest Virtual Machine Note In order to attach the USB device to the guest virtual machine, you first must attach it to the host physical machine and confirm that the device is working. If the guest is running, you need to shut it down before proceeding. Procedure 15.1. Attaching USB Devices using Virt-Manager Open the guest virtual machine's Virtual Machine Details screen. Click Add Hardware Figure 15.5. Add Hardware Button In the Add New Virtual Hardware popup, select USB Host Device , select the device you want to attach from the list and Click Finish . Figure 15.6. Add USB Device To use the USB device in the guest virtual machine, start the guest virtual machine.

Commands:
3.9. Software Collection Log File Support By default, programs packaged in a Software Collection create log files in the /opt/ provider /%{scl}/root/var/log/ directory. To make log files more accessible and easier to manage, you are advised to use the nfsmountable macro that redefines the _localstatedir macro. This results in log files being created underneath the /var/opt/ provider /%{scl}/log/ directory, outside of the /opt/ provider /%{scl} file system hierarchy. For example, a service mydaemon normally stores its log file in /var/log/mydaemon/mydaemond.log in the base system installation. When mydaemon is packaged as a software_collection Software Collection and the nfsmountable macro is defined, the path to the log file in software_collection is as follows: For more information on using the nfsmountable macro, see Section 3.1, "Using Software Collections over NFS" .

Commands:
/var/opt/ provider / software_collection /log/ mydaemon / mydaemond.log
Preface Red Hat Ansible Automation Platform is a unified automation solution that automates a variety of IT processes, including provisioning, configuration management, application deployment, orchestration, and security and compliance changes (including patching systems). Ansible Automation Platform features a platform interface where you can set up centralized authentication, configure access management, and execute automation tasks from a single location. This guide will help you get started with Ansible Automation Platform by introducing three central concepts: automation execution, automation decisions, and automation content.

Commands:
20.4. Retrieving ACLs To determine the existing ACLs for a file or directory, use the getfacl command. In the example below, the getfacl is used to determine the existing ACLs for a file. Example 20.4. Retrieving ACLs The above command returns the following output: If a directory with a default ACL is specified, the default ACL is also displayed as illustrated below. For example, getfacl home/sales/ will display similar output:

Commands:
getfacl home/john/picture.png
file: home/john/picture.png owner: john group: john user::rw- group::r-- other::r--
file: home/sales/ owner: john group: john user::rw- user:barryg:r-- group::r-- mask::r-- other::r-- default:user::rwx default:user:john:rwx default:group::r-x default:mask::rwx default:other::r-x
10.3. Modifying Quorum Options (Red Hat Enterprise Linux 7.3 and later) As of Red Hat Enterprise Linux 7.3, you can modify general quorum options for your cluster with the pcs quorum update command. Executing this command requires that the cluster be stopped. For information on the quorum options, see the votequorum (5) man page. The format of the pcs quorum update command is as follows. The following series of commands modifies the wait_for_all quorum option and displays the updated status of the option. Note that the system does not allow you to execute this command while the cluster is running.

Commands:
pcs quorum update [auto_tie_breaker=[0|1]] [last_man_standing=[0|1]] [last_man_standing_window=[ time-in-ms ] [wait_for_all=[0|1]]
pcs quorum update wait_for_all=1 Checking corosync is not running on nodes Error: node1: corosync is running Error: node2: corosync is running pcs cluster stop --all node2: Stopping Cluster (pacemaker) node1: Stopping Cluster (pacemaker) node1: Stopping Cluster (corosync) node2: Stopping Cluster (corosync) pcs quorum update wait_for_all=1 Checking corosync is not running on nodes node2: corosync is not running node1: corosync is not running Sending updated corosync.conf to nodes node1: Succeeded node2: Succeeded pcs quorum config Options: wait_for_all: 1
29.3. Protecting Keytabs To protect Kerberos keytabs from other users with access to the server, restrict access to the keytab to only the keytab owner. It is recommended to protect the keytabs right after they are retrieved. For example, to protect the Apache keytab at /etc/httpd/conf/ipa.keytab : Set the owner of the file to apache . Set the permissions for the file to 0600 . This grants read, write, and execute permissions to the owner.

Commands:
chown apache /etc/httpd/conf/ipa.keytab
chmod 0600 /etc/httpd/conf/ipa.keytab
Chapter 8. Important links Red Hat AMQ Broker 7.11 Release Notes Red Hat AMQ Broker 7.10 Release Notes Red Hat AMQ Broker 7.9 Release Notes Red Hat AMQ Broker 7.8 Release Notes Red Hat AMQ Broker 7.7 Release Notes Red Hat AMQ Broker 7.6 Release Notes Red Hat AMQ Broker 7.1 to 7.5 Release Notes (aggregated) Red Hat AMQ 7 Supported Configurations Red Hat AMQ 7 Component Details Revised on 2025-03-18 14:05:28 UTC

Commands:
Providing feedback on Red Hat documentation We appreciate your input on our documentation. Please let us know how we could make it better. To do so: For simple comments on specific passages, make sure you are viewing the documentation in the HTML format. Highlight the part of text that you want to comment on. Then, click the Add Feedback pop-up that appears below the highlighted text, and follow the displayed instructions. For submitting more complex feedback, create a Bugzilla ticket: Go to the Bugzilla website. As the Component, use Documentation . Fill in the Description field with your suggestion for improvement. Include a link to the relevant part(s) of documentation. Click Submit Bug .

Commands:
2.7. Design-Time and Runtime Metadata Teiid Designer software distinguishes between design-time metadata and runtime metadata. This distinction becomes important if you use the JBoss Data Virtualization Server. Design-time data is laden with details and representations that help the user understand and efficiently organize metadata. Much of that detail is unnecessary to the underlying system that runs the Virtual Database that you will create. Any information that is not absolutely necessary to running the Virtual Database is stripped out of the runtime metadata to ensure maximum system performance.

Commands:
Chapter 8. Reinstalling an Existing Host as a Self-Hosted Engine Node You can convert an existing, standard host in a self-hosted engine environment to a self-hosted engine node capable of hosting the Manager virtual machine. Procedure Click Compute Hosts and select the host. Click Management Maintenance and click OK . Click Installation Reinstall . Click the Hosted Engine tab and select DEPLOY from the drop-down list. Click OK . The host is reinstalled with self-hosted engine configuration, and is flagged with a crown icon in the Administration Portal. After reinstalling the hosts as self-hosted engine nodes, you can check the status of the new environment by running the following command on one of the nodes: If the new environment is running without issue, you can decommission the original Manager machine.

Commands:
hosted-engine --vm-status
Chapter 2. Accessing the Fuse Console Follow these steps to access the Fuse Console for Red Hat JBoss Enterprise Application Platform. Prerequisite You must install Fuse on the JBoss EAP container. For step-by-step instructions, see Installing on JBoss EAP . Procedure To access the Fuse Console for a standalone JBoss EAP distribution: Start Red Hat Fuse standalone with the following command: On Linux/Mac OS: ./bin/standalone.sh On Windows: ./bin/standalone.bat In a web browser, enter the URL to connect to the Fuse Console. For example: http://localhost:8080/hawtio In the login page, enter your user name and password and then click Log In . By default, the Fuse Console shows the Home page. The left navigation tabs indicate the running plugins. Note If the main Fuse Console page takes a long time to display in the browser, you might need to reduce the number and the size of the log files. You can use the periodic-size-rotating-file-handler to rotate the file when it reaches a maximum size (rotate-size) and maintains a number of files (max-backup-index). For details on how to use this handler, see the Red Hat JBoss Enterprise Application Platform product documentation.

Commands:
15.5.6. File Transfer Options The following lists directives which affect directories. download_enable - When enabled, file downloads are permitted. The default value is YES . chown_uploads - When enabled, all files uploaded by anonymous users are owned by the user specified in the chown_username directive. The default value is NO . chown_username - Specifies the ownership of anonymously uploaded files if the chown_uploads directive is enabled. The default value is root . write_enable - When enabled, FTP commands which can change the file system are allowed, such as DELE , RNFR , and STOR . The default value is YES .

Commands:
Chapter 5. Troubleshooting RHOSP dynamic routing Diagnosing problems in a Red Hat OpenStack Platform (RHOSP) environment that uses dynamic routing begins with examining the appropriate logs and querying the various FRRouting components with VTY shell. The topics included in this section are: OVN BGP agent and FRRouting logs Using VTY shell commands for troubleshooting BGP 5.1. OVN BGP agent and FRRouting logs The Red Hat OpenStack Platform (RHOSP) OVN BGP agent writes its logs on the Compute and Networker nodes at this location: /var/log/containers/stdouts/ovn_bgp_agent.log . The Free Range Routing (FRRouting, or FRR) components such as the BGP, BFD, and Zebra daemons write their logs on all RHOSP nodes at this location: /var/log/containers/frr/frr.log 5.2. Using VTY shell commands for troubleshooting BGP You can use the shell for Virtual Terminal Interface (VTY shell) to interact with the Free Range Routing (FRRouting, or FRR) daemons. In Red Hat OpenStack Platform, FRR daemons like bgpd run inside a container. Using the VTY shell can help you troubleshoot BGP routing issues. Prerequisites You must have sudo privileges on the host where you want to run VTY shell commands. Procedure Log in to the host where you want to troubleshoot the BGP daemon, bgpd . Typically, bgpd runs on all of the overcloud nodes. Enter the FRR container. You have two options for running VTY shell commands: Interactive mode Type sudo vtysh once to enter interactive mode to run multiple VTY shell commands. Example Direct mode Preface each VTY shell command with sudo vtysh -c . Example Here are several VTY shell BGP daemon troubleshooting commands: Tip Omit the ip argument when you are using IPv6. Display a particular routing table or all routing tables: Output routes advertised to a BGP peer Output routes received from a BGP peer Additional resources Displaying BGP Information in the FRRouting User Guide

Commands:
sudo podman exec -it frr bash
sudo vtysh > show bgp summary
sudo vtysh -c 'show bgp summary'
> show ip bgp <IPv4_address> | all > show bgp <IPv6_address> | all
> show ip bgp neighbors <router-ID> <advertised-routes>
> show ip bgp neighbors <router-ID> <received-routes>
Chapter 18. Managing asset metadata and version history Most assets within Business Central have metadata and version information associated with them to help you identify and organize them within your projects. You can manage asset metadata and version history from the asset designer in Business Central. Procedure In Business Central, go to Menu Design Projects and click the project name. Select the asset from the list to open the asset designer. In the asset designer window, select Overview . If an asset doesn't have an Overview tab, then no metadata is associated with that asset. Select the Version History or Metadata tab to edit and update version and metadata details. Note Another way to update the working version of an asset is by clicking Latest Version in the top-right corner of the asset designer. Figure 18.1. Latest version of an asset Click Save to save changes.

Commands:
C.7. ClusterCacheStats org.infinispan.stats.impl.ClusterCacheStatsImpl The ClusterCacheStats component contains statistics such as timings, hit/miss ratio, and operation information for the whole cluster. Table C.12. Attributes Name Description Type Writable activations The total number of activations in the cluster. long No averageReadTime Cluster wide total average number of milliseconds for a read operation on the cache. long No averageRemoveTime Cluster wide total average number of milliseconds for a remove operation in the cache. long No averageWriteTime Cluster wide average number of milliseconds for a write operation in the cache. long No cacheLoaderLoads The total number of cacheloader load operations in the cluster. long No cacheLoaderMisses The total number of cacheloader load misses in the cluster. long No evictions Cluster wide total number of cache eviction operations. long No hitRatio Cluster wide total percentage hit/(hit+miss) ratio for this cache. double No hits Cluster wide total number of cache hits. long No invalidations The total number of invalidations in the cluster. long No misses Cluster wide total number of cache attribute misses. long No numberOfEntries Cluster wide total number of entries currently in the cache. int No numberOfLocksAvailable Total number of exclusive locks available in the cluster. int No numberOfLocksHeld The total number of locks held in the cluster. int No passivations The total number of passivations in the cluster. long No readWriteRatio Cluster wide read/writes ratio for the cache. double No removeHits Cluster wide total number of cache removal hits. double No removeMisses Cluster wide total number of cache removals where keys were not found. long No statisticsEnabled Enables or disables the gathering of statistics by this component. boolean Yes storeWrites The total number of cachestore store operations in the cluster. long No stores Cluster wide total number of cache attribute put operations. long No timeSinceStart Number of seconds since the first cache node started. long No Table C.13. Operations Name Description Signature setStaleStatsTreshold Sets the threshold for cluster wide stats refresh (in milliseconds). void setStaleStatsTreshold(long staleStatsThreshold) resetStatistics Resets statistics gathered by this component. void resetStatistics() Report a bug

Commands: