Re: [LEDE-DEV] [PATCH][ubox] Fixes log read starvation issue after threshold reached

Jo-Philipp Wich [2017-07-12 23:34:13]: Hi, > Do you have an easy test case for this? Is piping ~16K plaintext to the > logger enough to trigger the starvation? I'd like to understand the > problem some more before judging the patch. I was trying to fix probably similar issue back

Re: [LEDE-DEV] [PATCH][ubox] Fixes log read starvation issue after threshold reached

On 2017-07-11 21:04, Ron Brash wrote: > This patch fixes a logread starvation error, which occurs after many > logs are generated (around 16k if defaults are used). The log read > process seems to halt silently and yet continues running. A restart > of the log services fixes it. > > This is

[LEDE-DEV] [PATCH][ubox] Fixes log read starvation issue after threshold reached

This patch fixes a logread starvation error, which occurs after many logs are generated (around 16k if defaults are used). The log read process seems to halt silently and yet continues running. A restart of the log services fixes it. This is problematic because logs should be logged, instead of