mtpti5iD/redhat-docs_dataset huggingface dataset:
7.210. redhat-rpm-config 7.210.1. RHBA-2013:0460 - redhat-rpm-config bug fix and enhancement update Updated redhat-rpm-config packages that fix two bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The redhat-rpm-config packages are used during the build of RPM packages to apply various default distribution options determined by Red Hat. It also provides a few Red Hat RPM macro customizations, such as those used during the building of Driver Update packages. Bug Fixes BZ#795577 The kmodtool script is a helper script for building kernel module RPMs. Previously, the "verrel" parameter in the kmodtool script returned the kernel version and variant string with a dangling sign ("."). With this update, the dangling sign has been removed from the "verrel" output. BZ#822073 The "brp-java-repack-jars" script was unable to correctly handle certain Java Archive (JAR) files. Those files set permissions on "exploded" directory hierarchies to non-standard permissions modes, such as "0000". With this update, standard user permissions are set correctly on the "exploded" directory hierarchy, which prevents certain errors from occurring, such as being unable to remove the directory tree when it is necessary to do so. Enhancements BZ# 669638 Previously, the number of parallel compilation jobs suggested by the %_smp_mflags macro was limited to maximum of 16 CPUs. This update introduces the %_smp_ncpus_max macro, which makes the CPU limit adjustable. BZ#869062 Previously, the /usr/lib/rpm/redhat/rpmrc file contained a leftover "macrofiles" line, which is ignored by later versions of RPM. With this update, the aforementioned line has been removed from rprmc to avoid confusion. All users of redhat-rpm-config are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 7. Monitoring Dashboard and Concepts The Monitoring Dashboard provides high level visual information on health, performance and utilization of cluster wide resources. 7.1. Dashboard Selector The Dashboard Selector is the primary navigation tool to move between different dashboards. Figure 7.1. Dashboard Selector 7.2. Dashboard Panels The Dashboard is composed of individual visualization blocks displaying different metrics and statistics termed as Panels. The panels exhibit different data based on the current status of the cluster component. Panels can be dragged and dropped and rearranged on the Dashboard. The following are the types of panels available to visualize monitoring data: Single Status Panel : The status panel displays the aggregated value of a series in e a single number data. For example, the Health, volume, snapshots are Singlestat panels. Figure 7.2. Single Status Panel Example Multiple Status Panel : The Multiple status panel displays multiple values of a data source. The multiple status panel displays: The severity of the component If the component is disabled Extra data in the panel about the component Figure 7.3. Multiple Status Panel Example Note If a multitple status panel displays Invalid Number as a status for a component, it indicates there is no data available to display from the time series database. Graph Panel : The Graph panel allows to visualize unrestrained amounts of metrics. The Connection Trend and the Throughput Trend are examples of Graph panel. Figure 7.4. Graph Panel Example Table Panel : The Graph panel allows to visualize unrestrained amounts of metrics. The Connection Trend and the Throughput Trend are examples of Graph panel. Figure 7.5. Table Panel Example 7.3. Dashboard Rows A row is a logical divider in a given Dashboard. The panels of the dashboard are arranged and organized in rows to give a streamlined look and visual. 7.4. Dashboard Color Codes The Dashboard panels text displays the following color codes to represent health status information: Green : Healthy Orange : Degraded Red : Unhealthy, Down, or Unavailable

Commands:
A.6. The VDSM Hook Domain XML Object When hook scripts are started, the _hook_domxml variable is appended to the environment. This variable contains the path of the libvirt domain XML representation of the relevant virtual machine. Several hooks are an exception to this rule, as outlined below. The _hook_domxml variable of the following hooks contains the XML representation of the NIC and not the virtual machine. *_nic_hotplug_* *_nic_hotunplug_* *_update_device *_device_create *_device_migrate_* Important The before_migration_destination and before_dehibernation hooks currently receive the XML of the domain from the source host. The XML of the domain at the destination will have various differences. The libvirt domain XML format is used by VDSM to define virtual machines. Details on the libvirt domain XML format can be found at http://libvirt.org/formatdomain.html . The UUID of the virtual machine may be deduced from the domain XML, but it is also available as the environment variable vmId.

Commands:
Chapter 7. Viewing and managing JMX domains and MBeans Java Management Extensions (JMX) is a Java technology that allows you to manage resources (services, devices, and applications) dynamically at runtime. The resources are represented by objects called MBeans (for Managed Bean). You can manage and monitor resources as soon as they are created, implemented, or installed. With the JMX plugin on the Fuse Console, you can view and manage JMX domains and MBeans. You can view MBean attributes, run commands, and create charts that show statistics for the MBeans. The JMX tab provides a tree view of the active JMX domains and MBeans organized in folders. You can view details and execute commands on the MBeans. Procedure To view and edit MBean attributes: In the tree view, select an MBean. Click the Attributes tab. Click an attribute to see its details. To perform operations: In the tree view, select an MBean. Click the Operations tab, expand one of the listed operations. Click Execute to run the operation. To view charts: In the tree view, select an item. Click the Chart tab.

Commands:
11.2.10. Other Interfaces Other common interface configuration files include the following: ifcfg-lo A local loopback interface is often used in testing, as well as being used in a variety of applications that require an IP address pointing back to the same system. Any data sent to the loopback device is immediately returned to the host's network layer. Warning The loopback interface script, /etc/sysconfig/network-scripts/ifcfg-lo , should never be edited manually. Doing so can prevent the system from operating correctly. ifcfg-irlan0 An infrared interface allows information between devices, such as a laptop and a printer, to flow over an infrared link. This works in a similar way to an Ethernet device except that it commonly occurs over a peer-to-peer connection. ifcfg-plip0 A Parallel Line Interface Protocol ( PLIP ) connection works much the same way as an Ethernet device, except that it utilizes a parallel port. Interface configuration files for Linux on System z include the following: ifcfg-hsiN A HiperSockets interface is an interface for high-speed TCP/IP communication within and across z/VM guest virtual machines and logical partitions (LPARs) on an IBM System z mainframe.

Commands:
Chapter 2. SQL Support 2.1. SQL Support Red Hat JBoss Data Virtualization supports SQL for issuing queries and for defining view transformations. JBoss Data Virtualization provides nearly all of the functionality of SQL-92 DML. SQL-99 and later features have been added as required. The following does not attempt to cover SQL exhaustively, but rather highlights usage of SQL within Red Hat JBoss Data Virtualization. See the appendix for the SQL grammar accepted by Red Hat JBoss Data Virtualization.

Commands:
Chapter 1. Red Hat Enterprise Linux 9 This section outlines the packages released for Red Hat Enterprise Linux 9. 1.1. Red Hat Satellite Client 6 for RHEL 9 x86_64 (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-x86_64-rpms repository. Table 1.1. Red Hat Satellite Client 6 for RHEL 9 x86_64 (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:5497 katello-agent 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:5497 puppet-agent 7.16.0-2.el9sat RHBA-2022:5497 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:5497 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:5497 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:5497 qpid-proton-c 0.35.0-2.el9 RHBA-2022:5497 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:5497 1.2. Red Hat Satellite Client 6 for RHEL 9 ppc64le (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-ppc64le-rpms repository. Table 1.2. Red Hat Satellite Client 6 for RHEL 9 ppc64le (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:5497 katello-agent 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:5497 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:5497 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:5497 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:5497 qpid-proton-c 0.35.0-2.el9 RHBA-2022:5497 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:5497 1.3. Red Hat Satellite Client 6 for RHEL 9 s390x (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-s390x-rpms repository. Table 1.3. Red Hat Satellite Client 6 for RHEL 9 s390x (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:5497 katello-agent 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:5497 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:5497 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:5497 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:5497 qpid-proton-c 0.35.0-2.el9 RHBA-2022:5497 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:5497 1.4. Red Hat Satellite Client 6 for RHEL 9 aarch64 (RPMs) The following table outlines the packages included in the satellite-client-6-for-rhel-9-aarch64-rpms repository. Table 1.4. Red Hat Satellite Client 6 for RHEL 9 aarch64 (RPMs) Name Version Advisory gofer 2.12.5-7.1.el9sat RHBA-2022:5497 katello-agent 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools 3.5.7-3.el9sat RHBA-2022:5497 katello-host-tools-tracer 3.5.7-3.el9sat RHBA-2022:5497 python3-gofer 2.12.5-7.1.el9sat RHBA-2022:5497 python3-gofer-proton 2.12.5-7.1.el9sat RHBA-2022:5497 python3-qpid-proton 0.35.0-2.el9 RHBA-2022:5497 qpid-proton-c 0.35.0-2.el9 RHBA-2022:5497 rubygem-foreman_scap_client 0.5.0-1.el9sat RHBA-2022:5497

Commands:
Appendix C. Using your subscription AMQ is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. C.1. Accessing your account Procedure Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. C.2. Activating a subscription Procedure Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. C.3. Downloading release files To access .zip, .tar.gz, and other release files, use the customer portal to find the relevant files for download. If you are using RPM packages or the Red Hat Maven repository, this step is not required. Procedure 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 entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ product. The Software Downloads page opens. Click the Download link for your component. C.4. Registering your system for packages To install RPM packages for this product on Red Hat Enterprise Linux, your system must be registered. If you are using downloaded release files, this step is not required. Procedure 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. For more information about registering your system, see one of the following resources: Red Hat Enterprise Linux 7 - Registering the system and managing subscriptions Red Hat Enterprise Linux 8 - Registering the system and managing subscriptions

Commands:
B.75. python B.75.1. RHBA-2011:0284 - python bug fix update Updated python packages that fix two bugs are now available for Red Hat Enterprise Linux 6. Python is an interpreted, interactive, object-oriented programming language often compared to Tcl, Perl, Scheme, or Java. Python includes modules, classes, exceptions, very high level dynamic data types and dynamic typing. Python supports interfaces to many system calls and libraries, as well as to various windowing systems such as X11, Motif, Tk, Mac, and MFC. Bug Fixes BZ# 668975 Prior to this update, Python programs that used "ulimit -n" to enable communication with large numbers of subprocesses could still monitor only 1024 file descriptors at a time, which caused an exception: ValueError: filedescriptor out of range in select() This was due to the subprocess module using the "select" system call. The module now uses the "poll" system call, removing this limitation. BZ# 671343 Due to the urllib2 module ignoring the "no_proxy" environment variable for the FTP scheme, programs such as Yum could erroneously access a proxy server for ftp:// URLs covered by a "no_proxy" exclusion. With this update, a patch has been applied to address this issue, and "no_proxy" is no longer ignored. All users of python are advised to upgrade to these updated packages, which resolve these issues.

Commands:
probe::sunrpc.sched.release_task Name probe::sunrpc.sched.release_task - Release all resources associated with a task Synopsis sunrpc.sched.release_task Values prot the IP protocol in the RPC call tk_flags the flags of the task vers the program version in the RPC call xid the transmission id in the RPC call prog the program number in the RPC call Description rpc_release_task function might not be found for a particular kernel. So, if we can't find it, just return '-1' for everything.

Commands:
4.4. Configuring Static Routes with ip commands As a system administrator, you can configure static routes using the ip route command. To display the IP routing table, use the ip route command. For example: The ip route commands take the following form: ip route [ add | del | change | append | replace ] destination-address See the ip-route(8) man page for more details on the options and formats. To add a static route to a host address, in other words to a single IP address: where 192.0.2.1 is the IP address of the host in dotted decimal notation, 10.0.0.1 is the hop address and interface is the exit interface leading to the hop. To add a static route to a network, in other words to an IP address representing a range of IP addresses: where 192.0.2.0 is the IP address of the destination network in dotted decimal notation and /24 is the network prefix. The network prefix is the number of enabled bits in the subnet mask. This format of network address slash network prefix length is sometimes referred to as classless inter-domain routing ( CIDR ) notation. To remove the assigned static route: Any changes that you make to the routing table using ip route do not persist across system reboots. To permanently configure static routes, you can configure them by creating a route- interface file in the /etc/sysconfig/network-scripts/ directory for the interface. For example, static routes for the enp1s0 interface would be stored in the /etc/sysconfig/network-scripts/route- enp1s0 file. Any changes that you make to a route- interface file do not take effect until you restart either the network service or the interface. The route- interface file has two formats: ip command arguments, see the section called "Static Routes Using the IP Command Arguments Format" . and network/netmask directives, see the section called "Static Routes Using the Network/Netmask Directives Format" . See the ip-route(8) man page for more information on the ip route command.

Commands:
~]USD ip route default via 192.168.122.1 dev ens9 proto static metric 1024 192.168.122.0/24 dev ens9 proto kernel scope link src 192.168.122.107 192.168.122.0/24 dev enp1s0 proto kernel scope link src 192.168.122.126
~]# ip route add 192.0.2.1 via 10.0.0.1 [ dev interface ]
~]# ip route add 192.0.2.0/24 via 10.0.0.1 [ dev interface ]
~]# ip route del 192.0.2.1
4.3.3. Determining Time Spent in Kernel and User Space This section illustrates how to determine the amount of time any given thread is spending in either kernel or user-space. thread-times.stp thread-times.stp lists the top 20 processes currently taking up CPU time within a 5-second sample, along with the total number of CPU ticks made during the sample. The output of this script also notes the percentage of CPU time each process used, as well as whether that time was spent in kernel space or user space. Example 4.13, "thread-times.stp Sample Output" contains a 5-second sample of the output for thread-times.stp : Example 4.13. thread-times.stp Sample Output

Commands:
#! /usr/bin/env stap probe perf.sw.cpu_clock!, timer.profile { // NB: To avoid contention on SMP machines, no global scalars/arrays used, // only contention-free statistics aggregates. tid=tid(); e=execname() if (!user_mode()) kticks[e,tid] <<< 1 else uticks[e,tid] <<< 1 ticks <<< 1 tids[e,tid] <<< 1 } global uticks, kticks, ticks global tids probe timer.s(5), end { allticks = @count(ticks) printf ("%16s %5s %7s %7s (of %d ticks)\n", "comm", "tid", "%user", "%kernel", allticks) foreach ([e,tid] in tids- limit 20) { uscaled = @count(uticks[e,tid])*10000/allticks kscaled = @count(kticks[e,tid])*10000/allticks printf ("%16s %5d %3d.%02d%% %3d.%02d%%\n", e, tid, uscaled/100, uscaled%100, kscaled/100, kscaled%100) } printf("\n") delete uticks delete kticks delete ticks delete tids }
tid %user %kernel (of 20002 ticks) 0 0.00% 87.88% 32169 5.24% 0.03% 9815 3.33% 0.36% 9859 0.95% 0.00% 3611 0.56% 0.12% 9861 0.62% 0.01% 11106 0.37% 0.02% 32167 0.08% 0.08% 3897 0.01% 0.08% 3800 0.03% 0.00% 2886 0.02% 0.00% 3243 0.00% 0.01% 3862 0.01% 0.00% 3782 0.00% 0.00% 21767 0.00% 0.00% 2522 0.00% 0.00% 3883 0.00% 0.00% 3775 0.00% 0.00% 3943 0.00% 0.00% 3873 0.00% 0.00%
Chapter 4. New Packages 4.1. RHEA-2012:0842 - new package: byzanz A new byzanz package is now available for Red Hat Enterprise Linux 6. The byzanz package contains an easy-to-use desktop recorder that can record to GIF images, Ogg Theora video (optionally with sound), and other formats. A GNOME panel applet and a command-line recording tool are also included in the package. This enhancement update adds the byzanz package to Red Hat Enterprise Linux 6. (BZ# 623262 ) All users who require byzanz are advised to install this new package.

Commands:
Chapter 16. Floating Disks 16.1. Floating Disk Elements The disks collection provides information about all disks in a Red Hat Virtualization environment. A user attaches and detaches disks from any virtual machine and floats them between virtual machines. An API user accesses this information through the rel="disks" link obtained from the entry point URI. The following table shows specific elements contained in a disks resource representation. Table 16.1. Elements for floating disks Element Type Description Properties link rel="statistics" relationship A link to the statistics sub-collection for a virtual machine's disk statistics. image_id GUID A reference to the virtual machine image stored on the defined storage domain. storage_domains Complex The storage domains associated with this disk. Each storage_domain element contains an id attribute with the associated storage domain's GUID. Update this element with POST to perform live migration of a disk from one data storage domain to another. size integer Size of the disk in bytes. provisioned_size integer The provisioned size of the disk in bytes. actual_size integer Actual size of the disk in bytes. status One of illegal , invalid , locked or ok The status of the disk device. These states are listed in disk_states under capabilities . interface enumerated The type of interface driver used to connect to the disk device. A list of enumerated values is available in capabilities . format enumerated The underlying storage format. A list of enumerated values is available in capabilities . Copy On Write (COW) allows snapshots, with a small performance overhead. Raw does not allow snapshots, but offers improved performance. sparse Boolean: true or false true if the physical storage for the disk should not be preallocated. bootable Boolean: true or false true if this disk is to be marked as bootable. shareable Boolean: true or false true to share the disk with multiple virtual machines. wipe_after_delete Boolean: true or false true if the underlying physical storage for the disk should be zeroed when the disk is deleted. This increases security but is a more intensive operation and may prolong delete times. propagate_errors Boolean: true or false true if disk errors should not cause virtual machine to be paused and, instead, disk errors should be propagated to the guest OS. quota id= GUID Sets a quota for the disk. lunStorage complex A reference to a direct LUN mapping for storage usage. Requires a storage element that contains iSCSI or FCP device details. active Boolean Defines if the disk is connected to the virtual machine. Important Search queries for disks based upon name require the alias search parameter instead of name .

Commands:
Chapter 4. Integrated applications Cryostat integrates with specific applications that can enhance how you analyze data from your JFR recording. 4.1. Viewing a JFR recording on Grafana Cryostat 2.4 integrates with the Grafana application, so you can plot JFR recording data in Grafana. You can view plot data in time interval sections to precisely analyze the performance of your target JVM application. Prerequisites Entered your authentication details for your Cryostat instance. Created a JFR recording. See Creating a JDK Flight Recorder (JFR) recording (Creating a JFR recording with Cryostat). Procedure Go to the Recordings menu or the Archives menu on your Cryostat instance. Depending on your needs, click either the Active Recordings tab or the Archived Recordings tab. Locate your JFR recording and then select the overflow menu. Figure 4.1. Overflow menu items available for an example JFR recording From the overflow menu, click the View in Grafana option. The Grafana application opens in a new web browser window. Click the sign-in icon on the Grafana dashboard. Determine your credentials by issuing the following commands in your terminal. You can also locate your credentials from the Grafana Secret custom resource (CR) on the Cryostat details page on Red Hat OpenShift. Figure 4.2. The Grafana Secret CR on the Cryostat details page on OpenShift Enter your credentials in the Grafana web console login page. A dashboard window opens and shows your JFR recording's data in various time-series plots. Optional: Interact with any plot by selecting a time-series segment on the plot. Grafana expands the on-screen data to show only the data for that time interval. Figure 4.3. Example of a Grafana dashboard with plotted graphs Revised on 2023-12-12 17:53:25 UTC

Commands:
<cryostat_name> =USD(kubectl get cryostat -o jsonpath='{USD.items[0].metadata.name}') get secret USD <cryostat_name> -grafana-basic -o jsonpath='{USD.data.GF_SECURITY_ADMIN_USER}' | base64 -d get secret USD <cryostat_name> -grafana-basic -o jsonpath='{USD.data.GF_SECURITY_ADMIN_PASSWORD}' | base64 -d