mtpti5iD/redhat-docs_dataset huggingface dataset:
22.15. Configure ntpdate Servers The purpose of the ntpdate service is to set the clock during system boot. This can be used to ensure that the services started after ntpdate will have the correct time and will not observe a jump in the clock. The use of ntpdate and the list of step-tickers is considered deprecated and so Red Hat Enterprise Linux 6 uses the -g option to the ntpd command by default and not ntpdate . However, the -g option only enables ntpd to ignore the offset limit of 1000s and attempt to synchronize the time. It does not guarantee the time will be correct when other programs or services are started. Therefore the ntpdate service can be useful when ntpd is disabled or if there are services which need to be started with the correct time and not observe a jump in the clock. To check if the ntpdate service is enabled to run at system start, issue the following command: To enable the service to run at system start, issue the following command as root : To configure ntpdate servers, using a text editor running as root, edit /etc/ntp/step-tickers to include one or more host names as follows: The number of servers listed is not very important as ntpdate will only use this to obtain the date information once when the system is starting. If you have an internal time server then use that host name for the first line. An additional host on the second line as a backup is sensible. The selection of backup servers and whether the second host is internal or external depends on your risk assessment. For example, what is the chance of any problem affecting the first server also affecting the second server? Would connectivity to an external server be more likely to be available than connectivity to internal servers in the event of a network failure disrupting access to the first server? The ntpdate service has a file that must contain a list of NTP servers to be used on system start. It is recommend to have at last four servers listed to reduce the chance of a " false ticker " (incorrect time source) influencing the quality of the time offset calculation. However, publicly accessible time sources are rarely incorrect.

Commands:
~]USD chkconfig --list ntpdate ntpdate 0:off 1:off 2:on 3:on 4:on 5:on 6:off
~]# chkconfig ntpdate on
clock1.example.com clock2.example.com
10.2.2. Main Server Configuration The main server configuration section of the configuration file sets up the main server, which responds to any requests that are not handled by a virtual host defined within a <VirtualHost> container. Values here also provide defaults for any <VirtualHost> containers defined. The directives used in this section have changed little between Apache HTTP Server 1.3 and version 2.0. If the main server configuration is heavily customized, it may be easier to modify the existing configuration file to suit Apache HTTP Server 2.0. Users with only lightly customized main server sections should migrate their changes into the default 2.0 configuration. 10.2.2.1. UserDir Mapping The UserDir directive is used to enable URLs such as http://example.com/~bob/ to map to a subdirectory within the home directory of the user bob , such as /home/bob/public_html/ . A side-effect of this feature allows a potential attacker to determine whether a given username is present on the system. For this reason, the default configuration for Apache HTTP Server 2.0 disables this directive. To enable UserDir mapping, change the directive in httpd.conf from: to the following: For more on this topic, refer to the following documentation on the Apache Software Foundation's website: http://httpd.apache.org/docs-2.0/mod/mod_userdir.html#userdir

Commands:
UserDir disable
UserDir public_html
Chapter 11. Editing applications You can edit the configuration and the source code of the application you create using the Topology view. 11.1. Prerequisites You have created and deployed an application on Red Hat OpenShift Service on AWS using the Developer perspective . You have logged in to the web console and have switched to the Developer perspective. 11.2. Editing the source code of an application using the Developer perspective You can use the Topology view in the Developer perspective to edit the source code of your application. Procedure In the Topology view, click the Edit Source code icon, displayed at the bottom-right of the deployed application, to access your source code and modify it. Note This feature is available only when you create applications using the From Git , From Catalog , and the From Dockerfile options. 11.3. Editing the application configuration using the Developer perspective You can use the Topology view in the Developer perspective to edit the configuration of your application. Note Currently, only configurations of applications created by using the From Git , Container Image , From Catalog , or From Dockerfile options in the Add workflow of the Developer perspective can be edited. Configurations of applications created by using the CLI or the YAML option from the Add workflow cannot be edited. Prerequisites Ensure that you have created an application using the From Git , Container Image , From Catalog , or From Dockerfile options in the Add workflow. Procedure After you have created an application and it is displayed in the Topology view, right-click the application to see the edit options available. Figure 11.1. Edit application Click Edit application-name to see the Add workflow you used to create the application. The form is pre-populated with the values you had added while creating the application. Edit the necessary values for the application. Note You cannot edit the Name field in the General section, the CI/CD pipelines, or the Create a route to the application field in the Advanced Options section. Click Save to restart the build and deploy a new image. Figure 11.2. Edit and redeploy application

Commands:
7.58. gcc-libraries 7.58.1. RHBA-2015:1429 - gcc-libraries bug fix and enhancement update Updated gcc-libraries packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The gcc-libraries packages contain various GNU Compiler Collection (GCC) runtime libraries, such as libatomic and libitm. Note The gcc-libraries packages have been upgraded to upstream version 5.0.0, which provides a number of bug fixes and enhancements over the version. These enhancements are required by the features that will be present in future releases of Red Hat Developer Toolset. Among other changes, a new package "libmpx" is now available, which contains Memory Protection Extensions runtime libraries. (BZ# 1201767 ) Users of gcc-libraries are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
5.368. xulrunner 5.368.1. RHSA-2012:1361 - Critical: xulrunner security update Updated xulrunner packages that fix one security issue are now available for Red Hat Enterprise Linux 5 and 6. The Red Hat Security Response Team has rated this update as having critical 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. XULRunner provides the XUL Runtime environment for applications using the Gecko layout engine. Security Fix CVE-2012-4193 A flaw was found in the way XULRunner handled security wrappers. A web page containing malicious content could possibly cause an application linked against XULRunner (such as Mozilla Firefox) to execute arbitrary code with the privileges of the user running the application. For technical details regarding this flaw, refer to the Mozilla security advisories: http://www.mozilla.org/security/known-vulnerabilities/firefoxESR.html Red Hat would like to thank the Mozilla project for reporting this issue. Upstream acknowledges moz_bug_r_a4 as the original reporter. All XULRunner users should upgrade to these updated packages, which correct this issue. After installing the update, applications using XULRunner must be restarted for the changes to take effect.

Commands:
20.16.9.13. Interface ROM BIOS configuration To specify the ROM BIOS configuration settings, use a management tool to make the following changes to the domain XML: ... <devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> <rom bar='on' file='/etc/fake/boot.bin'/> </interface> </devices> ... Figure 20.50. Interface ROM BIOS configuration For hypervisors which support it, you can change how a PCI Network device's ROM is presented to the guest virtual machine. The bar attribute can be set to on or off , and determines whether or not the device's ROM will be visible in the guest virtual machine's memory map. (In PCI documentation, the "rombar" setting controls the presence of the Base Address Register for the ROM). If no rom bar is specified, the qemu default will be used (older versions of qemu used a default of off , while newer qemus have a default of on ). The optional file attribute is used to point to a binary file to be presented to the guest virtual machine as the device's ROM BIOS. This can be useful to provide an alternative boot ROM for a network device.

Commands:
<devices> <interface type='network'> <source network='default'/> <target dev='vnet1'/> <rom bar='on' file='/etc/fake/boot.bin'/> </interface> </devices>
23.3. Creating an LDIF File with an Example CoS Definition Use the dsctl ldifgen cos-def command to create an LDIF file with a Class of Service (CoS) definition. For example, to create an LDIF file named /tmp/cos-definition.ldif that adds a classic CoS definition to the ou=cos definitions,dc=example,dc=com entry: For further details about the options used in the example and other options you can set to create the LDIF file, enter:

Commands:
dsctl instance_name ldifgen cos-def Postal_Def --type classic --parent "ou=cos definitions,dc=example,dc=com" --cos-specifier businessCatagory --cos-template "cn=sales,cn=classicCoS,dc=example,dc=com" --cos-attr postalcode telephonenumber --ldif-file /tmp/cos-definition.ldif
dsctl instance_name ldifgen cos-def --help
4.112. kabi-whitelists 4.112.1. RHEA-2011:1747 - kabi-whitelists enhancement update An updated kabi-whitelists package that adds various enhancements is now available for Red Hat Enterprise Linux 6. The kabi-whitelists package contains reference files documenting interfaces provided by the Red Hat Enterprise Linux 6 kernel that are considered to be stable by Red Hat kernel engineering, and safe for longer term use by third party loadable device drivers, as well as for other purposes. Enhancements BZ# 680469 The "pci_reset_function" symbol has been added to the Red Hat Enterprise Linux 6.2 kernel application binary interface (ABI) whitelists. BZ# 690479 The "aio_complete" and "aio_put_req" symbols have been added to the kernel ABI whitelists. BZ# 700406 The "__blk_end_request", "bdget_disk", "blk_limits_io_min", "blk_limits_io_opt", "blk_plug_device", "blk_queue_bounce", "blk_queue_max_discard_sectors", "blk_remove_plug", "blk_requeue_request", "jiffies_to_usecs", "prepare_to_wait_exclusive", "ipv6_ext_hdr", "lro_receive_frags", and "lro_vlan_hwaccel_receive_frags" symbols have been added to the kernel ABI whitelists. BZ# 700432 The "ipv6_ext_hdr", "lro_receive_frags", and "lro_vlan_hwaccel_receive_frags" symbols have been added to the kernel ABI whitelists. BZ# 702675 The "ipv6_ext_hdr", "lro_receive_frags", "lro_vlan_hwaccel_receive_frags", "netif_set_real_num_tx_queues", and "pci_find_ext_capability" symbols have been added to the kernel ABI whitelists. The only exception is "pci_find_ext_capability", which is not available for IBM System z. BZ# 703125 The "compat_alloc_user_space" symbol has been added to the kernel ABI whitelists. BZ# 730410 The "paca" symbol has been added to the kernel ABI whitelists for the 64-bit PowerPC architecture. BZ# 748520 The "dm_put_device", "enl_register_ops", "m_device_name", "m_unregister_target", "m_register_target", "m_table_get_mode", "m_table_get_md", "m_get_device", and "enl_register_family" symbols have been added to the kernel ABI whitelists. Note: It is not necessary to install the kabi-whitelists package in order to use Driver Updates. The kabi-whitelists package only provides reference files for use by those creating Driver Update packages, or for those who wish to enable support for verification of kernel ABI compatibility by installing the appropriate Yum plug-in. All users of kabi-whitelists are advised to upgrade to this updated package, which adds these enhancements.

Commands:
Chapter 5. Advisories related to this release The following advisories have been issued to bugfixes and CVE fixes included in this release. RHSA-2022:1435 RHSA-2022:1439 RHSA-2022:1440 RHSA-2022:1441 RHSA-2022:1442 RHSA-2022:1443 RHSA-2022:1444 RHBA-2022:1446 RHBA-2022:1447 Revised on 2024-05-09 16:46:44 UTC

Commands:
C.4.7. Add an Entry to /etc/fstab Add an entry to /etc/fstab. This is only necessary if you want to establish a persistent association between the device and a mountpoint. Use the decrypted device, /dev/mapper/<name> in the /etc/fstab file. In many cases it is desirable to list devices in /etc/fstab by UUID or by a filesystem label. The main purpose of this is to provide a constant identifier in the event that the device name (eg: /dev/sda4 ) changes. LUKS device names in the form of /dev/mapper/luks-<luks_uuid> are based only on the device's LUKS UUID, and are therefore guaranteed to remain constant. This fact makes them suitable for use in /etc/fstab . Note For details on the format of the /etc/fstab file, read the fstab(5) man page.

Commands:
8.74. gnupg2 8.74.1. RHBA-2014:0806 - gnupg2 bug fix update Updated gnupg2 packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The GNU Privacy Guard (GnuPG or GPG) is a tool for encrypting data and creating digital signatures, compliant with the proposed OpenPGP Internet standard and the S/MIME standard. Bug Fixes BZ# 638635 Previously, the secret key management daemon for GnuPG, gpg-agent, failed to encode a new iteration count value when it created a new protected key or changed an existing key. As a consequence, the key could not be unprotected and gpg-agent thus did not properly interact with a number of programs that use key decryption, such as KMail or Kleopatra. With this update, the new iteration count is encoded properly and the decryption of keys created or modified by gpg-agent no longer fails. BZ# 966493 Prior to this update, the GnuPG encryption and signing tool, gpg2, by default used CAST5, an encryption algorithm not approved by FIPS standards. Consequently, when gpg2 was run in FIPS mode, data encryption and decryption failed and caused gpg2 to terminate unexpectedly. With this update, GnuPG uses AES, a FIPS-approved encryption algorithm, and gpg2 data encryption and decryption in FIPS mode work as intended. BZ# 1006879 Previously, the GnuPG signature checking tool, gpgv2, did not correctly interact with the Libgcrypt library. As a consequence, when the gpgv command was used on a file, gpgv2 terminated unexpectedly. This update fixes the error and the gpgv command now functions correctly. BZ# 1078957 Prior to this update, GnuPG did not check for availability of the RIPEMD-160 hash function digest. Because the RIPEMD-160 algorithm is not approved by FIPS standards, GnuPG therefore terminated unexpectedly when the "gpg --verify" command was used in FIPS mode to verify a signature that contained a RIPEMD-160 hash. With this update, GnuPG properly checks for RIPEMD-160 support and the crash no longer occurs. Users of gnupg2 are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 1. Availability Red Hat provides a distribution of .NET that enables developers to create applications using the C#, Visual Basic, and F# languages and then deploy them on Red Hat Enterprise Linux (RHEL), Red Hat OpenShift Container Platform, or other platforms. A no-cost Red Hat Enterprise Linux Developer Subscription is available, including a full suite of tools for container development. For Red Hat Enterprise Linux 7, .NET 6.0 is available as the RPM rh-dotnet60 in the following repositories: RHEL 7 Server: rhel-7-server-dotnet-rpms RHEL 7 Workstation: rhel-7-workstation-dotnet-rpms RHEL 7 HPC: rhel-7-hpc-node-dotnet-rpms Full instructions for installing .NET 6.0 on Red Hat Enterprise Linux 7 are available in the Getting started with .NET on RHEL 7 guide. Important .NET on Red Hat Enterprise Linux 7 will no longer receive support or updates after 30 June 2024 . As such, Red Hat recommends either using RHEL 8-based .NET 6.0 containers on RHEL 7 after 30 June 2024 or upgrading to a more recent version of RHEL. For Red Hat Enterprise Linux 8, .NET 6.0 is available as the RPM dotnet-sdk-6.0 in the AppStream repositories. The AppStream repositories are enabled by default in RHEL 8. .NET 6.0 is available for aarch64 , s390x , and x86_64 architectures on Red Hat Enterprise Linux 8 and OpenShift Container Platform. Full instructions for installing .NET 6.0 on RHEL 8 are available in the Getting started with .NET on RHEL 8 guide.

Commands:
4.98. iprutils 4.98.1. RHEA-2011:1546 - iprutils bug fix and enhancement update An updated iprutils package that fixes various bugs and provides one enhancement is now available for Red Hat Enterprise Linux 6. The iprutils package provides utilities to manage and configure SCSI devices that are supported by the IBM Power RAID SCSI storage device driver. The iprutils package has been upgraded to upstream version 2.3.4, which provides support for the Serial Attached SCSI (SAS) vRAID functions. (BZ# 693816 ) Bug Fixes BZ# 694756 Due to a NULL pointer dereference, the iprconfig utility terminated unexpectedly with a segmentation fault when attempting to display hardware status. A patch has been applied to address this issue and hardware status is now displayed correctly. BZ# 703255 Previously, iprutils did not work correctly when performing RAID migration and asymmetric access functions on new adapters. With this update, array migration functionality is fixed. Now, iprutils can correctly perform the raid migration and asymmetric access functions. BZ# 741835 The find_multipath_vset routine used the ARRAY_SIZE() macro to calculate the length of the serial number. Previously, the length was calculated incorrectly, which could have led to false positives when looking for the corresponding vset. As a consequence, attempting to delete arrays failed: the target and the second array were set to be read/write protected, writing to both arrays was not possible, and the system had to be rebooted. To fix the problem, the IPR_SERIAL_NUM_LEN macro is now used instead of ARRAY_SIZE. BZ# 741835 With the maximum number of devices attached to one of the new Silicon Integrated Systems (SiS) 64-bit adapters, the configuration data could have grown over the buffer size. With this update, the buffer size has been increased, which fixes the problem and ensures room for any possible future growth. All users of iprutils are advised to upgrade to this updated package, which fixes these bugs and provides this enhancement.

Commands:
4.157. lohit-assamese-fonts 4.157.1. RHEA-2011:1138 - lohit-assamese-fonts enhancement update An updated lohit-assamese-fonts package which adds one enhancement is now available for Red Hat Enterprise Linux 6. The lohit-assamese-fonts package provides a free Assamese TrueType/OpenType font. Enhancement BZ# 691284 Unicode 6.0, the most recent major version of the Unicode standard, introduces the Indian Rupee Sign (U+20B9), the new official Indian currency symbol. With this update, the lohit-assamese-fonts package now includes a glyph for this new character. All users requiring the Indian rupee sign should install this updated package, which adds this enhancement.

Commands:
Chapter 4. Advisories related to this release The following advisories have been issued to bugfixes and to CVE fixes included in this release: RHSA-2022:6999 RHSA-2022:7000 RHSA-2022:7001 RHSA-2022:7051 RHSA-2022:7054 Revised on 2024-05-03 15:36:36 UTC

Commands:
Introduction This document provides information about installing, configuring and managing Red Hat High Availability Add-On components. Red Hat High Availability Add-On components allow you to connect a group of computers (called nodes or members ) to work together as a cluster. In this document, the use of the word cluster or clusters is used to refer to a group of computers running the Red Hat High Availability Add-On. The audience of this document should have advanced working knowledge of Red Hat Enterprise Linux and understand the concepts of clusters, storage, and server computing. For more information about Red Hat Enterprise Linux 6, see the following resources: Red Hat Enterprise Linux Installation Guide - Provides information regarding installation of Red Hat Enterprise Linux 6. Red Hat Enterprise Linux Deployment Guide - Provides information regarding the deployment, configuration and administration of Red Hat Enterprise Linux 6. For more information about the High Availability Add-On and related products for Red Hat Enterprise Linux 6, see the following resources: High Availability Add-On Overview - Provides a high-level overview of the Red Hat High Availability Add-On. Cluster Administration - Provides information about installing, configuring and managing the High Availability Add-On. Logical Volume Manager Administration - Provides a description of the Logical Volume Manager (LVM), including information on running LVM in a clustered environment. Global File System 2: Configuration and Administration - Provides information about installing, configuring, and maintaining Red Hat GFS2 (Red Hat Global File System 2), which is included in the Resilient Storage Add-On. DM Multipath - Provides information about using the Device-Mapper Multipath feature of Red Hat Enterprise Linux 6. Load Balancer Administration - Provides information on configuring high-performance systems and services with the Load Balancer Add-On, a set of integrated software components that provide Linux Virtual Servers (LVS) for balancing IP load across a set of real servers. Release Notes - Provides information about the current release of Red Hat products. Red Hat documents are available in HTML, PDF, and RPM versions on the Red Hat Enterprise Documentation CD and online at https://access.redhat.com/site/documentation/ . 1. Feedback If you spot a typo, or if you have thought of a way to make this manual better, we would love to hear from you. Please submit a report in Bugzilla: http://bugzilla.redhat.com/bugzilla/ . File the bug against the product Red Hat Enterprise Linux 6 and the component doc-Cluster_General . Be sure to mention the manual identifier: By mentioning this manual's identifier, we know exactly which version of the guide you have. If you have a suggestion for improving the documentation, try to be as specific as possible. If you have found an error, include the section number and some of the surrounding text so we can find it easily.

Commands:
Configuring_High_Availability_With_Pacemaker(EN)-6 (2017-1-4T16:26)