mtpti5iD/redhat-docs_dataset huggingface dataset:
5.9.3.2.2. Viewing /proc/mounts The /proc/mounts file is part of the proc virtual file system. As with the other files under /proc/ , the mounts "file" does not exist on any disk drive in your Red Hat Enterprise Linux system. In fact, it is not even a file; instead it is a representation of system status made available (by the Linux kernel) in file form. Using the command cat /proc/mounts , we can view the status of all mounted file systems: As we can see from the above example, the format of /proc/mounts is very similar to that of /etc/mtab . There are a number of file systems mounted that have nothing to do with disk drives. Among these are the /proc/ file system itself (along with two other file systems mounted under /proc/ ), pseudo-ttys, and shared memory. While the format is admittedly not very user-friendly, looking at /proc/mounts is the best way to be 100% sure of seeing what is mounted on your Red Hat Enterprise Linux system, as the kernel is providing this information. Other methods can, under rare circumstances, be inaccurate. However, most of the time you will likely use a command with more easily-read (and useful) output. The section describes that command.

Commands:
rootfs / rootfs rw 0 0 /dev/root / ext3 rw 0 0 /proc /proc proc rw 0 0 usbdevfs /proc/bus/usb usbdevfs rw 0 0 /dev/sda1 /boot ext3 rw 0 0 none /dev/pts devpts rw 0 0 /dev/sda4 /home ext3 rw 0 0 none /dev/shm tmpfs rw 0 0 none /proc/sys/fs/binfmt_misc binfmt_misc rw 0 0
16.6.2. Running virt-rescue Before you use virt-rescue on a guest virtual machine, make sure the guest virtual machine is not running, otherwise disk corruption will occur. When you are sure the guest virtual machine is not live, enter: (where GuestName is the guest name as known to libvirt), or: (where the path can be any file, any logical volume, LUN, or so on) containing a guest virtual machine disk. You will first see output scroll past, as virt-rescue boots the rescue VM. In the end you will see: The shell prompt here is an ordinary bash shell, and a reduced set of ordinary Red Hat Enterprise Linux commands is available. For example, you can enter: The command will list disk partitions. To mount a file system, it is suggested that you mount it under /sysroot , which is an empty directory in the rescue machine for the user to mount anything you like. Note that the files under / are files from the rescue VM itself: When you are finished rescuing the guest virtual machine, exit the shell by entering exit or Ctrl+d . virt-rescue has many command line options. The options most often used are: --ro : Operate in read-only mode on the guest virtual machine. No changes will be saved. You can use this to experiment with the guest virtual machine. As soon as you exit from the shell, all of your changes are discarded. --network : Enable network access from the rescue shell. Use this if you need to, for example, download RPM or other files into the guest virtual machine.

Commands:
virt-rescue GuestName
virt-rescue /path/to/disk/image
Welcome to virt-rescue, the libguestfs rescue shell. Note: The contents of / are the rescue appliance. You have to mount the guest virtual machine's partitions under /sysroot before you can examine them. bash: cannot set terminal process group (-1): Inappropriate ioctl for device bash: no job control in this shell ><rescue>
><rescue> fdisk -l /dev/vda
><rescue> mount /dev/vda1 /sysroot/ EXT4-fs (vda1): mounted filesystem with ordered data mode. Opts: (null) ><rescue> ls -l /sysroot/grub/ total 324 -rw-r--r--. 1 root root 63 Sep 16 18:14 device.map -rw-r--r--. 1 root root 13200 Sep 16 18:14 e2fs_stage1_5 -rw-r--r--. 1 root root 12512 Sep 16 18:14 fat_stage1_5 -rw-r--r--. 1 root root 11744 Sep 16 18:14 ffs_stage1_5 -rw-------. 1 root root 1503 Oct 15 11:19 grub.conf [...]
Chapter 7. New Packages 7.1. RHEA-2013:1625 - new packages: freerdp New freerdp packages are now available for Red Hat Enterprise Linux 6. FreeRDP is a free implementation of the Remote Desktop Protocol (RDP), released under the Apache license. The xfreerdp client can connect to RDP servers such as Microsoft Windows machines, xrdp and VirtualBox. This enhancement update adds the freerdp packages to Red Hat Enterprise Linux 6. (BZ# 951696 ) All users who require freerdp are advised to install these new packages.

Commands:
4.5. Configure Expiration In Red Hat JBoss Data Grid, expiration is configured in a manner similar to eviction, with differing parameters for Library Mode and Remote Client-Server Mode. Procedure 4.1. Configure Expiration in Library Mode Add the Expiration Tag Add the <expiration> tag to your project's <cache> tags as follows: Set the Expiration Lifespan Set the lifespan value to set the period of time (in milliseconds) an entry can remain in memory. The following is an example of this step: Set the Maximum Idle Time Set the time that entries are allowed to remain idle (unused) after which they are removed (in milliseconds). The default value is -1 for unlimited time. Set the Background Reaper Thread Enable or disable the background reaper thread to test entries for expiration. Regardless of whether a reaper is used, entries are tested for expiration lazily when they are touched. The default value is true . Set the Expiration Interval Set the interval (in milliseconds) between subsequent runs to purge expired entries from memory and any associated cache stores. To disable the periodic eviction process set the interval to -1 . The default value is 1000 . Procedure 4.2. Configuration Expiration in Remote Client-Server Mode Set the Expiration Lifespan Set the lifespan value to set the period of time (in milliseconds) an entry can remain in memory. The following is an example of this step: Set the Maximum Idle Time Set the time that entries are allowed to remain idle (unused) after which they are removed (in milliseconds). The default value is -1 for unlimited time. Set the Expiration Interval Set the interval (in milliseconds) between subsequent runs to purge expired entries from memory and any associated cache stores. To disable the periodic eviction process set the interval to -1 . The default value is 5000 . Reaper Thread in Remote Client-Server Mode In Remote Client-Server Mode the background reaper thread is only enabled if interval is greater than 0 . As interval defaults to 5000 the background reaper thread is automatically enabled if expiration is configured. Report a bug

Commands:
<expiration />
<expiration lifespan="1000" />
<expiration lifespan="1000" maxIdle="1000" />
<expiration lifespan="1000" maxIdle="1000" reaperEnabled="true" />
<expiration lifespan="1000" maxIdle="1000" reaperEnabled="true" wakeUpInterval="5000" />
<expiration lifespan="1000" />
<expiration lifespan="1000" max-idle="1000" />
<expiration lifespan="1000" max-idle="1000" interval="10000" />
1.3. A Look at Managing Certificates (Non-TMS) A conventional PKI environment provides the basic framework to manage certificates stored in software databases. This is a non-TMS environment, since it does not manage certificates on smart cards. At a minimum, a non-TMS requires only a CA, but a non-TMS environment can use OCSP responders and KRA instances as well. For information on this topic, see the following sections in the Red Hat Certificate System Planning, Installation, and Deployment Guide : Managing Certificates Using a Single Certificate Manager Planning for Lost Keys: Key Archival and Recovery Balancing Certificate Request Processing Balancing Client OCSP Requests

Commands:
Chapter 2. Executive reports You can download a high-level executive report summarizing the security exposure of your infrastructure. Executive reports are two to three-page PDF files, designed for an executive audience, and include the following information: On page 1 Number of RHEL systems analyzed Number of individual CVEs to which your systems are currently exposed Number of security rules in your infrastructure List of CVEs that have advisories On page 2 Percentage of CVEs by severity (CVSS base score) range Number of CVEs published by 7, 30, and 90 day time frame Top three CVEs in your infrastructure, including security rules and known exploits On page 3 Security rule breakdown by severity Top 3 security rules, including severity and number of exposed systems 2.1. Downloading an executive report Use the following steps to download an executive report for key stakeholders in your security organization: Procedure Navigate to the Security > Vulnerability > Reports tab and log in if necessary. On the Executive report card, click Download PDF . Click Save File and click OK . Verification Verify that the PDF file is in your Downloads folder or other specified location. 2.2. Downloading an executive report using the vulnerability service API You can download an executive report using the vulnerability service API . Request URL: https://console.openshiftusgov.com/api/vulnerability/v1/report/executive Curl: curl -X GET "https://console.openshiftusgov.com/api/vulnerability/v1/report/executive" -H "accept: application/vnd.api+json"

Commands:
curl -X GET "https://console.openshiftusgov.com/api/vulnerability/v1/report/executive" -H "accept: application/vnd.api+json"
4.263. raptor 4.263.1. RHSA-2012:0410 - Important: raptor security update Updated raptor packages that fix one security issue are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having important security impact. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available from the CVE link(s) associated with each description below. Raptor provides parsers for Resource Description Framework (RDF) files. Security Fix CVE-2012-0037 An XML External Entity expansion flaw was found in the way Raptor processed RDF files. If an application linked against Raptor were to open a specially-crafted RDF file, it could possibly allow a remote attacker to obtain a copy of an arbitrary local file that the user running the application had access to. A bug in the way Raptor handled external entities could cause that application to crash or, possibly, execute arbitrary code with the privileges of the user running the application. Red Hat would like to thank Timothy D. Morgan of VSR for reporting this issue. All Raptor users are advised to upgrade to these updated packages, which contain a backported patch to correct this issue. All running applications linked against Raptor must be restarted for this update to take effect.

Commands:
Chapter 9. Logging Logging is important in troubleshooting and debugging. By default logging is turned off. To enable logging, you must set a logging level and provide a delegate function to receive the log messages. 9.1. Setting the log output level The library emits log traces at different levels: Error Warning Information Verbose The lowest log level, Error , traces only error events and produces the fewest log messages. A higher log level includes all the log levels below it and generates a larger volume of log messages. 9.2. Enabling protocol logging The Log level Frame is handled differently. Setting trace level Frame enables tracing outputs for AMQP protocol headers and frames. Logical OR must be used to get normal tracing output and AMQP frame tracing at the same time. For example The following code writes AMQP frames to the console. Example: Logging delegate Trace.TraceLevel = TraceLevel.Frame; Trace.TraceListener = (f, a) => Console.WriteLine( DateTime.Now.ToString("[hh:mm:ss.fff]") + " " + string.Format(f, a));

Commands:
// Enable Error logs only. Trace.TraceLevel = TraceLevel.Error
// Enable Verbose logs. This includes logs at all log levels. Trace.TraceLevel = TraceLevel.Verbose
// Enable just AMQP frame tracing Trace.TraceLevel = TraceLevel.Frame;
// Enable AMQP Frame logs, and Warning and Error logs Trace.TraceLevel = TraceLevel.Frame | TraceLevel.Warning;
Trace.TraceLevel = TraceLevel.Frame; Trace.TraceListener = (f, a) => Console.WriteLine( DateTime.Now.ToString("[hh:mm:ss.fff]") + " " + string.Format(f, a));
Deploying and managing OpenShift Data Foundation using Red Hat OpenStack Platform Red Hat OpenShift Data Foundation 4.9 Instructions on deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install and manage Red Hat OpenShift Data Foundation using Red Hat OpenShift Container Platform on Red Hat OpenStack Platform (RHOSP). Important Deploying and managing OpenShift Data Foundation on Red Hat OpenStack Platform is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Commands:
4.210. openssl-ibmca 4.210.1. RHBA-2011:1568 - openssl-ibmca bug fix and enhancement update An updated openssl-ibmca package that fixes several bugs and adds various enhancements is available for Red Hat Enterprise Linux 6. The openssl-ibmca package provides a dynamic OpenSSL engine for the IBM eServer Cryptographic Accelerator (ICA) crypto hardware on IBM eServer zSeries machines. The openssl-ibmca package has been upgraded to upstream version 1.2, which provides a number of bug fixes and enhancements over the version. (BZ# 694194 ) All users of openssl-ibmca are advised to upgrade to this updated package, which fixes these bug and adds these enhancements. 4.210.2. RHBA-2012:0433 - openssl-ibmca bug fix update An updated openssl-ibmca package that fixes one bug is now available for Red Hat Enterprise Linux 6. The openssl-ibmca package provides a dynamic OpenSSL engine for the IBM eServer Cryptographic Accelerator (ICA) crypto hardware on IBM eServer zSeries machines. Bug Fix BZ# 804612 Due to a bug in the ibmca OpenSSL engine code, applications using the OpenSSL library terminated unexpectedly with a segmentation fault when running the ibmca engine with ciphers enabled in output feedback (OFB) mode on IBM System z, z196 series, hardware. A patch has been applied to address this issue, ensuring that the OpenSSL library no longer crashes under these circumstances. All users of openssl-ibmca are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 10. Internationalization 10.1. Red Hat Enterprise Linux 8 international languages Red Hat Enterprise Linux 8 supports the installation of multiple languages and the changing of languages based on your requirements. East Asian Languages - Japanese, Korean, Simplified Chinese, and Traditional Chinese. European Languages - English, German, Spanish, French, Italian, Portuguese, and Russian. The following table lists the fonts and input methods provided for various major languages. Language Default Font (Font Package) Input Methods English dejavu-sans-fonts French dejavu-sans-fonts German dejavu-sans-fonts Italian dejavu-sans-fonts Russian dejavu-sans-fonts Spanish dejavu-sans-fonts Portuguese dejavu-sans-fonts Simplified Chinese google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-libpinyin, libpinyin Traditional Chinese google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-libzhuyin, libzhuyin Japanese google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-kkc, libkkc Korean google-noto-sans-cjk-ttc-fonts, google-noto-serif-cjk-ttc-fonts ibus-hangul, libhangul 10.2. Notable changes to internationalization in RHEL 8 RHEL 8 introduces the following changes to internationalization compared to RHEL 7: Support for the Unicode 11 computing industry standard has been added. Internationalization is distributed in multiple packages, which allows for smaller footprint installations. For more information, see Using langpacks . several glibc locales have been synchronized with Unicode Common Locale Data Repository (CLDR).

Commands:
7.4. Run Red Hat JBoss Data Grid with a Custom Configuration To run Red Hat JBoss Data Grid with a custom configuration, add a configuration file to the USDJDG_HOME/standalone/configuration directory. Use the following command to specify the created custom configuration file for standalone mode: Use the following command to specify the created custom configuration file for clustered mode: The -c used for this script does not allow absolute paths, therefore the specified file must be available in the USDJDG_HOME/standalone/configuration directory. If the command is run without the -c parameter, JBoss Data Grid uses the default configuration. Report a bug

Commands:
USDJDG_HOME/bin/standalone.sh -c USD{FILENAME}
USDJDG_HOME/bin/clustered.sh -c USD{FILENAME}
Chapter 58. Security OpenSCAP rpmverifypackage does not work correctly The chdir and chroot system calls are called twice by the rpmverifypackage probe. Consequently, an error occurs when the probe is utilized during an OpenSCAP scan with custom Open Vulnerability and Assessment Language (OVAL) content. To work around this problem, do not use the rpmverifypackage_test OVAL test in your content or use only the content from the scap-security-guide package where rpmverifypackage_test is not used. (BZ# 1603347 ) dconf databases are not checked by OVAL OVAL (Open Vulnerability and Assessment Language) checks used in the SCAP Security Guide project are not able to read a dconf binary database, only files used to generate the database. The database is not regenerated automatically, the administrator needs to enter the dconf update command. As a consequence, changes to the database that are not made using files in the /etc/dconf/db/ directory cannot be detected by scanning. This may cause false negatives results. To work around this problem, run dconf update periodically, for example, using the /etc/crontab configuration file. (BZ# 1631378 ) SCAP Workbench fails to generate results-based remediations from tailored profiles The following error occurs when trying to generate results-based remediation roles from a customized profile using the the SCAP Workbench tool: To work around this problem, use the oscap command with the --tailoring-file option. (BZ# 1533108 ) OpenSCAP scanner results contain a lot of SELinux context error messages The OpenSCAP scanner logs inability to get SELinux context on the ERROR level even in situations where it is not a true error. As a result, OpenSCAP scanner results contain a lot of SELinux context error messages. Both the oscap command-line utility and the SCAP Workbench graphical utility outputs can be hard to read for that reason. (BZ# 1640522 ) oscap scans use an excessive amount of memory Result data of Open Vulnerability Assessment Language (OVAL) probes are kept in memory for the whole duration of a scan and the generation of reports is also a memory-intensive process. Consequently, when very large file systems are scanned, the oscap process can take all available memory and be killed by the operating system. To work around this problem, use tailoring to exclude rules that scan complete file systems and run them separately. Furthermore, do not use the --oval-results option. As a result, if you lower the amount of processed data, scanning of the system should no longer crash because of the excessive use of memory. (BZ#1548949)

Commands:
Error generating remediation role '.../remediation.sh': Exit code of 'oscap' was 1: [output truncated]
Deploying and managing OpenShift Data Foundation using Google Cloud Red Hat OpenShift Data Foundation 4.9 Instructions on deploying and managing OpenShift Data Foundation on existing Red Hat OpenShift Container Platform Google Cloud clusters Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install and manage Red Hat OpenShift Data Foundation using Red Hat OpenShift Container Platform on Google Cloud. Important Deploying and managing OpenShift Data Foundation on Google Cloud is a Technology Preview feature. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process.

Commands:
Chapter 4. Fencing: Configuring STONITH STONITH is an acronym for Shoot-The-Other-Node-In-The-Head and it protects your data from being corrupted by rogue nodes or concurrent access. Just because a node is unresponsive, this does not mean it is not accessing your data. The only way to be 100% sure that your data is safe, is to fence the node using STONITH so we can be certain that the node is truly offline, before allowing the data to be accessed from another node. STONITH also has a role to play in the event that a clustered service cannot be stopped. In this case, the cluster uses STONITH to force the whole node offline, thereby making it safe to start the service elsewhere. 4.1. Available STONITH (Fencing) Agents Use the following command to view of list of all available STONITH agents. You specify a filter, then this command displays only the STONITH agents that match the filter.

Commands:
pcs stonith list [ filter ]
Chapter 337. Adding Security Definitions in API doc Available as of Camel 3.1.0 The Rest DSL now supports declaring OpenApi securityDefinitions in the generated API document. For example as shown below: rest("/user").tag("dude").description("User rest service") // setup security definitions .securityDefinitions() .oauth2("petstore_auth").authorizationUrl("http://petstore.swagger.io/oauth/dialog").end() .apiKey("api_key").withHeader("myHeader").end() .end() .consumes("application/json").produces("application/json") Here we have setup two security definitions OAuth2 - with implicit authorization with the provided url Api Key - using an api key that comes from HTTP header named myHeader Then you need to specify on the rest operations which security to use by referring to their key (petstore_auth or api_key). .get("/{id}/{date}").description("Find user by id and date").outType(User.class) .security("api_key") ... .put().description("Updates or create a user").type(User.class) .security("petstore_auth", "write:pets,read:pets") Here the get operation is using the Api Key security and the put operation is using OAuth security with permitted scopes of read and write pets.

Commands:
rest("/user").tag("dude").description("User rest service") // setup security definitions .securityDefinitions() .oauth2("petstore_auth").authorizationUrl("http://petstore.swagger.io/oauth/dialog").end() .apiKey("api_key").withHeader("myHeader").end() .end() .consumes("application/json").produces("application/json")
.get("/{id}/{date}").description("Find user by id and date").outType(User.class) .security("api_key") .put().description("Updates or create a user").type(User.class) .security("petstore_auth", "write:pets,read:pets")