mtpti5iD/redhat-docs_dataset huggingface dataset:
4.8. Starting LVS To start LVS, it is best to have two root terminals open simultaneously or two simultaneous root open ssh sessions to the primary LVS router. In one terminal, watch the kernel log messages with the command: tail -f /var/log/messages Then start LVS by typing the following command into the other terminal: /sbin/service pulse start Follow the progress of the pulse service's startup in the terminal with the kernel log messages. When you see the following output, the pulse daemon has started properly: gratuitous lvs arps finished To stop watching /var/log/messages , type Ctrl + c . From this point on, the primary LVS router is also the active LVS router. While you can make requests to LVS at this point, you should start the backup LVS router before putting LVS into service. To do this, simply repeat the process described above on the backup LVS router node. After completing this final step, LVS will be up and running.

Commands:
Chapter 57. DeploymentTemplate schema reference Used in: CruiseControlTemplate , EntityOperatorTemplate , JmxTransTemplate , KafkaBridgeTemplate , KafkaConnectTemplate , KafkaExporterTemplate , KafkaMirrorMakerTemplate Full list of DeploymentTemplate schema properties Use deploymentStrategy to specify the strategy used to replace old pods with new ones when deployment configuration changes. Use one of the following values: RollingUpdate : Pods are restarted with zero downtime. Recreate : Pods are terminated before new ones are created. Using the Recreate deployment strategy has the advantage of not requiring spare resources, but the disadvantage is the application downtime. Example showing the deployment strategy set to Recreate . # ... template: deployment: deploymentStrategy: Recreate # ... This configuration change does not cause a rolling update. 57.1. DeploymentTemplate schema properties Property Property type Description metadata MetadataTemplate Metadata applied to the resource. deploymentStrategy string (one of [RollingUpdate, Recreate]) Pod replacement strategy for deployment configuration changes. Valid values are RollingUpdate and Recreate . Defaults to RollingUpdate .

Commands:
template: deployment: deploymentStrategy: Recreate
7.119. libsemanage 7.119.1. RHBA-2013:0465 - libsemanage bug fix update Updated libsemanage packages that fix two bugs are now available for Red Hat Enterprise Linux 6. The libsemanage library provides an API for the manipulation of SELinux binary policies. It is used by checkpolicy (the policy compiler) and similar tools, as well as by programs such as load_policy, which must perform specific transformations on binary policies (for example, customizing policy boolean settings). Bug Fixes BZ#798332 Previously, the "usepasswd" parameter was not available in the /etc/selinux/semanage.conf file. This update adds the missing "usepasswd" parameter to this file. BZ# 829378 When a custom SELinux policy module was loaded with an error, an error message that was not very informative was returned. This update fixes the error message to be more helpful for users. All users of libsemanage are advised to upgrade to these updated packages, which fix these bugs.

Commands:
probe::tcpmib.AttemptFails Name probe::tcpmib.AttemptFails - Count a failed attempt to open a socket Synopsis tcpmib.AttemptFails Values op value to be added to the counter (default value of 1) sk pointer to the struct sock being acted on Description The packet pointed to by skb is filtered by the function tcpmib_filter_key . If the packet passes the filter is is counted in the global AttemptFails (equivalent to SNMP's MIB TCP_MIB_ATTEMPTFAILS)

Commands:
4.3. Virtual Database Connection Type Once your VDB is deployed, you can configure a property in it called connection type . By setting this property, you can determine what type of connections can be made to the VDB. You can set it to one of the following: NONE : disallow new connections. BY_VERSION : (the default setting) allow connections only if the version is specified or if this is the earliest BY_VERSION VDB and there are no VDBs marked as ANY. ANY : allow connections with or without a version specified. If you only want to migrate a few of your applications to the new version of the VDB, then set it to BY_VERSION. This ensures that only applications that know of the new version may use it. If only a select few applications are to remain on the current VDB version, then you will need to update their connection settings to reference the current VDB by its version. The newly deployed VDB will then have its connection type set to ANY, which allows all new connections to be made against the newer version. If you need to undertake a rollback in this scenario, then the newly-deployed VDB will, accordingly, have its connection type set to NONE or BY_VERSION.

Commands:
Chapter 10. Logging 10.1. Configuring logging AMQ JavaScript uses the JavaScript debug module to implement logging. For example, to enable detailed client logging, set the DEBUG environment variable to rhea* : Example: Enabling detailed logging USD export DEBUG=rhea* USD <your-client-program> 10.2. Enabling protocol logging The client can log AMQP protocol frames to the console. This data is often critical when diagnosing problems. To enable protocol logging, set the DEBUG environment variable to rhea:frames : Example: Enabling protocol logging USD export DEBUG=rhea:frames USD <your-client-program>

Commands:
export DEBUG=rhea* <your-client-program>
export DEBUG=rhea:frames <your-client-program>
29.2. Editing the GRUB Configuration The GRUB boot loader uses the configuration file /boot/grub/grub.conf . To configure GRUB to boot from the new files, add a boot stanza to /boot/grub/grub.conf that refers to them. A minimal boot stanza looks like the following listing: You may wish to add options to the end of the kernel line of the boot stanza. These options set preliminary options in Anaconda which the user normally sets interactively. For a list of available installer boot options, refer to Chapter 28, Boot Options . The following options are generally useful for medialess installations: ip= repo= lang= keymap= ksdevice= (if installation requires an interface other than eth0) vnc and vncpassword= for a remote installation When you are finished, change the default option in /boot/grub/grub.conf to point to the new first stanza you added:

Commands:
title Installation root (hd0,0) kernel /vmlinuz-install initrd /initrd.img-install
default 0
8.168. ql2400-firmware 8.168.1. RHBA-2013:1707 - ql2400-firmware bug fix and enhancement update An updated ql2400-firmware package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The ql2400-firmware package provides the firmware required to run the QLogic 2400 Series of mass storage adapters. Note The ql2400-firmware package has been upgraded to upstream version 7.00.01, which provides a number of bug fixes and enhancements over the version. (BZ# 996752 ) All users of QLogic 2400 Series Fibre Channel adapters are advised to upgrade to this updated package, which fixes these bugs and adds these enhancements.

Commands:
8.9. biosdevname 8.9.1. RHBA-2013:1638 - biosdevname bug fix and enhancement update Updated biosdevname packages that fix several bugs and add various enhancements are now available for Red Hat Enterprise Linux 6. The biosdevname packages contain a udev helper utility which provides an optional convention for naming network interfaces; it assigns names to network interfaces based on their physical location. The utility is disabled by default, except for on a limited set of Dell PowerEdge, C Series and Precision Workstation systems. Note The biosdevname packages have been upgraded to upstream version 0.5.0, which provides a number of bug fixes and enhancements over the version. (BZ# 947841 ) Bug Fix BZ# 1000386 Previously, the addslot() function returned the same "dev->index_in_slot" value for two or more interfaces. As a consequence, more than one network interfaces could be named "renameN". This update restores the logic used to obtain a port number that existed in biosdevname version 0.3.11 and, as a result, all interfaces are named as expected. Users of biosdevname are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
14.6. Using Persistent Search A persistent search is an ldapsearch which remains open even after the initial search results are returned. Important The OpenLDAP client tools with Red Hat Enterprise Linux do not support persistent searches. The server itself, however, does. Other LDAP clients must be used to perform persistent searches. The purpose of a persistent search is to provide a continuous list of changes to the directory entries as well as the complete entries themselves, something like a hybrid search and changelog. Therefore, the search command must specify what entries to return (the search parameters) and what changes cause an entry to be returned (entry change parameters). Persistent searches are especially useful for applications or clients which access the Directory Server and provide two important benefits: Keep a consistent and current local cache. Any client will query local cache before trying to connect to and query the directory. Persistent searches provide the local cache necessary to improve performance for these clients. Automatically initiate directory actions. The persistent cache can be automatically updated as entries are modified, and the persistent search results can display what kind of modification was performed on the entry. Another application can use that output to update entries automatically, such as automatically creating an email account on a mail server for new users or generating a unique user ID number. There are some performance considerations when running persistent searches, as well: The ldapsearch does not send a notification when the client disconnects, and the change notifications are not sent for any changes made while the search is disconnected. This means that the client's cache will not be updated if it is ever disconnected and there is no good way to update the cache with any new, modified, or deleted entries that were changed while it was disconnected. An attacker could open a large number of persistent searches to launch a denial of service attack. A persistent search requires leaving open a TCP connection between the Directory Server and client. This should only be done if the server is configured to allow a lot of client connections and has a way to close idle connections. In the access logs, a persistent search is identified with the tag options=persistent .

Commands:
[12/Jan/2009:12:51:54.899423510 -0500] conn=19636710736396323 op=0 SRCH base="dc=example,dc=com" scope=2 filter="(objectClass=person)" attrs=ALL options=persistent
Part III. Setting up the subscriptions service for data collection To set up the environment for the subscriptions service data collection, connect your Red Hat Enterprise Linux, Red Hat OpenShift, and Red Hat Ansible systems to the Hybrid Cloud Console services through one or more data collection tools. After you complete the steps to set up this environment, you can continue with the steps to activate and open the subscriptions service. Do these steps To gather Red Hat Enterprise Linux usage data, complete at least one of the following steps to connect your Red Hat Enterprise Linux systems to the Hybrid Cloud Console by enabling a data collection tool. This connection enables subscription usage data to show in the subscriptions service. Deploy Insights on every RHEL system that is managed by Red Hat Satellite: Deploying Red Hat Insights Ensure that Satellite is configured to manage your RHEL systems and install the Satellite inventory upload plugin: Installing the Satellite inventory upload plugin Ensure that Red Hat Subscription Management is configured to manage your RHEL systems: Registering systems to Red Hat Subscription Management For pay-as-you-go On-Demand subscriptions for metered RHEL, ensure that a cloud integration is configured in the Hybrid Cloud Console for collection of the metering data. Connecting cloud integrations to the subscriptions service To gather Red Hat OpenShift usage data, complete the following step for Red Hat OpenShift data collection on the Hybrid Cloud Console. Set up the connection between Red Hat OpenShift and the subscriptions service based upon the operating system that is used for clusters: Connecting Red Hat OpenShift to the subscriptions service To gather Red Hat Ansible usage data, no additional setup steps are necessary. Ansible data collection is configured automatically during the provisioning of the Ansible control plane.

Commands:
F.2. File Menu The File menu provides actions to manage your workspace resources. Figure F.2. File Menu The New > submenu provides specific actions to create various generic workspace resources as well as Teiid Designer models and VDBs. Figure F.3. File Menu The File menu contains the following actions: New > Model Project - Create user a new model project. New > Folder - Create new folder within an existing project or folder. New > Model - Create a new model of a specified model type and class using the New Model Wizards. New > Virtual Database Definition - Create a new VDB, or Virtual Database Definition. Open File - Enables you to open a file for editing - including files that do not reside in the Workspace. Close (Ctrl+W) - Closes the active editor. You are prompted to save changes before the file closes. Close All (Shift+Ctrl+W) - Closes all open editors. You are prompted to save changes before the files close. Save (Ctrl+S) - Saves the contents of the active editor. Save As - Enables you to save the contents of the active editor under another file name or location. Save All (Shift+Ctrl+S) - Saves the contents of all open editors. Move - Launches a Refactor > Move resource dialog.. Rename (F2) - Launches a Refactor > Rename resource dialog if resource selected, else inline rename is preformed. Refresh - Refreshes the resource with the contents in the file system. Convert Line Delimiters To - Alters the line delimiters for the selected files. Changes are immediate and persist until you change the delimiter again - you do not need to save the file. Print (Ctrl+P) - Prints the contents of the active editor. In the Teiid Designer, this action prints the diagram in the selected editor. Allows control over orientation (portrait or landscape), scaling, margins and page order. User can also specify a subset of the pages to print (i.e., 2 through 8). Switch Workspace - Opens the Workspace Launcher, from which you can switch to a different workspace. This restarts the Workbench. Restart - Exits and restarts the Workbench. --> Import - Launches the Import Wizard which provides several ways to construct or import models.. Export - Launches the Export Wizard which provides options for exporting model data. Properties (Alt+Enter) - Opens the Properties dialog for the currently selected resource. These will include path to the resource on the file system, date of last modification and its writable or executable state. Most Recent Files List - Contains a list of the most recently accessed files in the Workbench. You can open any of these files from the File menu by selecting the file name. Exit - Closes and exits the Workbench.

Commands:
7.121. man-pages-fr 7.121.1. RHBA-2015:0667 - man-pages-fr bug fix update An updated man-pages-fr package that fixes one bug is now available for Red Hat Enterprise Linux 6. The man-pages-fr package contains a collection of manual pages translated into French. Bug Fix BZ# 1135541 The French version of the "du" man page does not contain an up-to-date list of "du" options and their descriptions. Because the man page is no longer maintained, this update adds a message at the top of the page stating that the documentation is outdated, and that users can find the latest version in the English man page. Users of man-pages-fr are advised to upgrade to this updated package, which fixes this bug.

Commands:
Chapter 6. Using the survey editor When ordering a product in automation services catalog, users may be required to provide additional information to complete the request. This prompt is created by a survey associated with the product. Initially created and edited in Ansible Tower, Catalog Administrators and portfolio users with update permissions can edit the survey in automation services catalog. Once submitted and validated, the surveys pass user-submitted extra variables to the job or workflow template run on Ansible Tower on the execution of an order. See Surveys in the Ansible Tower User Guide to learn more creating and editing surveys for job templates. Using the survey properties editor, you can: Set labels, helper text or placeholders to enhance the user experience of users providing information Further restrict existing validation parameters. Change validation messages. Hide, disable or set to read-only chosen fields in the survey. 6.1. Survey properties editor Values for surveys are defined in Ansible Tower and the automation services catalog properties editor allows Catalog Administrators to restrict survey options, such as adjusting default values and removing items from drop-down menus. Additionally, use the properties editor to hide, disable, or set a field to read only. Note Provide an initial value for any required field set to Hidden or Disabled. This includes read only fields. 6.2. Editing surveys You can edit fields in the surveys from the product detail view. Edit each field individually using the Properties editor. Prerequisites The product has an associated survey, created in Ansible Tower. Procedure Click Products . Locate the product and click on its title. Click and select Edit survey . Select a field in the survey. The Properties editor will appear. Click Properties to view the elements to edit for that field. Select Validation to configure the validator types used to validate user input. Click Save when finished.

Commands:
5.296. seabios 5.296.1. RHBA-2012:0802 - seabios bug fix and enhancement update Updated seabios packages that fix several bugs and add multiple enhancements are now available for Red Hat Enterprise Linux 6. The seabios package contains a legacy BIOS implementation, which can be used as a coreboot payload. Bug Fixes BZ# 757999 Previously, SeaBIOS sometimes booted from an incorrect drive. This happened because the QEMU hard-drive priority was lower than the virtio block-device priority. With this update, the QEMU hard-drive priority has been raised above the virtio block-device priority and SeaBIOS now boots from the correct drive. BZ# 771946 Previously, a guest could remain unresponsive during boot after the S3 (Suspend to RAM) state as SeaBIOS failed to advertise to the guest's operating system that the device was powered down. With this update, the underlying code handling the block device resume has been fixed and the problem no longer occurs. BZ# 786142 Previously, a Windows guest could detect an HPET (High Precision Event Timer) device although the guest had the HPET device disabled. This occurred because the HPET device was defined in the DSDT (Differentiated System Description Table). This update removes the definition from the table and the problem no longer occurs. BZ# 801293 Booting from some USB flash drives could fail because SeaBIOS did not support recovery from USB STALL conditions. This update adds support for recovery from STALLs. BZ# 804933 RTC (Real-Time Clock) wake-up for Windows guest did not work. With this update, the underlying code of FADT (Fixed ACPI Description Table) has been fixed to match QEMU behavior and the problem no longer occurs. BZ# 808033 Previously, if a device was hot plugged while the guest was still processing a hot-plug event, the new hot-plug event failed to be processed and the device was not detected. With this update, SeaBIOS uses a different event to handle hotplugging and the problem no longer occurs. BZ# 810471 Guest booting could fail if the guest had more than 62 sockets and multiple virtio disk devices. This happened because, BIOS ran out of memory and failed to initialize the boot disk. With this update, new memory is allocated under these circumstances and booting succeeds. Enhancements BZ# 809797 The in-guest S4 (Suspend-to-Disk) and S3 (Suspend-to-RAM) power management features were added as a Technology Preview. The features provide the ability to perform suspend-to-disk and suspend-to-RAM functions on the guest. To enable the feature, users have to choose the /usr/share/seabios/bios-pm.bin file for VM BIOS instead of the default /usr/share/seabios/bios.bin file through libvirt. BZ# 782028 SeaBIOS now supports booting from virtio-scsi devices. More information about Red Hat Technology Previews is available here: https://access.redhat.com/support/offerings/techpreview/ All seabios users are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
probe::signal.send.return Name probe::signal.send.return - Signal being sent to a process completed Synopsis Values retstr The return value to either __group_send_sig_info, specific_send_sig_info, or send_sigqueue send2queue Indicates whether the sent signal was sent to an existing sigqueue name The name of the function used to send out the signal shared Indicates whether the sent signal is shared by the thread group. Context The signal's sender. (correct?) Description Possible __group_send_sig_info and specific_send_sig_info return values are as follows; 0 -- The signal is sucessfully sent to a process, which means that (1) the signal was ignored by the receiving process, (2) this is a non-RT signal and the system already has one queued, and (3) the signal was successfully added to the sigqueue of the receiving process. -EAGAIN -- The sigqueue of the receiving process is overflowing, the signal was RT, and the signal was sent by a user using something other than kill . Possible send_group_sigqueue and send_sigqueue return values are as follows; 0 -- The signal was either sucessfully added into the sigqueue of the receiving process, or a SI_TIMER entry is already queued (in which case, the overrun count will be simply incremented). 1 -- The signal was ignored by the receiving process. -1 -- (send_sigqueue only) The task was marked exiting, allowing * posix_timer_event to redirect it to the group leader.

Commands:
signal.send.return
Chapter 2. General Updates Users with any UID are now able to log in after the update to RHEL 7 Since Red Hat Enterprise Linux 7.3, the default value of the first_valid_uid configuration option of Dovecot changed from 500 in Red Hat Enterprise Linux 6 to 1000 in Red Hat Enterprise Linux 7. Consequently, if a Red Hat Enterprise Linux 6 installation did not have first_valid_uid explicitly defined, the Dovecot configuration did not allow users with UID less than 1000 to log in after the update to Red Hat Enterprise Linux 7. Note that only installations where first_valid_uid was not explicitly defined were affected. This problem has been addressed by the post-upgrade script, which now changes the first_valid_uid value from 1000 to the original value on the source system. As a result, users with any UID are able to log in after the update to Red Hat Enterprise Linux 7. (BZ# 1388967 )

Commands: