mtpti5iD/redhat-docs_dataset huggingface dataset:
function::user_string_n2 Name function::user_string_n2 - Retrieves string of given length from user space. Synopsis Arguments addr The user space address to retrieve the string from. n The maximum length of the string (if not null terminated). err_msg The error message to return when data isn't available. General Syntax user_string_n2:string(addr:long, n:long, err_msg:string) Description Returns the C string of a maximum given length from a given user space address. Returns the given error message string on the rare cases when userspace data is not accessible at the given address.

Commands:
function user_string_n2:string(addr:long,n:long,err_msg:string)
Chapter 4. Resetting the Directory Manager password The Directory Manager is the privileged database administrator, comparable to the root user in a Linux operating system. The Directory Manager password is set during the instance installation. If you lose the password, you can reset it to regain privileged access to the directory. 4.1. Resetting the Directory Manager password using the command line If you have the root access to the Directory Server instance, you can reset the password of the Directory Manager. Procedure Generate a new password hash. For example: # pwdhash -D /etc/dirsrv/slapd- instance_name new_password {PBKDF2_SHA256}AAAgABU0bKhyjY53NcxY33ueoPjOUWtl4iyYN5uW... Because you specified the path to the Directory Server instance configuration, the pwdhash generator automatically uses the password storage scheme set in the nsslapd-rootpwstoragescheme attribute to encrypt the new password. Stop the Directory Server instance: # dsctl instance_name stop Edit the /etc/dirsrv/slapd- instance_name /dse.ldif file and set the nsslapd-rootpw attribute to the value displayed in the first step: nsslapd-rootpw: {PBKDF2_SHA256}AAAgABU0bKhyjY53NcxY33ueoPjOUWtl4iyYN5uW... Start the Directory Server instance: # dsctl instance_name start

Commands:
pwdhash -D /etc/dirsrv/slapd- instance_name new_password {PBKDF2_SHA256}AAAgABU0bKhyjY53NcxY33ueoPjOUWtl4iyYN5uW
dsctl instance_name stop
nsslapd-rootpw: {PBKDF2_SHA256}AAAgABU0bKhyjY53NcxY33ueoPjOUWtl4iyYN5uW
dsctl instance_name start
Chapter 5. DM-Multipath Administration and Troubleshooting This chapter will provide information on administering DM-Multipath on a running system. It includes sections on the following topics: Multipath Command Output Multipath Queries with multipath Command Multipath Command Options Multipath Queries with dmsetup Command Troubleshooting with the multipathd Interactive Console Resizing an Online Multipathed Device 5.1. Multipath Command Output When you create, modify, or list a multipath device, you get a printout of the current device setup. The format is as follows. For each multipath device: For each path group: For each path: For example, the output of a multipath command might appear as follows: If the path is up and ready for I/O, the status of the path is ready or active . If the path is down, the status is faulty or failed . The path status is updated periodically by the multipathd daemon based on the polling interval defined in the /etc/multipath.conf file. The dm status is similar to the path status, but from the kernel's point of view. The dm status has two states: failed , which is analogous to faulty , and active which covers all other path states. Occasionally, the path state and the dm state of a device will temporarily not agree. Note When a multipath device is being created or modified, the path group status and the dm status are not known. Also, the features are not always correct. When a multipath device is being listed, the path group priority is not known.

Commands:
action_if_any: alias (wwid_if_different_from_alias) [size][features][hardware_handler]
\_ scheduling_policy [path_group_priority_if_known] [path_group_status_if_known]
\_ host:channel:id:lun devnode major:minor [path_status] [dm_status_if_known]
mpath1 (3600d0230003228bc000339414edb8101) [size=10 GB][features="0"][hwhandler="0"] \_ round-robin 0 [prio=1][active] \_ 2:0:0:6 sdb 8:16 [active][ready] \_ round-robin 0 [prio=1][enabled] \_ 3:0:0:6 sdc 8:64 [active][ready]
7.5. RHEA-2013:1621 - new package: ps_mem A new ps_mem package is now available for Red Hat Enterprise Linux 6. The ps_mem package provides a memory usage script written in Python that calculates how much RAM is used per program. The script automatically selects the most accurate method, which is available for a particular running kernel. This enhancement update adds the ps_mem package to Red Hat Enterprise Linux 6. (BZ# 962850 ) All users who require ps_mem are advised to install this new package.

Commands:
18.7.2. Useful Websites http://www.netfilter.org/ - The home of the netfilter/iptables project. Contains assorted information about iptables , including a FAQ addressing specific problems and various helpful guides by Rusty Russell, the Linux IP firewall maintainer. The HOWTO documents on the site cover subjects such as basic networking concepts, kernel packet filtering, and NAT configurations. http://www.linuxnewbie.org/nhf/Security/IPtables_Basics.html - A basic and general look at the way packets move through the Linux kernel, plus an introduction to constructing basic iptables commands. http://www.redhat.com/support/resources/networking/firewall.html - This webpage links to a variety of update-to-date packet filter resources.

Commands:
3.7. Uninstalling a Client Uninstalling a client removes the client from the IdM domain, along with all of the IdM-specific configuration for system services, such as SSSD. This restores the client machine's configuration. Run the ipa-client-install --uninstall command: Remove the DNS entries for the client host manually from the server. See Section 33.4.6, "Deleting Records from DNS Zones" .

Commands:
ipa-client-install --uninstall
Chapter 2. Starting and Stopping Red Hat Satellite Satellite provides the satellite-maintain service command to manage Satellite services from the command line. This is useful when creating a backup of Satellite. For more information on creating backups, see Chapter 8, Backing Up Satellite Server and Capsule Server . After installing Satellite with the satellite-installer command, all Satellite services are started and enabled automatically. View the list of these services by executing: To see the status of running services, execute: To stop Satellite services, execute: To start Satellite services, execute: To restart Satellite services, execute:

Commands:
satellite-maintain service list
satellite-maintain service status
satellite-maintain service stop
satellite-maintain service start
satellite-maintain service restart
6.3.2. Files Controlling User Accounts and Groups On Red Hat Enterprise Linux, information about user accounts and groups are stored in several text files within the /etc/ directory. When a system administrator creates new user accounts, these files must either be edited manually or applications must be used to make the necessary changes. The following section documents the files in the /etc/ directory that store user and group information under Red Hat Enterprise Linux. 6.3.2.1. /etc/passwd The /etc/passwd file is world-readable and contains a list of users, each on a separate line. On each line is a colon delimited list containing the following information: Username - The name the user types when logging into the system. Password - Contains the encrypted password (or an x if shadow passwords are being used - more on this later). User ID ( UID ) - The numerical equivalent of the username which is referenced by the system and applications when determining access privileges. Group ID ( GID ) - The numerical equivalent of the primary group name which is referenced by the system and applications when determining access privileges. GECOS - Named for historical reasons, the GECOS [25] field is optional and is used to store extra information (such as the user's full name). Multiple entries can be stored here in a comma delimited list. Utilities such as finger access this field to provide additional user information. Home directory - The absolute path to the user's home directory, such as /home/juan/ . Shell - The program automatically launched whenever a user logs in. This is usually a command interpreter (often called a shell ). Under Red Hat Enterprise Linux, the default value is /bin/bash . If this field is left blank, /bin/sh is used. If it is set to a non-existent file, then the user will be unable to log into the system. Here is an example of a /etc/passwd entry: This line shows that the root user has a shadow password, as well as a UID and GID of 0. The root user has /root/ as a home directory, and uses /bin/bash for a shell. For more information about /etc/passwd , see the passwd(5) man page. [25] GECOS stands for General Electric Comprehensive Operating Supervisor. This field was used at Bell Labs, in the original UNIX implementation. The lab had many different computers, including one running GECOS. This field was used to store information when the UNIX system sent batch and print jobs to the GECOS system.

Commands:
root:x:0:0:root:/root:/bin/bash
4.311. system-config-firewall 4.311.1. RHBA-2011:1223 - system-config-firewall bug fix update Updated system-config-firewall packages that fix several bugs are now available for Red Hat Enterprise Linux 6. The system-config-firewall packages contain a graphical user interface for basic firewall setup. Bug Fixes BZ# 565625 Prior to this update, remote virtual machine management with TLS encryption used the same port as the one used for the unencrypted connection. With this update, the port for the remote virtual machine management has been changed so that remote virtual machine management with TLS encryption now works as expected. BZ# 624400 Prior to this update, the Tamil translation was incomplete. As a result, certain messages were displayed in English. With this update, the missing messages have been added to the translation. BZ# 632979 Prior to this update, the Hindi translation was incomplete. As a result, certain messages were displayed in English. With this update, the missing messages have been added to the translation. BZ# 635245 Prior to this update, the Punjabi translation was incomplete. As a result, certain messages were displayed in English. With this update, the missing messages have been added to the translation. All users of system-config-firewall are advised to upgrade to these updated packages, which fix these bugs.

Commands:
2.8.2. Basic Firewall Configuration Just as a firewall in a building attempts to prevent a fire from spreading, a computer firewall attempts to prevent malicious software from spreading to your computer. It also helps to prevent unauthorized users from accessing your computer. In a default Red Hat Enterprise Linux installation, a firewall exists between your computer or network and any untrusted networks, for example the Internet. It determines which services on your computer remote users can access. A properly configured firewall can greatly increase the security of your system. It is recommended that you configure a firewall for any Red Hat Enterprise Linux system with an Internet connection. 2.8.2.1. Firewall Configuration Tool During the Firewall Configuration screen of the Red Hat Enterprise Linux installation, you were given the option to enable a basic firewall as well as to allow specific devices, incoming services, and ports. After installation, you can change this preference by using the Firewall Configuration Tool . To start this application, either select System Administration Firewall from the panel, or type system-config-firewall at a shell prompt. Figure 2.5. Firewall Configuration Tool Note The Firewall Configuration Tool only configures a basic firewall. If the system needs more complex rules, see Section 2.8.9, "IPTables" for details on configuring specific iptables rules. As of Red Hat Enterprise Linux 6.5 , the iptables and ip6tables services now provide the ability to assign a fallback firewall configuration if the default configuration cannot be applied. If application of the firewall rules from /etc/sysconfig/iptables fails, the fallback file is applied if it exists. The fallback file is named /etc/sysconfig/iptables.fallback and uses the same file format as /etc/sysconfig/iptables . If application of the fallback file also fails, there is no further fallback. To create a fallback file, use the standard firewall configuration tool and rename or copy the file to the fallback file. For the ip6tables service, replace all occurrences of iptables with ip6tables in the above examples. Warning If you have previously set up some custom packet-filtering rules by directly using the iptables utility (as described in Section 2.8.9, "IPTables" ), running the system-config-firewall utility will erase these custom rules immediately.

Commands:
3.4. Associative Arrays SystemTap also supports the use of associative arrays. While an ordinary variable represents a single value, associative arrays can represent a collection of values. Simply put, an associative array is a collection of unique keys; each key in the array has a value associated with it. Since associative arrays are normally processed in multiple probes (as we will demonstrate later), they should be declared as global variables in the SystemTap script. The syntax for accessing an element in an associative array is similar to that of awk , and is as follows: array_name [ index_expression ] Here, the array_name is any arbitrary name the array uses. The index_expression is used to see a specific unique key in the array. To illustrate, let us try to build an array named arr that specifies the ages of three people (the unique keys): tom , dick , and harry . To assign them the ages (associated values) of 23, 24, and 25 respectively, we'd use the following array statements: Example 3.11. Basic Array Statements arr["tom"] = 23 arr["dick"] = 24 arr["harry"] = 25 You can specify up to nine index expressons in an array statement, each one delimited by a comma ( , ). This is useful if you wish to have a key that contains multiple pieces of information. The following line from Example 4.9, "disktop.stp" uses 5 elements for the key: process ID, executable name, user ID, parent process ID, and string "W". It associates the value of devname with that key. device[pid(),execname(),uid(),ppid(),"W"] = devname Important All associate arrays must be declared as global , regardless of whether the associate array is used in one or multiple probes.

Commands:
array_name [ index_expression ]
arr["tom"] = 23 arr["dick"] = 24 arr["harry"] = 25
device[pid(),execname(),uid(),ppid(),"W"] = devname
Appendix F. Revision History Note that revision numbers relate to the edition of this manual, not to version numbers of Red Hat Certificate System. Revision History Revision 10.1-1 Mon Jan 25 2021 Florian Delehaye Various fixes and improvements. Revision 10.1-0 Wed Dec 02 2020 Florian Delehaye Red Hat Certificate System 10.1 release of the guide. Revision 10.0-0 Wed Sep 17 2020 Florian Delehaye Red Hat Certificate System 10.0 release of the guide.

Commands:
Chapter 9. (Preview) Streams for Apache Kafka Proxy Streams for Apache Kafka Proxy is an Apache Kafka protocol-aware proxy designed to enhance Kafka-based systems. Through its filter mechanism it allows additional behaviour to be introduced into a Kafka-based system without requiring changes to either your applications or the Kafka cluster itself. Streams for Apache Kafka Proxy is currently available as a technology preview, which introduces Streams for Apache Kafka Proxy's Record Encryption filter. The Record Encryption filter provides encryption at rest, using industry-standard cryptographic techniques to apply encryption to Kafka Messages, ensuring the confidentiality of data stored in the Kafka Cluster. For more information on connecting to and using the Streams for Apache Kafka Proxy, see the proxy guide in the Streams for Apache Kafka documentation .

Commands:
4.298. smartmontools 4.298.1. RHBA-2011:1201 - smartmontools bug fix update An updated smartmontools package that fixes one bug is now available for Red Hat Enterprise Linux 6. The smartmontools package contains two utilities, smartctl and smartd, that enable the controlling and monitoring of Self-Monitoring, Analysis and Reporting Technology System (S.M.A.R.T.) enabled storage systems. These utilities provide advanced warning of disk degradation and failure. Bug Fix BZ# 697867 Prior to this update, when a system event relevant to smartd happened, the following spurious error message was output if no mail address was configured: This unintended behavior has been fixed in this update so that the spurious error message is no longer displayed. All smartmontools users are advised to upgrade to this updated package, which fixes this bug.

Commands:
smartd: internal error in MailWarning(): cfg.mailwarn->emailfreq=0
Chapter 3. What is deployed with Streams for Apache Kafka Apache Kafka components are provided for deployment to OpenShift with the Streams for Apache Kafka distribution. The Kafka components are generally run as clusters for availability. A typical deployment incorporating Kafka components might include: Kafka cluster of broker nodes ZooKeeper cluster of replicated ZooKeeper instances Kafka Connect cluster for external data connections Kafka MirrorMaker cluster to mirror the Kafka cluster in a secondary cluster Kafka Exporter to extract additional Kafka metrics data for monitoring Kafka Bridge to make HTTP-based requests to the Kafka cluster Cruise Control to rebalance topic partitions across broker nodes Not all of these components are mandatory, though you need Kafka and ZooKeeper as a minimum. Some components can be deployed without Kafka, such as MirrorMaker or Kafka Connect. 3.1. Order of deployment The required order of deployment to an OpenShift cluster is as follows: Deploy the Cluster Operator to manage your Kafka cluster Deploy the Kafka cluster with the ZooKeeper cluster, and include the Topic Operator and User Operator in the deployment Optionally deploy: The Topic Operator and User Operator standalone if you did not deploy them with the Kafka cluster Kafka Connect Kafka MirrorMaker Kafka Bridge Components for the monitoring of metrics The Cluster Operator creates OpenShift resources for the components, such as Deployment , Service , and Pod resources. The names of the OpenShift resources are appended with the name specified for a component when it's deployed. For example, a Kafka cluster named my-kafka-cluster has a service named my-kafka-cluster-kafka . 3.2. (Preview) Deploying the Streams for Apache Kafka Proxy Streams for Apache Kafka Proxy is an Apache Kafka protocol-aware proxy designed to enhance Kafka-based systems. Through its filter mechanism it allows additional behavior to be introduced into a Kafka-based system without requiring changes to either your applications or the Kafka cluster itself. For more information on connecting to and using the Streams for Apache Kafka Proxy, see the proxy guide in the Streams for Apache Kafka documentation . Note The Streams for Apache Kafka Proxy is currently available as a technology preview. 3.3. (Preview) Deploying the Streams for Apache Kafka Console After you have deployed a Kafka cluster that's managed by Streams for Apache Kafka, you can deploy the Streams for Apache Kafka Console and connect your cluster. The Streams for Apache Kafka Console facilitates the administration of Kafka clusters, providing real-time insights for monitoring, managing, and optimizing each cluster from its user interface. For more information on connecting to and using the Streams for Apache Kafka Console, see the console guide in the Streams for Apache Kafka documentation . Note The Streams for Apache Kafka Console is currently available as a technology preview.

Commands:
B.19. evince B.19.1. RHSA-2011:0009 - Moderate: evince security update Updated evince packages that fix multiple 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. Evince is a document viewer. CVE-2010-2640 , CVE-2010-2641 An array index error was found in the DeVice Independent (DVI) renderer's PK and VF font file parsers. A DVI file that references a specially-crafted font file could, when opened, cause Evince to crash or, potentially, execute arbitrary code with the privileges of the user running Evince. CVE-2010-2642 A heap-based buffer overflow flaw was found in the DVI renderer's AFM font file parser. A DVI file that references a specially-crafted font file could, when opened, cause Evince to crash or, potentially, execute arbitrary code with the privileges of the user running Evince. CVE-2010-2643 An integer overflow flaw was found in the DVI renderer's TFM font file parser. A DVI file that references a specially-crafted font file could, when opened, cause Evince to crash or, potentially, execute arbitrary code with the privileges of the user running Evince. Note: The above issues are not exploitable unless an attacker can trick the user into installing a malicious font file. Red Hat would like to thank the Evince development team for reporting these issues. Upstream acknowledges Jon Larimer of IBM X-Force as the original reporter of these issues. Users are advised to upgrade to these updated packages, which contain a backported patch to correct these issues.

Commands:
Preface Kamelets are reusable route components that hide the complexity of creating data pipelines that connect to external systems. Making open source more inclusive Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright's message .

Commands:
5.2.21. /proc/modules This file displays a list of all modules loaded into the kernel. Its contents vary based on the configuration and use of your system, but it should be organized in a similar manner to this sample /proc/modules file output: Note This example has been reformatted into a readable format. Most of this information can also be viewed via the /sbin/lsmod command. The first column contains the name of the module. The second column refers to the memory size of the module, in bytes. The third column lists how many instances of the module are currently loaded. A value of zero represents an unloaded module. The fourth column states if the module depends upon another module to be present in order to function, and lists those other modules. The fifth column lists what load state the module is in: Live , Loading , or Unloading are the only possible values. The sixth column lists the current kernel memory offset for the loaded module. This information can be useful for debugging purposes, or for profiling tools such as oprofile .

Commands:
nfs 170109 0 - Live 0x129b0000 lockd 51593 1 nfs, Live 0x128b0000 nls_utf8 1729 0 - Live 0x12830000 vfat 12097 0 - Live 0x12823000 fat 38881 1 vfat, Live 0x1287b000 autofs4 20293 2 - Live 0x1284f000 sunrpc 140453 3 nfs,lockd, Live 0x12954000 3c59x 33257 0 - Live 0x12871000 uhci_hcd 28377 0 - Live 0x12869000 md5 3777 1 - Live 0x1282c000 ipv6 211845 16 - Live 0x128de000 ext3 92585 2 - Live 0x12886000 jbd 65625 1 ext3, Live 0x12857000 dm_mod 46677 3 - Live 0x12833000