mtpti5iD/redhat-docs_dataset huggingface dataset:
38.2. Systems Registered with RHN Classic There is no command to specifically unregister a system which is registered with RHN Classic. To delete the registration locally, remove the file with the system ID assigned to the system when it was registered: Note If the system is being unregistered in order to register it with Red Hat Subscription Management (Customer Portal Subscription Management, Subscription Asset Manager, or CloudForms System Engine), then instead of unregistering the system, use the rhn-migrate-classic-to-rhsm script to migrate the system and all its attached subscriptions to the specified Red Hat Subscription Management server. Using the migration scripts is covered in the Subscription Management Guide .

Commands:
rm -rf /etc/sysconfig/rhn/systemid
27.2. At and Batch While Cron is used to schedule recurring tasks, the At utility is used to schedule a one-time task at a specific time and the Batch utility is used to schedule a one-time task to be executed when the system load average drops below 0.8. 27.2.1. Installing At and Batch To determine if the at package is already installed on your system, issue the rpm -q at command. The command returns the full name of the at package if already installed or notifies you that the package is not available. To install the packages, use the yum command in the following form: yum install package To install At and Batch, type the following at a shell prompt: Note that you must have superuser privileges (that is, you must be logged in as root ) to run this command. For more information on how to install new packages in Red Hat Enterprise Linux, see Section 8.2.4, "Installing Packages" .

Commands:
~]# yum install at
8.2.5. Removing Packages Similarly to package installation, Yum allows you to uninstall (remove in RPM and Yum terminology) both individual packages and a package group. Removing Individual Packages To uninstall a particular package, as well as any packages that depend on it, run the following command as root : yum remove package_name As when you install multiple packages, you can remove several at once by adding more package names to the command. For example, to remove totem , rhythmbox , and sound-juicer , type the following at a shell prompt: Similar to install , remove can take these arguments: package names glob expressions file lists package provides Warning Yum is not able to remove a package without also removing packages which depend on it. This type of operation can only be performed by RPM , is not advised, and can potentially leave your system in a non-functioning state or cause applications to misbehave and/or crash. For further information, see Section B.2.4, "Uninstalling" in the RPM chapter. Removing a Package Group You can remove a package group using syntax congruent with the install syntax: yum groupremove group yum remove @ group The following are alternative but equivalent ways of removing the KDE Desktop group: Important When you tell yum to remove a package group, it will remove every package in that group, even if those packages are members of other package groups or dependencies of other installed packages. However, you can instruct yum to remove only those packages which are not required by any other packages or groups by adding the groupremove_leaf_only=1 directive to the [main] section of the /etc/yum.conf configuration file. For more information on this directive, see Section 8.4.1, "Setting [main] Options" .

Commands:
~]# yum remove totem rhythmbox sound-juicer
~]# yum groupremove "KDE Desktop" ~]# yum groupremove kde-desktop ~]# yum remove @kde-desktop
Appendix A. Java IPv4 and IPv6 properties You can use Java properties to configure IPv4 and IPv6 addresses. You can subsequently export these properties to Tomcat and use address values to specify Tomcat bindings. A.1. Overview of Java IPv4 and IPv6 properties Java provides two properties that you can use to configure IPv4 and IPv6 addresses: java.net.preferIPv4Stack (default: false) If IPv6 is available, the underlying native socket is an IPv6 socket by default. This socket enables applications to connect and accept connections from IPv4 and IPv6 hosts. If applications use IPv4 sockets only, set this property to true . However, applications that are using IPv4 sockets only cannot communicate with IPv6-only hosts. java.net.preferIPv6Addresses (default: false) If a host has both IPv4 and IPv6 addresses, and IPv6 is available, the default behavior is to use IPv4 addresses over IPv6. This allows backward compatibility. If applications depend on an IPv4 address representation, such as 192.168.1.1, set this property to true to change the preference, and use IPv6 addresses over IPv4 where possible. A.2. Exporting Java IPv4 and IPv6 properties to Tomcat You can export Java IPv4 and IPv6 properties to Tomcat by setting CATALINA_OPTS in the JWS_HOME /tomcat/bin/setenv.* file. On Red Hat Enterprise Linux, the setenv file has a . sh extension. On Microsoft Windows, the setenv file has a .bat extension. Procedure If the JWS_HOME /tomcat/bin/setenv.* file does not exist, create the file. Note If you are using Red Hat Enterprise Linux, create a setenv.sh file. If you are using Microsoft Windows, create a setenv.bat file. To export Java IPv4 and IPv6 properties to Tomcat, perform either of the following steps: If you are using Red Hat Enterprise Linux, enter the following command: If you are using Microsoft Windows, enter the following command: A.3. Configuring Tomcat bindings You can configure Tomcat bindings in the JWS_HOME /tomcat/conf/server.xml file by specifying the IPv6 address. Procedure Open the JWS_HOME /tomcat/conf/server.xml file. To specify the Tomcat binding address, enter the following details: To specify the HTTP connector address, enter the following details: To specify the AJP connector address, enter the following details: Note Ensure that you replace TOMCAT_BINDING_ADDRESS , HTTP_CONNECTOR_ADDRESS , and AJP_CONNECTOR_ADDRESS with the correct IPv6 address.

Commands:
export "CATALINA_OPTS=-Djava.net.preferIPv4Stack= YOUR_VALUE -Djava.net.preferIPv6Addresses= YOUR_VALUE "
set "CATALINA_OPTS=-Djava.net.preferIPv4Stack= YOUR_VALUE -Djava.net.preferIPv6Addresses= YOUR_VALUE "
<Server ... address=" TOMCAT_BINDING_ADDRESS ">
<Connector protocol="HTTP/1.1" ... address=" HTTP_CONNECTOR_ADDRESS ">
<Connector protocol="AJP/1.3" ... address=" AJP_CONNECTOR_ADDRESS ">
1.7. Virtualization System monitoring via SNMP, BZ# 642556 This feature provides KVM support for stable technology that is already used in data center with bare metal systems. SNMP is the standard for monitoring and is extremely well understood as well as computationally efficient. System monitoring via SNMP in Red Hat Enterprise Linux 6.2 allows the KVM hosts to send SNMP traps on events so that hypervisor events can be communicated to the user via standard SNMP protocol. This feature is provided through the addition of a new package: libvirt-snmp . This feature is introduced as a Technology Preview. Wire speed requirement in KVM network drivers Virtualization and cloud products that run networking work loads need to run wire speeds. Up until Red Hat Enterprise Linux 6.1, the only way to reach wire speed on a 10 GB Ethernet NIC with a lower CPU utilization was to use PCI device assignment (passthrough), which limits other features like memory overcommit and guest migration The macvtap / vhost zero-copy capabilities allows the user to use those features when high performance is required. This feature improves performance for any Red Hat Enterprise Linux 6.x guest in the VEPA use case. This feature is introduced as a Technology Preview.

Commands:
14.4. Locking Operations 14.4.1. About the LockManager The LockManager component is responsible for locking an entry before a write process initiates. The LockManager uses a LockContainer to locate, hold and create locks. There are two types of LockContainers JBoss Data Grid uses internally and their choice is dependent on the useLockStriping setting. The first type offers support for lock striping while the second type supports one lock per entry. See Also: Chapter 15, Set Up Lock Striping Report a bug 14.4.2. About Lock Acquisition Red Hat JBoss Data Grid acquires remote locks lazily by default. The node running a transaction locally acquires the lock while other cluster nodes attempt to lock cache keys that are involved in a two phase prepare/commit phase. JBoss Data Grid can lock cache keys in a pessimistic manner either explicitly or implicitly. Report a bug 14.4.3. About Concurrency Levels Concurrency refers to the number of threads simultaneously interacting with the data grid. In Red Hat JBoss Data Grid, concurrency levels refer to the number of concurrent threads used within a lock container. In JBoss Data Grid, concurrency levels determine the size of each striped lock container. Additionally, concurrency levels tune all related JDK ConcurrentHashMap based collections, such as those internal to DataContainers . Report a bug

Commands:
26.2. Configuration Examples 26.2.1. Mapping SELinux users to IdM users The following procedure shows how to create a new SELinux mapping and how to add a new IdM user to this mapping. Procedure 26.1. How to Add a User to an SELinux Mapping To create a new SELinux mapping, enter the following command where SELinux_mapping is the name of the new SELinux mapping and the --selinuxuser option specifies a particular SELinux user: Enter the following command to add an IdM user with the tuser user name to the SELinux mapping: To add a new host named ipaclient.example.com to the SELinux mapping, enter the following command: The tuser user gets the staff_u:s0-s0:c0.c1023 label when logged in to the ipaclient.example.com host:

Commands:
~]USD ipa selinuxusermap-add SELinux_mapping --selinuxuser=staff_u:s0-s0:c0.c1023
~]USD ipa selinuxusermap-add-user --users=tuser SELinux_mapping
~]USD ipa selinuxusermap-add-host --hosts=ipaclient.example.com SELinux_mapping
[tuser@ipa-client]USD id -Z staff_u:staff_r:staff_t:s0-s0:c0.c1023
Chapter 13. log 13.1. log:clear 13.1.1. Description Clear log entries. 13.1.2. Syntax log:clear [options] 13.1.3. Options Name Description --help Display this help message 13.2. log:display 13.2.1. Description Displays log entries. 13.2.2. Syntax log:display [options] [logger] 13.2.3. Arguments Name Description logger The name of the logger. This can be ROOT, ALL, or the name of a logger specified in the org.ops4j.pax.logger.cfg file. 13.2.4. Options Name Description -p Pattern for formatting the output --help Display this help message --no-color Disable syntax coloring of log events -n Number of entries to display -l, --level The minimal log level to display 13.3. log:exception-display 13.3.1. Description Displays the last occurred exception from the log. 13.3.2. Syntax log:exception-display [options] [logger] 13.3.3. Arguments Name Description logger The name of the logger. This can be ROOT, ALL, or the name of a logger specified in the org.ops4j.pax.logger.cfg file. 13.3.4. Options Name Description --help Display this help message 13.4. log:get 13.4.1. Description Shows the currently set log level. 13.4.2. Syntax log:get [options] [logger] 13.4.3. Arguments Name Description logger The name of the logger or ALL (default) 13.4.4. Options Name Description --help Display this help message --no-format Disable table rendered output 13.5. log:load-test 13.5.1. Description Load test log. 13.5.2. Syntax log:load-test [options] 13.5.3. Options Name Description --help Display this help message --messaged --threads 13.6. log:log 13.6.1. Description Log a message. 13.6.2. Syntax log:log [options] message 13.6.3. Arguments Name Description message The message to log 13.6.4. Options Name Description --help Display this help message --level, -l The level the message will be logged at 13.7. log:set 13.7.1. Description Sets the log level. 13.7.2. Syntax log:set [options] level [logger] 13.7.3. Arguments Name Description level The log level to set (TRACE, DEBUG, INFO, WARN, ERROR) or DEFAULT to unset logger Logger name or ROOT (default) 13.7.4. Options Name Description --help Display this help message 13.8. log:tail 13.8.1. Description Continuously display log entries. Use ctrl-c to quit this command 13.8.2. Syntax log:tail [options] [logger] 13.8.3. Arguments Name Description logger The name of the logger. This can be ROOT, ALL, or the name of a logger specified in the org.ops4j.pax.logger.cfg file. 13.8.4. Options Name Description -p Pattern for formatting the output --help Display this help message --no-color Disable syntax coloring of log events -n Number of entries to display -l, --level The minimal log level to display

Commands:
Chapter 3. General Updates abrt no longer missing a dependency on python-argparse A previously missing dependency of the abrt packages on the python-argparse package resulting in errors like ImportError: No module named argparse has been fixed. This problem usually occurred if customers upgraded from an earlier version of Red Hat Enterprise Linux, or during a fresh installation if customers removed the nfs-utils or ipa-client packages. (BZ# 1246539 ) rds-stress can now correctly send messages of varying size The rds-stress command previously could not send Reliable Datagram Sockets (RDS) messages of varying sizes if RDMA was enabled due to bugs in both the kernel and in the rds-tools package. These bugs have been fixed and you can now send RDS messages of any size as expected. (BZ#746716)

Commands:
Chapter 17. Enabling faster client IO or recovery IO during OSD backfill During a maintenance window, you may want to favor either client IO or recovery IO. Favoring recovery IO over client IO will significantly reduce OSD recovery time. The valid recovery profile options are balanced , high_client_ops , and high_recovery_ops . Set the recovery profile using the following procedure. Prerequisites Download the odf-cli tool from the customer portal . Procedure Check the current recovery profile: Modify the recovery profile: Replace option with either balanced , high_client_ops , or high_recovery_ops . Verify the updated recovery profile:

Commands:
odf get recovery-profile
odf set recovery-profile <option>
odf get recovery-profile
function::proc_mem_string_pid Name function::proc_mem_string_pid - Human readable string of process memory usage Synopsis Arguments pid The pid of process to examine Description Returns a human readable string showing the size, rss, shr, txt and data of the memory used by the given process. For example " size: 301m, rss: 11m, shr: 8m, txt: 52k, data: 2248k " .

Commands:
function proc_mem_string_pid:string(pid:long)
function::ubacktrace Name function::ubacktrace - Hex backtrace of current user-space task stack. Synopsis Arguments None Description Return a string of hex addresses that are a backtrace of the stack of the current task. Output may be truncated as per maximum string length. Returns empty string when current probe point cannot determine user backtrace. See backtrace for kernel traceback. Note To get (full) backtraces for user space applications and shared shared libraries not mentioned in the current script run stap with -d /path/to/exe-or-so and/or add --ldd to load all needed unwind data.

Commands:
ubacktrace:string()
Chapter 23. Customizing the branding of Business Central You can customize the branding of the Business Central login page and application header by replacing the images with your own. 23.1. Customizing the Business Central login page You can customize the company logo and the project logo on the Business Central login page. Procedure Start Red Hat JBoss EAP and open Business Central in a web browser. Copy an SVG format image to the EAP_HOME /standalone/deployments/business-central.war/img/ directory in your Red Hat Decision Manager installation. In the EAP_HOME /standalone/deployments/business-central.war/img/ directory, either move or rename the existing redhat_logo.png file. Rename your PNG file redhat_logo.png . To change the project logo that appears above the User name and Password fields, replace the default image BC_Logo.png with a new SVG file. Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5. 23.2. Customizing Business Central application header You can customize the Business Central application header. Procedure Start Red Hat JBoss EAP, open Business Central in a web browser, and log in with your user credentials. Copy your new application header image in the SVG format to the EAP_HOME /standalone/deployments/business-central.war/banner/ directory in your Red Hat Decision Manager installation. Open the EAP_HOME /standalone/deployments/business-central.war/banner/banner.html file in a text editor. Replace logo.png in the <img> tag with the file name of your new image:admin-and-config/ Force a full reload of the login page, bypassing the cache, to view the changes. For example, in most Linux and Windows web browsers, press Ctrl+F5.

Commands:
<img src="banner/logo.png"/>
5.18. Additional Resources The following sources of information provide additional resources regarding firewalld . 5.18.1. Installed Documentation firewalld(1) man page - Describes command options for firewalld . firewalld.conf(5) man page - Contains information to configure firewalld . firewall-cmd(1) man page - Describes command options for the firewalld command-line client. firewall-config(1) man page - Describes settings for the firewall-config tool. firewall-offline-cmd(1) man page - Describes command options for the firewalld offline command-line client. firewalld.icmptype(5) man page - Describes XML configuration files for ICMP filtering. firewalld.ipset(5) man page - Describes XML configuration files for the firewalld IP sets. firewalld.service(5) man page - Describes XML configuration files for firewalld service . firewalld.zone(5) man page - Describes XML configuration files for firewalld zone configuration. firewalld.direct(5) man page - Describes the firewalld direct interface configuration file. firewalld.lockdown-whitelist(5) man page - Describes the firewalld lockdown whitelist configuration file. firewalld.richlanguage(5) man page - Describes the firewalld rich language rule syntax. firewalld.zones(5) man page - General description of what zones are and how to configure them. firewalld.dbus(5) man page - Describes the D-Bus interface of firewalld . 5.18.2. Online Documentation http://www.firewalld.org/ - firewalld home page.

Commands:
Chapter 2. Learn more about OpenShift Container Platform Use the following sections to find content to help you learn about and use OpenShift Container Platform. 2.1. Architect Learn about OpenShift Container Platform Plan an OpenShift Container Platform deployment Additional resources Enterprise Kubernetes with OpenShift Tested platforms OpenShift blog Architecture Security and compliance What's new in OpenShift Container Platform Networking OpenShift Container Platform life cycle Backup and restore 2.2. Cluster Administrator Learn about OpenShift Container Platform Deploy OpenShift Container Platform Manage OpenShift Container Platform Additional resources Enterprise Kubernetes with OpenShift Installing OpenShift Container Platform Using Insights to identify issues with your cluster Getting Support Architecture Post installation configuration Logging OpenShift Knowledgebase articles OpenShift Interactive Learning Portal Networking Monitoring overview OpenShift Container Platform Life Cycle Storage Backup and restore Updating a cluster 2.3. Application Site Reliability Engineer (App SRE) Learn about OpenShift Container Platform Deploy and manage applications Additional resources OpenShift Interactive Learning Portal Projects Getting Support Architecture Operators OpenShift Knowledgebase articles Logging OpenShift Container Platform Life Cycle Blogs about logging Monitoring 2.4. Developer Learn about application development in OpenShift Container Platform Deploy applications Getting started with OpenShift for developers (interactive tutorial) Creating applications Red Hat Developers site Builds Red Hat OpenShift Dev Spaces (formerly Red Hat CodeReady Workspaces) Operators Images Developer-focused CLI

Commands:
Chapter 35. Log Files Log files are files that contain messages about the system, including the kernel, services, and applications running on it. There are different log files for different information. For example, there is a default system log file, a log file just for security messages, and a log file for cron tasks. Log files can be very useful when trying to troubleshoot a problem with the system such as trying to load a kernel driver or when looking for unauthorized log in attempts to the system. This chapter discusses where to find log files, how to view log files, and what to look for in log files. Some log files are controlled by a daemon called syslogd . A list of log messages maintained by syslogd can be found in the /etc/syslog.conf configuration file. 35.1. Locating Log Files Most log files are located in the /var/log/ directory. Some applications such as httpd and samba have a directory within /var/log/ for their log files. You may notice multiple files in the log file directory with numbers after them. These are created when the log files are rotated. Log files are rotated so their file sizes do not become too large. The logrotate package contains a cron task that automatically rotates log files according to the /etc/logrotate.conf configuration file and the configuration files in the /etc/logrotate.d/ directory. By default, it is configured to rotate every week and keep four weeks worth of log files.

Commands:
Chapter 85. versions This chapter describes the commands under the versions command. 85.1. versions show Show available versions of services Usage: Table 85.1. Command arguments Value Summary -h, --help Show this help message and exit --all-interfaces Show values for all interfaces --interface <interface> Show versions for a specific interface. --region-name <region_name> Show versions for a specific region. --service <region_name> Show versions for a specific service. --status <region_name> Show versions for a specific status. [valid values are SUPPORTED, CURRENT, DEPRECATED, EXPERIMENTAL] Table 85.2. Output formatter options Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 85.3. CSV formatter options Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 85.4. JSON formatter options Value Summary --noindent Whether to disable indenting the json Table 85.5. Table formatter options Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack versions show [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--all-interfaces | --interface <interface>] [--region-name <region_name>] [--service <region_name>] [--status <region_name>]