dmeventd(8) [centos man page]

DMEVENTD(8)						      System Manager's Manual						       DMEVENTD(8)

NAME

       dmeventd - Device-mapper event daemon

SYNOPSIS

       dmeventd [-d [-d [-d]]] [-f] [-h] [-R] [-V] [-?]

DESCRIPTION

       dmeventd  is the event monitoring daemon for device-mapper devices.  Library plugins can register and carry out actions triggered when par-
       ticular events occur.

LVM PLUGINS

       Mirror Attempts to handle device failure automatically.	See lvm.conf(5).

       Raid   Attempts to handle device failure automatically.	See lvm.conf(5).

       Snapshot
	      Monitors how full a snapshot is becoming and emits a warning to syslog when it exceeds 80% full.	The warning is repeated when  85%,
	      90% and 95% of the snapshot is filled.  See lvm.conf(5).

       Thin   Monitors how full a thin pool is becoming and emits a warning to syslog when it exceeds 80% full.  The warning is repeated when 85%,
	      90% and 95% of the thin pool is filled.  See lvm.conf(5).

OPTIONS

       -d     Repeat from 1 to 3 times (-d, -dd, -ddd) to increase the detail of debug messages sent to syslog.  Each extra d adds more  debugging
	      information.

       -f     Don't fork, run in the foreground.

       -h, -? Show help information.

       -R     Replace  a running dmeventd instance. The running dmeventd must be version 2.02.77 or newer. The new dmeventd instance will obtain a
	      list of devices and events to monitor from the currently running daemon.

       -V     Show version of dmeventd.

SEE ALSO

       lvm(8), lvm.conf(5)

Red Hat Inc					      DM TOOLS 2.02.105(2)-RHEL7 (2014-03-26)					       DMEVENTD(8)

LVMETAD(8)						      System Manager's Manual							LVMETAD(8)

NAME

       lvmetad - LVM metadata cache daemon

SYNOPSIS

       lvmetad [-l {all|wire|debug}] [-p pidfile_path] [-s socket_path] [-f] [-h] [-V] [-?]

DESCRIPTION

       lvmetad	is  a  metadata caching daemon for LVM. The daemon receives notifications from udev rules (which must be installed for LVM to work
       correctly when lvmetad is in use). Through these notifications, lvmetad has an up-to-date and consistent image of the volume groups  avail-
       able in the system.

       By default, lvmetad, even if running, is not used by LVM. See lvm.conf(5).

OPTIONS

       To run the daemon in a test environment both the pidfile_path and the socket_path should be changed from the defaults.

       -f     Don't fork, but run in the foreground.

       -h, -? Show help information.

       -l {all|wire|debug}
	      Select  the  type of log messages to generate.  Messages are logged by syslog.  Additionally, when -f is given they are also sent to
	      standard error.  Since release 2.02.98, there are two classes of messages: wire and debug.  Selecting 'all'  supplies  both  and	is
	      equivalent  to  a comma-separated list -l wire,debug.  Prior to release 2.02.98, repeating -d from 1 to 3 times, viz. -d, -dd, -ddd,
	      increased the detail of messages.

       -p pidfile_path
	      Path to the pidfile. This  overrides  both  the  built-in  default  (#DEFAULT_PID_DIR#/lvmetad.pid)  and	the  environment  variable
	      LVM_LVMETAD_PIDFILE.  This file is used to prevent more than one instance of the daemon running simultaneously.

       -s socket_path
	      Path  to	the  socket  file.  This  overrides  both  the	built-in  default  (/run/lvm/lvmetad.socket)  and the environment variable
	      LVM_LVMETAD_SOCKET.  To communicate successfully with lvmetad, all LVM2 processes should use the same socket path.

       -V     Display the version of lvmetad daemon.

ENVIRONMENT VARIABLES

       LVM_LVMETAD_PIDFILE
	      Path for the pid file.

       LVM_LVMETAD_SOCKET
	      Path for the socket file.

SEE ALSO

       lvm(8), lvm.conf(5)

Red Hat Inc					     LVM TOOLS 2.02.105(2)-RHEL7 (2014-03-26)						LVMETAD(8)