mtpti5iD/redhat-docs_dataset huggingface dataset:
5.2.26. /proc/slabinfo This file gives full information about memory usage on the slab level. Linux kernels greater than version 2.2 use slab pools to manage memory above the page level. Commonly used objects have their own slab pools. Instead of parsing the highly verbose /proc/slabinfo file manually, the /usr/bin/slabtop program displays kernel slab cache information in real time. This program allows for custom configurations, including column sorting and screen refreshing. A sample screen shot of /usr/bin/slabtop usually looks like the following example: Some of the more commonly used statistics in /proc/slabinfo that are included into /usr/bin/slabtop include: OBJS - The total number of objects (memory blocks), including those in use (allocated), and some spares not in use. ACTIVE - The number of objects (memory blocks) that are in use (allocated). USE - Percentage of total objects that are active. ((ACTIVE/OBJS)(100)) OBJ SIZE - The size of the objects. SLABS - The total number of slabs. OBJ/SLAB - The number of objects that fit into a slab. CACHE SIZE - The cache size of the slab. NAME - The name of the slab. For more information on the /usr/bin/slabtop program, refer to the slabtop man page.

Commands:
Active / Total Objects (% used) : 133629 / 147300 (90.7%) Active / Total Slabs (% used) : 11492 / 11493 (100.0%) Active / Total Caches (% used) : 77 / 121 (63.6%) Active / Total Size (% used) : 41739.83K / 44081.89K (94.7%) Minimum / Average / Maximum Object : 0.01K / 0.30K / 128.00K OBJS ACTIVE USE OBJ SIZE SLABS OBJ/SLAB CACHE SIZE NAME 44814 43159 96% 0.62K 7469 6 29876K ext3_inode_cache 36900 34614 93% 0.05K 492 75 1968K buffer_head 35213 33124 94% 0.16K 1531 23 6124K dentry_cache 7364 6463 87% 0.27K 526 14 2104K radix_tree_node 2585 1781 68% 0.08K 55 47 220K vm_area_struct 2263 2116 93% 0.12K 73 31 292K size-128 1904 1125 59% 0.03K 16 119 64K size-32 1666 768 46% 0.03K 14 119 56K anon_vma 1512 1482 98% 0.44K 168 9 672K inode_cache 1464 1040 71% 0.06K 24 61 96K size-64 1320 820 62% 0.19K 66 20 264K filp 678 587 86% 0.02K 3 226 12K dm_io 678 587 86% 0.02K 3 226 12K dm_tio 576 574 99% 0.47K 72 8 288K proc_inode_cache 528 514 97% 0.50K 66 8 264K size-512 492 372 75% 0.09K 12 41 48K bio 465 314 67% 0.25K 31 15 124K size-256 452 331 73% 0.02K 2 226 8K biovec-1 420 420 100% 0.19K 21 20 84K skbuff_head_cache 305 256 83% 0.06K 5 61 20K biovec-4 290 4 1% 0.01K 1 290 4K revoke_table 264 264 100% 4.00K 264 1 1056K size-4096 260 256 98% 0.19K 13 20 52K biovec-16 260 256 98% 0.75K 52 5 208K biovec-64
Appendix A. Using your subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the AMQ Streams for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-04-29 12:48:17 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Chapter 2. Creating an activation key for virtual machines Use this procedure to create an activation key with auto-attach enabled and no subscriptions attached. When you register virtual machines using this activation key, the virtual machines inherit a subscription from their hypervisor if that hypervisor has a host-based subscription attached. Note This procedure is only valid if you have Simple Content Access (SCA) disabled on Satellite. You are not required to attach subscriptions to Activation Keys if you have SCA enabled. Note that SCA is enabled by default for newly created organizations. To learn more about SCA, see Simple Content Access . For more information about activation keys, see Managing Activation Keys in Managing Content . Procedure In the Satellite web UI, navigate to Content > Activation keys and click Create Activation Key . In the Name field, enter the name of the activation key. Ensure the Unlimited Hosts check box is selected. Alternatively, if you want to set a limit, clear the Unlimited hosts check box, and in the Limit field, enter the maximum number of virtual machines you can register with the activation key. In the Description field, enter a description for the activation key. From the Environment list, select the environment to use. From the Content View list, select a Content View to use. Click Save . When the new activation key appears in the Activation Keys window, click the name of the key. Click the Subscriptions tab. Ensure that Auto-Attach is set to Yes . If it is not, click the edit icon, select the check box, and click Save . Do not add any subscriptions to this activation key. For CLI users Create the activation key: Enable auto-attach on the activation key:

Commands:
hammer activation-key create --name " VM_Activation_Key " --unlimited-hosts --description " For VMs to inherit a VDC Subscription " --lifecycle-environment " Environment_Name " --content-view " CV_Name " --organization " My_Organization "
hammer activation-key update --name " VM_Activation_Key " --organization " My_Organization " --auto-attach true
12.5. Advanced Features of BIND Most BIND implementations only use named to provide name resolution services or to act as an authority for a particular domain or sub-domain. However, BIND version 9 has a number of advanced features that allow for a more secure and efficient DNS service. Warning Some of these advanced features, such as DNSSEC, TSIG, and IXFR (which are defined in the following section), should only be used in network environments with nameservers that support the features. If the network environment includes non-BIND or older BIND nameservers, verify that each advanced feature is supported before attempting to use it. All of the features mentioned are discussed in greater detail in the BIND 9 Administrator Reference Manual referenced in Section 12.7.1, "Installed Documentation" . 12.5.1. DNS Protocol Enhancements BIND supports Incremental Zone Transfers (IXFR), where a slave nameserver only downloads the updated portions of a zone modified on a master nameserver. The standard transfer process requires that the entire zone be transferred to each slave nameserver for even the smallest change. For very popular domains with very lengthy zone files and many slave nameservers, IXFR makes the notification and update process much less resource intensive. Note that IXFR is only available when using dynamic updating to make changes to master zone records. If manually editing zone files to make changes, Automatic Zone Transfer (AXFR) is used. More information on dynamic updating is available in the BIND 9 Administrator Reference Manual . See Section 12.7.1, "Installed Documentation" for more information.

Commands:
function::kernel_string2 Name function::kernel_string2 - Retrieves string from kernel memory with alternative error string. Synopsis Arguments addr The kernel address to retrieve the string from. err_msg The error message to return when data isn't available. General Syntax kernel_string2:string(addr:long, err_msg:string) Description This function returns the null terminated C string from a given kernel memory address. Reports the given error message on string copy fault.

Commands:
function kernel_string2:string(addr:long,err_msg:string)
Preface Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security and bug fix errata. The Red Hat Enterprise Linux 6.6 Release Notes documents the major changes made to the Red Hat Enterprise Linux 6 operating system and its accompanying applications for this minor release. Detailed notes on changes (that is, bugs fixed, enhancements added, and known issues found) in this minor release are available in the Technical Notes . The Technical Notes document also contains a complete list of all currently available Technology Previews along with packages that provide them. Important The online Red Hat Enterprise Linux 6.6 Release Notes , which are located online here , are to be considered the definitive, up-to-date version. Customers with questions about the release are advised to consult the online Release and Technical Notes for their version of Red Hat Enterprise Linux. Capabilities and limits of Red Hat Enterprise Linux 6 as compared to other versions of the system are available in the Knowledge Base article available at https://access.redhat.com/site/articles/rhel-limits . Should you require information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands:
Install builds for Red Hat OpenShift 1.1 Installing Builds Red Hat OpenShift Documentation Team

Commands:
apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: openshift-builds-operator namespace: openshift-builds spec: channel: <channel-name> 1 name: openshift-builds-operator 2 source: redhat-operators 3 sourceNamespace: openshift-marketplace 4
oc apply -f sub.yml
oc get openshiftbuilds
oc get shipwrightbuilds
oc get pods -n openshift-builds
oc get pods -n openshift-builds NAME READY STATUS RESTARTS AGE openshift-builds-operator-6f5c48c6b5-cvp2w 2/2 Running 0 13d openshift-pipelines-operator-64d8c4969c-952cc 2/2 Running 0 3d13h shared-resource-csi-driver-node-gbkqs 2/2 Running 0 13d shared-resource-csi-driver-node-kcqxc 2/2 Running 0 13d shared-resource-csi-driver-node-sbsvg 2/2 Running 0 13d shared-resource-csi-driver-webhook-9d9bd48f4-d5ln6 1/1 Running 0 13d shipwright-build-controller-5454475b85-mmm6w 1/1 Running 0 13d shipwright-build-webhook-7fbd49c6bb-2n77s 1/1 Running 0 13d tekton-operator-webhook-756f5dfdc7-c99mc 1/1 Running 0 3d13h
oc patch openshiftbuild cluster --type=merge -p '{"spec":{"shipwright":{"build":{"state":"Disabled"}}}}'
5.2. Which Log File is Used In Red Hat Enterprise Linux 6, the dbus and audit packages are installed by default, unless they are removed from the default package selection. The setroubleshoot-server must be installed via Yum (the yum install setroubleshoot command). If the auditd daemon is running, SELinux denial messages, such as the following, are written to /var/log/audit/audit.log by default: In Red Hat Enterprise Linux 6, setroubleshootd no longer constantly runs as a service. However, it is still used to analyze the AVC messages. Two new programs act as a method to start setroubleshoot when needed: sedispatch and seapplet . The sedispatch utility runs as part of the audit subsystem, and via dbus , sends a message when an AVC denial message is returned. These messages go straight to setroubleshootd if it is already running. If setroubleshootd is not running, sedispatch starts it automatically. The seapplet utility runs in the system toolbar, waiting for dbus messages in setroubleshootd . It launches the notification bubble, allowing the user to review AVC messages. Procedure 5.1. Starting Daemons Automatically To configure the auditd and rsyslogd daemons to automatically start at boot, run the following commands as the Linux root user: Use the service service-name status command to check if these services are running, for example: If the above services are not running ( service-name is stopped ), use the service service-name start command as the Linux root user to start them. For example:

Commands:
type=AVC msg=audit(1223024155.684:49): avc: denied { getattr } for pid=2000 comm="httpd" path="/var/www/html/file1" dev=dm-0 ino=399185 scontext=unconfined_u:system_r:httpd_t:s0 tcontext=system_u:object_r:samba_share_t:s0 tclass=file
May 7 18:55:56 localhost setroubleshoot: SELinux is preventing httpd (httpd_t) "getattr" to /var/www/html/file1 (samba_share_t). For complete SELinux messages. run sealert -l de7e30d6-5488-466d-a606-92c9f40d316d
~]# chkconfig --levels 2345 auditd on ~]# chkconfig --levels 2345 rsyslog on
~]# service auditd status auditd (pid 1318 ) is running
~]# service auditd start Starting auditd: [ OK ]
7.296. gnome-power-manager 7.296.1. RHBA-2013:0597 - gnome-power-manager bug fix update Updated gnome-power-manager packages that fix one bug are now available for Red Hat Enterprise Linux 6. GNOME Power Manager is a session daemon for the GNOME desktop environment which allows users to manage power settings on their laptop or desktop system. Bug Fix BZ# 912270 When the power saving features (reduce backlight brightness and dim display when idle) were enabled for the "on battery power" mode and the brightness was adjusted manually, then leaving the laptop idle caused it to forget custom brightness settings. Currently, the "dim display when idle" functionality is disabled by default and laptops remember custom brightness settings. Users of gnome-power-manager are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 5. Adding a CA bundle after upgrading Red Hat OpenShift AI provides support for using self-signed certificates. If you have upgraded from OpenShift AI 2.7 or earlier versions, you can add self-signed certificates to the OpenShift AI deployments and Data Science Projects in your cluster. There are two ways to add a Certificate Authority (CA) bundle to OpenShift AI. You can use one or both of these methods: For OpenShift clusters that rely on self-signed certificates, you can add those self-signed certificates to a cluster-wide Certificate Authority (CA) bundle ( ca-bundle.crt ) and use the CA bundle in Red Hat OpenShift AI. You can use self-signed certificates in a custom CA bundle ( odh-ca-bundle.crt ) that is separate from the cluster-wide bundle. For more information, see Working with certificates . Prerequisites You have admin access to the DSCInitialization resources in the OpenShift cluster. You installed the OpenShift command line interface ( oc ) as described in Installing the OpenShift CLI . You upgraded Red Hat OpenShift AI. If you are working in a new installation of Red Hat OpenShift AI, see Adding a CA bundle . Procedure Log in to the OpenShift as a cluster administrator. Click Operators Installed Operators and then click the Red Hat OpenShift AI Operator. Click the DSC Initialization tab. Click the default-dsci object. Click the YAML tab. Add the following to the spec section, setting the managementState field to Managed : If you want to use self-signed certificates added to a cluster-wide CA bundle, log in to the OpenShift as a cluster administrator and follow the steps as described in Configuring the cluster-wide proxy during installation . If you want to use self-signed certificates in a custom CA bundle that is separate from the cluster-wide bundle, follow these steps: Add the custom certificate to the customCABundle field of the default-dsci object, as shown in the following example: Click Save . The Red Hat OpenShift AI Operator creates an odh-trusted-ca-bundle ConfigMap containing the certificates in all new and existing non-reserved namespaces. Verification If you are using a cluster-wide CA bundle, run the following command to verify that all non-reserved namespaces contain the odh-trusted-ca-bundle ConfigMap: If you are using a custom CA bundle, run the following command to verify that a non-reserved namespace contains the odh-trusted-ca-bundle ConfigMap and that the ConfigMap contains your customCABundle value. In the following command, example-namespace is the non-reserved namespace and examplebundle123 is the customCABundle value.

Commands:
spec: trustedCABundle: managementState: Managed customCABundle: ""
spec: trustedCABundle: managementState: Managed customCABundle: | -----BEGIN CERTIFICATE----- examplebundle123 -----END CERTIFICATE-----
oc get configmaps --all-namespaces -l app.kubernetes.io/part-of=opendatahub-operator | grep odh-trusted-ca-bundle
oc get configmap odh-trusted-ca-bundle -n example-namespace -o yaml | grep examplebundle123
7.39. dmidecode 7.39.1. RHBA-2015:1425 - dmidecode bug fix update Updated dmidecode packages that fix one bug are now available for Red Hat Enterprise Linux 6. The dmidecode packages provide utilities for extracting x86 and Intel Itanium hardware information from the system BIOS or EFI, depending on the SMBIOS/DMI standard. This information typically includes system manufacturer, model name, serial number, BIOS version, and asset tag. Bug Fix BZ# 1192357 Prior to this update, the dmidecode utility did not support the DDR4 type of memory. Consequently, compiling of the dmidecode code for hardware with DDR4 memory type gave out of specs results. With this update, dmidecode has been updated so that the DDR4 is among memory types and no longer returns out of specs while compiling the dmidecode source code. Users of dmidecode are advised to upgrade to these updated packages, which fix this bug.

Commands:
5.266. ql2400-firmware 5.266.1. RHBA-2012:0859 - ql2400-firmware bug fix and enhancement update An updated ql2400-firmware package that provides several bug fixes and enhancements is now available for Red Hat Enterprise Linux 6. The ql2400-firmware package provides the firmware required to run the QLogic 2400 Series of mass storage adapters. This update upgrades the ql2400 firmware to upstream version 5.06.05, which provides a number of bug fixes and enhancements over the version. (BZ# 766048 ) All users of QLogic 2400 Series Fibre Channel adapters are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
Chapter 2. Accessing the web console The OpenShift Dedicated web console is a user interface accessible from a web browser. Developers can use the web console to visualize, browse, and manage the contents of projects. 2.1. Prerequisites JavaScript must be enabled to use the web console. For the best experience, use a web browser that supports WebSockets . Review the OpenShift Container Platform 4.x Tested Integrations page before you create the supporting infrastructure for your cluster. 2.2. Understanding and accessing the web console The web console runs as a pod on the control plane node. The static assets required to run the web console are served by the pod. Procedure Log in to OpenShift Cluster Manager and click the name of your cluster. On the cluster Overview tab, click Open console , and log in with your credentials. Alternatively, use the oc whoami --show-console command to get the web console URL.

Commands:
9.3. Run Red Hat JBoss Data Virtualization on an Azure Instance Go here to learn how to create an Azure virtual machine: https://docs.microsoft.com/en-us/azure/virtual-machines/linux/tutorial-manage-vm . Connect to the Azure virtual machine using SSH. Copy the Red Hat JBoss Data Virtualization installer to that machine over SSH. Run the installer as per normal: To start the server, add the following parameters to bind the management and host ports: Here is an example:

Commands:
java -jar jboss-dv-VERSION-installer.jar
-Djboss.bind.address.management=0.0.0.0
-b 0.0.0.0
./standalone.sh -Djboss.bind.address.management=0.0.0.0 -b 0.0.0.0
Appendix A. Using your Red Hat subscription Red Hat Connectivity Link is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Managing your subscriptions Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. In the menu bar, click Subscriptions to view and manage your subscriptions. Revised on 2024-12-09 19:07:14 UTC

Commands:
Chapter 33. Kickstart Configurator Kickstart Configurator allows you to create or modify a kickstart file using a graphical user interface, so that you do not have to remember the correct syntax of the file. Kickstart Configurator is not installed by default on Red Hat Enterprise Linux 6.9. Run su - yum install system-config-kickstart or use your graphical package manager to install the software. To launch Kickstart Configurator , boot your system into a graphical environment, then run system-config-kickstart , or click Applications System Tools Kickstart on the GNOME desktop or Kickoff Application Launcher + Applications System Kickstart on the KDE desktop. As you are creating a kickstart file, you can click File Preview at any time to review your current selections. To start with an existing kickstart file, select File Open and select the existing file. 33.1. Basic Configuration Figure 33.1. Basic Configuration Choose the language to use during the installation and as the default language to be used after installation from the Default Language menu. Select the system keyboard type from the Keyboard menu. From the Time Zone menu, choose the time zone to use for the system. To configure the system to use UTC, select Use UTC clock . Enter the desired root password for the system in the Root Password text entry box. Type the same password in the Confirm Password text box. The second field is to make sure you do not mistype the password and then realize you do not know what it is after you have completed the installation. To save the password as an encrypted password in the file, select Encrypt root password . If the encryption option is selected, when the file is saved, the plain text password that you typed is encrypted and written to the kickstart file. Do not type an already encrypted password and select to encrypt it. Because a kickstart file is a plain text file that can be easily read, it is recommended that an encrypted password be used. Choosing Target Architecture specifies which specific hardware architecture distribution is used during installation. Choosing Target Architecture specifies which specific hardware architecture distribution is used during installation. Choosing Reboot system after installation reboots your system automatically after the installation is finished. Kickstart installations are performed in graphical mode by default. To override this default and use text mode instead, select the Perform installation in text mode option. You can perform a kickstart installation in interactive mode. This means that the installation program uses all the options pre-configured in the kickstart file, but it allows you to preview the options in each screen before continuing to the screen. To continue to the screen, click the button after you have approved the settings or change them before continuing the installation. To select this type of installation, select the Perform installation in interactive mode option.

Commands: