mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 7. Deleting a container repository Delete a container repository from your local automation hub to manage your disk space. You can delete repositories from the Red Hat Ansible Automation Platform interface in the Container Repository list view. 7.1. Deleting a container repository Prerequisites You have permissions to manage repositories. Procedure Navigate to Execution Environments . On the container repository you would like to delete, click , then click Delete . When presented with the confirmation message, click the checkbox, then click Delete . Verification Return to the Execution Environments list view. The container repository should be removed from the list.

Commands:
5.2.3. OProfile Documentation For more extensive information on OProfile , see the oprofile (1) manual page. Red Hat Enterprise Linux also provides two comprehensive guides to OProfile in file:///usr/share/doc/oprofile- version / : OProfile Manual A comprehensive manual with detailed instructions on the setup and use of OProfile is found at file:///usr/share/doc/oprofile- version /oprofile.html OProfile Internals Documentation on the internal workings of OProfile , useful for programmers interested in contributing to the OProfile upstream, can be found at file:///usr/share/doc/oprofile- version /internals.html

Commands:
7.88. irqbalance 7.88.1. RHBA-2015:1279 - irqbalance bug fix and enhancement update Updated irqbalance packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The irqbalance packages provide a daemon that evenly distributes the interrupt request (IRQ) load across multiple CPUs for enhanced performance. Note The irqbalance packages have been upgraded to upstream version 1.0.7, which provides a number of bug fixes and enhancements over the version. Notably, irqbalance now works with Xen PV guest, broken deepest cache backport has been fixed, and the IRQ migration algorithm has been enhanced. (BZ# 1181720 ) Bug Fixes BZ# 1158932 Previously, the irqbalance utility did not set signal handlers for particular signals. Consequently, when irqbalance received a signal other than SIGINT or SIGHUP, it terminated without a cleanup. This update provides signal handlers for SIGUSR1, SIGUSR2, and SIGTERM. As a result, irqbalance now stops gracefully after finishing the current balancing iteration. BZ# 1178247 Prior to this update, the /sys/bus/pci/devices file handle was not freed properly if the directory was not available. As a consequence, a memory leak occurred. With this update, the file handle is freed as expected when irqbalance cannot open the directory, and memory leaks no longer occur in the described situation. Users of irqbalance are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
5.3.5. Making a File System and Mounting the New Logical Volume You can make a file system on the new logical volume and mount it.

Commands:
gfs_mkfs -plock_nolock -j 1 /dev/yourvg/yourlv This will destroy any data on /dev/yourvg/yourlv. Are you sure you want to proceed? [y/n] y Device: /dev/yourvg/yourlv Blocksize: 4096 Filesystem Size: 1277816 Journals: 1 Resource Groups: 20 Locking Protocol: lock_nolock Lock Table: Syncing All Done mount /dev/yourvg/yourlv /mnt
Chapter 2. Streams for Apache Kafka installation methods You can install Streams for Apache Kafka on OpenShift 4.12 to 4.16 in two ways. Installation method Description Installation artifacts (YAML files) Download Red Hat Streams for Apache Kafka 2.7 OpenShift Installation and Example Files from the Streams for Apache Kafka software downloads page . Deploy the YAML installation artifacts to your OpenShift cluster using oc . You start by deploying the Cluster Operator from install/cluster-operator to a single namespace, multiple namespaces, or all namespaces. You can also use the install/ artifacts to deploy the following: Streams for Apache Kafka administrator roles ( strimzi-admin ) A standalone Topic Operator ( topic-operator ) A standalone User Operator ( user-operator ) Streams for Apache Kafka Drain Cleaner ( drain-cleaner ) OperatorHub Use the Streams for Apache Kafka operator in the OperatorHub to deploy Streams for Apache Kafka to a single namespace or all namespaces. For the greatest flexibility, choose the installation artifacts method. The OperatorHub method provides a standard configuration and allows you to take advantage of automatic updates. Note Installation of Streams for Apache Kafka using Helm is not supported.

Commands:
B.2. iSCSI Disks During Start Up ISCSI-related events might occur at a number of points while the system starts: The init script in the initrd will log in to iSCSI targets used for / (if any). This is done using the iscsistart utility (which can do this without requiring iscsid to run). When the root filesystem has been mounted and the various service initscripts get run, the iscsid initscript will get called. This script will then start iscsid if any iSCSI targets are used for / , or if any targets in the iSCSI database are marked to be logged in to automatically. After the classic network service script has been run (or would have been run if enabled) the iscsi initscript will run. If the network is accessible, this will log in to any targets in the iSCSI database which are marked to be logged in to automatically. If the network is not accessible, this script will exit quietly. When using NetworkManager to access the network (instead of the classic network service script), NetworkManager will call the iscsi initscript. See: /etc/NetworkManager/dispatcher.d/04-iscsi Important Because NetworkManager is installed in /usr , you cannot use it to configure network access if /usr is on network-attached storage such as an iSCSI target. If iscsid is not needed as the system starts, it will not start automatically. If you start iscsiadm , iscsiadm will start iscsid in turn.

Commands:
Chapter 5. Basic System Recovery When things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter describes how to boot into rescue mode, single-user mode, and emergency mode, where you can use your own knowledge to repair the system. 5.1. Common Problems You might need to boot into one of these recovery modes for any of the following reasons: You are unable to boot normally into Red Hat Enterprise Linux (runlevel 3 or 5). You are having hardware or software problems, and you want to get a few important files off of your system's hard drive. You forgot the root password. 5.1.1. Unable to Boot into Red Hat Enterprise Linux This problem is often caused by the installation of another operating system after you have installed Red Hat Enterprise Linux. Some other operating systems assume that you have no other operating system(s) on your computer. They overwrite the Master Boot Record (MBR) that originally contained the GRUB boot loader. If the boot loader is overwritten in this manner, you cannot boot Red Hat Enterprise Linux unless you can get into rescue mode and reconfigure the boot loader. Another common problem occurs when using a partitioning tool to resize a partition or create a new partition from free space after installation, and it changes the order of your partitions. If the partition number of your / partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, boot in rescue mode and modify the /boot/grub/grub.conf file. For instructions on how to reinstall the GRUB boot loader from a rescue environment, refer to Section 5.2.1, "Reinstalling the Boot Loader" . 5.1.2. Hardware/Software Problems This category includes a wide variety of different situations. Two examples include failing hard drives and specifying an invalid root device or kernel in the boot loader configuration file. If either of these occur, you might not be able to reboot into Red Hat Enterprise Linux. However, if you boot into one of the system recovery modes, you might be able to resolve the problem or at least get copies of your most important files. 5.1.3. Root Password What can you do if you forget your root password? To reset it to a different password, boot into rescue mode or single-user mode, and use the passwd command to reset the root password.

Commands:
Chapter 9. Importing and deploying business assets projects in Business Central You can import a business assets project that is part of a Red Hat Process Automation Manager business application into Business Central and then deploy that project to a business application. Prerequisites You have a business application project running in development mode. Red Hat Process Automation Manager Business Central is installed. Procedure Navigate to the <BUSINESS-APPLICATION>/<BUSINESS-APPLICATION>-kjar folder, where <BUSINESS-APPLICATION> is the name of your Spring Boot project. Execute the following following commands to initialize the Git repository for your project: Log in to Business Central and go to Menu Design Projects . Select Import Project and enter the following URL: Click Import and confirm the project to be imported. After the business assets project is imported into Business Central, open the project and click Add Assets to add assets such as business processes to your business assets project. Click Deploy on your project page to deploy your project to a running business application. Note You can also select the Build & Install option to build the project and publish the KJAR file to the configured Maven repository without deploying to a KIE Server. In a development environment, you can click Deploy to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option is disabled and you can click Deploy only to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a corresponding project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode. To review project deployment details, click View deployment details in the deployment banner at the top of the screen or in the Deploy drop-down menu. This option directs you to the Menu Deploy Execution Servers page. To interact with your newly deployed business assets, go to Menu Manage Process Definitions and Process Instances .

Commands:
git init git add -A git commit -m "Initial project structure"
file:///<business-application-path>/<business-application-name>-kjar
3.5. Setting the Signing Algorithms for Certificates The CA's signing certificate can sign the certificates it issues with any public key algorithm supported by the CA. For example, an ECC signing certificate can sign both ECC and RSA certificate requests as long as both ECC and RSA algorithms are supported by the CA. An RSA signing certificate can can sign a PKCS #10 request with EC keys, but may not be able to sign CRMF certificate requests with EC keys if the ECC module is not available for the CA to verify the CRMF proof of possession (POP). ECC and RSA are public key encryption and signing algorithms. Both public key algorithms support different cipher suites, algorithms used to encrypt and decrypt data. Part of the function of the CA signing certificate is to issue and sign certificates using one of its supported cipher suites. Each profile can define which cipher suite the CA should use to sign certificates processed through that profile. If no signing algorithm is set, then the profile uses whatever the default signing algorithm is. 3.5.1. Setting the CA's Default Signing Algorithm Open the CA console. In the Configuration tab, expand the Certificate Manager tree. In the General Settings tab, set the algorithm to use in the Algorithm drop-down menu. Note pkiconsole is being deprecated. 3.5.2. Setting the Signing Algorithm Default in a Profile Each profile has a Signing Algorithm Default extension defined. The default has two settings: a default algorithm and a list of allowed algorithms, if the certificate request specifies a different algorithm. If no signing algorithms are specified, then the profile uses whatever is set as the default for the CA. In the profile's .cfg file, the algorithm is set with two parameters: To configure the Signing Algorithm Default through the console: Note Before a profile can be edited, it must first be disabled by an agent. Open the CA console. In the Configuration tab, expand the Certificate Manager tree. Click the Certificate Profiles item. Click the Policies tab. Select the Signing Alg policy, and click the Edit button. To set the default signing algorithm, set the value in the Defaults tab. If this is set to - , then the profile uses the CA's default. To set a list of allowed signing algorithms which can be accepted in a certificate request, open the Constraints tab, and set the list of algorithms in the Value field for signingAlgsAllowed . The possible values for the constraint are listed in Section B.2.10, "Signing Algorithm Constraint" . Note pkiconsole is being deprecated.

Commands:
pkiconsole https://server.example.com:8443/ca
policyset.cmcUserCertSet.8.constraint.class_id=signingAlgConstraintImpl policyset.cmcUserCertSet.8.constraint.name=No Constraint policyset.cmcUserCertSet.8.constraint.params.signingAlgsAllowed=SHA256withRSA,SHA512withRSA,SHA256withEC,SHA384withRSA,SHA384withEC,SHA512withEC policyset.cmcUserCertSet.8.default.class_id=signingAlgDefaultImpl policyset.cmcUserCertSet.8.default.name=Signing Alg policyset.cmcUserCertSet.8.default.params.signingAlg=-
pkiconsole https://server.example.com:8443/ca
13.2.3. Starting and Stopping SSSD Important Configure at least one domain before starting SSSD for the first time. See Section 13.2.10, "SSSD and Identity Providers (Domains)" . Either the service command or the /etc/init.d/sssd script can start SSSD. For example: By default, SSSD is not configured to start automatically. There are two ways to change this behavior: Enabling SSSD through the authconfig command: Adding the SSSD process to the start list using the chkconfig command:

Commands:
~]# service sssd start
~]# authconfig --enablesssd --enablesssdauth --update
~]# chkconfig sssd on
8.56. fence-virt 8.56.1. RHBA-2014:1589 - fence-virt bug fix and enhancement update Updated fence-virt packages that fix two bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The fence-virt packages provide a fencing agent for virtual machines as well as a host agent, which processes fencing requests. Bug Fixes BZ# 1014238 Previously, the manual page for the fence_virt.conf file did not describe the relationship between socket path for fence_virtd and virtual machine serial socket path. This could cause confusions or misunderstandings. With this update, the description of "path" in the manual page has been extended to explain the aforementioned difference. BZ# 1104740 Prior to this update, the fence-virt agent could not fence inactive virtual machines. As a consequence, the cluster became unresponsive because the fence_virtd daemon was unable to find the running domain. The underlying source code has been patched, and fence-virt now fences both active and inactive virtual machines. In addition, this update adds the following Enhancements BZ# 914144 With this update, the libvirt backend of the fence_virt daemon has been extended to support multiple KVM hypervisors. BZ# 1054225 With this update, fence-virt fencing using KVM serial ports instead of network multicast is supported for production use. Users of fence-virt are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
C.11. Invalidation org.infinispan.interceptors.InvalidationInterceptor The Invalidation component invalidates entries on remote caches when entries are written locally. Table C.19. Attributes Name Description Type Writable invalidations Number of invalidations. long No statisticsEnabled Enables or disables the gathering of statistics by this component. boolean Yes Table C.20. 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:
Chapter 5. Application Properties Configure your project with application.properties or application.yaml . # # Embedded Properties - Uncomment properties to use them. # # Enables embedded capabilities in your application. # Values are true (default) or false. #infinispan.embedded.enabled = # Sets the Spring state machine ID. #infinispan.embedded.machineId = # Sets the name of the embedded cluster. #infinispan.embedded.clusterName = # Specifies a XML configuration file that takes priority over the global # configuration bean or any configuration customizer. #infinispan.embedded.configXml = # # Server Properties - Uncomment properties to use them. # # Specifies a custom filename for Hot Rod client properties. #infinispan.remote.clientProperties = # Enables remote server connections. # Values are true (default) or false. #infinispan.remote.enabled = # Defines a comma-separated list of servers in this format: # `host1[:port],host2[:port]`. #infinispan.remote.server-list= # Sets a timeout value, in milliseconds, for socket connections. #infinispan.remote.socketTimeout = # Sets a timeout value for initializing connections with servers. #infinispan.remote.connectTimeout = # Sets the maximum number of attempts to connect to servers. #infinispan.remote.maxRetries = # Specifies the marshaller to use. #infinispan.remote.marshaller = # Adds your classes to the serialization allow list. #infinispan.remote.java-serial-allowlist=

Commands:
# Embedded Properties - Uncomment properties to use them. # Enables embedded capabilities in your application. Values are true (default) or false. #infinispan.embedded.enabled = Sets the Spring state machine ID. #infinispan.embedded.machineId = Sets the name of the embedded cluster. #infinispan.embedded.clusterName = Specifies a XML configuration file that takes priority over the global configuration bean or any configuration customizer. #infinispan.embedded.configXml = # Server Properties - Uncomment properties to use them. # Specifies a custom filename for Hot Rod client properties. #infinispan.remote.clientProperties = Enables remote server connections. Values are true (default) or false. #infinispan.remote.enabled = Defines a comma-separated list of servers in this format: `host1[:port],host2[:port]`. #infinispan.remote.server-list= Sets a timeout value, in milliseconds, for socket connections. #infinispan.remote.socketTimeout = Sets a timeout value for initializing connections with servers. #infinispan.remote.connectTimeout = Sets the maximum number of attempts to connect to servers. #infinispan.remote.maxRetries = Specifies the marshaller to use. #infinispan.remote.marshaller = Adds your classes to the serialization allow list. #infinispan.remote.java-serial-allowlist=
probe::signal.send_sig_queue Name probe::signal.send_sig_queue - Queuing a signal to a process Synopsis Values sigqueue_addr The address of the signal queue name Name of the probe point sig_name A string representation of the signal sig The queued signal pid_name Name of the process to which the signal is queued sig_pid The PID of the process to which the signal is queued

Commands:
signal.send_sig_queue
Appendix A. Revision History Revision 7-6.1, Tue Oct 30 2018, Vladimir Slavik Build for 7.6 GA release. Revision 7-6, Tue Aug 21 2018, Vladimir Slavik Build for 7.6 Beta release. Revision 7-5.1, Tue Apr 10 2018, Vladimir Slavik Build for the 7.5 GA release. Revision 7-5, Tue Jan 9 2018, Vladimir Slavik Published preview of new book version for 7.5 Beta Revision 7-4.1, Tue Aug 22 2017, Vladimir Slavik Update for new releases of linked products. Revision 7-4, Wed Jul 26 2017, Vladimir Slavik Build for 7.4 GA release. New chapter about setting up a workstation for development. Revision 1-12, Fri May 26 2017, Vladimir Slavik Update to remove outdated information. Revision 7-3.9, Mon May 15 2017, Robert Kratky Build for 7.4 Beta release.

Commands:
28.4.8. Uploading and Reporting Using a Proxy Server The reporter-bugzilla and the reporter-upload tools respect the http_proxy and the ftp_proxy environment variables. When you use environment variables as a part of a reporting event, they inherit their values from the process which performs reporting, usually abrt-gui or abrt-cli . Therefore, you can specify HTTP or FTP proxy servers by using these variables in your working environment. If you arrange these tools to be a part of the post-create event, they will run as children of the abrtd process. You should either adjust the environment of abrtd or modify the rules to set these variables. For example: EVENT=post-create analyzer=Python test -f component || abrt-action-save-package-data export http_proxy=http://proxy.server:8888/ reporter-bugzilla -c /etc/abrt/plugins/bugzilla.conf

Commands:
EVENT=post-create analyzer=Python test -f component || abrt-action-save-package-data export http_proxy=http://proxy.server:8888/ reporter-bugzilla -c /etc/abrt/plugins/bugzilla.conf