mtpti5iD/redhat-docs_dataset huggingface dataset:
16.2. Considerations for Hard Drive Installation on IBM Z If you want to boot the installation program from a hard drive, you can optionally install the zipl boot loader on the same (or a different) disk. Be aware that zipl only supports one boot record per disk. If you have multiple partitions on a disk, they all "share" the disk's single boot record. To prepare a hard drive to boot the installation program, install the zipl boot loader on the hard drive by entering the following command: See Section 16.1, "Customizing boot parameters" for details on customizing boot parameters in the generic.prm configuration file.

Commands:
zipl -V -t /mnt/ -i /mnt/images/kernel.img -r /mnt/images/initrd.img -p /mnt/images/generic.prm
Chapter 10. Deploying a business process in Business Central After you design your business process in Business Central, you can build and deploy your project in Business Central to make the process available to KIE Server. Prerequisites KIE Server is deployed and connected to Business Central. For more information about KIE Server configuration, see Installing and configuring Red Hat Process Automation Manager on Red Hat JBoss EAP 7.4 . Procedure In Business Central, go to Menu Design Projects . Click the project that you want to deploy. Click Deploy . Note You can also select the Build & Install option to build the project and publish the KJAR file to the configured Maven repository without deploying to a KIE Server. In a development environment, you can click Deploy to deploy the built KJAR file to a KIE Server without stopping any running instances (if applicable), or click Redeploy to deploy the built KJAR file and replace all instances. The time you deploy or redeploy the built KJAR, the deployment unit (KIE container) is automatically updated in the same target KIE Server. In a production environment, the Redeploy option is disabled and you can click Deploy only to deploy the built KJAR file to a new deployment unit (KIE container) on a KIE Server. To configure the KIE Server environment mode, set the org.kie.server.mode system property to org.kie.server.mode=development or org.kie.server.mode=production . To configure the deployment behavior for a corresponding project in Business Central, go to project Settings General Settings Version and toggle the Development Mode option. By default, KIE Server and all new projects in Business Central are in development mode. You cannot deploy a project with Development Mode turned on or with a manually added SNAPSHOT version suffix to a KIE Server that is in production mode. To review project deployment details, click View deployment details in the deployment banner at the top of the screen or in the Deploy drop-down menu. This option directs you to the Menu Deploy Execution Servers page.

Commands:
Chapter 13. Running Directory Server in FIPS mode Directory Server fully supports the Federal Information Processing Standard (FIPS) 140-2. When you run Directory Server run in FIPS mode, security-related settings change. For example, SSL is automatically disabled and only TLS 1.2 and 1.3 encryption is used. 13.1. Enabling the FIPS mode To use Directory Server in Federal Information Processing Standard (FIPS) mode, enable the mode in RHEL and Directory Server. Prerequisites You enabled the FIPS mode in RHEL. Procedure Enable the FIPS mode for the network security services (NSS) database: # modutil -dbdir /etc/dirsrv/slapd- instance_name / -fips true Restart the instance: # dsctl instance_name restart Verification Verify that FIPS mode is enabled for the NSS database: # modutil -dbdir /etc/dirsrv/slapd- instance_name / -chkfips true FIPS mode enabled. The command returns FIPS mode enabled , if the module is in FIPS mode. 13.2. Additional resources Federal Information Processing Standard (FIPS) Switching the system to FIPS mode

Commands:
modutil -dbdir /etc/dirsrv/slapd- instance_name / -fips true
dsctl instance_name restart
modutil -dbdir /etc/dirsrv/slapd- instance_name / -chkfips true FIPS mode enabled.
Chapter 87. versions This chapter describes the commands under the versions command. 87.1. versions show Show available versions of services Usage: Table 87.1. Optional Arguments Value Summary -h, --help Show this help message and exit --all-interfaces Show values for all interfaces --interface <interface> Show versions for a specific interface. --region-name <region_name> Show versions for a specific region. --service <region_name> Show versions for a specific service. --status <region_name> Show versions for a specific status. [valid values are SUPPORTED, CURRENT, DEPRECATED, EXPERIMENTAL] Table 87.2. Output Formatters Value Summary -f {csv,json,table,value,yaml}, --format {csv,json,table,value,yaml} The output format, defaults to table -c COLUMN, --column COLUMN Specify the column(s) to include, can be repeated --sort-column SORT_COLUMN Specify the column(s) to sort the data (columns specified first have a priority, non-existing columns are ignored), can be repeated Table 87.3. CSV Formatter Value Summary --quote {all,minimal,none,nonnumeric} When to include quotes, defaults to nonnumeric Table 87.4. JSON Formatter Value Summary --noindent Whether to disable indenting the json Table 87.5. Table Formatter Value Summary --max-width <integer> Maximum display width, <1 to disable. you can also use the CLIFF_MAX_TERM_WIDTH environment variable, but the parameter takes precedence. --fit-width Fit the table to the display width. implied if --max- width greater than 0. Set the environment variable CLIFF_FIT_WIDTH=1 to always enable --print-empty Print empty table if there is no data to show.

Commands:
openstack versions show [-h] [-f {csv,json,table,value,yaml}] [-c COLUMN] [--quote {all,minimal,none,nonnumeric}] [--noindent] [--max-width <integer>] [--fit-width] [--print-empty] [--sort-column SORT_COLUMN] [--all-interfaces | --interface <interface>] [--region-name <region_name>] [--service <region_name>] [--status <region_name>]
Chapter 2. User Accounts 2.1. User Accounts The following account types are available for you to use in JBoss Data Virtualization: JBoss EAP Management User You must have a JBoss EAP Management User in order to administer your JBoss Data Virtualization installation via the Management Console, Management CLI, JBoss Developer Studio, and Admin API. JBoss Data Virtualization User JBoss Data Virtualization users can access the virtual databases (VDBs). You can define what permissions each of these users has to dictate what they can do with these databases. Hierarchical Database User Hierarchical database users can access the provided hierarchical database. You can define what permissions each of these users has to dictate what they can do with this database. Note User/role names and details are independent of any other accounts such as operating system accounts. They relate only to JBoss EAP and JBoss Data Virtualization.

Commands:
1.3.3. Threats to Workstation and Home PC Security Workstations and home PCs may not be as prone to attack as networks or servers, but since they often contain sensitive data, such as credit card information, they are targeted by system attackers. Workstations can also be co-opted without the user's knowledge and used by attackers as "slave" machines in coordinated attacks. For these reasons, knowing the vulnerabilities of a workstation can save users the headache of reinstalling the operating system, or worse, recovering from data theft. 1.3.3.1. Bad Passwords Bad passwords are one of the easiest ways for an attacker to gain access to a system. For more on how to avoid common pitfalls when creating a password, see Section 2.1.3, "Password Security" .

Commands:
14.13.2. Displaying Virtual CPU Information To display virtual CPU information from a guest virtual machine with virsh : An example of virsh vcpuinfo output:

Commands:
virsh vcpuinfo {domain-id, domain-name or domain-uuid}
virsh vcpuinfo rhel6 VCPU: 0 CPU: 2 State: running CPU time: 7152.4s CPU Affinity: yyyy VCPU: 1 CPU: 2 State: running CPU time: 10889.1s CPU Affinity: yyyy
Chapter 73. Exporting and importing test scenario spreadsheets These sections show how to export and import test scenario spreadsheets in the test scenario designer. You can analyze and manage test scenario spreadsheets with software such as Microsoft Excel or LibreOffice Calc. Test scenario designer supports the .CSV file format. For more information about the RFC specification for the Comma-Separated Values (CSV) format, see Common Format and MIME Type for Comma-Separated Values (CSV) Files . 73.1. Exporting a test scenario spreadsheet Follow the procedure below to export a test scenario spreadsheet using the Test Scenario designer. Procedure In the Test Scenario designer toolbar on the upper-right, click Export button. Select a destination in your local file directory and confirm to save the .CSV file. The .CSV file is exported to your local machine. 73.2. Importing a test scenario spreadsheet Follow the procedure below to import a test scenario spreadsheet using the Test Scenario designer. Procedure In the Test Scenario designer toolbar on the upper-right, click Import button. In the Select file to Import prompt, click Choose File... and select the .CSV file you would like to import from your local file directory. Click Import . The .CSV file is imported to the Test Scenario designer. Warning You must not modify the headers in the selected .CSV file. Otherwise, the spreadsheet may not be successfully imported.

Commands:
2.3. Define a Connection Factory Extend the org.teiid.resourse.spi.BasicConnectionFactory class, and provide an implementation for the getConnection() method. This method will create and return an instance of a connection. public class MyConnectionFactory extends BasicConnectionFactory { @Override public MyConnection getConnection() throws ResourceException { return new MyConnection(); } } Since the Managed Connection Factory creates a Connection Factory, it has access to all the configuration parameters so that the getConnection() method can pass credentials to the requesting application. Therefore, the Connection Factory can reference the calling user's javax.security.auth.Subject from within the getConnection() method. Subject subject = ConnectionContext.getSubject(); A Subject can give access to logged-in user's credentials and roles that are defined. This may be null . Note You can define a security-domain for this resource adapter that is separate from the default Red Hat JBoss Data Virtualization security-domain for validating the JDBC user. However, it is the user's responsibility to perform the necessary logins before the application server's thread accesses this resource adapter.

Commands:
public class MyConnectionFactory extends BasicConnectionFactory { @Override public MyConnection getConnection() throws ResourceException { return new MyConnection(); } }
Subject subject = ConnectionContext.getSubject();
9.15.4. Create LVM Logical Volume Important LVM initial set up is not available during text-mode installation. If you need to create an LVM configuration from scratch, press Alt + F2 to use a different virtual console, and run the lvm command. To return to the text-mode installation, press Alt + F1 . Logical Volume Management (LVM) presents a simple logical view of underlying physical storage space, such as a hard drives or LUNs. Partitions on physical storage are represented as physical volumes that can be grouped together into volume groups . Each volume group can be divided into multiple logical volumes , each of which is analogous to a standard disk partition. Therefore, LVM logical volumes function as partitions that can span multiple physical disks. To read more about LVM, refer to the Red Hat Enterprise Linux Deployment Guide . Note, LVM is only available in the graphical installation program. LVM Physical Volume Choose this option to configure a partition or device as an LVM physical volume. This option is the only choice available if your storage does not already contain LVM Volume Groups. This is the same dialog that appears when you add a standard partition - refer to Section 9.15.2, "Adding Partitions" for a description of the available options. Note, however, that File System Type must be set to physical volume (LVM) Figure 9.44. Create an LVM Physical Volume Make LVM Volume Group Choose this option to create LVM volume groups from the available LVM physical volumes, or to add existing logical volumes to a volume group. Figure 9.45. Make LVM Volume Group To assign one or more physical volumes to a volume group, first name the volume group. Then select the physical volumes to be used in the volume group. Finally, configure logical volumes on any volume groups using the Add , Edit and Delete options. You may not remove a physical volume from a volume group if doing so would leave insufficient space for that group's logical volumes. Take for example a volume group made up of two 5 GB LVM physical volume partitions, which contains an 8 GB logical volume. The installer would not allow you to remove either of the component physical volumes, since that would leave only 5 GB in the group for an 8 GB logical volume. If you reduce the total size of any logical volumes appropriately, you may then remove a physical volume from the volume group. In the example, reducing the size of the logical volume to 4 GB would allow you to remove one of the 5 GB physical volumes. Make Logical Volume Choose this option to create an LVM logical volume. Select a mount point, file system type, and size (in MB) just as if it were a standard disk partition. You can also choose a name for the logical volume and specify the volume group to which it will belong. Figure 9.46. Make Logical Volume

Commands:
9.8. Using Hardware Security Modules A security module serves as a medium between the Directory Server and the TLS layer. The module stores the keys and certificates used for encryption and decryption. The standard which defines these modules is Public Key Cryptography Standard (PKCS) #11, so these modules are PKCS#11 modules. By default, Directory Server uses built-in security databases, key4.db and cert9.db , to store the keys and certificates used by the servers. It is also possible to use external security devices to store Directory Server certificates and keys. For Directory Server to use an external PKCS#11 module, the module's drivers must be installed in Directory Server. For more information, consult the documentation for your hardware security module.

Commands:
11.2. Default Evaluators Red Hat Certificate System provides four default evaluators. The following entries are listed by default in the CS.cfg file: The group access evaluator evaluates the group membership properties of a user. For example, in the following enrollment profile entry, only the CA agents are allowed to go through enrollment with that profile: The ipaddress access evaluator evaluates the IP address of the requesting subject. For example, in the following enrollment profile entry, only the host bearing the specified IP address can go through enrollment with that profile: The user access evaluator evaluates the user ID for exact match. For example, in the following enrollment profile entry, only the user matching the listed user is allowed to go through enrollment with that profile: The user_origreq access evaluator evaluates the authenticated user against a matching request for equality. This special evaluator is designed specifically for renewal purpose to make sure the user requesting the renewal is the same user that owns the original request. For example, in the following renewal enrollment profile entry, the UID of the authenticated user must match the UID of the user requesting the renewal: New evaluators can be written in the current framework and can be registered through the CS console. The default evaluators can be used as templates to expand and customize into more targeted plug-ins.

Commands:
accessEvaluator.impl.group.class=com.netscape.cms.evaluators.GroupAccessEvaluator accessEvaluator.impl.ipaddress.class=com.netscape.cms.evaluators.IPAddressAccessEvaluator accessEvaluator.impl.user.class=com.netscape.cms.evaluators.UserAccessEvaluator accessEvaluator.impl.user_origreq.class=com.netscape.cms.evaluators.UserOrigReqAccessEvaluator
authz.acl=group="Certificate Manager Agents"
authz.acl=ipaddress="a.b.c.d.e.f"
authz.acl=user="bob"
authz.acl=user_origreq="auth_token.uid"
2.2.10. Perl The perl package adds support for the Perl programming language. This package provides Perl core modules, the Perl Language Interpreter, and the PerlDoc tool. Red Hat also provides various perl modules in package form; these packages are named with the perl-* prefix. These modules provide stand-alone applications, language extensions, Perl libraries, and external library bindings. 2.2.10.1. Perl Updates For a full list of the differences between the Perl versions see the following documents: Perl 5.12 Updates Perl 5.12 has the following updates: Perl conforms closer to the Unicode standard. Experimental APIs allow Perl to be extended with "pluggable" keywords and syntax. Perl will be able to keep accurate time well past the "Y2038" barrier. Package version numbers can be directly specified in "package" statements. Perl warns the user about the use of depreciated features by default. The Perl 5.12 delta can be accessed at http://perldoc.perl.org/perl5120delta.html . Perl 5.14 Updates Perl 5.14 has the following updates: Unicode 6.0 support. Improved support for IPv6. Easier auto-configuration of the CPAN client. A new /r flag that makes s/// substitutions non-destructive. New regular expression flags to control whether matched strings should be treated as ASCII or Unicode. New package Foo { } syntax. Less memory and CPU usage than releases. A number of bug fixes. The Perl 5.14 delta can be accessed at http://perldoc.perl.org/perl5140delta.html . Perl 5.16 Updates Perl 5.14 has the following updates: Support for Unicode 6.1. USDUSD variable is writable. Improved debugger. Accessing Unicode database files directly is now depreciated; use Unicode::UCD instead. Version :: Requirements is depreciated in favor of CPAN:: Meta :: Requirements . A number of perl4 libraries are removed: abbrev.pl assert.pl bigfloat.pl bigint.pl bigrat.pl cacheout.pl complete.pl ctime.pl dotsh.pl exceptions.pl fastcwd.pl flush.pl getcwd.pl getopt.pl getopts.pl hostname.pl importenv.pl lib/find{,depth}.pl look.pl newgetopt.pl open2.pl open3.pl pwd.pl hellwords.pl stat.pl tainted.pl termcap.pl timelocal.pl The Perl 5.16 delta can be accessed at http://perldoc.perl.org/perl5160delta.html .

Commands:
Chapter 13. Post-installation security hardening RHEL is designed with robust security features enabled by default. However, you can enhance its security further through additional hardening measures. For more information about: Installing security updates and displaying additional details about the updates to keep your RHEL systems secured against newly discovered threats and vulnerabilities, see Managing and monitoring security updates . Processes and practices for securing RHEL servers and workstations against local and remote intrusion, exploitation, and malicious activity, see Security hardening . Control how users and processes interact with the files on the system or control which users can perform which actions by mapping them to specific SELinux confined users, see Using SELinux . Tools and techniques to improve the security of your networks and lower the risks of data breaches and intrusions, see Securing networks . Packet filters, such as firewalls, that use rules to control incoming, outgoing, and forwarded network traffic, see Configuring firewalls and packet filters .

Commands:
Chapter 1. Adding a subscription to your inventory Authorized users can acquire new subscriptions directly from the Subscription Inventory page. Red Hat subscriptions are available through multiple channels, including Red Hat Marketplace, Red Hat Store, a Red Hat sales representative, or a Red Hat business partner. To learn more about the purchasing options or to access a no-cost trial, click Purchase subscriptions . After the new subscription is activated, you can view it in the All subscriptions table for the account.

Commands:
5.9.6.2.3. Erase the Contents of the Disk Drive Erasing the contents of a disk drive under Red Hat Enterprise Linux is a straightforward procedure. After unmounting all of the disk drive's partitions, issue the following command (while logged in as root): Where <device-name> represents the file name of the disk drive you wish to erase, excluding the partition number. For example, /dev/hdb for the second ATA hard drive. The following output is displayed while badblocks runs: Keep in mind that badblocks is actually writing four different data patterns to every block on the disk drive. For large disk drives, this process can take a long time -- quite often several hours. Important Many companies (and government agencies) have specific methods of erasing data from disk drives and other data storage media. You should always be sure you understand and abide by these requirements; in many cases there are legal ramifications if you fail to do so. The example above should in no way be considered the ultimate method of wiping a disk drive. However, it is much more effective than using the rm command. That is because when you delete a file using rm it only marks the file as deleted -- it does not erase the contents of the file.

Commands:
badblocks -ws <device-name>
Writing pattern 0xaaaaaaaa: done Reading and comparing: done Writing pattern 0x55555555: done Reading and comparing: done Writing pattern 0xffffffff: done Reading and comparing: done Writing pattern 0x00000000: done Reading and comparing: done
1.5. Key Management Before a certificate can be issued, the public key it contains and the corresponding private key must be generated. Sometimes it may be useful to issue a single person one certificate and key pair for signing operations and another certificate and key pair for encryption operations. Separate signing and encryption certificates keep the private signing key only on the local machine, providing maximum nonrepudiation. This also aids in backing up the private encryption key in some central location where it can be retrieved in case the user loses the original key or leaves the company. Keys can be generated by client software or generated centrally by the CA and distributed to users through an LDAP directory. There are costs associated with either method. Local key generation provides maximum nonrepudiation but may involve more participation by the user in the issuing process. Flexible key management capabilities are essential for most organizations. Key recovery , or the ability to retrieve backups of encryption keys under carefully defined conditions, can be a crucial part of certificate management, depending on how an organization uses certificates. In some PKI setups, several authorized personnel must agree before an encryption key can be recovered to ensure that the key is only recovered to the legitimate owner in authorized circumstance. It can be necessary to recover a key when information is encrypted and can only be decrypted by the lost key.

Commands:
6.4. Configuring the I/O Scheduler The I/O scheduler is configured one way for Red Hat Enterprise Linux 5 and 6 and a different way for Red Hat Enterprise Linux 7. 6.4.1. Configuring the I/O Scheduler for Red Hat Enterprise Linux 5 and 6 The I/O scheduler can be selected at boot time using the elevator kernel parameter. In the following example grub.conf stanza, the system is configured to use the noop scheduler. The example shown is for VMware ESX.

Commands:
title Red Hat Enterprise Linux Server (2.6.18-8.el5) root (hd0,0) kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/vg0/lv0 elevator=noop initrd /initrd-2.6.18-8.el5.img