From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: Cliff Burdick <shaklee3@gmail.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] Capture EAL Output For Logging
Date: Wed, 29 Jun 2016 16:30:12 +0000 [thread overview]
Message-ID: <E923DB57A917B54B9182A2E928D00FA612920395@IRSMSX102.ger.corp.intel.com> (raw)
In-Reply-To: <CA+Gp1nZmXU4iC1_GKwvys8CEDiiiq+g-ECjgzrKGA-oOHVZjFw@mail.gmail.com>
> From: users [mailto:users-bounces@dpdk.org] On Behalf Of Cliff Burdick
> Hi, if I have my own logging mechanism, is there a way to capture the EAL
> output, especially on startup? The best way I can think of is to open a
> pipe to a child process that reads from stdout, and logs from there, but
> that seems like somewhat of a hack.
The same approach of using pipes has been taken for the CollectD plugin for DPDK[1]; it has proven to work fine. Based on the experience of developing, having a child process with pipes makes it a little more complex to debug, but not drastically so.
Hope that helps! Regards, -Harry
[1] https://github.com/collectd/collectd/pull/1649
prev parent reply other threads:[~2016-06-29 16:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-29 16:21 Cliff Burdick
2016-06-29 16:30 ` Van Haaren, Harry [this message]
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=E923DB57A917B54B9182A2E928D00FA612920395@IRSMSX102.ger.corp.intel.com \
--to=harry.van.haaren@intel.com \
--cc=shaklee3@gmail.com \
--cc=users@dpdk.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;
as well as URLs for NNTP newsgroup(s).