mtpti5iD/redhat-docs_dataset huggingface dataset:
D.14. Datatype Hierarchy View To open Teiid Designer's Datatype Hierarchy view, click the main menu's Window > Show View > Other... and then click the Teiid Designer > Datatypes view in the dialog. Figure D.25. Datatype Hierarchy View The following table shows the mapping between Teiid Designer Types and JBoss Data Virtualization Runtime Types. Table D.1. Corresponding Runtime Types Teiid Designer Type Java Runtime Type anyURI java.lang.String base64Binary java.lang.String bigdecimal java.math.BigDecimal biginteger java.math.BigInteger blob java.sql.Blob [a] boolean java.lang.Boolean byte java.lang.Byte char java.lang.Character clob java.sql.Clob [b] date java.sql.Date dateTime java.sql.Timestamp decimal java.math.BigDecimal double java.lang.Double duration java.lang.String ENTITIES java.lang.String ENTITY java.lang.String float java.lang.Float gDay java.math.BigInteger gMonth java.math.BigInteger gMonthDay java.sql.Timestamp gYear java.math.BigInteger gYearMonth java.sql.Timestamp hexBinary java.lang.String ID java.lang.String IDREF java.lang.String IDREFS java.lang.String int java.lang.Integer integer java.math.BigInteger language java.lang.String long java.lang.Long Name java.lang.String NCName java.lang.String negativeInteger java.math.BigInteger NMTOKENS java.lang.String NMTOKENS java.lang.String nonNegativeInteger java.math.BigInteger nonPositiveInteger java.math.BigInteger normalizedString java.lang.String NOTATION java.lang.String object java.lang.Object positiveInteger java.math.BigInteger QName java.lang.String short java.lang.Short string java.lang.String time java.sql.Time timestamp java.sql.Timestamp token java.lang.String unsignedByte java.lang.Short unsignedInt java.lang.Long unsignedLong java.lang.BigInteger unsignedShort java.lang.Integer XMLLiteral java.sql.SQLXML [c] [a] The concrete type is expected to be org.teiid.core.types.BlobType. [b] The concrete type is expected to be org.teiid.core.types.ClobType. [c] The concrete type is expected to be org.teiid.core.types.XMLType.

Commands:
Appendix A. The Virtual Host Metrics Daemon (vhostmd) vhostmd (the Virtual Host Metrics Daemon) allows virtual machines to see limited information about the host they are running on. This daemon is only supplied with Red Hat Enterprise Linux for SAP. In the host, a daemon ( vhostmd ) runs which writes metrics periodically into a disk image. This disk image is exported read-only to guest virtual machines. Guest virtual machines can read the disk image to see metrics. Simple synchronization stops guest virtual machines from seeing out of date or corrupt metrics. The system administrator chooses which metrics are available for use on a per guest virtual machine basis. In addition, the system administrator may block one or more guest virtual machines from having any access to metric configurations. Customers who want to use vhostmd and vm-dump-metrics therefore need subscriptions for "RHEL for SAP Business Applications" to be able to subscribe their RHEL systems running SAP to the "RHEL for SAP" channel on the Customer Portal or Red Hat Subscription Management to install the packages. The following kbase article in the customer portal describes the setup of vhostmd on RHEL: https://access.redhat.com/knowledge/solutions/41566

Commands:
10.5.56. AddHandler AddHandler maps file extensions to specific handlers. For example, the cgi-script handler can be matched with the extension .cgi to automatically treat a file ending with .cgi as a CGI script. The following is a sample AddHandler directive for the .cgi extension. This directive enables CGIs outside of the cgi-bin to function in any directory on the server which has the ExecCGI option within the directories container. Refer to Section 10.5.22, " Directory " for more information about setting the ExecCGI option for a directory. In addition to CGI scripts, the AddHandler directive is used to process server-parsed HTML and image-map files.

Commands:
AddHandler cgi-script .cgi
11.3.3.7. Special Options These options are occasionally useful for overriding defaults often found in the .fetchmailrc file. -a - Fetchmail downloads all messages from the remote email server, whether new or previously viewed. By default, Fetchmail only downloads new messages. -k - Fetchmail leaves the messages on the remote email server after downloading them. This option overrides the default behavior of deleting messages after downloading them. -l <max-number-bytes> - Fetchmail does not download any messages over a particular size and leaves them on the remote email server. --quit - Quits the Fetchmail daemon process. More commands and .fetchmailrc options can be found in the fetchmail man page.

Commands:
27.2.7. Controlling Access to At and Batch You can restrict the access to the at and batch commands using the /etc/at.allow and /etc/at.deny files. These access control files use the same format defining one user name on each line. Mind that no whitespace are permitted in either file. If the file at.allow exists, only users listed in the file are allowed to use at or batch , and the at.deny file is ignored. If at.allow does not exist, users listed in at.deny are not allowed to use at or batch . The at daemon ( atd ) does not have to be restarted if the access control files are modified. The access control files are read each time a user tries to execute the at or batch commands. The root user can always execute at and batch commands, regardless of the content of the access control files.

Commands:
3.11. perf_event When the perf_event subsystem is attached to a hierarchy, all cgroups in that hierarchy can be used to group processes and threads which can then be monitored with the perf tool, as opposed to monitoring each process or thread separately or per-CPU. Cgroups which use the perf_event subsystem do not contain any special tunable parameters other than the common parameters listed in Section 3.12, "Common Tunable Parameters" . For additional information on how tasks in a cgroup can be monitored using the perf tool, refer to the Red Hat Enterprise Linux Developer Guide , available from http://access.redhat.com/site/documentation/Red_Hat_Enterprise_Linux/ .

Commands:
9.4. JMS Master and Slave Back End Configuration While using an Infinispan directory, it is recommended to use the JMS Master/Slave backend. In Infinispan, all nodes share the same index and since IndexWriter is active on different nodes, it acquires the lock on the same index. So instead of sending updates directly to the index, send it to a JMS queue and make a single node apply all changes on behalf of all other nodes. Warning Not enabling a JMS based backend will lead to timeout exceptions when multiple nodes attempt to write to the index. To configure a JMS slave, replace only the backend and set the directory provider to Infinispan. Set the same directory provider on the master and it will connect without the need to set up the copy job across nodes. For Master and Slave backend configuration examples, see the Back End Setup and Operations section of the Red Hat JBoss EAP Administration and Configuration Guide . Report a bug

Commands:
7.5. Configure Distribution Mode (Remote Client-Server Mode) Distribution mode is a clustered mode in Red Hat JBoss Data Grid. Distribution mode can be added to any cache container using the following procedure: Procedure 7.1. The distributed-cache Element The distributed-cache element configures settings for the distributed cache using the following parameters: The name parameter provides a unique identifier for the cache. The mode parameter sets the clustered cache mode. Valid values are SYNC (synchronous) and ASYNC (asynchronous). The (optional) segments parameter specifies the number of hash space segments per cluster. The recommended value for this parameter is ten multiplied by the cluster size and the default value is 20 . The start parameter specifies whether the cache starts when the server starts up or when it is requested or deployed. The owners parameter indicates the number of nodes that will contain the hash segment. If statistics are enabled at the container level, per-cache statistics can be selectively disabled for caches that do not require monitoring by setting the statistics attribute to false . Important JGroups must be appropriately configured for clustered mode before attempting to load this configuration. For details about the cache-container , locking , and transaction elements, see the appropriate chapter. Report a bug

Commands:
<cache-container name="clustered" default-cache="default" statistics="true"> <transport executor="infinispan-transport" lock-timeout="60000"/> <distributed-cache name="default" mode="SYNC" segments="20" start="EAGER" owners="2" statistics="true"> <!-- Additional configuration information here --> </distributed-cache> </cache-container>
18.2. Setup Download the Fuse Full Install binary from the Red Hat Customer Portal. Export the path to the folder where the CSV files will be placed by running the command: Run the following command in the root directory of the quickstart: Set the FUSE_INSTALL_PATH and FUSE_BINARY_PATH variables in the same shell: If running the camel-jbossdatagrid-fuse quickstart in JBoss Fuse 6.2.1 the following changes to the setupEverythingOnFuse.sh script must be made; otherwise proceed to the step: Change the version of Fuse being exported to reference the 6.2.1 component. Update the container name to child1 . Once the environment variables are set run the following from the root directory of the quickstart: After the script completes confirm that the Fuse Hawtio Console may be accessed without error. This console, by default, runs at http://127.0.0.1:8181/hawtio/index.html#/login ; the username and password are both admin . Confirm that both the child1 and child2 containers were created by accessing Fuse Fabric at http://127.0.0.1:8181/hawtio/index.html#/fabric/containers . Both containers should be highlighted in green to indicate they are ready. Report a bug

Commands:
export incomingFolderPath=[Full path to the CSV folder]
mvn clean install -DincomingFolderPath=USDincomingFolderPath
export FUSE_INSTALL_PATH = [Full path to the folder where Fuse will be installed] export FUSE_BINARY_PATH = [Full path to the Fuse zip file downloaded in step 1]
Original line with old version export FUSE_VERSION=jboss-fuse-6.2.0.redhat-133 Updated line for Fuse 6.2.1: export FUSE_VERSION=jboss-fuse-6.2.1.redhat-084 Original line exporting the profile #sh client -r 2 -d 10 "fabric:container-add-profile child demo-local_producer" > /dev/null 2>&1 Updated line for Fuse 6.2.1: sh client -r 2 -d 10 "fabric:container-add-profile child1 demo-local_producer" > /dev/null 2>&1
./setupEverythingOnFuse.sh
B.15.4. RHBA-2011:0294 - device-mapper-multipath bug fix update Updated device-mapper-multipath packages that resolve an issue are now available for Red Hat Enterprise Linux 6. The device-mapper-multipath packages provide tools to manage multipath devices by giving the "dm-multipath" kernel module instructions on what to do, as well as by managing the creation and removal of partitions for Device-Mapper devices. Bug Fix BZ# 672151 Multipathd caches the value of sysfs attribute lookups for the path devices that make up a multipath device. Previously, these weren't being removed when the path devices were removed. As well, in some cases the cache was not helpful and not used. This occasionally caused memory leaks when path devices were removed and restored. With this update, the unnecessary caching has been completely removed and the cached values are now removed when the corresponding path device is removed. Consequently, the occasional memory leaks no longer occur. All device-mapper-multipath users are advised to upgrade to these updated packages, which resolve this issue.

Commands:
Appendix G. Swift response headers The response from the server should include an X-Auth-Token value. The response might also contain a X-Storage-Url that provides the API_VERSION / ACCOUNT prefix that is specified in other requests throughout the API documentation. Table G.1. Response Headers Name Description Type X-Storage-Token The authorization token for the X-Auth-User specified in the request. String X-Storage-Url The URL and API_VERSION / ACCOUNT path for the user. String

Commands:
Chapter 5. GDM GDM is the GNOME Display Manager , which provides a graphical login environment. After the transition from GNOME 2 to GNOME 3, configuring GDM is only possible through systemd as it no longer supports other init systems. the gdm package The gdm package has replaced xorg-x11-xdm , which provided a legacy display login manager for the X Window System. As mentioned before, the gdm package provides the graphical login screen, shown shortly after boot up, log out, and when user-switching. GDM and logind GDM now uses logind for defining and tracking users. For more information, see Chapter 2, logind . System administrators can also set up automatic login manually in the GDM custom configuration file: /etc/gdm/custom.conf . custom.conf GDM configuration is now found in /etc/gdm/custom.conf . However for backwards compatibility, if /etc/gdm/gdm.conf is found it will be used instead of custom.conf . When upgrading, Red Hat recommends removing your old gdm.conf file and migrating any custom configuration to custom.conf . Getting More Information For more information on GDM , see Section 14.1, "What Is GDM?" . For information on configuring and managing user sessions, see Section 14.3, "User Sessions" . For information on customizing the login screen appearance, see Section 10.4, "Customizing the Login Screen" .

Commands:
Chapter 9. Server Message Block (SMB) The Server Message Block (SMB) protocol implements an application-layer network protocol used to access resources on a server, such as file shares and shared printers. On Microsoft Windows, SMB is implemented by default. If you run Red Hat Enterprise Linux, use Samba to provide SMB shares and the cifs-utils utility to mount SMB shares from a remote server. Note In the context of SMB, you sometimes read about the Common Internet File System (CIFS) protocol, which is a dialect of SMB. Both the SMB and CIFS protocol are supported and the kernel module and utilities involved in mounting SMB and CIFS shares both use the name cifs . 9.1. Providing SMB Shares See the Samba section in the Red Hat System Administrator's Guide .

Commands:
8.216. sgml-common 8.216.1. RHBA-2014:0540 - sgml-common bug fix update Updated sgml-common packages that fix one bug are now available for Red Hat Enterprise Linux 6. The sgml-common packages contain a collection of entities and document type definitions (DTDs) that are useful for processing Standard Generalized Markup Language (SGML), but do not need to be included in multiple packages. The sgml-common packages also include an up-to-date Open Catalog file. Bug Fix BZ# 613637 Prior to this update, the licensing COPYING file and documentation was missing from the xml-common subpackage. This update adds the missing basic documentation and COPYING file to xml-common. Users of sgml-common are advised to upgrade to these updated packages, which fix this bug.

Commands:
2.2.4.2. Securing NFS Mount Options The use of the mount command in the /etc/fstab file is explained in the Storage Administration Guide. From a security administration point of view it is worthwhile to note that the NFS mount options can also be specified in /etc/nfsmount.conf , which can be used to set custom default options. 2.2.4.2.1. Review the NFS Server Warning Only export entire file systems. Exporting a subdirectory of a file system can be a security issue. It is possible in some cases for a client to "break out" of the exported part of the file system and get to unexported parts (see the section on subtree checking in the exports(5) man page. Use the ro option to export the file system as read-only whenever possible to reduce the number of users able to write to the mounted file system. Only use the rw option when specifically required. Refer to the man exports(5) page for more information. Allowing write access increases the risk from symlink attacks for example. This includes temporary directories such as /tmp and /usr/tmp . Where directories must be mounted with the rw option avoid making them world-writable whenever possible to reduce risk. Exporting home directories is also viewed as a risk as some applications store passwords in clear text or weakly encrypted. This risk is being reduced as application code is reviewed and improved. Some users do not set passwords on their SSH keys so this too means home directories present a risk. Enforcing the use of passwords or using Kerberos would mitigate that risk. Restrict exports only to clients that need access. Use the showmount -e command on an NFS server to review what the server is exporting. Do not export anything that is not specifically required. Do not use the no_root_squash option and review existing installations to make sure it is not used. Refer to Section 2.2.4.4, "Do Not Use the no_root_squash Option" for more information. The secure option is the server-side export option used to restrict exports to " reserved " ports. By default, the server allows client communication only from " reserved " ports (ports numbered less than 1024), because traditionally clients have only allowed " trusted " code (such as in-kernel NFS clients) to use those ports. However, on many networks it is not difficult for anyone to become root on some client, so it is rarely safe for the server to assume that communication from a reserved port is privileged. Therefore the restriction to reserved ports is of limited value; it is better to rely on Kerberos, firewalls, and restriction of exports to particular clients. Most clients still do use reserved ports when possible. However, reserved ports are a limited resource, so clients (especially those with a large number of NFS mounts) may choose to use higher-numbered ports as well. Linux clients may do this using the " noresvport " mount option. If you want to allow this on an export, you may do so with the " insecure " export option. It is good practice not to allow users to login to a server. While reviewing the above settings on an NFS server conduct a review of who and what can access the server.

Commands:
B.39. krb5 B.39.1. RHSA-2010:0863 - Important: krb5 security update Updated krb5 packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. Kerberos is a network authentication system which allows clients and servers to authenticate to each other using symmetric encryption and a trusted third party, the Key Distribution Center (KDC). CVE-2010-1322 An uninitialized pointer use flaw was found in the way the MIT Kerberos KDC handled TGS (Ticket-granting Server) request messages. A remote, authenticated attacker could use this flaw to crash the KDC or, possibly, disclose KDC memory or execute arbitrary code with the privileges of the KDC (krb5kdc). Red Hat would like to thank the MIT Kerberos Team for reporting this issue. Upstream acknowledges Mike Roszkowski as the original reporter. All krb5 users should upgrade to these updated packages, which contain a backported patch to correct this issue. After installing the updated packages, the krb5kdc daemon will be restarted automatically.

Commands:
2.2. Volume Groups Physical volumes are combined into volume groups (VGs). This creates a pool of disk space out of which logical volumes can be allocated. Within a volume group, the disk space available for allocation is divided into units of a fixed-size called extents. An extent is the smallest unit of space that can be allocated, Within a physical volume, extents are referred to as physical extents. A logical volume is allocated into logical extents of the same size as the physical extents. The extent size is thus the same for all logical volumes in the volume group. The volume group maps the logical extents to physical extents.

Commands:
Chapter 120. AclRuleTopicResource schema reference Used in: AclRule The type property is a discriminator that distinguishes use of the AclRuleTopicResource type from AclRuleGroupResource , AclRuleClusterResource , AclRuleTransactionalIdResource . It must have the value topic for the type AclRuleTopicResource . Property Property type Description type string Must be topic . name string Name of resource for which given ACL rule applies. Can be combined with patternType field to use prefix pattern. patternType string (one of [prefix, literal]) Describes the pattern used in the resource field. The supported types are literal and prefix . With literal pattern type, the resource field will be used as a definition of a full topic name. With prefix pattern type, the resource name will be used only as a prefix. Default value is literal .

Commands:
Chapter 22. Upgrading Certificate System 10 to the latest minor version To upgrade Red Hat Certificate System 10.0 to the latest minor version, for example 10.1, you need to update the packages and the configuration files. Upgrade all packages on the server: During the update, Certificate System configuration files, such as /etc/pki/ <instance_name> / subsystem /CS.cfg and /etc/pki/ <instance_name> /server.xml , are automatically modified to the new version. Log files generated during the Certificate System upgrade are: /var/log/pki/pki-server-upgrade- version .log /var/log/pki/pki-upgrade- version .log Note that the version number in the log file's name represent the pki* package version and not the Certificate System version. Note If Directory Server is installed on a different host, additionally update all packages on that host as well. For details about updating Directory Server, see: the corresponding chapter in the Red Hat Directory Server Installation G e . Red Hat Directory Server Release Notes for notable changes, bug fixes, and known issues in Directory Server. Restart the Certificate System instance: Note To migrate from a lower major version, such as 9.7, to Certificate System 10, see Chapter 21, Upgrading from Certificate System 9 to Certificate System 10 .

Commands:
yum update
systemctl restart pki-tomcatd@ <instance_name> .service
Chapter 5. Device Drivers This chapter provides a comprehensive listing of all device drivers that are new or have been updated in Red Hat Enterprise Linux 7.9. 5.1. New Drivers Graphics Drivers and Miscellaneous Drivers MC Driver for Intel 10nm server processors (i10nm_edac.ko.xz) 5.2. Updated Drivers Network Driver Updates The Netronome Flow Processor (NFP) driver (nfp.ko.xz) has been updated to version 3.10.0-1150.el7.x86_64. VMware vmxnet3 virtual NIC driver (vmxnet3.ko.xz) has been updated to version 1.4.17.0-k. Storage Driver Updates QLogic FCoE Driver (bnx2fc.ko.xz) has been updated to version 2.12.13. Driver for HP Smart Array Controller (hpsa.ko.xz) has been updated to version 3.4.20-170-RH5. Broadcom MegaRAID SAS Driver (megaraid_sas.ko.xz) has been updated to version 07.714.04.00-rh1. QLogic Fibre Channel HBA Driver (qla2xxx.ko.xz) has been updated to version 10.01.00.22.07.9-k. Driver for Microsemi Smart Family Controller version (smartpqi.ko.xz) has been updated to version 1.2.10-099.

Commands:
Preface Given the Metro disaster recovery stretch cluster is to provide resiliency in the face of a complete or partial site outage, it is important to understand the different methods of recovery for applications and their storage. How the application is architected determines how soon it becomes available again on the active zone. There are different methods of recovery for applications and their storage depending on the site outage. The recovery time depends on the application architecture. The different methods of recovery are as follows: Recovery for zone-aware HA applications with RWX storage . Recovery for HA applications with RWX storage . Recovery for applications with RWO storage . Recovery for StatefulSet pods .

Commands: