mtpti5iD/redhat-docs_dataset huggingface dataset:
7.2. Block I/O Tuning The virsh blkiotune command allows administrators to set or display a guest virtual machine's block I/O parameters manually in the <blkio> element in the guest XML configuration. To display current <blkio> parameters for a virtual machine: To set a virtual machine's <blkio> parameters, refer to the following command and replace values according to your environment: Parameters include: weight The I/O weight, within the range 100 to 1000. device-weights A single string listing one or more device/weight pairs, in the format of /path/to/device ,weight, /path/to/device ,weight . Each weight must be within the range 100-1000, or the value 0 to remove that device from per-device listings. Only the devices listed in the string are modified; any existing per-device weights for other devices remain unchanged. config Add the --config option for changes to take effect at boot. live Add the --live option to apply the changes to the running virtual machine. Note The --live option requires the hypervisor to support this action. Not all hypervisors allow live changes of the maximum memory limit. current Add the --current option to apply the changes to the current virtual machine. Note See # virsh help blkiotune for more information on using the virsh blkiotune command.

Commands:
virsh blkiotune virtual_machine
virsh blkiotune virtual_machine [--weight number ] [--device-weights string ] [--config] [--live] [--current]
Chapter 10. Restricting the session to a single application You can start the GNOME session in single-application mode, also known as kiosk mode. In this session, GNOME displays only a full-screen window of the application that you have selected. 10.1. Single-application mode Single-application mode is a modified GNOME session that reconfigures the Mutter window manager into an interactive kiosk. This session locks down certain behavior to make the standard desktop more restrictive. The user can interact only with a single application selected by the administrator. You can set up single-application mode for several use cases, such as: In the communication, entertainment, or education fields As a self-serve machine As an event manager As a registration point The GNOME Kiosk utility provides the single-application mode configuration and sessions. The following single-application sessions are available: Search Appliance Session This session always starts the Mozilla Firefox web browser at the www.google.com website. Kiosk Script Session This session starts an arbitrary application that you specify in a shell script. 10.2. Enabling search appliance mode This procedure installs and enables the Search Appliance Session, which restricts the GNOME session to the Google search engine in a web browser. Procedure Install the GNOME Kiosk packages: At the GNOME login screen, select Search Appliance Session from the gear button menu and log in as the single-application user. The Mozilla Firefox browser opens as a full-screen window in its kiosk mode. It shows the Google search page. Additional resources The /usr/share/doc/gnome-kiosk/README.md file provided by the gnome-kiosk package. 10.3. Enabling single-application mode This procedure installs and enables the Kiosk Script Session, which restricts the GNOME session to a selected single application. Procedure Install the GNOME Kiosk packages: At the GNOME login screen, select Kiosk Script Session from the gear button menu and log in as the single-application user. The gedit text editor opens as a full-screen window. It shows the shell script that configures which application runs in your single-application session. Edit the shell script and enter the application that you want to start in the single-application session. For example, to start the Mozilla Firefox browser, enter the following content: Save the script file. Close the gedit window. The session terminates and restarts with your selected application. The time you log into the single-application session, your selected application runs. Additional resources The /usr/share/doc/gnome-kiosk/README.md file provided by the gnome-kiosk package.

Commands:
dnf install gnome-kiosk gnome-kiosk-search-appliance
dnf install gnome-kiosk gnome-kiosk-script-session
#!/usr/bin/sh firefox --kiosk https://example.org
Chapter 7. Supported integration products AMQ Streams 2.1 supports integration with the following Red Hat products. Red Hat Single Sign-On Provides OAuth 2.0 authentication and OAuth 2.0 authorization. Red Hat 3scale API Management Secures the Kafka Bridge and provides additional API management features. Red Hat Debezium Monitors databases and creates event streams. Red Hat Service Registry Provides a centralized store of service schemas for data streaming. For information on the functionality these products can introduce to your AMQ Streams deployment, refer to the product documentation. Additional resources Red Hat Single Sign-On Supported Configurations Red Hat 3scale API Management Supported Configurations Red Hat Debezium Supported Configurations Red Hat Service Registry Supported Configurations

Commands:
5.347. vios-proxy 5.347.1. RHBA-2012:0755 - vios-proxy bug fix update Updated vios-proxy packages that fix one bug are now available for Red Hat Enterprise Linux 6. The vios-proxy program suite creates a network tunnel between a server in the QEMU host and a client in a QEMU guest. The proxied server and client programs open normal TCP network ports on localhost and the vios-proxy tunnel connects them using QEMU virtioserial channels. Bug Fix BZ# 743723 Previously, the packages did not contain manual pages for the vios-proxy-host and vios-proxy-guest daemons. With this update, these manual pages are now available. All users of vios-proxy are advised to upgrade to these updated packages, which fix this bug.

Commands:
19.7. Administering User Tasks From the Administration Portal 19.7.1. Adding Users and Assigning VM Portal Permissions Users must be created already before they can be added and assigned roles and permissions. The roles and permissions assigned in this procedure give the user the permission to log in to the VM Portal and to start creating virtual machines. The procedure also applies to group accounts. Adding Users and Assigning VM Portal Permissions On the header bar, click Administration Configure to open the Configure window. Click System Permissions . Click Add to open the Add System Permission to User window. Select a profile under Search . The profile is the domain you want to search. Enter a name or part of a name in the search text field, and click GO . Alternatively, click GO to view a list of all users and groups. Select the check boxes for the appropriate users or groups. Select an appropriate role to assign under Role to Assign . The UserRole role gives the user account the permission to log in to the VM Portal. Click OK . Log in to the VM Portal to verify that the user account has the permissions to log in. 19.7.2. Viewing User Information Viewing User Information Click Administration Users to display the list of authorized users. Click the user's name to open the details view, usually with the General tab displaying general information, such as the domain name, email and status of the user. The other tabs allow you to view groups, permissions, quotas, and events for the user. For example, to view the groups to which the user belongs, click the Directory Groups tab. 19.7.3. Viewing User Permissions on Resources Users can be assigned permissions on specific resources or a hierarchy of resources. You can view the assigned users and their permissions on each resource. Viewing User Permissions on Resources Find and click the resource's name to open the details view. Click the Permissions tab to list the assigned users, the user's role, and the inherited permissions for the selected resource. 19.7.4. Removing Users When a user account is no longer required, remove it from Red Hat Virtualization. Removing Users Click Administration Users to display the list of authorized users. Select the user to be removed. Ensure the user is not running any virtual machines. Click Remove , then click OK . The user is removed from Red Hat Virtualization, but not from the external directory. 19.7.5. Viewing Logged-In Users You can view the users who are currently logged in, along with session times and other details. Click Administration Active User Sessions to view the Session DB ID , User Name , Authorization provider , User id , Source IP , Session Start Time , and Session Last Active Time for each logged-in user. 19.7.6. Terminating a User Session You can terminate the session of a user who is currently logged in. Terminating a User Session Click Administration Active User Sessions . Select the user session to be terminated. Click Terminate Session . Click OK .

Commands:
Chapter 2. Acknowledgments Red Hat Ceph Storage version 7.0 contains many contributions from the Red Hat Ceph Storage team. In addition, the Ceph project is seeing amazing growth in the quality and quantity of contributions from individuals and organizations in the Ceph community. We would like to thank all members of the Red Hat Ceph Storage team, all of the individual contributors in the Ceph community, and additionally, but not limited to, the contributions from organizations such as: Intel(R) Fujitsu (R) UnitedStack Yahoo TM Ubuntu Kylin Mellanox (R) CERN TM Deutsche Telekom Mirantis (R) SanDisk TM SUSE (R) Croit TM Clyso TM Cloudbase solutions TM

Commands:
4.2. Server Support Running the Certificate Authority (CA), Key Recovery Authority (KRA), Online Certificate Status Protocol (OCSP), Token Key Service (TKS), and Token Processing System (TPS) subsystems of Certificate System 10.6 is supported on Red Hat Enterprise Linux 8.8. The supported Directory Server version is 11.7. For more information, see the Section 1.3.1, "Server Support" of the release notes. Note Certificate System 10.6 is supported running on a Red Hat Enterprise Linux 8.8 virtual guest on a certified hypervisor. For details, see the Which hypervisors are certified to run Red Hat Enterprise Linux? solution article.

Commands:
11.4. Enabling and Disabling User Accounts The administrator can disable and enable active user accounts. Disabling a user account deactivates the account. Disabled user accounts cannot be used to authenticate. A user whose account has been disabled cannot log into IdM and cannot use IdM services, such as Kerberos, or perform any tasks. Disabled user accounts still exist within IdM and all of the associated information remains unchanged. Unlike preserved user accounts, disabled user accounts remain in the active state. Therefore, they are displayed in the output of the ipa user-find command. For example: Any disabled user account can be enabled again. Note After disabling a user account, existing connections remain valid until the user's Kerberos TGT and other tickets expire. After the ticket expires, the user will not be able renew it. Enabling and Disabling User Accounts in the Web UI Select the Identity Users tab. From the Active users list, select the required user or users, and then click Disable or Enable . Figure 11.12. Disabling or Enabling a User Account Disabling and Enabling User Accounts from the Command Line To disable a user account, use the ipa user-disable command. To enable a user account, use the ipa user-enable command.

Commands:
ipa user-find User login: user First name: User Last name: User Home directory: /home/user Login shell: /bin/sh UID: 1453200009 GID: 1453200009 Account disabled: True Password: False Kerberos keys available: False
ipa user-disable user_login ---------------------------- Disabled user account "user_login" ----------------------------
ipa user-enable user_login ---------------------------- Enabled user account "user_login" ----------------------------
7.2.2. Window Managers Window managers are X client programs which are either part of a desktop environment or, in some cases, standalone. Their primary purpose is to control the way graphical windows are positioned, resized, or moved. Window managers also control title bars, window focus behavior, and user-specified key and mouse button bindings. Four window managers are included with Red Hat Enterprise Linux: kwin - The KWin window manager is the default window manager for KDE. It is an efficient window manager which supports custom themes. metacity - The Metacity window manager is the default window manager for GNOME. It is a simple and efficient window manager which supports custom themes. mwm - The Motif window manager is a basic, standalone window manager. Since it is designed to be a standalone window manager, it should not be used in conjunction with GNOME or KDE. twm - The minimalist Tab Window Manager , which provides the most basic tool set of any of the window managers and can be used either as a standalone or with a desktop environment. It is installed as part of the X11R6.8 release. These window managers can be run without desktop environments to gain a better sense of their differences. To do this, type the xinit -e <path-to-window-manager> command, where <path-to-window-manager> is the location of the window manager binary file. The binary file can be found by typing which <window-manager-name> , where <window-manager-name> is the name of the window manager you are querying.

Commands:
4.105. jasper 4.105.1. RHSA-2011:1807 - Important: jasper security update Updated jasper packages that fix two security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. JasPer is an implementation of Part 1 of the JPEG 2000 image compression standard. Security Fix CVE-2011-4516 , CVE-2011-4517 Two heap-based buffer overflow flaws were found in the way JasPer decoded JPEG 2000 compressed image files. An attacker could create a malicious JPEG 2000 compressed image file that, when opened, would cause applications that use JasPer (such as Nautilus) to crash or, potentially, execute arbitrary code. Red Hat would like to thank Jonathan Foote of the CERT Coordination Center for reporting these issues. Users are advised to upgrade to these updated packages, which contain a backported patch to correct these issues. All applications using the JasPer libraries (such as Nautilus) must be restarted for the update to take effect.

Commands:
Chapter 1. Required Infrastructure Component Versions When you work with Red Hat support for Spring Boot, you can use the following components. However, Red Hat does not provide support for components listed below except Red Hat OpenShift cluster and Red Hat OpenJDK. Required components The following components are required to build and develop applications using Spring Boot. Table 1.1. Required components Component name Version Maven 3.6.3 JDK [a] OpenJDK 8, OpenJDK 11, OpenJDK 17 [a] A full JDK installation is required because JRE does not provide tools for compiling Java applications from source. Optional components Red Hat recommends using the following components depending on your development and production environments. Table 1.2. Optional components Component name Version git 2.0 or later oc command line tool 4.12 or later [a] Access to a Red Hat OpenShift cluster [b] 4.12, 4.13 [a] The version of the oc CLI tool should correspond to the version of OCP that you are using. [b] OpenShift cluster is supported by Red Hat.

Commands:
11.6.2. Useful Websites http://www.redhat.com/mirrors/LDP/HOWTO/Mail-Administrator-HOWTO.html - Provides an overview of how email works, and examines possible email solutions and configurations on the client and server sides. http://www.redhat.com/mirrors/LDP/HOWTO/Mail-User-HOWTO/ - Looks at email from the user's perspective, investigates various popular email client applications and gives an introduction to topics such as aliases, forwarding, auto-replying, mailing lists, mail filters, and spam. http://www.redhat.com/mirrors/LDP/HOWTO/mini/Secure-POP+SSH.html - Demonstrates a way to retrieve POP email using SSH with port forwarding, so that the email passwords and messages are transferred securely. http://www.sendmail.net/ - Contains news, interviews, and articles concerning Sendmail, including an expanded view of the many options available. http://www.sendmail.org/ - Offers a thorough technical breakdown of Sendmail features and configuration examples. http://www.postfix.org/ - The Postfix project home page contains a wealth of information about Postfix. The mailing list is a particularly good place to look for information. http://catb.org/~esr/fetchmail/ - The home page for Fetchmail, featuring an online manual, and a thorough FAQ. http://www.procmail.org/ - The home page for Procmail with links to assorted mailing lists dedicated to Procmail as well as various FAQ documents. http://www.ling.helsinki.fi/users/reriksso/procmail/mini-faq.html - An excellent Procmail FAQ, offers troubleshooting tips, details about file locking, and the use of wildcard characters. http://www.uwasa.fi/~ts/info/proctips.html - Contains dozens of tips that make using Procmail much easier. Includes instructions on how to test .procmailrc files and use Procmail scoring to decide if a particular action should be taken. http://www.spamassassin.org/ - The official site of the SpamAssassin project.

Commands:
3.4. RHEA-2011:1636 - new package: libvirt-qmf A new libvirt-qmf package is now available for Red Hat Enterprise Linux 6. The libvirt-qmf package contains a daemon to allow remote control of the libvirt API through the Qpid Management Framework (QMF). Enhancement BZ# 688194 With this update, the libvirt-qmf package obsoletes the libvirt-qpid package, which provided similar functionality. The new package uses the matahari library to provide an interface consistent with that of other Matahari agents. Note: After installation, it is advisable to convert existing QMF consoles, that previously connected to libvirt-qpid, to use libvirt-qmf as their interface. Also, when creating a new QMF console, it is recommended to use libvirt-qmf to communicate with libvirt. All users requiring libvirt-qmf are advised to install this new package, which adds this enhancement.

Commands:
2.8.4. Common IPTables Filtering Preventing remote attackers from accessing a LAN is one of the most important aspects of network security. The integrity of a LAN should be protected from malicious remote users through the use of stringent firewall rules. However, with a default policy set to block all incoming, outgoing, and forwarded packets, it is impossible for the firewall/gateway and internal LAN users to communicate with each other or with external resources. To allow users to perform network-related functions and to use networking applications, administrators must open certain ports for communication. For example, to allow access to port 80 on the firewall , append the following rule: This allows users to browse websites that communicate using the standard port 80. To allow access to secure websites (for example, https://www.example.com/), you also need to provide access to port 443, as follows: Important When creating an iptables ruleset, order is important. If a rule specifies that any packets from the 192.168.100.0/24 subnet be dropped, and this is followed by a rule that allows packets from 192.168.100.13 (which is within the dropped subnet), then the second rule is ignored. The rule to allow packets from 192.168.100.13 must precede the rule that drops the remainder of the subnet. To insert a rule in a specific location in an existing chain, use the -I option. For example: This rule is inserted as the first rule in the INPUT chain to allow local loopback device traffic. There may be times when you require remote access to the LAN. Secure services, for example SSH, can be used for encrypted remote connection to LAN services. Administrators with PPP-based resources (such as modem banks or bulk ISP accounts), dial-up access can be used to securely circumvent firewall barriers. Because they are direct connections, modem connections are typically behind a firewall/gateway. For remote users with broadband connections, however, special cases can be made. You can configure iptables to accept connections from remote SSH clients. For example, the following rules allow remote SSH access: These rules allow incoming and outbound access for an individual system, such as a single PC directly connected to the Internet or a firewall/gateway. However, they do not allow nodes behind the firewall/gateway to access these services. To allow LAN access to these services, you can use Network Address Translation ( NAT ) with iptables filtering rules.

Commands:
~]# iptables -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT
~]# iptables -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT
~]# iptables -I INPUT 1 -i lo -p all -j ACCEPT
~]# iptables -A INPUT -p tcp --dport 22 -j ACCEPT ~]# iptables -A OUTPUT -p tcp --sport 22 -j ACCEPT
2.7.2. Configuration File Directives The following are directives commonly used in the GRUB menu configuration file: chainloader </path/to/file> - Loads the specified file as a chain loader. Replace </path/to/file> with the absolute path to the chain loader. If the file is located on the first sector of the specified partition, use the blocklist notation, +1 . color <normal-color> <selected-color> - Allows specific colors to be used in the menu, where two colors are configured as the foreground and background. Use simple color names such as red/black . For example: default= <integer> - Replace <integer> with the default entry title number to be loaded if the menu interface times out. fallback= <integer> - Replace <integer> with the entry title number to try if the first attempt fails. hiddenmenu - Prevents the GRUB menu interface from being displayed, loading the default entry when the timeout period expires. The user can see the standard GRUB menu by pressing the Esc key. initrd </path/to/initrd> - Enables users to specify an initial RAM disk to use when booting. Replace </path/to/initrd> with the absolute path to the initial RAM disk. kernel </path/to/kernel> <option-1> <option-N> - Specifies the kernel file to load when booting the operating system. Replace </path/to/kernel> with an absolute path from the partition specified by the root directive. Multiple options can be passed to the kernel when it is loaded. password= <password> - Prevents a user who does not know the password from editing the entries for this menu option. Optionally, it is possible to specify an alternate menu configuration file after the password= <password> directive. In this case, GRUB restarts the second stage boot loader and uses the specified alternate configuration file to build the menu. If an alternate menu configuration file is left out of the command, a user who knows the password is allowed to edit the current configuration file. For more information about securing GRUB, refer to the chapter titled Workstation Security in the Security Guide . root ( <device-type> <device-number> , <partition> ) - Configures the root partition for GRUB, such as (hd0,0) , and mounts the partition. rootnoverify ( <device-type> <device-number> , <partition> ) - Configures the root partition for GRUB, just like the root command, but does not mount the partition. timeout= <integer> - Specifies the interval, in seconds, that GRUB waits before loading the entry designated in the default command. splashimage= <path-to-image> - Specifies the location of the splash screen image to be used when GRUB boots. title group-title - Specifies a title to be used with a particular group of commands used to load a kernel or operating system. To add human-readable comments to the menu configuration file, begin the line with the hash mark character ( # ).

Commands:
color red/black green/blue