public inbox for lvm2-cvs@sourceware.org
help / color / mirror / Atom feed
From: agk@sourceware.org
To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org
Subject: LVM2 ./WHATS_NEW lib/commands/toolcontext.c
Date: Tue, 23 Jan 2007 16:03:00 -0000 [thread overview]
Message-ID: <20070123160354.18078.qmail@sourceware.org> (raw)
CVSROOT: /cvs/lvm2
Module name: LVM2
Changes by: agk@sourceware.org 2007-01-23 16:03:54
Modified files:
. : WHATS_NEW
lib/commands : toolcontext.c
Log message:
Long-lived processes write out persistent dev cache in refresh_toolcontext().
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.552&r2=1.553
http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/commands/toolcontext.c.diff?cvsroot=lvm2&r1=1.44&r2=1.45
--- LVM2/WHATS_NEW 2007/01/23 15:58:05 1.552
+++ LVM2/WHATS_NEW 2007/01/23 16:03:53 1.553
@@ -1,5 +1,6 @@
Version 2.02.20 -
===================================
+ Long-lived processes write out persistent dev cache in refresh_toolcontext().
Fix refresh_toolcontext() always to wipe persistent device filter cache.
Add is_long_lived to toolcontext.
Add --clustered to man pages.
--- LVM2/lib/commands/toolcontext.c 2007/01/23 15:58:05 1.44
+++ LVM2/lib/commands/toolcontext.c 2007/01/23 16:03:54 1.45
@@ -1080,6 +1080,13 @@
if (!_init_segtypes(cmd))
return 0;
+ /*
+ * If we are a long-lived process, write out the updated persistent
+ * device cache for the benefit of short-lived processes.
+ */
+ if (cmd->is_long_lived && cmd->dump_filter)
+ persistent_filter_dump(cmd->filter);
+
cmd->config_valid = 1;
return 1;
}
next reply other threads:[~2007-01-23 16:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-23 16:03 agk [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-05-23 13:02 zkabelac
2012-03-23 9:42 zkabelac
2012-02-27 10:05 zkabelac
2012-02-08 10:46 zkabelac
2011-07-08 16:49 agk
2011-06-28 0:23 agk
2010-11-24 9:34 zkabelac
2010-04-30 12:37 zkabelac
2009-07-21 20:00 mpatocka
2009-07-14 12:17 mbroz
2009-06-15 11:56 mbroz
2009-04-02 20:46 taka
2007-02-08 17:31 agk
2005-01-27 15:50 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=20070123160354.18078.qmail@sourceware.org \
--to=agk@sourceware.org \
--cc=lvm-devel@redhat.com \
--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).