mtpti5iD/redhat-docs_dataset huggingface dataset:
3.5.3. Creating Network Packet Filter Rules Before assigning any iptables rules for FTP service, review the information in Section 3.4.1, "Assigning Firewall Marks" concerning multi-port services and techniques for checking the existing network packet filtering rules. Below are rules which assign the same firewall mark, 21, to FTP traffic. For these rules to work properly, you must also use the VIRTUAL SERVER subsection of Piranha Configuration Tool to configure a virtual server for port 21 with a value of 21 in the Firewall Mark field. See Section 4.6.1, "The VIRTUAL SERVER Subsection" for details. 3.5.3.1. Rules for Active Connections The rules for active connections tell the kernel to accept and forward connections coming to the internal floating IP address on port 20 - the FTP data port. The following iptables command allows the LVS router to accept outgoing connections from the real servers that IPVS does not know about: /sbin/iptables -t nat -A POSTROUTING -p tcp -s n.n.n .0/24 --sport 20 -j MASQUERADE In the iptables command, n.n.n should be replaced with the first three values for the floating IP for the NAT interface's internal network interface defined in the GLOBAL SETTINGS panel of the Piranha Configuration Tool .

Commands:
Chapter 47. Business Central custom dashboards A dashboard is a collection of Business Central pages that contain at least one reporting component. Dashboards often contain data sets, navigation trees, and permissions. Data set authoring: Define a data set for accessing the data and displaying it through the pages. For more information, see Adding data sets . Security management - In this stage, role and group permissions are set which defines the privileges that are granted to a user when the user is working on Business Central. For more information, see Security management . Additional resources To migrate dashboards from a version of Business Central, use the Dashbuilder Data Transfer feature described in Section 50.1, "Exporting dashboard data" .

Commands:
4.8. Creating the Initial Data Disk Create a 10,220 GB standard persistent disk for the rhgs-primary-n01 VM instance in the same zone as the instance. In the Google Developers Console, click Compute > Compute Engine > Disks > New disk . Enter the following in the New Disk window and click Create . Name: rhgs-primary-n01-data Zone: us-central1-a Disk Type: Standard persistent disk Source Type: None (blank disk) Size (GB): 10220

Commands:
30.6.2. Configuring the Loopback Device Limit The maximum number of loopback devices in Red Hat Enterprise Linux 6 is set by the max_loop kernel option. For example, to set the maximum number of loopback devices to 64 , edit the /etc/grub.conf file, and add max_loop=64 at the end of the kernel line. The line in /etc/grub.conf would then look something like this: Reboot the system for the changes to take affect. By default, eight /dev/loop* devices ( /dev/loop0 to /dev/loop7 ) are automatically generated, but others can be created as desired. For example, to set up a ninth loop device named /dev/loop8 , issue the following command as root : Thus, an administrator on a system with a Red Hat Enterprise Linux 6 kernel can create the desired number of loopback devices manually, with an init script, or with a udev rule. However, if max_loop has been set before the system booted, max_loop becomes a hard limit on the number of loopback devices, and the number of loopback devices cannot be dynamically grown beyond the limit.

Commands:
kernel /vmlinuz-2.6.32-131.0.15.el6.x86_64 ro root=/dev/mapper/root rhgb quiet max_loop=64 initrd /initramfs-2.6.32-131.0.15.el6.x86_64.img
~]# mknod /dev/loop8 b 7 8
32.6. Shadow Passwords In multiuser environments it is very important to use shadow passwords (provided by the shadow-utils package). Doing so enhances the security of system authentication files. For this reason, the installation program enables shadow passwords by default. The following lists the advantages pf shadow passwords have over the traditional way of storing passwords on UNIX-based systems: Improves system security by moving encrypted password hashes from the world-readable /etc/passwd file to /etc/shadow , which is readable only by the root user. Stores information about password aging. Allows the use the /etc/login.defs file to enforce security policies. Most utilities provided by the shadow-utils package work properly whether or not shadow passwords are enabled. However, since password aging information is stored exclusively in the /etc/shadow file, any commands which create or modify password aging information do not work. The following is a list of commands which do not work without first enabling shadow passwords: chage gpasswd /usr/sbin/usermod -e or -f options /usr/sbin/useradd -e or -f options

Commands:
Chapter 22. Upgrade Parameters You can modify the behavior of the upgrade process with upgrade parameters. Parameter Description UpgradeInitCommand Command or script snippet to run on all overcloud nodes to initialize the upgrade process. For example, a repository switch. UpgradeInitCommonCommand Common commands required by the upgrades process. This should not normally be modified by the operator and is set and unset in the major-upgrade-composable-steps.yaml and major-upgrade-converge.yaml environment files. UpgradeLeappCommandOptions Additional command line options to append to the Leapp command. UpgradeLeappDebug Print debugging output when running Leapp. The default value is false . UpgradeLeappDevelSkip Skip Leapp checks by setting env variables when running Leapp in development/testing. For example, LEAPP_DEVEL_SKIP_RHSM=1. UpgradeLeappEnabled Use Leapp for operating system upgrade. The default value is false . UpgradeLeappPostRebootDelay Maximum (seconds) to wait for machine to reboot and respond to a test command. The default value is 120 . UpgradeLeappRebootTimeout Timeout (seconds) for the OS upgrade phase via Leapp. The default value is 3600 . UpgradeLeappToInstall List of packages to install after Leapp upgrade. UpgradeLeappToRemove List of packages to remove during Leapp upgrade.

Commands:
Chapter 23. Creating Test Entries The dsctl ldifgen command creates LDIF files with different types of test entries. For example, you can use this LDIF file to populate a test instance or a sub-tree to test the performance of Directory Server with the example entries. You can pass one of the following entry type arguments to dsctl ldifgen : users : Creates an LDIF file that contains user entries. groups : Creates an LDIF file that contains static group and member entries. cos-def : Creates an LDIF file that either contains a classic pointer or an indirect Class of Service (CoS) definition. cos-template : Creates an LDIF file that contains a CoS template. roles : Creates an LDIF file that contains managed, filtered, or indirect role entries. mod-load : Creates an LDIF file that contains modify operations. Import this file using the ldapmodify utility. nested : Creates an LDIF file that contains heavily nested entries in a cascading or fractal tree design. Note The dsctl ldifgen command creates only the LDIF file. To load the file into your Directory Server instance, use the: ldapmodify utility after you created an LDIF file using the mod-load option ldapadd utility for all other options Except for the nested entry type, if you do not provide any command line options, the dsctl ldifgen command uses an interactive mode: 23.1. Creating an LDIF File with Example User Entries Use the dsctl ldifgen users command to create an LDIF file with example user entries. For example, to create an LDIF file named /tmp/users.ldif that adds 100,000 generic users to the dc=example,dc=com suffix, enter: Note that the command creates the following organizational units (OU) and randomly assigns the users to these OUs: ou=accounting ou=product development ou=product testing ou=human resources ou=payroll ou=people ou=groups For further details and other options you can use to create the LDIF file, enter:

Commands:
dsctl instance_name ldifgen entry_type
dsctl instance_name ldifgen users --suffix "dc=example,dc=com" --number 100000 --generic --ldif-file=/tmp/users.ldif
dsctl instance_name ldifgen users --help
Preface The Red Hat Ansible Certified Content Collection for Red Hat JBoss Web Server is a prepackaged Ansible content collection that Red Hat provides. You can use the Red Hat Ansible Certified Content Collection to automate the installation and configuration of the Red Hat JBoss Web Server product. You can also add customized tasks to your playbook to automate the deployment of JBoss Web Server applications either at the same time as the automated product installation or later. Note The rest of this document refers to the Red Hat Ansible Certified Content Collection for Red Hat JBoss Web Server as the JBoss Web Server collection .

Commands:
Chapter 1. New features and enhancements Red Hat JBoss Core Services (JBCS) 2.4.57 Service Pack 6 includes the following new features and enhancements. 1.1. Updated default setting for JkShmFile directive in mod_jdk.conf file In JBCS 2.4.57 Service Pack 6, the JkShmFile directive in the mod_jk.conf file has a default setting of /var/cache/httpd/jk.shm , which helps to ensure successful operation with the default SELinux policies. This enhancement supersedes the behavior in releases where the JkShmFile directive had a default setting of /run/jk.shm . 1.2. Archive file distribution for RHEL 9 provides service pack details in version.txt file The archive file distribution of JBCS 2.4.57 Service Pack 6 for Red Hat Enterprise Linux 9 includes a version.txt file that provides the following service pack details:

Commands:
Red Hat build of Apache httpd packaged with JBoss Core Services SP6
4.218. parted 4.218.1. RHBA-2011:1626 - parted bug fix and enhancement update Updated parted packages that fix three bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The parted packages allow you to create, destroy, resize, move, and copy hard disk partitions. The parted program can be used for creating space for new operating systems, reorganizing disk usage, and copying data to new hard disks. Bug Fixes BZ# 665496 Prior to this update, parted incorrectly calculated the position of the new partition when partitions of 1 or smaller units (eg. 1GB, 0.5GB) were created. As a result, only an extremely small partition was created. This update fixes the snap problem for 1 unit and no longer allows defining units less than 1. The value 0 is still allowed when specifying the start of the device. The smaller units should be used instead of a value smaller than 1. eg. Use 500MB instead of 0.5GB. BZ# 692562 Prior to this update, a cylinder-head-sector (CHS) value was, under certain circumstances, especially with factory partitioned USB drives, not found. As a result, parted threw an assertion when attempting to guess the CHS used to create a partition table, even though it was safe to continue without the CHS information. This update no longer throws an assertion when it cannot guess the CHS values used to create a partition table. BZ# 746098 Prior to this update, several tests of the parted test suite failed when running as root on IBM System z and 64-bit PowerPCs. With this update, the tests run as expected. Enhancement BZ# 711148 GPT disklabels now support the legacy_boot flag to allow bootloaders such as syslinux's hybrid gptmbr to be used on BIOS and EFI systems. It is set with the set command in parted. All parted users are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
1.2.3. The Kernel When the kernel is loaded, it immediately initializes and configures the computer's memory and configures the various hardware attached to the system, including all processors, I/O subsystems, and storage devices. It then looks for the compressed initramfs image(s) in a predetermined location in memory, decompresses it directly to /sysroot/ , and loads all necessary drivers. , it initializes virtual devices related to the file system, such as LVM or software RAID, before completing the initramfs processes and freeing up all the memory the disk image once occupied. The kernel then creates a root device, mounts the root partition read-only, and frees any unused memory. At this point, the kernel is loaded into memory and operational. However, since there are no user applications that allow meaningful input to the system, not much can be done with the system. To set up the user environment, the kernel executes the /sbin/init program.

Commands:
Chapter 7. Unmanaged KIE Server An unmanaged KIE Server is a standalone instance, and therefore must be configured individually using REST/JMS API from KIE Server itself. The configuration is automatically persisted by the server into a file and that is used as the internal server state, in case of restarts. The configuration is updated during the following operations: Deploy KIE container Undeploy KIE container Start KIE container Stop KIE container Note If KIE Server is restarted, it will attempt to re-establish the same state that was persisted before shutdown. Therefore, KIE containers (deployment units) that were running will be started, but the ones that were stopped will not.

Commands:
32.4. Standard Groups Table 32.5, "Standard Groups" lists the standard groups configured by an Everything installation. Groups are stored in the /etc/group file. Table 32.5. Standard Groups Group GID Members root 0 root bin 1 root, bin, daemon daemon 2 root, bin, daemon sys 3 root, bin, adm adm 4 root, adm, daemon tty 5 disk 6 root lp 7 daemon, lp mem 8 kmem 9 wheel 10 root mail 12 mail, postfix, exim news 13 news uucp 14 uucp man 15 games 20 gopher 30 dip 40 ftp 50 lock 54 nobody 99 users 100 rpm 37 utmp 22 floppy 19 vcsa 69 dbus 81 ntp 38 canna 39 nscd 28 rpc 32 postdrop 90 postfix 89 mailman 41 exim 93 named 25 postgres 26 sshd 74 rpcuser 29 nfsnobody 65534 pvm 24 apache 48 xfs 43 gdm 42 htt 101 mysql 27 webalizer 67 mailnull 47 smmsp 51 squid 23 ldap 55 netdump 34 pcap 77 quaggavt 102 quagga 92 radvd 75 slocate 21 wnn 49 dovecot 97 radiusd 95

Commands:
10.4.3. Recording a gdb Backtrace Session Once you have captured the core file, you can view its contents by using gdb , the GNU Debugger. To record a script session of gdb on the core file from the affected system, run the following: This will start a gdb session, while script records it to the appropriate text file. While in gdb , run the following commands: Press ctrl-D to stop the script session and save it to the text file.

Commands:
script /tmp/gdb-rgmanager.txt gdb /usr/sbin/rgmanager /tmp/rgmanager-.core.
(gdb) thread apply all bt full (gdb) quit
2.16. RHEA-2011:0656 - new package: libnes The libnes package is now available. libnes is a userspace hardware driver for use with the libibverbs InfiniBand/iWARP verbs library. This driver enables NetEffect iWARP capable ethernet devices. This update adds the libnes driver to the distribution. (BZ# 664801 ) All users requiring libnes should install this new package, which adds this enhancement.

Commands:
Chapter 6. Configuring the heap size for Red Hat build of OpenJDK application on RHEL You can configure Red Hat build of OpenJDK to use a customized heap size. Procedure Add the maximum heap size option to the java command when running your application. For example, to set the maximum heap size to 100 megabytes, use the -Xmx100m option: Additional resources For more information about the Xmx option, see -Xmxsize in the Java documentation . Revised on 2024-10-29 14:17:48 UTC

Commands:
java -Xmx100m <your_application_name>
Chapter 5. Installing the Load Balancer The following example provides general guidance for configuring an HAProxy load balancer. However, you can install any suitable load balancing software solution that supports TCP forwarding. On a Red Hat Enterprise Linux 7 host, install HAProxy: Install the following package that includes the semanage tool: Configure SELinux to allow HAProxy to bind any port: Configure the load balancer to balance the network load for the ports as described in Table 5.1, "Ports Configuration for the Load Balancer" . For example, to configure ports for HAProxy, edit the /etc/haproxy/haproxy.cfg file to correspond with the table. For more information, see Configuration example for haproxy.cfg for HAProxy load balancer with Satellite 6 in the Red Hat Knowledgebase . Table 5.1. Ports Configuration for the Load Balancer Service Port Mode Balance Mode Destination HTTP 80 TCP roundrobin port 80 on all Capsule Servers HTTPS and RHSM 443 TCP source port 443 on all Capsule Servers AMQP 5647 TCP roundrobin port 5647 on all Capsule Servers Puppet ( Optional ) 8140 TCP roundrobin port 8140 on all Capsule Servers PuppetCA ( Optional ) 8141 TCP roundrobin port 8140 only on the system where you configure Capsule Server to sign Puppet certificates SmartProxy ( Optional for OpenScap ) 9090 TCP roundrobin port 9090 on all Capsule Servers Configure the load balancer to disable SSL offloading and allow client-side SSL certificates to pass through to back end servers. This is required because communication from clients to Capsule Servers depends on client-side SSL certificates. Start and enable the HAProxy service:

Commands:
yum install haproxy
yum install policycoreutils-python
semanage boolean --modify --on haproxy_connect_any
systemctl start haproxy systemctl enable haproxy
Preface Debezium is a set of distributed services that capture row-level changes in your databases so that your applications can see and respond to those changes. Debezium records all row-level changes committed to each database table. Each application reads the transaction logs of interest to view all operations in the order in which they occurred. This guide provides details about using the following Debezium topics: Chapter 1, High level overview of Debezium Chapter 2, Source connectors Chapter 3, Sink connectors Chapter 4, Monitoring Debezium Chapter 5, Debezium logging Chapter 6, Configuring Debezium connectors for your application Chapter 7, Applying transformations to modify messages exchanged with Apache Kafka Chapter 8, Developing Debezium custom data type converters Chapter 9, Using post processors to modify event messages Chapter 10, Debezium Server (Developer Preview) Providing feedback on Red Hat documentation We appreciate your feedback on our documentation. To propose improvements, open a Jira issue and describe your suggested changes. Provide as much detail as possible to enable us to address your request quickly. Prerequisite You have a Red Hat Customer Portal account. This account enables you to log in to the Red Hat Jira Software instance. If you do not have an account, you will be prompted to create one. Procedure Click the following link: Create issue . In the Summary text box, enter a brief description of the issue. In the Description text box, provide the following information: The URL of the page where you found the issue. A detailed description of the issue. You can leave the information in any other fields at their default values. Click Create to submit the Jira issue to the documentation team. Thank you for taking the time to provide feedback.

Commands:
Appendix A. Using your subscription Streams for Apache Kafka is provided through a software subscription. To manage your subscriptions, access your account at the Red Hat Customer Portal. Accessing Your Account Go to access.redhat.com . If you do not already have an account, create one. Log in to your account. Activating a Subscription Go to access.redhat.com . Navigate to My Subscriptions . Navigate to Activate a subscription and enter your 16-digit activation number. Downloading Zip and Tar Files To access zip or tar files, use the customer portal to find the relevant files for download. If you are using RPM packages, this step is not required. Open a browser and log in to the Red Hat Customer Portal Product Downloads page at access.redhat.com/downloads . Locate the Streams for Apache Kafka for Apache Kafka entries in the INTEGRATION AND AUTOMATION category. Select the desired Streams for Apache Kafka product. The Software Downloads page opens. Click the Download link for your component. Installing packages with DNF To install a package and all the package dependencies, use: dnf install <package_name> To install a previously-downloaded package from a local directory, use: dnf install <path_to_download_package> Revised on 2025-03-05 17:44:41 UTC

Commands:
dnf install <package_name>
dnf install <path_to_download_package>
OpenShift Dedicated clusters on GCP OpenShift Dedicated 4 Installing OpenShift Dedicated clusters on GCP Red Hat OpenShift Documentation Team

Commands:
ocm gcp create wif-config --name <wif_name> \ 1 --project <gcp_project_id> \ 2
ocm gcp create wif-config --name <wif_name> \ 1 --project <gcp_project_id> \ 2 --version <osd_version> 3
2024/09/26 13:05:41 Creating workload identity configuration 2024/09/26 13:05:47 Workload identity pool created with name 2e1kcps6jtgla8818vqs8tbjjls4oeub 2024/09/26 13:05:47 workload identity provider created with name oidc 2024/09/26 13:05:48 IAM service account osd-worker-oeub created 2024/09/26 13:05:49 IAM service account osd-control-plane-oeub created 2024/09/26 13:05:49 IAM service account openshift-gcp-ccm-oeub created 2024/09/26 13:05:50 IAM service account openshift-gcp-pd-csi-driv-oeub created 2024/09/26 13:05:50 IAM service account openshift-image-registry-oeub created 2024/09/26 13:05:51 IAM service account openshift-machine-api-gcp-oeub created 2024/09/26 13:05:51 IAM service account osd-deployer-oeub created 2024/09/26 13:05:52 IAM service account cloud-credential-operator-oeub created 2024/09/26 13:05:52 IAM service account openshift-cloud-network-c-oeub created 2024/09/26 13:05:53 IAM service account openshift-ingress-gcp-oeub created 2024/09/26 13:05:55 Role "osd_deployer_v4.18" updated
ocm gcp create wif-config --name <wif_name> \ 1 --project <gcp_project_id> \ 2 --mode=manual
ocm create cluster --interactive 1
ocm create cluster <cluster_name> \ 1 --provider=gcp \ 2 --ccs=true \ 3 --wif-config <wif_name> \ 4 --region <gcp_region> \ 5 --subscription-type=marketplace-gcp \ 6 --marketplace-gcp-terms=true \ 7 --version <version> \ 8 --multi-az=true \ 9 --enable-autoscaling=true \ 10 --min-replicas=3 \ 11 --max-replicas=6 \ 12 --secure-boot-for-shielded-vms=true 13
ocm list clusters --parameter search="gcp.authentication.wif_config_id != ''"
ocm list clusters --parameter search="gcp.authentication.wif_config_id = '<wif_config_id>'" 1
ocm gcp update wif-config <wif_name> \ 1 --version <version> 2
ocm gcp list wif-configs
ocm gcp verify wif-config <wif_config_name>|<wif_config_id> 1
Error: verification failed with error: missing role 'compute.storageAdmin'. Running 'ocm gcp update wif-config' may fix errors related to cloud resource misconfiguration. exit status 1.