mtpti5iD/redhat-docs_dataset huggingface dataset:
29.4. Removing Keytabs Removing a keytab and creating a new keytab is necessary for example when you unenroll and re-enroll a host or when you experience Kerberos connection errors. To remove all keytabs on a host, use the ipa-rmkeytab utility, and pass these options: --realm ( -r ) to specify the Kerberos realm --keytab ( -k ) to specify the path to the keytab file To remove a keytab for a specific service, use the --principal ( -p ) option to specify the service principal:

Commands:
ipa-rmkeytab --realm EXAMPLE.COM --keytab /etc/krb5.keytab
ipa-rmkeytab --principal ldap/client.example.com --keytab /etc/krb5.keytab
6.3. Resizing an Ext4 File System Before growing an ext4 file system, ensure that the underlying block device is of an appropriate size to hold the file system later. Use the appropriate resizing methods for the affected block device. An ext4 file system may be grown while mounted using the resize2fs command: The resize2fs command can also decrease the size of an unmounted ext4 file system: When resizing an ext4 file system, the resize2fs utility reads the size in units of file system block size, unless a suffix indicating a specific unit is used. The following suffixes indicate specific units: s - 512 byte sectors K - kilobytes M - megabytes G - gigabytes Note The size parameter is optional (and often redundant) when expanding. The resize2fs automatically expands to fill all available space of the container, usually a logical volume or partition. For more information about resizing an ext4 file system, refer to man resize2fs .

Commands:
resize2fs /mount/device node
resize2fs /dev/ device size
7.122. libtalloc 7.122.1. RHBA-2013:0352 - libtalloc bug fix update Updated libtalloc packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The libtalloc packages provide a library that implements a hierarchical memory allocator with destructors. Note The libtalloc packages have been upgraded to upstream version 2.0.7, which provides a number of bug fixes over the version. (BZ# 766335 ) All libtalloc users are advised to upgrade to these updated packages, which fix these bugs.

Commands:
11.3. Locking Down Enabled Extensions In GNOME Shell, you can prevent the user from enabling or disabling extensions by locking down the org.gnome.shell.enabled-extensions and org.gnome.shell.development-tools keys. Locking down the org.gnome.shell.development-tools key ensures that the user cannot use GNOME Shell's integrated debugger and inspector tool ( Looking Glass ) to disable any mandatory extensions. Procedure 11.3. Locking down enabled extensions Create a local database file for machine-wide settings in /etc/dconf/db/local.d/00-extensions : The enabled-extensions key specifies the enabled extensions using the extensions' uuid ( myextension1@myname.example.com and myextension2@myname.example.com ). The development-tools key is set to false to disable access to Looking Glass . Override the user's setting and prevent the user from changing it in /etc/dconf/db/local.d/locks/extensions : Update the system databases: Users must log out and back in again before the system-wide settings take effect. After locking down the org.gnome.shell.enabled-extensions and org.gnome.shell.development-tools keys, any extensions installed in ~/.local/share/gnome-shell/extensions or /usr/share/gnome-shell/extensions that are not listed in the org.gnome.shell.enabled-extensions key will not be loaded by GNOME Shell, thus preventing the user from using them.

Commands:
List all extensions that you want to have enabled for all users enabled-extensions=[' myextension1@myname.example.com ', ' myextension2@myname.example.com '] Disable access to Looking Glass development-tools=false
Lock the list of mandatory extensions and access to Looking Glass /org/gnome/shell/enabled-extensions /org/gnome/shell/development-tools
dconf update
16.13. Initializing the Hard Disk If no readable partition tables are found on existing hard disks, the installation program asks to initialize the hard disk. This operation makes any existing data on the hard disk unreadable. If your system has a brand new hard disk with no operating system installed, or you have removed all partitions on the hard disk, click Re-initialize drive . The installation program presents you with a separate dialog for each disk on which it cannot read a valid partition table. Click the Ignore all button or Re-initialize all button to apply the same answer to all devices. Figure 16.34. Warning screen - initializing hard drive Certain RAID systems or other nonstandard configurations may be unreadable to the installation program and the prompt to initialize the hard disk may appear. The installation program responds to the physical disk structures it is able to detect. To enable automatic initializing of hard disks for which it turns out to be necessary, use the kickstart command zerombr (refer to Chapter 32, Kickstart Installations ). This command is required when performing an unattended installation on a system with previously initialized disks. Warning If you have a nonstandard disk configuration that can be detached during installation and detected and configured afterward, power off the system, detach it, and restart the installation.

Commands:
3.12. RHEA-2011:1728 - new package: python-rtslib A new python-rtslib package is now available for Red Hat Enterprise Linux 6. The python-rtslib package provides a library for interacting with storage target-related interfaces for the Python programming environment. This enhancement update adds the python-rtslib package to Red Hat Enterprise Linux 6 as part of the Technology Preview of Fibre Channel over Ethernet (FCoE) target mode. (BZ# 726778 ) Important This package is provided as a dependency of the fcoe-target-utils package. It is recommended to install it only as a prerequisite for running fcoe-target-utils, and not to use it independently. All users who want to use the Technology Preview of Fibre Channel over Ethernet target mode should install this newly-released package, which adds this enhancement.

Commands:
18.3.2. Command Options Command options instruct iptables to perform a specific action. Only one command option is allowed per iptables command. With the exception of the help command, all commands are written in upper-case characters. The iptables commands are as follows: -A - Appends the iptables rule to the end of the specified chain. This is the command used to add a rule when rule order in the chain does not matter. -C - Checks a particular rule before adding it to the user-specified chain. This command can help you construct complicated iptables rules by prompting you for additional parameters and options. -D - Deletes a rule in a particular chain by number (such as 5 for the fifth rule in a chain). You can also type the entire rule, and iptables deletes the rule in the chain that matches it. -E - Renames a user-defined chain. This does not affect the structure of the table. -F - Flushes the selected chain, which effectively deletes every rule in the the chain. If no chain is specified, this command flushes every rule from every chain. -h - Provides a list of command structures, as well as a quick summary of command parameters and options. -I - Inserts a rule in a chain at a point specified by a user-defined integer value. If no number is specified, iptables places the command at the top of the chain. Warning Be aware when using the -A or -I option that the order of the rules within a chain are important for determining which rules apply to which packets. -L - Lists all of the rules in the chain specified after the command. To list all rules in all chains in the default filter table, do not specify a chain or table. Otherwise, the following syntax should be used to list the rules in a specific chain in a particular table: Additional options for the -L command option, which provide rule numbers and allow more verbose rule descriptions, are described in Section 18.3.6, "Listing Options" . -N - Creates a new chain with a user-specified name. -P - Sets the default policy for the specified chain, so that when packets traverse an entire chain without matching a rule, they are sent on to the specified target, such as ACCEPT or DROP. -R - Replaces a rule in the specified chain. The rule's number must be specified after the chain's name. The first rule in a chain corresponds to rule number one. -X - Deletes a user-specified chain. Deleting a built-in chain for any table is not allowed. -Z - Zeros the byte and packet counters in all chains for a table.

Commands:
iptables -L <chain-name> -t <table-name>
10.9. Additional Resources To learn more about the Apache HTTP Server, refer to the following resources. 10.9.1. Useful Websites http://httpd.apache.org/ - The official website for the Apache HTTP Server with documentation on all the directives and default modules. http://www.modssl.org/ - The official website for mod_ssl . http://www.apacheweek.com/ - A comprehensive online weekly newsletter about all things Apache.

Commands:
Chapter 1. Debezium Overview Debezium for Red Hat Integration is a distributed platform that captures database operations, creates data change event records for row-level operations, and streams change event records to Apache Kafka topics. Debezium is built on Apache Kafka and is deployed and integrated with Streams for Apache Kafka. Debezium captures row-level changes to a database table and passes corresponding change events to Streams for Apache Kafka. Applications can read these change event streams and access the change events in the order in which they occurred. Debezium is the upstream community project for Debezium for Red Hat Integration. Debezium has multiple uses, including: Data replication Updating caches and search indexes Simplifying monolithic applications Data integration Enabling streaming queries Debezium provides Apache Kafka Connect connectors for the following common databases: Db2 MariaDB MySQL MongoDB Oracle PostgreSQL SQL Server

Commands:
Chapter 6. Backing OpenShift Container Platform applications with OpenShift Container Storage You cannot directly install OpenShift Container Storage during the OpenShift Container Platform installation. However, you can install OpenShift Container Storage on an existing OpenShift Container Platform by using the Operator Hub and then configure the OpenShift Container Platform applications to be backed by OpenShift Container Storage. Prerequisites OpenShift Container Platform is installed and you have administrative access to OpenShift Web Console. OpenShift Container Storage is installed and running in the openshift-storage namespace. Procedure In the OpenShift Web Console, perform one of the following: Click Workloads Deployments . In the Deployments page, you can do one of the following: Select any existing deployment and click Add Storage option from the Action menu (...). Create a new deployment and then add storage. Click Create Deployment to create a new deployment. Edit the YAML based on your requirement to create a deployment. Click Create . Select Add Storage from the Actions drop down menu on the top right of the page. Click Workloads Deployment Configs . In the Deployment Configs page, you can do one of the following: Select any existing deployment and click Add Storage option from the Action menu (...). Create a new deployment and then add storage. Click Create Deployment Config to create a new deployment. Edit the YAML based on your requirement to create a deployment. Click Create . Select Add Storage from the Actions drop down menu on the top right of the page. In the Add Storage page, you can choose one of the following options: Click the Use existing claim option and select a suitable PVC from the drop down list. Click the Create new claim option. Select the appropriate CephFS or RBD storage class from the Storage Class drop down list. Provide a name for the Persistent Volume Claim. Select ReadWriteOnce (RWO) or ReadWriteMany (RWX) access mode. Note ReadOnlyMany (ROX) is deactivated as it is not supported. Select the size of the desired storage capacity. Note You can expand the block PVs but cannot reduce the storage capacity after the creation of Persistent Volume Claim. Specify the mount path and subpath (if required) for the mount path volume inside the container. Click Save . Verification steps Depending on your configuration, perform one of the following: Click Workloads Deployments . Click Workloads Deployment Configs . Set the Project as required. Click the deployment for which you added storage to display the deployment details. Scroll down to Volumes and verify that your deployment has a Type that matches the Persistent Volume Claim that you assigned. Click the Persistent Volume Claim name and verify the storage class name in the Persistent Volume Claim Overview page.

Commands:
3.2. Prerequisites Install the Microsoft Azure CLI based on the instructions listed at https://access.redhat.com/articles/uploading-rhel-image-to-azure#install-the-azure-cross-platform-cli-on-your-azure-administration-server-6 . Migrate your subscriptions from Red Hat to Microsoft Azure based on the instructions listed at https://access.redhat.com/articles/migrating-to-red-hat-cloud-access . Minimum required number of nodes is 3. For compatible physical server, virtual server and client OS platforms , refer https://access.redhat.com/articles/66206 . It is also possible to manage Gluster Storage using the Windows Powershell environment based on the instructions at: https://azure.microsoft.com/en-in/documentation/articles/powershell-install-configure . But that is not listed in this chapter. All of the procedures here will use the Microsoft Azure CLI.

Commands:
Chapter 27. Deployment and Tools systemd component, BZ# 978955 When attempting to start, stop, or restart a service or unit using the systemctl [start|stop|restart] NAME command, no message is displayed to inform the user whether the action has been successful. systemd component, BZ#968401 The /etc/rc.d/rc.local file does not have executable permissions in Red Hat Enterprise Linux 7. If commands are added to the /etc/rc.d/rc.local file, the file has to be made executable afterwards. By default, /etc/rc.d/rc.local does not have executable permissions because if these permissions are detected, the system has to wait until the network is "up" before the boot process can be finished. flightrecorder component, BZ#1049701 The flightrecorder package is currently not included in Red Hat Enterprise Linux 7.

Commands:
probe::sunrpc.svc.destroy Name probe::sunrpc.svc.destroy - Destroy an RPC service Synopsis sunrpc.svc.destroy Values sv_nrthreads the number of concurrent threads sv_name the service name sv_prog the number of the program rpcbadauth the count of requests drooped for authentication failure rpcbadfmt the count of requests dropped for bad formats rpccnt the count of valid RPC requests sv_progname the name of the program netcnt the count of received RPC requests nettcpconn the count of accepted TCP connections

Commands:
Appendix H. Using Your Subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Red Hat AMQ Streams entries in the JBOSS INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Registering Your System for Packages To install RPM packages on Red Hat Enterprise Linux, your system must be registered. If you are using zip or tar files, this step is not required. Go to access.redhat.com . Navigate to Registration Assistant . Select your OS version and continue to the page. Use the listed command in your system terminal to complete the registration. To learn more see How to Register and Subscribe a System to the Red Hat Customer Portal . Revised on 2021-05-18 10:42:27 UTC

Commands:
Chapter 4. Removed features Removed features are those that were deprecated in earlier releases. They are now removed from the Ansible Automation Platform, and will no longer be supported. The following table provides information about features that are removed in Ansible Automation Platform 2.5: Component Feature Automation controller Proxy support for the automation controller has been removed. Load balancers must now point to the platform gateway instead of the controller. ansible-lint Support for old Ansible include tasks syntax is removed in version 2.16 and moved to include_tasks or import_tasks . Update content to use the currently-supported Ansible syntax, like include_tasks or import_tasks . Event-Driven Ansible controller Tokens for the Event-Driven Ansible controller are deprecated. Their configuration has been removed from rulebook activations, and they have been replaced with the Ansible Automation Platform credential type. Ansible-core Support for Windows Server versions 2012 and 2012 R2 is removed, as Microsoft's supported end-of-life date is 10 October 2023. These versions of Windows Server are not tested in the Ansible Automation Platform 2.5 release. Red Hat does not guarantee that these features will continue to work as expected in this and future releases. Ansible-core In the Action plugin with an ActionBase class, the deprecated _remote_checksum method is now removed. Use _execute_remote_stat instead. Ansible-core The deprecated FileLock class is now removed. Add your own implementation or rely on third-party support. Ansible-core Python 3.9 is now removed as a supported version of the automation controller. Use Python 3.10 or later. Ansible-core The include module that was deprecated in ansible-core 2.12 is now removed. Use include_tasks or import_tasks instead. Ansible-core Templar - The deprecated shared_loader_obj parameter of init is now removed. Ansible-core fetch_url - Removed auto disabling decompress when gzip is not available. Ansible-core inventory_cache - Removed deprecated default.fact_caching_prefix ini configuration option. Use defaults.fact_caching_prefix instead. Ansible-core module_utils/basic.py - Removed Python 3.5 as a supported remote version. Python version 2.7 or Python version 3.6 or later is now required. Removed Python versions 2.7 and 3.6 as supported remote versions. Use Python 3.7 or later for target execution. NOTE: This applies to Ansible version 2.17 only. With the removal of Python 2 support, the yum module and yum action plug-in are removed and redirected to dnf . Ansible-core stat - Removed the unused get_md5 parameter. Ansible-core Removed the deprecated JINJA2_NATIVE_WARNING environment variable. Ansible-core Removed the deprecated scp_if_ssh from the ssh connection plugin. Ansible-core Removed the deprecated crypt support from ansible.utils.encrypt . Execution environment The Python link is no longer available in the ubi9-based execution environments; only python3 is. Replace scripts that use python or /bin/python with python3 or /bin/python3 .

Commands:
10.4. Input Set Editor (XML) The Input Set represents a special class that contains attributes from a parent mapping class. When you create mapping classes for an XML Document model, the Teiid Designer automatically adds an Input Set to all XML transformation diagrams for mapping classes beneath the highest node in the Document meta object. The Input Set proves especially useful for information integration using the JBoss Data Virtualization Server . Through the Input Set, you can access a row of data generated by any XML transformation in a mapping class higher in the XML document's hierarchy. You can use Input Set attributes, which are individual columns from the rows of data, within the criteria of an XML transformation query of the child mapping class. You cannot use the Input Set attributes within the SELECT portion of the XML transformation query. To use an Input Set, you must use the Input Set Editor to bind attributes from parent classes. Once you have created an Input Set, you can use the attributes within it as source material for the XML transformation diagram's query. The Input Set only serves to enable data flow between nested mapping classes. If you use the JBoss Data Virtualization Server for data access, your applications cannot directly query an Input Set. Input Sets only display in the XML transformation diagram to which they belong. Input Sets do not display on the Model Explorer view and you cannot use them as you would a normal class, such as for source classes in other transformations. To open the Input Set Editor , either double-click the input set in the Mapping Transformation Diagram or click the edit button on the Input Set in the diagram. Figure 10.25. Edit Input Set Button Figure 10.26. Input Set Editor Panel The Input Parameters table contains a list of mapping attributes within the input set and the mapping attributes bound to input set mapping attributes. The tree on the right displays the parent mapping classes and the attributes available from each. Using the Input Set Editor, you can: Add a mapping attribute from a parent mapping class to the Input Set. In the tree on the right, select the symbol for which you want to create an attribute and click New . The item displays in the Input Parameters and Mapping Class Bindings table. Delete a mapping attribute from the Input Set. Click the row in the Input Parameters and Mapping Class Bindings table that you want to delete and click Delete . The Teiid Designer removes this row from the table and this mapping attribute from your Input Set. Bind and Unbind Input Parameters. Once you have created the mapping attributes within the Input Set that you need, you can use the Input Set Parameters within a mapping class transformation to produce mapping attributes you can map to your XML document.

Commands:
Chapter 1. Red Hat Ansible Automation Platform 2.4 upgrades Upgrade to Red Hat Ansible Automation Platform 2.4 by setting up your inventory and running the installation script. Ansible then upgrades your deployment to 2.4. If you plan to upgrade from Ansible Automation Platform 2.0 or earlier, you must migrate Ansible content for compatibility with 2.4. 1.1. Ansible Automation Platform upgrades Upgrading to version 2.4 from Ansible Automation Platform 2.1 or later involves downloading the installation package and then performing the following steps: Set up your inventory to match your installation environment. Run the 2.4 installation program over your current Ansible Automation Platform installation. Additional resources Upgrading to Red Hat Ansible Automation Platform 2.4 1.2. Ansible Automation Platform legacy upgrades Upgrading to version 2.4 from Ansible Automation Platform 2.0 or earlier requires you to migrate Ansible content for compatibility. The following steps provide an overview of the legacy upgrade process: Duplicate your custom virtual environments into automation execution environments by using the awx-manage command. Migrate data from isolated legacy nodes to execution nodes by performing a side-by-side upgrade so nodes are compatible with the latest automation mesh features. Import or generate a new automation hub API token. Reconfigure your Ansible content to include Fully Qualified Collection Names (FQCN) for compatibility with ansible-core 2.15. Additional resources Migrate virtual environments to automation execution environments Migrate isolated nodes to execution nodes Migrate Ansible content

Commands: