Section 8: administration and privileged commands
fidentify – Determine file type using PhotoRec database Synopsis fidentify [–check] [directory|file] fidentify –version Description fidentify identify the file type, the "extension", by using the same database than PhotoRec. When a file or directory is specified, fidentify will output the type of file, or files under the specified directory. If given no arguments, fidentify will output type…
fetchmail_selinux – Security Enhanced Linux Policy for the fetchmail processes Description Security-Enhanced Linux secures the fetchmail processes via flexible mandatory access control. The fetchmail processes execute with the fetchmail_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep…
fetch-crl – retrieve certificate revocation lists Synopsis fetch-crl [-c config] [-v[v..]] [-q] [-h] [–inet6glue] [-l infopath] [-o outputpath] [-s statepath] [-a agingtolerance] [-T httptimeout] [-r randomwait] [-p parallelism] [–formats openssl|pem|der|nss] .. [–define key=value] .. [–cfgdir dirname] Description The fetch-crl utility will retrieve certificate revocation lists (CRLs) for a set of installed trust anchors, based on crl_url files…
fenced_selinux – Security Enhanced Linux Policy for the fenced processes Description Security-Enhanced Linux secures the fenced processes via flexible mandatory access control. The fenced processes execute with the fenced_t SELinux type. You can check if you have these processes running by executing the ps command with the -Z qualifier. For example: ps -eZ | grep…
fenced – the I/O Fencing daemon Synopsis fenced [OPTIONS] Description The fencing daemon, fenced, fences cluster nodes that have failed. Fencing a node generally means rebooting it or otherwise preventing it from writing to storage, e.g. disabling its port on a SAN switch. Fencing involves interacting with a hardware device, e.g. network power switch, SAN…
fence_zvm – I/O Fencing agent for GFS on s390 and zSeries VM clusters Synopsis fence_zvm [OPTION]… Description fence_zvm is an I/O Fencing agent used on a GFS virtual machine in a s390 or zSeries VM cluster. It uses the s3270 program to log the specified virtual machine out of VM. For fence_zvm to execute correctly,…
fence_xvmd – Libvirt-based, general purpose fencing host for virtual machines. Synopsis fence_xvmd [OPTION]… Description fence_xvmd is an I/O Fencing host which resides on bare metal machines and is used in conjunction with the fence_xvm fencing agent. Together, these two programs can be used to fence can be used machines which are part of a cluster….
fence_virt – Fencing agent for virtual machines using VM Channel fence_xvm – Fencing agent for virtual machines using multicast Description fence_virt and fence_xvm are an I/O Fencing agents which can be used with virtual machines. Fence_xvm is backward compatible with fence_xvmd. Fence_virt and fence_xvm talk to fence_virtd, which supports multiple backend plugins, including: – libvirt…
fence_xcat – I/O Fencing agent for xcat environments Synopsis fence_xcat [OPTION]… Description fence_xcat is a wrapper to the rpower(1) command that is distributed with the xCAT project available at http://www.xcat.org. Use of fence_xcat requires that xcat has already been properly configured for your environment. Refer to xCAT(1) for more information on configuring xCAT. fence_xcat accepts…
fence_wti – Fence agent for WTI Description fence_wti is an I/O Fencing agent which can be used with the WTI Network Power Switch (NPS). It logs into an NPS via telnet or ssh and boots a specified plug. Lengthy telnet connections to the NPS should be avoided while a GFS cluster is running because the…
fence_vmware_soap – Fence agent for VMWare over SOAP API Description fence_vmware_soap is an I/O Fencing agent which can be used with the virtual machines managed by VMWare products that have SOAP API v4.1+. Name of virtual machine (-n / port) has to be used in inventory path format (e.g. /datacenter/vm/Discovered virtual machine/myMachine). In the cases…
fence_vmware – Fence agent for VMWare Description fence_vmware is an I/O Fencing agent which can be used with the VMware ESX, VMware ESXi or VMware Server to fence virtual machines. Before you can use this agent, it must be installed VI Perl Toolkit or vmrun command on every node you want to make fencing. VI…
fence_vixel – I/O Fencing agent for Vixel FC switches Synopsis fence_vixel [OPTION]… Description fence_vixel is an I/O Fencing agent which can be used with Vixel FC switches. It logs into a Vixel switch via telnet and removes the specified port from the zone. Removing the zone access from the port disables the port from being…
fence_virtd – Fencing host for virtual machines Description fence_virtd is a host daemon designed to route fencing requests for virtual machines. Fence_virt and fence_xvm talk to fence_virtd, which supports multiple backend plugins, including: – libvirt for single-node operation – Cluster Checkpoints when using Linux-cluster release 3.0.0 or later – libvirt-qpid for multi-node, non-cluster operation For…
fence_virt – Fencing agent for virtual machines using VM Channel fence_xvm – Fencing agent for virtual machines using multicast Description fence_virt and fence_xvm are an I/O Fencing agents which can be used with virtual machines. Fence_xvm is backward compatible with fence_xvmd. Fence_virt and fence_xvm talk to fence_virtd, which supports multiple backend plugins, including: – libvirt…
fence_virsh – Fence agent for virsh Description fence_virsh is an I/O Fencing agent which can be used with the virtual machines managed by libvirt. It logs via ssh to a dom0 and there run virsh command, which does all work. By default, virsh needs root account to do properly work. So you must allow ssh…
fence_tool – a utility for the fenced daemon Synopsis fence_tool [COMMAND] [OPTIONS] Description This utility controls and queries the fenced(8) daemon with the following commands: join join the fence domain. leave leave the fence domain. dump print the fenced internal debug buffer ont stdout. ls display internal fenced state. The leave command will not be…
fence_scsi – Fence agent for SCSI persistent reservation Description fence_scsi is an I/O fencing agent that uses SCSI-3 persistent reservations to control access to shared storage devices. These devices must support SCSI-3 persistent reservations (SPC-3 or greater) as well as the "preempt-and-abort" subcommand. The fence_scsi agent works by having each node in the cluster register…
fence_sanlockd – daemon for fence_sanlock agent Synopsis fence_sanlockd [OPTIONS] Description The fence_sanlockd daemon is used by the fence_sanlock agent. See fence_sanlock(8), for full description. Options -D Enable debugging to stderr and don’t fork. -p path Path to shared storage with sanlock leases. -i host_id Local sanlock host_id (1-128). -w Wait for fence_sanlockd -s to send options (p,i)….
fence_sanlock – fence agent using watchdog and shared storage leases Synopsis fence_sanlock [OPTIONS] Description fence_sanlock uses the watchdog device to reset nodes, in conjunction with three daemons: fence_sanlockd, sanlock, and wdmd. The watchdog device, controlled through /dev/watchdog, is available when a watchdog kernel module is loaded. A module should be loaded for the available hardware….