Re: [PATCH 1/1] Optionally re-introduce bb_info_msg()

2019-04-30 Thread Denys Vlasenko
Applied, thanks! On Fri, Apr 12, 2019 at 7:02 PM James Byrne wrote: > > Between Busybox 1.24.2 and 1.25.0 the bb_info_msg() function was > eliminated and calls to it changed to be bb_error_msg(). The downside of > this is that daemons now log all messages to syslog at the LOG_ERR level > which

Re: [PATCH 1/1] Optionally re-introduce bb_info_msg()

2019-04-12 Thread Natanael Copa
On Fri, 12 Apr 2019 17:01:51 + James Byrne wrote: > Between Busybox 1.24.2 and 1.25.0 the bb_info_msg() function was > eliminated and calls to it changed to be bb_error_msg(). The downside of > this is that daemons now log all messages to syslog at the LOG_ERR level > which makes it hard to

[PATCH 1/1] Optionally re-introduce bb_info_msg()

2019-04-12 Thread James Byrne
Between Busybox 1.24.2 and 1.25.0 the bb_info_msg() function was eliminated and calls to it changed to be bb_error_msg(). The downside of this is that daemons now log all messages to syslog at the LOG_ERR level which makes it hard to filter errors from informational messages. This change

[PATCH 1/1] Optionally re-introduce bb_info_msg()

2018-05-09 Thread James Byrne
Between Busybox 1.24.2 and 1.25.0 the bb_info_msg() function was eliminated and calls to it changed to be bb_error_msg(). The downside of this is that daemons now log all messages to syslog at the LOG_ERR level which makes it hard to filter errors from informational messages. This change