From: Yosuke Iwamatsu <y-iwamatsu@ab.jp.nec.com>
To: xen-devel@lists.xensource.com
Cc: Yuji Shimada <shimada-yxb@necst.nec.co.jp>
Subject: [PATCH] Log qemu-dm's message with date, time and pid
Date: Thu, 26 Jun 2008 14:02:54 +0900 [thread overview]
Message-ID: <486322FE.3070304@ab.jp.nec.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 658 bytes --]
The qemu-dm's log message doesn't have date, time, and pid. It is
difficult to find out the message we want.
This patch solves the problem without changing the codes which write
messages.
We developed a small program called ioemu-logger. qemu-dm creates a pipe
and starts ioemu-logger. qemu-dm associates a stream with the pipe, and
sets the stream to existing "logfile" variable. When qemu-dm writes a
message to "logfile", ioemu-logger receive it through the pipe and
outputs it with date, time and pid to the actual log file.
Signed-off-by: Yuji Shimada <shimada-yxb@necst.nec.co.jp>
-----------------------
Yosuke Iwamatsu
NEC Corporation
[-- Attachment #2: ioemu-logger.patch --]
[-- Type: all/allfiles, Size: 7843 bytes --]
[-- Attachment #3: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next reply other threads:[~2008-06-26 5:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-26 5:02 Yosuke Iwamatsu [this message]
2008-06-26 11:20 ` [PATCH] Log qemu-dm's message with date, time and pid Kevin Wolf
2008-06-26 14:46 ` Ian Jackson
2008-06-26 16:38 ` Daniel P. Berrange
2008-07-01 17:38 ` Ian Jackson
2008-07-01 18:10 ` Daniel P. Berrange
2008-07-01 20:06 ` John Levon
2008-07-02 10:26 ` Ian Jackson
2008-07-02 10:41 ` Daniel P. Berrange
2008-07-02 15:20 ` Brendan Cully
2008-06-27 8:19 ` Yuji Shimada
2008-06-27 9:10 ` Kevin Wolf
2008-06-27 13:40 ` Ian Jackson
2008-06-30 8:21 ` Yuji Shimada
2008-06-30 9:45 ` Kevin Wolf
2008-07-01 8:01 ` Yuji Shimada
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=486322FE.3070304@ab.jp.nec.com \
--to=y-iwamatsu@ab.jp.nec.com \
--cc=shimada-yxb@necst.nec.co.jp \
--cc=xen-devel@lists.xensource.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.