[dpdk-dev] Question about log levels and rte_panic

2016-02-14 Thread Stephen Hemminger
On Sat, 13 Feb 2016 17:43:38 + "Wiles, Keith" wrote: > The reason it appears to just exit to the shell is I was setting ?log-level 0 > on the command line, which means no CRIT, EMERG or ALERTs panic messages are > printed. If I set the log-level 3 then I am able to see these ?critical? > p

[dpdk-dev] Question about log levels and rte_panic

2016-02-13 Thread Wiles, Keith
I have some code I have been debugging that does a rte_panic() at some point. The problem is it just appeared to exit without printing the panic message. I tracked it down to rte_vlog() doing the following test. if ((level > rte_logs.level) || !(logtype & rte_logs.type)) return 0; The r

[dpdk-dev] Question about log levels and rte_panic

2016-02-13 Thread Matthew Hall
> On Feb 13, 2016, at 9:43 AM, Wiles, Keith 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 cu