mtpti5iD/redhat-docs_dataset huggingface dataset:
5.7. Displaying Configured Resources To display a list of all configured resources, use the following command. For example, if your system is configured with a resource named VirtualIP and a resource named WebSite , the pcs resource show command yields the following output. To display a list of all configured resources and the parameters configured for those resources, use the --full option of the the pcs resource show command, as in the following example. To display the configured parameters for a resource, use the following command. For example, the following command displays the currently configured parameters for resource VirtualIP .

Commands:
pcs resource show
pcs resource show VirtualIP (ocf::heartbeat:IPaddr2): Started WebSite (ocf::heartbeat:apache): Started
pcs resource show --full Resource: VirtualIP (type=IPaddr2 class=ocf provider=heartbeat) Attributes: ip=192.168.0.120 cidr_netmask=24 Operations: monitor interval=30s Resource: WebSite (type=apache class=ocf provider=heartbeat) Attributes: statusurl=http://localhost/server-status configfile=/etc/httpd/conf/httpd.conf Operations: monitor interval=1min
pcs resource show resource_id
pcs resource show VirtualIP Resource: VirtualIP (type=IPaddr2 class=ocf provider=heartbeat) Attributes: ip=192.168.0.120 cidr_netmask=24 Operations: monitor interval=30s
Chapter 3. Getting started This chapter guides you through the steps to set up your environment and run a simple messaging program. 3.1. Prerequisites You must complete the installation procedure for your environment. You must have an AMQP 1.0 message broker listening for connections on interface localhost and port 5672 . It must have anonymous access enabled. For more information, see Starting the broker . You must have a queue named hello-world-example . For more information, see Creating a queue . Alternatively, you can specify above information using following environment variables: HOST , PORT , ADDRESS The examples are available from the source or upstream Download the amq-qpid-proton-dotnet-1.0.0-M9-src .zip file. When you extract the contents of the .zip file, a directory named amq-dotnet-1.0.0-M9-src is created. This is the top-level directory of the installation and is referred to as <src-install-dir> throughout this document. 3.2. Running HelloWorld on Red Hat Enterprise Linux The Hello World example creates a connection to the broker, sends a message containing a greeting to the hello-world-example queue, and receives it back. On success, it prints the received message to the console. Change to the <source-dir> /examples/Example.HelloWorld/ and use dotnet run to build and execute the program. USD cd <source-dir> /examples/Example.HelloWorld/ USD dotnet run Received message with body: Hello World 3.3. Running Hello World on Microsoft Windows The Hello World example creates a connection to the broker, sends a message containing a greeting to the hello-world-example queue, and receives it back. On success, it prints the received message to the console. Procedure Navigate to <source-dir> and open the Proton.sln solution file in Visual Studio. Select Build Solution from the Build menu to compile the solution. Open a command prompt window and execute the following commands to send and receive a message: > cd <source-dir> \bin\Debug > Example.HelloWorld Received message with body: Hello World

Commands:
cd <source-dir> /examples/Example.HelloWorld/ dotnet run Received message with body: Hello World
> cd <source-dir> \bin\Debug > Example.HelloWorld Received message with body: Hello World
7.22. chkconfig 7.22.1. RHBA-2015:0671 - chkconfig bug fix update Updated chkconfig packages that fix one bug are now available for Red Hat Enterprise Linux 6. The basic system utility chkconfig updates and queries runlevel information for system services. Bug Fix BZ# 965103 Previously, when the chkconfig utility modified a file in the /etc/xinetd.d/ directory, it set the file permissions to "644" and the SELinux context to "root:object_r:etc_t". Such permissions, however, do not adhere to the Defense Information Systems Agency's (DISA) Security Technical Implementation Guide (STIG), which requires files in /etc/xinetd.d/ to be unreadable by other users. With this update, chkconfig ensures that the xinetd files it modifies have the "600" permissions and the correct SELinux context is preserved. Users of chkconfig are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Overview AMQ JMS Pool is a library that provides caching of JMS connections, sessions, and message producers. It enables reuse of connection resources beyond the standard lifecycle defined by the JMS API. AMQ JMS Pool operates as a standard JMS ConnectionFactory instance that wraps the ConnectionFactory of your chosen JMS provider and manages the lifetime of Connection objects from that provider based on the configuration of the JMS pool. It can be configured to share one or more connections among callers to the pool createConnection() methods. AMQ JMS Pool is part of AMQ Clients, a suite of messaging libraries supporting multiple languages and platforms. For an overview of the clients, see AMQ Clients Overview . For information about this release, see AMQ Clients 2.8 Release Notes . AMQ JMS Pool is based on the Pooled JMS messaging library. 1.1. Key features JMS 1.1 and 2.0 compatible Automatic reconnect Configurable connection and session pool sizes 1.2. Supported standards and protocols AMQ JMS Pool supports version 2.0 of the Java Message Service API. 1.3. Supported configurations AMQ JMS Pool supports the OS and language versions listed below. For more information, see Red Hat AMQ 7 Supported Configurations . Red Hat Enterprise Linux 7 and 8 with the following JDKs: OpenJDK 8 and 11 Oracle JDK 8 IBM JDK 8 Red Hat Enterprise Linux 6 with the following JDKs: OpenJDK 8 Oracle JDK 8 IBM AIX 7.1 with IBM JDK 8 Microsoft Windows 10 Pro with Oracle JDK 8 Microsoft Windows Server 2012 R2 and 2016 with Oracle JDK 8 Oracle Solaris 10 and 11 with Oracle JDK 8 1.4. Document conventions The sudo command In this document, sudo is used for any command that requires root privileges. Exercise caution when using sudo because any changes can affect the entire system. For more information about sudo , see Using the sudo command . File paths In this document, all file paths are valid for Linux, UNIX, and similar operating systems (for example, /home/andrea ). On Microsoft Windows, you must use the equivalent Windows paths (for example, C:\Users\andrea ). Variable text This document contains code blocks with variables that you must replace with values specific to your environment. Variable text is enclosed in arrow braces and styled as italic monospace. For example, in the following command, replace <project-dir> with the value for your environment: USD cd <project-dir>

Commands:
cd <project-dir>
Chapter 1. Overview of alt-java Red Hat packages contain a mitigation for the SSB vulnerability in the form of a patch for the java binary. This patch disables an optimization present in x86-64 (Intel and AMD) processors. Disabling that optimization reduces the risk of kernel side-channel attacks, but also reduces CPU performance. Since the patch reduces performance, it has been removed from the java launcher. A new binary alt-java is now available. From the January 2021 Critical Patch Update release (1.8.0 282.b08, 11.0.10.9) onwards, the alt-java binary is included in Red Hat build of OpenJDK 8 and Red Hat build of OpenJDK 11 GA RPM packages. Additional resources For more information about the performance impact of SSB mitigation, see Kernel Side-Channel Attack using Speculative Store Bypass - CVE-2018-3639 on the Red Hat Customer Portal For more information about the java binary patch, see RH1566890 in the Red Hat Bugzilla documentation.

Commands:
22.10. Understanding the ntpd Sysconfig File The file will be read by the ntpd init script on service start. The default contents is as follows: The -g option enables ntpd to ignore the offset limit of 1000s and attempt to synchronize the time even if the offset is larger than 1000s, but only on system start. Without that option ntpd will exit if the time offset is greater than 1000s. It will also exit after system start if the service is restarted and the offset is greater than 1000s even with the -g option. The -p option sets the path to the pid file and -u sets the user and group to which the daemon should drop the root privileges.

Commands:
Drop root to id 'ntp:ntp' by default. OPTIONS="-u ntp:ntp -p /var/run/ntpd.pid -g"
1.3.3.2. Vulnerable Client Applications Although an administrator may have a fully secure and patched server, that does not mean remote users are secure when accessing it. For instance, if the server offers Telnet or FTP services over a public network, an attacker can capture the plain text user names and passwords as they pass over the network, and then use the account information to access the remote user's workstation. Even when using secure protocols, such as SSH, a remote user may be vulnerable to certain attacks if they do not keep their client applications updated. For instance, v.1 SSH clients are vulnerable to an X-forwarding attack from malicious SSH servers. Once connected to the server, the attacker can quietly capture any keystrokes and mouse clicks made by the client over the network. This problem was fixed in the v.2 SSH protocol, but it is up to the user to keep track of what applications have such vulnerabilities and update them as necessary. Section 2.1, "Workstation Security" discusses in more detail what steps administrators and home users should take to limit the vulnerability of computer workstations.

Commands:
Chapter 18. tags Optional. An operator-defined list of tags placed on each log by the collector or normalizer. The payload can be a string with whitespace-delimited string tokens or a JSON list of string tokens. Data type text file The path to the log file from which the collector reads this log entry. Normally, this is a path in the /var/log file system of a cluster node. Data type text offset The offset value. Can represent bytes to the start of the log line in the file (zero- or one-based), or log line numbers (zero- or one-based), so long as the values are strictly monotonically increasing in the context of a single log file. The values are allowed to wrap, representing a new version of the log file (rotation). Data type long

Commands:
Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To propose improvements, open a Jira issue and describe your suggested changes. Provide as much detail as possible to enable us to address your request quickly. Prerequisite You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one. Procedure Click the following Create issue . In the Summary text box, enter a brief description of the issue. In the Description text box, provide the following information: The URL of the page where you found the issue. A detailed description of the issue. You can leave the information in any other fields at their default values. Click Create to submit the Jira issue to the documentation team. Thank you for taking the time to provide feedback.

Commands:
10.2. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. The following types are used with postgresql . Different types allow you to configure flexible access: postgresql_db_t This type is used for several locations. The locations labeled with this type are used for data files for PostgreSQL: /usr/lib/pgsql/test/regres /usr/share/jonas/pgsql /var/lib/pgsql/data /var/lib/postgres(ql)? postgresql_etc_t This type is used for configuration files in /etc/postgresql/ . postgresql_exec_t This type is used for several locations. The locations labeled with this type are used for binaries for PostgreSQL: /usr/bin/initdb(.sepgsql)? /usr/bin/(se)?postgres /usr/lib(64)?/postgresql/bin/.* /usr/lib/phsql/test/regress/pg_regress postgresql_initrc_exec_t This type is used for the PostgreSQL initialization file located at /etc/rc.d/init.d/postgresql . postgresql_log_t This type is used for several locations. The locations labeled with this type are used for log files: /var/lib/pgsql/logfile /var/lib/pgsql/pgstartup.log /var/lib/sepgsql/pgstartup.log /var/log/postgresql /var/log/postgres.log.* /var/log/rhdb/rhdb /var/log/sepostgresql.log.* postgresql_var_run_t This type is used for run-time files for PostgreSQL, such as the process id (PID) in /var/run/postgresql/ .

Commands:
21.5. Enable JMX for CacheManagers At the CacheManager level, JMX statistics can be enabled either declaratively or programmatically, as follows. Enable JMX Declaratively at the CacheManager Level Add the following in the <global> element to enable JMX declaratively at the CacheManager level: Enable JMX Programmatically at the CacheManager Level Add the following code to programmatically enable JMX at the CacheManager level: Report a bug

Commands:
<globalJmxStatistics enabled="true"/>
GlobalConfiguration globalConfiguration = new GlobalConfigurationBuilder()..globalJmxStatistics().enable().build();
5.3.2. Use a Password-like NIS Domain Name and Hostname Any machine within an NIS domain can use commands to extract information from the server without authentication, as long as the user knows the NIS server's DNS hostname and NIS domain name. For instance, if someone either connects a laptop computer into the network or breaks into the network from outside (and manages to spoof an internal IP address), the following command reveals the /etc/passwd map: If this attacker is a root user, they can obtain the /etc/shadow file by typing the following command: Note If Kerberos is used, the /etc/shadow file is not stored within an NIS map. To make access to NIS maps harder for an attacker, create a random string for the DNS hostname, such as o7hfawtgmhwg.domain.com . Similarly, create a different randomized NIS domain name. This makes it much more difficult for an attacker to access the NIS server.

Commands:
ypcat -d <NIS_domain> -h <DNS_hostname> passwd
ypcat -d <NIS_domain> -h <DNS_hostname> shadow
8.155. pki-core 8.155.1. RHBA-2013:1682 - pki-core bug fix update Updated pki-core packages that fix three bugs are now available for Red Hat Enterprise Linux 6. Red Hat Certificate System is an enterprise software system designed to manage enterprise public key infrastructure (PKI) deployments. PKI Core contains fundamental packages required by Red Hat Certificate System, which comprise the Certificate Authority (CA) subsystem. Note: The Certificate Authority component provided by this advisory cannot be used as a standalone server. It is installed and operates as a part of Identity Management (the IPA component) in Red Hat Enterprise Linux. Bug Fixes BZ# 887305 Previously, the /var/run/pki/ca/ directory was assigned an incorrect SElinux context after the installation of the pki-ca package. With this update, the restorecon command is applied on /var/run/pki/ca/ during the post-installation process. As a result, this directory is now labeled with the correct SElinux context. BZ# 895702 , BZ# 999055 Prior to this update, when the pki-ca daemon was restarted on the Red Hat Enterprise Linux 6.4 Identity Management server, AVC denials were reported. With this update, pki-ca has been modified and AVC denials are no longer reported in the aforementioned scenario. BZ# 998715 The pki-selinux package sets the file context for certain default paths, so that the context need not be set when Red Hat Certificate System instances are created. Prior to this update, when pki-selinux was installed, unnecessary warning messages were displayed if these paths did not yet exist. These messages are now suppressed. All users of pki-core are advised to upgrade to these updated packages, which fix these bugs.

Commands:
12.4.4. Deleting a Storage Pool Using virsh The following demonstrates how to delete a storage pool using virsh: To avoid any issues with other guests using the same pool, it is best to stop the storage pool and release any resources in use by it. Optionally, if you want to remove the directory where the storage pool resides use the following command: Remove the storage pool's definition

Commands:
virsh pool-destroy guest_images_disk
virsh pool-delete guest_images_disk
virsh pool-undefine guest_images_disk
Chapter 9. Custom Logging 9.1. Customized Logging Red Hat JBoss Data Virtualization provides a great deal of information via its logging system. To control logging level, contexts, and log locations, you should be familiar with the server's standalone.xml or domain.xml configuration file and the "logging" subsystem. Refer to the Red Hat JBoss Data Virtualization Administration and Configuration Guide for more details about the different contexts available. If you want a custom log handler, you must write a custom java.util.logging.Handler . To do so, ensure you place the implementation class in the "org.jboss.teiid" module as a jar. , define its name, along with any dependencies it may need, in the module.xml file.

Commands:
Chapter 21. Roles 21.1. Role Elements The rel="roles" link obtained from the entry point URI provides access to a static set of system roles. Each individual role element contains the following: Table 21.1. Role elements Element Type Description Properties link="permits" relationship A link to the permits sub-collection for role permits. mutable Boolean: true or false Defines the ability to update or delete the role. Roles with mutable set to false are roles built into the Red Hat Virtualization environment. administrative Boolean: true or false Defines the role as administrative-only.

Commands:
B.27.3. RHBA-2011:1180 - glibc bug fix update Updated glibc packages that fix several bugs are now available for Red Hat Enterprise Linux 6 Extended Update Support. The glibc packages contain the standard C and the standard math libraries. These libraries are used by multiple programs on the system, and without these libraries, the Linux system cannot function properly. Bug Fixes BZ# 712124 Under certain circumstances, a threaded process could have been granted incomplete group membership of the user who was running the process. This was caused by glibc using its default method for group membership determination, which led to the situation where multiple threads interfered with each other while attempting to retrieve the information simultaneously. Due to the nature of the group membership determination method used, each thread ended up with a different subset of the entire result set. With this update, the group membership determination method has been modified to precede this interference. BZ# 712406 When a process corrupted its heap, the malloc() function could have entered a deadlock situation while building up an error message string. This caused the process unresponsive. With this update, the code has been modified to use the mmap() function to allocate memory for the error message. This workaround ensures that malloc() deadlock no longer occurs when allocating memory for an error message when the corrupted process heap is detected, and such a process is now normally aborted. BZ# 715386 Previously, nscd did not take into consideration time-to-live (TTL) parameters for the DNS records it was caching. With this update, the code has been modified so that nscd now respects TTL parameters when it answers requests for DNS records. All users of glibc are advised to upgrade to these updated packages, which fix these bugs.

Commands:
8.111. libcgroup 8.111.1. RHBA-2014:1480 - libcgroup bug fix and enhancement update Updated libcgroup packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The libcgroup packages provide tools and libraries to manage and monitor control groups. Bug Fixes BZ# 1022842 Previously, the cgset command failed to assign value to multiple subsystem parameters at once. This behavior occurred only when using the -r option more than once to tune parameters of a single subsystem. Configuring different subsystems simultaneously worked correctly. This bug has been fixed, and cgset can now set multiple parameters of a single subsystem without complications. BZ# 1028773 libcgroup update introduced an unnecessary dependency on the redhat-lsb-core package. The redhat-lsb-core package subsequently pulled in a large number of other packages, which could cause problems on hardware with limited storage. With this update, the unnecessary dependency on the redhat-lsb-core package has been removed, and thus no unneeded packages are installed on system. BZ# 1057676 Prior to this update, the /src/config.c file contained the incorrectly specified cgroup_copy_cgroup() function. Consequently, certain user-specific resource limits set in the /etc/cgconfig.conf configuration file were not applied. This update fixes the syntax of the aforementioned function in /src/config.c. As a result, all settings in /etc/cgconfig.conf are applied as expected. BZ# 1060227 Previously applied patch that aimed to increase the performance of the pam_cgroup module contained a bug. Consequently, pam_cgroup failed to start and it did not produce an error message. With this update, the aforementioned patch has been reverted, and pam_cgroup now works as expected. BZ# 1080281 The cgset utility did not process all memory subsystem parameters passed to the --copy-from command-line option correctly. Consequently, these control group parameters were not transferred successfully and no warning message was issued. With this update, cgset has been modified to correctly process parameters of memory subsystem passed to --copy-from option, thus fixing this bug. In addition, this update adds the following Enhancement BZ# 1058363 This update adds the /etc/cgconfig.d/ hierarchy designed to store configuration files applicable to various services. Users of libcgroup are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
31.2. VNC Modes in Anaconda Anaconda offers two modes for VNC installation. The mode you select will depend on the network configuration in your environment. 31.2.1. Direct Mode Direct mode VNC in anaconda is when the client initiates a connection to the VNC server running in anaconda. Anaconda will tell you when to initiate this connection in the VNC viewer. Direct mode can be activated by either of the following commands: Specify vnc as a boot argument. Specify the vnc command in the kickstart file used for installation. When you activate VNC mode, anaconda will complete the first stage of the installer and then start VNC to run the graphical installer. The installer will display a message on the console in the following format: Anaconda will also tell you the IP address and display number to use in your VNC viewer. At this point, you need to start the VNC viewer and connect to the target system to continue the installation. The VNC viewer will present anaconda to you in graphical mode. There are some disadvantages to direct mode, including: Requires visual access to the system console to see the IP address and port to connect the VNC viewer to. Requires interactive access to the system console to complete the first stage of the installer. If either of these disadvantages would prevent you from using direct mode VNC in anaconda, then connect mode is probably more suited to your environment.

Commands:
Running anaconda VERSION , the PRODUCT system installer - please wait