mtpti5iD/redhat-docs_dataset huggingface dataset:
10.5.60. Location The <Location> and </Location> tags create a container in which access control based on URL can be specified. For instance, to allow people connecting from within the server's domain to see status reports, use the following directives: Replace <.example.com> with the second-level domain name for the Web server. To provide server configuration reports (including installed modules and configuration directives) to requests from inside the domain, use the following directives: Again, replace <.example.com> with the second-level domain name for the Web server.

Commands:
<Location /server-status> SetHandler server-status Order deny,allow Deny from all Allow from <.example.com> </Location>
<Location /server-info> SetHandler server-info Order deny,allow Deny from all Allow from <.example.com> </Location>
probe::netfilter.arp.out Name probe::netfilter.arp.out - - Called for each outgoing ARP packet Synopsis netfilter.arp.out Values ar_tip Ethernet+IP only (ar_pro==0x800): target IP address nf_drop Constant used to signify a 'drop' verdict ar_pro Format of protocol address ar_sip Ethernet+IP only (ar_pro==0x800): source IP address indev Address of net_device representing input device, 0 if unknown ar_sha Ethernet+IP only (ar_pro==0x800): source hardware (MAC) address pf Protocol family -- always " arp " ar_op ARP opcode (command) nf_queue Constant used to signify a 'queue' verdict ar_hrd Format of hardware address nf_accept Constant used to signify an 'accept' verdict ar_data Address of ARP packet data region (after the header) ar_tha Ethernet+IP only (ar_pro==0x800): target hardware (MAC) address outdev_name Name of network device packet will be routed to (if known) nf_stop Constant used to signify a 'stop' verdict ar_hln Length of hardware address ar_pln Length of protocol address nf_stolen Constant used to signify a 'stolen' verdict length The length of the packet buffer contents, in bytes outdev Address of net_device representing output device, 0 if unknown nf_repeat Constant used to signify a 'repeat' verdict arphdr Address of ARP header indev_name Name of network device packet was received on (if known)

Commands:
3.2.2.2. The Operating System It is difficult to determine how much processing power is consumed by the operating system. The reason for this is that operating systems use a mixture of process-level and system-level code to perform their work. While, for example, it is easy to use a process monitor to determine what the process running a daemon or service is doing, it is not so easy to determine how much processing power is being consumed by system-level I/O-related processing (which is normally done within the context of the process requesting the I/O.) In general, it is possible to divide this kind of operating system overhead into two types: Operating system housekeeping Process-related activities Operating system housekeeping includes activities such as process scheduling and memory management, while process-related activities include any processes that support the operating system itself, such as processes handling system-wide event logging or I/O cache flushing.

Commands:
8.213. selinux-policy 8.213.1. RHBA-2014:1568 - selinux-policy bug fix and enhancement update Updated selinux-policy packages that fix multiple bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The selinux-policy packages contain the rules that govern how confined processes run on the system. Bug Fixes BZ# 1062384 SELinux prevented the qemu-guest-agent process from executing the settimeofday() and hwclock() functions. Consequently, qemu-guest-agent was unable to set the system time. A new rule has been added to the SELinux policy and qemu-guest-agent can now set the time as expected. BZ# 1082640 Previously, SELinux did not allow the dhcpd daemon to change file ownership on the system. As a consequence, the ownership of files that dhcpd created was changed from the required dhcpd:dhcpd to root:root. The appropriate SELinux policy has been changed, and dhcpd is now able to change the file ownership on the system. BZ# 1097387 Due to the missing miscfiles_read_public_files Boolean, the user could not allow the sshd daemon to read public files used for file transfer services. The Boolean has been added to the SELinux policy, thus providing the user the ability to set sshd to read public files. BZ# 1111538 Due to a missing SELinux policy rule, the syslog daemon was unable to read the syslogd configuration files labeled with the syslog_conf_t SELinux context. With this update, the SELinux policy has been modified accordingly, and syslog now can read the syslog_conf_t files as expected. BZ# 1111581 Due to an insufficient SELinux policy rule, the thttpd daemon ran in the httpd_t domain. As a consequence, the daemon was unable to change file attributes of its log files. The SELinux policy has been modified to fix this bug, and SELinux no longer prevents thttpd from changing attributes of its log files. BZ# 1122866 Previously, SELinux did not allow the sssd daemon to write to the krb5 configuration file, thus the daemon was unable to make any changes in krb5. The SELinux policy has been changed with this update, and sssd can now write to krb5. BZ# 1127602 Due to a missing SELinux policy rule, the Samba daemons could not list the /tmp/ directory. The SELinux policy has been modified accordingly, and SELinux no longer prevents the Samba daemons from listing the /tmp/ directory. In addition, this update adds the following Enhancement BZ# 1069843 With this update, new SELinux policy rules have been added, and the following services now run in their own domains, not in the initrc_t domain: thttpd Users of selinux-policy are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
21.3. Printer Configuration The Printer Configuration tool serves for printer configuring, maintenance of printer configuration files, print spool directories and print filters, and printer classes management. The tool is based on the Common Unix Printing System ( CUPS ). If you upgraded the system from a Red Hat Enterprise Linux version that used CUPS, the upgrade process preserved the configured printers. Important The cupsd.conf man page documents configuration of a CUPS server. It includes directives for enabling SSL support. However, CUPS does not allow control of the protocol versions used. Due to the vulnerability described in Resolution for POODLE SSLv3.0 vulnerability (CVE-2014-3566) for components that do not allow SSLv3 to be disabled via configuration settings , Red Hat recommends that you do not rely on this for security. It is recommend that you use stunnel to provide a secure tunnel and disable SSLv3 . For more information on using stunnel , see the Red Hat Enterprise Linux 6 Security Guide . For ad-hoc secure connections to a remote system's Print Settings tool, use X11 forwarding over SSH as described in Section 14.5.1, "X11 Forwarding" . Note You can perform the same and additional operations on printers directly from the CUPS web application or command line. To access the application, in a web browser, go to http://localhost:631/ . For CUPS manuals see the links on the Home tab of the web site. 21.3.1. Starting the Printer Configuration Tool With the Printer Configuration tool you can perform various operations on existing printers and set up new printers. However, you can use also CUPS directly (go to http://localhost:631/ to access CUPS). On the panel, click System Administration Printing , or run the system-config-printer command from the command line to start the tool. The Printer Configuration window depicted in Figure 21.3, "Printer Configuration window" appears. Figure 21.3. Printer Configuration window

Commands:
Chapter 2. Life cycle dates Red Hat Automation Hub Release General Availability Full support ends Maintenance Support 1 ends End of Life 4.4 December 2, 2021 June 2, 2022 December 2, 2022 June 2, 2023 4.2 November, 18, 2020 May 17, 2021 November 18, 2021 November 18, 2022

Commands:
Chapter 5. Kourier and Istio ingresses OpenShift Serverless supports the following two ingress solutions: Kourier Istio using Red Hat OpenShift Service Mesh The default is Kourier. 5.1. Kourier and Istio ingress solutions 5.1.1. Kourier Kourier is the default ingress solution for OpenShift Serverless. It has the following properties: It is based on envoy proxy. It is simple and lightweight. It provides the basic routing functionality that Serverless needs to provide its set of features. It supports basic observability and metrics. It supports basic TLS termination of Knative Service routing. It provides only limited configuration and extension options. 5.1.2. Istio using OpenShift Service Mesh Using Istio as the ingress solution for OpenShift Serverless enables an additional feature set that is based on what Red Hat OpenShift Service Mesh offers: Native mTLS between all connections Serverless components are part of a service mesh Additional observability and metrics Authorization and authentication support Custom rules and configuration, as supported by Red Hat OpenShift Service Mesh However, the additional features come with a higher overhead and resource consumption. For details, see the Red Hat OpenShift Service Mesh documentation. See the "Integrating Service Mesh with OpenShift Serverless" section of Serverless documentation for Istio requirements and installation instructions. 5.1.3. Traffic configuration and routing Regardless of whether you use Kourier or Istio, the traffic for a Knative Service is configured in the knative-serving namespace by the net-kourier-controller or the net-istio-controller respectively. The controller reads the KnativeService and its child custom resources to configure the ingress solution. Both ingress solutions provide an ingress gateway pod that becomes part of the traffic path. Both ingress solutions are based on Envoy. By default, Serverless has two routes for each KnativeService object: A cluster-external route that is forwarded by the OpenShift router, for example myapp-namespace.example.com . A cluster-local route containing the cluster domain, for example myapp.namespace.svc.cluster.local . This domain can and should be used to call Knative services from Knative or other user workloads. The ingress gateway can forward requests either in the serve mode or the proxy mode: In the serve mode, requests go directly to the Queue-Proxy sidecar container of the Knative service. In the proxy mode, requests first go through the Activator component in the knative-serving namespace. The choice of mode depends on the configuration of Knative, the Knative service, and the current traffic. For example, if a Knative Service is scaled to zero, requests are sent to the Activator component, which acts as a buffer until a new Knative service pod is started.

Commands:
10.4. Installing virt-who Manually This section will describe how to manually attach the subscription provided by the hypervisor. Procedure 10.2. How to attach a subscription manually List subscription information and find the Pool ID First you need to list the available subscriptions which are of the virtual type. Enter the following command: Note the Pool ID displayed. Copy this ID as you will need it in the step. Attach the subscription with the Pool ID Using the Pool ID you copied in the step run the attach command. Replace the Pool ID XYZ123 with the Pool ID you retrieved. Enter the following command:

Commands:
subscription-manager list --avail --match-installed | grep 'Virtual' -B12 Subscription Name: Red Hat Enterprise Linux ES (Basic for Virtualization) Provides: Red Hat Beta Oracle Java (for RHEL Server) Red Hat Enterprise Linux Server SKU: ------- Pool ID: XYZ123 Available: 40 Suggested: 1 Service Level: Basic Service Type: L1-L3 Multi-Entitlement: No Ends: 01/02/2017 System Type: Virtual
subscription-manager attach --pool=XYZ123 Successfully attached a subscription for: Red Hat Enterprise Linux ES (Basic for Virtualization)
probe::ioscheduler.elv_add_request.tp Name probe::ioscheduler.elv_add_request.tp - tracepoint based probe to indicate a request is added to the request queue. Synopsis Values disk_major Disk major no of request. rq Address of request. q Pointer to request queue. name Name of the probe point elevator_name The type of I/O elevator currently enabled. disk_minor Disk minor number of request. rq_flags Request flags.

Commands:
ioscheduler.elv_add_request.tp
Chapter 15. Using 2-way replication with CephFS To reduce storage overhead with CephFS when data resiliency is not a primary concern, you can opt for using 2-way replication (replica-2). This reduces the amount of storage space used and decreases the level of fault tolerance. There are two ways to use replica-2 for CephFS: Edit the existing default pool to replica-2 and use it with the default CephFS storageclass . Add an additional CephFS data pool with replica-2 . 15.1. Editing the existing default CephFS data pool to replica-2 Use this procedure to edit the existing default CephFS pool to replica-2 and use it with the default CephFS storageclass. Procedure Patch the storagecluster to change default CephFS data pool to replica-2. Check the pool details. 15.2. Adding an additional CephFS data pool with replica-2 Use this procedure to add an additional CephFS data pool with replica-2. Prerequisites Ensure that you are logged into the OpenShift Container Platform web console and OpenShift Data Foundation cluster is in Ready state. Procedure Click Storage StorageClasses Create Storage Class . Select CephFS Provisioner . Under Storage Pool , click Create new storage pool . Fill in the Create Storage Pool fields. Under Data protection policy , select 2-way Replication . Confirm Storage Pool creation In the Storage Class creation form, choose the newly created Storage Pool. Confirm the Storage Class creation. Verification Click Storage Data Foundation . In the Storage systems tab, select the new storage system. The Details tab of the storage system reflect the correct volume and device types you chose during creation

Commands:
oc patch storagecluster ocs-storagecluster -n openshift-storage --type json --patch '[{ "op": "replace", "path": "/spec/managedResources/cephFilesystems/dataPoolSpec/replicated/size", "value": 2 }]' storagecluster.ocs.openshift.io/ocs-storagecluster patched
oc get cephfilesystem ocs-storagecluster-cephfilesystem -o=jsonpath='{.spec.dataPools}' | jq [ { "application": "", "deviceClass": "ssd", "erasureCoded": { "codingChunks": 0, "dataChunks": 0 }, "failureDomain": "zone", "mirroring": {}, "quotas": {}, "replicated": { "replicasPerFailureDomain": 1, "size": 2, "targetSizeRatio": 0.49 }, "statusCheck": { "mirror": {} } } ]
ceph osd pool ls | grep filesystem ocs-storagecluster-cephfilesystem-metadata ocs-storagecluster-cephfilesystem-data0
5.254. pulseaudio 5.254.1. RHBA-2012:1070 - pulseaudio bug fix update Updated pulseaudio packages that fix one bug are now available for Red Hat Enterprise Linux 6. PulseAudio is a sound server for Linux and other Unix like operating systems. Bug Fix BZ# 836139 On certain sound card models by Creative Labs, the S/PDIF Optical Raw output was enabled on boot regardless of the settings. This caused the audio output on the analog duplex output to be disabled. With this update, the S/PDIF Optical Raw output is disabled on boot so that the analog output works as expected. All users of pulseaudio are advised to upgrade to these updated packages, which fix this bug.

Commands:
Appendix A. Using your subscription AMQ Streams is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the AMQ Streams for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired AMQ Streams product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2024-04-29 12:48:40 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
Preface Red Hat Enterprise Linux minor releases are an aggregation of individual enhancement, security, and bug fix errata. The Red Hat Enterprise Linux 7.2 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:
9.8. Encrypting the Database Information is stored in a database in plain text. Consequently, some extremely sensitive information, such as government identification numbers or passwords, may not be sufficiently protected by access control measures. It may be possible to gain access to a server's persistent storage files, either directly through the file system or by accessing discarded disk drives or archive media. Database encryption allows individual attributes to be encrypted as they are stored in the database. When configured, every instance of a particular attribute, even index data, is encrypted and can only be accessed using a secure channel, such as TLS. For information on using database encryption, see the "Configuring Directory Databases" chapter in the Red Hat Directory Server Administration Guide .

Commands:
Chapter 2. Configuring the Compute service (nova) To designate and configure all node sets for a particular feature or workload, the Compute service (nova) provides a default ConfigMap CR named nova-extra-config , where you can add generic configuration that applies to all the node sets that use the default nova service. If you use this default nova-extra-config ConfigMap to add generic configuration to be applied to all the node sets, then you do not need to create a custom service. Example of a generic feature configuration: Replace <integer> with an integer that indicates when the configuration should be applied in the series of configuration files that are applied to etc/<service>/<service>.conf.d/ in the <service> container when the service is deployed. Numbers below 25 are reserved for the OpenStack services and Ansible configuration files. Replace <service> with the name of the service. Replace <feature> with a string that identifies the feature. Replace <section> with the section to which you want to add the configuration. You can configure only whole node sets. Reconfiguring a subset of the nodes within a node set is not supported. If you need to reconfigure a subset of nodes within a node set, you must split the node set via scaling in the current node set, remove the scaled in nodes from the node set, and add them to a new node set. If your deployment has more than one node set, changes to the nova-extra-config ConfigMap might directly affect more than one node set, depending on how the node sets and the DataPlaneServices are configured. Procedure Create or update the default ConfigMap CR named nova-extra-config . Create a new OpenStackDataPlaneDeployment CR to configure the services on the data plane nodes. Specify nodeSets to include all the OpenStackDataPlaneNodeSet CRs you want to deploy. Deploy the data plane. Additional resources Customizing the data plane in Customizing the Red Hat OpenStack Services on OpenShift deployment

Commands:
apiVersion: v1 kind: ConfigMap metadata: name: nova-extra-config namespace: openstack data: <integer>-<service>-<feature>.conf: | [<section>] <config_option>=<value>
20.5. Removing Keytabs Refreshing Kerberos tickets adds a new key to the keytab, but it does not clear the keytab. If a host is being unenrolled and re-added to the IdM domain or if there are Kerberos connection errors, then it may be necessary to remove the keytab and create a new keytab. This is done using the ipa-rmkeytab command. To remove all principals on the host, specify the realm with the -r option: To remove the keytab for a specific service, use the -p option to specify the service principal:

Commands:
ipa-rmkeytab -r EXAMPLE.COM -k /etc/krb5.keytab
ipa-rmkeytab -p ldap/client.example.com -k /etc/krb5.keytab
9.2. Add Dependencies to Your Project Set up Red Hat JBoss Data Grid by adding dependencies to your project. If you are using Maven or other build systems that support Maven dependencies, add the following to your pom.xml file, located in the Maven repository folder: Note Replace the version value with the appropriate version of the libraries included in JBoss Data Grid. Report a bug

Commands:
<dependency> <groupId>org.infinispan</groupId> <artifactId>infinispan-embedded</artifactId> <version>USDVERSION</version> </dependency>