mtpti5iD/redhat-docs_dataset huggingface dataset:
Introduction Welcome to the Reference Guide . The Reference Guide contains useful information about the Red Hat Enterprise Linux system. From fundamental concepts, such as the structure of the file system, to the finer points of system security and authentication control, we hope you find this book to be a valuable resource. This guide is for you if you want to learn a bit more about how the Red Hat Enterprise Linux system works. Topics that you can explore within this manual include the following: The boot process The file system structure The X Window System Network services Security tools 1. Changes To This Manual This manual has been reorganized for clarity and updated for the latest features of Red Hat Enterprise Linux 4.5.0. Some of the changes include: A New Samba Chapter The new Samba chapter explains various Samba daemons and configuration options. Special thanks to John Terpstra for his hard work in helping to complete this chapter. A New SELinux Chapter The new SELinux chapter explains various SELinux files and configuration options. Special thanks to Karsten Wade for his hard work in helping to complete this chapter. An Updated proc File System Chapter The proc file system chapter includes updated information in regards to the 2.6 kernel. Special thanks to Arjan van de Ven for his hard work in helping to complete this chapter. An Updated Network File System (NFS) Chapter The Network File System (NFS) chapter has been revised and reorganized to include NFSv4. An Updated The X Window System Chapter The X Window System chapter has been revised to include information on the X11R6.8 release developed by the X.Org team. Before reading this guide, you should be familiar with the contents of the Installation Guide concerning installation issues, the Red Hat Enterprise Linux Introduction to System Adminitration for basic administration concepts, the System Administrators Guide for general customization instructions, and the Security Guide for security related instructions. This guide contains information about topics for advanced users.

Commands:
1.5. Know Your Users Although some people bristle at the term "users" (perhaps due to some system administrators' use of the term in a derogatory manner), it is used here with no such connotation implied. Users are those people that use the systems and resources for which you are responsible -- no more, and no less. As such, they are central to your ability to successfully administer your systems; without understanding your users, how can you understand the system resources they require? For example, consider a bank teller. A bank teller uses a strictly-defined set of applications and requires little in the way of system resources. A software engineer, on the other hand, may use many different applications and always welcomes more system resources (for faster build times). Two entirely different users with two entirely different needs. Make sure you learn as much about your users as you can.

Commands:
Chapter 1. Support policy for Cryostat Red Hat supports a major version of Cryostat for a minimum of 6 months. Red Hat bases this figure on the time that the product gets released on the Red Hat Customer Portal. You can install and deploy Cryostat on Red Hat OpenShift Container Platform 4.12 or a later version that runs on an x86_64 or ARM64 architecture. Additional resources For more information about the Cryostat life cycle policy, see Red Hat build of Cryostat on the Red Hat OpenShift Container Platform Life Cycle Policy web page.

Commands:
Preface This tutorial demonstrates how to use Debezium to capture updates in a MySQL database. As the data in the database changes, you can see the resulting event streams. Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To propose improvements, open a Jira issue and describe your suggested changes. Provide as much detail as possible to enable us to address your request quickly. Prerequisite You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one. Procedure Click the following link: Create issue . In the Summary text box, enter a brief description of the issue. In the Description text box, provide the following information: The URL of the page where you found the issue. A detailed description of the issue. You can leave the information in any other fields at their default values. Click Create to submit the Jira issue to the documentation team. Thank you for taking the time to provide feedback.

Commands:
9.20. Installation Complete Congratulations! Your Red Hat Enterprise Linux installation is now complete! The installation program prompts you to prepare your system for reboot. Remember to remove any installation media if it is not ejected automatically upon reboot. After your computer's normal power-up sequence has completed, Red Hat Enterprise Linux loads and starts. By default, the start process is hidden behind a graphical screen that displays a progress bar. Eventually, a login: prompt or a GUI login screen (if you installed the X Window System and chose to start X automatically) appears. The first time you start your Red Hat Enterprise Linux system in run level 5 (the graphical run level), the FirstBoot tool appears, which guides you through the Red Hat Enterprise Linux configuration. Using this tool, you can set your system time and date, install software, register your machine with Red Hat Network, and more. FirstBoot lets you configure your environment at the beginning, so that you can get started using your Red Hat Enterprise Linux system quickly. Chapter 34, Firstboot will guide you through the configuration process.

Commands:
Chapter 9. Importing projects from Git repositories Git is a distributed version control system. It implements revisions as commit objects. When you save your changes to a repository, a new commit object in the Git repository is created. Business Central uses Git to store project data, including assets such as rules and processes. When you create a project in Business Central, it is added to a Git repository that is connected to Business Central. If you have projects in Git repositories, you can import the project's master branch or import the master branch along with other specific branches into the Business Central Git repository through Business Central spaces. Prerequisites Red Hat Decision Manager projects exist in an external Git repository. You have the credentials required for read access to that external Git repository. Procedure In Business Central, go to Menu Design Projects . Select or create the space into which you want to import the projects. The default space is MySpace . In the upper-right corner of the screen, click the arrow to Add Project and select Import Project . In the Import Project window, enter the URL and credentials for the Git repository that contains the project that you want to import and click Import . The Import Projects page is displayed. Optional: To import master and specific branches, do the following tasks: On the Import Projects page, click the branches icon. In the Branches to be imported window, select branches from the list. Note You must select the master branch as a minimum. Click Ok . On the Import Projects page, ensure the project is highlighted and click Ok .

Commands:
Chapter 22. Deprecated Functionality in Red Hat Enterprise Linux 7 Symbols from libraries linked as dependencies no longer resolved by ld Previously, the ld linker resolved any symbols present in any linked library, even if some libraries were linked only implicitly as dependencies of other libraries. This allowed developers to use symbols from the implicitly linked libraries in application code and omit explicitly specifying these libraries for linking. For security reasons, ld has been changed to not resolve references to symbols in libraries linked implicitly as dependencies. As a result, linking with ld fails when application code attempts to use symbols from libraries not declared for linking and linked only implicitly as dependencies. To use symbols from libraries linked as dependencies, developers must explicitly link against these libraries as well. To restore the behavior of ld , use the -copy-dt-needed-entries command-line option. (BZ# 1292230 ) Windows guest virtual machine support limited As of Red Hat Enterprise Linux 7, Windows guest virtual machines are supported only under specific subscription programs, such as Advanced Mission Critical (AMC).

Commands:
5.2.29. /proc/sysrq-trigger Using the echo command to write to this file, a remote root user can execute most System Request Key commands remotely as if at the local terminal. To echo values to this file, the /proc/sys/kernel/sysrq must be set to a value other than 0 . For more information about the System Request Key, refer to Section 5.3.9.3, " /proc/sys/kernel/ " . Although it is possible to write to this file, it cannot be read, even by the root user.

Commands:
2.8. Installing Ansible to Support Gdeploy Note Consult with your IT department to confirm your organization's supported download instructions for Ansible. gDeploy depends on Ansible to execute the playbooks and modules. You must install Ansible 2.5 or higher to use gDeploy. Execute the following command to enable the repository required to install Ansible: For Red Hat Enterprise Linux 8 For Red Hat Enterprise Linux 7 Install ansible by executing the following command:

Commands:
subscription-manager repos --enable=ansible-2-for-rhel-8-x86_64-rpms
subscription-manager repos --enable=rhel-7-server-ansible-2-rpms
yum install ansible
Chapter 7. Conclusion Congratulations. In this tutorial, you learned how to incorporate data science, artificial intelligence, and machine learning into an OpenShift development workflow. You used an example fraud detection model and completed the following tasks: Explored a pre-trained fraud detection model by using a Jupyter notebook. Deployed the model by using OpenShift AI model serving. Refined and trained the model by using automated pipelines. Learned how to train the model by using Ray, a distributed computing framework.

Commands:
D.3. Controlling Activation with Tags You can specify in the configuration file that only certain logical volumes should be activated on that host. For example, the following entry acts as a filter for activation requests (such as vgchange -ay ) and only activates vg1/lvol0 and any logical volumes or volume groups with the database tag in the metadata on that host. There is a special match "@*" that causes a match only if any metadata tag matches any host tag on that machine. As another example, consider a situation where every machine in the cluster has the following entry in the configuration file: If you want to activate vg1/lvol2 only on host db2 , do the following: Run lvchange --addtag @db2 vg1/lvol2 from any host in the cluster. Run lvchange -ay vg1/lvol2 . This solution involves storing host names inside the volume group metadata.

Commands:
activation { volume_list = ["vg1/lvol0", "@database" ] }
tags { hosttags = 1 }
Chapter 11. Configuring alert notifications In OpenShift Container Platform, an alert is fired when the conditions defined in an alerting rule are true. An alert provides a notification that a set of circumstances are apparent within a cluster. Firing alerts can be viewed in the Alerting UI in the OpenShift Container Platform web console by default. After an installation, you can configure OpenShift Container Platform to send alert notifications to external systems. 11.1. Sending notifications to external systems In OpenShift Container Platform 4.18, firing alerts can be viewed in the Alerting UI. Alerts are not configured by default to be sent to any notification systems. You can configure OpenShift Container Platform to send alerts to the following receiver types: PagerDuty Webhook Email Slack Microsoft Teams Routing alerts to receivers enables you to send timely notifications to the appropriate teams when failures occur. For example, critical alerts require immediate attention and are typically paged to an individual or a critical response team. Alerts that provide non-critical warning notifications might instead be routed to a ticketing system for non-immediate review. Checking that alerting is operational by using the watchdog alert OpenShift Container Platform monitoring includes a watchdog alert that fires continuously. Alertmanager repeatedly sends watchdog alert notifications to configured notification providers. The provider is usually configured to notify an administrator when it stops receiving the watchdog alert. This mechanism helps you quickly identify any communication issues between Alertmanager and the notification provider. 11.2. Additional resources About OpenShift Container Platform monitoring Configuring alert notifications

Commands:
Installation Guide Red Hat CodeReady Workspaces 2.1 Installing Red Hat CodeReady Workspaces 2.1 Supriya Takkhi Robert Kratky rkratky@redhat.com Michal Maler mmaler@redhat.com Fabrice Flore-Thebault ffloreth@redhat.com Yana Hontyk yhontyk@redhat.com Red Hat Developer Group Documentation Team devtools-docs@redhat.com

Commands:
Preface If you're using GitLab CI for your application, pipeline runs may fail due to missing secrets. Without them, integrations with Quay, JFrog, and Red Hat Advanced Cluster Security (ACS) won't work, breaking security tasks like vulnerability scanning, image signing, and SBOM generation for compliance. To prevent this, you need to securely store secrets in GitLab CI. This guide walks you through the process, ensuring your pipelines run smoothly and securely.

Commands:
Chapter 8. Frequently asked questions Is it possible to deploy applications from OpenShift Dev Spaces to an OpenShift cluster? The user must log in to the OpenShift cluster from their running workspace using oc login . For best performance, what is the recommended storage to use for Persistent Volumes used with OpenShift Dev Spaces? Use block storage. Is it possible to deploy more than one OpenShift Dev Spaces instance on the same cluster? Only one OpenShift Dev Spaces instance can be deployed per cluster. Is it possible to install OpenShift Dev Spaces offline (that is, disconnected from the internet)? See Installing Red Hat OpenShift Dev Spaces in restricted environments on OpenShift . Is it possible to use non-default certificates with OpenShift Dev Spaces? You can use self-signed or public certificates. See Importing untrusted TLS certificates . Is it possible to run multiple workspaces simultaneously? See Enabling users to run multiple workspaces simultaneously .

Commands:
Chapter 1. About Pipelines as Code With Pipelines as Code, cluster administrators and users with the required privileges can define pipeline templates as part of source code Git repositories. When triggered by a source code push or a pull request for the configured Git repository, Pipelines as Code runs the pipeline and reports the status. 1.1. Key features Pipelines as Code supports the following features: Pull request status and control on the platform hosting the Git repository. GitHub Checks API to set the status of a pipeline run, including rechecks. GitHub pull request and commit events. Pull request actions in comments, such as /retest . Git events filtering and a separate pipeline for each event. Automatic task resolution in OpenShift Pipelines, including local tasks, Tekton Hub, and remote URLs. Retrieval of configurations using GitHub blobs and objects API. Access Control List (ACL) over a GitHub organization or using a Prow style OWNERS file. The tkn pac CLI plugin for managing bootstrapping and Pipelines as Code repositories. Support for GitHub App, GitHub Webhook, Bitbucket Data Center, and Bitbucket Cloud.

Commands:
24.4. Host Log Files Log File Description /var/log/messages The log file used by libvirt . Use journalctl to view the log. You must be a member of the adm , systemd-journal , or wheel groups to view the log. /var/log/vdsm/spm-lock.log Log file detailing the host's ability to obtain a lease on the Storage Pool Manager role. The log details when the host has acquired, released, renewed, or failed to renew the lease. /var/log/vdsm/vdsm.log Log file for VDSM, the Manager's agent on the host(s). /tmp/ovirt-host-deploy- Date .log A host deployment log that is copied to the Manager as /var/log/ovirt-engine/host-deploy/ovirt- Date-Host-Correlation_ID .log after the host has been successfully deployed. /var/log/vdsm/import/import- UUID-Date .log Log file detailing virtual machine imports from a KVM host, a VMWare provider, or a RHEL 5 Xen host, including import failure information. UUID is the UUID of the virtual machine that was imported and Date is the date and time that the import began. /var/log/vdsm/supervdsm.log Logs VDSM tasks that were executed with superuser permissions. /var/log/vdsm/upgrade.log VDSM uses this log file during host upgrades to log configuration changes. /var/log/vdsm/mom.log Logs the activities of the VDSM's memory overcommitment manager.

Commands:
8.236. xmlrpc-c 8.236.1. RHBA-2013:1254 - xmlrpc-c bug fix update Updated xmlrpc-c packages that fix one bug are now available. XML-RPC is a remote procedure call (RPC) protocol that uses XML to encode its calls and HTTP as a transport mechanism. Bug Fix BZ# 809819 Previously, features listed when the "--help" command was run were not consistent with the list when the "--features" command was run. Also, running the reproducer script resulted in "Unrecognized token" errors. With this update, listed features are consistent, and "Unrecognized token" errors are no longer displayed. Users of xmlrpc-c are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 18. Post-installation security hardening RHEL is designed with robust security features enabled by default. However, you can enhance its security further through additional hardening measures. For more information about: Installing security updates and displaying additional details about the updates to keep your RHEL systems secured against newly discovered threats and vulnerabilities, see Managing and monitoring security updates . Processes and practices for securing RHEL servers and workstations against local and remote intrusion, exploitation, and malicious activity, see Security hardening . Control how users and processes interact with the files on the system or control which users can perform which actions by mapping them to specific SELinux confined users, see Using SELinux . Tools and techniques to improve the security of your networks and lower the risks of data breaches and intrusions, see Securing networks . Packet filters, such as firewalls, that use rules to control incoming, outgoing, and forwarded network traffic, see Configuring firewalls and packet filters .

Commands:
Chapter 4. Running the playbook After you define variable settings, you can run the playbook to begin the automated installation process. You can run a playbook by using the ansible-playbook command on the control node or by using the Red Hat Ansible automation controller . The JBoss Web Server collection then handles all installation and deployment tasks automatically. Note The following procedure assumes that you have created and updated a custom playbook. Prerequisites You have enabled an automated deployment of JBoss Web Server . You are familar with general Ansible concepts and creating Ansible playbooks. For more information, see the Ansible documentation . Your playbook includes an appropriate link to the location where you have defined your variables. For example: The preceding example assumes that you have defined variables in a vars.yml file. Replace <path_to_vars_file> with the appropriate path. Your playbook also specifies the redhat.jws.jws role. For example: Note The redhat.jws.jws role is already preconfigured with become: true directives, which activate user privilege escalation for performing any automated tasks that require root privileges on your target hosts. Red Hat Enterprise Linux (RHEL) version 8 or 9 is already installed on your target hosts. Procedure Perform either of the following steps: On your Ansible control node, enter the following command: In the preceding command, replace <playbook_name> with the name you have assigned to your playbook. The preceding command assumes that your user account supports passwordless authentication. Note If your user account requires password authentication, you can run the preceding command with the --ask-sudo-pass option and specify the required password when prompted. For example: USD ansible-playbook <playbook_name> .yml --ask-sudo-pass Use the Red Hat Ansible automation controller to run your playbook. For more information about getting started with the automation controller, see the Red Hat Ansible Automation Platform documentation page.

Commands:
--- [...] vars_files: - <path_to_vars_file> /vars.yml [...]
--- [...] roles: - redhat.jws.jws [...]
ansible-playbook <playbook_name> .yml
Chapter 136. KafkaConnectorStatus schema reference Used in: KafkaConnector 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. autoRestart AutoRestartStatus The auto restart status. connectorStatus map The connector status, as reported by the Kafka Connect REST API. tasksMax integer The maximum number of tasks for the Kafka Connector. topics string array The list of topics used by the Kafka Connector.

Commands:
10.6. Transport Security Authentication Modes The following authentication modes are available: anonymous No certificates are exchanged. Settings are not needed for the keystore and truststore properties. The client must have org.teiid.ssl.allowAnon set to true (the default) to connect to an anonymous server. Communications are encrypted using the TLS_DH_anon_WITH_AES_128_CBC_SHA SSL cipher suite. This is suitable for most secure intranets. 1-way Athenticates the server to the client. The server presents a certificate which is signed by the private key stored in the server's keystore. The server's corresponding public key must be in the client's truststore. 2-way Mutual client and server authentication. The server presents a certificate which is signed by the private key stored in the server's keystore. The server's corresponding public key must be in the client's truststore. Additionally, the client presents a certificate signed by its private key stored in the client's keystore. The client's corresponsing public key must be in the server's truststore. Note You can use keytool to generate encryption keys; however, you should first consider your local requirements for managing public key cryptography.

Commands: