From: Matthew Hall <mhall@mhcomputing.net>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Question about log levels and rte_panic
Date: Sat, 13 Feb 2016 11:12:51 -0800 [thread overview]
Message-ID: <F6BFB743-666B-4EF5-88CD-4E033F42CCE1@mhcomputing.net> (raw)
In-Reply-To: <74FAD086-9CA8-44F2-9AA5-F2E707F5232A@intel.com>
> On Feb 13, 2016, at 9:43 AM, Wiles, Keith <keith.wiles@intel.com> wrote:
>
> I would expect EMERG, ALERT and CRIT messages to be printed regardless of the log-level value
I wouldn't expect that based on the traditional custom of syslog daemons. If you specify a filter configuration, such as setlogmask or some custom logic in the syslog daemon itself, the logging system should respect it. Even if it might not make sense to a given individual.
That said, rte_panic should be making sure the messages it generates always get logged, regardless of the logging system settings, because it is hijacking control of your process which is a very hostile act. This special exemption should only happen for things that are truly fatal. Not anything else.
Matthew.
next prev parent reply other threads:[~2016-02-13 19:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-13 17:43 Wiles, Keith
2016-02-13 19:12 ` Matthew Hall [this message]
2016-02-14 20:23 ` Stephen Hemminger
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=F6BFB743-666B-4EF5-88CD-4E033F42CCE1@mhcomputing.net \
--to=mhall@mhcomputing.net \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.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 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).