mtpti5iD/redhat-docs_dataset huggingface dataset:
17.2. Establishing an Ethernet Connection To establish an Ethernet connection, you need a network interface card (NIC), a network cable (usually a CAT5 cable), and a network to connect to. Different networks are configured to use different network speeds; make sure your NIC is compatible with the network to which you want to connect. To add an Ethernet connection, follow these steps: Click the Devices tab. Click the New button on the toolbar. Select Ethernet connection from the Device Type list, and click Forward . If you have already added the network interface card to the hardware list, select it from the Ethernet card list. Otherwise, select Other Ethernet Card to add the hardware device. Note The installation program detects supported Ethernet devices and prompts you to configure them. If you configured any Ethernet devices during the installation, they are displayed in the hardware list on the Hardware tab. If you selected Other Ethernet Card , the Select Ethernet Adapter window appears. Select the manufacturer and model of the Ethernet card. Select the device name. If this is the system's first Ethernet card, select eth0 as the device name; if this is the second Ethernet card, select eth1 (and so on). The Network Administration Tool also allows you to configure the resources for the NIC. Click Forward to continue. In the Configure Network Settings window shown in Figure 17.2, "Ethernet Settings" , choose between DHCP and a static IP address. If the device receives a different IP address each time the network is started, do not specify a hostname. Click Forward to continue. Click Apply on the Create Ethernet Device page. Figure 17.2. Ethernet Settings After configuring the Ethernet device, it appears in the device list as shown in Figure 17.3, "Ethernet Device" . Figure 17.3. Ethernet Device After adding the Ethernet device, you can edit its configuration by selecting the device from the device list and clicking Edit . For example, when the device is added, it is configured to start at boot time by default. To change this setting, select to edit the device, modify the Activate device when computer starts value, and save the changes. If you associate more than one device with an Ethernet card, the subsequent devices are device aliases . A device alias allows you to setup multiple virtual devices for one physical device, thus giving the one physical device more than one IP address. For example, you can configure an eth1 device and an eth1:1 device. For details, refer to Section 17.11, "Device Aliases" .

Commands:
2.4. SELinux States and Modes SELinux can be either in the enabled or disabled state. When disabled, only DAC rules are used. When enabled, SELinux can run in one of the following modes: Enforcing: SELinux policy is enforced. SELinux denies access based on SELinux policy rules. Permissive: SELinux policy is not enforced. SELinux does not deny access, but denials are logged for actions that would have been denied if running in enforcing mode. Use the setenforce utility to change between enforcing and permissive mode. Changes made with setenforce do not persist across reboots. To change to enforcing mode, as the Linux root user, run the setenforce 1 command. To change to permissive mode, run the setenforce 0 command. Use the getenforce utility to view the current SELinux mode: Persistent states and modes changes are covered in Section 5.4, "Permanent Changes in SELinux States and Modes" .

Commands:
~]# getenforce Enforcing
~]# setenforce 0 ~]# getenforce Permissive
~]# setenforce 1 ~]# getenforce Enforcing
Part VII. Patching and upgrading Red Hat Decision Manager Starting with release 7.13, the distribution files for Red Hat Decision Manager are replaced with Red Hat Process Automation Manager files. You can apply updates to Red Hat Decision Manager release 7.12 and earlier or Red Hat Process Automation Manager 7.13 as they become available in the Red Hat Customer Portal to keep your distribution current with the latest enhancements and fixes. Red Hat provides update tools and product notifications for new product releases so you can more readily apply helpful updates to your installation environment. Prerequisites You have a Red Hat Customer Portal account. Red Hat Decision Manager or Red Hat Process Automation Manager is installed. For installation options, see Planning a Red Hat Decision Manager installation . Note If you are using Red Hat Decision Manager 7.10 and you want to upgrade to Red Hat Process Automation Manager 7.13, see Patching and upgrading Red Hat Decision Manager 7.10 .

Commands:
Chapter 2. Subscription models for JBoss EAP on Microsoft Azure You can choose between two subscription models for deploying JBoss EAP on Azure: bring your own subscription (BYOS) and pay-as-you-go (PAYG). The following are the differences between the two offerings: BYOS If you already have an existing Red Hat subscription, you can use it for deploying JBoss EAP on Azure with the BYOS model. For more information, see About Red Hat Cloud Access . PAYG If you do not have an existing Red Hat subscription, you can choose to pay based on the number of computing resources you used by using the PAYG model.

Commands:
Chapter 2. Installing Connectivity Link in the OpenShift web console You can use the OpenShift Container Platform web console to install the Red Hat Connectivity Link Operator. Note You must perform these steps on each OpenShift cluster that you want to use Connectivity Link on. Prerequisites See Chapter 1, Connectivity Link prerequisites and permissions . You have access to the OpenShift Container Platform web console. Procedure In the OpenShift Container Platform web console, log in with cluster-admin privileges. In the left navigation menu, click Operators > OperatorHub . In the Filter by keyword text box, enter Connectivity to find the Red Hat Connectivity Link Operator. Read the information about the Operator, and click Install to display the Operator subscription page. Select your subscription settings as follows: Update Channel : stable Version : 1.0.1 Installation mode : All namespaces on the cluster (default) . Installed namespace : Select the namespace where you want to install the Operator, for example, kuadrant-system . If the namespace does not already exist, click this field and select Create Project to create the namespace. Approval Strategy : Select Automatic or Manual . Click Install , and wait a few moments until the Operator is installed and ready for use. Click Operators > Installed Operators > Red Hat Connectivity Link . Click the Kuadrant tab, and click Create Kuadrant to create a deployment. In the Configure via field, click YAML view to edit the definition, for example, the deployment name. Click Create and wait for the deployment to be displayed in the list. Verification After you have installed the Operator, click Operators > Installed Operators to verify that the Red Hat Connectivity Link Operator and the following component Operators are installed in your namespace: Red Hat - Authorino Operator : Enables authentication and authorization for Gateways and applications in a Gateway API network. Red Hat - DNS Operator : Configures how north-south traffic from outside the network is balanced and reaches Gateways. Red Hat - Limitador Operator : Enables rate limiting for Gateways and applications in a Gateway API network. Additional resources OpenShift Operators documentation .

Commands:
Chapter 1. Introduction Red Hat Gluster Storage is a software only, scale-out storage solution that provides flexible and agile unstructured data storage for the enterprise. Red Hat Gluster Storage provides new opportunities to unify data storage and infrastructure, increase performance, and improve availability and manageability to meet a broader set of the storage challenges and needs of an organization. GlusterFS, a key building block of Red Hat Gluster Storage, is based on a stackable user space design and can deliver exceptional performance for diverse workloads. GlusterFS aggregates various storage servers over different network interfaces and connects them to form a single large parallel network file system. The POSIX compatible GlusterFS servers use XFS file system format to store data on disks. These servers can be accessed using industry standard access protocols including Network File System (NFS) and Server Message Block SMB (also known as CIFS). Red Hat Gluster Storage Servers for On-premises can be used in the deployment of private clouds or data centers. Red Hat Gluster Storage can be installed on commodity servers and storage hardware resulting in a powerful, massively scalable, and highly available NAS environment. Additionally, Red Hat Gluster Storage can be deployed in the public cloud using Red Hat Gluster Storage Server for Public Cloud with Amazon Web Services (AWS), Microsoft Azure, or Google Cloud. It delivers all the features and functionality possible in a private cloud or data center to the public cloud by providing massively scalable and high available NAS in the cloud. Red Hat Gluster Storage Server for On-premises Red Hat Gluster Storage Server for On-premises enables enterprises to treat physical storage as a virtualized, scalable, and centrally managed pool of storage by using commodity servers and storage hardware. Red Hat Gluster Storage Server for Public Cloud Red Hat Gluster Storage Server for Public Cloud packages GlusterFS for deploying scalable NAS in AWS, Microsoft Azure, and Google Cloud. This powerful storage server provides a highly available, scalable, virtualized, and centrally managed pool of storage for users of these public cloud providers.

Commands:
7.2.2. Saving and Restoring iptables Rules Firewall rules are only valid for the time the computer is on; so, if the system is rebooted, the rules are automatically flushed and reset. To save the rules so that they are loaded later, use the following command: The rules are stored in the file /etc/sysconfig/iptables and are applied whenever the service is started or restarted, including when the machine is rebooted.

Commands:
/sbin/service iptables save
7.153. netcf 7.153.1. RHBA-2013:0494 - netcf bug fix update Updated netcf packages that fix one bug are now available for Red Hat Enterprise Linux 6. The netcf packages contain a library for modifying the network configuration of a system. Network configuration is expressed in a platform-independent XML format, which netcf translates into changes to the system's "native" network configuration files. Bug Fix BZ# 886862 Previously, the netcf utility had been calling the nl_cache_mngt_provide() function in the libnl library, which was not thread-safe. Consequently, the libvirtd daemon could terminate unexpectedly. As nl_cache_mngt_provide() was not necessary for proper operation, it is no longer called by netcf, thus preventing this bug. Users of netcf are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.163. libvirt-cim 5.163.1. RHBA-2012:0757 - libvirt-cim bug fix and enhancement update An updated libvirt-cim package that fixes various bugs and adds multiple enhancements is now available for Red Hat Enterprise Linux 6. The libvirt-cim package contains a Common Information Model (CIM) provider based on Common Manageability Programming Interface (CMPI). It supports most libvirt virtualization features and allows management of multiple libvirt-based platforms. The libvirt-cim package has been upgraded to upstream version 0.6.1, which provides a number of bug fixes and enhancements over the version. (BZ# 739154 ) Bug Fix BZ# 799037 Previously, the libvirt-cim package required as its dependency the tog-pegasus package, which contains the OpenPegasus Web-Based Enterprise Management (WBEM) services. This is, however, incorrect as libvirt-cim should not require specifically tog-pegasus but any CIM server. With this update, libvirt-cim has been changed to require cim-server instead. The spec files of libvirt-cim and sblim-sfcb have been modified appropriately and libvirt-cim now uses either of the packages as its dependency. Enhancements BZ# 633338 Extension for Quality-of-Service (QoS) networking has been added. BZ# 739153 Support for domain events has been added. BZ# 739156 Extensions for networking of Central Processing Unit (CPU) shares have been added. All libvirt-cim users are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
A.3. Fsync Fsync is known as an I/O expensive operation, but this is is not completely true. Firefox used to call the sqlite library each time the user clicked on a link to go to a new page. Sqlite called fsync and because of the file system settings (mainly ext3 with data-ordered mode), there was a long latency when nothing happened. This could take a long time (up to 30 seconds) if another process was copying a large file at the same time. However, in other cases, where fsync wasn't used at all, problems emerged with the switch to the ext4 file system. Ext3 was set to data-ordered mode, which flushed memory every few seconds and saved it to a disk. But with ext4 and laptop_mode, the interval between saves was longer and data might get lost when the system was unexpectedly switched off. Now ext4 is patched, but we must still consider the design of our applications carefully, and use fsync as appropriate. The following simple example of reading and writing into a configuration file shows how a backup of a file can be made or how data can be lost: /* open and read configuration file e.g. ./myconfig */ fd = open("./myconfig", O_RDONLY); read(fd, myconfig_buf, sizeof(myconfig_buf)); close(fd); ... fd = open("./myconfig", O_WRONLY | O_TRUNC | O_CREAT, S_IRUSR | S_IWUSR); write(fd, myconfig_buf, sizeof(myconfig_buf)); close(fd); A better approach would be: /* open and read configuration file e.g. ./myconfig */ fd = open("./myconfig", O_RDONLY); read(fd, myconfig_buf, sizeof(myconfig_buf)); close(fd); ... fd = open("./myconfig.suffix", O_WRONLY | O_TRUNC | O_CREAT, S_IRUSR | S_IWUSR write(fd, myconfig_buf, sizeof(myconfig_buf)); fsync(fd); /* paranoia - optional */ ... close(fd); rename("./myconfig", "./myconfig~"); /* paranoia - optional */ rename("./myconfig.suffix", "./myconfig");

Commands:
/* open and read configuration file e.g. ./myconfig */ fd = open("./myconfig", O_RDONLY); read(fd, myconfig_buf, sizeof(myconfig_buf)); close(fd); fd = open("./myconfig", O_WRONLY | O_TRUNC | O_CREAT, S_IRUSR | S_IWUSR); write(fd, myconfig_buf, sizeof(myconfig_buf)); close(fd);
/* open and read configuration file e.g. ./myconfig */ fd = open("./myconfig", O_RDONLY); read(fd, myconfig_buf, sizeof(myconfig_buf)); close(fd); fd = open("./myconfig.suffix", O_WRONLY | O_TRUNC | O_CREAT, S_IRUSR | S_IWUSR write(fd, myconfig_buf, sizeof(myconfig_buf)); fsync(fd); /* paranoia - optional */ close(fd); rename("./myconfig", "./myconfig~"); /* paranoia - optional */ rename("./myconfig.suffix", "./myconfig");
7.2. Overcommitting Memory Guest virtual machines running on a KVM hypervisor do not have dedicated blocks of physical RAM assigned to them. Instead, each guest virtual machine functions as a Linux process where the host physical machine's Linux kernel allocates memory only when requested. In addition the host's memory manager can move the guest virtual machine's memory between its own physical memory and swap space. Overcommitting requires allotting sufficient swap space on the host physical machine to accommodate all guest virtual machines as well as enough memory for the host physical machine's processes. As a basic rule, the host physical machine's operating system requires a maximum of 4 GB of memory along with a minimum of 4 GB of swap space. For advanced instructions on determining an appropriate size for the swap partition, see the Red Hat Knowledgebase . Important Overcommitting is not an ideal solution for general memory issues. The recommended methods to deal with memory shortage are to allocate less memory per guest, add more physical memory to the host, or utilize swap space. A virtual machine will run slower if it is swapped frequently. In addition, overcommitting can cause the system to run out of memory (OOM), which may lead to the Linux kernel shutting down important system processes. If you decide to overcommit memory, ensure sufficient testing is performed. Contact Red Hat support for assistance with overcommitting. Overcommitting does not work with all virtual machines, but has been found to work in a desktop virtualization setup with minimal intensive usage or running several identical guests with KSM. For more information on KSM and overcommitting, see the Red Hat Enterprise Linux 7 Virtualization Tuning and Optimization Guide . Important Memory overcommit is not supported with device assignment. This is because when device assignment is in use, all virtual machine memory must be statically pre-allocated to enable direct memory access (DMA) with the assigned device.

Commands:
Appendix B. Mod_jk connector module The Apache Tomcat Connector, mod_jk , is a web server plug-in that the Apache Tomcat project provides. The Apache HTTP Server can use the mod_jk module to load-balance HTTP client requests to back-end servlet containers, while maintaining sticky sessions and communicating over the Apache JServ Protocol (AJP). The mod_jk module is included in the Apache HTTP Server part of a JBoss Core Services installation. The mod_jk module requires that you create both a mod_jk.conf file and a workers.properties file on the Apache HTTP Server host. The mod_jk.conf file specifies settings to load and configure the mod_jk.so module. The workers.properties file specifies back-end worker node details. You must also configure some settings on the [JWSShortName] host to enable mod_jk support. Additional resources Load balancing with the Apache Tomcat Connector ( mod_jk ) Workers.properties file for mod_jk

Commands:
4.242. pyparted 4.242.1. RHBA-2011:1641 - pyparted bug fix update An updated pyparted package that fixes a bug is now available for Red Hat Enterprise Linux 6. The pyparted package contains Python bindings for the libparted library. It is primarily used by the Red Hat Enterprise Linux installation software. Bug Fix BZ# 725558 Due to a missing flag in the GPT (Guid Partition Table) disklabel, the anaconda installer terminated with a traceback during the installation of Red Hat Enterprise Linux 6.2. With this update, support for the PARTITION_LEGACY_BOOT flag has been added to the pyparted package, thus fixing this bug. Users of pyparted are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 8. File Systems XFS runtime statistics are available per file system in the /sys/fs/ directory The existing XFS global statistics directory has been moved from the /proc/fs/xfs/ directory to the /sys/fs/xfs/ directory while maintaining compatibility with earlier versions with a symbolic link in /proc/fs/xfs/stat . New subdirectories will be created and maintained for statistics per file system in /sys/fs/xfs/ , for example /sys/fs/xfs/sdb7/stats and /sys/fs/xfs/sdb8/stats . Previously, XFS runtime statistics were available only per server. Now, XFS runtime statistics are available per device. (BZ#1205640) XFS supported file-system size has been increased Previously, the supported file-system size for XFS was 100 TB. With this update, the supported file-system size for XFS has been increased to 300 TB. (BZ#1273090) The use_hostname_for_mounts autofs option is now available A new autofs option to override the use of an IP address when mounting to a host name with multiple associated addresses has been implemented. If strict Round Robin DNS is needed, the use_hostname_for_mounts option enables bypassing the usual availability and proximity check, and the host name is used in mount requests regardless of whether the requests have multiple IP addresses. (BZ#1248798)

Commands:
4.2. Tuning Directory Server Resource Settings You can configure several parameters to manage and improve the amount of resources Directory Server uses. 4.2.1. Updating Directory Server Resource Settings Using the Command Line To update the server resource settings using the command line: Update the performance settings: You can set the following parameters: nsslapd-threadnumber : Sets the number of worker threads. nsslapd-maxdescriptors : Sets the maximum number of file descriptors. nsslapd-timelimit : Sets the search time limit. nsslapd-sizelimit : Sets the search size limit. nsslapd-pagedsizelimit : Sets the paged search size limit. nsslapd-idletimeout : Sets the idle connection timeout. nsslapd-ioblocktimeout : Sets the input/output (I/O) block timeout. nsslapd-ndn-cache-enabled : Enables or disables the normalized DN cache. nsslapd-ndn-cache-max-size : Sets the normalized DN cache size, if nsslapd-ndn-cache-enabled is enabled. nsslapd-outbound-ldap-io-timeout : Sets the outbound I/O timeout. nsslapd-maxbersize : Sets the maximum Basic Encoding Rules (BER) size. nsslapd-maxsasliosize : Sets the maximum Simple Authentication and Security Layer (SASL) I/O size. nsslapd-listen-backlog-size : Sets the maximum number of sockets available to receive incoming connections. nsslapd-max-filter-nest-level : Sets the maximum nested filter level. nsslapd-ignore-virtual-attrs : Enables or disables virtual attribute lookups. nsslapd-connection-nocanon : Enables or disables revers DNS lookups. nsslapd-enable-turbo-mode : Enables or disables the turbo mode feature. For further details about these parameters, see their descriptions in the Red Hat Directory Server Configuration, Command, and File Reference . Restart the Directory Server instance: 4.2.2. Updating Directory Server Resource Settings Using the Web Console To update the server resource settings using the Web Console: Open the Directory Server user interface in the web console. For details, see Logging Into Directory Server Using the Web Console section in the Red Hat Directory Server Administration Guide . Select the instance. Open the Server Settings menu, and select Tuning & Limits . Update the settings. Optionally, click Show Advanced Settings to display all settings. To display a tooltip and the corresponding attribute name in the cn=config entry for a parameter, hover the mouse cursor over the setting. For further details, see the parameter description in the Red Hat Directory Server Configuration, Command, and File Reference. . Click Save Configuration . Click the Actions button, and select Restart Instance .

Commands:
dsconf -D "cn=Directory Manager" ldap://server.example.com config replace parameter_name = setting
dsctl instance_name restart