mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Deprecated features This section describes features that are supported, but have been deprecated from AMQ Broker. upgrade attribute in Custom Resource Starting in 7.11, the upgrade attribute and the associated enabled and minor attributes are deprecated because they cannot work as originally designed. Use the image or version attributes to deploy specific broker container images. queues configuration element Starting in 7.10, the <queues> configuration element is deprecated. You can use the <addresses> configuration element to create addresses and associated queues. The <queues> configuration element will be removed in a future release. getAddressesSettings method Starting in 7.10, the get Addresses Settings method, which is included in the org.apache.activemq.artemis.core.config.Configuration interface, is deprecated. Use the get Address Settings method to configure addresses and queues for the broker programatically. OpenWire protocol Starting in 7.9, the OpenWire protocol is a deprecated feature. If you are creating a new AMQ Broker-based system, use one of the other supported protocols. In the 8.0 release, the Openwire protocol will be removed from AMQ Broker. Adding users when broker instance is not running Starting in 7.8, when an AMQ Broker instance is not running, the ability to add users to the broker from the CLI interface is removed. Network pinger Starting in 7.5, network pinging is a deprecated feature. Network pinging cannot protect a broker cluster from network isolation issues that can lead to irrecoverable message loss. This feature will be removed in a future release. Red Hat continues to support existing AMQ Broker deployments that use network pinging. However, Red Hat no longer recommends use of network pinging in new deployments. For guidance on configuring a broker cluster for high availability and to avoid network isolation issues, see Implementing high availability in Configuring AMQ Broker . Hawtio dispatch console plugin Starting in 7.3, AMQ Broker no longer ships with the Hawtio dispatch console plugin, dispatch-hawtio-console.war . Previously, the dispatch console was used to manage AMQ Interconnect. However, AMQ Interconnect now uses its own, standalone web console.

Commands:
Chapter 24. DHCP The dhcpd daemon is used in Red Hat Enterprise Linux to dynamically deliver and configure Layer 3 TCP/IP details for clients. The dhcp package provides the DHCP server and the dhcpd daemon. Enter the following command to see if the dhcp package is installed: If it is not installed, use the yum utility as root to install it: 24.1. DHCP and SELinux When dhcpd is enabled, it runs confined by default. Confined processes run in their own domains, and are separated from other confined processes. If a confined process is compromised by an attacker, depending on SELinux policy configuration, an attacker's access to resources and the possible damage they can do is limited. The following example demonstrates dhcpd and related processes running in their own domain. This example assumes the dhcp package is installed and that the dhcpd service has been started: Run the getenforce command to confirm SELinux is running in enforcing mode: The command returns Enforcing when SELinux is running in enforcing mode. Enter the following command as the root user to start dhcpd : Confirm that the service is running. The output should include the information below (only the time stamp will differ): Run following command to view the dhcpd processes: The SELinux context associated with the dhcpd process is system_u:system_r:dhcpd_t:s0 .

Commands:
~]# rpm -q dhcp package dhcp is not installed
~]# yum install dhcp
~]USD getenforce Enforcing
~]# systemctl start dhcpd.service
~]# systemctl status dhcpd.service dhcpd.service - DHCPv4 Server Daemon Loaded: loaded (/usr/lib/systemd/system/dhcpd.service; disabled) Active: active (running) since Mon 2013-08-05 11:49:07 CEST; 3h 20min ago
~]USD ps -eZ | grep dhcpd system_u:system_r:dhcpd_t:s0 5483 ? 00:00:00 dhcpd
5.5. Batching Network Packets In configurations with a long transmission path, batching packets before submitting them to the kernel may improve cache utilization. To configure the maximum number of packets that can be batched where N is the maximum number of packets to batch: To provide support for tun / tap rx batching for type='bridge' or type='network' interfaces, add a snippet similar to the following to the domain XML file.

Commands:
ethtool -C USDtap rx-frames N
<devices> <interface type='network'> <source network='default'/> <target dev='vnet0'/> <coalesce> <rx> <frames max='7'/> </rx> </coalesce> </interface> </devices>
6.3.6. Activating and Mounting the Original Logical Volume Since you had to deactivate the logical volume mylv , you need to activate it again before you can mount it.

Commands:
lvchange -a y /dev/myvg/mylv mount /dev/myvg/mylv /mnt df Filesystem 1K-blocks Used Available Use% Mounted on /dev/yourvg/yourlv 24507776 32 24507744 1% /mnt /dev/myvg/mylv 24507776 32 24507744 1% /mnt
2.4. Data Roles All authenticated users have access to a VDB. To restrict access, configure data roles. Set these in the Teiid Designer or the dynamic VDB's vdb.xml file. As part of the data role definition, you can map them to JAAS roles specified in <mapped-role-name> tags. (Establish these mappings using the addDataRoleMapping() method.) How these JAAS roles are associated with users depends on which particular JAAS login module you use. For instance, the default UsersRolesLoginModule associates users with JAAS roles in plain text files. For more information about data roles, see Red Hat JBoss Data Virtualization Development Guide: Reference Material . Important Do not use "admin" or "user" as JAAS role names as these are reserved specifically for Dashboard Builder permissions.

Commands:
20.10. Connecting the Serial Console for the Guest Virtual Machine The virsh console domain [--devname devicename ] [--force] [--safe] command connects the virtual serial console for the guest virtual machine. This is very useful for example for guests that do not provide VNC or SPICE protocols (and thus does not offer video display for GUI tools ) and that do not have network connection (and thus cannot be interacted with using SSH). The optional --devname parameter refers to the device alias of an alternate console, serial, or parallel device configured for the guest virtual machine. If this parameter is omitted, the primary console will be opened. If the --safe option is specified, the connection is only attempted if the driver supports safe console handling. This option specifies that the server has to ensure exclusive access to console devices. Optionally, the force option may be specified, which requests to disconnect any existing sessions, such as in the case of a broken connection. Example 20.19. How to start a guest virtual machine in console mode The following example starts a previously created guest1 virtual machine so that it connects to the serial console using safe console handling: # virsh console guest1 --safe

Commands:
4.2. Managing Cluster Nodes You can perform the following node-management functions through the luci server component of Conga : Make a node leave or join a cluster. Fence a node. Reboot a node. Delete a node. To perform one the functions in the preceding list, follow the steps in this section. The starting point of the procedure is at the cluster-specific page that you navigate to from Choose a cluster to administer displayed on the cluster tab. At the detailed menu for the cluster (below the clusters menu), click Nodes . Clicking Nodes causes the display of nodes in the center of the page and causes the display of an Add a Node element and a Configure element with a list of the nodes already configured in the cluster. At the right of each node listed on the page displayed from the preceding step, click the Choose a task drop-down box. Clicking Choose a task drop-down box reveals the following selections: Have node leave cluster / Have node join cluster , Fence this node , Reboot this node , and Delete . The actions of each function are summarized as follows: Have node leave cluster / Have node join cluster - Have node leave cluster is available when a node has joined of a cluster. Have node join cluster is available when a node has left a cluster. Selecting Have node leave cluster shuts down cluster software and makes the node leave the cluster. Making a node leave a cluster prevents the node from automatically joining the cluster when it is rebooted. Selecting Have node join cluster starts cluster software and makes the node join the cluster. Making a node join a cluster allows the node to automatically join the cluster when it is rebooted. Fence this node - Selecting this action causes the node to be fenced according to how the node is configured to be fenced. Reboot this node - Selecting this action causes the node to be rebooted. Delete - Selecting this action causes the node to be deleted from the cluster configuration. It also stops all cluster services on the node, and deletes the cluster.conf file from /etc/cluster/ . Select one of the functions and click Go . Clicking Go causes a progress page to be displayed. When the action is complete, a page is displayed showing the list of nodes for the cluster.

Commands:
14.2. Modifying BitRot Detection Behavior Once the daemon is enabled, you can pause and resume the detection process, check its status, and modify how often or how quickly it runs. gluster volume bitrot VOLNAME scrub ondemand Starts the scrubbing process and the scrubber will start crawling the file system immediately. Ensure to keep the scrubber in 'Active (Idle)' state, where the scrubber is waiting for it's frequency cycle to start scrubbing, for on demand scrubbing to be successful. On demand scrubbing does not work when the scrubber is in 'Paused' state or already running. gluster volume bitrot VOLNAME scrub pause Pauses the scrubbing process on the specified volume. Note that this does not stop the BitRot daemon; it stops the process that cycles through the volume checking files. gluster volume bitrot VOLNAME scrub resume Resumes the scrubbing process on the specified volume. Note that this does not start the BitRot daemon; it restarts the process that cycles through the volume checking files. gluster volume bitrot VOLNAME scrub status This command prints a summary of scrub status on the specified volume, including various configuration details and the location of the bitrot and scrubber error logs for this volume. It also prints details each node scanned for errors, along with identifiers for any corrupted objects located. gluster volume bitrot VOLNAME scrub-throttle rate Because the BitRot daemon scrubs the entire file system, scrubbing can have a severe performance impact. This command changes the rate at which files and objects are verified. Valid rates are lazy , normal , and aggressive . By default, the scrubber process is started in lazy mode. gluster volume bitrot VOLNAME scrub-frequency frequency This command changes how often the scrub operation runs when the BitRot daemon is enabled. Valid options are daily , weekly , biweekly , and monthly .By default, the scrubber process is set to run biweekly .

Commands:
7.4. Laser Printers An older technology than inkjet, laser printers are another popular alternative to legacy impact printing. Laser printers are known for their high volume output and low cost-per-page. Laser printers are often deployed in enterprises as a workgroup or departmental print center, where performance, durability, and output requirements are a priority. Because laser printers service these needs so readily (and at a reasonable cost-per-page), the technology is widely regarded as the workhorse of enterprise printing. Laser printers share much of the same technologies as photocopiers. Rollers pull a sheet of paper from a paper tray and through a charge roller , which gives the paper an electrostatic charge. At the same time, a printing drum is given the opposite charge. The surface of the drum is then scanned by a laser, discharging the drum's surface and leaving only those points corresponding to the desired text and image with a charge. This charge is then used to force toner to adhere to the drum's surface. The paper and drum are then brought into contact; their differing charges cause the toner to then adhere to the paper. Finally, the paper travels between fusing rollers , which heat the paper and melt the toner, fusing it onto the paper's surface. 7.4.1. Color Laser Printers Color laser printers aim to combine the best features of laser and inkjet technology into a multi-purpose printer package. The technology is based on traditional monochrome laser printing, but uses additional components to create color images and documents. Instead of using black toner only, color laser printers use a CMYK toner combination. The print drum either rotates each color and lays the toner down one color at a time, or lays all four colors down onto a plate and then passes the paper through the drum, transferring the complete image onto the paper. Color laser printers also employ fuser oil along with the heated fusing rolls, which further bonds the color toner to the paper and can give varying degrees of gloss to the finished image. Because of their increased features, color laser printers are typically twice (or several times) as expensive as monochrome laser printers. In calculating the total cost of ownership with respect to printing resources, some administrators may wish to separate monochrome (text) and color (image) functionality to a dedicated monochrome laser printer and a dedicated color laser (or inkjet) printer, respectively.

Commands:
10.6. Default Modules The Apache HTTP Server is distributed with a number of modules. By default the following modules are installed and enabled with the httpd package in Red Hat Enterprise Linux 4.5.0;: Additionally, the following modules are available by installing additional packages:

Commands:
mod_access mod_actions mod_alias mod_asis mod_auth mod_auth_anon mod_auth_dbm mod_auth_digest mod_auth_ldap mod_autoindex mod_cache mod_cern_meta mod_cgi mod_dav mod_dav_fs mod_deflate mod_dir mod_disk_cache mod_env mod_expires mod_ext_filter mod_file_cache mod_headers mod_imap mod_include mod_info mod_ldap mod_log_config mod_logio mod_mem_cache mod_mime mod_mime_magic mod_negotiation mod_proxy mod_proxy_connect mod_proxy_ftp mod_proxy_http mod_rewrite mod_setenvif mod_speling mod_status mod_suexec mod_unique_id mod_userdir mod_usertrack mod_vhost_alias
mod_auth_kerb mod_auth_mysql mod_auth_pgsql mod_authz_ldap mod_dav_svn mod_jk2 mod_perl mod_python mod_ssl php
6.4. Displaying Constraints There are a several commands you can use to display constraints that have been configured. The following command lists all current location, order, and colocation constraints. The following command lists all current location constraints. If resources is specified, location constraints are displayed per resource. This is the default behavior. If nodes is specified, location constraints are displayed per node. If specific resources or nodes are specified, then only information about those resources or nodes is displayed. The following command lists all current ordering constraints. If the --full option is specified, show the internal constraint IDs. The following command lists all current colocation constraints. If the --full option is specified, show the internal constraint IDs. The following command lists the constraints that reference specific resources.

Commands:
pcs constraint list|show
pcs constraint location [show resources|nodes [ specific nodes | resources ]] [--full]
pcs constraint order show [--full]
pcs constraint colocation show [--full]
pcs constraint ref resource
Chapter 31. Red Hat Enterprise Linux Atomic Host 7.3.5 31.1. Atomic Host OStree update : New Tree Version: 7.3.5 (hash: 0ccf9138962e5c2c3794969a228e751d13bb780f5b0a1f15f4a9649df06ba80a) Changes since Tree Version 7.3.4-1 (hash: d6c7a5639cdeb6c21cf40d80259d516d047176e35411c8684cae40a93eedbed0) Updated packages : cockpit-ostree-138-5.el7 redhat-release-atomic-host-7.3-20161129.0.atomic.el7.5 rpm-ostree-client-2017.5-1.atomic.el7 31.2. Extras Updated packages : atomic-1.17.2-3.git2760e30.el7 cockpit-138-6.el7 container-selinux-2.12-2.gite7096ce.el7 docker-1.12.6-28.git1398f24.el7 docker-distribution-2.6.1-1.el7 docker-latest-1.13.1-11.git3a17ad5.el7 etcd-3.1.7-1.el7 kubernetes-1.5.2-0.6.gitd33fd89.el7 * ostree-2017.5-1.el7 skopeo-0.1.19-1.el7 WALinuxAgent-2.2.10-1.el7 The asterisk (*) marks packages which are available for Red Hat Enterprise Linux only. 31.2.1. Container Images Updated : Red Hat Enterprise Linux 7.3 Container Image (rhel7.3, rhel7, rhel7/rhel, rhel) Red Hat Enterprise Linux Atomic Identity Management Server Container Image (rhel7/ipa-server) Red Hat Enterprise Linux Atomic Image (rhel-atomic, rhel7-atomic, rhel7/rhel-atomic) Red Hat Enterprise Linux Atomic Kubernetes apiserver Container Image (rhel7/kubernetes-apiserver) Red Hat Enterprise Linux Atomic Kubernetes controller-manager Container (rhel7/kubernetes-controller-mgr) Red Hat Enterprise Linux Atomic Kubernetes scheduler Container Image (rhel7/kubernetes-scheduler) Red Hat Enterprise Linux Atomic SSSD Container Image (rhel7/sssd) Red Hat Enterprise Linux Atomic Tools Container Image (rhel7/rhel-tools) Red Hat Enterprise Linux Atomic cockpit-ws Container Image (rhel7/cockpit-ws) Red Hat Enterprise Linux Atomic etcd Container Image (rhel7/etcd) Red Hat Enterprise Linux Atomic flannel Container Image (rhel7/flannel) Red Hat Enterprise Linux Atomic open-vm-tools Container Image (rhel7/open-vm-tools) Red Hat Enterprise Linux Atomic openscap Container Image (rhel7/openscap) Red Hat Enterprise Linux Atomic rsyslog Container Image (rhel7/rsyslog) Red Hat Enterprise Linux Atomic sadc Container Image (rhel7/sadc) New : Red Hat Enterprise Linux 7 Init Container Image (rhel7/rhel7-init) 31.3. New Features Red Hat Enterprise Linux 7 Init Container Image is now available The new Red Hat Enterprise Linux 7 Init Image allows creating containerized services based on the systemd init system. This container image configures systemd in an OCI container and enables running one or more services in a RHEL7 user space using unit files, init scripts, or both. For details on using rhev7-init , see Using the Atomic RHEL7 Init Container Image in the Managing Containers Guide.

Commands:
2.4. Storage Formats for Virtual Disks QCOW2 Formatted Virtual Machine Storage QCOW2 is a storage format for virtual disks. QCOW stands for QEMU copy-on-write. The QCOW2 format decouples the physical storage layer from the virtual layer by adding a mapping between logical and physical blocks. Each logical block is mapped to its physical offset, which enables storage over-commitment and virtual machine snapshots, where each QCOW volume only represents changes made to an underlying virtual disk. The initial mapping points all logical blocks to the offsets in the backing file or volume. When a virtual machine writes data to a QCOW2 volume after a snapshot, the relevant block is read from the backing volume, modified with the new information and written into a new snapshot QCOW2 volume. Then the map is updated to point to the new place. Raw The raw storage format has a performance advantage over QCOW2 in that no formatting is applied to virtual disks stored in the raw format. Virtual machine data operations on virtual disks stored in raw format require no additional work from hosts. When a virtual machine writes data to a given offset in its virtual disk, the I/O is written to the same offset on the backing file or logical volume. Raw format requires that the entire space of the defined image be preallocated unless using externally managed thin provisioned LUNs from a storage array.

Commands:
3.3. Spring Framework 3.2 The infinispan-spring3 module has been deprecated in JBoss Data Grid 6.6.0 as the Spring Framework 3.2.x line is reaching End-Of-Life at the end of 2016, and is expected to be removed in version 7.0.0. The integration with Spring Framework 4.x will continue to be supported in version 7.0.0, via the infinispan-spring4 module. Report a bug

Commands:
2.7. Create a Materialized View for Code Table Caching Procedure 2.1. Create a Materialized View for Code Table Caching Create a view selecting the appropriate columns from the desired table. In general, this view may have an arbitrarily complicated transformation query. Designate the appropriate column(s) as the primary key. Additional indexes can be added if needed. Set the materialized property to true. Add a cache hint to the transformation query. To mimic the behavior of the implicit internal materialized view created by the lookup function, use the Hints and Options /*+ cache(pref_mem) */ to indicate that the table data pages should prefer to remain in memory. Result Just as with the lookup function, the materialized view table will be created on first use and reused subsequently.

Commands:
7.15. binutils 7.15.1. RHBA-2013:0498 - binutils bug fix update Updated binutils packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The binutils packages provide a set of binary utilities, including "ar" (for creating, modifying and extracting from archives), "as" (a family of GNU assemblers), "gprof" (for displaying call graph profile data), "ld" (the GNU linker), "nm" (for listing symbols from object files), "objcopy" (for copying and translating object files), "objdump" (for displaying information from object files), "ranlib" (for generating an index for the contents of an archive), "readelf" (for displaying detailed information about binary files), "size" (for listing the section sizes of an object or archive file), "strings" (for listing printable strings from files), "strip" (for discarding symbols), and "addr2line" (for converting addresses to file and line). Bug Fixes BZ#773526 In order to display a non-printing character, the readelf utility adds the "0x40" string to the character. However, readelf previously did not add that string when processing multibyte characters, so that multibyte characters in the ELF headers were displayed incorrectly. With this update, the underlying code has been corrected and readelf now displays multibyte and non-ASCII characters correctly. BZ#825736 Under certain circumstances, the linker could fail to produce the GNU_RELRO segment when building an executable requiring GNU_RELRO. As a consequence, such an executable failed upon start-up. This problem affected also the libudev library so that the udev utility did not work. With this update, the linker has been modified so that the GNU_RELRO segment is now correctly created when it is needed, and utilities such as udev now work correctly. All users of binutils are advised to upgrade to these updated packages, which fix these bugs.

Commands:
9.2. Command Logging API If you want to build a custom appender for command logging that will have access to java.util.logging.LogRecord s to the "COMMAND_LOG" context, the handler will receive a message that is an instance of LogRecord . This object will contain a parameter of type org.teiid.logging.CommandLogMessage . The relevant Red Hat JBoss Data Virtualization classes are defined in the teiid-api-[versionNumber].jar . The CommandLogMessage includes information about VDB, session, command SQL, etc. CommandLogMessages are logged at the DEBUG level. An example follows.

Commands:
package org.something; import java.util.logging.Handler; import java.util.logging.LogRecord; public class CommandHandler extends Handler { @Override public void publish(LogRecord record) { CommandLogMessage msg = (CommandLogMessage)record.getParameters()[0]; //log to a database, trigger an email, etc. } @Override public void flush() { } @Override public void close() throws SecurityException { } }