mtpti5iD/redhat-docs_dataset huggingface dataset:
7.114. libhbalinux 7.114.1. RHBA-2013:0415 - libhbalinux bug fix and enhancement update Updated libhbalinux packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The libhbalinux package contains the Host Bus Adapter API (HBAAPI) vendor library which uses standard kernel interfaces to obtain information about Fiber Channel Host Buses (FC HBA) in the system. Note The libhbalinux packages have been upgraded to upstream version 1.0.14, which provides a number of bug fixes and enhancements over the version. (BZ#819936) All users of libhbalinux are advised to upgrade to these updated libhbalinux packages, which fix these bugs and add these enhancements.

Commands:
2.3. Starting the Piranha Configuration Tool Service After you have set the password for the Piranha Configuration Tool , start or restart the piranha-gui service located in /etc/rc.d/init.d/piranha-gui . To do this, type the following command as root: /sbin/service piranha-gui start or /sbin/service piranha-gui restart Issuing this command starts a private session of the Apache HTTP Server by calling the symbolic link /usr/sbin/piranha_gui -> /usr/sbin/httpd . For security reasons, the piranha-gui version of httpd runs as the piranha user in a separate process. The fact that piranha-gui leverages the httpd service means that: The Apache HTTP Server must be installed on the system. Stopping or restarting the Apache HTTP Server via the service command stops the piranha-gui service. Warning If the command /sbin/service httpd stop or /sbin/service httpd restart is issued on an LVS router, you must start the piranha-gui service by issuing the following command: /sbin/service piranha-gui start The piranha-gui service is all that is necessary to begin configuring LVS. However, if you are configuring LVS remotely, the sshd service is also required. You do not need to start the pulse service until configuration using the Piranha Configuration Tool is complete. See Section 4.8, "Starting LVS" for information on starting the pulse service. 2.3.1. Configuring the Piranha Configuration Tool Web Server Port The Piranha Configuration Tool runs on port 3636 by default. To change this port number, change the line Listen 3636 in Section 2 of the piranha-gui Web server configuration file /etc/sysconfig/ha/conf/httpd.conf . To use the Piranha Configuration Tool you need at minimum a text-only Web browser. If you start a Web browser on the primary LVS router, open the location http:// localhost :3636 . You can reach the Piranha Configuration Tool from anywhere via Web browser by replacing localhost with the hostname or IP address of the primary LVS router. When your browser connects to the Piranha Configuration Tool , you must login to access the configuration services. Enter piranha in the Username field and the password set with piranha-passwd in the Password field. Now that the Piranha Configuration Tool is running, you may wish to consider limiting who has access to the tool over the network. The section reviews ways to accomplish this task.

Commands:
10.6. Reporting the Incident The last part of the incident response plan is reporting the incident. The security team should take notes as the response is happening and report all issues to organizations such as local and federal authorities or multi-vendor software vulnerability portals, such as the Common Vulnerabilities and Exposures site (CVE) at http://cve.mitre.org/ . Depending on the type of legal counsel an enterprise employs, a post-mortem analysis may be required. Even if it is not a functional requirement to a compromise analysis, a post-mortem can prove invaluable in helping to learn how a cracker thinks and how the systems are structured so that future compromises can be prevented.

Commands:
9.3. Managing High-Availability Services You can manage high-availability services using the Cluster Status Utility , clustat , and the Cluster User Service Administration Utility , clusvcadm . clustat displays the status of a cluster and clusvcadm provides the means to manage high-availability services. This section provides basic information about managing HA services using the clustat and clusvcadm commands. It consists of the following subsections: Section 9.3.1, "Displaying HA Service Status with clustat " Section 9.3.2, "Managing HA Services with clusvcadm " 9.3.1. Displaying HA Service Status with clustat clustat displays cluster-wide status. It shows membership information, quorum view, the state of all high-availability services, and indicates which node the clustat command is being run at (Local). Table 9.1, "Services Status" describes the states that services can be in and are displayed when running clustat . Example 9.3, " clustat Display" shows an example of a clustat display. For more detailed information about running the clustat command see the clustat man page. Table 9.1. Services Status Services Status Description Started The service resources are configured and available on the cluster system that owns the service. Recovering The service is pending start on another node. Disabled The service has been disabled, and does not have an assigned owner. A disabled service is never restarted automatically by the cluster. Stopped In the stopped state, the service will be evaluated for starting after the service or node transition. This is a temporary state. You may disable or enable the service from this state. Failed The service is presumed dead. A service is placed into this state whenever a resource's stop operation fails. After a service is placed into this state, you must verify that there are no resources allocated (mounted file systems, for example) prior to issuing a disable request. The only operation that can take place when a service has entered this state is disable . Uninitialized This state can appear in certain cases during startup and running clustat -f . Example 9.3. clustat Display

Commands:
clustat Cluster Status for mycluster @ Wed Nov 17 05:40:15 2010 Member Status: Quorate Member Name ID Status ------ ---- ---- ------ node-03.example.com 3 Online, rgmanager node-02.example.com 2 Online, rgmanager node-01.example.com 1 Online, Local, rgmanager Service Name Owner (Last) State ------- ---- ----- ------ ----- service:example_apache node-01.example.com started service:example_apache2 (none) disabled
Chapter 5. Developer previews This section describes developer preview features introduced in Red Hat OpenShift Data Foundation 4.9. Important Developer preview feature is subject to Developer preview support limitations. Developer preview releases are not intended to be run in production environments. The clusters deployed with the developer preview features are considered to be development clusters and are not supported through the Red Hat Customer Portal case management system. If you need assistance with developer preview features, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on availability and work schedules. Regional-DR with Advanced Cluster Management Regional-DR solution provides an automated "one-click" recovery in the event of a regional disaster. The protected applications are automatically redeployed to a designated OpenShift Container Platform with OpenShift Data Foundation cluster that is available in another region. For more information, see Configuring Regional-DR with Advanced Cluster Management . Quota support for object data You can now set quota options for object bucket claims (OBC) to avoid resource starvation and increase the usage of the product. You set the quota during the OBC creation using the options maxObjects and maxSize in the custom resource definitions (CRD). You can also update these options after the OBC creation. For more information, see https://access.redhat.com/articles/6541861 . IPv6 support With this release, IPv6 single-stack and dual-stack can be used with OpenShift Data Foundation.

Commands:
Chapter 19. Applying security context to Streams for Apache Kafka pods and containers Security context defines constraints on pods and containers. By specifying a security context, pods and containers only have the permissions they need. For example, permissions can control runtime operations or access to resources. 19.1. Handling of security context by OpenShift platform Handling of security context depends on the tooling of the OpenShift platform you are using. For example, OpenShift uses built-in security context constraints (SCCs) to control permissions. SCCs are the settings and strategies that control the security features a pod has access to. By default, OpenShift injects security context configuration automatically. In most cases, this means you don't need to configure security context for the pods and containers created by the Cluster Operator. Although you can still create and manage your own SCCs. For more information, see the OpenShift documentation .

Commands:
2.6.2. Useful Websites http://people.redhat.com/alikins/system_tuning.html -- System Tuning Info for Linux Servers. A stream-of-consciousness approach to performance tuning and resource monitoring for servers. http://www.linuxjournal.com/article.php?sid=2396 -- Performance Monitoring Tools for Linux. This Linux Journal page is geared more toward the administrator interested in writing a customized performance graphing solution. Written several years ago, some of the details may no longer apply, but the overall concept and execution are sound. http://oprofile.sourceforge.net/ -- OProfile project website. Includes valuable OProfile resources, including pointers to mailing lists and the #oprofile IRC channel.

Commands:
19.2. Configure Passivation In Red Hat JBoss Data Grid's Remote Client-Server mode, add the passivation parameter to the cache store element to toggle passivation for it: Example 19.1. Toggle Passivation in Remote Client-Server Mode In Library mode, add the passivation parameter to the persistence element to toggle passivation: Example 19.2. Toggle Passivation in Library Mode Report a bug

Commands:
<local-cache name="customCache"/> <!-- Additional configuration elements here --> <file-store passivation="true" <!-- Additional configuration elements here --> /> <!-- Additional configuration elements here --> </local-cache>
<persistence passivation="true"> <!-- Additional configuration elements here --> </persistence>
Chapter 24. Viewing the history log of a task You can view the history log of a task in Business Central from the Logs tab of task. The history log lists all the events in the "Date Time: Task event" format. Procedure In Business Central, go to Menu Track Task Inbox . On the Task Inbox page, click the task to open it. On the task page, click the Logs tab. All events that take place during the task life cycle is listed in the Logs tab.

Commands:
3.3. Setting User Permissions By default, the root user and any user who is a member of the group haclient has full read/write access to the cluster configuration. As of Red Hat Enterprise Linux 6.6, you can use the pcs acl command to set permission for local users to allow read-only or read-write access to the cluster configuration by using access control lists (ACLs). Setting permissions for local users is a two-step process: Execute the pcs acl role create... command to create a role which defines the permissions for that role. Assign the role you created to a user with the pcs acl user create command. The following example procedure provides read-only access for a cluster configuration to a local user named rouser . This procedure requires that the user rouser exists on the local system and that the user rouser is a member of the group haclient . Enable Pacemaker ACLs with the enable-acl cluster property. Create a role named read-only with read-only permissions for the cib. Create the user rouser in the pcs ACL system and assign that user the read-only role. View the current ACLs. The following example procedure provides write access for a cluster configuration to a local user named wuser . This procedure requires that the user wuser exists on the local system and that the user wuser is a member of the group haclient . Enable Pacemaker ACLs with the enable-acl cluster property. Create a role named write-access with write permissions for the cib. Create the user wuser in the pcs ACL system and assign that user the write-access role. View the current ACLs. For further information about cluster ACLs, see the help screen for the pcs acl command.

Commands:
adduser rouser usermod -a -G haclient rouser
pcs property set enable-acl=true --force
pcs acl role create read-only description="Read access to cluster" read xpath /cib
pcs acl user create rouser read-only
pcs acl User: rouser Roles: read-only Role: read-only Description: Read access to cluster Permission: read xpath /cib (read-only-read)
adduser wuser usermod -a -G haclient wuser
pcs property set enable-acl=true --force
pcs acl role create write-access description="Full access" write xpath /cib
pcs acl user create wuser write-access
pcs acl User: rouser Roles: read-only User: wuser Roles: write-access Role: read-only Description: Read access to cluster Permission: read xpath /cib (read-only-read) Role: write-access Description: Full Access Permission: write xpath /cib (write-access-write)
Chapter 9. Additional resources Installation Installing and configuring Red Hat Decision Manager on Red Hat JBoss EAP 7.4 Installing and configuring Red Hat Decision Manager in a Red Hat JBoss EAP clustered environment Installing and configuring Red Hat Decision Manager on Red Hat JBoss Web Server Installing and configuring KIE Server on IBM WebSphere Application Server Installing and configuring KIE Server on Oracle WebLogic Server Integration Creating Red Hat Decision Manager business applications with Spring Boot Integrating Red Hat Fuse with Red Hat Decision Manager Integrating Red Hat Decision Manager with Red Hat Single Sign-On Red Hat build of OptaPlanner Developing Solvers with Red Hat Decision Manager OpenShift Deploying an Red Hat Decision Manager environment on Red Hat OpenShift Container Platform 4 using Operators Deploying an Red Hat Decision Manager environment on Red Hat OpenShift Container Platform 3 using templates

Commands:
Chapter 1. General Introduction to Virtualization 1.1. What is Virtualization? Virtualization is a broad computing term used for running software, usually multiple operating systems, concurrently and in isolation from other programs on a single system. Virtualization is accomplished by using a hypervisor . This is a software layer or subsystem that controls hardware and enables running multiple operating systems, called virtual machines (VMs) or guests , on a single (usually physical) machine. This machine with its operating system is called a host . For more information, see the Red Hat Customer Portal . There are several virtualization methods: Full virtualization Full virtualization uses an unmodified version of the guest operating system. The guest addresses the host's CPU via a channel created by the hypervisor. Because the guest communicates directly with the CPU, this is the fastest virtualization method. Paravirtualization Paravirtualization uses a modified guest operating system. The guest communicates with the hypervisor. The hypervisor passes the unmodified calls from the guest to the CPU and other interfaces, both real and virtual. Because the calls are routed through the hypervisor, this method is slower than full virtualization. Software virtualization (or emulation) Software virtualization uses binary translation and other emulation techniques to run unmodified operating systems. The hypervisor translates the guest calls to a format that can be used by the host system. Because all calls are translated, this method is slower than virtualization. Note that Red Hat does not support software virtualization on Red Hat Enterprise Linux. Containerization While KVM virtualization creates a separate instance of OS kernel, operating-system-level virtualization, also known as containerization , operates on top of an existing OS kernel and creates isolated instances of the host OS, known as containers . For more information on containers, see the Red Hat Customer Portal . Containers do not have the versatility of KVM virtualization, but are more lightweight and flexible to handle. For a more detailed comparison, see the Introduction to Linux Containers . To use containers on Red Hat Enterprise Linux, install the docker packages from the Extras channel . Note that Red Hat also offers optimized solutions for using containers, such as Red Hat Enterprise Linux Atomic Host and Red Hat OpenShift Container Platform . For details on container support, see the Red Hat KnowledgeBase .

Commands:
function::ustack Name function::ustack - Return address at given depth of user stack backtrace Synopsis Arguments n number of levels to descend in the stack. Description Performs a simple (user space) backtrace, and returns the element at the specified position. The results of the backtrace itself are cached, so that the backtrace computation is performed at most once no matter how many times ustack is called, or in what order.

Commands:
ustack:long(n:long)
17.3.4. Other Partitioning Problems for IBM Power Systems Users If you create partitions manually, but cannot move to the screen, you probably have not created all the partitions necessary for installation to proceed. You must have the following partitions as a bare minimum: A / (root) partition A <swap> partition of type swap A PReP Boot partition. A /boot/ partition. Refer to Section 16.17.5, "Recommended Partitioning Scheme" for more information. Note When defining a partition's type as swap, do not assign it a mount point. Anaconda automatically assigns the mount point for you.

Commands:
2.5. Installing from a PXE Server To boot your computer using a PXE server, you need a properly configured server and a network interface in your computer that supports PXE. Configure the computer to boot from the network interface. This option is in the BIOS, and may be labeled Network Boot or Boot Services . Once you properly configure PXE booting, the computer can boot the Red Hat Gluster Storage Server installation system without any other media. To boot a computer from a PXE server: Ensure that the network cable is attached. The link indicator light on the network socket should be lit, even if the computer is not switched on. Switch on the computer. A menu screen appears. Press the number key that corresponds to the preferred option. If your computer does not boot from the netboot server, ensure that the BIOS is configured so that the computer boots first from the correct network interface. Some BIOS systems specify the network interface as a possible boot device, but do not support the PXE standard. See your hardware documentation for more information.

Commands:
17.3.3. Trouble with Partition Tables If you receive an error after the Disk Partitioning Setup ( Section 16.15, "Disk Partitioning Setup" ) phase of the installation saying something similar to The partition table on device hda was unreadable. To create new partitions it must be initialized, causing the loss of ALL DATA on this drive. you may not have a partition table on that drive or the partition table on the drive may not be recognizable by the partitioning software used in the installation program. No matter what type of installation you are performing, backups of the existing data on your systems should always be made.

Commands:
Technical Notes Red Hat Virtualization 4.4 Technical notes for Red Hat Virtualization 4.4 and associated packages Red Hat Virtualization Documentation Team Red Hat Customer Content Services rhev-docs@redhat.com Abstract The Technical Notes document provides information about changes made between release 4.3 and release 4.4 of Red Hat Virtualization. This document is intended to supplement the information contained in the text of the relevant errata advisories available through the Content Delivery Network.

Commands:
Chapter 3. Configuring Visual Studio Code to use Dependency Analytics You can gain access to Red Hat's Trusted Profile Analyzer service by using the Dependency Analytics extension for Microsoft's Visual Studio Code (VS Code) editor application. With this extension you get access to the latest open source vulnerability information, and insights about your application's dependent packages. The Red Hat Dependency Analytics extension uses the following data sources for the most up-to-date vulnerability information available: The ONGuard service, integrates the Open Source Vulnerability (OSV) and the National Vulnerability Database (NVD) data sources. When given a set of packages to the ONGuard service, a query to OSV retrieves the associated vulnerability information, and then a query to NVD for public Common Vulnerability and Exposures (CVE) information. Dependency Analytics supports the following programming languages: Maven Node Python Go Important Visual Studio Code by default, executes binaries directly in a terminal found in your system's PATH environment. You can configure Visual Studio Code to look somewhere else to run the necessary binaries. You can configure this by accessing the extension settings . Click the Workspace tab, search for the word executable , and specify the absolute path to the binary file you want to use for Maven, Node, Python, or Go. Note The Dependency Analytics extension is an online service maintained by Red Hat. Dependency Analytics only accesses your manifest files to analyze your application dependencies before displaying the results. Prerequisites Install Visual Studio Code on your workstation. For Maven projects, analyzing a pom.xml file, you must have the mvn binary in your system's PATH environment. For Node projects, analyzing a package.json file, you must have the npm binary in your system's PATH environment. For Go projects, analyzing a go.mod file, you must have the go binary in your system's PATH environment. For Python projects, analyzing a requirements.txt file, you must have the python3/pip3 or python/pip binaries in your system's PATH environment. Also, the Python application needs to be in VS Code's interpreter path . Procedure Open the Visual Studio Code application. From the file menu, click View , and click Extensions . Search the Marketplace for Red Hat Dependency Analytics . Click the Install button to install the extension. Wait for the installation to finish. To start scanning your application for security vulnerabilities, and view the vulnerability report, you can do one of the following: Open a manifest file, hover over a dependency marked by the inline Component Analysis, indicated by the wavy-red line under a dependency name, click Quick Fix , and click Detailed Vulnerability Report . Open a manifest file, and click the pie chart icon. Right click on a manifest file in the Explorer view, and click Red Hat Dependency Analytics Report... . From the vulnerability pop-up alert message, click Open detailed vulnerability report . Additional resources Red Hat Dependency Analytics Visual Studio marketplace page . The GitHub project .

Commands: