mtpti5iD/redhat-docs_dataset huggingface dataset:
4.3.5. Tracking Most Frequently Used System Calls timeout.stp from Section 4.3.4, "Monitoring Polling Applications" helps you identify which applications are polling by pointing out which ones used the following system calls most frequently: poll select epoll itimer futex nanosleep signal However, in some systems, a different system call might be responsible for excessive polling. If you suspect that a polling application is using a different system call to poll, you need to identify first the top system calls used by the system. To do this, use topsys.stp . topsys.stp topsys.stp lists the top 20 system calls used by the system per 5-second interval. It also lists how many times each system call was used during that period. Refer to Example 4.15, "topsys.stp Sample Output" for a sample output. Example 4.15. topsys.stp Sample Output

Commands:
#! /usr/bin/env stap # This script continuously lists the top 20 systemcalls in the interval 5 seconds # global syscalls_count probe syscall.* { syscalls_count[name]++ } function print_systop () { printf ("%25s %10s\n", "SYSCALL", "COUNT") foreach (syscall in syscalls_count- limit 20) { printf("%25s %10d\n", syscall, syscalls_count[syscall]) } delete syscalls_count } probe timer.s(5) { print_systop () printf("--------------------------------------------------------------\n") }
-------------------------------------------------------------- SYSCALL COUNT gettimeofday 1857 read 1821 ioctl 1568 poll 1033 close 638 open 503 select 455 write 391 writev 335 futex 303 recvmsg 251 socket 137 clock_gettime 124 rt_sigprocmask 121 sendto 120 setitimer 106 stat 90 time 81 sigreturn 72 fstat 66 --------------------------------------------------------------
7.137. nfs-utils-lib 7.137.1. RHBA-2015:1312 - nfs-utils-lib bug fix update Updated nfs-utils-lib packages that fix one bug are now available for Red Hat Enterprise Linux 6. The nfs-utils-lib packages contain support libraries required by the programs in the nfs-utils packages. Bug Fixes BZ# 1129792 Prior to this update, the libnfsidmap library used "nobody@DEFAULTDOMAIN" when performing name lookup, but this did not match the behavior of the rpc.idmapd daemon. As a consequence, the nfsidmap utility did not properly handle situations when "nobody@DEFAULTDOMAIN" did not directly map to any user or group on the system. With this update, libnfsidmap uses the "Nobody-User" and "Nobody-Group" values in the /etc/idmapd.conf file when the default "nobody" user and group are set, and the described problem no longer occurs. BZ# 1223465 The nss_getpwnam() function previously failed to find the intended password entry when the DNS domain name contained both upper-case and lower-case characters. This update ensures that character case is ignored when comparing domain names, and nss_getpwnam() is able to retrieve passwords as expected. Users of nfs-utils-lib are advised to upgrade to these updated packages, which fix this bug.

Commands:
2.22. RHEA-2011:0626 - new package: osutil A new osutil package is now available. The Operating System Utilities Java Native Interface (JNI) package supplies various native operating system operations to Java programs. This new package adds JNI features that allow Red Hat Enterprise Linux 6 users to use the operating system utility libraries that are made available to java programs using JNI. Red Hat IPA and the Certificate System CA depend on JNI for their interface with the operating system. (BZ# 643543 ) Users are advised to upgrade to this updated package, which resolves this issue.

Commands:
4.2. Power Management by Proxy in Red Hat Virtualization The Red Hat Virtualization Manager does not communicate directly with fence agents. Instead, the Manager uses a proxy to send power management commands to a host power management device. The Manager uses VDSM to execute power management device actions, so another host in the environment is used as a fencing proxy. You can select between: Any host in the same cluster as the host requiring fencing. Any host in the same data center as the host requiring fencing. A viable fencing proxy host has a status of either UP or Maintenance .

Commands:
function::ansi_set_color3 Name function::ansi_set_color3 - Set the ansi Select Graphic Rendition mode. Synopsis Arguments fg Foreground color to set. bg Background color to set. attr Color attribute to set. Description Sends ansi code for Select Graphic Rendition mode for the given forground color, Black (30), Blue (34), Green (32), Cyan (36), Red (31), Purple (35), Brown (33), Light Gray (37), the given background color, Black (40), Red (41), Green (42), Yellow (43), Blue (44), Magenta (45), Cyan (46), White (47) and the color attribute All attributes off (0), Intensity Bold (1), Underline Single (4), Blink Slow (5), Blink Rapid (6), Image Negative (7).

Commands:
ansi_set_color3(fg:long,bg:long,attr:long)
Backup and restore Red Hat Advanced Cluster Security for Kubernetes 4.7 Backing up and restoring Red Hat Advanced Cluster Security for Kubernetes Red Hat OpenShift Documentation Team

Commands:
export ROX_API_TOKEN=<api_token>
export ROX_ENDPOINT=<address>:<port_number>
roxctl central backup 1
export ROX_ENDPOINT=<address>:<port_number>
roxctl -p <admin_password> central backup 1
oc get central -n _<central-namespace>_ _<central-name>_ -o yaml > central-cr.yaml
oc get secret -n _<central-namespace>_ central-tls -o json | jq 'del(.metadata.ownerReferences)' > central-tls.json
oc get secret -n _<central-namespace>_ central-htpasswd -o json | jq 'del(.metadata.ownerReferences)' > central-htpasswd.json
helm get values --all -n _<central-namespace>_ _<central-helm-release>_ -o yaml > central-values-backup.yaml
export ROX_API_TOKEN=<api_token>
export ROX_ENDPOINT=<address>:<port_number>
roxctl central db restore <backup_file> 1
export ROX_ENDPOINT=<address>:<port_number>
roxctl -p <admin_password> \ 1 central db restore <backup_file> 2
roxctl central generate interactive
Enter path to the backup bundle from which to restore keys and certificates (optional): _<backup-file-path>_
./central-bundle/central/scripts/setup.sh
cat central-bundle/password
oc apply -f central-tls.json
oc apply -f central-htpasswd.json
oc apply -f central-cr.yaml
roxctl central generate k8s pvc --backup-bundle _<path-to-backup-file>_ --output-format "helm-values"
helm install -n stackrox --create-namespace stackrox-central-services rhacs/central-services -f central-values-backup.yaml -f central-bundle/values-private.yaml
5.2. Creating a Striped Logical Volume This example creates an LVM striped logical volume called striped_logical_volume that stripes data across the disks at /dev/sda1 , /dev/sdb1 , and /dev/sdc1 . 5.2.1. Creating the Physical Volumes Label the disks you will use in the volume groups as LVM physical volumes. Warning This command destroys any data on /dev/sda1 , /dev/sdb1 , and /dev/sdc1 .

Commands:
pvcreate /dev/sda1 /dev/sdb1 /dev/sdc1 Physical volume "/dev/sda1" successfully created Physical volume "/dev/sdb1" successfully created Physical volume "/dev/sdc1" successfully created
Chapter 2. Browsing with the API REST APIs give access to resources (data entities) through URI paths. Procedure Go to the automation controller REST API in a web browser at: https://<server name>/api/controller/v2 Click the "v2" link to "current versions" or "available versions" . Automation controller supports version 2 of the API. Perform a GET with just the /api/ endpoint to get the current_version , which is the recommended version. Click the icon on the navigation menu, for documentation on the access methods for that particular API endpoint and what data is returned when using those methods. Use the PUT and POST verbs on the specific API pages by formatting JSON in the various text fields. You can also view changed settings from factory defaults at /api/v2/settings/changed/ endpoint. It reflects changes you made in the API browser, not changed settings that come from static settings files.

Commands:
7.300. esc 7.300.1. RHBA-2013:0735 - esc bug fix update Updated esc packages that fix one bug are now available for Red Hat Enterprise Linux 6. The esc packages contain the Smart Card Manager GUI, which allows user to manage security smart cards. The primary function of the tool is to enroll smart cards, so that they can be used for common cryptographic operations, such as secure e-mail and website access. Bug Fix BZ# 922646 The ESC utility did not start when the latest 17 series release of the XULRunner runtime environment was installed on the system. This update includes necessary changes to ensure that ESC works as expected with the latest version of XULRunner. Users of esc are advised to upgrade to these updated packages, which fix this bug.

Commands:
7.203. ql2500-firmware 7.203.1. RHBA-2013:0403 - ql2500-firmware bug fix and enhancement update An updated ql2500-firmware package that fixes multiple bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The ql2500-firmware package provides the firmware required to run the QLogic 2500 Series of mass storage adapters. Note This update upgrades the ql2500 firmware to upstream version 5.08.00., which provides a number of bug fixes and enhancements over the version. (BZ#826667) All users of QLogic 2500 Series Fibre Channel adapters are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
Chapter 5. Bookmarking files and locations In GNOME, applications and dialogs that manage files list bookmarks in the left side bar. You can add, remove, and edit the bookmarks. 5.1. Adding a bookmark You can save a reference to a folder by bookmarking it in the Files application. Prerequisite Locate the folder in the Files application. Procedure Add the folder to bookmarks using either of the following methods: By dragging: Drag the folder to the left side bar. Drop it over the New bookmark item. Using a keyboard shortcut: Open the folder. Press Ctrl + D . Using a menu: Open the folder. In the navigation bar at the top of the window, click the name of the folder. Select Add to Bookmarks . Verification Check that the bookmark now appears in the side bar. 5.2. Removing a bookmark You can delete an existing bookmark in the Files application. Procedure Right-click the bookmark in the side bar. Select Remove from the menu. Verification Check that the bookmark no longer appears in the side bar. 5.3. Renaming a bookmark You can rename a bookmark to distinguish it from other bookmarks. If you have bookmarks to several folders that all share the same name, you can tell the bookmarks apart if you rename them. Renaming the bookmark does not rename the folder. Procedure Right-click the bookmark in the side bar. Select Rename... . In the Name field, enter the new name for the bookmark. Click Rename . Verification Check that the side bar lists the bookmark under the new name. 5.4. Adding a bookmark for all users As a system administrator, you can set a bookmark for several users at once so that file shares are easily accessible to all the users. Procedure In the home directory of each existing user, edit the ~ user /.config/gtk-3.0/bookmarks file. In the file, add a Uniform Resource Identifiers (URI) line that identifies the bookmark. For example, the following lines add bookmarks to the /usr/share/doc/ directory and to the GNOME FTP network share: Optional: To also add the bookmarks for every newly created user on the system: Create the /etc/skel/.config/gtk-3.0/bookmarks file. Enter the bookmark URI lines in the file.

Commands:
file:///usr/share/doc/ ftp://ftp.gnome.org/
Chapter 2. Setting up credentials for Event-Driven Ansible controller Credentials are used by Event-Driven Ansible for authentication when launching rulebooks. 2.1. Setting up credentials Create a credential to use with a private repository (GitHub or GitLab) or a private container registry. Important If you are using a GitHub or GitLab repository, use the basic auth method. Both SCM servers are officially supported. You can use any SCM provider that supports basic auth . Procedure Log in to the Event-Driven Ansible controller Dashboard. From the navigation panel, select Resources Credentials . Click Create credential . Insert the following: Name Insert the name. Description This field is optional. Credential type The options available are a GitHub personal access token, a GitLab personal access token, or a container registry. Username Insert the username. Token Insert a token that allows you to authenticate to your destination. Note If you are using a container registry, the token field can be a token or a password, depending on the registry provider. If you are using the Ansible Automation Platform hub registry, insert the password for that in the token field. Click Create credential . After saving the credential, the credentials details page is displayed. From there or the Credentials list view, you can edit or delete it. 2.2. Credentials list view On the Credentials page, you can view the list of created credentials that you have created along with the Type of credential. From the menu bar, you can search for credentials in the Name field. You also have the following options in the menu bar: Choose which columns are shown in the list view by clicking Manage columns . Choose between a List view or a Card view , by clicking the icons. 2.3. Editing a credential Procedure Edit the credential by using one of these methods: From the Credentials list view, click the Edit credential icon to the desired credential. From the Credentials list view, select the name of the credential, click Edit credential . Edit the appropriate details and click Save credential . 2.4. Deleting a credential Procedure Delete the credential by using one of these methods: From the Credentials list view, click the More Actions icon ... to the desired credential and click Delete credential . From the Credentials list view, select the name of the credential, click the More Actions icon ... to Edit credential , and click Delete credential . In the pop-up window, select Yes, I confirm that I want to delete this credential . Click Delete credential . You can delete multiple credentials at a time by selecting the checkbox to each credential and clicking the More Actions icon ... in the menu bar and then clicking Delete selected credentials .

Commands:
6.3. Adjusting Automatic Updates Red Hat Enterprise Linux is configured to apply all updates on a daily schedule. If you want to change how your system installs updates, you must do so via Software Update Preferences . You can change the schedule, the type of updates to apply, or to notify you of available updates. In GNOME, you can find controls for your updates at: System Preferences Software Updates . In KDE, it is located at: Applications Settings Software Updates .

Commands:
Chapter 9. Installing an Instance with ECC System Certificates Elliptic curve cryptography (ECC) may be preferred over RSA-style encryption in some cases, as it allows it to use much shorter key lengths and makes it faster to generate certificates. CAs which are ECC-enabled can issue both RSA and ECC certificates, using their ECC signing certificate. Certificate System includes native support for ECC features; the support is enabled by default starting from NSS 3.16. It is also possible to load and use a third-party PKCS #11 module, such as a hardware security module (HSM). To use the ECC module, it must be loaded before the subsystem instance is configured. Important Third-party ECC modules must have an SELinux policy configured for them, or SELinux needs to be changed from enforcing mode to permissive mode to allow the module to function. Otherwise, any subsystem operations which require the ECC module will fail. 9.1. Loading a Third-Party ECC Module Loading a third-party ECC module follows the same principles as loading HSMs supported by Certificate System, which is described in Chapter 8, Using Hardware Security Modules for Subsystem Security Databases . See this chapter for more information.

Commands:
6.2. RHEA-2013:0484 - new packages: hypervkvpd New hypervkvpd packages are now available for Red Hat Enterprise Linux 6. The hypervkvpd packages contain hypervkvpd, the guest Hyper-V Key-Value Pair (KVP) daemon. Using VMbus, hypervkvpd passes basic information to the host. The information includes guest IP address, fully qualified domain name, operating system name, and operating system release number. An IP injection functionality is also provided which allows you to change the IP address of a guest from the host via the hypervkvpd daemon. This enhancement update adds the hypervkvpd packages to Red Hat Enterprise Linux 6. For more information about inclusion of, and guest installation support for, Microsoft Hyper-V drivers, refer to the Red Hat Enterprise Linux 6.4 Release Notes. (BZ#850674) All users who require hypervkvpd are advised to install these new packages. After installing the hypervkvpd packages, rebooting all guest machines is recommended, otherwise the Microsoft Windows server with Hyper-V might not be able to get information from these guest machines.

Commands:
Chapter 8. Configuring your Logging deployment 8.1. Configuring CPU and memory limits for logging components You can configure both the CPU and memory limits for each of the logging components as needed. 8.1.1. Configuring CPU and memory limits The logging components allow for adjustments to both the CPU and memory limits. Procedure Edit the ClusterLogging custom resource (CR) in the openshift-logging project: USD oc -n openshift-logging edit ClusterLogging instance apiVersion: "logging.openshift.io/v1" kind: "ClusterLogging" metadata: name: "instance" namespace: openshift-logging ... spec: managementState: "Managed" logStore: type: "elasticsearch" elasticsearch: nodeCount: 3 resources: 1 limits: memory: 16Gi requests: cpu: 200m memory: 16Gi storage: storageClassName: "gp2" size: "200G" redundancyPolicy: "SingleRedundancy" visualization: type: "kibana" kibana: resources: 2 limits: memory: 1Gi requests: cpu: 500m memory: 1Gi proxy: resources: 3 limits: memory: 100Mi requests: cpu: 100m memory: 100Mi replicas: 2 collection: resources: 4 limits: memory: 736Mi requests: cpu: 200m memory: 736Mi type: fluentd 1 Specify the CPU and memory limits and requests for the log store as needed. For Elasticsearch, you must adjust both the request value and the limit value. 2 3 Specify the CPU and memory limits and requests for the log visualizer as needed. 4 Specify the CPU and memory limits and requests for the log collector as needed.

Commands:
oc -n openshift-logging edit ClusterLogging instance
apiVersion: "logging.openshift.io/v1" kind: "ClusterLogging" metadata: name: "instance" namespace: openshift-logging spec: managementState: "Managed" logStore: type: "elasticsearch" elasticsearch: nodeCount: 3 resources: 1 limits: memory: 16Gi requests: cpu: 200m memory: 16Gi storage: storageClassName: "gp2" size: "200G" redundancyPolicy: "SingleRedundancy" visualization: type: "kibana" kibana: resources: 2 limits: memory: 1Gi requests: cpu: 500m memory: 1Gi proxy: resources: 3 limits: memory: 100Mi requests: cpu: 100m memory: 100Mi replicas: 2 collection: resources: 4 limits: memory: 736Mi requests: cpu: 200m memory: 736Mi type: fluentd
14.5.23. Creating a Virtual Machine XML Dump (Configuration File) Output a guest virtual machine's XML configuration file with virsh : This command outputs the guest virtual machine's XML configuration file to standard out ( stdout ). You can save the data by piping the output to a file. An example of piping the output to a file called guest.xml : This file guest.xml can recreate the guest virtual machine (refer to Section 14.6, "Editing a Guest Virtual Machine's configuration file" . You can edit this XML configuration file to configure additional devices or to deploy additional guest virtual machines. An example of virsh dumpxml output: Note that the <shareable/> flag is set. This indicates the device is expected to be shared between domains (assuming the hypervisor and OS support this), which means that caching should be deactivated for that device.

Commands:
virsh dumpxml {guest-id, guestname or uuid}
virsh dumpxml GuestID > guest.xml
virsh dumpxml guest1-rhel6-64 <domain type='kvm'> <name>guest1-rhel6-64</name> <uuid>b8d7388a-bbf2-db3a-e962-b97ca6e514bd</uuid> <memory>2097152</memory> <currentMemory>2097152</currentMemory> <vcpu>2</vcpu> <os> <type arch='x86_64' machine='rhel6.2.0'>hvm</type> <boot dev='hd'/> </os> <features> <acpi/> <apic/> <pae/> </features> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>restart</on_crash> <devices> <emulator>/usr/libexec/qemu-kvm</emulator> <disk type='file' device='disk'> <driver name='qemu' type='raw' cache='none' io='threads'/> <source file='/home/guest-images/guest1-rhel6-64.img'/> <target dev='vda' bus='virtio'/> <shareable/< <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x0'/> </disk> <interface type='bridge'> <mac address='52:54:00:b9:35:a9'/> <source bridge='br0'/> <model type='virtio'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x03' function='0x0'/> </interface> <serial type='pty'> <target port='0'/> </serial> <console type='pty'> <target type='serial' port='0'/> </console> <input type='tablet' bus='usb'/> <input type='mouse' bus='ps2'/> <graphics type='vnc' port='-1' autoport='yes'/> <sound model='ich6'> <address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/> </sound> <video> <model type='cirrus' vram='9216' heads='1'/> <address type='pci' domain='0x0000' bus='0x00' slot='0x02' function='0x0'/> </video> <memballoon model='virtio'> <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x0'/> </memballoon> </devices> </domain>
Chapter 4. Practical tutorial: Using the Dashboard Builder for the first time Click the Create Workspace icon to create new workspace properties. Give the workplace a name and then click Create Workspace . Click on the new workspace to edit the details. Set the User Home Search to be current page and press save to set the URL, From the tree of workspaces on the left, expand to Workspaces/workspace and click on Pages (which will be empty on the right). On the far right, click on the Page icon to create new page Enter the page name and press Create New Page . Click on Workspace (found in the top drop-down list). Select the page you just created. To add a tree menu panel click on the puzzle icon to create a panel, expand Navigation to select the Tree menu, drag the Create Panel to the page (you will see the page locations appear) and drop it on one of the left-hand location. To add a log-off panel, click on the puzzle icon to create a panel, expand Navigation to select the Tree menu and drag the Logout Panel from the page to the top right-hand side. To add a graphic panel, click on the puzzle icon to create a panel , expand Dashboard to select Key Performance Indicator (KPI) and drag the Create Panel to one of the central locations. The dialog box will appear, asking you to choose an instance. (You should see your data provider). Go into the KPI editor and enter the KPI name and select the graph type. There is no Save button to complete this page. Simply close the window to complete the task. Enter page name and press create new page.

Commands:
Chapter 2. What are the benefits of the subscriptions service? The subscriptions service provides these benefits: Tracks selected Red Hat product usage and capacity at the fleet or account level in a unified inventory and provides a daily snapshot of that data in a digestible, filterable dashboard at console.redhat.com. Tracks data over time for self-governance and analytics that can inform purchasing and renewal decisions, ongoing capacity planning, and mitigation for high-risk scenarios. Helps procurement officers make data-driven choices with portfolio-centered reporting dashboards that show both inventory-occupying subscriptions and current subscription limits across the entire organization. With its robust reporting capabilities, enables the transition to simple content access tooling that features broader, organizational-level subscription enforcement instead of system-level quantity enforcement.

Commands: