public inbox for lvm2-cvs@sourceware.org help / color / mirror / Atom feed
From: zkabelac@sourceware.org To: lvm-devel@redhat.com, lvm2-cvs@sourceware.org Subject: LVM2 ./WHATS_NEW lib/misc/lvm-exec.c Date: Mon, 19 Sep 2011 14:54:00 -0000 [thread overview] Message-ID: <20110919145425.15594.qmail@sourceware.org> (raw) CVSROOT: /cvs/lvm2 Module name: LVM2 Changes by: zkabelac@sourceware.org 2011-09-19 14:54:23 Modified files: . : WHATS_NEW lib/misc : lvm-exec.c Log message: Use log_error instead of log_verbose when executed command fails Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/WHATS_NEW.diff?cvsroot=lvm2&r1=1.2121&r2=1.2122 http://sourceware.org/cgi-bin/cvsweb.cgi/LVM2/lib/misc/lvm-exec.c.diff?cvsroot=lvm2&r1=1.14&r2=1.15 --- LVM2/WHATS_NEW 2011/09/19 14:52:33 1.2121 +++ LVM2/WHATS_NEW 2011/09/19 14:54:23 1.2122 @@ -1,5 +1,6 @@ Version 2.02.89 - ================================== + Use log_error instead of log_verbose when executed command fails. Add support for non /dev device paths into fsadm script. Support different PATH setting for fsadm script testing. Surround all executed commands with quotes in fsadm script. --- LVM2/lib/misc/lvm-exec.c 2011/09/19 12:48:02 1.14 +++ LVM2/lib/misc/lvm-exec.c 2011/09/19 14:54:23 1.15 @@ -96,7 +96,7 @@ if (WEXITSTATUS(status)) { if (rstatus) { *rstatus = WEXITSTATUS(status); - log_verbose("%s failed: %u", argv[0], *rstatus); + log_error("%s failed: %u", argv[0], *rstatus); } else log_error("%s failed: %u", argv[0], WEXITSTATUS(status)); return 0;
next reply other threads:[~2011-09-19 14:54 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-19 14:54 zkabelac [this message] -- strict thread matches above, loose matches on Subject: below -- 2011-09-19 12:48 zkabelac
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=20110919145425.15594.qmail@sourceware.org \ --to=zkabelac@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).