mtpti5iD/redhat-docs_dataset huggingface dataset:
10.3. Using the Cache With NFS NFS will not use the cache unless explicitly instructed. To configure an NFS mount to use FS-Cache, include the -o fsc option to the mount command: All access to files under /mount/point will go through the cache, unless the file is opened for direct I/O or writing (refer to Section 10.3.2, "Cache Limitations With NFS" for more information). NFS indexes cache contents using NFS file handle, not the file name; this means that hard-linked files share the cache correctly. Caching is supported in version 2, 3, and 4 of NFS. However, each version uses different branches for caching. 10.3.1. Cache Sharing There are several potential issues to do with NFS cache sharing. Because the cache is persistent, blocks of data in the cache are indexed on a sequence of four keys: Level 1: Server details Level 2: Some mount options; security type; FSID; uniquifier Level 3: File Handle Level 4: Page number in file To avoid coherency management problems between superblocks, all NFS superblocks that wish to cache data have unique Level 2 keys. Normally, two NFS mounts with same source volume and options will share a superblock, and thus share the caching, even if they mount different directories within that volume. Example 10.1. Cache sharing Take the following two mount commands: mount home0:/disk0/fred /home/fred -o fsc mount home0:/disk0/jim /home/jim -o fsc Here, /home/fred and /home/jim will likely share the superblock as they have the same options, especially if they come from the same volume/partition on the NFS server ( home0 ). Now, consider the two subsequent mount commands: mount home0:/disk0/fred /home/fred -o fsc,rsize=230 mount home0:/disk0/jim /home/jim -o fsc,rsize=231 In this case, /home/fred and /home/jim will not share the superblock as they have different network access parameters, which are part of the Level 2 key. The same goes for the following mount sequence: mount home0:/disk0/fred /home/fred1 -o fsc,rsize=230 mount home0:/disk0/fred /home/fred2 -o fsc,rsize=231 Here, the contents of the two subtrees ( /home/fred1 and /home/fred2 ) will be cached twice . Another way to avoid superblock sharing is to suppress it explicitly with the nosharecache parameter. Using the same example: mount home0:/disk0/fred /home/fred -o nosharecache,fsc mount home0:/disk0/jim /home/jim -o nosharecache,fsc However, in this case only one of the superblocks will be permitted to use cache since there is nothing to distinguish the Level 2 keys of home0:/disk0/fred and home0:/disk0/jim . To address this, add a unique identifier on at least one of the mounts, i.e. fsc= unique-identifier . For example: mount home0:/disk0/fred /home/fred -o nosharecache,fsc mount home0:/disk0/jim /home/jim -o nosharecache,fsc=jim Here, the unique identifier jim will be added to the Level 2 key used in the cache for /home/jim .

Commands:
mount nfs-share :/ /mount/point -o fsc
2.5. Repeating the Site Survey There may need to be more than one site survey, particularly if an enterprise has offices in multiple cities or countries. The informational needs might be so complex that several different organizations have to keep information at their local offices rather than at a single, centralized site. In this case, each office that keeps a main copy of information should perform its own site survey. After the site survey process has been completed, the results of each survey should be returned to a central team (probably consisting of representatives from each office) for use in the design of the enterprise-wide data schema model and directory tree.

Commands:
Chapter 43. Role-based access control for branches in Business Central Business Central provides the option for users to restrict the access for a target branch for a specific collaborator type. The security check uses both the Security Management screen and contributors sources to grant or deny permissions to spaces and projects. For example, if a user has the security permission to update a project and has write permission on that branch, based on the contributor type, then they are able to create new assets. 43.1. Customizing role-based branch access You can customize contributor role permissions for each branch of a project in Business Central. For example, you can set Read , Write , Delete , and Deploy access for each role assigned to a branch. Procedure In Business Central, go to Menu Design Projects . If needed, add a new contributor: Click the project name and then click the Contributors tab. Click Add Contributor . Enter user name in the text field. Select the Contributor role type from the drop-down list. Click Ok . Customize role-based branch access for the relevant contributor: Click Settings Branch Management . Select the branch name from the drop-down list. In the Role Access section, select or deselect the permissions check boxes to specify role-based branch access for each available role type. Click Save and click Save again to confirm your changes.

Commands:
3.2. Text-Based Installer You can install Red Hat JBoss Data Virtualization using the text-based installer. In this mode, you run the installation steps without stepping through the graphical wizard. The GUI installer will run in text mode automatically if no display server is available. Prerequisites You must have already downloaded the Red Hat JBoss Data Virtualization jar file from the Customer Portal . Procedure 3.2. Install JBoss Data Virtualization Open a terminal window and navigate to the location where the GUI installer was downloaded. Start the installation process: Follow the installation prompts displayed on the terminal. You can either install with default configuration or you can complete additional configuration steps. Finally, generate the automatic installation script. You can use this script to perform headless installation or identical installations across multiple instances.

Commands:
java -jar jboss-dv- VERSION -installer.jar -console
7.109. libcgroup 7.109.1. RHBA-2013:0452 - libcgroup bug fix and enhancement update Updated libcgroup packages that fix several bugs and add one enhancement are now available for Red Hat Enterprise Linux 6. The libcgroup packages provide tools and libraries to control and monitor control groups. Bug Fixes BZ#773544 Previously, the cgrulesengd daemon ignored the "--sticky" option of the cgexec command and, as a consequence, moved a process to another cgroup when the process called the setuid() or setgid() functions even if the process had to be stuck to the current cgroup. This bug is now fixed and the cgrulesengd daemon now checks whether the process is "sticky" or not when the process calls setuid or setgid. BZ# 819137 Previously, the lscgroup command dropped the first character of a path unless prefixed with a slash, which led to lscgroup generating invalid paths. This bug is now fixed and the generated paths are now correct. BZ#849757 Previously, adding a cgroup after the cgrulesengd daemon had started did not work. As a consequence, if a directory was created after cgrulesengd was already started, any /etc/cgrules.conf configuration for that directory would not be processed. With this update, a routine has been added to scan the cgrules.conf file and move matching running tasks in the /proc/pid/ directory into configured cgroups. This new routine is called at init time and also after inotify events on cgroups. With this update, a routine has been added to scan the cgrules.conf file and move matching running tasks into configured cgroups. BZ# 869990 Previously, the cgconfig service was not working properly with read-only file systems. As a consequence, cgconfig was not able to start with the default configuration on a Red Hat Enterprise Virtualization Hypervisor system. This update adds a check for the read-only file systems to the cgconfig service and it now works as expected with the default configuration on Red Hat Enterprise Virtualization Hypervisor systems. Enhancement BZ#738737 This update improves the logging facility and error messages generated by libcgroup. Users of libcgroup are advised to upgrade to these updated packages, which fix these bugs and add this enhancement.

Commands:
8.255. virt-who 8.255.1. RHBA-2014:1513 - virt-who bug fix and enhancement update Updated virt-who package that fixes several bugs and adds various enhancements is now available for Red Hat Enterprise Linux 6. The virt-who package provides an agent that collects information about virtual guests present in the system and reports them to the Red Hat Subscription Manager tool. This update also fixes the following bugs: Note The virt-who package has been upgraded to upstream version 0.10, which provides a number of bug fixes and enhancements over the version. This update includes support for multiple vCenter servers, fixed querying by cluster in large ESX environments, corrected communication with Red Hat Satellite server when ESXi has no host, fixed unregistering from Subscription Asset Manager (SAM) server, fixed bug in Virtual Desktop and Server Management (VDSM) mode, support for encrypted credentials, and fixed error when creating new VMs. (BZ# 1002640 , BZ# 994575 , BZ# 1002447 , BZ# 1009230 , BZ# 1011877 , BZ# 1017056 , BZ# 1081286 , BZ# 1082416 ) This update also fixes the following bugs: Bug Fixes BZ# 1098019 Previously, the virt-who daemon did not report guest attributes to the server, which disabled the virt_guest_limit feature. With this update, virt-who has been modified to correctly report guest attributes. As a result, virt_guest_limit is now supported by virt-who. BZ# 1113938 Prior to this update, every call to Libvirtd.listDomains() function from the /usr/share/virt-who/virt/libvirtd/libvirtd.py script opened a new connection to the libvirtd daemon but did not close it. Consequently, after several iterations, virt-who consumed all connections allowed for any client of libvirtd. With this update, Libvirtd.listDomains() has been modified to properly close the livirtd connections, thus fixing this bug. The virt-who package has been upgraded to upstream version 0.10, which provides a number of bug fixes and enhancements over the version. This update includes support for multiple vCenter servers, fixed querying by cluster in large ESX environments, corrected communication with Red Hat Satellite server when ESXi has no host, fixed unregistering from Subscription Asset Manager (SAM) server, fixed bug in Virtual Desktop and Server Management (VDSM) mode, support for encrypted credentials, and fixed error when creating new VMs. (BZ#1002640, BZ#994575, BZ#1002447, BZ#1009230, BZ#1011877, BZ#1017056, BZ#1081286, BZ#1082416) Users of virt-who are advised to upgrade to this updated package, which fixes these bugs and add these enhancements.

Commands:
Power Monitoring OpenShift Container Platform 4.15 Configuring and using power monitoring for OpenShift Container Platform Red Hat OpenShift Documentation Team

Commands:
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: port: 9103 1 nodeSelector: kubernetes.io/os: linux 2 Tolerations: 3 - key: "" operator: "Exists" value: "" effect: ""
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler status: exporter: conditions: 1 - lastTransitionTime: '2024-01-11T11:07:39Z' message: Reconcile succeeded observedGeneration: 1 reason: ReconcileSuccess status: 'True' type: Reconciled - lastTransitionTime: '2024-01-11T11:07:39Z' message: >- Kepler daemonset "kepler-operator/kepler" is deployed to all nodes and available; ready 2/2 observedGeneration: 1 reason: DaemonSetReady status: 'True' type: Available currentNumberScheduled: 2 2 desiredNumberScheduled: 2 3
apiVersion: kepler.system.sustainable.computing.io/v1alpha1 kind: Kepler metadata: name: kepler spec: exporter: deployment: redfish: secretRef: <secret_name> required 1 probeInterval: 60s 2 skipSSLVerify: false 3
<your_kubelet_node_name>,<redfish_username>,<redfish_password>,https://<redfish_ip_or_hostname>/
control-plane,exampleuser,examplepass,https://redfish.nodes.example.com worker-1,exampleuser,examplepass,https://redfish.nodes.example.com worker-2,exampleuser,examplepass,https://another.redfish.nodes.example.com
oc -n openshift-power-monitoring create secret generic redfish-secret --from-file=redfish.csv
apiVersion: v1 kind: Secret metadata: name: redfish-secret data: redfish.csv: YmFyCg== #
7.51. evolution-data-server 7.51.1. RHBA-2013:0410 - evolution-data-server bug fix update Updated evolution-data-server packages that fix one bug are now available for Red Hat Enterprise Linux 6. The evolution-data-server packages provide a unified back end for applications which interact with contacts, task and calendar information. Evolution Data Server was originally developed as a back end for Evolution, but is now used by various other applications. Bug Fix BZ# 734048 The CalDav calendar back end was converting Uniform Resource Identifiers (URIs) with unescaped space characters or the "%20" string to "%2520". As a consequence, rendering the back end did not allow to contact the remote CalDav service that caused CalDav calendars to be inaccessible. This bug has been fixed and evolution-data-server works correctly in the described scenario. All users of evolution-data-server are advised to upgrade to these updated packages, which fix this bug.

Commands:
Chapter 6. LVM Configuration Examples This chapter provides some basic LVM configuration examples. 6.1. Creating an LVM Logical Volume on Three Disks This example creates an LVM logical volume called new_logical_volume that consists of the disks at /dev/sda1 , /dev/sdb1 , and /dev/sdc1 . 6.1.1. Creating the Physical Volumes To use disks in a volume group, you label them as LVM physical volumes. Warning This command destroys any data on /dev/sda1 , /dev/sdb1 , and /dev/sdc1 . 6.1.2. Creating the Volume Group The following command creates the volume group new_vol_group . You can use the vgs command to display the attributes of the new volume group. 6.1.3. Creating the Logical Volume The following command creates the logical volume new_logical_volume from the volume group new_vol_group . This example creates a logical volume that uses 2GB of the volume group. 6.1.4. Creating the File System The following command creates a GFS2 file system on the logical volume. The following commands mount the logical volume and report the file system disk space usage.

Commands:
pvcreate /dev/sda1 /dev/sdb1 /dev/sdc1 Physical volume "/dev/sda1" successfully created Physical volume "/dev/sdb1" successfully created Physical volume "/dev/sdc1" successfully created
vgcreate new_vol_group /dev/sda1 /dev/sdb1 /dev/sdc1 Volume group "new_vol_group" successfully created
vgs VG #PV #LV #SN Attr VSize VFree new_vol_group 3 0 0 wz--n- 51.45G 51.45G
lvcreate -L2G -n new_logical_volume new_vol_group Logical volume "new_logical_volume" created
mkfs.gfs2 -plock_nolock -j 1 /dev/new_vol_group/new_logical_volume This will destroy any data on /dev/new_vol_group/new_logical_volume. Are you sure you want to proceed? [y/n] y Device: /dev/new_vol_group/new_logical_volume Blocksize: 4096 Filesystem Size: 491460 Journals: 1 Resource Groups: 8 Locking Protocol: lock_nolock Lock Table: Syncing All Done
mount /dev/new_vol_group/new_logical_volume /mnt df Filesystem 1K-blocks Used Available Use% Mounted on /dev/new_vol_group/new_logical_volume 1965840 20 1965820 1% /mnt
Chapter 21. Executing the MortgageApprovalProcess process application Now that you have deployed the project, you can execute the project's defined functionality. For this tutorial you input data into a mortgage application form acting as the mortgage broker. The MortgageApprovalProcess business process runs and determines whether or not the applicant has offered an acceptable down payment based on the decision rules that you defined earlier. The business process either ends the rule testing or requests that the applicant increase the down payment to proceed. If the application passes the business rule testing, the bank's approver reviews the application and either approve or deny the loan. Prerequisites KIE Server is deployed and connected to Business Central. The Mortgage_Process application has been deployed. The users working on the tasks are members of the following groups and roles: approver group: For the Qualify task broker group: For the Correct Data and Increase Down Payment tasks manager role: For the Final Approval task Procedure Log in to Red Hat Process Automation Manager as Bill (the broker) and click Menu Manage Process Definitions . Click the three vertical dots in the Actions column and select Start to start to open the Application form and input the following values in to the form fields: Down Payment : 30000 Years of amortization : 10 Name : Ivo Annual Income : 60000 SSN : 123456789 Age of property : 8 Address of property : Brno Locale : Rural Property Sale Price : 50000 Click Submit to start a new process instance. After starting the process instance, the Instance Details view opens. Click the Diagram tab to view the process flow within the process diagram. The state of the process is highlighted as it moves through each task. Log out of Business Central and log back in as Katy . Click Menu Track Task Inbox . This takes you to the Qualify form. Click the three vertical dots in the Actions column and select and click Claim . The Qualify task Status is now Reserved . Click the Qualify task row to open and review the task information. Click Claim and then Start at the bottom of the form. The application form is now active for approval or denial. To approve the application, select Is mortgage application in limit? and click Complete . In the Task Inbox , click anywhere in the Final Approval row to open the Final Approval task. In the Final Approval row, click the three vertical dots in the Actions column and click Claim . Click anywhere in the Final Approval row to open the Final Approval task. Click Start at the bottom of the form. Note that the Inlimit check box is selected to reflect that that application is ready for final approval. Click Complete . Note The Save and Release buttons are only used to either pause the approval process and save the instance if you are waiting on a field value, or to release the task for another user to modify.

Commands:
16.9.3. Running virt-inspector You can run virt-inspector against any disk image or libvirt guest virtual machine as shown in the following example: Or as shown here: The result will be an XML report ( report.xml ). The main components of the XML file are a top-level <operatingsystems> element containing usually a single <operatingsystem> element, similar to the following: Processing these reports is best done using W3C standard XPath queries. Red Hat Enterprise Linux 6 comes with a command line program ( xpath ) which can be used for simple instances; however, for long-term and advanced usage, you should consider using an XPath library along with your favorite programming language. As an example, you can list out all file system devices using the following XPath query: Or list the names of all applications installed by entering:

Commands:
virt-inspector --xml disk.img > report.xml
virt-inspector --xml GuestName > report.xml
<operatingsystems> <operatingsystem> <!-- the type of operating system and Linux distribution --> <name>linux</name> <distro>rhel</distro> <!-- the name, version and architecture --> <product_name>Red Hat Enterprise Linux Server release 6.4 </product_name> <major_version>6</major_version> <minor_version>4</minor_version> <package_format>rpm</package_format> <package_management>yum</package_management> <root>/dev/VolGroup/lv_root</root> <!-- how the filesystems would be mounted when live --> <mountpoints> <mountpoint dev="/dev/VolGroup/lv_root">/</mountpoint> <mountpoint dev="/dev/sda1">/boot</mountpoint> <mountpoint dev="/dev/VolGroup/lv_swap">swap</mountpoint> </mountpoints> < !-- filesystems--> <filesystem dev="/dev/VolGroup/lv_root"> <label></label> <uuid>b24d9161-5613-4ab8-8649-f27a8a8068d3</uuid> <type>ext4</type> <content>linux-root</content> <spec>/dev/mapper/VolGroup-lv_root</spec> </filesystem> <filesystem dev="/dev/VolGroup/lv_swap"> <type>swap</type> <spec>/dev/mapper/VolGroup-lv_swap</spec> </filesystem> <!-- packages installed --> <applications> <application> <name>firefox</name> <version>3.5.5</version> <release>1.fc12</release> </application> </applications> </operatingsystem> </operatingsystems>
virt-inspector --xml GuestName | xpath //filesystem/@dev Found 3 nodes: -- NODE -- dev="/dev/sda1" -- NODE -- dev="/dev/vg_f12x64/lv_root" -- NODE -- dev="/dev/vg_f12x64/lv_swap"
virt-inspector --xml GuestName | xpath //application/name [...long list...]
Chapter 4. Connecting to Red Hat Insights through your own proxy You might choose to use your own proxy to act as a gateway between the public Internet and your private network. This is a good security measure to protect your systems from malicious activity. To connect your systems to Red Hat Insights you must add hostnames, ports and allow additional URLs. 4.1. Connecting to Red Hat Insights through your own proxy Note If you are a Red Hat Satellite user, no proxy is required because Satellite serves as a proxy itself. See this article for more information: How to configure Red Hat Satellite 6 with proxy server To connect to Red Hat Insights, include specific hostnames and ports on your proxy's outgoing network. Prerequisites You have at least one active Red Hat Enterprise Linux (RHEL) subscription. You are logged in to the system as root or have sudo permissions. Your system is registered with Red Hat Subscription Manager (RHSM). Procedure You must include the following hostnames and ports on your proxy's outgoing network, to connect to Red Hat Insights: Navigate to your outgoing network configuration and add the following addresses and ports: Add the Red Hat Hybrid Cloud Console URL so that you can manage your account and hosts in the Red Hat Insights Web UI: Add the URL for Single-Sign-On to Red Hat to ensure access to authorization: Each host using your proxy needs the following details added to the /etc/rhsm/rhsm.conf file. Note This information is required for RHSM, Insights client and remote host configuration (rhc). Add your http proxy server's URL: Add the proxy scheme for authorization purposes (http is the default): Add the port for your proxy server: Optional If your proxy requires authentication, add your user name and password for authenticating: Add any domains you want to opt out from the proxy: By default, Insights client uses RHSM's configuration for a proxy. You can edit the insights-client.conf configuration file to change the proxy: Verification step To verify connectivity, open your command line interface (CLI) and run the following command as root: If connectivity is successful, you will see the following output in your CLI: Additional resources Using Red Hat Subscription Manager

Commands:
https://cert-api.access.redhat.com:443
https://cert.cloud.redhat.com:443
https://cert.console.redhat.com:443
https://console.redhat.com:443
https://sso.redhat.com:443
proxy_hostname =
proxy_scheme = http
proxy_port =
proxy_user =
proxy_password =
no_proxy =
/etc/insights-client/insights-client.conf
insights-client --test-connection --net-debug
End API URL Connection Test: SUCCESS Connectivity tests completed successfully See `/var/log/insights-client/insights-client.log` for more details.
8.3.2. Nessus Nessus is a full-service security scanner. The plug-in architecture of Nessus allows users to customize it for their systems and networks. As with any scanner, Nessus is only as good as the signature database it relies upon. Fortunately, Nessus is frequently updated and features full reporting, host scanning, and real-time vulnerability searches. Remember that there could be false positives and false negatives, even in a tool as powerful and as frequently updated as Nessus. Note Nessus is not included with Red Hat Enterprise Linux and is not supported. It has been included in this document as a reference to users who may be interested in using this popular application. For more information about Nessus, refer to the official website at the following URL: http://www.nessus.org/

Commands: