mtpti5iD/redhat-docs_dataset huggingface dataset:
Chapter 4. Role-based access reference The operations that an authenticated user is allowed to perform depend on the role (or roles) assigned to that user, as listed in Table 4.1, "Role-based access on Karaf standalone" . Table 4.1. Role-based access on Karaf standalone Operation admin manager viewer Log in/Log out Y Y Y View Help topics Y Y Y Set user preferences Y Y Y Connect Discover and connect to remote integrations Y Y Y Discover and connect to local integrations Y Y Y Camel View all running Camel applications Y Y Y Start, suspend, resume, and delete Camel contexts Y Y Send messages Y Y Add endpoints Y Y View routes, route diagrams, and runtime statistics Y Y Y Start and stop routes Y Y Delete routes Y Y JMX Change attribute values Y Y Select and view attributes in a time-based chart Y Y Y View operations Y Y Y OSGI View bundles, features, packages, services, servers, framework, and configurations Y Y Y Add and delete bundles Y Y Add configurations Y Y Install and uninstall features Y Runtime View system properties, metrics, and threads Y Y Y Logs View logs Y Y Y Additional resources For more information on role-based access control, see Deploying into Apache Karaf .

Commands:
23.3. I/O Standards This section describes I/O standards used by ATA and SCSI devices. ATA ATA devices must report appropriate information via the IDENTIFY DEVICE command. ATA devices only report I/O parameters for physical_block_size , logical_block_size , and alignment_offset . The additional I/O hints are outside the scope of the ATA Command Set. SCSI I/O parameters support in Red Hat Enterprise Linux 7 requires at least version 3 of the SCSI Primary Commands (SPC-3) protocol. The kernel will only send an extended inquiry (which gains access to the BLOCK LIMITS VPD page) and READ CAPACITY(16) command to devices which claim compliance with SPC-3. The READ CAPACITY(16) command provides the block sizes and alignment offset: LOGICAL BLOCK LENGTH IN BYTES is used to derive /sys/block/ disk /queue/physical_block_size LOGICAL BLOCKS PER PHYSICAL BLOCK EXPONENT is used to derive /sys/block/ disk /queue/logical_block_size LOWEST ALIGNED LOGICAL BLOCK ADDRESS is used to derive: /sys/block/ disk /alignment_offset /sys/block/ disk / partition /alignment_offset The BLOCK LIMITS VPD page ( 0xb0 ) provides the I/O hints. It also uses OPTIMAL TRANSFER LENGTH GRANULARITY and OPTIMAL TRANSFER LENGTH to derive: /sys/block/ disk /queue/minimum_io_size /sys/block/ disk /queue/optimal_io_size The sg3_utils package provides the sg_inq utility, which can be used to access the BLOCK LIMITS VPD page. To do so, run:

Commands:
sg_inq -p 0xb0 disk
2. Introduction The following topics are covered in this document: Installation-Related Notes Feature Updates Kernel-Related Updates Driver Updates Technology Previews Resolved Issues Known Issues 2.1. Lifecycle The Red Hat Enterprise Linux 4 Life Cycle is available at: https://www.redhat.com/security/updates/errata/ As previously announced, the release of Red Hat Enterprise Linux 4.8 will mark the beginning of Production 2 phase of the Red Hat Enterprise Linux 4. No new hardware enablement will be expected during this phase. https://www.redhat.com/archives/nahant-list/2008-July/msg00059.html Customers should note that their subscriptions provide access to all currently supported versions of Red Hat Enterprise Linux.

Commands:
Chapter 4. The Persistence SPI In Red Hat JBoss Data Grid, persistence can configure external (persistent) storage engines. These storage engines complement JBoss Data Grid's default in-memory storage. Persistent external storage provides several benefits: Memory is volatile and a cache store can increase the life span of the information in the cache, which results in improved durability. Using persistent external stores as a caching layer between an application and a custom storage engine provides improved Write-Through functionality. Using a combination of eviction and passivation, only the frequently required information is stored in-memory and other data is stored in the external storage. Report a bug 4.1. Persistence SPI Benefits The Red Hat JBoss Data Grid implementation of the Persistence SPI offers the following benefits: Alignment with JSR-107 ( http://jcp.org/en/jsr/detail?id=107 ). JBoss Data Grid's CacheWriter and CacheLoader interfaces are similar to the JSR-107 writer and reader. As a result, alignment with JSR-107 provides improved portability for stores across JCache-compliant vendors. Simplified transaction integration. JBoss Data Grid handles locking automatically and so implementations do not have to coordinate concurrent access to the store. Depending on the locking mode, concurrent writes on the same key may not occur. However, implementors expect operations on the store to originate from multiple threads and add the implementation code accordingly. Reduced serialization, resulting in reduced CPU usage. The new SPI exposes stored entries in a serialized format. If an entry is fetched from persistent storage to be sent remotely, it does not need to be deserialized (when reading from the store) and then serialized again (when writing to the wire). Instead, the entry is written to the wire in the serialized format as fetched from the storage. Report a bug

Commands:
20.6. Explanation of Quota Threshold Settings Table 20.3. Quota thresholds and grace Setting Definition Cluster Threshold The amount of cluster resources available per data center. Cluster Grace The amount of the cluster available for the data center after exhausting the data center's Cluster Threshold. Storage Threshold The amount of storage resources available per data center. Storage Grace The amount of storage available for the data center after exhausting the data center's Storage Threshold. If a quota is set to 100 GB with 20% Grace, then consumers are blocked from using storage after they use 120 GB of storage. If the same quota has a Threshold set at 70%, then consumers receive a warning when they exceed 70 GB of storage consumption (but they remain able to consume storage until they reach 120 GB of storage consumption.) Both "Threshold" and "Grace" are set relative to the quota. "Threshold" may be thought of as the "soft limit", and exceeding it generates a warning. "Grace" may be thought of as the "hard limit", and exceeding it makes it impossible to consume any more storage resources.

Commands:
8.3.6. Backup Site Staffing The problem of staffing a backup site is multi-dimensional. One aspect of the problem is determining the staffing required to run the backup data center for as long as necessary. While a skeleton crew may be able to keep things going for a short period of time, as the disaster drags on more people will be required to maintain the effort needed to run under the extraordinary circumstances surrounding a disaster. This includes ensuring that personnel have sufficient time off to unwind and possibly travel back to their homes. If the disaster was wide-ranging enough to affect peoples' homes and families, additional time must be allotted to allow them to manage their own disaster recovery. Temporary lodging near the backup site is necessary, along with the transportation required to get people to and from the backup site and their lodgings. Often a disaster recovery plan includes on-site representative staff from all parts of the organization's user community. This depends on the ability of your organization to operate with a remote data center. If user representatives must work at the backup site, similar accommodations must be made available for them, as well.

Commands:
B.55. net-snmp B.55.1. RHBA-2010:0901 - net-snmp bug fix update Updated net-snmp packages that resolve several issues are now available for Red Hat Enterprise Linux 6. The net-snmp packages provide various libraries and tools for the Simple Network Management Protocol (SNMP), including an SNMP library, an extensible agent, tools for requesting or setting information from SNMP agents, tools for generating and handling SNMP traps, a version of the netstat command which uses SNMP, and a Tk/Perl MIB browser. Bug Fixes BZ# 652223 The SNMP daemon, snmpd, returned the incorrect value of either "0.1" or 1.3" for sysObjectID. This update fixes the value of this OID so that the correct value, which is "1.3.6.1.4.1.8072.3.2.10", is now returned. BZ# 652551 Under certain conditions, and especially on networks with high traffic, snmpd wrote a lot of "c64 32 bit check failed" and "netsnmp_assert 1 == new_val->high failed" messages to the system log. Although these messages are harmless and not indicative of a serious error, they could potentially fill the system log quickly. This update suppresses these spurious messages in favor of more meaningful and specific error messages, which are written to the system log only once. All users of net-snmp are advised to upgrade to these updated packages, which resolve these issues.

Commands:
Appendix A. Applying Custom Configuration to Red Hat Satellite When you install and configure Satellite for the first time using satellite-installer , you can specify that the DNS and DHCP configuration files are not to be managed by Puppet using the installer flags --foreman-proxy-dns-managed=false and --foreman-proxy-dhcp-managed=false . If these flags are not specified during the initial installer run, rerunning of the installer overwrites all manual changes, for example, rerun for upgrade purposes. If changes are overwritten, you must run the restore procedure to restore the manual changes. For more information, see Restoring Manual Changes Overwritten by a Puppet Run . To view all installer flags available for custom configuration, run satellite-installer --scenario satellite --full-help . Some Puppet classes are not exposed to the Satellite installer. To manage them manually and prevent the installer from overwriting their values, specify the configuration values by adding entries to configuration file /etc/foreman-installer/custom-hiera.yaml . This configuration file is in YAML format, consisting of one entry per line in the format of <puppet class>::<parameter name>: <value> . Configuration values specified in this file persist across installer reruns. Common examples include: For Apache, to set the ServerTokens directive to only return the Product name: To turn off the Apache server signature entirely: The Puppet modules for the Satellite installer are stored under /usr/share/foreman-installer/modules . Check the .pp files (for example: moduleName /manifests/ example .pp) to look up the classes, parameters, and values. Alternatively, use the grep command to do keyword searches. Setting some values may have unintended consequences that affect the performance or functionality of Red Hat Satellite. Consider the impact of the changes before you apply them, and test the changes in a non-production environment first. If you do not have a non-production Satellite environment, run the Satellite installer with the --noop and --verbose options. If your changes cause problems, remove the offending lines from custom-hiera.yaml and rerun the Satellite installer. If you have any specific questions about whether a particular value is safe to alter, contact Red Hat support.

Commands:
apache::server_tokens: Prod
apache::server_signature: Off
Chapter 4. Setting up Key Archival and Recovery For more information on Key Archival and Recovery, see the Archiving, Recovering, and Rotating Keys section in the Red Hat Certificate System Planning, Installation, and Deployment Guide . This chapter explains how to setup the Key Recovery Authority (KRA), previously known as Data Recovery Manager (DRM), to archive private keys and to recover archived keys for restoring encrypted data. Note This chapter only discusses archiving keys through client-side key generation. Server-side key generation and archivals, whether it's initiated through TPS, or through CA's End Entity portal, are not discussed here. For information on smart card key recovery, see Section 6.11, "Setting Up Server-side Key Generation" . For information on server-side key generation provided at the CA's EE portal, see Section 5.2.2, "Generating CSRs Using Server-Side Key Generation" . Note Gemalto SafeNet LunaSA only supports PKI private key extraction in its CKE - Key Export model, and only in non-FIPS mode. The LunaSA Cloning model and the CKE model in FIPS mode do not support PKI private key extraction. When KRA is installed, it joins a security domain, and is paired up with the CA. At such time, it is configured to archive and recover private encryption keys. However, if the KRA certificates are issued by an external CA rather than one of the CAs within the security domain, then the key archival and recovery process must be set up manually. For more information, see the Manually Setting up Key Archival section in the Red Hat Certificate System Planning, Installation, and Deployment Guide . Note In a cloned environment, it is necessary to set up key archival and recovery manually. For more information, see the Updating CA-KRA Connector Information After Cloning section in the Red Hat Certificate System Planning, Installation, and Deployment Guide . 4.1. Configuring Agent-Approved Key Recovery in the Console Note While the number of key recovery agents can be configured in the Console, the group to use can only be set directly in the CS.cfg file. The Console uses the Key Recovery Authority Agents Group by default. Open the KRA's console. For example: Click the Key Recovery Authority link in the left navigation tree. Enter the number of agents to use to approve key recover in the Required Number of Agents field. Note For more information on how to configure agent-approved key recovery in the CS.cfg file, see the Configuring Agent-Approved Key Recovery in the Command Line section in the Red Hat Certificate System Planning, Installation, and Deployment Guide .

Commands:
pkiconsole https://server.example.com:8443/kra
Chapter 62. Servers and Services No clear indication of profile activation error in the Tuned service Errors in the Tuned service configuration or errors occurring when loading Tuned profiles are in some cases not shown in the output of the systemctl status tuned command. As a consequence, if errors occur that prevent Tuned from loading, Tuned sometimes enters a state with no profile activated. To view possible error messages, consult the output of the tuned-adm active command and check the contents of the /var/log/tuned/tuned.log file. (BZ# 1385838 ) db_hotbackup -c should be used with caution The db_hotbackup command with the -c option must be run by the user that owns the database. If the user is different and the log file reaches its maximal size, a new log file is created with an ownership of the user that ran the command, which consequently makes the database unusable for its owner. This note has been added to the db_hotbackup(1) manual page. (BZ# 1460077 ) Setting ListenStream= options in rpcbind.socket causes systemd-logind to fail and SSH connections to be delayed Setting the ListenStream= options in the rpcbind.socket unit file currently causes a failure of the systemd-logind service and a delay in SSH connections that import system users from a NIS database. To work around the problem, remove lines with the ListenStream= option from rpcbind.socket . (BZ#1425758) ReaR recovery process fails on non-UEFI systems with the grub2-efi-x64 package installed Installing the grub2-efi-x64 package, which contains the GRUB2 boot loader for UEFI systems, changes the file /boot/grub2/grubenv into a dead absolute symlink on systems which do not use UEFI firmware. When attempting to recover such a system using the ReaR (Relax and Recover) recovery tool, the process fails and the system is rendered unbootable. To work around this problem, do not install the grub2-efi-x64 package on systems where it is not required (systems without UEFI firmware). (BZ# 1498748 ) ISO images generated by ReaR with Linux TSM fail to work The password store has changed in the Linux TSM (Tivoli Storage Manager) client versions 8.1.2 and above. This means ISO images generated by ReaR using TSM will not work, as the TSM node password and encryption key will not be included in the ISO file. To fix this problem, add the following line into the /etc/rear/local.conf or /etc/rear/site.conf configuration file: (BZ# 1534646 ) Unexpected problems with the dbus rebase The dbus package rebase with its configuration changes can cause unexpected problems. Thus, it is recommended to avoid the following actions: updating only the dbus service updating only parts of the system updating from a graphical session On the contrary, it is recommended to reboot after executing the yum update command as updating several major components including dbus without reboot rarely works as expected. (BZ# 1550582 )

Commands:
COPY_AS_IS_TSM=( /etc/adsm /opt/tivoli/tsm/client /usr/local/ibm/gsk8* )
17.2. DistributedCallable API The DistributedCallable interface is a subtype of the existing Callable from java.util.concurrent.package , and can be executed in a remote JVM and receive input from Red Hat JBoss Data Grid. The DistributedCallable interface is used to facilitate tasks that require access to JBoss Data Grid cache data. When using the DistributedCallable API to execute a task, the task's main algorithm remains unchanged, however the input source is changed. Users who have already implemented the Callable interface must extend DistributedCallable if access to the cache or the set of passed in keys is required. Example 17.1. Using the DistributedCallable API Report a bug

Commands:
public interface DistributedCallable<K, V, T> extends Callable<T> { /** * Invoked by execution environment after DistributedCallable * has been migrated for execution to a specific Infinispan node. * * @param cache * cache whose keys are used as input data for this * DistributedCallable task * @param inputKeys * keys used as input for this DistributedCallable task */ public void setEnvironment(Cache<K, V> cache, Set<K> inputKeys); }
32.3.6. Displaying Open Files To display information about open files, type the files command at the interactive prompt. You can use files pid to display files opened by the selected process. Example 32.7. Displaying information about open files of the current context Type help files for more information on the command usage.

Commands:
crash> files PID: 5591 TASK: f196d560 CPU: 2 COMMAND: "bash" ROOT: / CWD: /root FD FILE DENTRY INODE TYPE PATH 0 f734f640 eedc2c6c eecd6048 CHR /pts/0 1 efade5c0 eee14090 f00431d4 REG /proc/sysrq-trigger 2 f734f640 eedc2c6c eecd6048 CHR /pts/0 10 f734f640 eedc2c6c eecd6048 CHR /pts/0 255 f734f640 eedc2c6c eecd6048 CHR /pts/0
Chapter 23. Installation Phase 3: Installing Using Anaconda This chapter describes an installation using the graphical user interface of anaconda . 23.1. The Non-interactive Line-Mode Text Installation Program Output If the cmdline option was specified as boot option in your parameter file (Refer to Section 26.6, "Parameters for Kickstart Installations" ) or in your kickstart file (refer to Chapter 32, Kickstart Installations ), anaconda starts with line-mode oriented text output. In this mode, all necessary information must be provided in the kickstart file. The installer will not allow user interaction and stops if there is unspecified installation information.

Commands:
16.6.2. Common pam_timestamp Directives The pam_timestamp.so module accepts several directives. Below are the two most commonly used options: timestamp_timeout - Specifies the number of seconds the during which the timestamp file is valid (in seconds). The default value is 300 seconds (five minutes). timestampdir - Specifies the directory in which the timestamp file is stored. The default value is /var/run/sudo/ . For more information about controlling the pam_timestamp.so module, refer to Section 16.8.1, "Installed Documentation" .

Commands:
16.3. Search Transformation SQL The Teiid Designer provides a search capability to string values present in transformation SQL text. To search for string values in your transformations SQL: Click Search > Teiid Designer > Transformations... action on the main toolbar which which opens the Search Transformations dialog. Specify a string segment in the Find: field and specify/change your case sensitive preference. Select Perform Search button. Any transformation object containing SQL text which contains occurrences of your string will be displayed in the results section. You can select individual objects and view the SQL. If a table or view supports updates and there is insert, update or delete SQL present, you can expand the object and select the individual SQL type as shown below. If you wish to view the selected object and its SQL in a Model Editor , you can click the Edit button. An editor will be opened if not already open. If an editor is open its tab will be selected. In addition, the Transformation Editor will be opened and you can perform Find/Replace (Ctrl-F) actions to highlight your original searched text string and edit your SQL if you wish.

Commands:
function::sprint_ustack Name function::sprint_ustack - Return stack for the current task from string. EXPERIMENTAL! Synopsis Arguments stk String with list of hexadecimal addresses for the current task. Description Perform a symbolic lookup of the addresses in the given string, which is assumed to be the result of a prior call to ubacktrace for the current task. Returns a simple backtrace from the given hex string. One line per address. Includes the symbol name (or hex address if symbol couldn't be resolved) and module name (if found). Includes the offset from the start of the function if found, otherwise the offset will be added to the module (if found, between brackets). Returns the backtrace as string (each line terminated by a newline character). Note that the returned stack will be truncated to MAXSTRINGLEN, to print fuller and richer stacks use print_ustack.

Commands:
function sprint_ustack:string(stk:string)