mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 50. Using OSGi blueprint with Camel A custom XML namespace for Blueprint has been created to let you leverage the nice XML dialect. Given Blueprint custom namespaces are not standardized yet, this namespace can only be used on the Apache Aries Blueprint implementation, which is the one used by Apache Karaf. 50.1. Overview The XML schema is mostly the same as the one for Spring, so all the xml snippets throughout the documentation referring to Spring XML also apply to Blueprint routes. Here is a very simple route definition using blueprint: <blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"> <camelContext xmlns="http://camel.apache.org/schema/blueprint"> <route> <from uri="timer:test" /> <to uri="log:test" /> </route> </camelContext> </blueprint> There are a few limitations at this point about the supported xml elements (compared to the Spring xml syntax): beanPostProcessor are specific to Spring and aren't allowed However, using blueprint when you deploy your applications in an OSGi enviroment has several advantages: when upgrading to a new camel version, you don't have to change the namespace, as the correct version will be selected based on the camel packages that are imported by your bundle no startup ordering issue with respect to the custom namespaces and your bundles you can use Blueprint property placeholders 50.2. Using camel-blueprint To leverage camel-blueprint in OSGi, you only need the Aries Blueprint bundle and the camel-blueprint bundle, in addition to camel-core and its dependencies. If you use Karaf, you can use the feature named camel-blueprint which will install all the required bundles.

Commands:
<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"> <camelContext xmlns="http://camel.apache.org/schema/blueprint"> <route> <from uri="timer:test" /> <to uri="log:test" /> </route> </camelContext> </blueprint>
9.2. Other Resources The National Security Agency (NSA) From the NSA Contributors to SELinux page: Researchers in NSA's National Information Assurance Research Laboratory (NIARL) designed and implemented flexible mandatory access controls in the major subsystems of the Linux kernel and implemented the new operating system components provided by the Flask architecture, namely the security server and the access vector cache. The NSA researchers reworked the LSM-based SELinux for inclusion in Linux 2.6. NSA has also led the development of similar controls for the X Window System (XACE/XSELinux) and for Xen (XSM/Flask). Main SELinux website: http://www.nsa.gov/research/selinux/index.shtml . SELinux documentation: http://www.nsa.gov/research/selinux/docs.shtml . SELinux background: http://www.nsa.gov/research/selinux/background.shtml . Tresys Technology Tresys Technology are the upstream for: SELinux userland libraries and tools . SELinux Reference Policy . SELinux Project Wiki Main page: http://selinuxproject.org/page/Main_Page . User resources, including links to documentation, mailing lists, websites, and tools: http://selinuxproject.org/page/User_Resources . Fedora Main page: http://fedoraproject.org/wiki/SELinux . Troubleshooting: http://fedoraproject.org/wiki/SELinux/Troubleshooting . Fedora SELinux FAQ: http://docs.fedoraproject.org/ . SELinux Managing Confined Services Guide: http://docs.fedoraproject.org/ The UnOfficial SELinux FAQ http://www.crypt.gen.nz/selinux/faq.html IRC On Freenode : #selinux #fedora-selinux #security

Commands:
Chapter 10. Deleting a bucket from your object store To delete a bucket from your object store from your workbench, use the delete_bucket() method. Prerequisites You have cloned the odh-doc-examples repository to your workbench. You have opened the s3client_examples.ipynb file in your workbench. You have installed Boto3 and configured an S3 client. You have ensured that the bucket that you want to delete is empty. Procedure In the notebook, locate the following instructions to delete a bucket: Replace <bucket_name> with the name of the bucket that you want to delete and run the code cell. The output displays an HTTP response status code of 200 , which indicates that the request was successful. Verification Locate the instructions to list buckets, and execute the code cell. The bucket that you deleted does not appear in the output.

Commands:
#Delete bucket s3_client.delete_bucket(Bucket='<bucket_name>')
#Delete bucket s3_client.delete_bucket(Bucket='aqs971-image-registry')
for bucket in s3_client.list_bucket()['Buckets']: print(bucket['Name'])
Chapter 19. Installing Kernel-64k on ARM using the command line By default, RHEL 9 is distributed with a kernel supporting a 4k page size. This 4k kernel is sufficient for efficient memory usage in smaller environments or small cloud instances where the usage of a 64k page kernel is not practical due to space, power, and cost constraints. If you have already installed RHEL with the default kernel (supporting 4k page size), you can install kernel-64k post installation using the command line. Important It is not recommended to move between 4k and 64k page size kernels after the initial boot without reinstallation of the OS. Procedure Open the terminal as the root user, and enter: To set the kernel-64k as default, enter: Set the system boot order to use RHEL as the default option. Obtain the current boot order. For example: Set the boot order to prioritize RHEL. For example, for the output in the step, use the following command: Reboot the system: Optional: After reboot, remove the 4k kernel: Keeping both versions accidentally can make the 4k kernel default when you update the kernel in future using the yum update command. Verification To verify the page size, open the terminal and run the following command as any user: The output 65536 indicates that the 64k kernel is in use. To verify swap is enabled, enter: The total and free columns are non-zero, which indicates the swap is enabled successfully.

Commands:
dnf -y install kernel-64k
k=USD(echo /boot/vmlinuz*64k) grubby --set-default=USDk --update-kernel=USDk --args="crashkernel=2G-:640M"
efibootmgr BootCurrent: 0000 Timeout: 5 seconds BootOrder: 0003,0004,0001,0000,0002,0005 Boot0000\* Red Hat Enterprise Linux
efibootmgr -o 0000,0001,0002,0003,0004,0005
reboot
dnf erase kernel
getconf PAGESIZE 65536
free total used free shared buff/cache available Mem: 35756352 3677184 34774848 25792 237120 32079168 Swap: 6504384 0 6504384
1.3. Enabling Support for Software Collections To enable support for Software Collections on your system so that you can enable and build Software Collections, you need to have installed the packages scl-utils and scl-utils-build . If the packages scl-utils and scl-utils-build are not already installed on your system, you can install them by typing the following at a shell prompt as root: The scl-utils package provides the scl tool that lets you enable Software Collections on your system. For more information on enabling Software Collections, see Section 1.6, "Enabling a Software Collection" . The scl-utils-build package provides macros that are essential for building Software Collections. For more information on building Software Collections, see Section 2.12, "Building a Software Collection" . Important Depending on the subscriptions available to your Red Hat Enterprise Linux system, you may need to enable the Optional channel to install the scl-utils-build package.

Commands:
yum install scl-utils scl-utils-build
2.4. PAM and Administrative Credential Caching A number of graphical administrative tools in Red Hat Enterprise Linux provide users with elevated privileges for up to five minutes using the pam_timestamp.so module. It is important to understand how this mechanism works, because a user who walks away from a terminal while pam_timestamp.so is in effect leaves the machine open to manipulation by anyone with physical access to the console. In the PAM timestamp scheme, the graphical administrative application prompts the user for the root password when it is launched. When the user has been authenticated, the pam_timestamp.so module creates a timestamp file. By default, this is created in the /var/run/sudo/ directory. If the timestamp file already exists, graphical administrative programs do not prompt for a password. Instead, the pam_timestamp.so module freshens the timestamp file, reserving an extra five minutes of unchallenged administrative access for the user. You can verify the actual state of the timestamp file by inspecting the file in the /var/run/sudo/ user directory. For the desktop, the relevant file is unknown:root . If it is present and its timestamp is less than five minutes old, the credentials are valid. The existence of the timestamp file is indicated by an authentication icon, which appears in the notification area of the panel. Figure 2.1. The Authentication Icon 2.4.1. Removing the Timestamp File Before abandoning a console where a PAM timestamp is active, it is recommended that the timestamp file be destroyed. To do this from a graphical environment, click the authentication icon on the panel. This causes a dialog box to appear. Click the Forget Authorization button to destroy the active timestamp file. Figure 2.2. Dismiss Authentication Dialog The PAM timestamp file has some important characteristics: If logged in to the system remotely using ssh , use the /sbin/pam_timestamp_check -k root command to destroy the timestamp file. Run the /sbin/pam_timestamp_check -k root command from the same terminal window where the privileged application was launched. The logged in user who originally invoked the pam_timestamp.so module must be the user who runs the /sbin/pam_timestamp_check -k command. Do not run this command as root. Killing the credentials on the desktop without using the Forget Authorization action on the icon can be done with the /sbin/pam_timestamp_chec command. Any other method only removes the credentials from the pty where the command was run. Refer to the pam_timestamp_check man page for more information about destroying the timestamp file using pam_timestamp_check . 2.4.2. Common pam_timestamp Directives The pam_timestamp.so module accepts several directives, with two used most commonly: timestamp_timeout - Specifies the period (in seconds) for which the timestamp file is valid. The default value is 300 (five minutes). timestampdir - Specifies the directory in which the timestamp file is stored. The default value is /var/run/sudo/ .

Commands:
/sbin/pam_timestamp_check -k root </dev/null >/dev/null 2>/dev/null
Chapter 22. Branding a Red Hat Quay deployment on the legacy UI You can brand the UI of your Red Hat Quay deployment by changing the registry title, logo, footer image, and by directing users to a website embedded in the footer image. Procedure Update your Red Hat Quay config.yaml file to add the following parameters: BRANDING: logo: 1 footer_img: 2 footer_url: 3 --- REGISTRY_TITLE: 4 REGISTRY_TITLE_SHORT: 5 1 The URL of the image that will appear at the top of your Red Hat Quay deployment. 2 The URL of the image that will appear at the bottom of your Red Hat Quay deployment. 3 The URL of the website that users will be directed to when clicking the footer image. 4 The long-form title for the registry. This is displayed in frontend of your Red Hat Quay deployment, for example, at the sign in page of your organization. 5 The short-form title for the registry. The title is displayed on various pages of your organization, for example, as the title of the tutorial on your organization's Tutorial page. Restart your Red Hat Quay deployment. After restarting, your Red Hat Quay deployment is updated with a new logo, footer image, and footer image URL.

Commands:
BRANDING: logo: 1 footer_img: 2 footer_url: 3 --- REGISTRY_TITLE: 4 REGISTRY_TITLE_SHORT: 5
20.14. Hypervisor Features Hypervisors may allow certain CPU / machine features to be enabled ( state='on') or disabled ( state='off' ). ... <features> <pae/> <acpi/> <apic/> <hap/> <privnet/> <hyperv> <relaxed state='on'/> </hyperv> </features> ... Figure 20.20. Hypervisor features All features are listed within the <features> element, if a <state> is not specified it is disabled. The available features can be found by calling the capabilities XML, but a common set for fully virtualized domains are: Table 20.11. Hypervisor features elements State Description <pae> Physical address extension mode allows 32-bit guest virtual machines to address more than 4 GB of memory. <acpi> Useful for power management, for example, with KVM guest virtual machines it is required for graceful shutdown to work. <apic> Allows the use of programmable IRQ management. For this element, there is an optional attribute eoi with values on and off which sets the availability of EOI (End of Interrupt) for the guest virtual machine. <hap> Enables the use of Hardware Assisted Paging if it is available in the hardware. hyperv Enables various features to improve the behavior of guest virtual machines running Microsoft Windows. Using the optional attribute relaxed with values on or off enables or disables the relax constraints on timers

Commands:
<features> <pae/> <acpi/> <apic/> <hap/> <privnet/> <hyperv> <relaxed state='on'/> </hyperv> </features>
Chapter 3. FAQ Can I install CodeReady Workspaces offline (that is, disconnected from the internet)? Yes, you can. For detailed instructions, see Installing CodeReady Workspaces in restricted environments chapter of the Installation Guide . Can I use non-default certificates with CodeReady Workspaces? Yes, you can use self-signed or public certificates. See Installing CodeReady Workspaces on OpenShift v3 chapter of the Installation Guide . Can I run multiple workspaces simultaneously? Yes. The following two conditions must be met to run multiple workspaces simultaneously: CodeReady Workspaces must use the per-workspace Persistent Volume Claim (PVC) strategy (default), and Persistent volumes (PVs) must use ReadWriteMany (RWX) access mode. Thus to run multiple workspaces simultaneously, ensure the following configuration is set: Set ReadWriteMany (RWX) access mode for PVs. Use the per-workspace PVC strategy (default in CodeReady Workspaces), or optionally, the unique strategy.

Commands:
24.6. Enabling the oVirt Engine Extension Logger log4j Logger implementation requires the ovirt-engine-extension-logger-log4j package. With the implementation, Red Had Virtualization Manager delegates records into log4j. Log4j is a customizable framework that provides appenders for various technologies, including SNMP and syslog. The oVirt Engine Extension Logger log4j passes the engine.log files to an existing syslog server. The configuration procedure overlaps with Setting up a Host Logging Server . Use this procedure on the central syslog server. You can use a separate logging server, or use this procedure to pass the engine.log files from the Manager to the syslog server. Note To define the syslog server for this extension, navigate to the /etc/ovirt-engine/extensions.d directory and edit the value for log4j.appender.myappender.SyslogHost in the Log4jLogger.properties file. To define the syslog facility, navigate to the /etc/ovirt-engine/extensions.d directory and edit the value for log4j.appender.myappender.Facility in the Log4jLogger.properties file. For example, log4j.appender.myappender.Facility=local1 . Configuring the oVirt Engine Extension Logger log4j Install the extension. Create the Log4jLogger.properties file in the /etc/ovirt-engine/extensions.d/ directory and include the following contents. Install and configure rsyslog. Configure SELinux to allow rsyslog traffic. Edit /etc/rsyslog.conf and add the following lines: Uncomment the following two lines. Restart the rsyslog service: If the firewall is enabled and active, run the following command to add the necessary rules for opening the rsyslog ports in Firewalld. Restart Red Hat Virtualization Manager. The existing syslog server can now receive and store the engine.log files.

Commands:
yum install ovirt-engine-extension-logger-log4j
ovirt.engine.extension.name = log4jlogger ovirt.engine.extension.provides = org.ovirt.engine.api.extensions.logger.Logger ovirt.engine.extension.bindings.method = jbossmodule ovirt.engine.extension.binding.jbossmodule.module = org.ovirt.engine-extensions.logger.log4j ovirt.engine.extension.binding.jbossmodule.class = org.ovirt.engineextensions.logger.log4j.Log4jLogger log4j.rootLogger=DEBUG, myappender log4j.appender.myappender=org.apache.log4j.net.SyslogAppender log4j.appender.myappender.SyslogHost=localhost log4j.appender.myappender.layout=org.apache.log4j.PatternLayout log4j.appender.myappender.layout.ConversionPattern=[%c] %m%n
yum install rsyslog
semanage port -a -t syslogd_port_t -p udp 514
USDtemplate TmplAuth, "/var/log/%fromhost%/secure" USDtemplate TmplMsg, "/var/log/%fromhost%/messages" USDRuleSet remote authpriv.* ?TmplAuth *.info,mail.none;authpriv.none,cron.none ?TmplMsg USDRuleSet RSYSLOG_DefaultRuleset USDInputUDPServerBindRuleset remote
#USDModLoad imudp #USDUDPServerRun 514
systemctl restart rsyslog.service
firewall-cmd --permanent --add-port=514/udp firewall-cmd --reload
restart ovirt-engine
4.349. xfsprogs 4.349.1. RHBA-2011:1736 - xfsprogs bug fix update Updated xfsprogs packages that fix two bugs are now available. xfsprogs contains a set of commands to use the XFS filesystem, including mkfs.xfs. Bug Fixes BZ# 679154 xfs_quota is the xfsprogs utility for managing XFS file system quotas. When "xfs_quota" was run on an XFS file system which had user quotas enabled but no enabled group quotas, it generated "XFS_GETQUOTA: No such process" errors. That is, xfs_quota was asking for and attempting to report on quotas which were not there. This update corrects this behavior. xfs_quota no longer tries to report on quotas that are not present and, consequently, the error above no longer presents. BZ# 694706 xfs_repair is the xfsprogs utility for repairing XFS file systems. Previously, when "xfs_repair -n" (the "-n" switch puts xfs_repair into "report-only, do not modify" mode) was run on an XFS filesystem, a check for whether a particular called pointer -- agno -- was within the file system was not done. In some circumstances (for example, if the file system had corrupted directory entries) this could cause the utility to read uninitialized memory, resulting in a segfault. As of this update "xfs_mount" is specifically passed to affected functions and agno is checked to ensure it is inside the XFS file system. Consequently, the uninitialized memory reads and resultant segfaults no longer occur. All XFS users should upgrade to these updated packages, which resolve these issues.

Commands:
2.3. Dynamic List Structure The operating system requires a set of information on each processor in the system. In Red Hat Enterprise Linux 5, this set of information was allocated to a fixed-size array in memory. Information on each individual processor was obtained by indexing into this array. This method was fast, easy, and straightforward for systems that contained relatively few processors. However, as the number of processors for a system grows, this method produces significant overhead. Because the fixed-size array in memory is a single, shared resource, it can become a bottleneck as more processors attempt to access it at the same time. To address this, Red Hat Enterprise Linux 6 uses a dynamic list structure for processor information. This allows the array used for processor information to be allocated dynamically: if there are only eight processors in the system, then only eight entries are created in the list. If there are 2048 processors, then 2048 entries are created as well. A dynamic list structure allows more fine-grained locking. For example, if information needs to be updated at the same time for processors 6, 72, 183, 657, 931 and 1546, this can be done with greater parallelism. Situations like this obviously occur much more frequently on large, high-performance systems than on small systems.

Commands:
3.2. Default File Based Authentication Module The default login module for teiid-security is RealmDirect: Note This module uses md5 to encrypt passwords. By default, Red Hat JBoss Data Virtualization inherits its definition of users and roles from EAP. You will find the configuration in the following section of the relevant configuration file (either (standalone/configuration/standalone.xml or domain/configuration/host.xml): See Also: Section 1.3, "Configure Authentication in a Security Domain"

Commands:
<subsystem xmlns="urn:jboss:domain:security:1.2"> <security-domain name="teiid-security" cache-type="default"> <authentication> <login-module code="RealmDirect" flag="sufficient"> <module-option name="password-stacking" value="useFirstPass"/> </login-module> </authentication> </security-domain>
<security-realm name="ApplicationRealm">
function::user_string_quoted Name function::user_string_quoted - Retrieves and quotes string from user space. Synopsis Arguments addr The user space address to retrieve the string from. General Syntax user_string_quoted:string(addr:long) Description Returns the null terminated C string from a given user space memory address where any ASCII characters that are not printable are replaced by the corresponding escape sequence in the returned string. Reports " NULL " for address zero. Returns " <unknown> " on the rare cases when userspace data is not accessible at the given address.

Commands:
function user_string_quoted:string(addr:long)
7.148. mod_revocator 7.148.1. RHBA-2013:0411 - mod_revocator bug fix update Updated mod_revocator packages that fix one bug are now available for Red Hat Enterprise Linux 6. The mod_revocator module retrieves and installs remote Certificate Revocation Lists (CRLs) into an Apache web server. Bug Fix BZ#861999 When "exec" URIs were used to configure Certificate Revocate Lists (CRLs), the mod_revocator module failed to load these URIs with the following error message: Unable to load Revocation module, NSS error -8187. CRL retrieval will be disabled. A patch has been provided to fix this problem, and CRL URIs are now loaded as expected in this scenario. Users of mod_revocator are advised to upgrade to these updated packages, which fix this bug.

Commands: