mtpti5iD/redhat-docs_dataset huggingface dataset:
7.4. CIFS Common Internet File System (CIFS), an implementation of the Server Message Block (SMB) protocol, is used to share file systems, printers, or serial ports over a network. Notably, CIFS allows sharing files between Linux and Windows platforms regardless of version. Red Hat recommends using CIFS with the Red Hat Enterprise Linux 6.6 or later with support for asynchronous reads and writes that increase the speed of data I/O. Read and Write Size Use the rsize= value_in_bytes option to set the network read size. The recommended size is 1 MiB for servers that support the POSIX extension, for example Samba, and 60 KiB for Windows servers. Use the wsize= value_in_bytes option to set the default network write size. The recommended size is 1 MiB for servers that support the POSIX extension, for example Samba, and 65 KiB for Windows servers. CIFS Installation Considerations Note that if your CIFS server is a Windows system, there is a long-standing issue that causes large reads to fail because Windows only supports a 60 KiB read and write blocks. If your workload is write-heavy and asynchronous, tune dirty pages to flush early and often. The following configuration allows for 512 MB of dirty pages, writes block at 1 GB of dirty pages, and page flushing happens every 5 seconds for dirty pages older than 2.5 seconds: File sharing can vary between tasks significantly. For example, an 8-KiB direct database I/O is an entirely different workload from a large streaming asynchronous write from backup software. When testing, use the actual production workload, preferably with a repeatable replay of the same production work, change only one thing at a time, and record all results for later analysis. Caching The following caching options are available: cache=none - disables caching. Applications have to wait while data is being sent. cache=loose - enables caching while increasing the danger of data corruption. cache=strict - adheres strictly to the protocol requirements where caching is regulated by the server. You can set the cache=strict option in Red Hat Enterprise Linux 6.6 and later. The cache=loose option is set by default in Red Hat Enterprise Linux 6. Using cache=strict is recommended, as cache=strict helps to reduce data corruption, although performance is slightly impacted. Mounting CIFS For instructions on how to mount CIFS, see section 9.3. SMB in the Red Hat Storage Administration Guide .

Commands:
vm.dirty_background_bytes=536870912 vm.dirty_bytes=1073741824 vm.dirty_expire_centisecs=250 vm.dirty_writeback_centisecs=500
Chapter 7. Adding a printer to CUPS by using the lpadmin utility Before users can print through CUPS, you must add printers. You can use both network printers and printers that are directly attached to the CUPS host, for example over USB. You can add printers by using the CUPS driverless feature or by using a PostScript Printer Description (PPD) file. Note CUPS prefers driverless printing, and using drivers is deprecated. Red Hat Enterprise Linux (RHEL) does not provide the name service switch multicast DNS plug-in ( nss-mdns ), which resolves requests by querying an mDNS responder. Consequently, automatic discovery and installation for local driverless printers by using mDNS is not available in RHEL. To work around this problem, install single printers manually or use cups-browsed to automatically install a high amount of print queues that are available on a remote print server. Prerequisites CUPS is configured . The printer supports driverless printing , if you want to use this feature. The printer accepts data on port 631 (IPP), 9100 (socket), or 515 (LPD). The port depends on the method you use to connect to the printer. Procedure Add the printer to CUPS: To add a printer with driverless support, enter: If the -m everywhere option does not work for your printer, try -m driverless: <uri> , for example: -m driverless: ipp://192.0.2.200/ipp/print . To add a queue from a remote print server with driverless support, enter: If the -m everywhere option does not work for your printer, try -m driverless: <uri> , for example: -m driverless: ipp://192.0.2.200/printers/example-queue . To add a printer with a driver in file, enter: To add a queue from a remote print server with a driver in a file, enter: To add a printer with a driver in the local driver database: List the drivers in the database: Add the printer with the URI to the driver in the database: These commands uses the following options: -p <printer_name> : Sets the name of the printer in CUPS. -E : Enables the printer and CUPS accepts jobs for it. Note that you must specify this option after -p . See the option's description in the man page for further details. -v <uri> : Sets the URI to the printer or remote print server queue. -m <driver_uri> : Sets the PPD file based on the provided driver URI obtained from the local driver database. -P <PPD_file> : Sets the path to the PPD file. Verification Display the available printers: Print a test page:

Commands:
lpadmin -p Demo-printer -E -v ipp://192.0.2.200/ipp/print -m everywhere
lpadmin -p Demo-printer -E -v ipp://192.0.2.201/printers/example-queue -m everywhere
lpadmin -p Demo-printer -E -v socket://192.0.2.200/ -P /root/example.ppd
lpadmin -p Demo-printer -E -v ipp://192.0.2.201/printers/example-queue -P /root/example.ppd
lpinfo -m drv:///sample.drv/generpcl.ppd Generic PCL Laser Printer
lpadmin -p Demo-printer -E -v socket://192.0.2.200/ -m drv:///sample.drv/generpcl.ppd
lpstat -p printer Demo-printer is idle. enabled since Fri 23 Jun 2023 09:36:40 AM CEST
lp -d Demo-printer /usr/share/cups/data/default-testpage.pdf
12.5.3. Deleting a Storage Pool Using virt-manager This procedure demonstrates how to delete a storage pool. To avoid any issues with other guest virtual machines using the same pool, it is best to stop the storage pool and release any resources in use by it. To do this, select the storage pool you want to stop and click the red X icon at the bottom of the Storage window. Figure 12.23. Stop Icon Delete the storage pool by clicking the Trash can icon. This icon is only enabled if you stop the storage pool first.

Commands:
5.84. gimp 5.84.1. RHSA-2012:1180 - Moderate: gimp security update Updated gimp packages that fix three 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 score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) associated with each description below. The GIMP (GNU Image Manipulation Program) is an image composition and editing program. Security Fixes CVE-2012-3481 An integer overflow flaw, leading to a heap-based buffer overflow, was found in the GIMP's GIF image format plug-in. An attacker could create a specially-crafted GIF image file that, when opened, could cause the GIF plug-in to crash or, potentially, execute arbitrary code with the privileges of the user running the GIMP. CVE-2011-2896 A heap-based buffer overflow flaw was found in the Lempel-Ziv-Welch (LZW) decompression algorithm implementation used by the GIMP's GIF image format plug-in. An attacker could create a specially-crafted GIF image file that, when opened, could cause the GIF plug-in to crash or, potentially, execute arbitrary code with the privileges of the user running the GIMP. CVE-2012-3403 A heap-based buffer overflow flaw was found in the GIMP's KiSS CEL file format plug-in. An attacker could create a specially-crafted KiSS palette file that, when opened, could cause the CEL plug-in to crash or, potentially, execute arbitrary code with the privileges of the user running the GIMP. Red Hat would like to thank Matthias Weckbecker of the SUSE Security Team for reporting the CVE-2012-3481 issue. Users of the GIMP are advised to upgrade to these updated packages, which contain backported patches to correct these issues. The GIMP must be restarted for the update to take effect.

Commands:
8.9. Configure ODBC Options on Red Hat Enterprise Linux Procedure 8.3. Configure ODBC Options on Red Hat Enterprise Linux Install the driver manager: Verify that your PostGreSQLdriver has installed correctly: To create the DSN, open the configuration file in a text editor: Note You must either use sudo or be logged in as root to open this file. Add the following configuration settings to the file: Save the file and exit the text editor. Run this command to test the DSN: To connect without DSN, use this DSN-less connection string: If you run isql but you encounter an error whereby you see this message: "Can't open lib '/opt/redhat/jboss-dv/v6/psqlodbc/lib64/psqlodbc.so' : file not found" it means that some of the postgres libraries are missing. To fix this issue, run this command as root: yum install postgres To verify that the packages are now installed, run this command: rpm -qa|grep post You should see the postgresql and postgresql-jdbc packages listed.

Commands:
install unixODBC
odbcinst -q -d
sudo vi /opt/redhat/odbc.ini
[<DSN name>] Driver = /usr/lib/psqlodbc.so Description = PostgreSQL Data Source Servername = <Teiid Host name or ip> Port = 35432 Protocol = 7.4 UserName = <user-name> Password = <password> Database = <vdb-name> ReadOnly = no ServerType = Postgres ConnSettings = UseServerSidePrepare=1 ByteaAsLongVarBinary=1 Optimizer=0 Ksqo=0 Trace = No TraceFile = /var/log/trace.log Debug = No DebugFile = /var/log/debug.log
isql <DSN-name> [<user-name> <password>] < commands.sql
ODBC;DRIVER={PostgreSQL};DATABASE=<vdb-name>;SERVER=<host-name>;PORT=<port>;Uid=<username>;Pwd=<password>
7.6. Printer Languages and Technologies Before the advent of laser and inkjet technology, impact printers could only print standard, justified text with no variation in letter size or font style. Today, printers are able to process complex documents with embedded images, charts, and tables in multiple frames and in several languages, all on one page. Such complexity must adhere to some format conventions. This is what spurred the development of the page description language (or PDL) -- a specialized document formatting language specially made for computer communication with printers. Over the years, printer manufacturers have developed their own proprietary languages to describe document formats. However, such proprietary languages applied only to the printers that the manufacturers created themselves. If, for example, you were to send a print-ready file using a proprietary PDL to a professional press, there was no guarantee that your file would be compatible with the printer's machines. The issue of portability came into question. Xerox (R) developed the Interpress TM protocol for their line of printers, but full adoption of the language by the rest of the printing industry was never realized. Two original developers of Interpress left Xerox and formed Adobe (R), a software company catering mostly to electronic graphics and document professionals. At Adobe, they developed a widely-adopted PDL called PostScript TM , which uses a markup language to describe text formatting and image information that could be processed by printers. At the same time, the Hewlett-Packard (R) Company developed the Printer Control Language TM (or PCL) for use in their ubiquitous laser and inkjet printer lines. PostScript and PCL are now widely adopted PDLs and are supported by most printer manufacturers. PDLs work on the same principle as computer programming languages. When a document is ready for printing, the PC or workstation takes the images, typographical information, and document layout, and uses them as objects that form instructions for the printer to process. The printer then translates those objects into rasters , a series of scanned lines that form an image of the document (called Raster Image Processing or RIP), and prints the output onto the page as one image, complete with text and any graphics included. This process makes printed documents more consistent, resulting in little or no variation when printing the same document on different model printers. PDLs are designed to be portable to any format, and scalable to fit different paper sizes. Choosing the right printer is a matter of determining what standards the various departments in your organization have adopted for their needs. Most departments use word processing and other productivity software that use the PostScript language for outputting to printers. However, if your graphics department requires PCL or some proprietary form of printing, you must take that into consideration as well.

Commands:
7.86. iptables 7.86.1. RHBA-2015:1404 - iptables bug fix and enhancement update Updated iptables packages that fix several bugs and add two enhancements are now available for Red Hat Enterprise Linux 6. The iptables utility controls the network packet filtering code in the Linux kernel. Bug Fixes BZ# 1081422 Previously, no iptables revision was used for rules that match an ipset. As a consequence, iptables rules with the match-set option could be added, but not removed again, as the rules could not be located again for their removal. This update adds revision 0 and 1 code patches for libipt_SET. As a result, new ipset match rules can now be removed. Please note that adding and removing rules using the match-set option now works with the patch applied, but removing a rule that was added with an earlier version of iptables does not work and cannot be fixed. Use the rule number to remove such rules. BZ# 1088400 In iptables version 1.4.7-9, the use of alternatives was introduced. Because of the use of versioned (/lib*/xtables-%{version}) custom plug-ins, the plug-ins had to be placed in the appropriate versioned plug-in directory. Starting with iptables version 1.4.7-10, the plug-in directory was reverted back to /lib*/xtables/, but custom plug-ins from iptables version 1.4.7-9 were not copied over. Consequently, upgrading iptables 1.4.7-9 to a newer version led to a loss of custom plug-ins. A plug-in update trigger which detects updates to iptables from version 1.4.7-15 and lower has been added. As a result, custom plug-ins from the /%{_lib}/xtables-1.4.7/ directory are copied to the /%{_lib}/xtables/ directory if the plug-in in /%{_lib}/xtables-1.4.7/ has a newer file date or if it does not exist in the destination directory while updating from iptables version earlier than 1.4.7-15 to a newer version. BZ# 1084974 Previously, a space after Datagram Congestion Control Protocol (DCCP) packet types for print and save was missing, which led to malformed output. With this update, a space has been added at the end of the print_types() function output. As a result, the output of the "iptables -L", "iptables -S", and iptables-save commands is now correct. BZ# 1081191 Previously, some init script warning messages for a failed euid 0 check (no configuration file and nothing to save) were missing. Consequently, only exit status codes were provided in these cases, but no messages. This update adds the warning messages that are now provided in the described situation. Enhancements BZ# 1161330 This update adds support for IPv6 ipset, as ipsets were not previously usable in IPv6 firewall rules. BZ# 1088361 This update adds support for the "-C" check option for the ip*tables commands. Previously, there was no simple way to check if a certain rule exists. Now, the "-C" option can be used in a rule to check if a rule exists. Users of iptables are advised to upgrade to these updated packages, which fix these bugs and add these enhancements.

Commands:
4.9.2. Tune GFS atime Quantum When atime updates are enabled, GFS (by default) only updates them once an hour. The time quantum is a tunable parameter that can be adjusted using the gfs_tool command. Each GFS node updates the access time based on the difference between its system time and the time recorded in the inode. It is required that system clocks of all GFS nodes in a cluster be synchronized. If a node's system time is out of synchronization by a significant fraction of the tunable parameter, atime_quantum , then atime updates are written more frequently. Increasing the frequency of atime updates may cause performance degradation in clusters with heavy work loads. By using the gettune flag of the gfs_tool command, all current tunable parameters including atime_quantum (default is 3600 seconds) are displayed. The gfs_tool settune command is used to change the atime_quantum parameter value. It must be set on each node and each time the file system is mounted. (The setting is not persistent across unmounts.) Usage Displaying Tunable Parameters MountPoint Specifies the directory where the GFS file system is mounted. Changing the atime_quantum Parameter Value MountPoint Specifies the directory where the GFS file system is mounted. Seconds Specifies the update period in seconds. Examples In this example, all GFS tunable parameters for the file system on the mount point /gfs1 are displayed. In this example, the atime update period is set to once a day (86,400 seconds) for the GFS file system on mount point /gfs1 .

Commands:
gfs_tool gettune MountPoint
gfs_tool settune MountPoint atime_quantum Seconds
gfs_tool gettune /gfs1
gfs_tool settune /gfs1 atime_quantum 86400
8.106. keyutils 8.106.1. RHBA-2014:1610 - keyutils bug fix update Updated keyutils packages that fix one bug are now available for Red Hat Enterprise Linux 6. The keyutils packages provide utilities to control the Linux kernel key management facility and to provide a mechanism by which the kernel calls up to user space to get a key instantiated. Bug Fix BZ# 1075652 Previously, the "keyctl show" command incorrectly displayed an abbreviated tree of nested keyrings and therefore the keyring trees that were more than two keyrings deep were not fully displayed. This bug has been fixed and "keyctl show" now displays entire keyring trees as expected. Moreover, the "keyctl show" command did not expand the field width to show the full decimal key ID. With this update, the key ID field is expanded correctly. Also, the maximum size of input data for the "keyctl padd" command and other pipe-in commands has been increased to 1MB. Finally, the "keyctl padd" command as well as other pipe-in commands have been modified not to specially handle zero-value bytes in binary input. Users of keyutils are advised to upgrade to these updated packages, which fix this bug.

Commands:
Part I. Creating a filtered or unfiltered AWS cloud integration Before you create an AWS integration, first decide if you want to create a filtered or unfiltered integration. Unfiltered flow An unfiltered integration enables cost management to directly read your billing reports from AWS. You can select the scope of the reports later on. To create an unfiltered integration, go to Creating an unfiltered AWS integration . Filtered flow A filtered integration enables you to customize and filter your data before cost management reads it. Some customers use the filtered integration to share billing data to only certain Red Hat products. It is more complex to set up and configure a filtered integration than an unfiltered one. To create a filtered integration, go to Creating a filtered AWS integration . Note You must create either a filtered or unfiltered integration. Do not follow both sets of instructions.

Commands:
15.5. vsftpd Configuration Options Although vsftpd may not offer the level of customization other widely available FTP servers have, it offers enough options to fill most administrator's needs. The fact that it is not overly feature-laden limits configuration and programmatic errors. All configuration of vsftpd is handled by its configuration file, /etc/vsftpd/vsftpd.conf . Each directive is on its own line within the file and follows the following format: For each directive, replace <directive> with a valid directive and <value> with a valid value. Important There must not be any spaces between the <directive> , equal symbol, and the <value> in a directive. Comment lines must be preceded by a hash mark ( # ) and are ignored by the daemon. For a complete list of all directives available, refer to the man page for vsftpd.conf . Important For an overview of ways to secure vsftpd , refer to the chapter titled Server Security in the Security Guide . The following is a list of some of the more important directives within /etc/vsftpd/vsftpd.conf . All directives not explicitly found within vsftpd 's configuration file are set to their default value. 15.5.1. Daemon Options The following is a list of directives which control the overall behavior of the vsftpd daemon. listen - When enabled, vsftpd runs in stand-alone mode. Red Hat Enterprise Linux sets this value to YES . This directive cannot be used in conjunction with the listen_ipv6 directive. The default value is NO . listen_ipv6 - When enabled, vsftpd runs in stand-alone mode, but listens only to IPv6 sockets. This directive cannot be used in conjunction with the listen directive. The default value is NO . session_support - When enabled, vsftpd attempts to maintain login sessions for each user through Pluggable Authentication Modules (PAM). Refer to Chapter 16, Pluggable Authentication Modules (PAM) for more information. If session logging is not necessary, disabling this option allows vsftpd to run with less processes and lower privileges. The default value is YES .

Commands:
<directive> = <value>
Chapter 1. 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 10, 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
8.3. Booleans SELinux is based on the least level of access required for a service to run. Services can be run in a variety of ways; therefore, you need to specify how you run your services. Use the following Booleans to set up SELinux: squid_connect_any When enabled, this Boolean permits squid to initiate a connection to a remote host on any port. Note Due to the continuous development of the SELinux policy, the list above might not contain all Booleans related to the service at all times. To list them, run the following command as root:

Commands:
~]# semanage boolean -l | grep service_name
Chapter 1. How to use this guide An Identity Management (IdM) domain includes IdM servers, also called replicas, and IdM clients. While installing an IdM deployment always starts with installing the primary IdM server, the order of the installation steps depends on the targeted topology. For example, you can install an IdM replica before or after installing an IdM client. Additionally, certain IdM deployments require a trust with Active Directory , while others do not. Additional resources Planning Identity Management

Commands:
Chapter 2. Uninstalling OpenShift Serverless Knative Eventing Before you can remove the OpenShift Serverless Operator, you must remove Knative Eventing. To uninstall Knative Eventing, you must remove the KnativeEventing custom resource (CR) and delete the knative-eventing namespace. 2.1. Uninstalling Knative Eventing Prerequisites You have cluster administrator permissions on OpenShift Container Platform, or you have cluster or dedicated administrator permissions on OpenShift Dedicated. Install the OpenShift CLI ( oc ). Procedure Delete the KnativeEventing CR: USD oc delete knativeeventings.operator.knative.dev knative-eventing -n knative-eventing After the command has completed and all pods have been removed from the knative-eventing namespace, delete the namespace: USD oc delete namespace knative-eventing

Commands:
oc delete knativeeventings.operator.knative.dev knative-eventing -n knative-eventing
oc delete namespace knative-eventing