mtpti5iD/redhat-docs_dataset huggingface dataset:
4.3.3. Exploring the Guest Virtual Machine You can view a virtual machine's console by selecting a virtual machine in the Virtual Machine Manager window and clicking Open . You can operate your Red Hat Enterprise Linux 7 virtual machine from the console in the same way as a physical system. Figure 4.7. The guest virtual machine console Show the graphical console : Shows the virtual machine's display. The virtual machine can be operated from the console the same as a physical machine. Show virtual hardware details : Shows details about the virtual hardware that the guest is using. These include an overview of basic system details, performance, processor, memory, and boot settings, and details of the system's virtual devices. These buttons control the virtual machine's state: Run : Turns on the virtual machine. Pause : Pauses the virtual machine. Shut down : Shuts down the virtual machine. Clicking on the arrow displays a drop-down menu with several options for turning off the virtual machine, including Reboot, Shut Down, Force Reset, Force Off, and Save. Full screen : Switches the virtual machine to full screen view. Send Key : Sends key combinations such as Ctrl+Alt+Backspace, Ctrl+Alt+Delete, Ctrl+Alt+F1, PrintScreen, and more to the virtual machine. Note For more information about using the Virtual Machine Manager to create and run virtual machines, refer to the Red Hat Enterprise Linux 6 Virtualization Host Configuration and Guest Installation Guide and the Red Hat Enterprise Linux 6 Virtualization Administration Guide .

Commands:
Image Builder Guide Red Hat Enterprise Linux 7 Creating customized system images with Image Builder Eliane Pereira Red Hat Customer Content Services elpereir@redhat.com Vladimir Slavik Red Hat Customer Content Services Abstract Image Builder is a tool for creating deployment-ready customized system images, for example installation disks, virtual machines, cloud vendor-specific images, and others. Image Builder enables you to create these images faster compared to manual procedures, because it abstracts away the specifics of each output type. Learn how to set up Image Builder and create images with it.

Commands:
5.51. dmraid 5.51.1. RHBA-2012:0910 - dmraid bug fix update Updated dmraid packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The dmraid packages provide the ATARAID/DDF1 activation tool. The tool supports RAID device discovery and RAID set activation. It also displays properties for ATARAID/DDF1-formatted RAID sets on Linux kernels using the device-mapper utility. Bug Fixes BZ# 729971 Prior to this update, a grub installation failed silently on a dmraid mirror because the device geometry of RAID sets was not set properly. Consequently, the set partition's MBR failed to be created and the partition failed to boot. With this update, the underlying code has been modified and the geometry on dmraid devices is set up correctly. BZ# 729032 The dmraid binary was compiled without gcc's -g option and the debuginfo file did not contain the ".debug_info" section. Consequently, it was not possible to generate debugging information and debug dmraid properly. With this update, the binary has been compiled with the proper debugging options and the problem no longer occurs. BZ# 701501 When the dmraid tool was accessing a 4 KB sector or smaller, it returned a misleading error message. With this update, the library function that checks the device size has been modified and the error message is no longer displayed under these circumstances. All users of dmraid are advised to upgrade to these updated packages, which fix these bug.

Commands:
8.224. spice-xpi 8.224.1. RHBA-2014:1560 - spice-xpi bug fix update Updated spice-xpi packages that fix one bug are now available for Red Hat Enterprise Linux 6. The spice-xpi packages provide the Simple Protocol for Independent Computing Environments (SPICE) extension for Mozilla that allows the SPICE client to be used from a web browser. This update fix the following update: * Due to a bug in the Red Hat Enterprise Virtualization Manager web admin portal, it was possible to open a second SPICE console, which caused the SPICE plug-in to terminate unexpectedly. With this update, the underlying source code has been modified to address this bug and the console no longer crashes in the described scenario. (BZ# 1073461 ) Bug Fix BZ# 1073461 Due to a bug in the Red Hat Enterprise Virtualization Manager web admin portal, it was possible to open a second SPICE console, which caused the SPICE plug-in to terminate unexpectedly. With this update, the underlying source code has been modified to address this bug and the console no longer crashes in the described scenario. This update fix the following update: Users of spice-xpi are advised to upgrade to these updated packages, which fix this bug. After installing the update, the Mozilla Firefox browser must be restarted for the changes to take effect.

Commands:
Configuring OpenShift Data Foundation Disaster Recovery for OpenShift Workloads Red Hat OpenShift Data Foundation 4.17 The OpenShift Data Foundation Disaster Recovery capabilities for Metropolitan and Regional regions is now General Available which also includes Disaster Recovery with stretch cluster. Red Hat Storage Documentation Team Abstract The intent of this solution guide is to detail the steps necessary to deploy OpenShift Data Foundation for disaster recovery with Advanced Cluster Management and stretch cluster to achieve a highly available storage infrastructure.

Commands:
6.3. Deployment 389-ds-base component, BZ# 878111 The ns-slapd utility terminates unexpectedly if it cannot rename the dirsrv- <instance> log files in the /var/log/ directory due to incorrect permissions on the directory. cpuspeed component, BZ# 626893 Some HP Proliant servers may report incorrect CPU frequency values in /proc/cpuinfo or /sys/device/system/cpu/*/cpufreq . This is due to the firmware manipulating the CPU frequency without providing any notification to the operating system. To avoid this ensure that the HP Power Regulator option in the BIOS is set to OS Control . An alternative available on more recent systems is to set Collaborative Power Control to Enabled . releng component, BZ# 644778 Some packages in the Optional repositories on RHN have multilib file conflicts. Consequently, these packages cannot have both the primary architecture (for example, x86_64) and secondary architecture (for example, i686) copies of the package installed on the same machine simultaneously. To work around this issue, install only one copy of the conflicting package. grub component, BZ# 695951 On certain UEFI-based systems, you may need to type BOOTX64 rather than bootx64 to boot the installer due to case sensitivity issues. grub component, BZ# 698708 When rebuilding the grub package on the x86_64 architecture, the glibc-static.i686 package must be used. Using the glibc-static.x86_64 package will not meet the build requirements.

Commands:
8.236. system-config-lvm 8.236.1. RHBA-2014:1403 - system-config-lvm bug fix update Updated system-config-lvm package that fixes several bugs is now available for Red Hat Enterprise Linux 6. The system-config-lvm utility enables users to configure logical volumes using a GUI. Bug Fixes BZ# 878253 Previously, the system-config-lvm utility did not support thin logical volumes. As a consequence, previously supported volumes could not be managed. With this update, thin logical volumes are still not supported but do not block managing supported volumes. BZ# 953071 Prior to this update, the Logical Volume Management (LVM) GUI was not always displayed correctly when accessed over remote access. Consequently, the user could not initiate the GUI. A patch has been provided to fix this bug, and the LVM GUI is now displayed correctly as intended. BZ# 1029755 Previously, when the ext3 Logical Volume (LV) partition was mounted and the user attempted to extend it online, the system-config-lvm utility tried to unmount ext3 and only after that to extend it. The underlying source code has been patched, and ext3 file systems can now be extended online using the command line tools without system-config-lvm trying to unmount it first. Users of system-config-lvm are advised to upgrade to this updated package, which fixes these bugs.

Commands:
Appendix D. Using AMQ Broker with the examples The AMQ .NET examples require a running message broker with a queue named amq.topic . Use the procedures below to install and start the broker and define the queue. D.1. Installing the broker Follow the instructions in Getting Started with AMQ Broker to install the broker and create a broker instance . Enable anonymous access. The following procedures refer to the location of the broker instance as <broker-instance-dir> . D.2. Starting the broker Procedure Use the artemis run command to start the broker. USD <broker-instance-dir> /bin/artemis run Check the console output for any critical errors logged during startup. The broker logs Server is now live when it is ready. USD example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server ... 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live ... D.3. Creating a queue In a new terminal, use the artemis queue command to create a queue named amq.topic . USD <broker-instance-dir> /bin/artemis queue create --name amq.topic --address amq.topic --auto-create-address --anycast You are prompted to answer a series of yes or no questions. Answer N for no to all of them. Once the queue is created, the broker is ready for use with the example programs. D.4. Stopping the broker When you are done running the examples, use the artemis stop command to stop the broker. USD <broker-instance-dir> /bin/artemis stop Revised on 2020-10-08 11:23:41 UTC

Commands:
<broker-instance-dir> /bin/artemis run
example-broker/bin/artemis run __ __ ____ ____ _ /\ | \/ |/ __ \ | _ \ | | / \ | \ / | | | | | |_) |_ __ ___ | | _____ _ __ / /\ \ | |\/| | | | | | _ <| '__/ _ \| |/ / _ \ '__| / ____ \| | | | |__| | | |_) | | | (_) | < __/ | /_/ \_\_| |_|\___\_\ |____/|_| \___/|_|\_\___|_| Red Hat AMQ <version> 2020-06-03 12:12:11,807 INFO [org.apache.activemq.artemis.integration.bootstrap] AMQ101000: Starting ActiveMQ Artemis Server 2020-06-03 12:12:12,336 INFO [org.apache.activemq.artemis.core.server] AMQ221007: Server is now live
<broker-instance-dir> /bin/artemis queue create --name amq.topic --address amq.topic --auto-create-address --anycast
<broker-instance-dir> /bin/artemis stop
Chapter 3. Ruby Examples 3.1. Connecting to the Red Hat Virtualization Manager The Connection class is the entry point of the software development kit. It provides access to the services of the Red Hat Virtualization Manager's REST API. The parameters of the Connection class are: url - Base URL of the Red Hat Virtualization Manager API username password ca_file - PEM file containing the trusted CA certificates. The ca.pem file is required when connecting to a server protected by TLS. If you do not specify the ca_file , the system-wide CA certificate store is used. Connecting to the Red Hat Virtualization Manager connection = OvirtSDK4::Connection.new( url: 'https://engine.example.com/ovirt-engine/api', username: 'admin@internal', password: '...', ca_file: 'ca.pem', ) Important The connection holds critical resources, including a pool of HTTP connections to the server and an authentication token. You must free these resources when they are no longer in use: The connection, and all the services obtained from it, cannot be used after the connection has been closed. If the connection fails, the software development kit will raise an Error exception, containing details of the failure. For more information, see Connection:initialize .

Commands:
connection = OvirtSDK4::Connection.new( url: 'https://engine.example.com/ovirt-engine/api', username: 'admin@internal', password: '...', ca_file: 'ca.pem', )
connection.close
function::print_stack Name function::print_stack - Print out kernel stack from string. Synopsis Arguments stk String with list of hexadecimal addresses. General Syntax print_stack(stk:string) Description This function performs a symbolic lookup of the addresses in the given string, which is assumed to be the result of a prior call to backtrace . Print one line per address, including the address, the name of the function containing the address, and an estimate of its position within that function. Return nothing.

Commands:
function print_stack(stk:string)
20.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: selinuxuser_mysql_connect_enabled When enabled, this Boolean allows users to connect to the local MariaDB server. exim_can_connect_db When enabled, this Boolean allows the exim mailer to initiate connections to a database server. ftpd_connect_db When enabled, this Boolean allows ftp daemons to initiate connections to a database server. httpd_can_network_connect_db Enabling this Boolean is required for a web server to communicate with a database server. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, enter the following command: Enter the following command to view description of a particular Boolean: Note that the additional policycoreutils-devel package providing the sepolicy utility is required for this command to work.

Commands:
~]USD getsebool -a | grep service_name
~]USD sepolicy booleans -b boolean_name
Chapter 16. Hosts A host is a system managed by Ansible Automation Platform, which may include a physical, virtual, cloud-based server, or other device. Typically a host is an operating system instance. Hosts are grouped in inventories and are sometimes referred to as a "nodes". Ansible works against multiple managed nodes or "hosts" in your infrastructure at the same time, using a list or group of lists known as an inventory. Once your inventory is defined, use patterns to select the hosts or groups you want Ansible to run against. 16.1. Creating a host To create a new host. Procedure From the navigation panel, select Automation Execution Infrastructure Hosts . Click Create host . On the Create Host page enter the following information: Name : Enter a name for your host. (Optional) Description : Enter a description for your host. Variables : Enter the inventory file variables associated with your host. Click Create host to save your changes. 16.2. Viewing the host details To view the Host details for a job run. Procedure From the navigation panel, select Automation Execution Infrastructure Hosts . The Hosts page displays the following information about the host or hosts affected by recent job runs. Selecting a particular host displays the Details page for that host, with the following information: The Name of the Host. The Inventory associated with that host. Selecting this inventory displays details of the inventory. When the Host was Created and who by. Selecting the creator displays details of the creator. When the Host was Last modified . Selecting the creator displays details of the creator. Variables associated with the Host. You can display the variables in YAML or JSON format. Click Edit host to edit details of the host. Select the Facts tab to display facts associated with the host. Select the Groups tab to display the Groups associated with the host. Click Associate groups to associate a group with the host. Select the Jobs tab to display the Jobs which ran on the host. Click the icon to display details of the job.

Commands:
Chapter 19. JavaScript Overview JavaScript, also known as ECMAScript is a Java-based scripting language that allows quick parsing of object. The JavaScript support is part of the camel-script module. Adding the script module To use JavaScript in your routes you need to add a dependency on camel-script to your project as shown in Example 19.1, "Adding the camel-script dependency" . Example 19.1. Adding the camel-script dependency Static import To use the javaScript() static method in your application code, include the following import statement in your Java source files: Built-in attributes Table 19.1, "JavaScript attributes" lists the built-in attributes that are accessible when using JavaScript. Table 19.1. JavaScript attributes Attribute Type Value context org.apache.camel.CamelContext The Camel Context exchange org.apache.camel.Exchange The current Exchange request org.apache.camel.Message The IN message response org.apache.camel.Message The OUT message properties org.apache.camel.builder.script.PropertiesFunction Function with a resolve method to make it easier to use the properties component inside scripts. The attributes all set at ENGINE_SCOPE . Example Example 19.2, "Route using JavaScript" shows a route that uses JavaScript. Example 19.2. Route using JavaScript Using the properties component To access a property value from the properties component, invoke the resolve method on the built-in properties attribute, as follows: Where PropKey is the key of the property you want to resolve, where the key value is of String type. For more details about the properties component, see Properties in the Apache Camel Component Reference Guide .

Commands:
<!-- Maven POM File --> <properties> <camel-version>2.23.2.fuse-7_13_0-00013-redhat-00001</camel-version> </properties> <dependencies> <dependency> <groupId>org.apache.camel</groupId> <artifactId>camel-script</artifactId> <version>USD{camel-version}</version> </dependency> </dependencies>
import static org.apache.camel.builder.script.ScriptBuilder.*;
<camelContext> <route> <from uri="direct:start"/> <choice> <when> <langauge langauge="javaScript">request.headers.get('user') == 'admin'</langauge> <to uri="seda:adminQueue"/> </when> <otherwise> <to uri="seda:regularQueue"/> </otherwise> </choice> </route> </camelContext>
.setHeader("myHeader").javaScript("properties.resolve( PropKey )")
Chapter 2. Conversion methods Depending on your requirements, you can convert to RHEL by using one of the following methods: Converting by using the command line - Use this method to convert a small number of servers, or to convert a large number of servers at scale by using custom automation. Note If you have a Satellite subscription but plan to convert by using the command line, you can access the required RHEL packages through Satellite instead of using the Red Hat Content Delivery Network (CDN). For more information about how to convert by using the command line, see Planning a RHEL conversion and Converting using the command-line . Converting by using Red Hat Satellite - Use this method to convert a large number of servers at scale. To convert by using Satellite, you must have a Satellite subscription. For more information about how to convert by using Satellite, see Converting a Host to Red Hat Enterprise Linux . Converting by using Red Hat Insights - Use this method to convert multiple systems in a user-friendly GUI interface without needing a Satellite subscription. Systems must be connected to the internet. Systems are fully onboarded with Red Hat Insights after the conversion. Note Insights supports conversions with Red Hat Enterprise Linux for Third Party Migration with the pay-as-you-go pricing model on Amazon Web Services (AWS). For more information, see Red Hat Enterprise Linux for Third Party Linux Migration . For more information about how to convert by using Red Hat Insights, see Planning a RHEL conversion .

Commands:
Appendix A. Revision History Revision History Revision 1.0-35 Thus May 23 2019 Jiri Herrmann Version for 7.7 Beta publication Revision 1.0-34 Tue Oct 25 2018 Jiri Herrmann Version for 7.6 GA publication Revision 1.0-32 Tue Aug 14 2018 Jiri Herrmann Version for 7.6 Beta publication Revision 1.0-31 Wed Apr 4 2018 Jiri Herrmann Version for 7.5 GA publication Revision 1.0-27 Mon Jul 27 2017 Jiri Herrmann Version for 7.4 GA publication Revision 1.0-24 Mon Oct 17 2016 Jiri Herrmann Version for 7.3 GA publication Revision 1.0-22 Mon Dec 21 2015 Laura Novich Republished Guide to fix several bugs Revision 1.0-19 Thu Oct 08 2015 Jiri Herrmann Cleaned up Revision History

Commands:
probe::vm.kmalloc Name probe::vm.kmalloc - Fires when kmalloc is requested. Synopsis Values ptr Pointer to the kmemory allocated caller_function Name of the caller function. call_site Address of the kmemory function. gfp_flag_name type of kmemory to allocate (in String format) name Name of the probe point bytes_req Requested Bytes bytes_alloc Allocated Bytes gfp_flags type of kmemory to allocate

Commands:
vm.kmalloc
20.3.4.4. Configuring ssh-agent with GNOME The ssh-agent utility can be used to save your passphrase so that you do not have to enter it each time you initiate an ssh or scp connection. If you are using GNOME, the openssh-askpass-gnome package contains the application used to prompt you for your passphrase when you log in to GNOME and save it until you log out of GNOME. You will not have to enter your password or passphrase for any ssh or scp connection made during that GNOME session. If you are not using GNOME, refer to Section 20.3.4.5, "Configuring ssh-agent " . To save your passphrase during your GNOME session, follow the following steps: You will need to have the package openssh-askpass-gnome installed; you can use the command rpm -q openssh-askpass-gnome to determine if it is installed or not. If it is not installed, install it from your Red Hat Enterprise Linux CD-ROM set, from a Red Hat FTP mirror site, or using Red Hat Network. Select Main Menu Button (on the Panel) => Preferences => More Preferences => Sessions , and click on the Startup Programs tab. Click Add and enter /usr/bin/ssh-add in the Startup Command text area. Set it a priority to a number higher than any existing commands to ensure that it is executed last. A good priority number for ssh-add is 70 or higher. The higher the priority number, the lower the priority. If you have other programs listed, this one should have the lowest priority. Click Close to exit the program. Log out and then log back into GNOME; in other words, restart X. After GNOME is started, a dialog box will appear prompting you for your passphrase(s). Enter the passphrase requested. If you have both DSA and RSA key pairs configured, you will be prompted for both. From this point on, you should not be prompted for a password by ssh , scp , or sftp .

Commands: