mtpti5iD/redhat-docs_dataset huggingface dataset:
2.2. Data Roles All authenticated users have access to a VDB. To restrict access, configure data roles. Set these in the Teiid Designer or the dynamic VDB's META-INF/vdb.xml file. As part of the data role definition, you can map them to JAAS roles specified in <mapped-role-name> tags. You can set up JAAS roles using the web console. How these JAAS roles are associated with users depends on which particular JAAS login module you use. For instance, the default UsersRolesLoginModule associates users with JAAS roles in plain text files. For more information about data roles, see Red Hat JBoss Data Virtualization Development Guide: Reference Material . Important Do not use "admin" or "user" as JAAS role names as these are reserved specifically for Dashboard Builder permissions.

Commands:
6.4. Install Signed Packages from Well Known Repositories Software packages are published through repositories. All well known repositories support package signing. Package signing uses public key technology to prove that the package that was published by the repository has not been changed since the signature was applied. This provides some protection against installing software that may have been maliciously altered after the package was created but before you downloaded it. Using too many repositories, untrustworthy repositories, or repositories with unsigned packages has a higher risk of introducing malicious or vulnerable code into your system. Use caution when adding repositories to yum/software update.

Commands:
2.5.2. DLM Tuning Options: Increase DLM Table Sizes DLM uses several tables to manage, coordinate, and pass lock information between nodes in the cluster. Increasing the size of the DLM tables might increase performance. In Red Hat Enterprise Linux 6.1 and later, the default sizes of these tables have been increased, but you can manually increase them with the following commands: These commands are not persistent and will not survive a reboot, so you must add them to one of the startup scripts and you must execute them before mounting any GFS2 file systems, or the changes will be silently ignored. For more detailed information on GFS2 node locking, see Section 2.9, "GFS2 Node Locking" .

Commands:
echo 1024 > /sys/kernel/config/dlm/cluster/lkbtbl_size echo 1024 > /sys/kernel/config/dlm/cluster/rsbtbl_size echo 1024 > /sys/kernel/config/dlm/cluster/dirtbl_size
1.6. Red Hat JBoss Data Grid Cache Architecture Figure 1.1. Red Hat JBoss Data Grid Cache Architecture Red Hat JBoss Data Grid's cache infrastructure depicts the individual elements and their interaction with each other in each JBoss Data Grid Usage Mode (Library and Remote Client-Server). For clarity, each cache architecture diagram is separated into two parts: Elements that a user cannot directly interact with are depicted within a dark grey box in the diagram. In Remote Client-Server mode, this includes Persistent Store, Cache, Cache Manager, L1 Cache, and Server Module. In Library mode, user cannot directly interact with Persistent Store and L1 Cache. Elements that a user can interact directly with are depicted in a light grey box in the diagram. In Remote Client-Server mode, this includes the Application and the Cache Client. In Library mode, users are allowed to interact with the Cache and Cache Manager, as well as the Application. Cache Architecture Elements JBoss Data Grid's cache architecture includes the following elements: The Persistent Store is an optional component. It can permanently store the cached entries for restoration after a data grid shutdown. The Level 1 Cache (or L1 Cache) stores remote cache entries after they are initially accessed, preventing unnecessary remote fetch operations for each subsequent use of the same entries. The Cache Manager controls the life cycle of Cache instances and can store and retrieve them when required. The Cache is the main component for storage and retrieval of the key-value entries. Library and Remote Client-Server Mode Architecture In Library mode, the Application (user code) can interact with the Cache and Cache Manager components directly. In this case the Application resides in the same Java Virtual Machine (JVM) and can call Cache and Cache Manager Java API methods directly. In Remote Client-Server mode, the Application does not directly interact with the cache. Additionally, the Application usually resides in a different JVM, on different physical host, or does not need to be a Java Application. In this case, the Application uses a Cache Client that communicates with a remote JBoss Data Grid Server over the network using one of the supported protocols such as Memcached, Hot Rod, or REST. The appropriate server module handles the communication on the server side. When a request is sent to the server remotely, it translates the protocol back to the concrete operations performed on the cache component to store and retrieve data. Report a bug

Commands:
Chapter 3. Installing applications in GNOME This section describes various approaches that you can use to install a new application in GNOME 3. Prerequisites Administrator priveleges. 3.1. The GNOME Software application GNOME Software is an utility that enables you to install and update applications, software components, and GNOME Shell extensions in a graphical interface. GNOME Software provides a catalog of graphical applications, which are the applications that include a *.desktop file. The available applications are grouped into multiple categories according to their purpose. GNOME Software uses the PackageKit and Flatpak technologies as its back ends. 3.2. Installing an application using GNOME Software This procedure installs a graphical application using the GNOME Software installer. Procedure Launch the GNOME Software application. Find the application to be installed in the available categories: Audio & Video Communication & News Productivity Graphics & Photography Add-ons Add-ons include for example GNOME Shell extensions, codecs, or fonts. Developer Tools Utilities Click the selected application. Click the Install button. 3.3. Installing an application to open a file type This procedure installs an application that can open a given file type. Prerequisites You can access a file of the required file type in your file system. Procedure Try opening a file that is associated with an application that is currently not installed on your system. GNOME automatically identifies the suitable application that can open the file, and offers to download the application. 3.4. Installing an RPM package in GNOME This procedure installs an RPM software package that you manually downloaded as a file. Procedure Download the required RPM package. In the Files application, open the directory that stores the downloaded RPM package. Note By default, downloaded files are stored in the /home/ user /Downloads/ directory. Double-click the icon of the RPM package to install it. 3.5. Installing an application from the application search in GNOME This procedure installs a graphical application that you find in the GNOME application search. Procedure Open the Activities Overview screen. Start typing the name of the required application in the search entry. GNOME automatically finds the application in a repository, and displays the application's icon. Click the application's icon to open GNOME Software . Click the icon of the application again. Click Install to finish the installation in GNOME Software . 3.6. Additional resources For installing software on the command line, see Installing software with yum .

Commands:
Chapter 7. Security 7.1. Securing connections with SSL/TLS Red Hat build of Rhea uses SSL/TLS to encrypt communication between clients and servers. To connect to a remote server with SSL/TLS, set the transport connection option to tls . Example: Enabling SSL/TLS var opts = { host: "example.com", port: 5671, transport: "tls" }; container.connect(opts); Note By default, the client will reject connections to servers with untrusted certificates. This is sometimes the case in test environments. To bypass certificate authorization, set the rejectUnauthorized connection option to false . Be aware that this compromises the security of your connection. 7.2. Connecting with a user and password Red Hat build of Rhea can authenticate connections with a user and password. To specify the credentials used for authentication, set the username and password connection options. Example: Connecting with a user and password var opts = { host: "example.com", username: "alice" , password: "secret" }; container.connect(opts); 7.3. Configuring SASL authentication Red Hat build of Rhea uses the SASL protocol to perform authentication. SASL can use a number of different authentication mechanisms . When two network peers connect, they exchange their allowed mechanisms, and the strongest mechanism allowed by both is selected. Red Hat build of Rhea enables SASL mechanisms based on the presence of user and password information. If the user and password are both specified, PLAIN is used. If only a user is specified, ANONYMOUS is used. If neither is specified, SASL is disabled.

Commands:
var opts = { host: "example.com", port: 5671, transport: "tls" }; container.connect(opts);
var opts = { host: "example.com", username: "alice" , password: "secret" }; container.connect(opts);
Chapter 3. Uninstalling OpenShift AI You can use Red Hat OpenShift Cluster Manager to safely uninstall Red Hat OpenShift AI from your OpenShift cluster. Prerequisites Credentials for OpenShift Cluster Manager ( https://console.redhat.com/openshift/ ). Administrator access to the OpenShift cluster. For AWS clusters, you have backed up the EBS volume containing your Persistent Volume Claims (PVCs). See Amazon Web Services documentation: Create Amazon EBS snapshots for more information. For GCP clusters, you have backed up the persistent disk containing your Persistent Volume Claims (PVCs). See Google Cloud documentation: Create and manage disk snapshots for more information. Procedure Log in to OpenShift Cluster Manager ( https://console.redhat.com/openshift/ ). Click Clusters . The Clusters page opens. Click the name of the cluster that hosts the instance OpenShift AI to uninstall. The Details page for the cluster opens. Click the Add-ons tab and locate the Red Hat OpenShift Data Science tile. Click Uninstall . This process takes approximately 30 minutes to complete. Do not manually delete any resources while uninstalling OpenShift AI, as this can interfere with the uninstall process. OpenShift AI is uninstalled and any persistent volume claims (PVCs) associated with your OpenShift AI instance are deleted. However, any user groups for OpenShift AI that you previously created remain on your cluster. Verification In OpenShift Cluster Manager, on the Add-ons tab for the cluster, confirm that the OpenShift Data Science tile does not show the Installed state. In your OpenShift cluster, click Home Projects and confirm that the following project namespaces are not visible: redhat-ods-applications redhat-ods-monitoring redhat-ods-operator Additional resources Amazon Web Services documentation: Create Amazon EBS snapshots Google Cloud documentation: Create and manage disk snapshots Deleting users and user resources

Commands:
11.2.2. Specific ifcfg Options for Linux on System z SUBCHANNELS= <read_device_bus_id> , <write_device_bus_id> , <data_device_bus_id> where <read_device_bus_id> , <write_device_bus_id> , and <data_device_bus_id> are the three device bus IDs representing a network device. PORTNAME= myname; where myname is the Open Systems Adapter (OSA) portname or LAN Channel Station (LCS) portnumber. CTCPROT = answer where answer is one of the following: 0 - Compatibility mode, TCP/IP for Virtual Machines (used with non-Linux peers other than IBM S/390 and IBM System z operating systems). This is the default mode. 1 - Extended mode, used for Linux-to-Linux Peers. 3 - Compatibility mode for S/390 and IBM System z operating systems. This directive is used in conjunction with the NETTYPE directive. It specifies the CTC protocol for NETTYPE='ctc'. The default is 0. OPTION = 'answer' where 'answer' is a quoted string of any valid sysfs attributes and their value. The Red Hat Enterprise Linux installer currently uses this to configure the layer mode, (layer2), and the relative port number, (portno), of QETH devices. For example:

Commands:
OPTIONS='layer2=1 portno=0'
Preface The Package manifest document provides a package listing for Red Hat Enterprise Linux 7.9. Capabilities and limits of RHEL 7 as compared to other versions of the system are available in the Knowledgebase article Red Hat Enterprise Linux technology capabilities and limits . Information regarding the RHEL life cycle is provided in the Red Hat Enterprise Linux Life Cycle document. Detailed changes in each minor release of RHEL are documented in the Release notes .

Commands:
2.9. numastat The numastat tool displays memory statistics for processes and the operating system on a per-NUMA-node basis. By default, numastat displays per-node NUMA hit an miss system statistics from the kernel memory allocator. Optimal performance is indicated by high numa_hit values and low numa_miss values. Numastat also provides a number of command line options, which can show how system and process memory is distributed across NUMA nodes in the system. It can be useful to cross-reference per-node numastat output with per-CPU top output to verify that process threads are running on the same node to which memory is allocated. Numastat is provided by the numactl package. For details about how to use numastat, see Section A.11, "numastat" . For further information about numastat, see the man page:

Commands:
man numastat
7.277. xinetd 7.277.1. RHSA-2013:0499 - Low: xinetd security and bug fix update An updated xinetd package that fixes one security issue and two bugs is 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 xinetd package provides a secure replacement for inetd, the Internet services daemon. xinetd provides access control for all services based on the address of the remote host and/or on time of access, and can prevent denial-of-access attacks. Security Fix CVE-2012-0862 When xinetd services are configured with the "TCPMUX" or "TCPMUXPLUS" type, and the tcpmux-server service is enabled, those services are accessible via port 1. It was found that enabling the tcpmux-server service (it is disabled by default) allowed every xinetd service, including those that are not configured with the "TCPMUX" or "TCPMUXPLUS" type, to be accessible via port 1. This could allow a remote attacker to bypass intended firewall restrictions. Red Hat would like to thank Thomas Swan of FedEx for reporting this issue. Bug Fixes BZ# 790036 Prior to this update, a file descriptor array in the service.c source file was not handled as expected. As a consequence, some of the descriptors remained open when xinetd was under heavy load. Additionally, the system log was filled with a large number of messages that took up a lot of disk space over time. This update modifies the xinetd code to handle the file descriptors correctly and messages no longer fill the system log. BZ#809271 Prior to this update, services were disabled permanently when their CPS limit was reached. As a consequence, a failed bind operation could occur when xinetd attempted to restart the service. This update adds additional logic that attempts to restart the service. Now, the service is only disabled if xinetd cannot restart the service after 30 attempts. All users of xinetd are advised to upgrade to this updated package, which contains backported patches to correct these issues.

Commands:
7.230. wireshark 7.230.1. RHSA-2015:1460 - Moderate: wireshark security, bug fix, and enhancement update Updated wireshark packages that fix multiple security issues, several bugs, and add various enhancements 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. Wireshark, previously known as Ethereal, is a network protocol analyzer, which is used to capture and browse the traffic running on a computer network. Security Fix CVE-2014-8714 , CVE-2014-8712 , CVE-2014-8713 , CVE-2014-8711 , CVE-2014-8710 , CVE-2015-0562 , CVE-2015-0564 , CVE-2015-2189 , CVE-2015-2191 Several denial of service flaws were found in Wireshark. Wireshark could crash or stop responding if it read a malformed packet off a network, or opened a malicious dump file. Bug Fixes BZ# 1095065 Previously, the Wireshark tool did not support Advanced Encryption Standard Galois/Counter Mode (AES-GCM) cryptographic algorithm. As a consequence, AES-GCM was not decrypted. Support for AES-GCM has been added to Wireshark, and AES-GCM is now correctly decrypted. BZ# 1121275 Previously, when installing the system using the kickstart method, a dependency on the shadow-utils packages was missing from the wireshark packages, which could cause the installation to fail with a "bad scriptlet" error message. With this update, shadow-utils are listed as required in the wireshark packages spec file, and kickstart installation no longer fails. BZ# 1131203 Prior to this update, the Wireshark tool could not decode types of elliptic curves in Datagram Transport Layer Security (DTLS) Client Hello. Consequently, Wireshark incorrectly displayed elliptic curves types as data. A patch has been applied to address this bug, and Wireshark now decodes elliptic curves types properly. BZ# 1160388 Previously, a dependency on the gtk2 packages was missing from the wireshark packages. As a consequence, the Wireshark tool failed to start under certain circumstances due to an unresolved symbol, "gtk_combo_box_text_new_with_entry", which was added in gtk version 2.24. With this update, a dependency on gtk2 has been added, and Wireshark now always starts as expected. Enhancements BZ# 1104210 With this update, the Wireshark tool supports process substitution, which feeds the output of a process (or processes) into the standard input of another process using the "<(command_list)" syntax. When using process substitution with large files as input, Wireshark failed to decode such input. BZ# 1146578 Wireshark has been enhanced to enable capturing packets with nanosecond time stamp precision, which allows better analysis of recorded network traffic. All wireshark users are advised to upgrade to these updated packages, which contain backported patches to correct these issues and add these enhancements. All running instances of Wireshark must be restarted for the update to take effect.

Commands:
9.8. Setting up Resumable CRL Downloads Certificate System provides option for interrupted CRL downloads to be resumed smoothly. This is done by publishing the CRLs as a plain file over HTTP. This method of downloading CRLs gives flexibility in retrieving CRLs and lowers overall network congestion. 9.8.1. Retrieving CRLs Using wget Because CRLs can be published as a text file over HTTP, they can be manually retrieved from the CA using a tool such as wget . The wget command can be used to retrieve any published CRL. For example, to retrieve a full CRL which is newer than the full CRL: The relevant parameters for wget are summarized in Table 9.4, "wget Options to Use for Retrieving CRLs" . Table 9.4. wget Options to Use for Retrieving CRLs Argument Description no argument Retrieves the full CRL. -N Retrieves the CRL that is newer than the local copy (delta CRL). -c Retrieves a partially-downloaded file. --no-check-certificate Skips SSL for the connection, so it is not necessary to configure SSL between the host and client. -d Prints debug information.

Commands:
wget --no-check-certificate -d https://server.example.com:8443/ca/ee/ca/crl/MasterCRL.bin
4.193. NetworkManager-openswan 4.193.1. RHBA-2011:1771 - NetworkManager-openswan bug fix update An updated NetworkManager-openswan package that fixes various bug is now available for Red Hat Enterprise Linux 6. NetworkManager-openswan contains software for integrating the Openswan VPN software with NetworkManager and the GNOME desktop. Bug Fixes BZ# 684809 When an openswan VPN is established, the NetworkManager applet did not display any notification (login banner) and the error message, "Error getting 'Banner'", was logged. With this update, NetworkManager now displays the connection establishment notification as a tooltip for the NetworkManager icon. BZ# 702323 Prior to this update, networkmanager-openswan did not provide an export feature. Due to this, it was not possible to save the configuration settings in a file. This update adds this feature and now it is possible to export configuration settings to a file. BZ# 705890 Prior to this update, NetworkManager could not properly track the status of an openswan VPN. Consequently, when an openswan VPN was disconnected, NetworkManager did not remove the VPN padlock icon. This update fixes this issue and now the VPN padlock icon is removed after an openswan VPN connection is terminated. All users of NetworkManager-openswan are advised to upgrade to this updated package, which fixes these bugs.

Commands:
4.116. kdebase-workspace 4.116.1. RHBA-2011:1115 - kdebase-workspace bug fix update Updated kdebase-workspace packages that fix several bugs are now available for Red Hat Enterprise Linux 6. KDE is a graphical desktop environment for the X Window System. The kdebase-workspace packages contains utilities for basic operations with the desktop environment. It allows users for example, to change system settings, resize and rotate X screens or set panels and widgets on the workspace. Bug Fixes BZ# 587917 If the KDE and GNOME desktop environments were both installed on one system, two System Monitor utilities were installed as well. These, located in System Tools of the Applications menu, had the same icons and title, which may have confused the user. With this update, KDE icons are used for the ksysguard tool. BZ# 639359 Prior to this update, the ksysguard process terminated unexpectedly with a segmentation fault after clicking the OK button in the Properties dialog of the Network History tab, which is included in the ksysguard application. This bug has been fixed in this update so that ksysguard no longer crashes and works properly. BZ# 649345 Previously, when rebooting the system, the kdm utility terminated with a segmentation fault if auto-login was enabled. This was caused by a NULL password being sent to the master process, which has been fixed, and rebooting the system with auto-login enabled no longer causes kdm to crash. BZ# 666295 When clicking Help in the Battery Monitor Settings dialog of the Battery Monitor widget, the message "The file or folder help:/plasma-desktop/index.html does not exist" appeared instead of displaying the help pages. This update adds the missing help pages, which fixes the problem. All users of kdebase-workspace are advised to upgrade to these updated packages, which fix these bugs.

Commands:
function::user_long Name function::user_long - Retrieves a long value stored in user space. Synopsis Arguments addr The user space address to retrieve the long from. General Syntax user_long:long(addr:long) Description Returns the long value from a given user space address. Returns zero when user space data is not accessible. Note that the size of the long depends on the architecture of the current user space task (for those architectures that support both 64/32 bit compat tasks).

Commands:
function user_long:long(addr:long)