mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 1. Authenticating with the Guest user To explore Developer Hub features, you can skip configuring authentication and authorization. You can configure Developer Hub to log in as a Guest user and access Developer Hub features. 1.1. Authenticating with the Guest user on an Operator-based installation After an Operator-based installation, you can configure Developer Hub to log in as a Guest user and access Developer Hub features. Prerequisites You installed Developer Hub by using the Operator . You added a custom Developer Hub application configuration , and have sufficient permissions to modify it. Procedure To enable the guest user in your Developer Hub custom configuration, edit your Developer Hub application configuration with following content: app-config.yaml fragment auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true Verification Go to the Developer Hub login page. To log in with the Guest user account, click Enter in the Guest tile. In the Developer Hub Settings page, your profile name is Guest . You can use Developer Hub features. 1.2. Authenticating with the Guest user on a Helm-based installation On a Helm-based installation, you can configure Developer Hub to log in as a Guest user and access Developer Hub features. Prerequisites You added a custom Developer Hub application configuration , and have sufficient permissions to modify it. You use the Red Hat Developer Hub Helm chart to run Developer Hub . Procedure To enable the guest user in your Developer Hub custom configuration, configure your Red Hat Developer Hub Helm Chart with following content: Red Hat Developer Hub Helm Chart configuration fragment upstream: backstage: appConfig: app: baseUrl: 'https://{{- include "janus-idp.hostname" . }}' auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true Verification Go to the Developer Hub login page. To log in with the Guest user account, click Enter in the Guest tile. In the Developer Hub Settings page, your profile name is Guest . You can use Developer Hub features.

Commands:
auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true
upstream: backstage: appConfig: app: baseUrl: 'https://{{- include "janus-idp.hostname" . }}' auth: environment: development providers: guest: dangerouslyAllowOutsideDevelopment: true
14.19. Setting Schedule Parameters schedinfo allows scheduler parameters to be passed to guest virtual machines. The following command format should be used: Each parameter is explained below: domain - this is the guest virtual machine domain --set - the string placed here is the controller or action that is to be called. Additional parameters or values if required should be added as well. --current - when used with --set , will use the specified set string as the current scheduler information. When used without will display the current scheduler information. --config - - when used with --set , will use the specified set string on the reboot. When used without will display the scheduler information that is saved in the configuration file. --live - when used with --set , will use the specified set string on a guest virtual machine that is currently running. When used without will display the configuration setting currently used by the running virtual machine The scheduler can be set with any of the following parameters: cpu_shares , vcpu_period and vcpu_quota . Example 14.5. schedinfo show This example shows the shell guest virtual machine's schedule information Example 14.6. schedinfo set In this example, the cpu_shares is changed to 2046. This effects the current state and not the configuration file.

Commands:
virsh schedinfo domain --set --weight --cap --current --config --live
virsh schedinfo shell Scheduler : posix cpu_shares : 1024 vcpu_period : 100000 vcpu_quota : -1
virsh schedinfo --set cpu_shares=2046 shell Scheduler : posix cpu_shares : 2046 vcpu_period : 100000 vcpu_quota : -1
4.3. Eviction and Expiration Comparison Expiration is a top-level construct in Red Hat JBoss Data Grid, and is represented in the global configuration, as well as the cache API . Eviction is limited to the cache instance it is used in, whilst expiration is cluster-wide. Expiration life spans ( lifespan ) and idle time ( maxIdle in Library Mode and max-idle in Remote Client-Server Mode) values are replicated alongside each cache entry. Report a bug

Commands:
10.5. Configuration Directives in httpd.conf The Apache HTTP Server configuration file is /etc/httpd/conf/httpd.conf . The httpd.conf file is well-commented and mostly self-explanatory. The default configuration works for most situations; however, it is a good idea to become familiar some of the more important configuration options. Warning With the release of Apache HTTP Server 2.0, many configuration options have changed. If migrating a version 1.3 configuration file to the 2.0 format, refer to Section 10.2, "Migrating Apache HTTP Server 1.3 Configuration Files" . 10.5.1. General Configuration Tips If configuring the Apache HTTP Server, edit /etc/httpd/conf/httpd.conf and then either reload, restart, or stop and start the httpd process as outlined in Section 10.4, "Starting and Stopping httpd " . Before editing httpd.conf , make a copy the original file. Creating a backup makes it easier to recover from mistakes made while editing the configuration file. If a mistake is made and the Web server does not work correctly, first review recently edited passages in httpd.conf to verify there are no typos. look in the Web server's error log, /var/log/httpd/error_log . The error log may not be easy to interpret, depending on your level of expertise. However, the last entries in the error log should provide useful information. The following subsections contain a list of short descriptions for many of the directives included in httpd.conf . These descriptions are not exhaustive. For more information, refer to the Apache documentation online at http://httpd.apache.org/docs-2.0/ . For more information about mod_ssl directives, refer to the documentation online at http://httpd.apache.org/docs-2.0/mod/mod_ssl.html .

Commands:
Chapter 22. Setting the due date and priority of a task You can set the priority, due date, and time of a task in Business Central from the Task Inbox page. Note that all users may not have permissions for setting priority and the due date of a task. Procedure In Business Central, go to Menu Track Task Inbox . On the Task Inbox page, click the task to open it. On the task page, click the Details tab. In the Due Date field, select the required date from the calendar and the due time from the drop-down list. In the Priority field, select the required priority. Click Update .

Commands:
Chapter 3. Red Hat certification self check (rhcert/selfcheck) The Red Hat Certification self check test also known as rhcert/selfcheck confirms that all the software packages required in the certification process are installed and that they have not been altered. This ensures that the test environment is ready for the certification process and that all the certification software packages are supportable. Success criteria The test environment includes the required certification packages process and their dependencies. The required certification packages have not been modified.

Commands:
33.3. Emergency Mode Emergency mode , provides the minimal bootable environment and allows you to repair your system even in situations when rescue mode is unavailable. In emergency mode , the system mounts only the root file system, and it is mounted as read-only. Also, the system does not activate any network interfaces and only a minimum of the essential services are set up. The system does not load any init scripts, therefore you can still mount file systems to recover data that would be lost during a re-installation if init is corrupted or not working. To boot into emergency mode follow this procedure: Procedure 33.3. Booting into Emergency Mode At the GRUB boot screen, press any key to enter the GRUB interactive menu. Select Red Hat Enterprise Linux with the version of the kernel that you want to boot and press the a to append the line. Type emergency as a separate word at the end of the line and press Enter to exit GRUB edit mode.

Commands:
A.2. UI Connection Problems If negotiate authentication is not working, turn on verbose logging for the authentication process to help diagnose the issue: Close all browser windows. In a terminal, set the new log levels for Firefox: This enables verbose logging and logs all information to /tmp/moz.log . Restart the browser from the same terminal window. Some of the common error messages and workarounds are in Table A.1, "UI Error Log Messages" . Table A.1. UI Error Log Messages Error Log Message Description and Fix There are no Kerberos tickets. Run kinit . This can occur when you have successfully obtained Kerberos tickets but are still unable to authenticate to the UI. This indicates that there is a problem with the Kerberos configuration. The first place to check is the [domain_realm] section in the /etc/krb5.conf file. Make sure that the IdM Kerberos domain entry is correct and matches the configuration in the Firefox negotiation parameters. For example: Nothing is in the log file. It is possible that you are behind a proxy which is removing the HTTP headers required for negotiate authentication. Try to connect to the server using HTTPS instead, which allows the request to pass through unmodified. Then check the log file again.

Commands:
export NSPR_LOG_MODULES=negotiateauth:5 export NSPR_LOG_FILE=/tmp/moz.log
-1208550944[90039d0]: entering nsNegotiateAuth::GetNextToken() -1208550944[90039d0]: gss_init_sec_context() failed: Miscellaneous failure No credentials cache found
-1208994096[8d683d8]: entering nsAuthGSSAPI::GetNextToken() -1208994096[8d683d8]: gss_init_sec_context() failed: Miscellaneous failure Server not found in Kerberos database
.example.com = EXAMPLE.COM example.com = EXAMPLE.COM
11.5. The REST Interface Connector The REST connector differs from the Hot Rod and Memcached connectors because it requires a web subsystem. Therefore configurations such as socket-binding, worker threads, timeouts, etc, must be performed on the web subsystem. The following enables a REST server. The following enables a REST server: See Section 11.6, "Using the REST Interface" for more information. Report a bug 11.5.1. Configure REST Connectors Use the following procedure to configure the rest-connector element in Red Hat JBoss Data Grid's Remote Client-Server mode. Procedure 11.1. Configuring REST Connectors for Remote Client-Server Mode The rest-connector element specifies the configuration information for the REST connector. The virtual-server parameter specifies the virtual server used by the REST connector. The default value for this parameter is default-host . This is an optional parameter. The cache-container parameter names the cache container used by the REST connector. This is a mandatory parameter. The context-path parameter specifies the context path for the REST connector. The default value for this parameter is an empty string ( "" ). This is an optional parameter. The security-domain parameter specifies that the specified domain, declared in the security subsystem, should be used to authenticate access to the REST endpoint. This is an optional parameter. If this parameter is omitted, no authentication is performed. The auth-method parameter specifies the method used to retrieve credentials for the end point. The default value for this parameter is BASIC . Supported alternate values include BASIC , DIGEST , and CLIENT-CERT . This is an optional parameter. The security-mode parameter specifies whether authentication is required only for write operations (such as PUT, POST and DELETE) or for read operations (such as GET and HEAD) as well. Valid values for this parameter are WRITE for authenticating write operations only, or READ_WRITE to authenticate read and write operations. The default value for this parameter is READ_WRITE . Report a bug

Commands:
<rest-connector virtual-server="default-host" cache-container="local" security-domain="other" auth-method="BASIC"/>
<subsystem xmlns="urn:infinispan:server:endpoint:6.1"> <rest-connector virtual-server="default-host" cache-container="local" context-path="USD{CONTEXT_PATH}" security-domain="USD{SECURITY_DOMAIN}" auth-method="USD{METHOD}" security-mode="USD{MODE}" /> </subsystem>
8.214. system-config-keyboard 8.214.1. RHBA-2013:0940 - system-config-keyboard bug fix update Updated system-config-keyboard packages that fix one bug are now available for Red Hat Enterprise Linux 6. The system-config-keyboard packages provide a graphical user interface that allows the user to change the default keyboard of the system. Bug Fix BZ# 952125 The system-config-keyboard packages contain a plug-in for firstboot. versions of system-config-keyboard depended on firstboot, so it was not possible to install the packages without pulling in firstboot too. This erroneous dependency has been removed and the system-config-keyboard packages can now be installed without pulling in firstboot. Users of system-config-keyboard are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 2. Installing Red Hat Enterprise Linux Virtual Machines Installing a Red Hat Enterprise Linux virtual machine involves the following key steps: Create a virtual machine. You must add a virtual disk for storage, and a network interface to connect the virtual machine to the network. Start the virtual machine and install an operating system. See your operating system's documentation for instructions. Red Hat Enterprise Linux 6: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/Installation_Guide/index.html Red Hat Enterprise Linux 7: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/Installation_Guide/index.html Red Hat Enterprise Linux Atomic Host 7: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_atomic_host/7/html/installation_and_configuration_guide Red Hat Enterprise Linux 8: https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/performing_a_standard_rhel_installation/index Enable the required repositories for your operating system. Install guest agents and drivers for additional virtual machine functionality. 2.1. Creating a Virtual Machine Create a new virtual machine and configure the required settings. Procedure Click Compute Virtual Machines . Click New to open the New Virtual Machine window. Select an Operating System from the drop-down list. Enter a Name for the virtual machine. Add storage to the virtual machine. Attach or Create a virtual disk under Instance Images . Click Attach and select an existing virtual disk. Click Create and enter a Size(GB) and Alias for a new virtual disk. You can accept the default settings for all other fields, or change them if required. See Section A.4, "Explanation of Settings in the New Virtual Disk and Edit Virtual Disk Windows" for more details on the fields for all disk types. Connect the virtual machine to the network. Add a network interface by selecting a vNIC profile from the nic1 drop-down list at the bottom of the General tab. Specify the virtual machine's Memory Size on the System tab. Choose the First Device that the virtual machine will boot from on the Boot Options tab. You can accept the default settings for all other fields, or change them if required. For more details on all fields in the New Virtual Machine window, see Section A.1, "Explanation of Settings in the New Virtual Machine and Edit Virtual Machine Windows" . Click OK . The new virtual machine is created and displays in the list of virtual machines with a status of Down . Before you can use this virtual machine, you must install an operating system and register with the Content Delivery Network.

Commands:
Assessing and Reporting Malware Signatures on RHEL Systems Red Hat Insights 1-latest Know when systems in your RHEL infrastructure are exposed to malware risks Red Hat Customer Content Services

Commands:
sudo dnf install yara
sudo yum install insights-client
sudo insights-client --test-connection
sudo insights-client --register
sudo insights-client --collector malware-detection
test_scan: false
sudo insights-client --collector malware-detection
scan_processes: true
sudo insights-client --collector malware-detection
FILESYSTEM_SCAN_ONLY=/etc,/tmp,/var/lib
sudo FILESYSTEM_SCAN_ONLY=/etc,/tmp,/var/lib TEST_SCAN=false insights-client --collector malware-detection
5.4. Virtual Memory 5.4.1. Hot Plugging Virtual Memory You can hot plug virtual memory. Hot plugging means enabling or disabling devices while a virtual machine is running. Each time memory is hot plugged, it appears as a new memory device in the Vm Devices tab in the details view of the virtual machine, up to a maximum of 16 available slots. When the virtual machine is restarted, these devices are cleared from the Vm Devices tab without reducing the virtual machine's memory, allowing you to hot plug more memory devices. If the hot plug fails (for example, if there are no more available slots), the memory increase will be applied when the virtual machine is restarted. Important This feature is currently not supported for the self-hosted engine Manager virtual machine. Hot Plugging Virtual Memory Click Compute Virtual Machines and select a running virtual machine. Click Edit . Click the System tab. Increase the Memory Size by entering the total amount required. Memory can be added in multiples of 256 MB. By default, the maximum memory allowed for the virtual machine is set to 4x the memory size specified. Though the value is changed in the user interface, the maximum value is not hot plugged, and you will see the pending changes icon ( ). To avoid that, you can change the maximum memory back to the original value. Click OK . This action opens the Pending Virtual Machine changes window, as some values such as maxMemorySizeMb and minAllocatedMem will not change until the virtual machine is restarted. However, the hot plug action is triggered by the change to the Memory Size value, which can be applied immediately. Click OK . The virtual machine's Defined Memory is updated in the General tab in the details view. You can see the newly added memory device in the Vm Devices tab in the details view. 5.4.2. Hot Unplugging Virtual Memory You can hot unplug virtual memory. Hot unplugging means disabling devices while a virtual machine is running. Important Only memory added with hot plugging can be hot unplugged. The virtual machine operating system must support memory hot unplugging. The virtual machines must not have a memory balloon device enabled. This feature is disabled by default. All blocks of the hot-plugged memory must be set to online_movable in the virtual machine's device management rules. In virtual machines running up-to-date versions of Red Hat Enterprise Linux or CoreOS, this rule is set by default. For information on device management rules, consult the documentation for the virtual machine's operating system. If any of these conditions are not met, the memory hot unplug action may fail or cause unexpected behavior. Hot Unplugging Virtual Memory Click Compute Virtual Machines and select a running virtual machine. Click the Vm Devices tab. In the Hot Unplug column, click Hot Unplug beside the memory device to be removed. Click OK in the Memory Hot Unplug window. The Physical Memory Guaranteed value for the virtual machine is decremented automatically if necessary.

Commands:
6.12. Affinity Labels 6.12.1. About Affinity Labels You can create and modify Affinity Labels in the Administration Portal. Affinity Labels are used together with Affinity Groups to set any kind of affinity between virtual machines and hosts (hard, soft, positive, negative). See the Affinity Groups section for more information about affinity hardness and polarity. Warning Affinity labels are a subset of affinity groups and can conflict with them. If there is a conflict, the virtual machine will not start. 6.12.2. Creating an Affinity Label You can create affinity labels from the details view of a virtual machine, host, or cluster. This procedure uses the cluster details view. Creating an Affinity Label Click Compute Clusters and select the appropriate cluster. Click the cluster's name to go to the details view. Click the Affinity Labels tab. Click New . Enter a Name for the affinity label. Use the drop-down lists to select the virtual machines and hosts to be associated with the label. Use the + button to add additional virtual machines and hosts. Click OK . 6.12.3. Editing an Affinity Label You can edit affinity labels from the details view of a virtual machine, host, or cluster. This procedure uses the cluster details view. Editing an Affinity Label Click Compute Clusters and select the appropriate cluster. Click the cluster's name to go to the details view. Click the Affinity Labels tab. Select the label you want to edit. Click Edit . Use the + and - buttons to add or remove virtual machines and hosts to or from the affinity label. Click OK . 6.12.4. Deleting an Affinity Label You can only remove an Affinity Label from the details view of a cluster after it is deleted from each entity. Deleting an Affinity Label Click Compute Clusters and select the appropriate cluster. Click the cluster's name to go to the details view. Click the Affinity Labels tab. Select the label you want to remove. Click Edit . Use the - buttons to remove all virtual machines and hosts from the label. Click OK . Click Delete . Click OK .

Commands:
B.43.3. RHSA-2011:0452 - Important: libtiff security update Updated libtiff 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. The libtiff packages contain a library of functions for manipulating Tagged Image File Format (TIFF) files. CVE-2009-5022 A heap-based buffer overflow flaw was found in the way libtiff processed certain TIFF image files that were compressed with the JPEG compression algorithm. An attacker could use this flaw to create a specially-crafted TIFF file that, when opened, would cause an application linked against libtiff to crash or, possibly, execute arbitrary code. All libtiff users should upgrade to these updated packages, which contain a backported patch to resolve this issue. All running applications linked against libtiff must be restarted for this update to take effect.

Commands:
14.2. Differences Between the CarMart and Transactional Quickstarts Despite the similarity in steps to build, deploy and remove the transactional and non-transactional CarMart quickstarts, some differences must be noted. The following is a list of such differences: CarMart is available for both Remote Client-Server Mode and Library Mode. Transactional CarMart is only available in Library Mode because transactions are not available in Remote Client-Server Mode. The Transactional Quickstart also displays how a transaction rollback occurs. Use the Add car with rollback button to view the rollback. The CarMart example has a simple Add car button instead. 23154%2C+Getting+Started+Guide-6.608-09-2016+09%3A22%3A31JBoss+Data+Grid+6Documentation6.6.1 Report a bug

Commands: