mtpti5iD/redhat-docs_dataset huggingface dataset:
3.5. RHEA-2011:1609 - new package: libvirt-snmp A new libvirt-snmp package is now available for Red Hat Enterprise Linux 6. The new package libvirt-snmp allows to control and monitor libvirt virtualization management tool by the way of the SNMP protocol. SNMP is an Internet-standard protocol for managing devices on IP networks, its modular structure allows it to be used in new fields and this new package allow virtualization management by bridging the SNMP protocol and the libvirt API. This enhancement update adds the libvirt-snmp package to Red Hat Enterprise Linux 6. (BZ# 642556 , BZ# 706114 ) All users who require libvert-snmp are advised to install this new package.

Commands:
13.5. XQuery Optimization A technique known as document projection is used to reduce the memory footprint of the context item document. Document projection loads only the parts of the document needed by the relevant XQuery and path expressions. Since document projection analysis uses all relevant path expressions, even 1 expression that could potentially use many nodes, e.g. //x rather than /a/b/x will cause a larger memory footprint. With the relevant content removed the entire document will still be loaded into memory for processing. Document projection will only be used when there is a context item (unnamed PASSING clause item) passed to XMLTABLE/XMLQUERY. A named variable will not have document projection performed. In some cases the expressions used may be too complex for the optimizer to use document projection. You should check the SHOWPLAN DEBUG full plan output to see if the appropriate optimization has been performed. With additional restrictions, simple context path expressions allow the processor to evaluate document subtrees independently - without loading the full document in memory. A simple context path expression can be of the form "[/][ns:]root/[ns1:]elem/...", where a namespace prefix or element name can also be the * wild card. As with normal XQuery processing, if namespace prefixes are used in the XQuery expression, they should be declared using the XMLNAMESPACES clause. Example 13.5. Streaming Eligible XMLQUERY Rather than loading the entire doc in-memory as a DOM tree, each child element will be independently added to the result. Example 13.6. Streaming Ineligible XMLQUERY The use of the descendant axis prevents the streaming optimization, but document projection can still be performed. When using XMLTABLE, the COLUMN PATH expressions have additional restrictions. They are allowed to reference any part of the element subtree formed by the context expression and they may use any attribute value from their direct parentage. Any path expression where it is possible to reference a non-direct ancestor or sibling of the current context item prevent streaming from being used. Example 13.7. Streaming Eligible XMLTABLE The context XQuery and the column path expression allow the streaming optimization, rather than loading the entire doc in-memory as a DOM tree, each child element will be independently added to the result. Example 13.8. Streaming Ineligible XMLTABLE The reference of an element outside of the child subtree in the sibling_attr path prevents the streaming optimization from being used, but document projection can still be performed. Column paths should be as targeted as possible to avoid performance issues. A general path such as '..//child' will cause the entire subtree of the context item to be searched on each output row.

Commands:
XMLQUERY('/*:root/*:child' PASSING doc)
XMLQUERY('//child' PASSING doc)
XMLTABLE('/*:root/*:child' PASSING doc COLUMNS fullchild XML PATH '.', parent_attr string PATH '../@attr', child_val integer)
XMLTABLE('/*:root/*:child' PASSING doc COLUMNS sibling_attr string PATH '../other_child/@attr')
Chapter 287. RSS DataFormat Available as of Camel version 2.1 The RSS component ships with an RSS dataformat that can be used to convert between String (as XML) and ROME RSS model objects. marshal = from ROME SyndFeed to XML String unmarshal = from XML String to ROME SyndFeed A route using this would look something like this: The purpose of this feature is to make it possible to use Camel's lovely built-in expressions for manipulating RSS messages. As shown below, an XPath expression can be used to filter the RSS message: Tip Query parameters If the URL for the RSS feed uses query parameters, this component will understand them as well, for example if the feed uses alt=rss , then you can for example do from("rss:http://someserver.com/feeds/posts/default?alt=rss&splitEntries=false&consumer.delay=1000").to("bean:rss"); 287.1. Options The RSS dataformat supports 1 options, which are listed below. Name Default Java Type Description contentTypeHeader false Boolean Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. 287.2. Spring Boot Auto-Configuration The component supports 4 options, which are listed below. Name Description Default Type camel.component.rss.enabled Enable rss component true Boolean camel.component.rss.resolve-property-placeholders Whether the component should resolve property placeholders on itself when starting. Only properties which are of String type can use property placeholders. true Boolean camel.dataformat.rss.content-type-header Whether the data format should set the Content-Type header with the type from the data format if the data format is capable of doing so. For example application/xml for data formats marshalling to XML, or application/json for data formats marshalling to JSon etc. false Boolean camel.dataformat.rss.enabled Enable rss dataformat true Boolean ND

Commands:
2.5. Security TPM TPM (Trusted Platform Module) hardware can create, store and use RSA keys securely (without ever being exposed in memory), verify a platform's software state using cryptographic hashes and more. The trousers and tpm-tools packages are considered a Technology Preview in Red Hat Enterprise Linux 6.3. Packages: trousers-0.3.4-4 , tpm-tools-1.3.4-2

Commands:
4.285. sblim-sfcc 4.285.1. RHBA-2011:1583 - sblim-sfcc bug fix update An updated sblim-sfcc package that fixes various bugs is now available for Red Hat Enterprise Linux 6. The small footprint CIM client library (sblim-sfcc) is a C API allowing client applications to interface with CIM (Common Information Model) implementations (e.g. CIM servers). Due to its small memory and disk footprint it is well-suited for embedded environments. The sblim-sfcc package has been upgraded to upstream version 2.2.2, which provides a number of bug fixes over the version. (BZ# 715331 ) All users of sblim-sfcc are advised to upgrade to this updated package, which fixes these bugs.

Commands:
2.2. Elements of a Tapset The following sections describe the most important aspects of writing a tapset. Most of the content herein is suitable for developers who wish to contribute to SystemTap's upstream library of tapsets. 2.2.1. Tapset Files Tapset files are stored in src /tapset/ of the SystemTap GIT directory. Most tapset files are kept at that level. If you have code that only works with a specific architecture or kernel version, you may choose to put your tapset in the appropriate subdirectory. Installed tapsets are located in /usr/share/systemtap/tapset/ or /usr/local/share/systemtap/tapset . Personal tapsets can be stored anywhere. However, to ensure that SystemTap can use them, use -I tapset_directory to specify their location when invoking stap .

Commands:
Chapter 7. Message delivery 7.1. Writing to a streamed large message To write to a large message, use the BytesMessage.writeBytes() method. The following example reads bytes from a file and writes them to a message: Example: Writing to a streamed large message BytesMessage message = session.createBytesMessage(); File inputFile = new File(inputFilePath); InputStream inputStream = new FileInputStream(inputFile); int numRead; byte[] buffer = new byte[1024]; while ((numRead = inputStream.read(buffer, 0, buffer.length)) != -1) { message.writeBytes(buffer, 0, numRead); } 7.2. Reading from a streamed large message To read from a large message, use the BytesMessage.readBytes() method. The following example reads bytes from a message and writes them to a file: Example: Reading from a streamed large message BytesMessage message = (BytesMessage) consumer.receive(); File outputFile = new File(outputFilePath); OutputStream outputStream = new FileOutputStream(outputFile); int numRead; byte buffer[] = new byte[1024]; for (int pos = 0; pos < message.getBodyLength(); pos += buffer.length) { numRead = message.readBytes(buffer); outputStream.write(buffer, 0, numRead); }

Commands:
BytesMessage message = session.createBytesMessage(); File inputFile = new File(inputFilePath); InputStream inputStream = new FileInputStream(inputFile); int numRead; byte[] buffer = new byte[1024]; while ((numRead = inputStream.read(buffer, 0, buffer.length)) != -1) { message.writeBytes(buffer, 0, numRead); }
BytesMessage message = (BytesMessage) consumer.receive(); File outputFile = new File(outputFilePath); OutputStream outputStream = new FileOutputStream(outputFile); int numRead; byte buffer[] = new byte[1024]; for (int pos = 0; pos < message.getBodyLength(); pos += buffer.length) { numRead = message.readBytes(buffer); outputStream.write(buffer, 0, numRead); }
18.7. Examples of Common Scenarios This section demonstrates different virtual networking modes and provides some example scenarios. 18.7.1. Bridged Mode Bridged mode operates on Layer 2 of the OSI model. When used, all of the guest virtual machines will appear on the same subnet as the host physical machine. The most common use cases for bridged mode include: Deploying guest virtual machines in an existing network alongside host physical machines making the difference between virtual and physical machines transparent to the end user. Deploying guest virtual machines without making any changes to existing physical network configuration settings. Deploying guest virtual machines which must be easily accessible to an existing physical network. Placing guest virtual machines on a physical network where they must access services within an existing broadcast domain, such as DHCP. Connecting guest virtual machines to an existing network where VLANs are used.

Commands:
32.2.5. Explaining the Process The following steps illustrate what happens if the command useradd juan is issued on a system that has shadow passwords enabled: A new line for juan is created in /etc/passwd . The line has the following characteristics: It begins with the username juan . There is an x for the password field indicating that the system is using shadow passwords. A UID greater than 499 is created. (Under Red Hat Enterprise Linux, UIDs and GIDs below 500 are reserved for system use.) A GID greater than 499 is created. The optional GECOS information is left blank. The home directory for juan is set to /home/juan/ . The default shell is set to /bin/bash . A new line for juan is created in /etc/shadow . The line has the following characteristics: It begins with the username juan . Two exclamation points ( !! ) appear in the password field of the /etc/shadow file, which locks the account. Note If an encrypted password is passed using the -p flag, it is placed in the /etc/shadow file on the new line for the user. The password is set to never expire. A new line for a group named juan is created in /etc/group . A group with the same name as a user is called a user private group . For more information on user private groups, refer to Section 32.1.1, "Adding a New User" . The line created in /etc/group has the following characteristics: It begins with the group name juan . An x appears in the password field indicating that the system is using shadow group passwords. The GID matches the one listed for user juan in /etc/passwd . A new line for a group named juan is created in /etc/gshadow . The line has the following characteristics: It begins with the group name juan . An exclamation point ( ! ) appears in the password field of the /etc/gshadow file, which locks the group. All other fields are blank. A directory for user juan is created in the /home/ directory. This directory is owned by user juan and group juan . However, it has read, write, and execute privileges only for the user juan . All other permissions are denied. The files within the /etc/skel/ directory (which contain default user settings) are copied into the new /home/juan/ directory. At this point, a locked account called juan exists on the system. To activate it, the administrator must assign a password to the account using the passwd command and, optionally, set password aging guidelines.

Commands:
8.196. redhat-release-server 8.196.1. RHBA-2014:1405 - redhat-release-server bug fix and enhancement update An updated redhat-release-server package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The redhat-release-server package contains the Red Hat Enterprise Linux Server release file. This updated redhat-release-server package reflects changes made for the release of Red Hat Enterprise Linux 6.6. Users of Red Hat Enterprise Linux 6 are advised to upgrade to this updated redhat-release-server package.

Commands:
5.226. pacemaker 5.226.1. RHBA-2012:0846 - pacemaker bug fix and enhancement update Updated pacemaker packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. Pacemaker is a high-availability cluster resource manager with a powerful policy engine. Bug Fixes BZ# 720214 Previously, the "port" parameter was declared as required in the fencing agent metadata. Some devices, however, determine the correct port automatically and therefore do not need it specified in their configuration. As a consequence, updating configurations that didn't contain the "port" parameter failed with the following error message: This update modifies the fencing agent metadata so that "port" is not declared as a required configuration option. As a result, updating configurations in which the "port" parameter is not specified succeeds. BZ# 720218 Previously, the "start" and "stop" actions were not declared in the fencing agent metadata. As a consequence, the following warning messages were displayed when configuring fencing devices: This update adds the "start" and "stop" actions to all fencing agent metadata. As a result, configuring fencing devices no longer displays the aforementioned warning messages. BZ# 789397 Due to an error in the underlying source code, operation failure records were not removed together with removed resources. Consequently, resources re-defined after deletion were associated with the failure records. This update modifies the underlying source code so that failure records are removed together with removed resources. As a consequence, previously deleted resources are not associated with any failure records after being re-defined. BZ# 799070 Previously, the logic for determining whether a resource is active was incorrect. Consequently, active resources on nodes in the "UNCLEAN" state were ignored by tools that relied on this logic. This update fixes the logic. As a result, tools relying on this logic report active resources on nodes in the "UNCLEAN" state as active. BZ# 801351 Previously, descriptions of the -v and -V options of the crm_report command were swapped in text of its manual pages. Consequently, some users were mislead by unexpected behavior when using these options. This update corrects the text of the manual pages so that they reflect the actual behavior of the crm_report command. Enhancement BZ# 782255 Pacemaker now uses the libqb library for logging. This provides less verbose logs while still providing the ability to debug and support Pacemaker. All users of Pacemaker are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
ERROR: apc-fencing: required parameter port not defined
WARNING: apc-fencing: action start not advertised in meta-data, it may not be supported by the RA WARNING: apc-fencing: action stop not advertised in meta-data, it may not be supported by the RA
8.47. freeipmi 8.47.1. RHBA-2013:1640 - freeipmi bug fix and enhancement update Updated freeipmi packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The FreeIPMI project provides "Remote-Console" (out-of-band) and "System Management Software" (in-band) based on the Intelligent Platform Management Interface specification. Note The freeipmi packages have been upgraded to upstream version 1.2.1, which provides a number of bug fixes and enhancements over the version. Among others, this rebase adds the ipmiseld daemon and subpackage, and the Serial Over Lan (SOL) command processing. This update also provides more secure permissions for configuration files that recognize remote password configuration. (BZ# 951700 ) Bug Fixes BZ# 616846 , BZ# 715605 Prior to this update, the ipmidetectd daemon did not fully validate input command-line parameters. Consequently, ipmidetectd terminated unexpectedly with a segmentation fault when parsing invalid command-line options. With this update, ipmidetectd validates command-line input properly, and therefore no longer crashes in this case. BZ# 818168 Previously, the bmc-watchdog daemon did not create the PID file and did not write the PID number into the file. As a consequence, tools depending on missing PID values did not work correctly. This bug has been fixed, the PID number is now stored in the created PID file and the described problems no longer occur. Users of freeipmi are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
3.3. Special File Locations Under Red Hat Enterprise Linux Red Hat Enterprise Linux extends the FHS structure slightly to accommodate special files. Most files pertaining to RPM are kept in the /var/lib/rpm/ directory. For more information on RPM, refer to the chapter titled Package Management with RPM in the System Administrators Guide . The /var/spool/up2date/ directory contains files used by Red Hat User Agent , including RPM header information for the system. This location may also be used to temporarily store RPMs downloaded while updating the system. For more information about Red Hat Network, refer to the documentation online at https://rhn.redhat.com/ . Another location specific to Red Hat Enterprise Linux is the /etc/sysconfig/ directory. This directory stores a variety of configuration information. Many scripts that run at boot time use the files in this directory. Refer to Chapter 4, The sysconfig Directory for more information about what is within this directory and the role these files play in the boot process. Finally, one more directory worth noting is the /initrd/ directory. It is empty, but is used as a critical mount point during the boot process. Warning Do not remove the /initrd/ directory for any reason. Removing this directory causes the system to fail to boot with a kernel panic error message.

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-05-30 17:22:40 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
4.163. lohit-punjabi-fonts 4.163.1. RHEA-2011:1135 - lohit-punjabi-fonts enhancement update An updated lohit-punjabi-fonts package which adds one enhancement is now available for Red Hat Enterprise Linux 6. The lohit-punjabi-fonts package provides a free Punjabi TrueType/OpenType font. Enhancement BZ# 691294 Unicode 6.0, the most recent major version of the Unicode standard, introduces the Indian Rupee Sign (U+20B9), the new official Indian currency symbol. With this update, the lohit-punjabi-fonts package now includes a glyph for this new character. All users requiring the Indian rupee sign should install this updated package, which adds this enhancement.

Commands:
7.52. evolution 7.52.1. RHSA-2013:0516 - Low: evolution security and bug fix update Updated evolution packages that fix one security issue and three bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. Evolution is the GNOME mailer, calendar, contact manager and communication tool. The components which make up Evolution are tightly integrated with one another and act as a seamless personal information-management tool. Security Fix CVE-2011-3201 The way Evolution handled mailto URLs allowed any file to be attached to the new message. This could lead to information disclosure if the user did not notice the attached file before sending the message. With this update, mailto URLs cannot be used to attach certain files, such as hidden files or files in hidden directories, files in the /etc/ directory, or files specified using a path containing "..". Red Hat would like to thank Matt McCutchen for reporting this issue. Bug Fixes BZ#707526 Creating a contact list with contact names encoded in UTF-8 caused these names to be displayed in the contact list editor in the ASCII encoding instead of UTF-8. This bug has been fixed and the contact list editor now displays the names in the correct format. BZ# 805239 Due to a bug in the evolution-alarm-notify process, calendar appointment alarms did not appear in some types of calendars. The underlying source code has been modified and calendar notifications work as expected. BZ# 890642 An attempt to print a calendar month view as a PDF file caused Evolution to terminate unexpectedly. This update applies a patch to fix this bug and Evolution no longer crashes in this situation. All evolution users are advised to upgrade to these updated packages, which contain backported patches to correct these issues. All running instances of Evolution must be restarted for this update to take effect.

Commands: