mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 204. Kubernetes Persistent Volume Component Available as of Camel version 2.17 The Kubernetes Persistent Volume component is one of Kubernetes Components which provides a producer to execute kubernetes persistent volume operations. 204.1. Component Options The Kubernetes Persistent Volume component has no options. 204.2. Endpoint Options The Kubernetes Persistent Volume endpoint is configured using URI syntax: with the following path and query parameters: 204.2.1. Path Parameters (1 parameters): Name Description Default Type masterUrl Required Kubernetes API server URL String 204.2.2. Query Parameters (20 parameters): Name Description Default Type apiVersion (producer) The Kubernetes API Version to use String dnsDomain (producer) The dns domain, used for ServiceCall EIP String kubernetesClient (producer) Default KubernetesClient to use if provided KubernetesClient operation (producer) Producer operation to do on Kubernetes String portName (producer) The port name, used for ServiceCall EIP String portProtocol (producer) The port protocol, used for ServiceCall EIP tcp String connectionTimeout (advanced) Connection timeout in milliseconds to use when making requests to the Kubernetes API server. Integer synchronous (advanced) Sets whether synchronous processing should be strictly used, or Camel is allowed to use asynchronous processing (if supported). false boolean caCertData (security) The CA Cert Data String caCertFile (security) The CA Cert File String clientCertData (security) The Client Cert Data String clientCertFile (security) The Client Cert File String clientKeyAlgo (security) The Key Algorithm used by the client String clientKeyData (security) The Client Key data String clientKeyFile (security) The Client Key file String clientKeyPassphrase (security) The Client Key Passphrase String oauthToken (security) The Auth Token String password (security) Password to connect to Kubernetes String trustCerts (security) Define if the certs we used are trusted anyway or not Boolean username (security) Username to connect to Kubernetes String 204.3. Spring Boot Auto-Configuration The component supports 2 options, which are listed below. Name Description Default Type camel.component.kubernetes-persistent-volumes.enabled Whether to enable auto configuration of the kubernetes-persistent-volumes component. This is enabled by default. Boolean camel.component.kubernetes-persistent-volumes.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

Commands:
kubernetes-persistent-volumes:masterUrl
C.15. Passivation org.infinispan.eviction.PassivationManager The Passivation component handles the passivation of entries to a CacheStore on eviction. Table C.24. Attributes Name Description Type Writable passivations Number of passivation events. String No statisticsEnabled Enables or disables the gathering of statistics by this component boolean Yes Table C.25. Operations Name Description Signature resetStatistics Resets statistics gathered by this component. void resetStatistics() 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
7.241. yum-rhn-plugin 7.241.1. RHBA-2015:1390 - yum-rhn-plugin bug fix and enhancement update Updated yum-rhn-plugin package that fixes two bugs and adds two enhancements is now available for Red Hat Enterprise Linux 6. The yum-rhn-plugin package allows the Yum package manager to access content from Red Hat Network. Bug Fixes BZ# 1155129 Previously, provisioning virtual guests on Red Hat Enterprise Linux 6 did not properly cooperate with the Satellite implementation of the koan tool. As a consequence, using the rhn_check program failed if the spacewalk-koan package was installed on the client. With this update, spacewalk-koan has been modified to be compatible with rhn_check, and the described problem no longer occurs. BZ# 1018929 The yum-rhn-plugin package has been updated to support API changes introduced in the update of the rhn-client-tools package. Enhancements BZ# 916597 With this update, the network connection error message has been enhanced to inform about the cause of the error. BZ# 729913 The rhnplugin.conf(5) manual page has been updated to provide the complete description of rhnplugin.conf configuration options. BZ# 1183989 When registering Red Hat Enterprise Linux 6.6 to Red Hat Satellite using an activation key configured to automatically install specific packages upon registration, the installation of these packages in some cases failed. This update fixes the underlying code, and package installations based on the activation key are now performed successfully. Users of fedfs-utils are advised to upgrade to this updated package, which fixes these bugs and adds this enhancement.

Commands:
9.6.2. Useful Websites http://nfs.sourceforge.net/ - The home of the Linux NFS project and a great place for project status updates. http://www.citi.umich.edu/projects/nfsv4/linux/ - An NFSv4 for Linux 2.6 kernel resource. http://www.nfsv4.org - The home of NFS version 4 and all related standards. http://www.vanemery.com/Linux/NFSv4/NFSv4-no-rpcsec.html - Describes the details of NFSv4 with Fedora Core 2, which includes the 2.6 kernel. http://www.nluug.nl/events/sane2000/papers/pawlowski.pdf - An excellent whitepaper on the features and enhancements of the NFS Version 4 protocol.

Commands:
2.5. Kerberos Maintaining system security and integrity within a network is critical, and it encompasses every user, application, service, and server within the network infrastructure. It requires an understanding of everything that is running on the network and the manner in which these services are used. At the core of maintaining this security is maintaining access to these applications and services and enforcing that access. Kerberos provides a mechanism that allows both users and machines to identify themselves to network and receive defined, limited access to the areas and services that the administrator configured. Kerberos authenticates entities by verifying their identity, and Kerberos also secures this authenticating data so that it cannot be accessed and used or tampered with by an outsider. For more information on Pluggable Authentication Modules, see the corresponding chapter in the Red Hat Enterprise Linux 6 Managing Single Sign-On and Smart Cards guide.

Commands:
probe::signal.checkperm Name probe::signal.checkperm - Check being performed on a sent signal Synopsis Values name Name of the probe point task A task handle to the signal recipient sinfo The address of the siginfo structure si_code Indicates the signal type sig_name A string representation of the signal sig The number of the signal pid_name Name of the process receiving the signal sig_pid The PID of the process receiving the signal

Commands:
signal.checkperm
Chapter 2. Installation This chapter guides you through the steps to install AMQ JMS Pool in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with AMQ JMS Pool, you must install Apache Maven . To use AMQ JMS Pool, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.messaginghub</groupId> <artifactId>pooled-jms</artifactId> <version>1.2.1.redhat-00003</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, AMQ JMS Pool can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the AMQ Clients 2.9.0 JMS Pool Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-clients-2.9.0-jms-pool-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.4. Installing the examples Procedure Use the git clone command to clone the source repository to a local directory named pooled-jms : USD git clone https://github.com/messaginghub/pooled-jms.git pooled-jms Change to the pooled-jms directory and use the git checkout command to switch to the 1.2.1 branch: USD cd pooled-jms USD git checkout 1.2.1 The resulting local directory is referred to as <source-dir> throughout this document.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.messaginghub</groupId> <artifactId>pooled-jms</artifactId> <version>1.2.1.redhat-00003</version> </dependency>
unzip amq-clients-2.9.0-jms-pool-maven-repository.zip
git clone https://github.com/messaginghub/pooled-jms.git pooled-jms
cd pooled-jms git checkout 1.2.1
Chapter 14. Red Hat Software Collections Red Hat Software Collections is a Red Hat content set that provides a set of dynamic programming languages, database servers, and related packages that you can install and use on all supported releases of Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 on AMD64 and Intel 64 architectures. Dynamic languages, database servers, and other tools distributed with Red Hat Software Collections do not replace the default system tools provided with Red Hat Enterprise Linux, nor are they used in preference to these tools. Red Hat Software Collections uses an alternative packaging mechanism based on the scl utility to provide a parallel set of packages. This set allows for optional use of alternative package versions on Red Hat Enterprise Linux. By using the scl utility, users can pick and choose which package version they want to run at any time. Red Hat Developer Toolset is now a part of Red Hat Software Collections. It is included as a separate Software Collection. Red Hat Developer Toolset is designed for developers working on the Red Hat Enterprise Linux platform. It provides current versions of the GNU Compiler Collection, GNU Debugger, Eclipse development platform, and other development, debugging, and performance monitoring tools. Important Red Hat Software Collections has a shorter life cycle and support term than Red Hat Enterprise Linux. For more information, see the Red Hat Software Collections Product Life Cycle . See the Red Hat Software Collections documentation for the components included in the set, system requirements, known problems, usage, and specifics of individual Software Collections. See the Red Hat Developer Toolset documentation for more information about the components included in this Software Collection, installation, usage, known problems, and more.

Commands:
8.6. The Installation Summary Screen The Installation Summary screen is the central location for setting up an installation. Figure 8.4. The Installation Summary Screen Instead of directing you through consecutive screens, the Red Hat Enterprise Linux installation program allows you to configure your installation in the order you choose. Use your mouse to select a menu item to configure a section of the installation. When you have completed configuring a section, or if you would like to complete that section later, click the Done button located in the upper left corner of the screen. Only sections marked with a warning symbol are mandatory. A note at the bottom of the screen warns you that these sections must be completed before the installation can begin. The remaining sections are optional. Beneath each section's title, the current configuration is summarized. Using this you can determine whether you need to visit the section to configure it further. Once all required sections are complete, click the Begin Installation button. Also see Section 8.17, "Begin Installation" . To cancel the installation, click the Quit button. Note When related background tasks are running, certain menu items might be temporarily unavailable. If you used a Kickstart option or a boot command-line option to specify an installation repository on a network, but no network is available at the start of the installation, the installation program will display the configuration screen for you to set up a network connection prior to displaying the Installation Summary screen. Figure 8.5. Network Configuration Screen When No Network Is Detected You can skip this step if you are installing from an installation DVD or other locally accessible media, and you are certain you will not need network to finish the installation. However, network connectivity is necessary for network installations (see Section 8.11, "Installation Source" ) or for setting up advanced storage devices (see Section 8.15, "Storage Devices" ). For more details about configuring a network in the installation program, see Section 8.12, "Network & Hostname" .

Commands:
probe::stap.cache_add_nss Name probe::stap.cache_add_nss - Add NSS (Network Security Services) information to cache Synopsis stap.cache_add_nss Values source_path the path the .sgn file is coming from (incl filename) dest_path the path the .sgn file is coming from (incl filename) Description Fires just before the file is actually moved. Note: stap must compiled with NSS support; if moving the kernel module fails, this probe will not fire.

Commands:
Chapter 1. About Red Hat AMQ 7 Red Hat AMQ provides fast, lightweight, and secure messaging for Internet-scale applications. AMQ Broker supports multiple protocols and fast message persistence. AMQ Interconnect leverages the AMQP protocol to distribute and scale your messaging resources across the network. AMQ Clients provides a suite of messaging APIs for multiple languages and platforms. Think of the AMQ components as tools inside a toolbox. They can be used together or separately to build and maintain your messaging application, and AMQP is the glue in the toolbox that binds them together. AMQ components share a common management console, so you can manage them from a single interface. 1.1. Key features AMQ enables developers to build messaging applications that are fast, reliable, and easy to administer. Messaging at internet scale AMQ contains the tools to build advanced, multi-datacenter messaging networks. It can connect clients, brokers, and stand-alone services in a seamless messaging fabric. Top-tier security and performance AMQ offers modern SSL/TLS encryption and extensible SASL authentication. AMQ delivers fast, high-volume messaging and class-leading JMS performance. Broad platform and language support AMQ works with multiple languages and operating systems, so your diverse application components can communicate. AMQ supports C++, Java, JavaScript, Python, Ruby, and .NET applications, as well as Linux, Windows, and JVM-based environments. Focused on standards AMQ implements the Java JMS 1.1 and 2.0 API specifications. Its components support the ISO-standard AMQP 1.0 and MQTT messaging protocols, as well as STOMP and WebSocket. Centralized management With AMQ, you can administer all AMQ components from a single management interface. You can use JMX or the REST interface to manage servers programmatically.

Commands:
4.140. libnih 4.140.1. RHEA-2011:1672 - libnih enhancement update An updated libnih package that adds one enhancement is now available for Red Hat Enterprise Linux 6. The libnih package includes a small library for C application development. The library is similar to other C libraries, such as glib. Enhancement BZ# 727284 Previously, the libnih package was compiled without the read-only relocations (RELRO) flag. Programs built against the libnih library could be vulnerable to various attacks based on overwriting the ELF section of a program. To enhance the security, the libnih package is now provided with partial RELRO support. All users of libnih are advised to upgrade to this updated package, which adds this enhancement.

Commands:
C.2.2. How Will I Access the Encrypted Devices After Installation? (System Startup) During system startup you will be presented with a passphrase prompt. After the correct passphrase has been provided the system will continue to boot normally. If you used different passphrases for multiple encrypted devices you may need to enter more than one passphrase during the startup. Note Consider using the same passphrase for all encrypted block devices in a given system. This will simplify system startup and you will have fewer passphrases to remember. Just make sure you choose a good passphrase!

Commands:
Chapter 20. Clustering Support for clufter , a tool for transforming and analyzing cluster configuration formats The clufter package, available as a Technology Preview in Red Hat Enterprise Linux 7, provides a tool for transforming and analyzing cluster configuration formats. It can be used to assist with migration from an older stack configuration to a newer configuration that leverages Pacemaker. For information on the capabilities of clufter , see the clufter(1) man page or the output of the clufter -h command.

Commands:
Chapter 2. Installation This chapter guides you through the steps to install Red Hat build of Apache Qpid JMS in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To build programs with Red Hat build of Apache Qpid JMS, you must install Apache Maven . To use Red Hat build of Apache Qpid JMS, you must install Java. 2.2. Using the Red Hat Maven repository Configure your Maven environment to download the client library from the Red Hat Maven repository. Procedure Add the Red Hat repository to your Maven settings or POM file. For example configuration files, see Section B.1, "Using the online repository" . <repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository> Add the library dependency to your POM file. <dependency> <groupId>org.apache.qpid</groupId> <artifactId>qpid-jms-client</artifactId> <version>2.4.0.redhat-00005</version> </dependency> The client is now available in your Maven project. 2.3. Installing a local Maven repository As an alternative to the online repository, Red Hat build of Apache Qpid JMS can be installed to your local filesystem as a file-based Maven repository. Procedure Use your subscription to download the Red Hat build of Apache Qpid JMS 2.4.0 Maven repository .zip file. Extract the file contents into a directory of your choosing. On Linux or UNIX, use the unzip command to extract the file contents. USD unzip amq-clients-2.4.0-maven-repository.zip On Windows, right-click the .zip file and select Extract All . Configure Maven to use the repository in the maven-repository directory inside the extracted install directory. For more information, see Section B.2, "Using a local repository" . 2.4. Installing the examples Procedure Use the git clone command to clone the source repository to a local directory named qpid-jms : USD git clone https://github.com/apache/qpid-jms.git qpid-jms Change to the qpid-jms directory and use the git checkout command to switch to the 2.4.0 branch: USD cd qpid-jms USD git checkout 2.4.0 The resulting local directory is referred to as <source-dir> throughout this document.

Commands:
<repository> <id>red-hat-ga</id> <url>https://maven.repository.redhat.com/ga</url> </repository>
<dependency> <groupId>org.apache.qpid</groupId> <artifactId>qpid-jms-client</artifactId> <version>2.4.0.redhat-00005</version> </dependency>
unzip amq-clients-2.4.0-maven-repository.zip
git clone https://github.com/apache/qpid-jms.git qpid-jms
cd qpid-jms git checkout 2.4.0
C.23. XSiteAdmin org.infinispan.xsite.XSiteAdminOperations The XSiteAdmin component exposes tooling for backing up data to remote sites. Table C.36. Operations Name Description Signature bringSiteOnline Brings the given site back online on all the cluster. String bringSiteOnline(String p0) amendTakeOffline Amends the values for 'TakeOffline' functionality on all the nodes in the cluster. String amendTakeOffline(String p0, int p1, long p2) getTakeOfflineAfterFailures Returns the value of the 'afterFailures' for the 'TakeOffline' functionality. String getTakeOfflineAfterFailures(String p0) getTakeOfflineMinTimeToWait Returns the value of the 'minTimeToWait' for the 'TakeOffline' functionality. String getTakeOfflineMinTimeToWait(String p0) setTakeOfflineAfterFailures Amends the values for 'afterFailures' for the 'TakeOffline' functionality on all the nodes in the cluster. String setTakeOfflineAfterFailures(String p0, int p1) setTakeOfflineMinTimeToWait Amends the values for 'minTimeToWait' for the 'TakeOffline' functionality on all the nodes in the cluster. String setTakeOfflineMinTimeToWait(String p0, long p1) siteStatus Check whether the given backup site is offline or not. String siteStatus(String p0) status Returns the status(offline/online) of all the configured backup sites. String status() takeSiteOffline Takes this site offline in all nodes in the cluster. String takeSiteOffline(String p0) pushState Starts the cross-site state transfer to the site name specified. String pushState(String p0) cancelPushState Cancels the cross-site state transfer to the site name specified. String cancelPushState(String p0) getSendingSiteName Returns the site name that is pushing state to this site. String getSendingSiteName() cancelReceiveState Restores the site to the normal state. It is used when the link between the sites is broken during the state transfer. String cancelReceiveState(String p0) getPushStateStatus Returns the status of completed and running cross-site state transfer. String getPushStateStatus() clearPushStateStatus Clears the status of completed cross-site state transfer. String clearPushStateStatus() 23149%2C+Administration+and+Configuration+Guide-6.628-06-2017+13%3A51%3A02JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands:
4.191. netcf 4.191.1. RHBA-2011:1631 - netcf bug fix and enhancement update Updated netcf packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The netcf packages contain a library for modifying the network configuration of a system. Network configuration is expressed in a platform-independent XML format, which netcf translates into changes to the system's "native" network configuration files. The netcf packages have been upgraded to upstream version 0.1.9, which provides a number of bug fixes and enhancements over the version. Bug Fix BZ# 713286 Prior to this update, certain interfaces associated configuration files in the /etc/sysconfig/network-scripts/ directory, but no corresponding device in the kernel. As a result, netcf returned an error status every time it was asked for the current status of an interface it was unable to find in the kernel, so management applications collected a large number of error log messages. With this update, failures to find an interface in the kernel are now ignored. Enhancements BZ# 616060 In this update, netcf has been modified to capture the stdout and stderr output of ifup and ifdown, and, in the case of an error, forward that information back to the management application, which used netcf to start or stop an interface. This makes it easier to troubleshoot problems. BZ# 708476 Changes made to a host's network configuration by netcf (via netcf's API, or the ncftool commands) immediately and permanently modify the host's configuration files (in /etc/sysconfig/network-scripts/ifcfg-*). With this update, new API/virsh commands have been added to enable saving the current state of network configuration before any changes are made, and easily reverting to that configuration if any problems are encountered. All users are advised to updated to these updated packages, which fix these bugs and add these enhancements.

Commands: