public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: pcaulfield@sourceware.org
To: lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW scripts/clvmd_init_rhel4
Date: Wed, 04 Oct 2006 08:42:00 -0000 [thread overview]
Message-ID: <20061004084214.31337.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: pcaulfield@sourceware.org 2006-10-04 08:42:14
Modified files:
. : WHATS_NEW
scripts : clvmd_init_rhel4
Log message:
Make clvmd restart init script wait until clvmd has died before starting it.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.449&r2=1.450
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/clvmd_init_rhel4.diff?cvsroot=lvm2&r1=1.7&r2=1.8
--- LVM2/WHATS_NEW 2006/10/04 08:22:15 1.449
+++ LVM2/WHATS_NEW 2006/10/04 08:42:14 1.450
@@ -1,5 +1,6 @@
Version 2.02.11 -
=====================================
+ Make clvmd restart init script wait until clvmd has died before starting it.
Add -R to clvmd which tells running clvmds to reload their device cache.
Add LV column to reports listing kernel modules needed for activation.
Show available fields if report given invalid field. (e.g. lvs -o list)
--- LVM2/scripts/clvmd_init_rhel4 2006/07/19 18:55:58 1.7
+++ LVM2/scripts/clvmd_init_rhel4 2006/10/04 08:42:14 1.8
@@ -93,6 +93,24 @@
return $rtrn
}
+wait_for_finish()
+{
+ count=0
+
+ while [ "$count" -le 10 -a -n "`pidof clvmd`" ]
+ do
+ sleep 1
+ count=$((count + 1))
+ done
+
+ if [ `pidof clvmd` ]
+ then
+ return 1
+ else
+ return 0
+ fi
+}
+
rtrn=1
# See how we were called.
@@ -112,6 +130,7 @@
restart)
if stop
then
+ wait_for_finish
start
fi
rtrn=$?
next reply other threads:[~2006-10-04 8:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-04 8:42 pcaulfield [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-30 10:16 pcaulfield
2006-11-21 17:44 agk
2006-11-01 18:25 agk
2006-07-19 18:55 agk
2005-01-20 22:16 agk
2005-01-11 22:00 agk
2004-12-21 18:07 agk
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=20061004084214.31337.qmail@sourceware.org \
--to=pcaulfield@sourceware.org \
--cc=lvm2-cvs@sourceware.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).