On Wed, 05 Apr 2017 16:51:13 +0200, Alexander Bluhm wrote:
> Syslogd's fatal() calls die() internally, so there is no change in
> behavior. The idea is that you may call fatal() anywhere and die()
> will do cleanup if necessary.
Ah, right, I missed that.
- todd
On Wed, Apr 05, 2017 at 08:18:03AM -0600, Todd C. Miller wrote:
> On Wed, 05 Apr 2017 13:58:12 +0200, Alexander Bluhm wrote:
> > Replace all combinations of logerror() and die() with log.c fatal().
> > Also all err(3) after log_init() are replaced.
>
> This is before we start accepting log message
On Wed, 05 Apr 2017 13:58:12 +0200, Alexander Bluhm wrote:
> On Fri, Mar 17, 2017 at 02:09:35AM +0100, Alexander Bluhm wrote:
> > This is the next step for refactoring internal syslogd(8) logging.
>
> Replace all combinations of logerror() and die() with log.c fatal().
> Also all err(3) after log
On Fri, Mar 17, 2017 at 02:09:35AM +0100, Alexander Bluhm wrote:
> This is the next step for refactoring internal syslogd(8) logging.
Replace all combinations of logerror() and die() with log.c fatal().
Also all err(3) after log_init() are replaced.
ok?
bluhm
Index: usr.sbin/syslogd/syslogd.c
=
