From: longtb5@viettel.com.vn
To: <users@dpdk.org>
Subject: Re: [dpdk-users] Logging with syslog
Date: Tue, 17 Jul 2018 19:37:19 +0700 (ICT) [thread overview]
Message-ID: <002801d41dcb$d67649f0$8362ddd0$@viettel.com.vn> (raw)
In-Reply-To:
Hi,
As it turns out, implementing a custom logstream with fopencookie() is
rather trivial. Sample code can be found online (google dpdk fopencookie)
and inside EAL source code as well.
> -----Original Message-----
> From: Bao Long Tran [mailto:longtb5@viettel.com.vn]
> Sent: Tuesday, July 17, 2018 11:17 AM
> To: 'users@dpdk.org' <users@dpdk.org>
> Subject: Logging with syslog
>
> Hi,
>
> I'm trying to improve the logging system for my application. From my
> understanding, the default log_stream is fopencookie()'d to enable sending
> logs to syslog as well. However, for my use case, logs should always be
sent
> to syslog, but not always written to stdout as it would clog up my command
> line interface (I'm using rte_cmdline).
>
> Is there a way to achieve this with available DPDK logging utilities via
some
> kind of configuration? Or must I manually create another log_stream with
> fopencookie()?
>
> Thanks and best regards,
> -BL
next reply other threads:[~2018-07-17 12:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-17 12:37 longtb5 [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-17 4:10 longtb5
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='002801d41dcb$d67649f0$8362ddd0$@viettel.com.vn' \
--to=longtb5@viettel.com.vn \
--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).