public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: mornfall@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW scripts/lvm_dump.sh Date: Tue, 02 Oct 2007 15:48:00 -0000 [thread overview] Message-ID: <20071002154858.24543.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: mornfall@sourceware.org 2007-10-02 15:48:58 Modified files: . : WHATS_NEW scripts : lvm_dump.sh Log message: Fix a bug in lvm_dump.sh checks for lvm/dmsetup binaries quote the invocations a bit more (although i'm fairly sure there are still quotes missing somewhere due to the eval in log). Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.714&r2=1.715 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/scripts/lvm_dump.sh.diff?cvsroot=lvm2&r1=1.9&r2=1.10 --- LVM2/WHATS_NEW 2007/09/24 13:25:31 1.714 +++ LVM2/WHATS_NEW 2007/10/02 15:48:57 1.715 @@ -1,5 +1,6 @@ Version 2.02.29 - ================================== + Fix a bug in lvm_dump.sh checks for lvm/dmsetup binaries. Refactor lvcreate stripe and mirror parameter validation. All tools: print --help output to stdout, not stderr. After a diagnostic, suggest --help, rather than printing all --help output. --- LVM2/scripts/lvm_dump.sh 2007/08/20 20:55:29 1.9 +++ LVM2/scripts/lvm_dump.sh 2007/10/02 15:48:58 1.10 @@ -17,7 +17,7 @@ # the debugging of lvm issues. # following external commands are used throughout the script -# which, echo and test are internal in bash at least +# echo and test are internal in bash at least MKDIR=mkdir # need -p TAR=tar # need czf RM=rm # need -rf @@ -43,12 +43,8 @@ exit $code } -# which should error out if the binary is not executable, although i -# am not sure we can rely on this -which $LVM >& /dev/null || die 2 "Fatal: could not find lvm binary '$LVM'" -test -x `which $LVM` || die 2 "Fatal: lvm binary '$LVM' not executable" -which $DMSETUP >& /dev/null || die 2 "Fatal: could not find dmsetup binary '$DMSETUP'" -test -x `which $DMSETUP` || die 2 "Fatal: dmsetup binary '$DMSETUP' not executable" +"$LVM" version >& /dev/null || die 2 "Could not run lvm binary '$LVM'" +"$DMSETUP" help >& /dev/null || die 2 "Fatal: could not run dmsetup binary '$DMSETUP'" function usage { echo "$0 [options]" @@ -166,13 +162,13 @@ myecho "Gathering LVM & device-mapper version info..." echo "LVM VERSION:" > $dir/versions -$LVM lvs --version >> $dir/versions 2>> $log +"$LVM" lvs --version >> $dir/versions 2>> $log echo "DEVICE MAPPER VERSION:" >> $dir/versions -$DMSETUP --version >> $dir/versions 2>> $log +"$DMSETUP" --version >> $dir/versions 2>> $log echo "KERNEL VERSION:" >> $dir/versions -$UNAME -a >> $dir/versions 2>> $log +"$UNAME" -a >> $dir/versions 2>> $log echo "DM TARGETS VERSIONS:" >> $dir/versions -$DMSETUP targets >> $dir/versions 2>> $log +"$DMSETUP" targets >> $dir/versions 2>> $log myecho "Gathering dmsetup info..." log "$DMSETUP info -c > $dir/dmsetup_info 2>> $log" @@ -215,9 +211,9 @@ if test -z "$userdir"; then lvm_dump="$dirbase.tgz" myecho "Creating report tarball in $HOME/$lvm_dump..." - cd $HOME - $TAR czf $lvm_dump $dirbase 2>/dev/null - $RM -rf $dir + cd "$HOME" + "$TAR" czf $lvm_dump $dirbase 2>/dev/null + "$RM" -rf $dir fi if test "$UID" != "0" && test "$EUID" != "0"; then
next reply other threads:[~2007-10-02 15:48 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-02 15:48 mornfall [this message] -- strict thread matches above, loose matches on Subject: below -- 2009-01-06 18:03 mbroz 2008-08-28 10:40 mbroz 2007-10-02 16:09 mornfall 2007-08-09 9:53 pcaulfield 2007-07-02 20:18 mbroz 2007-04-25 14:49 bmr 2006-11-23 17:23 agk 2006-10-05 18:42 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=20071002154858.24543.qmail@sourceware.org \ --to=mornfall@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).