mtpti5iD/redhat-docs_dataset huggingface dataset:
B.59. openldap B.59.1. RHSA-2011:0347 - Moderate: openldap security update Updated openldap packages that fix three security issues are now available for Red Hat Enterprise Linux 6. The Red Hat Security Response Team has rated this update as having moderate security impact. Common Vulnerability Scoring System (CVSS) base scores, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. OpenLDAP is an open source suite of LDAP (Lightweight Directory Access Protocol) applications and development tools. CVE-2011-1024 A flaw was found in the way OpenLDAP handled authentication failures being passed from an OpenLDAP slave to the master. If OpenLDAP was configured with a chain overlay and it forwarded authentication failures, OpenLDAP would bind to the directory as an anonymous user and return success, rather than return failure on the authenticated bind. This could allow a user on a system that uses LDAP for authentication to log into a directory-based account without knowing the password. CVE-2011-1025 It was found that the OpenLDAP back-ndb back end allowed successful authentication to the root distinguished name (DN) when any string was provided as a password. A remote user could use this flaw to access an OpenLDAP directory if they knew the value of the root DN. Note: This issue only affected OpenLDAP installations using the NDB back-end, which is only available for Red Hat Enterprise Linux 6 via third-party software. CVE-2011-1081 A flaw was found in the way OpenLDAP handled modify relative distinguished name (modrdn) requests. A remote, unauthenticated user could use this flaw to crash an OpenLDAP server via a modrdn request containing an empty old RDN value. Users of OpenLDAP should upgrade to these updated packages, which contain backported patches to resolve these issues. After installing this update, the OpenLDAP daemons will be restarted automatically.

Commands:
7.72. haproxy 7.72.1. RHBA-2015:1400 - haproxy bug fix and enhancement update Updated haproxy packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The haproxy packages provide a reliable, high-performance network load balancer for TCP and HTTP-based applications. Note The haproxy packages have been upgraded to upstream version 1.5.4, which provides a number of bug fixes and enhancements over the version. (BZ# 1136550 ) Enhancement BZ# 1166497 The OPTIONS parameter has been added to the /etc/sysconfig/haproxy file, which allows the user to set extra options for the haproxy utility. Users of haproxy are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
8.241. tomcat6 8.241.1. RHBA-2014:1618 - tomcat6 bug fix update Updated tomcat6 packages that fix one bug are now available for Red Hat Enterprise Linux 6. Apache Tomcat is a servlet container for the Java Servlet and JavaServer Pages (JSP) technologies. Bug Fix BZ# 1140855 Due to a bug in the tomcat6 packages, an attempt to install the ipa-server package with Domain Name System (DNS) failed because it was not possible to configure the Certification Authority (CA) instance. This update provides a patch to fix this bug and ipa-server can now be installed as expected. Users of tomcat6 are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 6. Web Administration Login The Web Administration interface is accessed on a client system using a compatible web browser. Procedure. Logging in the Web Administration interface Open the following URL in a web browser. Note Replace web-admin-server.example.com with the hostname or FQDN of the Web Administration server. The login page is displayed. Enter the default username admin and the default password adminuser , and click Log in . Figure 6.1. Login Page The Clusters interface is displayed after logging in to the Web Administration interface. This interface is the starting point to initiate a cluster import. Figure 6.2. Landing Page Note For instructions on how to import a Gluster cluster, see the import cluster chapter in the Red Hat Gluster Storage Web Administration Monitoring Guide .

Commands:
http://web-admin-server.example.com
16.14. Upgrading an Existing System Important The following sections only apply to upgrading Red Hat Enterprise Linux between minor versions, for example, upgrading Red Hat Enterprise Linux 6.4 to Red Hat Enterprise Linux 6.5 or higher. This approach is not supported for upgrades between major versions, for example, upgrading Red Hat Enterprise Linux 6 to Red Hat Enterprise Linux 7. In-place upgrades between major versions of Red Hat Enterprise Linux can be done, with certain limitations, using the Red Hat Upgrade Tool and Preupgrade Assistant tools. See Chapter 37, Upgrading Your Current System for more information. The installation system automatically detects any existing installation of Red Hat Enterprise Linux. The upgrade process updates the existing system software with new versions, but does not remove any data from users' home directories. The existing partition structure on your hard drives does not change. Your system configuration changes only if a package upgrade demands it. Most package upgrades do not change system configuration, but rather install an additional configuration file for you to examine later. Note that the installation medium that you are using might not contain all the software packages that you need to upgrade your computer. 16.14.1. The Upgrade Dialog If your system contains a Red Hat Enterprise Linux installation, a dialog appears asking whether you want to upgrade that installation. To perform an upgrade of an existing system, choose the appropriate installation from the drop-down list and select . Figure 16.35. The Upgrade Dialog Note Software you have installed manually on your existing Red Hat Enterprise Linux system may behave differently after an upgrade. You may need to manually reinstall or recompile this software after an upgrade to ensure it performs correctly on the updated system.

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. 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 allows for optional use of alternative package versions on Red Hat Enterprise Linux. By using the scl utility, users can pick and choose which package version they want to run at any time. Red Hat Developer Toolset is now a part of Red Hat Software Collections. It 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, Eclipse development platform, and other development, debugging, and performance monitoring tools. 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:
C.5. Debugging and Testing Services and Resource Ordering You can debug and test services and resource ordering with the rg_test utility. rg_test is a command-line utility provided by the rgmanager package that is run from a shell or a terminal (it is not available in Conga ). Table C.2, " rg_test Utility Summary" summarizes the actions and syntax for the rg_test utility. Table C.2. rg_test Utility Summary Action Syntax Display the resource rules that rg_test understands. rg_test rules Test a configuration (and /usr/share/cluster) for errors or redundant resource agents. rg_test test /etc/cluster/cluster.conf Display the start and stop ordering of a service. Display start order: rg_test noop /etc/cluster/cluster.conf start service servicename Display stop order: rg_test noop /etc/cluster/cluster.conf stop service servicename Explicitly start or stop a service. Important Only do this on one node, and always disable the service in rgmanager first. Start a service: rg_test test /etc/cluster/cluster.conf start service servicename Stop a service: rg_test test /etc/cluster/cluster.conf stop service servicename Calculate and display the resource tree delta between two cluster.conf files. rg_test delta cluster.conf file 1 cluster.conf file 2 For example: rg_test delta /etc/cluster/cluster.conf.bak /etc/cluster/cluster.conf

Commands:
Appendix A. Revision History Revision History Revision 1-6 Wed Feb 25 2015 Laura Bailey Rebuild for sort order. Revision 1-5 Wed Jan 21 2014 Elisla Slobodova Added the missing eCryptfs Technology Preview. Revision 1-4.6 Tue Jun 18 2013 Miroslav Svoboda Documented a new kernel erratum, RHSA-2013:1026. Revision 1-4.5 Tue Jun 18 2013 Eliska Slobodova Fixed broken links and links pointing to the old Product Documentation site. Revision 1-4.4 Thu Nov 1 2012 Eliska Slobodova Updated the initscripts known issue to provide a more detailed description of the problem. Revision 1-2 Tue Oct 2 2012 Martin Prpic Removed " KVM Live Snapshots " from the list of Technology Previews. This feature is only available via Red Hat Enterprise Virtualization 3.0. Revision 1-1 Wed May 20 2012 Martin Prpic Republished Technical Notes to update list of included advisories. For more information, refer to the Important note in the Package Updates chapter of this book. Revision 1-0 Tue Dec 6 2011 Martin Prpic Initial release of the Red Hat Enterprise Linux 6.2 Technical Notes.

Commands:
Chapter 6. Listing existing functions You can list existing functions. You can do it using the kn func tool. 6.1. Listing existing functions You can list existing functions by using kn func list . If you want to list functions that have been deployed as Knative services, you can also use kn service list . Procedure List existing functions: USD kn func list [-n <namespace> -p <path>] Example output NAME NAMESPACE RUNTIME URL READY example-function default node http://example-function.default.apps.ci-ln-g9f36hb-d5d6b.origin-ci-int-aws.dev.rhcloud.com True List functions deployed as Knative services: USD kn service list -n <namespace> Example output NAME URL LATEST AGE CONDITIONS READY REASON example-function http://example-function.default.apps.ci-ln-g9f36hb-d5d6b.origin-ci-int-aws.dev.rhcloud.com example-function-gzl4c 16m 3 OK / 3 True

Commands:
kn func list [-n <namespace> -p <path>]
NAME NAMESPACE RUNTIME URL READY example-function default node http://example-function.default.apps.ci-ln-g9f36hb-d5d6b.origin-ci-int-aws.dev.rhcloud.com True
kn service list -n <namespace>
NAME URL LATEST AGE CONDITIONS READY REASON example-function http://example-function.default.apps.ci-ln-g9f36hb-d5d6b.origin-ci-int-aws.dev.rhcloud.com example-function-gzl4c 16m 3 OK / 3 True
Chapter 1. Understanding Red Hat OpenStack Platform Red Hat OpenStack Platform (RHOSP) delivers an integrated foundation to create, deploy, and scale a secure and reliable public or private OpenStack cloud. RHOSP is packaged so that you can create private, public, or hybrid cloud platforms from your available physical hardware. RHOSP clouds include the following components: Fully distributed object storage Persistent block-level storage Virtual machine provisioning engine and image storage Authentication and authorization mechanisms Integrated networking Web browser-based interface accessible to users and administrators The RHOSP IaaS cloud is implemented by a collection of interacting services that control its computing, storage, and networking resources. You can manage the cloud with a web-based interface to control, provision, and automate RHOSP resources. Additionally, an extensive API controls the RHOSP infrastructure and this API is also available to end users of the cloud. 1.1. Advantages of using Red Hat OpenStack Platform You can use Red Hat OpenStack Platform to combine virtualization, networking, and storage based on your requirements. The following capabilities are some of the advantages of the Red Hat OpenStack Platform: You can create public, private, or hybrid clouds that you can scale up or down based on your requirements. You can deploy cloud-enabled workloads based on your needs. You can address customer demands in hours or minutes instead of weeks or days, without sacrificing security, performance, or budget. You can implement stability and agility for your cloud environments, using hybrid cloud management, monitoring, and reporting with Red Hat CloudForms. 1.2. Relationship between RDO and OpenStack Foundation OpenStack Foundation promotes the global development, distribution, and adoption of the OpenStack cloud operating system. The goal of the OpenStack Foundation is to serve developers, users, and the entire ecosystem globally by providing a set of shared resources to grow the footprint of public and private OpenStack clouds, enable technology vendors targeting the platform and assist developers to produce the best cloud software in the industry. RPM Distribution of OpenStack (RDO) is a free, community-supported distribution of the Red Hat version of OpenStack that runs on Red Hat Enterprise Linux (RHEL) and its derivatives, such as CentOS. RDO also makes the latest OpenStack development release available for Fedora. In addition to providing a set of software packages, RDO is a community of users of cloud computing platforms on Red Hat-based operating systems to get help and compare notes on running OpenStack. For enterprise-level support or information on partner certification, Red Hat offers Red Hat OpenStack Platform. For more information, see Red Hat OpenStack Platform .

Commands:
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 17 release of Eclipse Temurin, see OpenJDK 17.0.6 Released . New features and enhancements Review the following release notes to understand new features and feature enhancements included with the Eclipse Temurin 17.0.6 release: Enhanced BMP bounds By default, OpenJDK 17.0.6 disables loading a linked International Color Consortium (ICC) profile in a BMP image. You can enable this functionality by setting the new sun.imageio.bmp.enabledLinkedProfiles property to true . This property replaces the old sun.imageio.plugins.bmp.disableLinkedProfiles property See JDK-8295687 (JDK Bug System) . Improved banking of sounds Previously, the SoundbankReader implementation, com.sun.media.sound.JARSoundbankReader , downloaded a JAR soundbank from a URL. For OpenJDK 17.0.6, this behavior is now disabled by default. To re-enable the behavior, set the new system property jdk.sound.jarsoundbank to true . See JDK-8293742 (JDK Bug System) . Enhanced Datagram Transport Layer Security (DTLS) performance OpenJDK now exchanges DTLS cookies for all new and resumed handshake communications. To re-enable the release behavior, set the new system property jdk.tls.enableDtlsResumeCookie to false . See JDK-8287411 (JDK Bug System) . Added note for LoginModule implementation The OpenJDK 9 release changed the Set implementation, which holds principals and credentials, so that the implementation can reject null values. Any attempts to call add(null) , contains(null) , or remove(null) would throw a NullPointerException message. The OpenJDK 9 release did not update the logout() method in the LoginModule implementation to check for null values. These values could occur because of a failed login attempt, which can cause a logout() call to throw a NullPointerException message. The OpenJDK 17.0.6 release updates the LoginModule implementations to check for null values. Additionally, the release adds an implementation note to the specification that states the change also applies to third-party modules. The note advises developers of third-party modules to verify that a logout() method does not throw a NullPointerException message. See JDK-8015081 (JDK Bug System). See JDK-8282730 (JDK Bug System). Revised on 2024-05-03 15:35:53 UTC

Commands:
Configuring OpenShift Data Foundation for Regional-DR with Advanced Cluster Management Red Hat OpenShift Data Foundation 4.9 Instructions about setting up OpenShift Data Foundation between two different geographical locations for providing storage infrastructure with disaster recovery capabilities. Red Hat Storage Documentation Team Abstract The intent of this solution guide is to detail the steps necessary to deploy OpenShift Data Foundation for disaster recovery with Advanced Cluster Management to achieve a highly available storage infrastructure. Important Configuring OpenShift Data Foundation for Regional-DR with Advanced Cluster Management is a developer preview feature and is subject to developer preview support limitations. Developer preview releases are not intended to be run in production environments and are not supported through the Red Hat Customer Portal case management system. If you need assistance with developer preview features, reach out to the ocs-devpreview@redhat.com mailing list and a member of the Red Hat Development Team will assist you as quickly as possible based on their availability and work schedules.

Commands:
12.2.2. XFS No repair is performed automatically at boot time. To initiate a filesystem check or repair, the xfs_repair tool is used. Note Although an fsck.xfs binary is present in the xfsprogs package, this is present only to satisfy initscripts that look for an fsck. filesystem binary at boot time. fsck.xfs immediately exits with an exit code of 0. Another thing to be aware of is that older xfsprogs packages contain an xfs_check tool. This tool is very slow and does not scale well for large filesystems. As such, it has been depreciated in favor of xfs_repair -n . A clean log on a filesystem is required for xfs_repair to operate. If the filesystem was not cleanly unmounted, it should be mounted and unmounted prior to using xfs_repair . If the log is corrupt and cannot be replayed, the -L option may be used to zero the log. Important The -L option must only be used if the log cannot be replayed. The option discards all metadata updates in the log and will result in further inconsistencies. It is possible to run xfs_repair in a dry run, check-only mode by using the -n option. No changes will be made to the filesystem when this option is specified. xfs_repair takes very few options. Commonly used options include: -n No modify mode. Check-only operation. -L Zero metadata log. Use only if log cannot be replayed with mount. -m maxmem Limit memory used during run to maxmem MB. 0 can be specified to obtain a rough estimate of the minimum memory required. -l logdev Specify the external log device, if present. All options for xfs_repair are specified in the xfs_repair(8) manual page. The following eight basic phases are performed by xfs_repair while running: Inode and inode blockmap (addressing) checks. Inode allocation map checks. Inode size checks. Directory checks. Pathname checks. Link count checks. Freemap checks. Superblock checks. These phases, as well as messages printed during operation, are documented in depth in the xfs_repair(8) manual page. xfs_repair is not interactive. All operations are performed automatically with no input from the user. If it is desired to create a metadata image prior to repair for diagnostic or testing purposes, the xfs_metadump(8) and xfs_mdrestore(8) utilities may be used.

Commands:
Chapter 16. System and Subscription Management python-rhsm-debuginfo installed causes an upgrade failure When the user tries to upgrade to RHEL 6.10 while having the python-rhsm-debuginfo package installed, a transaction check error occurs due to a conflict with the subscription-manager-debuginfo package. As a consequence, the system upgrade fails, as well as an attempt to install or update subscription-manager-debuginfo . To work around this problem, uninstall the conflicting package by running yum remove python-rhsm-debuginfo before upgrading the system or before installing or updating subscription-manager-debuginfo . (BZ# 1581359 )

Commands:
Chapter 21. level The logging level from various sources, including rsyslog(severitytext property) , a Python logging module, and others. The following values come from syslog.h , and are preceded by their numeric equivalents : 0 = emerg , system is unusable. 1 = alert , action must be taken immediately. 2 = crit , critical conditions. 3 = err , error conditions. 4 = warn , warning conditions. 5 = notice , normal but significant condition. 6 = info , informational. 7 = debug , debug-level messages. The two following values are not part of syslog.h but are widely used: 8 = trace , trace-level messages, which are more verbose than debug messages. 9 = unknown , when the logging system gets a value it doesn't recognize. Map the log levels or priorities of other logging systems to their nearest match in the preceding list. For example, from python logging , you can match CRITICAL with crit , ERROR with err , and so on. Data type keyword Example value info

Commands:
Chapter 17. Managing bookmarks in GNOME In GNOME, you can edit the bookmarks that are displayed in applications and dialogs that manage files. 17.1. Bookmarks in GNOME Bookmarks integrate into GTK+ and in the GNOME desktop. Every application that presents a standard GTK+ Open and Save dialog ( GtkFileChooser ) lists bookmarks in the left panel of the dialog. Also, Files and its clones present bookmarks in a sidebar. Besides bookmarks, GtkFileChooser lists all other available GVFS volumes and mounts in the sidebar. While activating a bookmark for the first time, the GVFS subsystem looks for existing mounts and tries to mount the location if the mount does not exist yet. This way, you can authenticate even within the Open or Save dialog. Bookmarks are located in the ~/.config/gtk-3.0/bookmarks file. In the following example, the bookmarked locations are ~/Music , ~/Pictures , ~/Videos , ~/Downloads , and ~/bin , so the content of the ~/.config/gtk-3.0/bookmarks file looks as follows: Note Replace username with the user name you are logged in. You can use this file to edit bookmarks based on your requirements. 17.2. Adding a bookmark in Files You can save a reference to a location by bookmarking it. Procedure Select the folder or file you want to bookmark. Do one of the following: Press Ctrl + D or Drag and drop the file or folder to the sidebar. 17.3. Adding a bookmark for all users As a system administrator, you can set a bookmark for several users at once so that file shares are easily accessible to all the users. Procedure In the home directory of each existing user, edit the ~ user /.config/gtk-3.0/bookmarks file. In the file, add a Uniform Resource Identifiers (URI) line that identifies the bookmark. For example, the following lines add bookmarks to the /usr/share/doc/ directory and to the GNOME FTP network share: Optional: To also add the bookmarks for every newly created user on the system: Create the /etc/skel/.config/gtk-3.0/bookmarks file. Enter the bookmark URI lines in the file.

Commands:
file:///home/ username /Music file:///home/ username /Pictures file:///home/ username /Videos file:///home/ username /Downloads file:///home/ username /bin
file:///usr/share/doc/ ftp://ftp.gnome.org/