mtpti5iD/redhat-docs_dataset huggingface dataset:
3.5. Managing Groups via Command-Line Tools Groups are a useful tool for permitting co-operation between different users. There is a set of commands for operating with groups such as groupadd , groupmod , groupdel , or gpasswd . The files affected include /etc/group which stores group account information and /etc/gshadow , which stores secure group account information. 3.5.1. Creating Groups To add a new group to the system with default settings, the groupadd command is run at the shell prompt as root . Example 3.18. Creating a Group with Default Settings The groupadd command creates a new group called friends . You can read more information about the group from the newly-created line in the /etc/group file: Automatically, the group friends is attached with a unique GID (group ID) of 30005 and is not attached with any users. Optionally, you can set a password for a group by running gpasswd groupname . Alternatively, you can add command options with specific settings. If you, for example, want to specify the numerical value of the group's ID (GID) when creating the group, run the groupadd command with the -g option. Remember that this value must be unique (unless the -o option is used) and the value must be non-negative. Example 3.19. Creating a Group with Specified GID The command below creates a group named schoolmates and sets GID of 60002 for it: When used with -g and GID already exists, groupadd refuses to create another group with existing GID. As a workaround, use the -f option, with which groupadd creates a group, but with a different GID . You may also create a system group by attaching the -r option to the groupadd command. System groups are used for system purposes, which practically means that GID is allocated from 1 to 499 within the reserved range of 999. For more information on groupadd , see the groupadd(8) man pages.

Commands:
groupadd group_name
~]# groupadd friends
classmates:x:30005:
groupadd option(s) groupname
groupadd -g GID
~]# groupadd -g 60002 schoolmates
groupadd -f GID
groupadd -r group_name
Chapter 3. Block pools The OpenShift Data Foundation operator installs a default set of storage pools depending on the platform in use. These default storage pools are owned and controlled by the operator and cannot be deleted or modified. With OpenShift Container Platform, you can create multiple custom storage pools which map to storage classes that provide the following features: Enable applications with their own high availability to use persistent volumes with two replicas, potentially improving application performance. Save space for persistent volume claims using storage classes with compression enabled. Note Multiple block pools are not supported for external mode OpenShift Data Foundation clusters. 3.1. Creating a block pool Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure Click Storage Data Foundation . In the Storage systems tab, select the storage system and then click the BlockPools tab. Click Create Block Pool . Enter Pool name . Note Using 2-way replication data protection policy is not supported for the default pool. However, you can use 2-way replication if you are creating an additional pool. Select Data protection policy as either 2-way Replication or 3-way Replication . Optional: Select Enable compression checkbox if you need to compress the data. Enabling compression can impact application performance and might prove ineffective when data to be written is already compressed or encrypted. Data written before enabling compression is not compressed. Click Create . 3.2. Updating an existing pool Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure Click Storage Data Foundation . In the Storage systems tab, select the storage system and then click BlockPools . Click the Action Menu (...) at the end the pool you want to update. Click Edit Block Pool . Modify the form details as follows: Note Using 2-way replication data protection policy is not supported for the default pool. However, you can use 2-way replication if you are creating an additional pool. Change the Data protection policy to either 2-way Replication or 3-way Replication . Enable or disable the compression option. Enabling compression can impact application performance and might prove ineffective when data to be written is already compressed or encrypted. Data written before enabling compression is not compressed. Click Save . 3.3. Deleting a pool Use this procedure to delete a pool in OpenShift Data Foundation. Prerequisites You must be logged into the OpenShift Container Platform web console as an administrator. Procedure . Click Storage Data Foundation . In the Storage systems tab, select the storage system and then click the BlockPools tab. Click the Action Menu (...) at the end the pool you want to delete. Click Delete Block Pool . Click Delete to confirm the removal of the Pool. Note A pool cannot be deleted when it is bound to a PVC. You must detach all the resources before performing this activity.

Commands:
8.239. xorg-x11-drv-mga 8.239.1. RHBA-2013:1610 - xorg-x11-drv-mga bug fix update Updated xorg-x11-drv-mga packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The xorg-x11-drv-mga packages provide a video driver for Matrox G-series chipsets for the X.Org implementation of the X Window System. Bug Fixes BZ# 894959 Prior to this update, the graphical user interface could appear distorted on 19-inch monitors with the 16:9 ratio. The xorg-x11-drv-mga packages have been fixed, and so the distortion no longer occurs in this scenario. BZ# 918017 Previously, resolutions higher than 1440x900 were not available with Red Hat Enterprise Linux 6.4 using the MGA G200e chips. Consequently, the Matrox driver did not allow native resolutions to be reached for many monitors. With this update, the X Server no longer discards larger resolution modes, and resolutions higher than 1440x900 are now available. Users of xorg-x11-drv-mga are advised to upgrade to these updated packages, which fix these bugs.

Commands:
A.2. Investigating kinit Authentication Failures General Troubleshooting On the IdM client, display the debug messages from the kinit process: Verify that: The client forward record is correct both on the server and on the affected client: The server forward record is correct both on the server and on the affected client: The host server_IP_address command must return a fully qualified host name with a trailing dot at the end, such as: Review the /etc/hosts file on the client, and make sure that: All server entries in the file are correct In all server entries, the first name is a fully qualified domain name See also the section called "The /etc/hosts File" . Make sure you meet the other conditions in Section 2.1.5, "Host Name and DNS Configuration" . On the IdM server, make sure that the krb5kdc and dirsrv services are running: Review the Kerberos key distribution center (KDC) log: /var/log/krb5kdc.log . If the KDCs are hard-coded in the /etc/krb5.conf file (the file explicitly sets KDC directives and uses the dns_lookup_kdc = false setting), use the ipactl status command on each master server. Check the status of the IdM services on each server listed as KDC by the command: Troubleshooting Errors Cannot find KDC for realm If kinit authentication fails with an error that says Cannot find KDC for realm "EXAMPLE.COM" while getting initial credentials , it indicates that KDC is not running on the server or that the client has misconfigured DNS. In this situation, try these steps: If the DNS discovery is enabled in the /etc/krb5.conf file (the dns_lookup_kdc = true setting), use the dig utility to check whether the following records are resolvable: In the following example, one of the dig commands above failed with this output: The output indicated that the named service was not running on the master server. If DNS lookup fails, continue with the steps in Section A.6, "Troubleshooting DNS" . Related Information See Section C.2, "Identity Management Log Files and Directories" for descriptions of various Identity Management log files.

Commands:
KRB5_TRACE=/dev/stdout kinit admin
host client_fully_qualified_domain_name
host server_fully_qualified_domain_name
host server_IP_address
server.example.com.
systemctl status krb5kdc # systemctl status dirsrv.target
ipactl status Directory Service: RUNNING krb5kdc Service: RUNNING kadmin Service: RUNNING named Service: RUNNING httpd Service: RUNNING ipa-custodia Service: RUNNING ntpd Service: RUNNING pki-tomcatd Service: RUNNING ipa-otpd Service: RUNNING ipa-dnskeysyncd Service: RUNNING ipa: INFO: The ipactl command was successful
dig -t TXT _kerberos. ipa.example.com USD dig -t SRV _kerberos._udp. ipa.example.com USD dig -t SRV _kerberos._tcp. ipa.example.com
; <<>> DiG 9.11.0-P2-RedHat-9.11.0-6.P2.fc25 <<>> -t SRV _kerberos._tcp.ipa.server.example ;; global options: +cmd ;; connection timed out; no servers could be reached
34.2. Configuring the Subscription Service The products installed on a system (including the operating system itself) are covered by subscriptions . A subscription service is used to track registered systems, the products installed on those systems, and the subscriptions attached to the system to cover those products. The Subscription Management Registration screens identify which subscription service to use and, by default, attach the best-matched subscriptions to the system. More information about subscription management is available in the Red Hat Subscription Management guide. 34.2.1. Set Up Software Updates The first step is to select whether to register the system immediately with a subscription service. To register the system, select Yes, I'd like to register now , and click Forward . Figure 34.3. Set Up Software Updates Note Even if a system is not registered at firstboot, it can be registered with any of those three subscription services later, using the Red Hat Subscription Manager tools [13] . More information about the Red Hat Subscription Manager tools can be found in the Red Hat Subscription Management Guide . [13] Systems can also be registered with Satellite or RHN Classic. For Satellite information, see the Satellite documentation. For information on using RHN Classic, see the appendix in the Red Hat Subscription Management Guide .

Commands:
Chapter 3. Shenandoah garbage collector modes You can run Shenandoah in three different modes. Select a specific mode with the -XX:ShenandoahGCMode=<name> . The following list describes each Shenandoah mode: normal/satb (product, default) This mode runs a concurrent garbage collector (GC) with Snapshot-At-The-Beginning (SATB) marking. This marking mode does the similar work as G1, the default garbage collector for Red Hat build of OpenJDK 8. iu (experimental) This mode runs a concurrent GC with Incremental Update (IU) marking. It can reclaim unreachably memory more aggressively. This marking mode mirrors the SATB mode. This may make marking less conservative, especially around accessing weak references. passive (diagnostic) This mode runs Stop the World Event GCs. This mode is used for functional testing, but sometimes it is useful for bisecting performance anomalies with GC barriers, or to ascertain the actual live data size in the application.

Commands:
function::symdata Name function::symdata - Return the kernel symbol and module offset for the address. Synopsis Arguments addr The address to translate. General Syntax symdata:string(addr:long) Description Returns the (function) symbol name associated with the given address if known, the offset from the start and size of the symbol, plus module name (between brackets). If symbol is unknown, but module is known, the offset inside the module, plus the size of the module is added. If any element is not known it will be omitted and if the symbol name is unknown it will return the hex string for the given address.

Commands:
function symdata:string(addr:long)
Appendix A. Comparison between Ceph Ansible and Cephadm Cephadm is used for the containerized deployment of the storage cluster. The tables compare Cephadm with Ceph-Ansible playbooks for managing the containerized deployment of a Ceph cluster for day one and day two operations. Table A.1. Day one operations Description Ceph-Ansible Cephadm Installation of the Red Hat Ceph Storage cluster Run the site-container.yml playbook. Run cephadm bootstrap command to bootstrap the cluster on the admin node. Addition of hosts Use the Ceph Ansible inventory. Run ceph orch add host HOST_NAME to add hosts to the cluster. Addition of monitors Run the add-mon.yml playbook. Run the ceph orch apply mon command. Addition of managers Run the site-container.yml playbook. Run the ceph orch apply mgr command. Addition of OSDs Run the add-osd.yml playbook. Run the ceph orch apply osd command to add OSDs on all available devices or on specific hosts. Addition of OSDs on specific devices Select the devices in the osd.yml file and then run the add-osd.yml playbook. Select the paths filter under the data_devices in the osd.yml file and then run ceph orch apply -i FILE_NAME .yml command. Addition of MDS Run the site-container.yml playbook. Run the ceph orch apply FILESYSTEM_NAME command to add MDS. Addition of Ceph Object Gateway Run the site-container.yml playbook. Run the ceph orch apply rgw commands to add Ceph Object Gateway. Table A.2. Day two operations Description Ceph-Ansible Cephadm Removing hosts Use the Ansible inventory. Run ceph orch host rm HOST_NAME to remove the hosts. Removing monitors Run the shrink-mon.yml playbook. Run ceph orch apply mon to redeploy other monitors. Removing managers Run the shrink-mon.yml playbook. Run ceph orch apply mgr to redeploy other managers. Removing OSDs Run the shrink-osd.yml playbook. Run ceph orch osd rm OSD_ID to remove the OSDs. Removing MDS Run the shrink-mds.yml playbook. Run ceph orch rm SERVICE_NAME to remove the specific service. Exporting Ceph File System over NFS Protocol. Not supported on Red Hat Ceph Storage 4. Run ceph nfs export create command. Deployment of Ceph Object Gateway Run the site-container.yml playbook. Run ceph orch apply rgw SERVICE_NAME to deploy Ceph Object Gateway service. Removing Ceph Object Gateway Run the shrink-rgw.yml playbook. Run ceph orch rm SERVICE_NAME to remove the specific service. Block device mirroring Run the site-container.yml playbook. Run ceph orch apply rbd-mirror command. Minor version upgrade of Red Hat Ceph Storage Run the infrastructure-playbooks/rolling_update.yml playbook. Run ceph orch upgrade start command. Deployment of monitoring stack Edit the all.yml file during installation. Run the ceph orch apply -i FILE .yml after specifying the services. Additional Resources For more details on using the Ceph Orchestrator, see the Red Hat Ceph Storage Operations Guide .

Commands:
28.3. Time Zone Configuration The third tabbed window that appears is for configuring the system time zone. To configure the system time zone, click the Time Zone tab. The time zone can be changed by either using the interactive map or by choosing the desired time zone from the list below the map. To use the map, click on the desired region. The map zooms into the region selected, after which you may choose the city specific to your time zone. A red X appears and the time zone selection changes in the list below the map. Alternatively, you can also use the list below the map. In the same way that the map lets you choose a region before choosing a city, the list of time zones is now a treelist, with cities and countries grouped within their specific continents. Non-geographic time zones have also been added to address needs in the scientific community. Click OK to apply the changes and exit the program. If your system clock is set to use UTC, select the System clock uses UTC option. UTC stands for the Universal Time, Coordinated , also known as Greenwich Mean Time (GMT). Other time zones are determined by adding or subtracting from the UTC time.

Commands:
18.4. Actions 18.4.1. Allocate Virtual Machine Action The allocate virtual machine action allocates a virtual machine in the virtual machine pool. Example 18.5. Action to allocate a virtual machine from a virtual machine pool

Commands:
POST /ovirt-engine/api/vmpools/2d2d5e26-1b6e-11e1-8cda-001320f76e8e/allocatevm HTTP/1.1 Accept: application/xml Content-type: application/xml <action/>
7.65. gnutls 7.65.1. RHSA-2015:1457 - Moderate: gnutls security and bug fix update Updated gnutls packages that fix three security issues and one bug are now available for Red Hat Enterprise Linux 6. Red Hat Product Security has rated this update as having Moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which give detailed severity ratings, are available for each vulnerability from the CVE links in the References section. The GnuTLS library provides support for cryptographic algorithms and for protocols such as Transport Layer Security (TLS). Security Fixes CVE-2014-8155 It was found that GnuTLS did not check activation and expiration dates of CA certificates. This could cause an application using GnuTLS to incorrectly accept a certificate as valid when its issuing CA is already expired. CVE-2015-0282 It was found that GnuTLS did not verify whether a hashing algorithm listed in a signature matched the hashing algorithm listed in the certificate. An attacker could create a certificate that used a different hashing algorithm than it claimed, possibly causing GnuTLS to use an insecure, disallowed hashing algorithm during certificate verification. CVE-2015-0294 It was discovered that GnuTLS did not check if all sections of X.509 certificates indicate the same signature algorithm. This flaw, in combination with a different flaw, could possibly lead to a bypass of the certificate signature check. The CVE-2014-8155 issue was discovered by Marcel Kolaja of Red Hat. The CVE-2015-0282 and CVE-2015-0294 issues were discovered by Nikos Mavrogiannopoulos of the Red Hat Security Technologies Team. Bug Fix BZ# 1036385 Previously, under certain circumstances, the certtool utility could generate X.509 certificates which contained a negative modulus. Consequently, such certificates could have interoperation problems with the software using them. The bug has been fixed, and certtool no longer generates X.509 certificates containing a negative modulus. Users of gnutls are advised to upgrade to these updated packages, which contain backported patches to correct these issues.

Commands:
7.4. I/O Mode I/O mode options can be configured on a virtual machine during installation with virt-manager or the virt-install command, or on an existing guest by editing the guest XML configuration. Table 7.2. IO mode options Caching Option Description IO=native The default for Red Hat Enterprise Virtualization environments. This mode uses kernel asynchronous I/O with direct I/O options. IO=threads Sets the I/O mode to host user-mode based threads. IO=default Sets the I/O mode to the kernel default. In Red Hat Enterprise Linux 6, the default is IO=threads. In virt-manager , the I/O mode can be specified under Virtual Disk . For information on using virt-manager to change the I/O mode, see Section 3.4, "Virtual Disk Performance Options" To configure the I/O mode in the guest XML, use virsh edit to edit the io setting inside the driver tag, specifying native , threads , or default . For example, to set the I/O mode to threads : <disk type='file' device='disk'> <driver name='qemu' type='raw' io='threads'/> To configure the I/O mode when installing a guest using virt-install , add the io option to the --disk path parameter. For example, to configure io=threads during guest installation:

Commands:
<disk type='file' device='disk'> <driver name='qemu' type='raw' io='threads'/>
virt-install --disk path=/storage/images/USDNAME.img,io=threads,opt2=val2 .
Chapter 11. Configuring sound in GNOME You can configure sound volume and other sound options in GNOME. 11.1. Sound configuration tools in GNOME In RHEL 9, the PipeWire sound server handles sound output and input. PipeWire lets programs output the audio using the pipewire daemon. To configure sound, you can use one of the following graphical applications in GNOME: System menu The system menu is located in the top-right screen corner. It enables you only to set the intensity of the sound output or sound input through the sound bar. The sound bar for input sound is available only if you are running an application that is using an internal microphone (built-in audio), such as some teleconference tools. Settings Settings provides other general options to configure sound. Tweaks The Tweaks application enables you to configure only volume over-amplification. Additional resources For more information about PipeWire , see the pipewire man page on your system. 11.2. Accessing sound configuration in Settings This procedure opens the sound configuration screen in the Settings . Launch Settings . You can use one of the approaches described in Launching applications in GNOME . Alternatively, you can also launch it from the system menu by clicking on its icon. In Settings , choose Sound from the left vertical bar. 11.3. Sound options in Settings Through the Sound menu in Settings , you can configure the following sound options: Volume Levels The Volume levels section shows all currently running applications that can process sound, and allows you to amplify or lower the sound of a particular application. Output and Input The Output and Input sections show all built-in audio devices and external audio devices that are currently connected. Alert sound The Alert sound section shows different themes of system audio alerts. The Output section on the sound configuration screen

Commands: