All of lore.kernel.org
 help / color / mirror / Atom feed
From: jbrassow@sourceware.org <jbrassow@sourceware.org>
To: lvm-devel@redhat.com
Subject: LVM2/man cmirrord.8.in
Date: 22 Jan 2010 21:48:17 -0000	[thread overview]
Message-ID: <20100122214817.29882.qmail@sourceware.org> (raw)

CVSROOT:	/cvs/lvm2
Module name:	LVM2
Changes by:	jbrassow at sourceware.org	2010-01-22 21:48:17

Modified files:
	man            : cmirrord.8.in 

Log message:
	a little more information for the cmirrord man page

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/cmirrord.8.in.diff?cvsroot=lvm2&r1=1.2&r2=1.3

--- LVM2/man/cmirrord.8.in	2010/01/20 15:17:25	1.2
+++ LVM2/man/cmirrord.8.in	2010/01/22 21:48:17	1.3
@@ -7,7 +7,24 @@
 
 .SH DESCRIPTION
 cmirrord is the daemon that tracks mirror log information in a cluster.
-Cluster mirrors are not possible without this daemon running.
+It is specific to device-mapper based mirrors (and by extension, LVM
+cluster mirrors).  Cluster mirrors are not possible without this daemon
+running.
+
+This daemon relies on the cluster infrastructure provided by the
+Cluster MANager (CMAN), which must be set up and running in order for
+cmirrord to function.  (The cluster infrastructure is also required for
+clvmd.)
+
+Output is logged via syslog.  The USR1 signal can be issued to cmirrord
+to gather current status information for debugging purposes.
+
+Once started, cmirrord will run until it is shutdown via INT signal.  If
+there are still active cluster mirrors, however, the signal will be
+ignored.  Active cluster mirrors should be shutdown before stopping the
+cluster mirror log daemon.
 
 .SH SEE ALSO
+.BR lvm (8)
 .BR clvmd (8)
+.BR cluster.conf (5)
\ No newline at end of file



             reply	other threads:[~2010-01-22 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-22 21:48 jbrassow [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-01-20 15:17 LVM2/man cmirrord.8.in jbrassow

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20100122214817.29882.qmail@sourceware.org \
    --to=jbrassow@sourceware.org \
    --cc=lvm-devel@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.