mtpti5iD/redhat-docs_dataset huggingface dataset:
2.6.2.2.3. Shell Commands Option fields allow access rules to launch shell commands through the following two directives: spawn - Launches a shell command as a child process. This directive can perform tasks like using /usr/sbin/safe_finger to get more information about the requesting client or create special log files using the echo command. In the following example, clients attempting to access Telnet services from the example.com domain are quietly logged to a special file: twist - Replaces the requested service with the specified command. This directive is often used to set up traps for intruders (also called "honey pots"). It can also be used to send messages to connecting clients. The twist directive must occur at the end of the rule line. In the following example, clients attempting to access FTP services from the example.com domain are sent a message using the echo command: For more information about shell command options, see the hosts_options man page.

Commands:
in.telnetd : .example.com : spawn /bin/echo `/bin/date` from %h>>/var/log/telnet.log : allow
vsftpd : .example.com : twist /bin/echo "421 This domain has been black-listed. Access denied!"
5.293. sblim-cim-client2 5.293.1. RHSA-2012:0987 - Low: sblim-cim-client2 security update Updated sblim-cim-client2 packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The SBLIM (Standards-Based Linux Instrumentation for Manageability) CIM (Common Information Model) Client is a class library for Java applications that provides access to CIM servers using the CIM Operations over HTTP protocol defined by the DMTF (Distributed Management Task Force) standards. Security Fix CVE-2012-2328 It was found that the Java HashMap implementation was susceptible to predictable hash collisions. SBLIM uses HashMap when parsing XML inputs. A specially-crafted CIM-XML message from a WBEM (Web-Based Enterprise Management) server could cause a SBLIM client to use an excessive amount of CPU. Randomization has been added to help avoid collisions. All users of sblim-cim-client2 are advised to upgrade to these updated packages, which contain a backported patch to resolve this issue.

Commands:
Chapter 16. Upgrading RHUI Red Hat recommends that you keep RHUI up to date. Only the latest released version is supported. See the list of released advisories on the Red Hat Update Infrastructure product page . For information on how to keep RHUI up to date, see Upgrading Red Hat Update Infrastructure . 16.1. Preserving Custom Configuration After RHUI Upgrade If you modify the rhui-tools.conf file after RHUI installation, these changes will be reset to default when you update RHUI. To ensure your changes persist after an upgrade, create the /root/.rhui/rhui-tools-custom.conf file. Any sections specified in this file will override the default configuration. Example: Custom Synchronization Policies The following example demonstrates how to define custom synchronization policies in /root/.rhui/rhui-tools-custom.conf :

Commands:
The sync policy can be either "immediate" or "on_demand" default_sync_policy: on_demand
13.4. Resizing a Partition Warning Do not attempt to resize a partition on a device that is in use. Procedure 13.4. Resize a partition Before resizing a partition, boot into rescue mode (or unmount any partitions on the device and turn off any swap space on the device). Start parted , where /dev/ sda is the device on which to resize the partition: View the current partition table to determine the minor number of the partition to resize as well as the start and end points for the partition: To resize the partition, use the resize command followed by the minor number for the partition, the starting place in megabytes, and the end place in megabytes. Example 13.2. Resize a partition For example: resize 3 1024 2048 Warning A partition cannot be made larger than the space available on the device After resizing the partition, use the print command to confirm that the partition has been resized correctly, is the correct partition type, and is the correct file system type. After rebooting the system into normal mode, use the command df to make sure the partition was mounted and is recognized with the new size.

Commands:
parted /dev/ sda
print
Chapter 16. Upgrading the Red Hat build of Keycloak Client Libraries The client libraries are those artifacts: Java admin client - Maven artifact org.keycloak:keycloak-admin-client Java authorization client - Maven artifact org.keycloak:keycloak-authz-client Java policy enforcer - Maven artifact org.keycloak:keycloak-policy-enforcer Java common classes used by other client libraries above - Maven artifact org.keycloak:keycloak-client-common-synced The client libraries are supported with all the supported Red Hat build of Keycloak server versions. The fact that client libraries are supported with more server versions makes the update easier, so you may not need to update the server at the same time when you update client libraries of your application. It is possible that client libraries may work even with the older releases of the Red Hat build of Keycloak server, but it is not guaranteed and officially supported. It may be needed to consult the javadoc of the client libraries like Java admin-client to see what endpoints and parameters are supported with which Red Hat build of Keycloak server version.

Commands:
Chapter 5. Updating your Red Hat Enterprise Linux system prior to the setup Before you install RHUI, it is a good practice to secure your system by installing all the latest available updates. Prerequisites Ensure that the system is registered to Red Hat. All the relevant repositories are enabled. Procedure Apply any available operating system update to each of your nodes. For more information, see How do I apply package updates to my RHEL system? . If necessary, reboot the nodes. The command to check this is: needs-restarting -r Note This command is part of the yum-utils package, which must be installed on each system for the command to be available. Note The procedure above only applies to the initial setup, before RHUI is installed. For information on how to keep an existing installation of RHUI up to date, see Upgrading Red Hat Update Infrastructure .

Commands:
Chapter 5. Technology Previews Technology Preview features included with AMQ Streams 2.5. Important Technology Preview features are not supported with Red Hat production service-level agreements (SLAs) and might not be functionally complete; therefore, Red Hat does not recommend implementing any Technology Preview features in production environments. This Technology Preview feature provides early access to upcoming product innovations, enabling you to test functionality and provide feedback during the development process. For more information about the support scope, see Technology Preview Features Support Scope . 5.1. Kafka Static Quota plugin configuration Use the technology preview of the Kafka Static Quota plugin to set throughput and storage limits on brokers in your Kafka cluster. You enable the plugin and set limits by configuring the Kafka resource. You can set a byte-rate threshold and storage quotas to put limits on the clients interacting with your brokers. Example Kafka Static Quota plugin configuration apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster spec: kafka: # ... config: client.quota.callback.class: io.strimzi.kafka.quotas.StaticQuotaCallback client.quota.callback.static.produce: 1000000 client.quota.callback.static.fetch: 1000000 client.quota.callback.static.storage.soft: 400000000000 client.quota.callback.static.storage.hard: 500000000000 client.quota.callback.static.storage.check-interval: 5 See Setting limits on brokers using the Kafka Static Quota plugin .

Commands:
apiVersion: kafka.strimzi.io/v1beta2 kind: Kafka metadata: name: my-cluster spec: kafka: # config: client.quota.callback.class: io.strimzi.kafka.quotas.StaticQuotaCallback client.quota.callback.static.produce: 1000000 client.quota.callback.static.fetch: 1000000 client.quota.callback.static.storage.soft: 400000000000 client.quota.callback.static.storage.hard: 500000000000 client.quota.callback.static.storage.check-interval: 5
C.3.2. The xorg.conf.d Directory The X server supports two configuration directories. The /usr/share/X11/xorg.conf.d/ provides separate configuration files from vendors or third-party packages; changes to files in this directory may be overwritten by settings specified in the /etc/X11/xorg.conf file. The /etc/X11/xorg.conf.d/ directory stores user-specific configuration. Files with the suffix .conf in configuration directories are parsed by the X server upon startup and are treated like part of the traditional xorg.conf configuration file. These files may contain one or more sections; for a description of the options in a section and the general layout of the configuration file, see Section C.3.3, "The xorg.conf File" or to the xorg.conf(5) man page. The X server essentially treats the collection of configuration files as one big file with entries from xorg.conf at the end. Users are encouraged to put custom configuration into /etc/xorg.conf and leave the directory for configuration snippets provided by the distribution.

Commands:
Chapter 9. Reporting on user access on hosts using SSSD The Security System Services Daemon (SSSD) tracks which users can or cannot access clients. This chapter describes creating access control reports and displaying user data using the sssctl tool. Prerequisites SSSD packages are installed in your network environment 9.1. The sssctl command sssctl is a command-line tool that provides a unified way to obtain information about the Security System Services Daemon (SSSD) status. You can use the sssctl utility to gather information about: Domain state Client user authentication User access on clients of a particular domain Information about cached content With the sssctl tool, you can: Manage the SSSD cache Manage logs Check configuration files Note The sssctl tool replaces sss_cache and sss_debuglevel tools. Additional resources sssctl --help 9.2. Generating access control reports using sssctl You can list the access control rules applied to the machine on which you are running the report because SSSD controls which users can log in to the client. Note The access report is not accurate because the tool does not track users locked out by the Key Distribution Center (KDC). Prerequisites You must be logged in with administrator privileges The sssctl tool is available on RHEL 7, RHEL 8, and RHEL 9 systems. Procedure To generate a report for the idm.example.com domain, enter: 9.3. Displaying user authorization details using sssctl The sssctl user-checks command helps debug problems in applications that use the System Security Services Daemon (SSSD) for user lookup, authentication, and authorization. The sssctl user-checks [USER_NAME] command displays user data available through Name Service Switch (NSS) and the InfoPipe responder for the D-Bus interface. The displayed data shows whether the user is authorized to log in using the system-auth Pluggable Authentication Module (PAM) service. The command has two options: -a for a PAM action -s for a PAM service If you do not define -a and -s options, the sssctl tool uses default options: -a acct -s system-auth . Prerequisites You must be logged in with administrator privileges The sssctl tool is available on RHEL 7, RHEL 8, and RHEL 9 systems. Procedure To display user data for a particular user, enter: Additional resources sssctl user-checks --help

Commands:
sssctl access-report idm.example.com 1 rule cached Rule name: example.user Member users: example.user Member services: sshd
sssctl user-checks -a acct -s sshd example.user user: example.user action: acct service: sshd .
2.8.3. Monitor After configuring the video card, click on the Monitor tab as shown in Figure 2.13, "X Configuration - Monitor" . Figure 2.13. X Configuration - Monitor Probe for monitor is selected by default. Accept this default to have the installation program probe for the monitor during installation. Probing works for most modern monitors. If this option is selected and the installation program cannot successfully probe the monitor, the installation program stops at the monitor configuration screen. To continue the installation process, select your monitor from the list and click . Alternatively, you can select your monitor from the list. You can also specify the horizontal and vertical sync rates instead of selecting a specific monitor by checking the Specify hysnc and vsync instead of monitor option. This option is useful if the monitor for the system is not listed. Notice that when this option is enabled, the monitor list is disabled.

Commands:
10.3.2. Updated Packages The following table lists updated packages in Red Hat Enterprise Linux 6 and a description of noteworthy changes. Table 10.1. Updated Packages Updated Package Description OProfile OProfile has been updated to 0.9.5. This newer version includes support for Intel Atom and i7 processors, AMD Family 11h processors, and the Instruction Based Sampling (IBS) feature in AMD Family 10h. quota, edquota, setquota Now accepts a user name or user ID as an argument. If the argument appears to be a number it will be considered a user ID, otherwise it will be translated into an ID automatically. Be aware that this can cause a problem if the user name consists solely of digits. The quota package has been updated. The -x argument, which forced user name to ID translation in utilities such as quota , edquota and setquota has been removed. This functionality is now provided by the --always-resolve option. module-init-tools /etc/modprobe.conf does not exist by default. Can still be used if manually created. openscap As of Red Hat Enterprise Linux 6.6, the openscap package has been rebased to conform to the SCAP 1.2 specification. This update includes a number of changes to component specifications. For details, see http://scap.nist.gov . iscsi-initiator-utils To include a number of bug fix updates, the iscsiuio component has been rebased to version 0.7.8.2.

Commands:
3.7. Bonds A bond is a collection of multiple network interface cards into a single software-defined device. Because bonded network interfaces combine the transmission capability of the network interface cards included in the bond to act as a single network interface, they can provide greater transmission speed than that of a single network interface card. Also, because all network interface cards in the bond must fail for the bond itself to fail, bonding provides increased fault tolerance. However, one limitation is that the network interface cards that form a bonded network interface must be of the same make and model to ensure that all network interface cards in the bond support the same options and modes. The packet dispersal algorithm for a bond is determined by the bonding mode used. Important Modes 1, 2, 3 and 4 support both virtual machine (bridged) and non-virtual machine (bridgeless) network types. Modes 0, 5 and 6 support non-virtual machine (bridgeless) networks only.

Commands:
Appendix B. Using AMQ Broker with the examples The AMQ JavaScript examples require a running message broker with a queue named examples . Use the procedures below to install and start the broker and define the queue. B.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . B.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... B.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named examples . USD <broker-instance-dir> /bin/artemis queue create --name examples --address examples --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. B.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2021-08-24 14:26:52 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name examples --address examples --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
2.4. Configuration examples The following examples provide real-world demonstrations of how SELinux complements the Apache HTTP Server and how full function of the Apache HTTP Server can be maintained. 2.4.1. Running a static site To create a static website, label the .html files for that website with the httpd_sys_content_t type. By default, the Apache HTTP Server cannot write to files that are labeled with the httpd_sys_content_t type. The following example creates a new directory to store files for a read-only website: Run the mkdir /mywebsite command as the root user to create a top-level directory. As the root user, create a /mywebsite/index.html file. Copy and paste the following content into /mywebsite/index.html : To allow the Apache HTTP Server read only access to /mywebsite/ , as well as files and subdirectories under it, label /mywebsite/ with the httpd_sys_content_t type. Run the following command as the root user to add the label change to file-context configuration: Run the restorecon -R -v /mywebsite command as the root user to make the label changes: For this example, edit /etc/httpd/conf/httpd.conf as the root user. Comment out the existing DocumentRoot option. Add a DocumentRoot "/mywebsite" option. After editing, these options should look as follows: Run the service httpd status command as the root user to see the status of the Apache HTTP Server. If the server is stopped, run the service httpd start command as the root user to start it. If the server is running, run the service httpd restart command as the root user to restart the service (this also applies any changes made to httpd.conf ). Use a web browser to navigate to http://localhost/index.html . The following is displayed:

Commands:
<html> <h2>index.html from /mywebsite/</h2> </html>
~]# semanage fcontext -a -t httpd_sys_content_t "/mywebsite(/.*)?"
~]# restorecon -R -v /mywebsite restorecon reset /mywebsite context unconfined_u:object_r:default_t:s0->system_u:object_r:httpd_sys_content_t:s0 restorecon reset /mywebsite/index.html context unconfined_u:object_r:default_t:s0->system_u:object_r:httpd_sys_content_t:s0
#DocumentRoot "/var/www/html" DocumentRoot "/mywebsite"
index.html from /mywebsite/
Chapter 10. Downloading Red Hat build of OptaPlanner examples You can download the Red Hat build of OptaPlanner examples as a part of the {PRODUCTPAM} add-ons package available on the Red Hat Customer Portal. Procedure Navigate to the Software Downloads page in the Red Hat Customer Portal (login required), and select the product and version from the drop-down options: Product: Process Automation Manager Version: 7.13.5 Download Red Hat Process Automation Manager 7.13 Add Ons . Extract the rhpam-7.13.5-add-ons.zip file. The extracted add-ons folder contains the rhpam-7.13.5-planner-engine.zip file. Extract the rhpam-7.13.5-planner-engine.zip file. Result The extracted rhpam-7.13.5-planner-engine directory contains example source code under the following subdirectories: examples/sources/src/main/java/org/optaplanner/examples examples/sources/src/main/resources/org/optaplanner/examples 10.1. Running OptaPlanner examples Red Hat build of OptaPlanner includes several examples that demonstrate a variety of planning use cases. Download and use the examples to explore different types of planning solutions. Prerequisites You have downloaded and extracted the examples as described in Chapter 10, Downloading Red Hat build of OptaPlanner examples . Procedure To run the examples, in the rhpam-7.13.5-planner-engine/examples directory enter one of the following commands: Linux or Mac: Windows: The OptaPlanner Examples window opens. Select an example to run that example. Note Red Hat build of OptaPlanner has no GUI dependencies. It runs just as well on a server or a mobile JVM as it does on the desktop. 10.2. Running the Red Hat build of OptaPlanner examples in an IDE (IntelliJ, Eclipse, or Netbeans) If you use an integrated development environment (IDE), such as IntelliJ, Eclipse, or Netbeans, you can run your downloaded OptaPlanner examples within your development environment. Prerequisites You have downloaded and extracted the OptaPlanner examples as described in Chapter 10, Downloading Red Hat build of OptaPlanner examples . Procedure Open the OptaPlanner examples as a new project: For IntelliJ or Netbeans, open examples/sources/pom.xml as the new project. The Maven integration guides you through the rest of the installation. Skip the rest of the steps in this procedure. For Eclipse, open a new project for the /examples/binaries directory, located under the rhpam-7.13.5-planner-engine directory. Add all the JAR files that are in the binaries directory to the classpath, except for the examples/binaries/optaplanner-examples-7.67.0.Final-redhat-00024.jar file. Add the Java source directory src/main/java and the Java resources directory src/main/resources , located under the rhpam-7.13.5-planner-engine/examples/sources/ directory. Create a run configuration: Main class: org.optaplanner.examples.app.OptaPlannerExamplesApp VM parameters (optional): -Xmx512M -server -Dorg.optaplanner.examples.dataDir=examples/sources/data Working directory: examples/sources Run the run configuration.

Commands:
./runExamples.sh
runExamples.bat
13.4. SR-IOV Restrictions SR-IOV is only thoroughly tested with the following devices: Intel(R) 82576NS Gigabit Ethernet Controller ( igb driver) Intel(R) 82576EB Gigabit Ethernet Controller ( igb driver) Intel(R) 82599ES 10 Gigabit Ethernet Controller ( ixgbe driver) Intel(R) 82599EB 10 Gigabit Ethernet Controller ( ixgbe driver) Other SR-IOV devices may work but have not been tested at the time of release

Commands: