mtpti5iD/redhat-docs_dataset huggingface dataset:
3.8. Software Collection cronjob Support With your Software Collection, you can run periodic tasks on the system either with a dedicated service or with cronjobs. If you intend to use a dedicated service, refer to Section 3.4, "Managing Services in Software Collections" on how to work with initscripts in the Software Collection environment. Procedure 3.8. Running periodic tasks with cronjobs To use cronjobs for running periodic tasks, place a crontab file for your Software Collection in the /etc/cron.d/ directory with the Software Collection's name. For example, create the following file: Ensure that the contents of the crontab file follow the standard crontab file format, as in the following example: where software_collection is the name of your Software Collection, and /opt/ provider / software_collection /root/usr/bin/ cron_job_name is the command you want to periodically run. Add the file to your spec file of the Software Collection package: SOURCE2: %{?scl_prefix}crontab Install the file into the system directory /etc/cron.d/ by adjusting the %install section of the Software Collection package's spec file: %install install -p -c -m 644 %{SOURCE2} USDRPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/cron.d/

Commands:
%{?scl_prefix}crontab
0 1 * * Sun root scl enable software_collection ' /opt/ provider / software_collection /root/usr/bin/ cron_job_name '
SOURCE2: %{?scl_prefix}crontab
%install install -p -c -m 644 %{SOURCE2} USDRPM_BUILD_ROOT%{?scl:%_root_sysconfdir}%{!?scl:%_sysconfdir}/cron.d/
Chapter 2. Eclipse Temurin features Eclipse Temurin does not contain structural changes from the upstream distribution of OpenJDK. For the list of changes and security fixes included in the latest OpenJDK 8 release of Eclipse Temurin, see OpenJDK 8.0.342 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements that the Eclipse Temurin 8.0.342 and 8.0.345 releases provide: Customizing PKCS12 keystore generation The OpenJDK 8 release includes a new system property and a new security property that allows you to customize the generation of PKCS #12 keystores. Users can customize algorithms and parameters for key protection, certificate protection, and MacData. You can find information about the properties, including a list of possible values, in the "PKCS12 KeyStore properties" section of the java.security file. Also, the OpenJDK 8 release adds support for the following SHA-2 based HmacPBE algorithms to the SunJCE provider: HmacPBESHA224 HmacPBESHA256 HmacPBESHA384 HmacPBESHA512 HmacPBESHA512/224 HmacPBESHA512/256 See, JDK-8215293 (JDK Bug System) New system property to disable Windows Alternate Data Stream support in java.io.File The Windows implementation of java.io.File , you can access to NTFS Alternate Data Streams (ADS) by default. These streams are structured in the format filename:streamname . The OpenJDK 8.0.342 and 8.0.345 releases add a system property that you can use to disable ADS support in java.io.File . To disable ADS support in java.io.File , set the system property jdk.io.File.enableADS to false . Important Disabling ADS support in java.io.File results in stricter path checking that prevents the use of special device files, such as NUL: . See, JDK-8285660 (JDK Bug System) Revised on 2024-05-10 09:06:39 UTC

Commands:
Chapter 1. Installation overview Red Hat Enterprise Linux AI is distributed and installable as a bootable image. This bootable image includes a container that hold various software and tools for RHEL AI. Each image is compiled to support specific hardware vendors. Each RHEL AI image includes: Red Hat Enterprise Linux 9.4: A RHEL version 9.4 operating system (OS) for your machine. The InstructLab container: Contains InstructLab and various other tools required for RHEL AI. This includes: Python version 3.11: A Python 3.11 installation used internally by InstructLab. The InstructLab tools: The InstructLab command line interface (CLI). The LAB enhanced method of synthetic data generation (SDG). The LAB enhanced method of multi-phase training. InstructLab with vLLM: A high-input inference and serving engine for Large Language models (LLMs). InstructLab with DeepSpeed: A hardware optimization software that speeds up the training process. Similar functionalities of FSDP. InstructLab with FSDP: A training framework that makes training faster and more efficient. Similar functionalities of DeepSpeed Red Hat Enterprise Linux AI version 1.4 also includes a sample taxonomy tree with example skills and knowledge that you can download and use for training a model. For general availability, there are three options for installing and deploying Red Hat Enterprise Linux AI. Installing on bare metal Installing on Amazon Web Service (AWS) Installing on IBM Cloud Installing on Google Cloud Platform (GCP) Installing on Azure After installation with Red Hat Enterprise Linux AI general availability, you can manually download open source Granite LLMs that you can chat and interact with. For more information about downloading these models, see Downloading additional models .

Commands:
Chapter 2. Hardware Enablement 2.1. Intel Broadwell Processor and Graphics Support Red Hat Enterprise Linux 7.1 added initial support for 5th generation Intel processors (code named Broadwell ) with the enablement of the Intel Xeon E3-12xx v4 processor family. Support includes the CPUs themselves, integrated graphics in both 2D and 3D mode, and audio support (Broadwell High Definition Legacy Audio, HDMI audio, and DisplayPort audio). For detailed information regarding CPU enablement in Red Hat Enterprise Linux, please see the Red Hat Knowledgebase article available at https://access.redhat.com/support/policy/intel . The turbostat tool (part of the kernel-tools package) has also been updated with support for the new processors.

Commands:
Chapter 20. 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 OpenShift Data Foundation command line interface (CLI) tool. With the Data Foundation CLI tool, you can effectively manage and troubleshoot your Data Foundation environment from a terminal. You can find a compatible version and download the 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
5.339. udev 5.339.1. RHBA-2012:1007 - udev bug fix update Updated udev packages that fix one bug are now available for Red Hat Enterprise Linux 6. The udev packages implement a dynamic device-directory, providing only the devices present on the system. This dynamic directory runs in user space, dynamically creates and removes devices, provides consistent naming, and a user-space API. Bug Fix BZ# 829703 Due to a bug in the binutils linker, the libudev library lost the ExecShield (GNU_RELRO) section, and was no longer protected by the Exec Shield security mechanism. This update provides a patch which ensures that the libudev library contains the ExecShield (GNU_RELRO) section again. All users of udev are advised to upgrade to these updated packages, which fix this bug. 5.339.2. RHBA-2012:0906 - udev bug fix and enhancement update Updated udev packages that fix multiple bugs are now available for Red Hat Enterprise Linux 6. The udev packages implement a dynamic device-directory, providing only the devices present on the system. This dynamic directory runs in user space, dynamically creates and removes devices, provides consistent naming, and a user-space API. The udev package replaces the devfs package and provides better hot plug functionality. Bug Fixes BZ# 784648 Previously, libudev's function udev_device_get_devnode() returned NULL if the function was called before the udevd daemon processed the uevent for the device node. With this update, the udev_device_get_devnode() function now returns the devnode provided by the kernel. BZ# 735410 Previously, the udev-post non-service script located in the /etc/init.d/ directory always returned a failure code on a status request. This bug has been fixed in this update so that the udev-post service now returns information on whether it has already been run. BZ# 628762 Previously, the udev(7) man page did not mention the "nowatch" option. With this update, the "nowatch" option is now properly documented in the udev(7) man page. All users of udev are advised to upgrade to these updated packages, which fix these bugs.

Commands:
11.2. Setting Multiple Volume Option A group configuration file is a file used to define and customize volume options. There are some predefined group configuration files for specific workload patterns like negative lookup cache, virtualization, metadata cache and gluster-block. The parameters defined in the file can then be applied to a volume as a group, rather than setting one parameter at a time. Creating a group configuration file Create a new file in the /var/lib/glusterd/groups/ directory. Add the parameters and values that you want to set on the volume to the created file as key-value pairs, placing each parameter on a new line: For example, Adding configurations to volumes Run the following command to apply the configurations in the group file to specific volumes: For example, Note The configuration file created should be placed in all the hosts of the trusted storage pool under /var/lib/glusterd/groups/ . This can be achieved with the help of gdeploy configuration file. For information on deactivating group configuration, see Section 21.5, "Deactivating a group configuration"

Commands:
touch /var/lib/glusterd/groups/ filename
domain1.key1=value1 domain1.key2=value2 domain2.key3=value3
changelog.changelog=on client.event-threads=6 cluster.brick-multiplex=on
gluster volume set volname group filename
gluster volume set volume1 group virt gluster volume set volume2 group virt gluster volume set volume3 group dbgroup
10.3. CMC Authentication Plug-ins CMC enrollment allows an enrollment client to use a CMC Authentication plug-in for authentication, by which the certificate request is either pre-signed with an agent certificate or a user certificate, depending on the plug-in. The Certificate Manager automatically issues certificates when a CMC request signed with a valid certificate is received. The CMC authentication plug-ins also provide CMC revocation for the client. CMC revocation allows the client to have the certificate request either signed by the agent certificate, or a verifiable user that owns the certificate, and then send such a request to the Certificate Manager. The Certificate Manager automatically revokes certificates when a CMC revocation request signed with a valid certificate is received. Certificate System provides the following CMC authentication plug-ins: CMCAuth Use this plug-in when a CA agent signs CMC requests. To use the CMCAuth plug-in, set the following in the enrollment profile: By default, the following enrollment profiles use the CMCAuth plug-in: For system certificates: caCMCauditSigningCert caCMCcaCert caCMCECserverCert caCMCECsubsystemCert caCMCECUserCert caCMCkraStorageCert caCMCkraTransportCert caCMCocspCert caCMCserverCert caCMCsubsystemCert For user certificates: caCMCUserCert caECFullCMCUserCert caFullCMCUserCert CMCUserSignedAuth Use this plug-in when users submit signed or SharedSecret-based CMC requests. To use the CMCUserSignedAuth plug-in, set the following in the enrollment profile: A user-signed CMC request must be signed by the user's certificate which contains the same subjectDN attribute as the requested certificate. You can only use a user-signed CMC request if the user already obtained a signing certificate which can be used to prove the user's identity for other certificates. A SharedSecret-based CMC request means that the request was signed by the private key of the request itself. In this case, the CMC request must use the Shared Secret mechanism for authentication. A SharedSecret-based CMC request is typically used to obtain the user's first signing certificate, which is later used to obtain other certificates. For further details, see Section 10.4, "CMC SharedSecret Authentication" . By default, the following enrollment profiles use the CMCUserSignedAuth plug-in: caFullCMCUserSignedCert caECFullCMCUserSignedCert caFullCMCSharedTokenCert caECFullCMCSharedTokenCert

Commands:
auth.instance_id=CMCAuth
auth.instance_id=CMCUserSignedAuth
probe::socket.create.return Name probe::socket.create.return - Return from Creation of a socket Synopsis socket.create.return Values success Was socket creation successful? (1 = yes, 0 = no) family Protocol family value requester Requested by user process or the kernel (1 = kernel, 0 = user) name Name of this probe protocol Protocol value type Socket type value err Error code if success == 0 Context The requester (user process or kernel) Description Fires at the conclusion of creating a socket.

Commands:
Appendix A. API response codes The Red Hat Satellite 6 API provides HTTP response status codes for API calls. The following codes are common for all resources in the Satellite API. Table A.1. API response codes Response Explanation 200 OK For a successful request action: show, index, update, or delete (GET, PUT, DELETE requests). 201 Created For a successful create action (POST request). 301 Moved Permanently Redirect when Satellite is restricted to use HTTPS and HTTP is attempted. 400 Bad Request A required parameter is missing or the search query has invalid syntax. 401 Unauthorized Failed to authorize the user (for example, incorrect credentials). 403 Forbidden The user has insufficient permissions to perform the action or read the resource, or the action is unsupported in general. 404 Not Found The record with the given ID does not exist. It can appear in show and delete actions when the requested record does not exist; or in create, update and delete actions when one of the associated records does not exist. 409 Conflict Could not delete the record due to existing dependencies (for example, host groups with hosts). 415 Unsupported Media Type The content type of the HTTP request is not JSON. 422 Unprocessable Entity Failed to create an entity due to some validation errors. Applies to create or update actions only. 500 Internal Server Error Unexpected internal server error. 503 Service Unavailable The server is not running.

Commands:
12.5. Prestarting Virtual Machines in a Pool The virtual machines in a virtual machine pool are powered down by default. When a user requests a virtual machine from a pool, a machine is powered up and assigned to the user. In contrast, a prestarted virtual machine is already running and waiting to be assigned to a user, decreasing the amount of time a user has to wait before being able to access a machine. When a prestarted virtual machine is shut down it is returned to the pool and restored to its original state. The maximum number of prestarted virtual machines is the number of virtual machines in the pool. Prestarted virtual machines are suitable for environments in which users require immediate access to virtual machines which are not specifically assigned to them. Only automatic pools can have prestarted virtual machines. Prestarting Virtual Machines in a Pool Click Compute Pools and select the virtual machine pool. Click Edit . Enter the number of virtual machines to be prestarted in the Prestarted VMs field. Click the Type tab. Ensure Pool Type is set to Automatic . Click OK .

Commands:
8.144. perl-Config-General 8.144.1. RHBA-2013:1669 - perl-Config-General bug fix and enhancement update Updated perl-Config-General packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The Config::General Perl module is able to parse and write configuration files and presents an object-oriented access to their data. In addition, the Config::General module is 100% read-compatible with Apache configuration files, though it is also possible to create and access simple name/value configuration files. Certain enhancements such as here-documents, C-style comments and multi-line options are also available. Note The perl-Config-General package has been upgraded to upstream version 2.52, which provides a number of bug fixes and enhancements over the version. The most significant of these changes are the following: * When the Config::General module was supplied a directory instead of a configuration file, the module silently accepted it and returned an empty configuration hash. After this update, the module now calls the croak() function if the configuration file parameter is a directory and the "directory include" option is not turned on. * Parsing now accepts white spaces after the block closing character ">". * The save_file() function and a named block, whose second part starts with a slash character (/), now can be used to write valid configurations to a file correctly." * With this update, the sort() function is no longer used on arrays if the "-SaveSorted" option is turned off. * A character escaping bug has been fixed. Escaping the dollar "USD" or the backslash "\" characters is now handled correctly. * A tied hash now remains tied when saving to a file. * Preserving the single quotes during a variable interpolation has been corrected. An incrementor is now used to mark single quotes instead of using the rand() function. * Empty configuration values are no longer handed over to interpreting methods. * The "-Plug" parameter, which introduces plugin closures, has been added to the perl-Config-General packages. * The "-NoEscape" switch, which turns off escaping of every character, has been added to the perl-Config-General packages. * The parameters "-NormalizeOption", "-NormalizeBlock" and "-NormalizeValue", which take a subroutine reference and change a block, option or value accordingly, have been added to the perl-Config-General packages. * A new option "-AllowSingleQuoteInterpolation", which turns on interpolation for variables inside single quotes, has been added to the perl-Config-General packages. * A new option "-ForceArray" has been added to the perl-Config-General packages. When enabled, a single configuration value enclosed in square brackets "[ ]" will become an array forcefully. With this upgraded perl-Config-General package, users can write and process their configuration files more efficiently. (BZ# 658946 ) Users of perl-Config-General are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
Chapter 1. Migration from Service Registry 1.1 to 2.x Service Registry 2.x includes new features with breaking changes from the Service Registry 1.1 release. This section describes the major changes between Service Registry 1.1 and version 2.x. Because of the breaking changes in 2.x, there is no automatic upgrade and a migration process is required. This involves moving the data in your existing registry to a new registry. You must also review your existing registry client applications and update their configuration to meet the new requirements. When migrating to version 2.x, you must take the following major changes into account: 1.1. New data storage options The existing registry data storage options in Service Registry 1.1 ( streams , jpa , and infinispan ) have been replaced with new storage options in version 2.x ( sql and kafkasql ). These new storage options provide more robust, performant, and maintainable Service Registry deployments. For details on how to deploy Service Registry 2.x with your chosen storage option, see Installing and deploying Service Registry on OpenShift . 1.2. New v2 REST API Service Registry 2.x includes a new REST API with support for artifact groups and improved long term maintainability. Service Registry still supports the original registry v1 REST API and compatibility APIs, for example, Confluent and IBM schema registry APIs. Service Registry now also implements the Schema Registry specification provided in the CNCF Cloud Events specification. 1.3. Refactored Java client libraries The Service Registry Java client classes are available in version 2.x in a different Maven module named apicurio-registry-client . The Kafka client serializer and deserializer (SerDes) classes are available in version 2.x in three different Maven modules, one for each supported data format: Apache Avro, Protobuf, and JSON Schema. You can now use only the module you want without pulling in transitive dependencies that you are not concerned with. Additional resources For more details on the v2 REST API, see the Registry REST API documentation .

Commands:
Chapter 1. Shenandoah garbage collector Shenandoah is the low pause time garbage collector (GC) that reduces GC pause times by performing more garbage collection work concurrently with the running Java program. Concurrent Mark Sweep garbage collector (CMS) and G1, default garbage collector for Red Hat build of OpenJDK 8 perform concurrent marking of live objects. Shenandoah adds concurrent compaction. Shenandoah also reduces GC pause times by compacting objects concurrently with running Java threads. Pause times with Shenandoah are independent of the heap size, meaning you will have consistent pause time whether your heap is 200 MB or 200 GB. Shenandoah is an algorithm for applications which require responsiveness and predictable short pauses. Additional resources For more information about the Shenandoah garbage collector, see Shenandoah GC in the Oracle OpenJDK documentation.

Commands:
Appendix G. Revision History Revision History Revision 9.1-3 Wed Oct 18 2017 Steven Levine Update to Version for 6.9. Revision 9.1-2 Tue Mar 7 2017 Steven Levine Version for 6.9 GA publication. Revision 9.1-1 Fri Dec 11 2016 Steven Levine Version for 6.9 Beta publication. Revision 8.1-10 Tue Apr 26 2016 Steven Levine Preparing document for 6.8 GA publication. Revision 8.1-5 Wed Mar 9 2016 Steven Levine Initial revision for Red Hat Enterprise Linux 6.8 Beta release Revision 7.1-12 Wed Jul 8 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Revision 7.1-10 Thu Apr 16 2015 Steven Levine Initial revision for Red Hat Enterprise Linux 6.7 Beta release Revision 7.0-13 Wed Oct 8 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Revision 7.0-11 Thu Aug 7 2014 Steven Levine Initial revision for Red Hat Enterprise Linux 6.6 Beta release Revision 6.0-21 Wed Nov 13 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.5 Revision 6.0-15 Fri Sep 27 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.5 Beta release Revision 5.0-25 Mon Feb 18 2013 Steven Levine Initial revision for Red Hat Enterprise Linux 6.4 Revision 5.0-16 Mon Nov 26 2012 Steven Levine Initial revision for Red Hat Enterprise Linux 6.4 Beta release Revision 4.0-5 Fri Jun 15 2012 Steven Levine Initial revision for Red Hat Enterprise Linux 6.3 Revision 3.0-5 Thu Dec 1 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.2 Revision 3.0-1 Wed Sep 28 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.2 Beta release Revision 2.0-1 Thu May 19 2011 Steven Levine Initial revision for Red Hat Enterprise Linux 6.1 Revision 1.0-1 Wed Nov 10 2010 Paul Kennedy Initial revision for the Red Hat Enterprise Linux 6 release

Commands: