mtpti5iD/redhat-docs_dataset huggingface dataset:
4.4. Special Considerations when Mounting GFS2 File Systems GFS2 file systems that have been mounted manually rather than automatically through an entry in the fstab file will not be known to the system when file systems are unmounted at system shutdown. As a result, the GFS2 script will not unmount the GFS2 file system. After the GFS2 shutdown script is run, the standard shutdown process kills off all remaining user processes, including the cluster infrastructure, and tries to unmount the file system. This unmount will fail without the cluster infrastructure and the system will hang. To prevent the system from hanging when the GFS2 file systems are unmounted, you should do one of the following: Always use an entry in the fstab file to mount the GFS2 file system. If a GFS2 file system has been mounted manually with the mount command, be sure to unmount the file system manually with the umount command before rebooting or shutting down the system. If your file system hangs while it is being unmounted during system shutdown under these circumstances, perform a hardware reboot. It is unlikely that any data will be lost since the file system is synced earlier in the shutdown process.

Commands:
2.8.2.3. Trusted Services Enabling options in the Trusted services list allows the specified service to pass through the firewall. WWW (HTTP) The HTTP protocol is used by Apache (and by other Web servers) to serve web pages. If you plan on making your Web server publicly available, select this check box. This option is not required for viewing pages locally or for developing web pages. This service requires that the httpd package be installed. Enabling WWW (HTTP) will not open a port for HTTPS, the SSL version of HTTP. If this service is required, select the Secure WWW (HTTPS) check box. FTP The FTP protocol is used to transfer files between machines on a network. If you plan on making your FTP server publicly available, select this check box. This service requires that the vsftpd package be installed. SSH Secure Shell (SSH) is a suite of tools for logging into and executing commands on a remote machine. To allow remote access to the machine via SSH, select this check box. This service requires that the openssh-server package be installed. Telnet Telnet is a protocol for logging into remote machines. Telnet communications are unencrypted and provide no security from network snooping. Allowing incoming Telnet access is not recommended. To allow remote access to the machine via telnet, select this check box. This service requires that the telnet-server package be installed. Mail (SMTP) SMTP is a protocol that allows remote hosts to connect directly to your machine to deliver mail. You do not need to enable this service if you collect your mail from your ISP's server using POP3 or IMAP, or if you use a tool such as fetchmail . To allow delivery of mail to your machine, select this check box. Note that an improperly configured SMTP server can allow remote machines to use your server to send spam. NFS4 The Network File System (NFS) is a file sharing protocol commonly used on *NIX systems. Version 4 of this protocol is more secure than its predecessors. If you want to share files or directories on your system with other network users, select this check box. Samba Samba is an implementation of Microsoft's proprietary SMB networking protocol. If you need to share files, directories, or locally-connected printers with Microsoft Windows machines, select this check box.

Commands:
5.201. mrtg 5.201.1. RHBA-2012:1449 - mrtg bug fix update Updated mrtg packages that fix three bugs are now available for Red Hat Enterprise Linux 6. The mrtg packages provide the Multi Router Traffic Grapher (MRTG) to monitor the traffic load on network-links. MRTG generates HTML pages containing Portable Network Graphics (PNG) images, which provide a live, visual representation of this traffic. Bug Fixes BZ# 707188 Prior to this update, the MRTG tool did not handle the socket6 correctly. As a consequence, MRTG reported errors when run on a system with an IPv6 network interface due to a socket conflict. This update modifies the underlying code to socket6 as expected. (#706519) * Prior to this update, changing the "kMG" keyword in the MRTG configuration could cause the labels on the y-axis to overlap the main area of the generated chart. With this update, an upstream patch has been applied to address this issue, and changing the "kMG" keyword in the configuration no longer leads to the incorrect rendering of the resulting charts. BZ# 836197 Prior to this update, the wrong value was returned from the IBM Fibrechannel switch when using the ifSpeed interface. As a consequence, mrtg cfgmaker failed to use ifHighSpeed on IBM FibreChannel switches. This update modifies the underlying code to return the correct value. All users of mrtg are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 153. StrimziPodSetStatus schema reference Used in: StrimziPodSet Property Property type Description conditions Condition array List of status conditions. observedGeneration integer The generation of the CRD that was last reconciled by the operator. pods integer Number of pods managed by this StrimziPodSet resource. readyPods integer Number of pods managed by this StrimziPodSet resource that are ready. currentPods integer Number of pods managed by this StrimziPodSet resource that have the current revision.

Commands:
17.2. Start the Application Server Instances Procedure 17.1. Configure and Start the Servers in standalone mode Prepare an instance of JBoss EAP for copying: Unzip jboss-datagrid-USD{version}-eap-modules-library.zip . Copy the modules to the server modules directory: For Linux: For Windows: Add a user to each server for EJB access: For Linux: EAP_HOME/bin/add-user.sh -a -u quickuser -p quick-123 For Windows: EAP_HOME\bin\add-user.bat -a -u quickuser -p quick-123 Copy the prepared JBoss EAP server to 4 different directories labeled EAP_HOME[1-4]. Open a command line for each of the 4 nodes and navigate to the root of the JBoss EAP server directory. Start all four of the JBoss EAP servers using the following commands: For Linux: For Windows: Add the configuration for node2 (AppOne) to use EJB server-to-server invocation: For Linux: For Windows: Procedure 17.2. Configure and Start the Servers in domain mode Copy a fresh JBoss EAP installation to EAP_HOME: Unzip jboss-datagrid-USD{version}-eap-modules-library.zip . Copy the modules to the server modules directory: For Linux: For Windows: Open a command line and navigate to the root of JBoss EAP. Add a user: For Linux: For Windows: The following shows the command to start the domain: For Linux: For Windows: Apply the configuration for the quickstart, the domain will contain 4 nodes: For Linux: For Windows: Report a bug

Commands:
cp -a jboss-datagrid-USD{version}-eap-modules-library/modules EAP_HOME
xcopy /e/i/f jboss-datagrid-USD{version}-eap-modules-library/modules EAP_HOME\modules
EAP_HOME1/bin/standalone.sh -Djboss.node.name=node1 EAP_HOME2/bin/standalone.sh -Djboss.node.name=node2 -Djboss.socket.binding.port-offset=100 EAP_HOME3/bin/standalone.sh -Djboss.node.name=node3 -Djboss.socket.binding.port-offset=200 -c standalone-ha.xml EAP_HOME4/bin/standalone.sh -Djboss.node.name=node4 -Djboss.socket.binding.port-offset=300 -c standalone-ha.xml
EAP_HOME1\bin\standalone.bat -Djboss.node.name=node1 EAP_HOME2\bin\standalone.bat -Djboss.node.name=node2 -Djboss.socket.binding.port-offset=100 EAP_HOME3\bin\standalone.bat -Djboss.node.name=node3 -Djboss.socket.binding.port-offset=200 -c standalone-ha.xml EAP_HOME4\bin\standalone.bat -Djboss.node.name=node4 -Djboss.socket.binding.port-offset=300 -c standalone-ha.xml
EAP_HOME2/bin/jboss-cli.sh -c --controller=localhost:10099 --file=QUICKSTART_HOME/install-appOne-standalone.cli
EAP_HOME2\bin\jboss-cli.bat -c --controller=localhost:10099 --file=QUICKSTART_HOME/install-appOne-standalone.cli
cp -a jboss-datagrid-USD{version}-eap-modules-library/modules EAP_HOME
xcopy /e/i/f jboss-datagrid-USD{version}-eap-modules-library/modules EAP_HOME\modules
EAP_HOME/bin/add-user.sh -a -u quickuser -p quick-123
EAP_HOME\bin\add-user.bat -a -u quickuser -p quick-123
EAP_HOME/bin/domain.sh
EAP_HOME\bin\domain.bat
EAP_HOME/bin/jboss-cli.sh -c --file=QUICKSTART_HOME/install-domain.cli
EAP_HOME\bin\jboss-cli.bat -c --file=QUICKSTART_HOME/install-domain.cli
Preface Red Hat Enterprise Linux (RHEL) minor releases are an aggregation of individual security, enhancement, and bug fix errata. The Red Hat Enterprise Linux 7.5 Release Notes document describes the major changes made to the Red Hat Enterprise Linux 7 operating system and its accompanying applications for this minor release, as well as known problems and a complete list of all currently available Technology Previews. Capabilities and limits of Red Hat Enterprise Linux 7 as compared to other versions of the system are available in the Red Hat Knowledgebase article available at https://access.redhat.com/articles/rhel-limits . Packages distributed with this release are listed in Red Hat Enterprise Linux 7 Package Manifest . Migration from Red Hat Enterprise Linux 6 is documented in the Migration Planning Guide. For information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands:
Chapter 6. Tokens This tutorial contains information about 3scale tokens: what are they, how they work, and how to create them. 3scale has two types of tokens: Access tokens (created by the user) and Service tokens (automatically created when you create a new service in 3scale). 6.1. Access tokens Access tokens allow application programming interface (API) provider admins and members to authenticate against the 3scale APIs - Billing, Account management, and Analytics - and try them out using our ActiveDocs. An access token may provide either read and write access, or read only. An important thing to take into account is how access tokens work, which is according to the member's rights. Admins can create tokens to authenticate against all three 3scale APIs. Members will be limited by their permissions to access the different parts of the Admin Portal. For example, if a member does not have access to the Billing area, they will not be able to create a token to authenticate against the Billing API. 6.2. Creating access tokens Access tokens can be created on the tokens page. To create tokens, follow these steps: Click on the gear icon in the navigation bar. Navigate to Personal > Tokens . Click Add Access Token . Specify a name, select one or more scopes, and choose the permission for the token. To save the new token, click Create Access token . Note that if you are a member, you might not see all the APIs - just the ones you have been given access to by the admin of your account. You can create as many access tokens as you need. When you create a new token, you will be alerted to save the token so you can then use it to make requests to the 3scale API. If you lose a token, we recommend that you delete it - which will disable it and render it invalid - then create a new one. 6.3. Using access tokens When using your access token to make calls to the 3scale APIs the results will be filtered by the services you have access to. For example, when deploying APIcast self-managed, you will need an access token so your APIcast API gateway can pull the configuration of the service using the Account Management API. The way it works is if your organization has set up three services on 3scale, and as a member, you have access to Service 1, but not 2 and 3, and you also have access to the Account Management API, when you create a token and make a request to the Account Management API you will only get the applications which are using Service 1. Following the same example, if you have access to the Account Management API, but access to zero services, when making a call, you will get an access denied error. 6.3.1. Service tokens Service tokens are used to authenticate against 3scale Service Management API. Service tokens are generated automatically when a new service is created in 3scale, and are unique per service. They are shared among the users of the 3scale account. You can find the service tokens for the services that the user has access to in the Admin Portal's Dashboard: Account Settings (gear icon) > Personal > Tokens .

Commands:
probe::socket.sendmsg.return Name probe::socket.sendmsg.return - Return from socket.sendmsg. Synopsis socket.sendmsg.return Values type Socket type value size Size of message sent (in bytes) or error code if success = 0 flags Socket flags value state Socket state value success Was send successful? (1 = yes, 0 = no) family Protocol family value protocol Protocol value name Name of this probe Context The message sender. Description Fires at the conclusion of sending a message on a socket via the sock_sendmsg function

Commands:
5.4.3. Do Not Use the no_root_squash Option By default, NFS shares change the root user to the nfsnobody user, an unprivileged user account. In this way, all root-created files are owned by nfsnobody , which prevents uploading of programs with the setuid bit set. If no_root_squash is used, remote root users are able to change any file on the shared file system and leave trojaned applications for other users to inadvertently execute.

Commands:
Chapter 15. File Transfer Protocol File Transfer Protocol (FTP) is one of the oldest and most commonly used protocols found on the Internet today. Its purpose is to reliably transfer files between computer hosts on a network without requiring the user to log directly into the remote host or have knowledge of how to use the remote system. It allows users to access files on remote systems using a standard set of simple commands. The Very Secure FTP Daemon ( vsftpd ) is designed from the ground up to be fast, stable, and, most importantly, secure. Its ability to handle large numbers of connections efficiently and securely is why vsftpd is the only stand-alone FTP distributed with Red Hat Enterprise Linux. In Red Hat Enterprise Linux, the vsftpd package provides the Very Secure FTP daemon. Enter the following command to see if vsftpd is installed: If you want an FTP server and the vsftpd package is not installed, use the yum utility as the root user to install it: 15.1. Types The main permission control method used in SELinux targeted policy to provide advanced process isolation is Type Enforcement. All files and processes are labeled with a type: types define a SELinux domain for processes and a SELinux type for files. SELinux policy rules define how types access each other, whether it be a domain accessing a type, or a domain accessing another domain. Access is only allowed if a specific SELinux policy rule exists that allows it. By default, anonymous users have read access to files in the /var/ftp/ directory when they log in using FTP. This directory is labeled with the public_content_t type, allowing only read access, even if write access is configured in /etc/vsftpd/vsftpd.conf . The public_content_t type is accessible to other services, such as Apache HTTP Server, Samba, and NFS. Use one of the following types to share files through FTP: public_content_t Label files and directories you have created with the public_content_t type to share them read-only through vsftpd . Other services, such as Apache HTTP Server, Samba, and NFS, also have access to files labeled with this type. Files labeled with the public_content_t type cannot be written to, even if Linux permissions allow write access. If you require write access, use the public_content_rw_t type. public_content_rw_t Label files and directories you have created with the public_content_rw_t type to share them with read and write permissions through vsftpd . Other services, such as Apache HTTP Server, Samba, and NFS, also have access to files labeled with this type. Remember that Booleans for each service must be enabled before they can write to files labeled with this type.

Commands:
~]USD rpm -q vsftpd package vsftpd is not installed
~]# yum install vsftpd
Chapter 1. Managing your private automation hub container registry Manage container image repositories in your Ansible Automation Platform infrastructure using the automation hub container registry. Automation hub provides features to govern who can access individual container repositories, change tags on images, view activity and image layers, and provide additional information related to each container repository. 1.1. Container registries The automation hub container registry is used for storing and managing container images. Once you have built or sourced a container image, you can push that container image to the registry portion of private automation hub to create a container repository. 1.2. steps Push a container image to the automation hub container registry. Create a group with access to the container repository in the registry. Add the new group to the container repository. Add a README to the container repository to provide users with information and relevant links.

Commands:
Chapter 3. Managing access control instructions in LDAP browser This set of instructions provides you with the basics of managing the access control instructions (ACIs) by using the LDAP browser wizard in the web console. 3.1. Creating an access control instruction in the LDAP browser You can create and add an access control instruction (ACI) for a Red Hat Directory Server (RHDS) entry by using the LDAP Browser in the web console. Prerequisites Access to the web console. A parent entry exists in the Red Hat Directory Server. Procedure Log in to the web console and click Red Hat Directory Server . After the web console loads the Red Hat Directory Server interface, click LDAP browser . Select an LDAP entry and click the Options menu. From the drop-down menu, select ACIs . To create an ACI by using the LDAP browser wizard, you have two options: Click Add ACI Wizard to create the ACI using the wizard. Continue with the step. Click Add ACI Manually , specify the instruction in the text field, and click Save ACI . Follow the steps in the wizard and click the button after you complete each step. To create the ACI, review the data that the wizard generated, and click Add ACI . To close the wizard window, click the Finish button. Verification Verify the new ACI appears in the Manage ACIs window. 3.2. Editing access control instructions in the LDAP Browser You can edit an access control instruction (ACI) for a Red Hat Directory Server entry by using the LDAP Browser Manage ACIs window in the web console. Prerequisites Access to the web console. A parent entry exists in the Red Hat Directory Server. Procedure Log in to the web console and click Red Hat Directory Server . After the web console loads the Red Hat Directory Server interface, click LDAP browser . Select an LDAP entry and click the Options menu. From the drop-down menu select ACIs . Click the Options menu and select Edit ACI . Modify the instruction in the text field and click Save ACI . Verification In the Manage ACIs window expand the ACI you modified and observe your changes. 3.3. Removing an access control instruction in the LDAP browser You can remove an access control instruction (ACI) for a Red Hat Directory Server entry by using the LDAP Browser in the web console. Prerequisites Access to the web console. A parent entry exists in the Red Hat Directory Server. Procedure Log in to the web console and click Red Hat Directory Server . After the web console loads the Red Hat Directory Server interface, click LDAP Browser . Select an LDAP entry and click the Options menu. From the drop-down menu select ACIs to open the Manage ACIs window. Click the Node options icon for the ACI you are removing and select Remove ACI . Select the Yes, I'm sure checkbox and click the Delete ACI button. Verification On the Manage ACIs window, verify the ACI you removed no longer appears on the list of ACIs.

Commands:
1.4. Indexing When indexing is set up, the Query module transparently indexes every added, updated, or removed cache entry. Indices improve performance of queries, though induce additional overhead during updates. For index-less querying see Chapter 6, The Infinispan Query DSL . For data that already exists in the grid, create an initial Lucene index. After relevant properties and annotations are added, trigger an initial batch index as shown in Section 2.4.4, "Rebuilding the Index" . Report a bug 1.4.1. Indexing with Transactional and Non-transactional Caches In Red Hat JBoss Data Grid, the relationship between transactions and indexing is as follows: If the cache is transactional, index updates are applied using a listener after the commit process (after-commit listener). Index update failure does not cause the write to fail. If the cache is not transactional, index updates are applied using a listener that works after the event completes (post-event listener). Index update failure does not cause the write to fail. Report a bug

Commands:
probe::ioscheduler.elv_add_request.tp Name probe::ioscheduler.elv_add_request.tp - tracepoint based probe to indicate a request is added to the request queue. Synopsis ioscheduler.elv_add_request.tp Values q Pointer to request queue. elevator_name The type of I/O elevator currently enabled. name Name of the probe point rq Address of request. disk_major Disk major no of request. disk_minor Disk minor number of request. rq_flags Request flags.

Commands:
6.6. RHEA-2013:0355 - new package: keepalived A new keepalived package is now available as a Technology Preview for Red Hat Enterprise Linux 6. The keepalived package provides simple and robust facilities for load-balancing and high-availability. The load-balancing framework relies on the well-known and widely used Linux Virtual Server kernel module providing Layer4 network load-balancing. The keepalived daemon implements a set of health checkers to load-balanced server pools according their state. The keepalived daemon also implements the Virtual Router Redundancy Protocol (VRRP), allowing router or director failover to achieve high availability. This enhancement update adds the keepalived package to Red Hat Enterprise Linux 6 as a Technology Preview. (BZ#846064) More information about Red Hat Technology Previews is available at https://access.redhat.com/support/offerings/techpreview/ All users who want to use the keepalived Technology Preview should install this newly-released package, which adds this enhancement.

Commands:
8.218. sysvinit 8.218.1. RHBA-2013:1003 - sysvinit bug fix update Updated sysvinit packages that fix one bug are now available for Red Hat Enterprise Linux 6. The sysvinit packages contain a group of processes that control basic functions of your system. SysVinit includes the init program, which is the first program started by the Linux kernel when the system boots. The init program then controls the starting up and shutting down of all other programs. Bug Fix BZ#814132 When the pidof utility was processing the /proc/*/stat file, the content of the file was read by the fgets() function. This function did not behave correctly when the new line character, "\n", was in the name of a process and also when the read file disappeared between the fopen and fgets function. Consequently, the "pidof: could not get program name from" message was emitted in these cases. To fix this problem, the program reads the whole file and silently skips all files with empty content. As a result, binary files containing the new line character with "\n" are now correctly recognized and disappearing files do not emit any warning messages. Users of sysvinit are advised to upgrade to these updated packages, which fix this bug.

Commands: