On Sun, 01 Jan 2017 21:05:58 +0100, Alexander Bluhm wrote: > Regular programs should die as early as possible when an error > occurs, then it can be fixed. But syslogd is special. If it dies, > you become blind and don't see any errors at all. An attacker could > exploit this. So I think syslogd should exit during startup e.g. > if an invalid option was specified. But then it should just log > errors and run as many subsystems as possible. > > So yes, a missing address should not be fatal. But there is more > to do. For each error it should be considered wether err() or die() > or logerror() is called. This is quite on top on my TODO list.
I couldn't agree more. - todd
