mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Publishing applications with .NET 9.0 .NET 9.0 applications can be published to use a shared system-wide version of .NET or to include .NET. The following methods exist for publishing .NET 9.0 applications: Self-contained deployment (SCD) - The application includes .NET. This method uses a runtime built by Microsoft. Framework-dependent deployment (FDD) - The application uses a shared system-wide version of .NET. Note When publishing an application for RHEL, Red Hat recommends using FDD, because it ensures that the application is using an up-to-date version of .NET, built by Red Hat, that uses a set of native dependencies. Prerequisites Existing .NET application. For more information about how to create a .NET application, see Creating an application using .NET . 4.1. Publishing .NET applications The following procedure outlines how to publish a framework-dependent application. Procedure Publish the framework-dependent application: Replace my-app with the name of the application you want to publish. Optional: If the application is for RHEL only, trim out the dependencies needed for other platforms: Replace architecture based on the platform you are using: For Intel: x64 For IBM Z and LinuxONE: s390x For 64-bit Arm: arm64 For IBM Power: ppc64le

Commands:
dotnet publish my-app -f net9.0
dotnet publish my-app -f net9.0 -r rhel.9- architecture --self-contained false
4.7. Adding Journals to a File System The gfs2_jadd command is used to add journals to a GFS2 file system. You can add journals to a GFS2 file system dynamically at any point without expanding the underlying logical volume. The gfs2_jadd command must be run on a mounted file system, but it needs to be run on only one node in the cluster. All the other nodes sense that the expansion has occurred. Note If a GFS2 file system is full, the gfs2_jadd will fail, even if the logical volume containing the file system has been extended and is larger than the file system. This is because in a GFS2 file system, journals are plain files rather than embedded metadata, so simply extending the underlying logical volume will not provide space for the journals. Before adding journals to a GFS file system, you can use the journals option of the gfs2_tool to find out how many journals the GFS2 file system currently contains. The following example displays the number and size of the journals in the file system mounted at /mnt/gfs2 . Usage Number Specifies the number of new journals to be added. MountPoint Specifies the directory where the GFS2 file system is mounted. Examples In this example, one journal is added to the file system on the /mygfs2 directory. In this example, two journals are added to the file system on the /mygfs2 directory. Complete Usage MountPoint Specifies the directory where the GFS2 file system is mounted. Device Specifies the device node of the file system. Table 4.4, "GFS2-specific Options Available When Adding Journals" describes the GFS2-specific options that can be used when adding journals to a GFS2 file system. Table 4.4. GFS2-specific Options Available When Adding Journals Flag Parameter Description -h Help. Displays short usage message. -J MegaBytes Specifies the size of the new journals in megabytes. Default journal size is 128 megabytes. The minimum size is 32 megabytes. To add journals of different sizes to the file system, the gfs2_jadd command must be run for each size journal. The size specified is rounded down so that it is a multiple of the journal-segment size that was specified when the file system was created. -j Number Specifies the number of new journals to be added by the gfs2_jadd command. The default value is 1. -q Quiet. Turns down the verbosity level. -V Displays command version information.

Commands:
gfs2_tool journals /mnt/gfs2 journal2 - 128MB journal1 - 128MB journal0 - 128MB 3 journal(s) found.
gfs2_jadd -j Number MountPoint
gfs2_jadd -j1 /mygfs2
gfs2_jadd -j2 /mygfs2
gfs2_jadd [ Options ] { MountPoint | Device } [ MountPoint | Device ]
7.270. virt-who 7.270.1. RHBA-2013:0374 - virt-who bug fix and enhancement update Updated virt-who packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The virt-who packages provide an agent that collects information about virtual guests present in the system and reports them to the Red Hat Subscription Manager tool. Bug Fixes BZ# 825215 Previously, when running the virt-who service, unregistering a Red Hat Enterprise Virtualization Hypervisor host from the Subscription Asset Manager (SAM) server caused the service to be terminated with the following message: Only the last line of the aforementioned message should have been displayed. This bug has been fixed, and the traceback errors are now saved to the log file and not printed on the screen. BZ# 866890 When a snapshot of a virtual machine (VM) was created in Microsoft Hyper-V Server, the virt-who agent replaced the UUID of the VM file with the UUID of the snapshot. This bug has been fixed, and the UUID is not changed in the described case. Additionally, in certain cases, the virt-who agent running with the "--hyperv" command-line option terminated with the following message: This bug has been fixed and the aforementioned error no longer occurs. BZ# 869960 Previously, the virt-who agent failed to function correctly when a URL, which was set in the VIRTWHO_ESX_SERVER parameter, was missing the initial "https://" string. With this update, virt-who has been modified, and "https://" is no longer required in VIRTWHO_ESX_SERVER. Enhancements BZ# 808060 With this update, the virt-who agent has been modified to start as a foreground process and to print error messages or debugging output (the "-d" command-line option) to the standard error output. Moreover, the following command-line options have been enhanced: the "-o" option provides the one-shot mode and exits after sending the list of guests; the "-b" option and the "service virt-who start" command equivalently start on the background and send data to the /var/log/ directory. BZ# 846788 The virt-who agent has been modified to support Red Hat Enterprise Virtualization Manager polling. BZ#860854 With this update, the virt-who agent has been modified to correctly recognize guest virtual machines, which are installed on top of Microsoft Hyper-V Server. BZ# 868149 The virt-who manual pages and the output of the "virt-who --help" command have been enhanced with clarifying information. In addition, a typographical error has been corrected in both texts. All users of virt-who are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
SubscriptionManagerError: No such file or directory Error in communication with candlepin, trying to recover Unable to read certificate, system is not registered or you are not root
AttributeError: HyperV instance has no attribute 'ping'
Chapter 5. Converting physical machines to virtual machines Warning The Red Hat Enterprise Linux 6 version of the virt-v2v utility has been deprecated. Users of Red Hat Enterprise Linux 6 are advised to create a Red Hat Enterprise 7 virtual machine, and install virt-v2v in that virtual machine. The Red Hat Enterprise Linux 7 version is fully supported and documented in virt-v2v Knowledgebase articles . Read this chapter for information about converting physical machines to virtual machines with the Red Hat Physical-to-Virtual (P2V) solution, Virt P2V. Virt P2V is comprised of both virt-p2v-server , included in the virt-v2v package, and the P2V client, available from the Red Hat Customer Portal as rhel-6.x-p2v.iso . rhel-6.x-p2v.iso is a bootable disk image based on a customized Red Hat Enterprise Linux 6 image. Booting a machine from rhel-6.x-p2v.iso and connecting to a V2V conversion server that has virt-v2v installed allows data from the physical machine to be uploaded to the conversion server and converted for use with either Red Hat Enterprise Virtualization, or KVM managed by libvirt . Note that the host must be running Red Hat Enterprise Linux 6. Other host configurations will not work. Important Adhere to the following rules. Failure to do so may cause the loss of data and disk malfunction: The Physical to Virtual (P2V) feature requires a Red Hat Enterprise Linux 6 virtualization host with virt-v2v version 0.8.7 or later. You can check your version of virt-v2v by running USD rpm -q virt-v2v . Note that you cannot convert to a Red Hat Enterprise Linux 5 conversion server, or with a virt-v2v package to version 0.8.7-6.el6. A number of operating systems can be converted from physical machines to virtual machines, but be aware that there are known issues converting physical machines using software RAID. Red Hat Enterprise Linux 6 machines with a filesystem root on a software RAID md device may be converted to guest virtual machines. Red Hat Enterprise Linux 4 and Red Hat Enterprise Linux 5 physical machines with their filesystem root on a software RAID md device cannot be converted to virtual machines. There is currently no workaround available. 5.1. Prerequisites For a physical machine to be converted using the P2V client, it must meet basic hardware requirements in order to successfully boot the P2V client: Must be bootable from PXE, Optical Media (CD, DVD), or USB. At least 512 MB of RAM. An ethernet connection. Console access (keyboard, video, mouse). An operating system supported by virt-v2v : Red Hat Enterprise Linux 3.9 Red Hat Enterprise Linux 4 Red Hat Enterprise Linux 5 Red Hat Enterprise Linux 6 Windows XP Windows Vista Windows 7 Windows Server 2003 Windows Server 2008

Commands:
18.3. Testing the camel-jbossdatagrid-fuse Quickstart To test the local_cache_producer create a CSV file in the incomingFolderPath , previously specified. The following command will generate a file with a single entry: Once the file has been removed from the directory then the producer has successfully parsed the file. Proceed to testing the consumer. To test the local_cache_consumer navigate to http://127.0.0.1:8282/cache/get/1 in a web browser. This will query the cache for the entry with an Id of 1 , which was specified above. The following JSON of the created POJO should be returned: Report a bug

Commands:
echo "1,Bill,Gates,59" > USDincomingFolderPath/sample.csv
id: 1
firstName: Bill
lastName: Gates
age: 59
4.134. libgpg-error 4.134.1. RHBA-2011:1717 - libgpg-error enhancement update An updated libgpg-error package is now available for Red Hat Enterprise Linux 6. The libgpg-error library provides a set of common error codes and definitions which are shared by the gnupg, libgcrypt and other packages. Enhancement BZ# 727287 Previously, the libgpg-error package was compiled without the RELRO (read-only relocations) flag. Programs provided by this package were thus vulnerable to various attacks based on overwriting the ELF section of a program. To increase the security of the libgpg-error library, the libgpg-error spec file has been modified to use the "-Wl,-z,relro" flags when compiling the package. As a result, the libgpg-error package is now provided with partial RELRO protection. Users of libgpg-error are advised to upgrade to this updated package, which adds this enhancement.

Commands:
4.295. shadow-utils 4.295.1. RHBA-2011:1650 - shadow-utils bug fix and enhancement update An updated shadow-utils package that fixes multiple bugs and adds three enhancements is now available for Red Hat Enterprise Linux 6. The shadow-utils package includes programs for converting UNIX password files to the shadow password format, as well as tools for managing user and group accounts. Bug Fixes BZ# 586796 Previously, the extended access control lists (ACL) on a file or directory below the /etc/skel directory were not preserved when a new user was created. As a result, the file or directory was copied but the extended ACLs that were associated with the file or directory were lost. This update preserves these extended ACLs. BZ# 667593 Previously,the switch-group (sg) command failed with a segmentation fault when using password protected groups. This update modifies the gshadow functions in shadow-utils and also uses the gshadow functions from glibc so that the sg command now handles password protected groups as expected. BZ# 672510 Previously, the new group (newgrp) command failed with a segmentation fault when using password protected groups. This update modifies the newgrp command so that the newgrp command now handles password protected groups as expected. BZ# 674878 , BZ# 696213 Previously, the man page for the useradd command contained misleading information about the -m option. The -m option is described correctly. BZ# 693377 Previously, the useradd command failed with a segmentation fault when the user ID (UID) range exceeded the maximum of 2147483647 (UID_MAX) accounts on a 64bit system. This update replaces the alloca() function with the malloc() function and checks the return value. Now, the useradd command operates in this range as expected. BZ# 706321 Previously, the lastlog command did not work correctly with large UIDs on 32bit system due to integer overflow. As a result, lastlog showed only users that were logged in. This update modifies the code so that lastlog now shows also users that were never logged in. Enhancements BZ# 723921 This update is compiled with the position-independent executable (PIE) and relocation read-only (RELRO) flags which enhance the security of the system. BZ# 639900 With this update, the userdel command offers the option to delete both from the SELinux login mapping. BZ# 629277 , BZ# 696213 This update adds additional comments in "/etc/login.defs". These comments inform the administrator that certain configuration options are ignored in favor of the pam-cracklib module. All users of shadow-utils are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
10.7. Adding Modules The Apache HTTP Server supports Dynamically Shared Objects ( DSO s), or modules, which can easily be loaded at runtime as necessary. The Apache Project provides complete DSO documentation online at http://httpd.apache.org/docs-2.0/dso.html . Or, if the http-manual package is installed, documentation about DSOs can be found online at http://localhost/manual/mod/ . For the Apache HTTP Server to use a DSO, it must be specified in a LoadModule directive within /etc/httpd/conf/httpd.conf . If the module is provided by a separate package, the line must appear within the modules configuration file in the /etc/httpd/conf.d/ directory. Refer to Section 10.5.12, " LoadModule " for more information. If adding or deleting modules from http.conf , Apache HTTP Server must be reloaded or restarted, as referred to in Section 10.4, "Starting and Stopping httpd " . If creating a new module, first install the httpd-devel package which contains the include files, the header files, as well as the APache eXtenSion ( /usr/sbin/apxs ) application, which uses the include files and the header files to compile DSOs. After writing a module, use /usr/sbin/apxs to compile the module sources outside the Apache source tree. For more information about using the /usr/sbin/apxs command, refer to the the Apache documentation online at http://httpd.apache.org/docs-2.0/dso.html as well as the apxs man page. Once compiled, put the module in the /usr/lib/httpd/modules/ directory. Then add a LoadModule line to the httpd.conf , using the following structure: Where <module-name> is the name of the module and <path/to/module.so> is the path to the DSO.

Commands:
LoadModule <module-name> <path/to/module.so>
Deploying OpenShift Data Foundation using IBM Z Red Hat OpenShift Data Foundation 4.15 Instructions on deploying Red Hat OpenShift Data Foundation to use local storage on IBM Z Red Hat Storage Documentation Team Abstract Read this document for instructions about how to install Red Hat OpenShift Data Foundation to use local storage on IBM Z. Note While this document refers only to IBM Z, all information in it also applies to IBM(R) LinuxONE.

Commands:
1.4. We Need Feedback! If you find a typographical error in this manual, or if you have thought of a way to make this manual better, we would love to hear from you! Please submit a report in Bugzilla: http://bugzilla.redhat.com/ against the product Red Hat Enterprise Linux 6 and the component doc-Logical_Volume_Manager . When submitting a bug report, be sure to mention the manual's identifier: If you have a suggestion for improving the documentation, try to be as specific as possible when describing it. If you have found an error, include the section number and some of the surrounding text so we can find it easily.

Commands:
Logical_Volume_Manager_Administration(EN)-6 (2017-3-8-15:20)
Chapter 11. Supplementary Client Variant The following table lists all the packages in the Supplementary Client variant. For more information about support scope, see the Scope of Coverage Details document. Package Core Package? License acroread No Commercial acroread-plugin No Commercial chromium-browser No BSD and LGPLv2+ flash-plugin No Commercial java-1.5.0-ibm No IBM Binary Code License java-1.5.0-ibm-demo No IBM Binary Code License java-1.5.0-ibm-devel No IBM Binary Code License java-1.5.0-ibm-javacomm No IBM Binary Code License java-1.5.0-ibm-jdbc No IBM Binary Code License java-1.5.0-ibm-plugin No IBM Binary Code License java-1.5.0-ibm-src No IBM Binary Code License java-1.6.0-ibm No IBM Binary Code License java-1.6.0-ibm-demo No IBM Binary Code License java-1.6.0-ibm-devel No IBM Binary Code License java-1.6.0-ibm-javacomm No IBM Binary Code License java-1.6.0-ibm-jdbc No IBM Binary Code License java-1.6.0-ibm-plugin No IBM Binary Code License java-1.6.0-ibm-src No IBM Binary Code License java-1.7.1-ibm No IBM Binary Code License java-1.7.1-ibm-demo No IBM Binary Code License java-1.7.1-ibm-devel No IBM Binary Code License java-1.7.1-ibm-jdbc No IBM Binary Code License java-1.7.1-ibm-plugin No IBM Binary Code License java-1.7.1-ibm-src No IBM Binary Code License java-1.8.0-ibm No IBM Binary Code License java-1.8.0-ibm-demo No IBM Binary Code License java-1.8.0-ibm-devel No IBM Binary Code License java-1.8.0-ibm-jdbc No IBM Binary Code License java-1.8.0-ibm-plugin No IBM Binary Code License java-1.8.0-ibm-src No IBM Binary Code License kmod-kspiceusb-rhel60 No GPLv2 spice-usb-share No Redistributable, no modification permitted system-switch-java No GPLv2+ virtio-win No Red Hat Proprietary and GPLv2

Commands:
7.36. cvs 7.36.1. RHBA-2012:1302 - cvs bug fix update An updated cvs package that fixes two bugs is now available for Red Hat Enterprise Linux 6. [Update 19 November 2012] The file list of this advisory was updated to move the new cvs-inetd package from the base repository to the optional repository in the Client and HPC Node variants. No changes have been made to the packages themselves. The Concurrent Versions System (CVS) is a version control system that can record the history of your files. CVS only stores the differences between versions, instead of every version of every file you have ever created. CVS also keeps a log of who, when, and why changes occurred. BZ# 671145 Prior to this update, the C shell (csh) did not set the CVS_RSH environment variable to "ssh" and the remote shell (rsh) was used instead when the users accessed a remote CVS server. As a consequence, the connection was vulnerable to attacks because the remote shell is not encrypted or not necessarily enabled on every remote server. The cvs.csh script now uses valid csh syntax and the CVS_RSH environment variable is properly set at log-in. BZ# 695719 Prior to this update, the xinetd package was not a dependency of the cvs package. As a result, the CVS server was not accessible through network. With this update, the cvs-inetd package, which contains the CVS inetd configuration file, ensures that the xinetd package is installed as a dependency and the xinetd daemon is available on the system. All users of cvs are advised to upgrade to these updated packages, which fix these bugs.

Commands:
Chapter 18. Red Hat Software Collections Red Hat Software Collections is a Red Hat content set that provides a set of dynamic programming languages, database servers, and related packages that you can install and use on all supported releases of Red Hat Enterprise Linux 6 and Red Hat Enterprise Linux 7 on AMD64 and Intel 64 architectures. Red Hat Developer Toolset is included as a separate Software Collection. Red Hat Developer Toolset is designed for developers working on the Red Hat Enterprise Linux platform. It provides current versions of the GNU Compiler Collection, GNU Debugger, and other development, debugging, and performance monitoring tools. Since Red Hat Software Collections 2.3, the Eclipse development platform is provided as a separate Software Collection. Dynamic languages, database servers, and other tools distributed with Red Hat Software Collections do not replace the default system tools provided with Red Hat Enterprise Linux, nor are they used in preference to these tools. Red Hat Software Collections uses an alternative packaging mechanism based on the scl utility to provide a parallel set of packages. This set enables optional use of alternative package versions on Red Hat Enterprise Linux. By using the scl utility, users can choose which package version they want to run at any time. Important Red Hat Software Collections has a shorter life cycle and support term than Red Hat Enterprise Linux. For more information, see the Red Hat Software Collections Product Life Cycle . See the Red Hat Software Collections documentation for the components included in the set, system requirements, known problems, usage, and specifics of individual Software Collections. See the Red Hat Developer Toolset documentation for more information about the components included in this Software Collection, installation, usage, known problems, and more.

Commands: