mtpti5iD/redhat-docs_dataset huggingface dataset:
29.9. Graphical Interface Some OProfile preferences can be set with a graphical interface. To start it, execute the oprof_start command as root at a shell prompt. To use the graphical interface, you will need to have the oprofile-gui package installed. After changing any of the options, save them by clicking the Save and quit button. The preferences are written to /root/.oprofile/daemonrc , and the application exits. Note Exiting the application does not stop OProfile from sampling. On the Setup tab, to set events for the processor counters as discussed in Section 29.2.2, "Setting Events to Monitor" , select the counter from the pulldown menu and select the event from the list. A brief description of the event appears in the text box below the list. Only events available for the specific counter and the specific architecture are displayed. The interface also displays whether the profiler is running and some brief statistics about it. Figure 29.1. OProfile Setup On the right side of the tab, select the Profile kernel option to count events in kernel mode for the currently selected event, as discussed in Section 29.2.3, "Separating Kernel and User-space Profiles" . If this option is unselected, no samples are collected for the kernel. Select the Profile user binaries option to count events in user mode for the currently selected event, as discussed in Section 29.2.3, "Separating Kernel and User-space Profiles" . If this option is unselected, no samples are collected for user applications. Use the Count text field to set the sampling rate for the currently selected event as discussed in Section 29.2.2.1, "Sampling Rate" . If any unit masks are available for the currently selected event, as discussed in Section 29.2.2.2, "Unit Masks" , they are displayed in the Unit Masks area on the right side of the Setup tab. Select the check box beside the unit mask to enable it for the event. On the Configuration tab, to profile the kernel, enter the name and location of the vmlinux file for the kernel to monitor in the Kernel image file text field. To configure OProfile not to monitor the kernel, select No kernel image . Figure 29.2. OProfile Configuration If the Verbose option is selected, the oprofiled daemon log includes more information. If Per-application profiles is selected, OProfile generates per-application profiles for libraries. This is equivalent to the opcontrol --separate=library command. If Per-application profiles, including kernel is selected, OProfile generates per-application profiles for the kernel and kernel modules as discussed in Section 29.2.3, "Separating Kernel and User-space Profiles" . This is equivalent to the opcontrol --separate=kernel command. To force data to be written to samples files as discussed in Section 29.5, "Analyzing the Data" , click the Flush button. This is equivalent to the opcontrol --dump command. To start OProfile from the graphical interface, click Start . To stop the profiler, click Stop . Exiting the application does not stop OProfile from sampling.

Commands:
4.76. gnome-session 4.76.1. RHEA-2011:1654 - gnome-session bug fix and enhancement update Updated gnome-session packages that fix a bug and add an enhancement are now available for Red Hat Enterprise Linux 6. The gnome-session package manages the GNOME desktop session. It starts up the other core components of GNOME and handles logout and saving of the session. Bug Fix BZ# 664516 Prior to this update, the gnome-session utility may have improperly saved desktop sessions. As a consequence, when logging in, the running applications were incorrectly collapsed from multiple workspaces into the first workspace and their initial position was not restored. This has been fixed: applications are now restored in their original workspaces and correctly positionally placed. Enhancement BZ# 622849 Prior to this update, users were not able to manage multiple custom GNOME sessions while being logged in. Now, multiple sessions can be managed under the Options tab of System -> Preferences -> Startup Applications. Users are advised to upgrade to these updated gnome-session packages, which resolve this bug and add this enhancement.

Commands:
Chapter 9. Troubleshooting and deleting remaining resources during Uninstall Occasionally some of the custom resources managed by an operator may remain in "Terminating" status waiting on the finalizer to complete, although you have performed all the required cleanup tasks. In such an event you need to force the removal of such resources. If you do not do so, the resources remain in the "Terminating" state even after you have performed all the uninstall steps. Check if the openshift-storage namespace is stuck in Terminating state upon deletion. Output: Check for the NamespaceFinalizersRemaining and NamespaceContentRemaining messages in the STATUS section of the command output and perform the step for each of the listed resources. Example output : Delete all the remaining resources listed in the step. For each of the resources to be deleted, do the following: Get the object kind of the resource which needs to be removed. See the message in the above output. Example : message: Some content in the namespace has finalizers remaining: cephobjectstoreuser.ceph.rook.io Here cephobjectstoreuser.ceph.rook.io is the object kind. Get the Object name corresponding to the object kind. Example : Example output: Patch the resources. Example: Output: Verify that the openshift-storage project is deleted. Output: If the issue persists, reach out to Red Hat Support .

Commands:
oc get project -n <namespace>
NAME DISPLAY NAME STATUS openshift-storage Terminating
oc get project openshift-storage -o yaml
status: conditions: - lastTransitionTime: "2020-07-26T12:32:56Z" message: All resources successfully discovered reason: ResourcesDiscovered status: "False" type: NamespaceDeletionDiscoveryFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: All legacy kube types successfully parsed reason: ParsedGroupVersions status: "False" type: NamespaceDeletionGroupVersionParsingFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: All content successfully deleted, may be waiting on finalization reason: ContentDeleted status: "False" type: NamespaceDeletionContentFailure - lastTransitionTime: "2020-07-26T12:32:56Z" message: 'Some resources are remaining: cephobjectstoreusers.ceph.rook.io has 1 resource instances' reason: SomeResourcesRemain status: "True" type: NamespaceContentRemaining - lastTransitionTime: "2020-07-26T12:32:56Z" message: 'Some content in the namespace has finalizers remaining: cephobjectstoreuser.ceph.rook.io in 1 resource instances' reason: SomeFinalizersRemain status: "True" type: NamespaceFinalizersRemaining
oc get <Object-kind> -n <project-name>
oc get cephobjectstoreusers.ceph.rook.io -n openshift-storage
NAME AGE noobaa-ceph-objectstore-user 26h
oc patch -n <project-name> <object-kind>/<object-name> --type=merge -p '{"metadata": {"finalizers":null}}'
oc patch -n openshift-storage cephobjectstoreusers.ceph.rook.io/noobaa-ceph-objectstore-user --type=merge -p '{"metadata": {"finalizers":null}}'
cephobjectstoreuser.ceph.rook.io/noobaa-ceph-objectstore-user patched
oc get project openshift-storage
Error from server (NotFound): namespaces "openshift-storage" not found
8.82. hal 8.82.1. RHBA-2014:1460 - hal bug fix and enhancement update Updated hal packages that fix two bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The hal packages provide the Hardware Abstraction Layer (HAL) daemon. HAL collects and maintains information about the hardware on the system from several sources, and provides a live device list through D-BUS. Bug Fixes BZ# 736415 Prior to this update, the HAL daemon did not properly handle the hot plug addition and removal events. Consequently, the HAL daemon terminated unexpectedly with a segmentation fault during device probing. With this update, hot plug events are properly handled and the HAL daemon no longer crashes in the aforementioned scenario. BZ# 755209 Prior to this update, the /usr/libexec/hald-probe-smbios script, as well as certain other hald-probe scripts, terminated unexpectedly after they were manually started. This bug has been fixed and the aforementioned scripts can be started manually without complications. In addition, this update adds the following Enhancement BZ# 1076664 Previously, the HAL daemon did not recognize touchscreen monitors correctly. Consequently, these monitors were not added to the list of hot plugged devices in the Xorg window system. Support for touchscreen devices has been added to HAL and these devices are now recognized correctly. Users of hal are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
2.2. Boot Loader GRUB 2 Red Hat Enterprise Linux 7 includes a new boot loader, GRUB 2, which is more robust, portable, and powerful than its predecessor, GRUB, which is the boot loader that Red Hat Enterprise Linux 6 uses. GRUB 2 provides a number of features and improvements, the most notable of which are: In addition to the 64-bit Intel and AMD architectures, GRUB 2 supports a wider variety of platforms, including PowerPC. GRUB 2 supports additional firmware types, including BIOS, EFI and OpenFirmware. In addition to supporting Master Boot Record (MBR) partition tables, GRUB 2 supports GUID Partition Tables (GPT). In addition to the Linux file systems, GRUB 2 also supports non-Linux file systems such as Apple Hierarchical File System Plus ( HFS+ ) and Microsoft NTFS file system.

Commands:
20.14. Using Active Directory-formatted User Names for Authentication When you connect to Directory Server, you must specify the distinguished name (DN) of the user, such as uid= user_name ,ou=People,dc=example,dc=com , to authenticate. However, the DN can be difficult to remember. If you enable and configure the AD DN plug-in, you can use Active Directory-formatted user names, such as user_name or user_name @ domain instead of the DN. After you enable the plug-in and a user connects to the directory using a user name that is not DN-formatted, Directory Server searches the DN based on the plug-in's configuration. If the search returns one DN, Directory Server uses this DN for the authentication. If none or multiple DNs are returned, authentication fails. Note You can only enable and configure the AD DN plug-in using the command line. To enable and configure the plug-in it to use example.com as the default domain: Add the cn=addn,cn=plugins,cn=config plug-in entry and set the default domain: The required addn_default_domain parameter in the plug-in entry sets the default domain. The plug-in appends this domain if the specified user name during an authentication does not contain a domain name. Add a configuration entry for the default domain: For details about the parameters used in the example, see their descriptions in the Red Hat Directory Server Configuration, Command, and File Reference . Warning You must add at least a configuration entry for the default domain. If the entry is missing, Directory Server fails to start. Optionally, you can create additional domain configurations as described in the step to support multiple domain names. Each domain configuration can use a different search base and filter. Restart the Directory Server instance:

Commands:
ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: cn=addn,cn=plugins,cn=config changetype: add objectClass: top objectClass: nsSlapdPlugin objectClass: extensibleObject cn: addn nsslapd-pluginPath: libaddn-plugin nsslapd-pluginInitfunc: addn_init nsslapd-pluginType: preoperation nsslapd-pluginEnabled: on nsslapd-pluginId: addn nsslapd-pluginVendor: 389 Project nsslapd-pluginVersion: 1.3.6.0 nsslapd-pluginDescription: Allow AD DN style bind names to LDAP addn_default_domain: example.com
ldapmodify -D "cn=Directory Manager" -W -p 389 -h server.example.com -x dn: cn= example.com ,cn=addn,cn=plugins,cn=config changetype: add objectClass: top objectClass: extensibleObject cn: example.com addn_base: ou=People,dc=example,dc=com addn_filter: (&(objectClass=account)(uid=%s))
dsctl instance_name restart
21.3.4. Adding an AppSocket/HP JetDirect printer Follow this procedure to add an AppSocket/HP JetDirect printer: Open the New Printer dialog (see Section 21.3.1, "Starting the Printer Configuration Tool" ). In the list on the left, select Network Printer AppSocket/HP JetDirect . On the right, enter the connection settings: Hostname Printer host name or IP address. Port Number Printer port listening for print jobs ( 9100 by default). Figure 21.5. Adding a JetDirect printer Click Forward . Select the printer model. See Section 21.3.8, "Selecting the Printer Model and Finishing" for details.

Commands:
E.2.25. /proc/stat This file keeps track of a variety of different statistics about the system since it was last restarted. The contents of /proc/stat , which can be quite long, usually begins like the following example: Some of the more commonly used statistics include: cpu - Measures the number of jiffies (1/100 of a second for x86 systems) that the system has been in user mode, user mode with low priority (nice), system mode, idle task, I/O wait, IRQ (hardirq), and softirq respectively. The IRQ (hardirq) is the direct response to a hardware event. The IRQ takes minimal work for queuing the "heavy" work up for the softirq to execute. The softirq runs at a lower priority than the IRQ and therefore may be interrupted more frequently. The total for all CPUs is given at the top, while each individual CPU is listed below with its own statistics. The following example is a 4-way Intel Pentium Xeon configuration with multi-threading enabled, therefore showing four physical processors and four virtual processors totaling eight processors. page - The number of memory pages the system has written in and out to disk. swap - The number of swap pages the system has brought in and out. intr - The number of interrupts the system has experienced. btime - The boot time, measured in the number of seconds since January 1, 1970, otherwise known as the epoch .

Commands:
cpu 259246 7001 60190 34250993 137517 772 0 cpu0 259246 7001 60190 34250993 137517 772 0 intr 354133732 347209999 2272 0 4 4 0 0 3 1 1249247 0 0 80143 0 422626 5169433 ctxt 12547729 btime 1093631447 processes 130523 procs_running 1 procs_blocked 0 preempt 5651840 cpu 209841 1554 21720 118519346 72939 154 27168 cpu0 42536 798 4841 14790880 14778 124 3117 cpu1 24184 569 3875 14794524 30209 29 3130 cpu2 28616 11 2182 14818198 4020 1 3493 cpu3 35350 6 2942 14811519 3045 0 3659 cpu4 18209 135 2263 14820076 12465 0 3373 cpu5 20795 35 1866 14825701 4508 0 3615 cpu6 21607 0 2201 14827053 2325 0 3334 cpu7 18544 0 1550 14831395 1589 0 3447 intr 15239682 14857833 6 0 6 6 0 5 0 1 0 0 0 29 0 2 0 0 0 0 0 0 0 94982 0 286812 ctxt 4209609 btime 1078711415 processes 21905 procs_running 1 procs_blocked 0
Chapter 2. Installation This chapter guides you through the steps to install AMQ C++ in your environment. 2.1. Prerequisites You must have a subscription to access AMQ release files and repositories. To install packages on Red Hat Enterprise Linux, you must register your system . To build programs using AMQ C++ on Red Hat Enterprise Linux, you must install the gcc-c++ , cmake , and make packages. To build programs using AMQ C++ on Microsoft Windows, you must install Visual Studio. 2.2. Installing on Red Hat Enterprise Linux Procedure Use the subscription-manager command to subscribe to the required package repositories. If necessary, replace <variant> with the value for your variant of Red Hat Enterprise Linux (for example, server or workstation ). Red Hat Enterprise Linux 7 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms Red Hat Enterprise Linux 8 USD sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms Use the yum command to install the qpid-proton-cpp-devel and qpid-proton-cpp-docs packages. USD sudo yum install qpid-proton-cpp-devel qpid-proton-cpp-docs For more information about using packages, see Appendix B, Using Red Hat Enterprise Linux packages . 2.3. Installing on Microsoft Windows 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 Clients entry in the INTEGRATION AND AUTOMATION category. Click Red Hat AMQ Clients . The Software Downloads page opens. Download the AMQ Clients 2.9.0 C++ .zip file. Extract the file contents into a directory of your choosing by right-clicking on the zip file and selecting Extract All . When you extract the contents of the .zip file, a directory named amq-clients-2.9.0-cpp-win is created. This is the top-level directory of the installation and is referred to as <install-dir> throughout this document.

Commands:
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-7- <variant> -rpms
sudo subscription-manager repos --enable=amq-clients-2-for-rhel-8-x86_64-rpms
sudo yum install qpid-proton-cpp-devel qpid-proton-cpp-docs
12.3. Querying Cluster Property Settings In most cases, when you use the pcs command to display values of the various cluster components, you can use pcs list or pcs show interchangeably. In the following examples, pcs list is the format used to display an entire list of all settings for more than one property, while pcs show is the format used to display the values of a specific property. To display the values of the property settings that have been set for the cluster, use the following pcs command. To display all of the values of the property settings for the cluster, including the default values of the property settings that have not been explicitly set, use the following command. To display the current value of a specific cluster property, use the following command. For example, to display the current value of the cluster-infrastructure property, execute the following command: For informational purposes, you can display a list of all of the default values for the properties, whether they have been set to a value other than the default or not, by using the following command.

Commands:
pcs property list
pcs property list --all
pcs property show property
pcs property show cluster-infrastructure Cluster Properties: cluster-infrastructure: cman
pcs property [list|show] --defaults
5.8. Automating the Installation with Kickstart Red Hat Enterprise Linux 7 offers a way to partially or fully automate the installation process using a Kickstart file . Kickstart files contain answers to all questions normally asked by the installation program, such as what time zone do you want the system to use, how should the drives be partitioned or which packages should be installed. Providing a prepared Kickstart file at the beginning of the installation therefore allows you to perform the entire installation (or parts of it) automatically, without need for any intervention from the user. This is especially useful when deploying Red Hat Enterprise Linux on a large number of systems at once. In addition to allowing you to automate the installation, Kickstart files also provide more options regarding software selection. When installing Red Hat Enterprise Linux manually using the graphical installation interface, your software selection is limited to pre-defined environments and add-ons. A Kickstart file allows you to install or remove individual packages as well. For instructions about creating a Kickstart file and using it to automate the installation, see Chapter 27, Kickstart Installations .

Commands:
5.284. rpcbind 5.284.1. RHEA-2012:0974 - rpcbind enhancement update Enhanced rpcbind packages that add one enhancement are now available for Red Hat Enterprise Linux 6. The rpcbind utility maps RPC (Remote Procedure Call) services to the ports on which the services listen and allows the host to make RPC calls to the RPC server. Enhancement BZ# 726954 The rpcbind tool did not drop supplementary groups and the groups remained available after rpcbind downgraded from root-group privileges. As a security hardening measure, rpcbind now drops root privileges correctly, running as a non-root user after it has bound to its privileged network port. Users of rpcbind are advised to upgrade to these enhanced packages, which add this enhancement. 5.284.2. RHBA-2013:1453 - rpcbind bug fix Updated rpcbind packages that fix one bug are now available for Red Hat Enterprise Linux 6 Extended Update Support. The rpcbind utility maps RPC (Remote Procedure Call) services to the ports on which the services listen and allows the host to make RPC calls to the RPC server. Bug Fix BZ# 858573 Previously, in the insecure mode, which enables non-root users to set or unset ports, a privileged port was required. As only root users can obtain a privileged port, non-root users could not set or unset ports. To fix this bug, the privileged port has been removed, and thus non-root users are now allowed to set or unset ports on the loopback interface. All users of rpcbind are advised to upgrade to these updated packages, which fix this bug.

Commands:
8.80. java-1.7.0-openjdk 8.80.1. RHBA-2013:1611 - java-1.7.0-openjdk bug fix and enhancement update Updated java-1.7.0-openjdk packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The java-1.7.0-openjdk packages provide the OpenJDK 7 Java Runtime Environment and the OpenJDK 7 Software Development Kit. Note The java-1.7.0-openjdk package has been upgraded to upstream version 2.4.3, which provides a number of bug fixes and enhancements over the version. Bug Fixes BZ# 825824 Attempting to compile a SystemTap script using the jstack tapset could have failed with an error similar to the following: error: the frame size of 272 bytes is larger than 256 bytes This update corrects the jstack tapset and resolves this problem. BZ# 871771 Because of incorrect KDC list concatenation logic, the sun.security.krb5.Config.getKDCList method returned incorrect KDC lists when the dns_lookup_kdc property in the krb5.conf file was set to true. The concatenation logic has been fixed with this release and correct KDC lists are now returned. BZ# 997633 The java-1.7.0-openjdk RPM package contained incorrect specification of the libnss3 dependency and installed its x86_64 version on i686 systems. Because of the missing dependency, launching the java command with the -Dcom.sun.management.jmxremote parameter on 32bit JVMs terminated unexpectedly. The dependency specification has been corrected with this update. As a result, the correct version of the libnss3 package is installed and the java command no longer terminates when launched with the -Dcom.sun.management.jmxremote parameter. Enhancements BZ# 831734 , BZ# 905128 The NSS security provider is now the default security provider in OpenJDK 7. This brings a significant performance improvement over the releases. BZ# 916288 The java-1.7.0-openjdk RPM package now provides the java dependency. As a result, it is no longer necessary to have the java-1.6.0-openjdk package installed alongside java-1.7.0-openjdk for the java dependency to be available. Users of java-1.7.0-openjdk are advised to upgrade to these updated packages, which fix these bugs and add these enhancements. All running instances of OpenJDK Java must be restarted for the update to take effect.

Commands:
Chapter 9. Refreshing external user groups for LDAP To set the LDAP source to synchronize user group membership automatically on user login, in the Auth Source page, select the Usergroup Sync option. If this option is not selected, LDAP user groups are refreshed automatically through a scheduled cron job synchronizing the LDAP Authentication source every 30 minutes by default. If the user groups in the LDAP Authentication source change in the lapse of time between scheduled tasks, the user can be assigned to incorrect external user groups. This is corrected automatically when the scheduled task runs. Use this procedure to refresh the LDAP source manually. Procedure In the Satellite web UI, navigate to Administer > Usergroups and select a user group. On the External Groups tab, click Refresh to the right of the required user group. CLI procedure Enter the following command:

Commands:
foreman-rake ldap:refresh_usergroups