From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.mhcomputing.net (master.mhcomputing.net [74.208.228.170]) by dpdk.org (Postfix) with ESMTP id 33E0B95D9 for ; Sat, 13 Feb 2016 20:12:53 +0100 (CET) Received: from [IPv6:2602:306:322e:5ae0:cae0:ebff:fe17:5b39] (unknown [IPv6:2602:306:322e:5ae0:cae0:ebff:fe17:5b39]) by mail.mhcomputing.net (Postfix) with ESMTPSA id 60856EFD; Sat, 13 Feb 2016 11:12:52 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 9.2 \(3112\)) From: Matthew Hall In-Reply-To: <74FAD086-9CA8-44F2-9AA5-F2E707F5232A@intel.com> Date: Sat, 13 Feb 2016 11:12:51 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: References: <74FAD086-9CA8-44F2-9AA5-F2E707F5232A@intel.com> To: "Wiles, Keith" X-Mailer: Apple Mail (2.3112) Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] Question about log levels and rte_panic X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 Feb 2016 19:12:53 -0000 > On Feb 13, 2016, at 9:43 AM, Wiles, Keith = wrote: >=20 > 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.=