mtpti5iD/redhat-docs_dataset huggingface dataset:
7.39. dhcp 7.39.1. RHSA-2013:0504 - Low: dhcp security and bug fix update Updated dhcp packages that fix one security issue and two bugs are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having low 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 dhcp packages provide the Dynamic Host Configuration Protocol (DHCP) that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. Security Fix CVE-2012-3955 A flaw was found in the way the dhcpd daemon handled the expiration time of IPv6 leases. If dhcpd's configuration was changed to reduce the default IPv6 lease time, lease renewal requests for previously assigned leases could cause dhcpd to crash. Bug Fixes BZ# 803540 Prior to this update, the DHCP server discovered only the first IP address of a network interface if the network interface had more than one configured IP address. As a consequence, the DHCP server failed to restart if the server was configured to serve only a subnet of the following IP addresses. This update modifies network interface addresses discovery code to find all addresses of a network interface. The DHCP server can also serve subnets of other addresses. BZ# 824622 Prior to this update, the dhclient rewrote the /etc/resolv.conf file with backup data after it was stopped even when the PEERDNS flag was set to "no" before shut down if the configuration file was changed while the dhclient ran with PEERDNS=yes. This update removes the backing up and restoring functions for this configuration file from the dhclient-script. Now, the dhclient no longer rewrites the /etc/resolv.conf file when stopped. All users of DHCP are advised to upgrade to these updated packages, which fix these issues. After installing this update, all DHCP servers will be restarted automatically. 7.39.2. RHBA-2013:1255 - dhcp bug fix update Updated dhcp packages that fix one bug are now available for Red Hat Enterprise Linux 6. The Dynamic Host Configuration Protocol (DHCP) is a protocol that allows individual devices on an IP network to get their own network configuration information, including an IP address, a subnet mask, and a broadcast address. The dhcp packages provide a relay agent and ISC DHCP service required to enable and administer DHCP on a network. Bug Fix BZ# 1005672 Previously, the dhcpd daemon or dhclient tool were started to serve on an alias interface for Infiniband network interface card. Consequently, dhcpd/dhclient terminated unexpectedly. One of patches was improved to cover this specific case, thus fixing the bug. Now, both dhcpd and dhclient run correctly. All users of dhcp are advised to upgrade to these updated packages, which fix this bug.

Commands:
1.3.2. Creating a New Repository A CVS repository is a central place to store files and directories that are under revision control, as well as additional data such as a complete history of changes or information about who made those changes and when. A typical CVS repository stores multiple projects in separate subdirectories called modules . When publicly accessible, it allows several developers to create a working copy of any of the modules, make changes, and share these changes with others by committing them back to the repository. Initializing an Empty Repository To create a new, empty CVS repository in a directory of your choice, run the following command: cvs -d path init Note that path must be an absolute path to the directory in which you want to store the repository (for example, /var/cvs/ ). Alternatively, you can specify this path by changing the value of the USDCVSROOT environment variable: export CVSROOT= path This allows you to omit the path from cvs init and other CVS-related commands: cvs init Example 1.15. Initializing a new CVS repository To create an empty CVS repository in the ~/cvs/ directory, type: Importing Data to a Repository To put an existing project under revision control, change to the directory in which the project is stored and run the following command: cvs [ -d cvs_repository ] import [ -m " commit message " ] module vendor_tag release_tag Note that cvs_repository is a path to the CVS repository, module is the subdirectory in which you want to import the project (such as project ), and vendor_tag and release_tag are vendor and release tags. Example 1.16. Importing a project to a CVS repository Imagine that the directory with your project has the following contents: Also imagine that you have an empty CVS repository in ~/cvs/ . To import the project under project in this repository with vendor tag mycompany and release tag init , type:

Commands:
~]USD export CVSROOT=~/cvs ~]USD cvs init
~]USD ls myproject AUTHORS doc INSTALL LICENSE Makefile README src TODO
myproject]USD export CVSROOT=~/cvs myproject]USD cvs import -m "Initial import." project mycompany init N project/Makefile N project/AUTHORS N project/LICENSE N project/TODO N project/INSTALL
7.110. libdbi 7.110.1. RHBA-2013:0326 - libdbi bug fix update Updated libdbi packages that fix one bug are now available for Red Hat Enterprise Linux 6. The libdbi packages provide implementation of a database-independent abstraction layer in the C language. This framework allows programmers to write one generic set of code that works with multiple databases and multiple simultaneous database connections. Bug Fix BZ#733413 Previously, when processing query results, the last row of a query result was not freed due to an off-by-one logic error. This resulted in a memory leak that could become significant after processing a large number of query results. This update corrects an incorrect test condition in the underlying source code and memory leaks no longer occur in this scenario. All users of libdbi are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 1. Introduction Red Hat Single Sign-On (RH-SSO) 7.4 is based on the Keycloak project and provides security for your web applications by providing Web single sign-on capabilities based on popular standards such as SAML 2.0, OpenID Connect, and OAuth 2.0. The Red Hat Single Sign-On Server can act as a SAML or OpenID Connect-based identity provider, mediating with your enterprise user directory or third-party SSO provider for identity information and your applications using standards-based tokens. RH-SSO provides two operating modes: standalone server or managed domain. The standalone server operating mode represents running RH-SSO as a single server instance. The managed domain operating mode allows for the management of multiple RH-SSO instances from a single control point. The upgrade process differs depending on which operating mode has been implemented. Specific instructions for each mode are provided where applicable. The purpose of this guide is to document the steps that are required to successfully upgrade from Red Hat Single Sign-On 7.x to Red Hat Single Sign-On 7.4. 1.1. About Upgrades 1.1.1. Major Upgrades A major upgrade or migration is required when RH-SSO is upgraded from one major release to another, for example, from Red Hat Single Sign-On 7.2 to Red Hat Single Sign-On 8.0. There may be breaking API changes between major releases that could require rewriting parts of applications or server extensions. 1.1.2. Minor Updates Red Hat Single Sign-On periodically provides point releases, which are minor updates that include bug fixes, security fixes, and new features. If you plan to upgrade from one Red Hat Single Sign-On point release to another, for example, from Red Hat Single Sign-On 7.3 to Red Hat Single Sign-On 7.4, code changes should not be required for applications or custom server extensions as long as no private, unsupported, or tech preview APIs are used. 1.1.3. Micro Updates Red Hat Single Sign-On 7.4 also periodically provides micro releases that contain bug and security fixes. Micro releases increment the minor release version by the last digit, for example from 7.4.0 to 7.4.1. These releases do not require migration and should not impact the server configuration files. The patch management system for ZIP installations can also rollback the patch and server configuration. A micro release only contains the artifacts that have changed. For example if Red Hat Single Sign-On 7.4.1 contains changes to the server and the JavaScript adapter, but not the EAP adapter, only the server and JavaScript adapter are released and require updating. 1.2. Migration from Keycloak You can migrate to Red Hat Single Sign-On, the supported Red Hat product, from Keycloak, the community project. Prerequisites To learn about new features before the upgrade, review the changes . Verify that you have installed the correct version of Keycloak as a starting point. To migrate to Red Hat Single Sign-On 7.4, you need Keycloak 9.0.x. Procedure Perform the Minor Upgrades procedure. Although this procedure is labelled Minor Upgrade , the same steps apply for this migration. Perform the Adapter Upgrade procedure .

Commands:
14.5. Domain Commands A domain name is required for most of these commands as they manipulate the specified domain directly. The domain may be given as a short integer (0,1,2...), a name, or a full UUID. 14.5.1. Configuring a Domain to be Started Automatically at Boot USD virsh autostart [--disable] domain will automatically start the specified domain at boot. Using the --disable option disables autostart. In the example above, the rhel6 guest virtual machine will automatically start when the host physical machine boots In the example above, the autostart function is disabled and the guest virtual machine will no longer start automatically when the host physical machine boots.

Commands:
virsh autostart rhel6
virsh autostart rhel6 --disable
5.5.2.2. Adding a Member to a Running DLM Cluster That Contains More Than Two Nodes To add a member to an existing DLM cluster that is currently in operation, and contains more than two nodes, follow these steps: Add the node and configure fencing for it as in Section 5.5.1, "Adding a Member to a New Cluster" . Click Send to Cluster to propagate the updated configuration to other running nodes in the cluster. Use the scp command to send the updated /etc/cluster/cluster.conf file from one of the existing cluster nodes to the new node. Start cluster services on the new node by running the following commands in this order: service ccsd start service cman start service fenced start service clvmd start , if CLVM has been used to create clustered volumes service gfs start , if you are using Red Hat GFS service rgmanager start , if the cluster is running high-availability services ( rgmanager ) Start system-config-cluster (refer to Section 5.2, "Starting the Cluster Configuration Tool " ). At the Cluster Configuration Tool tab, verify that the configuration is correct. At the Cluster Status Tool tab verify that the nodes and services are running as expected. Note Make sure to configure other parameters that may be affected by changes in this section. Refer to Section 5.1, "Configuration Tasks" .

Commands:
Appendix A. YAML for the Skupper policy CRD The policy system allows a cluster administrator restrict Skupper usage on a cluster. It is not required for typical Skupper usage. The following YAML applies the Skupper policy CRD to a cluster.

Commands:
--- apiVersion: apiextensions.k8s.io/v1 kind: CustomResourceDefinition metadata: name: skupperclusterpolicies.skupper.io spec: group: skupper.io versions: - name: v1alpha1 served: true storage: true schema: openAPIV3Schema: type: object properties: spec: type: object properties: namespaces: type: array items: type: string allowIncomingLinks: type: boolean allowedOutgoingLinksHostnames: type: array items: type: string allowedExposedResources: type: array items: type: string allowedServices: type: array items: type: string scope: Cluster names: plural: skupperclusterpolicies singular: skupperclusterpolicy kind: SkupperClusterPolicy --- apiVersion: rbac.authorization.k8s.io/v1 kind: ClusterRole metadata: labels: application: skupper-service-controller name: skupper-service-controller rules: - apiGroups: - skupper.io resources: - skupperclusterpolicies verbs: - get - list - watch - apiGroups: - "" resources: - namespaces verbs: - get
3.12. RFKill Many computer systems contain radio transmitters, including Wi-Fi, Bluetooth, and 3G devices. These devices consume power, which is wasted when the device is not in use. RFKill is a subsystem in the Linux kernel that provides an interface through which radio transmitters in a computer system can be queried, activated, and deactivated. When transmitters are deactivated, they can be placed in a state where software can reactive them (a soft block ) or where software cannot reactive them (a hard block ). The RFKill core provides the API for the subsystem. Kernel drivers that have been designed to support RFkill use this API to register with the kernel, and include methods for enabling and disabling the device. Additionally, the RFKill core provides notifications that user applications can interpret and ways for user applications to query transmitter states. The RFKill interface is located at /dev/rfkill which contains the current state of all radio transmitters on the system. Each device has its current RFKill state registered in sysfs . Additionally, RFKill issues uevents for each change of state in an RFKill-enabled device. rfkill is a command-line tool with which you can query and change RFKill-enabled devices on the system. To obtain the tool, install the rfkill package. Use the command rfkill list to obtain a list of devices, each of which has an index number associated with it, starting at 0 . You can use this index number to tell rfkill to block or unblock a device. Example 3.2. Blocking a RFKill-enabled Device Run the following command to block the first RFKill-enabled device on the system: You can also use rfkill to block certain categories of devices. This command blocks all Wi-Fi devices on the system: To block all RFKill-enabled devices, run: To unblock RFKill-enabled devices, execute: To obtain a full list of device categories that rfkill can block, run: For more information on rkfill , see the rfkill(1) man page.

Commands:
rfkill block 0
rfkill block wifi
rfkill block all
rfkill unblock
rfkill help
Chapter 3. Planned changes to naming convention for Windows build artifacts From October 2024 onward, Red Hat plans to introduce naming changes for some files that are distributed as part of Red Hat build of OpenJDK releases for Windows Server platforms. These file naming changes will affect both the .zip archive and .msi installers that Red Hat provides for the JDK, JRE and debuginfo packages for Red Hat build of OpenJDK versions 8, 11, and 17. The aim of this change is to adopt a common naming convention that is consistent across all versions of OpenJDK that Red Hat supports. Red Hat build of OpenJDK versions 8, 11, and 17 will be aligned with the naming convention that Red Hat has already adopted for Red Hat build of OpenJDK 21. This means that Red Hat build of OpenJDK 21 will not require any naming changes. These planned changes do not affect the files for the Linux portable builds of any Red Hat build of OpenJDK version. Red Hat build of OpenJDK 17.0.12 is the last release where Red Hat plans to use the old naming convention for Windows artifacts. The following list provides an example of how the planned naming changes will affect each file for future releases of Red Hat build of OpenJDK 17: MSI installer for JDK package Old file name: java-17-openjdk- <version> .win.x86_64.msi New file name: java-17-openjdk- <version> .win.jdk.x86_64.msi .zip archive for JDK package Old file name: java-17-openjdk- <version> .win.x86_64.zip New file name: java-17-openjdk- <version> .win.jdk.x86_64.zip MSI installer for JRE package Old file name: java-17-openjdk- <version> .jre.win.x86_64.msi New file name: java-17-openjdk- <version> .win.jre.x86_64.msi .zip archive for for JRE package Old file name: java-17-openjdk- <version> .jre.win.x86_64.zip New file name: java-17-openjdk- <version> .win.jre.x86_64.zip .zip archive for debuginfo package Old file name: java-17-openjdk- <version> .win.x86_64.debuginfo.zip New file name: java-17-openjdk- <version> .win.debuginfo.x86_64.zip

Commands:
Chapter 7. alarming This chapter describes the commands under the alarming command. 7.1. alarming capabilities list List capabilities of alarming service Usage: Table 7.1. Command arguments Value Summary -h, --help Show this help message and exit Table 7.2. Output formatter options Value Summary -f {json,shell,table,value,yaml}, --format {json,shell,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated to show multiple columns Table 7.3. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 7.4. Shell formatter options Value Summary --prefix PREFIX Add a prefix to all variable names Table 7.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack alarming capabilities list [-h] [-f {json,shell,table,value,yaml}] [-c COLUMN] [--noindent] [--prefix PREFIX] [--max-width <integer>] [--fit-width] [--print-empty]
7.93. irqbalance 7.93.1. RHBA-2013:0367 - irqbalance bug fix and enhancement update Updated irqbalance packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The irqbalance packages provide a daemon that evenly distributes interrupt request (IRQ) load across multiple CPUs for enhanced performance. Note The irqbalance packages have been upgraded to upstream version 1.0.4, which provides a number of bug fixes and enhancements over the version. Among other changes, the irqbalance daemon has been enhanced to support multiple MSI-X interrupts for PCI devices, which significantly boosts speed of devices producing high-rate interrupts, such as network cards. Also, the irqbalance logic has been modified to consider PCI bus topology when making IRQ mapping decisions. (BZ#789946) Bug Fixes BZ# 813078 The irqbalance(1) man page did not contain documentation for the IRQBALANCE_BANNED_CPUS environment variable. This update adds the extensive documentation to this man page. BZ#843379 The irqbalance daemon assigns each interrupt source in the system to a "class", which represents the type of the device (for example Networking, Storage or Media). Previously, irqbalance used the IRQ handler names from the /proc/interrupts file to decide the source class, which caused irqbalance to not recognize network interrupts correctly. As a consequence, systems that use NIC biosdevnames did not have their hardware interrupts distributed and pinned as expected. With this update, the device classification mechanism has been improved, which ensures a better interrupts distribution. BZ# 860627 Previously, the irqbalance init script started the irqbalance daemon with the "--foreground" option, which caused irqbalance to become unresponsive. With this update, the "--foreground" option has been removed from the init script and irqbalance now starts as expected. All users of irqbalance are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
8.259. x3270 8.259.1. RHBA-2014:1494 - x3270 bug fix update Updated x3270 packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The x3270 packages contain files needed for emulating the IBM 3278 and 3279 terminals, commonly used with mainframe applications. Bug Fixes BZ# 1070750 Prior to this update, the x3270 application entered a loop when it was executed with the "-script" option. As a consequence, x3270 terminated unexpectedly with a segmentation fault. With this update, x3270 no longer enters a loop in the above circumstances, and the crash thus no longer occurs. BZ# 961111 Due to an error in the underlying code, some Program Function (PF) keys did not work correctly in the X3270 interface. This error has been fixed and the affected PF keys now work as expected. Users of x3270 are advised to upgrade to these updated packages, which fix these bugs.

Commands:
F.2.2.2. Boot Loaders for Other Architectures Once the kernel loads and hands off the boot process to the init command, the same sequence of events occurs on every architecture. So the main difference between each architecture's boot process is in the application used to find and load the kernel. For example, the IBM eServer pSeries architecture uses yaboot , and the IBM System z systems use the z/IPL boot loader. Consult the sections of this guide specific to these platforms for information on configuring their boot loaders.

Commands:
8.24. c-ares 8.24.1. RHBA-2014:1478 - c-ares bug fix and enhancement update Updated c-ares packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The c-ares C library defines asynchronous DNS (Domain Name System) requests and provides name resolving API. Note The c-ares packages have been upgraded to upstream version 1.10.0, which provides a number of bug fixes and enhancements over the version. (BZ# 1077544 ) Users of c-ares are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands: