[dpdk-dev] The use of --log-level and its default state

Keith, your mail is very long but it's maybe on purpose to show that there are too many logs ;) 2015-06-05 12:32, Wiles, Keith: > On 6/5/15, 5:00 AM, "Thomas Monjalon" wrote: > >2015-05-27 15:10, Wiles, Keith: > >> I would like to have the log-level default changed to not log > >>everything, > >>

[dpdk-dev] The use of --log-level and its default state

On 6/5/15, 8:58 AM, "Thomas Monjalon" wrote: >Keith, your mail is very long but it's maybe on purpose to show that >there are too many logs ;) Yes it was kind of the point, but only because I wanted to show the complete output. > >2015-06-05 12:32, Wiles, Keith: >> On 6/5/15, 5:00 AM, "Thomas

[dpdk-dev] The use of --log-level and its default state

On 6/5/15, 5:00 AM, "Thomas Monjalon" wrote: >2015-05-27 15:10, Wiles, Keith: >> I would like to have the log-level default changed to not log >>everything, >> but the user needs to enable the log messages if he needs to see more >> information. Normally applications or systems are not so verbo

[dpdk-dev] The use of --log-level and its default state

2015-05-27 15:10, Wiles, Keith: > I would like to have the log-level default changed to not log everything, > but the user needs to enable the log messages if he needs to see more > information. Normally applications or systems are not so verbose, but if > needed the user enables the verbose or deb

[dpdk-dev] The use of --log-level and its default state

Hi Everyone, Sorry, if this has been covered already. I would like to have the log-level default changed to not log everything, but the user needs to enable the log messages if he needs to see more information. Normally applications or systems are not so verbose, but if needed the user enables th