mtpti5iD/redhat-docs_dataset huggingface dataset:
20.26. Sending a Keystroke Combination to a Specified Guest Virtual machine The virsh send-key domain --codeset --holdtime keycode command allows you to send a sequence as a keycode to a specific guest virtual machine. Each keycode can either be a numeric value or a symbolic name from the corresponding codeset below. If a --holdtime is given, each keystroke will be held for the specified amount in milliseconds. The --codeset allows you to specify a code set, the default being Linux , but the following options are permitted: linux - choosing this option causes the symbolic names to match the corresponding Linux key constant macro names and the numeric values are those offered by the Linux generic input event subsystems. xt - this will send a value that is defined by the XT keyboard controller. No symbolic names are provided atset1 - the numeric values are those that are defined by the AT keyboard controller, set1 (XT compatible set). Extended keycodes from the atset1 may differ from extended keycodes in the XT codeset. No symbolic names are provided. atset2 - The numeric values are those defined by the AT keyboard controller, set 2. No symbolic names are provided. atset3 - The numeric values are those defined by the AT keyboard controller, set 3 (PS/2 compatible). No symbolic names are provided. os_x - The numeric values are those defined by the OS-X keyboard input subsystem. The symbolic names match the corresponding OS-X key constant macro names. xt_kbd - The numeric values are those defined by the Linux KBD device. These are a variant on the original XT codeset, but often with different encoding for extended keycodes. No symbolic names are provided. win32 - The numeric values are those defined by the Win32 keyboard input subsystem. The symbolic names match the corresponding Win32 key constant macro names. usb - The numeric values are those defined by the USB HID specification for keyboard input. No symbolic names are provided. rfb - The numeric values are those defined by the RFB extension for sending raw keycodes. These are a variant on the XT codeset, but extended keycodes have the low bit of the second bite set, instead of the high bit of the first byte. No symbolic names are provided. Example 20.53. How to send a keystroke combination to a guest virtual machine The following example sends the Left Ctrl , Left Alt , and Delete in the Linux encoding to the guest1 virtual machine, and holds them for 1 second. These keys are all sent simultaneously, and may be received by the guest in a random order: # virsh send-key guest1 --codeset Linux --holdtime 1000 KEY_LEFTCTRL KEY_LEFTALT KEY_DELETE Note If multiple keycodes are specified, they are all sent simultaneously to the guest virtual machine and as such may be received in random order. If you need distinct keycodes, you must run the virsh send-key command multiple times in the order you want the sequences to be sent.

Commands:
6.3. Starting ricci In order to create and distribute cluster configuration files on the nodes of the cluster, the ricci service must be running on each node. Before starting ricci , you should ensure that you have configured your system as follows: The IP ports on your cluster nodes should be enabled for ricci . For information on enabling IP ports on cluster nodes, see Section 3.3.1, "Enabling IP Ports on Cluster Nodes" . The ricci service is installed on all nodes in the cluster and assigned a ricci password, as described in Section 3.13, "Considerations for ricci " . After ricci has been installed and configured on each node, start the ricci service on each node:

Commands:
service ricci start Starting ricci: [ OK ]
28.4. Changing Domain DNS Configuration 28.4.1. Setting DNS Entries for Multi-Homed Servers Some server machines may support multiple network interface cards (NICs). Multi-homed machines typically have multiple IPs, all assigned to the same hostname. This works fine in IdM most of the time because it listens on all available interfaces, except localhost. For a server to be available through any NIC, edit the DNS zone file and add entries for each IP address. For example: 28.4.2. Setting up Additional Name Servers The list of configured nameservers in /etc/resolv.conf only contains the IdM server itself when configuration is finished. If the local named service ever crashes, then the IdM server is unable to run and DNS services for the entire domain are no longer available. Other DNS servers should be added manually to the IdM server's /etc/resolv.conf file. Note A default limit of three servers is set for the /etc/resolv.conf file. Other information about configuring the /etc/resolv.conf file is given in the resolv.conf manpage. 28.4.3. Changing Load Balancing for IdM Servers and Replicas As Section 1.3.1, "About IdM Servers and Replicas" touches on, IdM servers and replicas in the domain automatically share the load among instances to maintain performance. The load balancing is defined first by the priority set for the server or replica in its SRV entry, and then by the weight of that instance for servers/replicas with the same priority. Clients contact servers/replicas with the highest priority and then work their way down. Load balancing is done automatically by servers, replicas, and clients. The configuration used for load balancing can be altered by changing the priority and the weight given to a server or replica. (All replicas are initially created with the same priority.) For example, this gives server1 a higher priority than server 2, meaning it will be contacted first: More information about SRV records is in RFC 2782 .

Commands:
ipaserver IN A 192.168.1.100 ipaserver IN A 192.168.1.101 ipaserver IN A 192.168.1.102
vim /etc/resolv.conf search example.com ; the IdM server nameserver 127.0.0.1 ; backup DNS servers nameserver 198.51.100.0 nameserver 192.0.2.0
ipa dnsrecord-add server.example.com _ldap._tcp --srv-rec="0 100 389 server1.example.com." ipa dnsrecord-add server.example.com _ldap._tcp --srv-rec="1 100 389 server2.example.com."
Chapter 17. Connecting to the installation system After the Initial Program Load (IPL) of the Anaconda installation program is complete, connect to the IBM Z system from a local machine, as an 'install' user, using an ssh connection. You need to connect to the installation system to continue the installation process. Use a VNC mode to run a GUI-based installation or use the established connection to run a text mode installation. Additional resources: For more information about installing VNC and various VNC modes for GUI-based installation, see Chapter 25, Using VNC 17.1. Setting up remote connection using VNC From a local machine, run the steps below to set up a remote connection with the IBM Z system. Prequisite: The initial program boot is complete on the IBM Z system, and the command prompt displays: If you want to restrict VNC access to the installation system, then ensure inst.vncpassword= PASSWORD boot parameter is configured. On the command prompt, run the following command: OR Depending on whether or not have you configured the inst.vnc parameter, the ssh session displays the following output: When inst.vnc parameter is configured: When inst.vnc parameter is not configured: If you have configured the inst.vnc parameter, proceed to step 5. Enter 1 to start VNC. Enter a password, if you have not set the inst.vncpassword= boot option, but want to secure the server connection. From a new command prompt, connect to the VNC server. If you have secured the connection, use the password that you have entered in the step or the one that you had set for inst.vncpassword= boot option. The RHEL installer is launched in the VNC client.

Commands:
Starting installer, one moment Please ssh install@ my-z-system ( system ip address ) to begin the install.
ssh install@ my-z-system-domain-name
ssh install@ my-z-system-IP-address
Starting installer, one moment Please manually connect your vnc client to my-z-system:1 (system-ip-address:1) to begin the install.
Starting installer, one moment Graphical installation is not available. Starting text mode. ============= Text mode provides a limited set of installation options. It does not offer custom partitioning for full control over the disk layout. Would you like to use VNC mode instead? 1) Start VNC 2) Use text mode Please make your choice from above ['q' to quit | 'c' to continue | 'r' to refresh]:
vncviewer my-z-system-ip-address:display_number
probe::vm.kmem_cache_alloc_node Name probe::vm.kmem_cache_alloc_node - Fires when kmem_cache_alloc_node is requested Synopsis vm.kmem_cache_alloc_node Values gfp_flags type of kmemory to allocate name name of the probe point bytes_req requested Bytes ptr pointer to the kmemory allocated bytes_alloc allocated Bytes caller_function name of the caller function call_site address of the function calling this kmemory function gfp_flag_name type of kmemory to allocate(in string format)

Commands:
9.10. Testing Publishing to Files To verify that the Certificate Manager is publishing certificates and CRLs correctly to file: Open the CA's end-entities page, and request a certificate. Approve the request through the agent services page, if required. Retrieve the certificate from the end-entities page, and download the certificate into the browser. Check whether the server generated the DER-encoded file containing the certificate. Open the directory to which the binary blob of the certificate is supposed to be published. The certificate file should be named cert- serial_number .der . Convert the DER-encoded certificate to its base 64-encoded format using the Binary to ASCII tool. For more information on this tool, refer to the BtoA(1) man page. input_file sets the path to the file that contains the DER-encoded certificate, and output_file sets the path to the file to write the base-64 encoded certificate. Open the ASCII file; the base-64 encoded certificate is similar to the one shown: Convert the base 64-encoded certificate to a readable form using the Pretty Print Certificate tool. For more information on this tool, refer to the PrettyPrintCert(1) man page. input_file sets the path to the ASCII file that contains the base-64 encoded certificate, and output_file , optionally, sets the path to the file to write the certificate. If an output file is not set, the certificate information is written to the standard output. Compare the output with the certificate issued; check the serial number in the certificate with the one used in the filename. If everything matches, the Certificate Manager is configured correctly to publish certificates to file. Revoke the certificate. Check whether the server generated the DER-encoded file containing the CRL. Open the directory to which the server is to publish the CRL as a binary blob. The CRL file should have a name in the form crl- this_update .der . this_update specifies the value derived from the time-dependent This Update variable of the CRL. Convert the DER-encoded CRL to its base 64-encoded format using the Binary to ASCII tool. Convert the base 64-encoded CRL to readable form using the Pretty Print CRL tool. Compare the output.

Commands:
BtoA input_file output_file
-----BEGIN CERTIFICATE----- MMIIBtgYJYIZIAYb4QgIFoIIBpzCCAZ8wggGbMIIBRaADAgEAAgEBMA0GCSqGSIb3DQEBBAUAMFcxC AJBgNVBAYTAlVTMSwwKgYDVQQKEyNOZXRzY2FwZSBDb21tdW5pY2F0aWhfyyuougjgjjgmkgjkgmjg fjfgjjjgfyjfyj9ucyBDb3Jwb3JhdGlvbjpMEaMBgGA1UECxMRSXNzdWluZyhgdfhbfdpffjphotoo gdhkBBdXRob3JpdHkwHhcNOTYxMTA4MDkwNzM0WhcNOTgxMTA4MDkwNzMM0WjBXMQswCQYDVQQGEwJ VUzEsMCoGA1UEChMjTmV0c2NhcGUgQ29tbXVuaWNhdGlvbnMgQ29ycG9yY2F0aW9ucyBDb3Jwb3Jhd GlvbjpMEaMBgGA1UECxMRSXNzdWluZyBBdXRob3JpdHkwHh -----END CERTIFICATE-----
PrettyPrintCert input_file [output_file]
BtoA input_file output_file
PrettyPrintCrl input_file [output_file]
7.309. abrt 7.309.1. RHBA-2013:1289 - abrt bug fix update Updated abrt packages that fix two bugs are now available for Red Hat Enterprise Linux 6. ABRT (Automatic Bug Reporting Tool) is a tool to help users detect defects in applications create bug reports with all the information needed by a maintainer to fix it. It uses a plug-in system to extend its functionality. libreport provides an API for reporting different problems in applications to different bug targets, such as Bugzilla, FTP, and Trac. Bug Fixes BZ# 968345 Previously, attempts to create a Python virtualenv environment using the "--system-site-packages" option resulted in an exception when the site.py() function attempted to load the abrt_exception_handler package. This was caused because Python tried to load the abrt.pth file, in which the abrt_exception_handler module was imported. Since the abrt_exception_handler module was installed under the /usr/lib64 directory and the abrt.pth file was installed under the /usr/lib directory, the site.py() function did not find the required module. This update moves the abrt.pth file to the architecture specific folder, so on 32-bit systems to the /usr/lib/python2.7/site-packages/ directory and on 64-bit systems to the /usr/lib64/python2.7/site-packages/ directory, which corrects this issue. BZ# 1002856 Prior to this update, attempts to use ABRT to report bugs in a Bugzilla server returned the following Remote Procedure Call (RPC) error message: "fatal: RPC failed at server. The requested method 'bugzilla.getBug' was not found." Consequently, Bugzilla tickets were not created, and bugs were not reported. This update changes the code to use the new XMLRPC calls, and with the latest version of ABRT, Bugzilla tickets are created without any problems. Users of abrt are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 6. Attaching your Red Hat Ansible Automation Platform subscription You must have valid subscriptions attached on all nodes before installing Red Hat Ansible Automation Platform. Attaching your Ansible Automation Platform subscription provides access to subscription-only resources necessary to proceed with the installation. Note Attaching a subscription is unnecessary if you have enabled Simple Content Access Mode on your Red Hat account. Once enabled, you will need to register your systems to either Red Hat Subscription Management (RHSM) or Satellite before installing the Ansible Automation Platform. For more information, see Simple Content Access . Procedure Obtain the pool_id for your Red Hat Ansible Automation Platform subscription: # subscription-manager list --available --all | grep "Ansible Automation Platform" -B 3 -A 6 Note Do not use MCT4022 as a pool_id for your subscription because it can cause Ansible Automation Platform subscription attachment to fail. Example An example output of the subsciption-manager list command. Obtain the pool_id as seen in the Pool ID: section: Subscription Name: Red Hat Ansible Automation, Premium (5000 Managed Nodes) Provides: Red Hat Ansible Engine Red Hat Ansible Automation Platform SKU: MCT3695 Contract: ```` Pool ID: <pool_id> Provides Management: No Available: 4999 Suggested: 1 Attach the subscription: # subscription-manager attach --pool=<pool_id> You have now attached your Red Hat Ansible Automation Platform subscriptions to all nodes. Verification Verify the subscription was successfully attached: # subscription-manager list --consumed Troubleshooting If you are unable to locate certain packages that came bundled with the Ansible Automation Platform installer, or if you are seeing a Repositories disabled by configuration message, try enabling the repository by using the command: Red Hat Ansible Automation Platform 2.4 for RHEL 8 subscription-manager repos --enable ansible-automation-platform-2.4-for-rhel-8-x86_64-rpms Red Hat Ansible Automation Platform 2.4 for RHEL 9 subscription-manager repos --enable ansible-automation-platform-2.4-for-rhel-9-x86_64-rpms

Commands:
subscription-manager list --available --all | grep "Ansible Automation Platform" -B 3 -A 6
Subscription Name: Red Hat Ansible Automation, Premium (5000 Managed Nodes) Provides: Red Hat Ansible Engine Red Hat Ansible Automation Platform SKU: MCT3695 Contract: ```` Pool ID: <pool_id> Provides Management: No Available: 4999 Suggested: 1
subscription-manager attach --pool=<pool_id>
subscription-manager list --consumed
subscription-manager repos --enable ansible-automation-platform-2.4-for-rhel-8-x86_64-rpms
subscription-manager repos --enable ansible-automation-platform-2.4-for-rhel-9-x86_64-rpms
10.6. VLAN on Bond and Bridge Using ip Commands To use VLANs over bonds and bridges, proceed as follows: Add a bond device as root : Set VLAN on the bond device: Add the bridge device and attach VLAN to it:

Commands:
ip link add bond0 type bond ip link set bond0 type bond miimon 100 mode active-backup ip link set em1 down ip link set em1 master bond0 ip link set em2 down ip link set em2 master bond0 ip link set bond0 up
ip link add link bond0 name bond0.2 type vlan id 2 ip link set bond0.2 up
ip link add br0 type bridge ip link set bond0.2 master br0 ip link set br0 up
7.9. RHEA-2014:1530 - new packages: json-c New json-c packages are now available for Red Hat Enterprise Linux 6. JSON-C implements a reference counting object model that allows users to easily construct JavaScript Object Notation (JSON) objects in C, output them as JSON formatted strings and parse JSON formatted strings back into the C representation of JSON objects. This enhancement update adds the json-c packages to Red Hat Enterprise Linux 6. (BZ# 966964 ) All users who require json-c are advised to install these new packages.

Commands:
Chapter 1. Red Hat JBoss Web Server 6.0 Service Pack 1 Welcome to the Red Hat JBoss Web Server version 6.0 Service Pack 1 release. Red Hat JBoss Web Server is a fully integrated and certified set of components for hosting Java web applications. It consists of an application server (Apache Tomcat servlet container) and the Apache Tomcat Native Library. JBoss Web Server includes the following key components: Apache Tomcat is a servlet container in accordance with the Java Servlet Specification. JBoss Web Server contains Apache Tomcat 10.1. The Apache Tomcat Native Library improves Tomcat scalability, performance, and integration with native server technologies. Tomcat-vault is an extension for the JBoss Web Server that is used for securely storing passwords and other sensitive information used by a JBoss Web Server. The mod_cluster library enables communication between JBoss Web Server and the Apache HTTP Server mod_proxy_cluster module. The mod_cluster library enables you to use the Apache HTTP Server as a load balancer for JBoss Web Server. For more information about configuring mod_cluster , or for information about installing and configuring alternative load balancers such as mod_jk and mod_proxy , see the Apache HTTP Server Connectors and Load Balancing Guide . Apache portable runtime (APR) is a runtime that provides an OpenSSL-based TLS implementation for the HTTP connectors. JBoss Web Server provides a distribution of APR for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the APR package that the operating system provides. OpenSSL is a software library that implements the Secure Sockets Layer (SSL) and Transport Layer Security (TLS) protocols and includes a basic cryptographic library. JBoss Web Server provides a distribution of OpenSSL for supported Windows platforms only. For Red Hat Enterprise Linux, you can use the OpenSSL package that the operating system provides. This release of JBoss Web Server includes some important security updates. This release of JBoss Web Server provides OpenShift images based on Red Hat Enterprise Linux 8.

Commands:
Chapter 5. Reviewing and resolving migration issues You can review and resolve migration issues identified by the MTA extension in the left pane. 5.1. Reviewing issues You can use the MTA extension icons to prioritize issues based on their severity. Procedure Select a run configuration directory on the left pane. Expand its folders to view the Hints generated for each application file. Select a hint to view the source code. Right-click a hint and select View Details to view the Rule ID and other information. Prioritize issues based on the following icons, which are displayed to each hint: : The issue must be fixed for a successful migration. : The issue might need to be addressed during migration. 5.2. Resolving issues You can resolve issues by editing the code of a file with a hint 5.2.1. Editing the code of a file You can edit the file of a project imported to VS Code. Procedure In the left pane, right-click an issue and select Open Code . Make any changes needed to the code and save the file. Optional: Right-click the issue and select Mark as Complete or Delete .

Commands:
3.11. Virtual LAN (VLAN) A VLAN (Virtual LAN) is an attribute that can be applied to network packets. Network packets can be "tagged" into a numbered VLAN. A VLAN is a security feature used to isolate network traffic at the switch level. VLANs are separate and mutually exclusive. The Red Hat Virtualization Manager is VLAN-aware and able to tag and redirect VLAN traffic, however VLAN implementation requires a switch that supports VLANs. At the switch level, ports are assigned a VLAN designation. A switch applies a VLAN tag to traffic originating from a particular port, marking the traffic as part of a VLAN, and ensures that responses carry the same VLAN tag. A VLAN can extend across multiple switches. VLAN tagged network traffic on a switch is undetectable except by machines connected to a port designated with the correct VLAN. A given port can be tagged into multiple VLANs, which allows traffic from multiple VLANs to be sent to a single port, to be deciphered using software on the machine that receives the traffic.

Commands:
Appendix C. Revision History Revision History Revision 4.1-1 Wed Aug 7 2019 Steven Levine Preparing document for 7.7 GA publication. Revision 3.1-1 Thu Oct 4 2018 Steven Levine Preparing document for 7.6 GA publication. Revision 2.1-1 Thu Mar 15 2018 Steven Levine Preparing document for 7.5 GA publication. Revision 2.1-0 Thu Dec 14 2017 Steven Levine Preparing document for 7.5 Beta publication. Revision 1.3-6 Wed Nov 8 2017 Steven Levine Updated version for 7.4. Revision 1.3-3 Thu Jul 27 2017 Steven Levine Document version for 7.4 GA publication. Revision 1.3-1 Wed May 10 2017 Steven Levine Preparing document for 7.4 Beta publication. Revision 1.2-5 Thu Mar 23 2017 Steven Levine Update to 7.3 GA publication. Revision 1.2-4 Mon Oct 17 2016 Steven Levine Version for 7.3 GA publication. Revision 1.2-3 Wed Aug 17 2016 Steven Levine Preparing document for 7.3 Beta publication. Revision 0.3-5 Mon Nov 9 2015 steven levine Preparing document for 7.2 GA publication Revision 0.3-2 Wed Aug 19 2015 Steven Levine Preparing document for 7.2 Beta publication. Revision 0.2-13 Wed Feb 18 2015 Steven Levine Version for 7.1 GA release Revision 0.2-8 Thu Dec 11 2014 Steven Levine Version for 7.0 Beta release Revision 0.1-29 Wed Jun 11 2014 Steven Levine Version for 7.0 GA release Revision 0.1-11 Mon Dec 9 2013 Steven Levine 7.0 Beta release Revision 0.1-1 Wed Jan 16 2013 Steven Levine Branched from the Red Hat Enterprise Linux 6 version of the document

Commands:
Preface Red Hat Enterprise Linux minor releases are an aggregation of individual security, enhancement, and bug fix errata. The Red Hat Enterprise Linux 7.3 Release Notes document describes the major changes made to the Red Hat Enterprise Linux 7 operating system and its accompanying applications for this minor release, as well as known problems and a complete list of all currently available Technology Previews. Capabilities and limits of Red Hat Enterprise Linux 7 as compared to other versions of the system are available in the Red Hat Knowledgebase article available at https://access.redhat.com/articles/rhel-limits . For information regarding the Red Hat Enterprise Linux life cycle, refer to https://access.redhat.com/support/policy/updates/errata/ .

Commands: