Re: [LEDE-DEV] odhcpd: [PATCH 1/3] enable loglevel setting via envvar ODHCPD_LOG_LEVEL

2016-09-26 Thread John Crispin
On 27/09/2016 01:33, Karl Palsson wrote: > > John Crispin wrote: >> >> >> On 22/09/2016 19:32, Karl Palsson wrote: >>> From: Karl Palsson >>> >>> Currently the loglevel is hardcoded to LOG_WARNING, even though there is >>> debug log messages. Allow an

Re: [LEDE-DEV] odhcpd: [PATCH 1/3] enable loglevel setting via envvar ODHCPD_LOG_LEVEL

2016-09-26 Thread Karl Palsson
John Crispin wrote: > > > On 22/09/2016 19:32, Karl Palsson wrote: > > From: Karl Palsson > > > > Currently the loglevel is hardcoded to LOG_WARNING, even though there is > > debug log messages. Allow an env var to control the log threshold. > > > >

Re: [LEDE-DEV] odhcpd: [PATCH 1/3] enable loglevel setting via envvar ODHCPD_LOG_LEVEL

2016-09-26 Thread John Crispin
On 22/09/2016 19:32, Karl Palsson wrote: > From: Karl Palsson > > Currently the loglevel is hardcoded to LOG_WARNING, even though there is > debug log messages. Allow an env var to control the log threshold. > > Signed-off-by: Karl Palsson > --- >

[LEDE-DEV] odhcpd: [PATCH 1/3] enable loglevel setting via envvar ODHCPD_LOG_LEVEL

2016-09-22 Thread Karl Palsson
From: Karl Palsson Currently the loglevel is hardcoded to LOG_WARNING, even though there is debug log messages. Allow an env var to control the log threshold. Signed-off-by: Karl Palsson --- src/odhcpd.c | 16 +++- 1 file changed, 15