From: dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
To: initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
Subject: [patch 1/2] move memory usage tracing output to stderr
Date: Mon, 25 Feb 2013 14:38:15 +0800 [thread overview]
Message-ID: <20130225064007.527029731@redhat.com> (raw)
In-Reply-To: 20130225063814.423057451@redhat.com
[-- Attachment #1: mem-trace-stderr.patch --]
[-- Type: text/plain, Size: 662 bytes --]
memory usage tracing outputs are debug info, so it should be moved to
stderr instead of stdout.
Signed-off-by: Dave Young <dyoung-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
---
modules.d/99base/dracut-lib.sh | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- dracut.orig/modules.d/99base/dracut-lib.sh
+++ dracut/modules.d/99base/dracut-lib.sh
@@ -1029,7 +1029,7 @@ make_trace_mem()
msg="$1"
shift
if [ -n "$DEBUG_MEM_LEVEL" ] && [ "$DEBUG_MEM_LEVEL" -gt 0 ]; then
- make_trace show_memstats $DEBUG_MEM_LEVEL "[debug_mem]" "$msg" "$@"
+ make_trace show_memstats $DEBUG_MEM_LEVEL "[debug_mem]" "$msg" "$@" >&2
fi
}
next prev parent reply other threads:[~2013-02-25 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-25 6:38 [patch 0/2] memory usage trace follow-ups dyoung-H+wXaHxf7aLQT0dZR+AlfA
2013-02-25 6:38 ` dyoung-H+wXaHxf7aLQT0dZR+AlfA [this message]
2013-02-25 6:38 ` [patch 2/2] add memory usage trace points in the old init script as well dyoung-H+wXaHxf7aLQT0dZR+AlfA
[not found] ` <20130225063814.423057451-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2013-03-11 2:36 ` [patch 0/2] memory usage trace follow-ups Dave Young
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=20130225064007.527029731@redhat.com \
--to=dyoung-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=harald-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=initramfs-u79uwXL29TY76Z2rM5mHXA@public.gmane.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