mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 3. LVM Administration Overview This chapter provides an overview of the administrative procedures you use to configure LVM logical volumes. This chapter is intended to provide a general understanding of the steps involved. For specific step-by-step examples of common LVM configuration procedures, see Chapter 5, LVM Configuration Examples . For descriptions of the CLI commands you can use to perform LVM administration, see Chapter 4, LVM Administration with CLI Commands . 3.1. Logical Volume Creation Overview The following is a summary of the steps to perform to create an LVM logical volume. Initialize the partitions you will use for the LVM volume as physical volumes (this labels them). Create a volume group. Create a logical volume. After creating the logical volume you can create and mount the file system. The examples in this document use GFS2 file systems. Create a GFS2 file system on the logical volume with the mkfs.gfs2 command. Create a new mount point with the mkdir command. In a clustered system, create the mount point on all nodes in the cluster. Mount the file system. You may want to add a line to the fstab file for each node in the system. Note Although a GFS2 file system can be implemented in a standalone system or as part of a cluster configuration, for the Red Hat Enterprise Linux 7 release Red Hat does not support the use of GFS2 as a single-node file system. Red Hat will continue to support single-node GFS2 file systems for mounting snapshots of cluster file systems (for example, for backup purposes). Creating the LVM volume is machine independent, since the storage area for LVM setup information is on the physical volumes and not the machine where the volume was created. Servers that use the storage have local copies, but can recreate that from what is on the physical volumes. You can attach physical volumes to a different server if the LVM versions are compatible.

Commands:
function::user_string_n_quoted Name function::user_string_n_quoted - Retrieves and quotes string from user space. Synopsis Arguments addr The user space address to retrieve the string from. n The maximum length of the string (if not null terminated). General Syntax user_string_n_quoted:string(addr:long, n:long) Description Returns up to n characters of a C string from the given user space memory address where any ASCII characters that are not printable are replaced by the corresponding escape sequence in the returned string. Reports " NULL " for address zero. Returns " <unknown> " on the rare cases when userspace data is not accessible at the given address.

Commands:
function user_string_n_quoted:string(addr:long,n:long)
7.5. RHEA-2014:1433 - new package: google-crosextra-caladea-fonts A new google-crosextra-caladea-fonts package is now available for Red Hat Enterprise Linux 6. The Caladea font family is metric-compatible with the Cambria font. Caladea is a serif typeface family based on the Lato font. This enhancement update adds the google-crosextra-caladea-fonts package to Red Hat Enterprise Linux 6. (BZ# 1025629 ) All users who require google-crosextra-caladea-fonts are advised to install this new package.

Commands:
Chapter 17. Creating a dummy interface As a Red Hat Enterprise Linux user, you can create and use dummy network interfaces for debugging and testing purposes. A dummy interface provides a device to route packets without actually transmitting them. It enables you to create additional loopback-like devices managed by NetworkManager and makes an inactive SLIP (Serial Line Internet Protocol) address look like a real address for local programs. 17.1. Creating a dummy interface with both an IPv4 and IPv6 address by using nmcli You can create a dummy interface with various settings, such as IPv4 and IPv6 addresses. After creating the interface, NetworkManager automatically assigns it to the default public firewalld zone. Procedure Create a dummy interface named dummy0 with static IPv4 and IPv6 addresses: Note To configure a dummy interface without IPv4 and IPv6 addresses, set both the ipv4.method and ipv6.method parameters to disabled . Otherwise, IP auto-configuration fails, and NetworkManager deactivates the connection and removes the device. Verification List the connection profiles: Additional resources nm-settings(5) man page on your system

Commands:
nmcli connection add type dummy ifname dummy0 ipv4.method manual ipv4.addresses 192.0.2.1/24 ipv6.method manual ipv6.addresses 2001:db8:2::1/64
nmcli connection show NAME UUID TYPE DEVICE dummy-dummy0 aaf6eb56-73e5-4746-9037-eed42caa8a65 dummy dummy0
Preface Open Java Development Kit (OpenJDK) is a free and open source implementation of the Java Platform, Standard Edition (Java SE). The Red Hat build of Red Hat build of OpenJDK is available in two versions, Red Hat build of OpenJDK 8u and Red Hat build of OpenJDK 11u. Packages for the Red Hat build of Red Hat build of OpenJDK are made available on Red Hat Enterprise Linux and Microsoft Windows and shipped as a JDK and JRE in the Red Hat Container Catalog.

Commands:
Chapter 3. Legacy Support 3.1. Legacy /lifecycle endpoint support Abstract Support legacy API endpoint /lifecycle. JSON XML 3.2. Parameters Name Description Example Default products Index of products filter. Multi-products seperated by comma(,) is suppported. products=Red%20Hat%20Enterprise%20Linux,Openshift%20Container%20Platform all all_versions Index of all versions including ones that are out of Red Hat service. all_versions=false true

Commands:
GET /plccapi/lifecycle.json
GET /plccapi/lifecycle.xml
9.3. Performing Integrity Checks To initiate a manual check, enter the following command as root : At a minimum, AIDE should be configured to run a weekly scan. At most, AIDE should be run daily. For example, to schedule a daily execution of AIDE at 4:05 am using cron (see the Automating System Tasks chapter in the System Administrator's Guide), add the following line to /etc/crontab :

Commands:
~]# aide --check AIDE found differences between database and filesystem!! Start timestamp: 2017-04-07 17:11:33 Summary: Total number of files: 104892 Added files: 7 Removed files: 0 Changed files: 52
05 4 * * * root /usr/sbin/aide --check
18.7. Managing ACIs using the command line This section describes how to manage ACIs using the command line. Note Managing Directory Server ACIs is not supported in the web console. 18.7.1. Displaying ACIs Use the ldapsearch utility to display ACI using the command line. For example, to display the ACIs set on dc=example,dc=com and sub-entries: 18.7.2. Adding an ACI Use the ldapmodify utility to add an ACI. For example: 18.7.3. Deleting an ACI To delete an ACI using the command line: Display the ACIs set on the entry. See Section 18.7.1, "Displaying ACIs" . Delete the ACI: If only one aci attribute is set on the entry or you want to remove all ACIs from the entry: If multiple ACIs exist on the entry and you want to delete a specific ACI, specify the exact ACI: For further details about deleting attributes, see Section 3.1.4.3, "Deleting Attributes from an Entry" . 18.7.4. Updating an ACI To update an ACI using the command line: Delete the existing ACI. See Section 18.7.3, "Deleting an ACI" . Add a new ACI with the updated settings. See Section 18.7.2, "Adding an ACI" .

Commands:
ldapsearch -D "cn=Directory Manager" -W -p 389 -h server.example.com -x -b "dc=example,dc=com" -s sub '(aci=*)' aci
ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: ou=People,dc=example,dc=com changetype: modify add: aci aci: (targetattr="userPassword") (version 3.0; acl "Allow users updating their password"; allow (write) userdn= "ldap:///self";)
ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: ou=People,dc=example,dc=com changetype: delete delete: aci
ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: ou=People,dc=example,dc=com changetype: modify delete: aci aci: (targetattr="userPassword") (version 3.0; acl "Allow users updating their password"; allow (write) userdn= "ldap:///self";)
7.163. openchange 7.163.1. RHSA-2013:0515 - Moderate: openchange security, bug fix and enhancement update Updated openchange packages that fix one security issue, several bugs, and add various enhancements are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate 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 openchange packages provide libraries to access Microsoft Exchange servers using native protocols. Evolution-MAPI uses these libraries to integrate the Evolution PIM application with Microsoft Exchange servers. Note The openchange packages have been upgraded to upstream version 1.0, which provides a number of bug fixes and enhancements over the version, including support for the rebased samba4 packages and several API changes. (BZ# 767672 , BZ# 767678 ) Security Fix CVE-2012-1182 A flaw was found in the Samba suite's Perl-based DCE/RPC IDL (PIDL) compiler. As OpenChange uses code generated by PIDL, this could have resulted in buffer overflows in the way OpenChange handles RPC calls. With this update, the code has been generated with an updated version of PIDL to correct this issue. Bug Fixes BZ# 680061 When the user tried to modify a meeting with one required attendee and himself as the organizer, a segmentation fault occurred in the memcpy() function. Consequently, the evolution-data-server application terminated unexpectedly with a segmentation fault. This bug has been fixed and evolution-data-server no longer crashes in the described scenario. BZ# 870405 Prior to this update, OpenChange 1.0 was unable to send messages with a large message body or with extensive attachment. This was caused by minor issues in OpenChange's exchange.idl definitions. This bug has been fixed and OpenChange now sends extensive messages without complications. All users of openchange are advised to upgrade to these updated packages, which fix these issues and add these enhancements.

Commands:
Chapter 12. RHEL for Real Time scheduler RHEL for Real Time uses the command line utilities help you to configure and monitor process configurations. 12.1. chrt utility for setting the scheduler The chrt utility checks and adjusts scheduler policies and priorities. It can start new processes with the desired properties, or change the current properties of a running process. The chrt utility takes the either --pid or the -p option to specify the process ID (PID). The chrt utility takes the following policy options: -f or --fifo : sets the schedule to SCHED_FIFO . -o or --other : sets the schedule to SCHED_OTHER . -r or --rr : sets schedule to SCHED_RR . -d or --deadline : sets schedule to SCHED_DEADLINE . The following example shows the attributes for a specified process. 12.2. Preemptive scheduling The real-time preemption is the mechanism to temporarily interrupt an executing task, with the intention of resuming it at a later time. It occurs when a higher priority process interrupts the CPU usage. Preemption can have a particularly negative impact on performance, and constant preemption can lead to a state known as thrashing. This problem occurs when processes are constantly preempted and no process ever gets to run completely. Changing the priority of a task can help reduce involuntary preemption. You can check for voluntary and involuntary preemption occurring on a single process by viewing the contents of the /proc/PID/status file, where PID is the process identifier. The following example shows the preemption status of a process with PID 1000. 12.3. Library functions for scheduler priority The real-time processes use a different set of library calls to control policy and priority. The functions require the inclusion of the sched.h header file. The symbols SCHED_OTHER , SCHED_RR and SCHED_FIFO must also be defined in the sched.h header file. The table lists the functions that set the policy and priority for the real-time scheduler. Table 12.1. Library functions for real-time scheduler Functions Description sched_getscheduler() Retrieves the scheduler policy for a specific process identifier (PID) sched_setscheduler() Sets the scheduler policy and other parameters. This function requires three parameters: sched_setscheduler(pid_t pid , int policy , const struct sched_param *sp); sched_getparam() Retrieves the scheduling parameters of a scheduling policy. sched_setparam() Sets the parameters associated with a scheduling policy that has been already set and can be verified using the sched_getparam() function. sched_get_priority_max() Returns the maximum valid priority associated with the scheduling policy. sched_get_priority_min() Returns the minimum valid priority associated with the scheduling policy . sched_rr_get_interval() Displays the allocated timeslice for each process.

Commands:
chrt -p 468 pid 468's current scheduling policy: SCHED_FIFO pid 468's current scheduling priority: 85
grep voluntary /proc/1000/status voluntary_ctxt_switches: 194529 nonvoluntary_ctxt_switches: 195338
4.7. Set the Transaction Wrapping Mode You can set the transaction mode as a property when you establish the connection using: the autoCommitTxn property in the connection URL (see Section 1.9, "Connection Properties for the Driver and Data Source Classes" ), the setAutoCommitTxn method (see Section 1.9, "Connection Properties for the Driver and Data Source Classes" ), or on a per-query basis, using the SET statement with the PROP_TXN_AUTO_WRAP property (see Section 3.5, "Execution Properties" ).

Commands:
Chapter 8. Important links Red Hat AMQ Broker 7.8 Release Notes Red Hat AMQ Broker 7.7 Release Notes Red Hat AMQ Broker 7.6 Release Notes Red Hat AMQ Broker 7.1 to 7.5 Release Notes (aggregated) Red Hat AMQ 7 Supported Configurations Red Hat AMQ 7 Component Details Revised on 2022-07-07 11:41:10 UTC

Commands:
5.3. Model Extension Definition Registry (MED Registry) A MED registry keeps track of all the MEDs that are registered in a workspace. Only registered MEDs can be used to extend a model. There are three different types of MEDs stored in the registry: Built-In MED - these are registered during Teiid Designer installation. These MEDs cannot be updated or unregistered by the user. Local MED - these are created or imported by the user. These MEDs can be updated, registered, and unregistered by the user. Imported MED - these are imported automatically when the server starts for the first time. Any functions that depend on these MEDs are available after the server starts for the first time. The MED Registry state is persisted and is restored each time a new session is started.

Commands:
Chapter 6. Updating RHEL 8 content With YUM , you can check if your system has any pending updates. You can list packages that need updating and choose to update a single package, multiple packages, or all packages at once. If any of the packages you choose to update have dependencies, these dependencies are updated as well. 6.1. Checking for updates To identify which packages installed on your system have available updates, you can list them. Procedure Check the available updates for installed packages: The output returns the list of packages and their dependencies that have an update available. 6.2. Updating packages You can use YUM to update a single package or all packages and their dependencies at once. Important When applying updates to kernel, YUM always installs a new kernel regardless of whether you are using the yum update or yum install command. Note that this only applies to packages identified by using the installonlypkgs YUM configuration option. Such packages include, for example, the kernel , kernel-core , and kernel-modules packages. Depending on your scenario, use one of the following options to apply updates: To update all packages and their dependencies, enter: To update a single package, enter: Important If you upgraded the GRUB boot loader packages on a BIOS or IBM Power system, reinstall GRUB. See Reinstalling GRUB . 6.3. Updating package groups Package groups bundle multiple packages, and you can use package groups to update all packages assigned to a group in a single step. Procedure Update packages from a specific package group: Important If you upgraded the GRUB boot loader packages on a BIOS or IBM Power system, reinstall GRUB. See Reinstalling GRUB . 6.4. Updating security-related packages You can use YUM to update packages that have security errata. Procedure Depending on your scenario, use one of the following options to apply updates: To upgrade to the latest available packages that have security errata, enter: To upgrade to the last security errata packages, enter: Important If you upgraded the GRUB boot loader packages on a BIOS or IBM Power system, reinstall GRUB. See Reinstalling GRUB . Additional resources Managing and monitoring security updates

Commands:
yum check-update
yum update
yum update <package_name>
yum group update <group_name>
yum update --security
yum update-minimal --security
4.2.5. Monitoring Reads and Writes to a File This section describes how to monitor reads from and writes to a file in real time. inodewatch.stp inodewatch.stp takes the following information about the file as arguments on the command line: The file's major device number. The file's minor device number. The file's inode number. To get this information, use stat -c '%D %i' filename , where filename is an absolute path. For instance: if you wish to monitor /etc/crontab , run stat -c '%D %i' /etc/crontab first. This gives the following output: 805 is the base-16 (hexadecimal) device number. The lower two digits are the minor device number and the upper digits are the major number. 1078319 is the inode number. To start monitoring /etc/crontab , run stap inodewatch.stp 0x8 0x05 1078319 (The 0x prefixes indicate base-16 values). The output of this command contains the name and ID of any process performing a read/write, the function it is performing (that is vfs_read or vfs_write ), the device number (in hex format), and the inode number. Example 4.9, "inodewatch.stp Sample Output" contains the output of stap inodewatch.stp 0x8 0x05 1078319 (when cat /etc/crontab is executed while the script is running) : Example 4.9. inodewatch.stp Sample Output

Commands:
#! /usr/bin/env stap probe vfs.write, vfs.read { # dev and ino are defined by vfs.write and vfs.read if (dev == MKDEV(USD1,USD2) # major/minor device && ino == USD3) printf ("%s(%d) %s 0x%x/%u\n", execname(), pid(), probefunc(), dev, ino) }
805 1078319
cat(16437) vfs_read 0x800005/1078319 cat(16437) vfs_read 0x800005/1078319
8.3. ORBit2 8.3.1. RHBA-2014:1563 - ORBit2 bug fix update Updated ORBit2 packages that fix one bug are now available for Red Hat Enterprise Linux 6. The ORBit2 packages provide a high-performance Object Request Broker (ORB) for the Common Object Request Broker Architecture (CORBA). ORBit allows programs to send requests and receive replies from other programs, regardless of where the programs are located. CORBA is a standard that enables communication between program objects, regardless of the programming language and platform used. Bug Fix BZ# 784223 Due to improper synchronization between multiple threads when accessing shared data objects, the bonobo-activation-server process was in certain cases killed by the SIGSEGV signal. With this update, clean-up tasks on one thread have been deferred, so synchronization is no longer necessary. As a result, the process does not crash anymore in the described scenario. Users of ORBit2 are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Creating the first administrator After installing Red Hat build of Keycloak, you need an administrator account that can act as a super admin with full permissions to manage Red Hat build of Keycloak. With this account, you can log in to the Red Hat build of Keycloak Admin Console where you create realms and users and register applications that are secured by Red Hat build of Keycloak. 2.1. Creating the account on the local host If your server is accessible from localhost , perform these steps. Procedure In a web browser, go to the http://localhost:8080 URL. Supply a username and password that you can recall. Welcome page 2.2. Creating the account remotely If you cannot access the server from a localhost address or just want to start Red Hat build of Keycloak from the command line, use the KC_BOOTSTRAP_ADMIN_USERNAME and KC_BOOTSTRAP_ADMIN_PASSWORD environment variables to create an initial admin account. For example: export KC_BOOTSTRAP_ADMIN_USERNAME=<username> export KC_BOOTSTRAP_ADMIN_PASSWORD=<password> bin/kc.[sh|bat] start

Commands:
export KC_BOOTSTRAP_ADMIN_USERNAME=<username> export KC_BOOTSTRAP_ADMIN_PASSWORD=<password> bin/kc.[sh|bat] start
Chapter 2. Support Only the configuration options described in this documentation are supported for the logging subsystem. Do not use any other configuration options, as they are unsupported. Configuration paradigms might change across OpenShift Container Platform releases, and such cases can only be handled gracefully if all configuration possibilities are controlled. If you use configurations other than those described in this documentation, your changes will be overwritten, because Operators are designed to reconcile any differences. Note If you must perform configurations not described in the OpenShift Container Platform documentation, you must set your Red Hat OpenShift Logging Operator to Unmanaged . An unmanaged OpenShift Logging environment is not supported and does not receive updates until you return OpenShift Logging to Managed . Note The logging subsystem for Red Hat OpenShift is provided as an installable component, with a distinct release cycle from the core OpenShift Container Platform. The Red Hat OpenShift Container Platform Life Cycle Policy outlines release compatibility. The logging subsystem for Red Hat OpenShift is an opinionated collector and normalizer of application, infrastructure, and audit logs. It is intended to be used for forwarding logs to various supported systems. The logging subsystem for Red Hat OpenShift is not: A high scale log collection system Security Information and Event Monitoring (SIEM) compliant Historical or long term log retention or storage A guaranteed log sink Secure storage - audit logs are not stored by default

Commands:
4.132. libesmtp 4.132.1. RHEA-2011:1775 - libesmtp enhancement update An updated libesmtp package that adds one enhancement is now available for Red Hat Enterprise Linux 6. LibESMTP is a library to manage posting or submitting electronic mail using SMTP to a preconfigured Mail Transport Agent (MTA). The libesmtp package is required by Open MPI. Enhancement BZ# 738760 Previously, LibESMTP was not shipped with Red Hat Enterprise Linux 6 on the 64-bit PowerPC platform. This update adds the LibESMTP package to the 64-bit PowerPC variant, as a requirement of the updated OpenMPI. Note, that this update does not contain any changes for other architectures. All users requiring libesmtp on the 64-bit PowerPC architecture are advised to install this package, which adds this enhancement.

Commands: