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 man/lvm.8.in Date: Fri, 20 Feb 2009 01:47:00 -0000 [thread overview] Message-ID: <20090220014703.31706.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: agk@sourceware.org 2009-02-20 01:47:02 Modified files: . : WHATS_NEW man : lvm.8.in Log message: Mention the restriction on file descriptors at invocation on the lvm man page. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.1044&r2=1.1045 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/man/lvm.8.in.diff?cvsroot=lvm2&r1=1.1&r2=1.2 --- LVM2/WHATS_NEW 2009/02/17 18:56:41 1.1044 +++ LVM2/WHATS_NEW 2009/02/20 01:47:02 1.1045 @@ -1,5 +1,6 @@ Version 2.02.45 - =================================== + Mention the restriction on file descriptors at invocation on the lvm man page. Index cached vgmetadata by vgid not vgname to cope with duplicate vgnames. No longer require kernel and metadata major numbers to match. Add a fully-functional get_cluster_name() to clvmd corosync interface. --- LVM2/man/lvm.8.in 2008/10/08 12:50:13 1.1 +++ LVM2/man/lvm.8.in 2009/02/20 01:47:02 1.2 @@ -18,6 +18,10 @@ LVM command (for example by using a hard or soft link) it acts as that command. .LP +On invocation, \fBlvm\fP requires that only the standard file descriptors +stdin, stdout and stderr are available. If others are found, they +get closed and messages are issued warning about the leak. +.LP Where commands take VG or LV names as arguments, the full path name is optional. An LV called "lvol0" in a VG called "vg0" can be specified as "vg0/lvol0". Where a list of VGs is required but is left empty,
next reply other threads:[~2009-02-20 1:47 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-02-20 1:47 agk [this message] 2012-03-01 10:39 zkabelac 2012-04-26 15:24 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=20090220014703.31706.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: linkBe 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).