mtpti5iD/redhat-docs_dataset huggingface dataset:
8.23. boost 8.23.1. RHBA-2014:1440 - boost bug fix and enhancement update Updated boost packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The boost packages contain a large number of free peer-reviewed portable C++ source libraries. These libraries are suitable for tasks such as portable file-systems and time/date abstraction, serialization, unit testing, thread creation and multi-process synchronization, parsing, graphing, regular expression manipulation, and many others. Bug Fixes BZ# 1037680 Due to the way the Python programming language was packaged for Red Hat Enterprise Linux, the boost packages could not be provided for secondary architectures. For example, boost-devel.i686 was not available on the x86-64 architecture. The Python packaging has been updated, and it is now possible to install secondary-architecture versions of the boost packages. BZ# 1021004 A coding error in the shared_ptr pointer previously caused a memory leak when serializing and unserializing shared pointers. The shared_ptr code has been corrected and the memory leak now no longer occurs. BZ# 969183 Due to an error in threading configuration of GNU Compiler Collection (GCC) version 4.7 or later, Boost failed to detect the support for multithreading versions of GCC. This patch fixes the error and Boost now detects multithreading support in the described circumstances correctly. BZ# 1108268 Prior to this update, a number of boost libraries were not compatible with GCC provided with Red Hat Developer Toolset. A fix has been implemented to address this problem and the affected libraries now properly work with Red Hat Developer Toolset GCC. BZ# 801534 The mpi.so library was previously missing from the boost libraries. Consequently, using the Message Passing Interface (MPI) in combination with Python scripts failed. With this update, mpi.so is included in the boost packages and using MPI with Python works as expected. In addition, this update adds the following Enhancement BZ# 1132455 The MPICH2 library has been replaced with a later version, MPICH 3.0. Note that Boost packaging has been updated accordingly and new packages are named boost-mpich* instead of boost-mpich2*. Users of Boost are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
8.191. sanlock 8.191.1. RHBA-2013:1632 - sanlock bug fix and enhancement update Updated sanlock packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The sanlock packages provide a shared storage lock manager. Hosts with shared access to a block device or a file can use sanlock to synchronize their activities. VDSM and libvirt use sanlock to synchronize access to virtual machine images. Note The sanlock packages have been upgraded to upstream version 2.8, which provides a number of bug fixes and enhancements over the version, including a new API provided for applications to request the release of a resource. (BZ# 960989 ) Bug Fix BZ# 961032 Previously, the wdmd daemon did not always select the functional device when some watchdog modules provided two devices. Consequently, wdmd did not work correctly in some instances. A patch has been applied to address this bug, and wdmd now verifies the state of both devices and selects the one that works properly. Enhancements BZ# 960993 With this update, a new API has been provided for applications to verify the status of hosts in a lockspace. BZ# 966088 With this update, a new API has been provided for applications to check the status of hosts that are holding a resource lease. Users of sanlock are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
10.2.4.2. The mod_ssl Module The configuration for mod_ssl has been moved from the httpd.conf file into the /etc/httpd/conf.d/ssl.conf file. For this file to be loaded, and for mod_ssl to work, the statement Include conf.d/*.conf must be in the httpd.conf file as described in Section 10.2.1.3, "Dynamic Shared Object (DSO) Support" . ServerName directives in SSL virtual hosts must explicitly specify the port number. For example, the following is a sample Apache HTTP Server 1.3 directive: To migrate this setting to Apache HTTP Server 2.0, use the following structure: It is also important to note that both the SSLLog and SSLLogLevel directives have been removed. The mod_ssl module now obeys the ErrorLog and LogLevel directives. Refer to Section 10.5.35, " ErrorLog " and Section 10.5.36, " LogLevel " for more information about these directives. For more on this topic, refer to the following documentation on the Apache Software Foundation's website: http://httpd.apache.org/docs-2.0/mod/mod_ssl.html http://httpd.apache.org/docs-2.0/vhosts/

Commands:
<VirtualHost _default_:443> # General setup for the virtual host ServerName ssl.example.name </VirtualHost>
<VirtualHost _default_:443> # General setup for the virtual host ServerName ssl.host.name :443 </VirtualHost>
Chapter 2. Installation This chapter guides you through the steps to install AMQ OpenWire JMS in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with AMQ OpenWire JMS, you must install Apache Maven . To use AMQ OpenWire JMS, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-client</artifactId> <version>5.11.0.redhat-630416</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, AMQ OpenWire JMS can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the AMQ Broker 7.9.0 Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-broker-7.9.0-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.4. Installing the examples Procedure Use your subscription to download the AMQ Broker 7.9.0 .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-broker-7.9.0.zip On Windows, right-click the .zip file and select Extract All . When you extract the contents of the .zip file, a directory named amq-broker-7.9.0 is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.apache.activemq</groupId> <artifactId>activemq-client</artifactId> <version>5.11.0.redhat-630416</version> </dependency>
unzip amq-broker-7.9.0-maven-repository.zip
unzip amq-broker-7.9.0.zip
B.7. cifs-utils B.7.1. RHBA-2011:0380 - cifs-utils bug fix update An updated cifs-utils package that fixes a bug is now available for Red Hat Enterprise Linux 6. The Server Message Block (SMB), also known as Common Internet File System (CIFS), is a standard file-sharing protocol widely deployed on Windows machines. The tools included in this package work in conjunction with support in the kernel to allow users to mount a SMB/CIFS share onto a client, and use it as if it were a standard Linux file system. Bug Fix BZ# 668366 Due to an error in the cifs.upcall utility, Generic Security Services Application Program Interface (GSSAPI) channel bindings in Kerberos authentication messages were not set properly. This would cause some servers to reject authentication requests. Consequent to this, an attempt to mount a CIFS share with the security mode set to "krb5" could fail with the following error: This update corrects the cifs.upcall utility to set the GSSAPI channel bindings properly, and such CIFS shares can now be mounted as expected. All users of cifs-utils are advised to upgrade to this updated package, which resolves this issue.

Commands:
mount error(5): Input/output error
1.3. Implications for Resource Management Because a task can belong to only a single cgroup in any one hierarchy, there is only one way that a task can be limited or affected by any single subsystem. This is logical: a feature, not a limitation. You can group several subsystems together so that they affect all tasks in a single hierarchy. Because cgroups in that hierarchy have different parameters set, those tasks will be affected differently. It may sometimes be necessary to refactor a hierarchy. An example would be removing a subsystem from a hierarchy that has several subsystems attached, and attaching it to a new, separate hierarchy. Conversely, if the need for splitting subsystems among separate hierarchies is reduced, you can remove a hierarchy and attach its subsystems to an existing one. The design allows for simple cgroup usage, such as setting a few parameters for specific tasks in a single hierarchy, such as one with just the cpu and memory subsystems attached. The design also allows for highly specific configuration: each task (process) on a system could be a member of each hierarchy, each of which has a single attached subsystem. Such a configuration would give the system administrator absolute control over all parameters for every single task.

Commands:
Chapter 3. Enabling Linux control group version 1 (cgroup v1) As of OpenShift Container Platform 4.14, OpenShift Container Platform uses Linux control group version 2 (cgroup v2) in your cluster. If you are using cgroup v1 on OpenShift Container Platform 4.13 or earlier, migrating to OpenShift Container Platform 4.16 will not automatically update your cgroup configuration to version 2. A fresh installation of OpenShift Container Platform 4.14 or later will use cgroup v2 by default. However, you can enable Linux control group version 1 (cgroup v1) upon installation. Enabling cgroup v1 in OpenShift Container Platform disables all cgroup v2 controllers and hierarchies in your cluster. Important cgroup v1 is a deprecated feature. Deprecated functionality is still included in OpenShift Container Platform and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments. For the most recent list of major functionality that has been deprecated or removed within OpenShift Container Platform, refer to the Deprecated and removed features section of the OpenShift Container Platform release notes. cgroup v2 is the current version of the Linux cgroup API. cgroup v2 offers several improvements over cgroup v1, including a unified hierarchy, safer sub-tree delegation, new features such as Pressure Stall Information , and enhanced resource management and isolation. However, cgroup v2 has different CPU, memory, and I/O management characteristics than cgroup v1. Therefore, some workloads might experience slight differences in memory or CPU usage on clusters that run cgroup v2. You can switch between cgroup v1 and cgroup v2, as needed, by editing the node.config object. For more information, see "Configuring the Linux cgroup on your nodes" in the "Additional resources" of this section. 3.1. Enabling Linux cgroup v1 during installation You can enable Linux control group version 1 (cgroup v1) when you install a cluster by creating installation manifests. Important cgroup v1 is a deprecated feature. Deprecated functionality is still included in OpenShift Container Platform and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments. For the most recent list of major functionality that has been deprecated or removed within OpenShift Container Platform, refer to the Deprecated and removed features section of the OpenShift Container Platform release notes. Procedure Create or edit the node.config object to specify the v1 cgroup: apiVersion: config.openshift.io/v1 kind: Node metadata: name: cluster spec: cgroupMode: "v2" Proceed with the installation as usual. Additional resources OpenShift Container Platform installation overview Configuring the Linux cgroup on your nodes

Commands:
apiVersion: config.openshift.io/v1 kind: Node metadata: name: cluster spec: cgroupMode: "v2"
8.212. scsi-target-utils 8.212.1. RHBA-2014:1599 - scsi-target-utils bug fix update Updated scsi-target-utils packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The scsi-target-utils packages contain a daemon and utilities to setup Small Computer System Interface (SCSI) targets. Currently, software Internet SCSI (iSCSI) and iSCSI Extensions for RDMA (iSER) targets are supported. Bug Fixes BZ# 848585 Previously, the tgtadm SCSI target administration utility did not correctly handle backing-store errors. As a consequence, calling tgtadm with an invalid backing-store parameter in some cases caused the tgtd service to become unresponsive. With this update, the bug in tgtadm has been fixed, and tgtd now recovers from an invalid request as intended. BZ# 854123 Prior to this update, tgtadm failed to handle setting a device to pass-through mode. As a consequence, calling tgtadm with the device-type option set to "passthrough" caused tgtd on the server side to terminate unexpectedly with a segmentation fault. A patch has been applied to fix this bug, and tgtadm no longer crashes in the described scenario. BZ# 865960 Prior to this update, running the "tgtadm --mode target --op show" command did not return the complete number of targets if many targets were present on the system. Consequently, tgtadm could show incorrect and also inconsistent results, because the displayed number of targets varied over repeated attempts. A patch has been applied to fix this bug. Running "tgtadm --mode target --op show" now shows all the targets correctly even on systems with a large amount of targets. BZ# 1094084 Previously, scsi-target-utils did not support the "WRITE and VERIFY (10)" SCSI command which is used by the AIX operating system. As a consequence, AIX failed to execute the mkvg command when the user tried to add iSCSI targets to the system. With this update, the support for "WRITE and VERIFY (10)" has been added, and scsi-target-utils now provide iSCSI targets to AIX as expected. BZ# 1123438 Previously, tgtd could experience a buffer overflow due to incorrect usage of the snprintf() function in the source code. As a consequence, tgtd terminated unexpectedly when trying to respond to a tgtadm query about a large number of connections. The source code has been updated to avoid the buffer overflow, and using tgtadm to display a large number of connections no longer causes tgtd to crash. Users of scsi-target-utils are advised to upgrade to these updated packages, which fix these bugs. All running scsi-target-utils services must be restarted for the update to take effect.

Commands:
25.4.2. Compatibility with sysklogd The compatibility mode specified via the -c option exists in rsyslog version 5 but not in version 7. Also, the sysklogd-style command-line options are deprecated and configuring rsyslog through these command-line options should be avoided. However, you can use several templates and directives to configure rsyslogd to emulate sysklogd-like behavior. For more information on various rsyslogd options, see the rsyslogd(8) manual page.

Commands:
4.3. sVirt Configuration SELinux Booleans are variables that can be toggled on or off, quickly enabling or disabling features or other special conditions. Booleans can be toggled by running either setsebool boolean_name {on|off} for a temporary change, or setsebool -P boolean_name {on|off} to make the change persistent across reboots. The following table shows the SELinux Boolean values that affect KVM when launched by libvirt. The current state of these booleans (on or off) can be found by running the command getsebool -a|grep virt . Table 4.1. KVM SELinux Booleans SELinux Boolean Description staff_use_svirt Enables staff users to create and transition to sVirt domains. unprivuser_use_svirt Enables unprivileged users to create and transition to sVirt domains. virt_sandbox_use_audit Enables sandbox containers to send audit messages. virt_sandbox_use_netlink Enables sandbox containers to use netlink system calls. virt_sandbox_use_sys_admin Enables sandbox containers to use sys_admin system calls, such as mount. virt_transition_userdomain Enables virtual processes to run as user domains. virt_use_comm Enables virt to use serial/parallel communication ports. virt_use_execmem Enables confined virtual guests to use executable memory and executable stack. virt_use_fusefs Enables virt to read FUSE mounted files. virt_use_nfs Enables virt to manage NFS mounted files. virt_use_rawip Enables virt to interact with rawip sockets. virt_use_samba Enables virt to manage CIFS mounted files. virt_use_sanlock Enables confined virtual guests to interact with the sanlock. virt_use_usb Enables virt to use USB devices. virt_use_xserver Enables virtual machine to interact with the X Window System. Note For more information on SELinux Booleans, see the Red Hat Enterprise Linux SELinux Users and Administrators Guide .

Commands:
Preface To begin, install Ansible Automation Platform and select a target system where you can deploy an initial playbook (provided by automation controller). This first playbook executes simple Ansible tasks, while teaching you how to use the controller and properly set it up. You can use any sort of system manageable by Ansible, as described in the Managed nodes section of the Ansible documentation. For further instructions, see the Red Hat Ansible Automation Platform Installation Guide . Note Ansible Automation Platform is offered on a subscription basis. These subscriptions vary in price and support-levels. For more information about subscriptions and features, see Subscription Types .

Commands:
Chapter 28. Profiling memory allocation with numastat With the numastat tool, you can display statistics over memory allocations in a system. The numastat tool displays data for each NUMA node separately. You can use this information to investigate memory performance of your system or the effectiveness of different memory policies on your system. 28.1. Default numastat statistics By default, the numastat tool displays statistics over these categories of data for each NUMA node: numa_hit The number of pages that were successfully allocated to this node. numa_miss The number of pages that were allocated on this node because of low memory on the intended node. Each numa_miss event has a corresponding numa_foreign event on another node. numa_foreign The number of pages initially intended for this node that were allocated to another node instead. Each numa_foreign event has a corresponding numa_miss event on another node. interleave_hit The number of interleave policy pages successfully allocated to this node. local_node The number of pages successfully allocated on this node by a process on this node. other_node The number of pages allocated on this node by a process on another node. Note High numa_hit values and low numa_miss values (relative to each other) indicate optimal performance. 28.2. Viewing memory allocation with numastat You can view the memory allocation of the system by using the numastat tool. Prerequisites Install the numactl package: Procedure View the memory allocation of your system: Additional resources numastat(8) man page on your system

Commands:
dnf install numactl
numastat node0 node1 numa_hit 76557759 92126519 numa_miss 30772308 30827638 numa_foreign 30827638 30772308 interleave_hit 106507 103832 local_node 76502227 92086995 other_node 30827840 30867162
Chapter 92. MavenArtifact schema reference Used in: Plugin The type property is a discriminator that distinguishes use of the MavenArtifact type from JarArtifact , TgzArtifact , ZipArtifact , OtherArtifact . It must have the value maven for the type MavenArtifact . Property Description repository Maven repository to download the artifact from. Applicable to the maven artifact type only. string group Maven group id. Applicable to the maven artifact type only. string artifact Maven artifact id. Applicable to the maven artifact type only. string version Maven version number. Applicable to the maven artifact type only. string insecure By default, connections using TLS are verified to check they are secure. The server certificate used must be valid, trusted, and contain the server name. By setting this option to true , all TLS verification is disabled and the artifacts will be downloaded, even when the server is considered insecure. boolean type Must be maven . string

Commands:
22.3. Connecting to a Samba Share You can use Nautilus to view available Samba shares on your network. Select Main Menu Button (on the Panel) => Network Servers to view a list of Samba workgroups on your network. You can also type smb: in the Location: bar of Nautilus to view the workgroups. As shown in Figure 22.6, "SMB Workgroups in Nautilus" , an icon appears for each available SMB workgroup on the network. Figure 22.6. SMB Workgroups in Nautilus Double-click one of the workgroup icons to view a list of computers within the workgroup. Figure 22.7. SMB Machines in Nautilus As you can see from Figure 22.7, "SMB Machines in Nautilus" , there is an icon for each machine within the workgroup. Double-click on an icon to view the Samba shares on the machine. If a username and password combination is required, you are prompted for them. Alternately, you can also specify the Samba server and sharename in the Location: bar for Nautilus using the following syntax (replace <servername> and <sharename> with the appropriate values): 22.3.1. Command Line To query the network for Samba servers, use the findsmb command. For each server found, it displays its IP address, NetBIOS name, workgroup name, operating system, and SMB server version. To connect to a Samba share from a shell prompt, type the following command: Replace <hostname> with the hostname or IP address of the Samba server you want to connect to, <sharename> with the name of the shared directory you want to browse, and <username> with the Samba username for the system. Enter the correct password or press Enter if no password is required for the user. If you see the smb:\> prompt, you have successfully logged in. Once you are logged in, type help for a list of commands. If you wish to browse the contents of your home directory, replace sharename with your username. If the -U switch is not used, the username of the current user is passed to the Samba server. To exit smbclient , type exit at the smb:\> prompt.

Commands:
smb:// <servername> / <sharename> /
smbclient // <hostname> / <sharename> -U <username>