Hi all, since long, rsyslog has a so-called "emergency config system" which provides a very minimal config in case rsyslog can not load the real config. I am working on that system, which creates some complexity inside the code. Most importantly, I noticed that somewhere along development, that system notably degraded, obviously without anybody noticing. All it currently does is spit out startup error messages to some well known destinations (like the system console). It does NOT process the kernel log or the regular log socket.
As nobody reported any problems with the system, I guess nobody really used it. In order to streamline the code, I am about to drop it from v6 (even more so because systemd handles many of the situations this system originally was thought for [1]). Removing helps getting cleaner, less complex and faster to work on code. Any objections against dropping the emergency config system? If so, please let know the exact reason because I need to remodel the system in any case and this feedback would be very useful (plus prove the point that there is real need for this system ;)). Thanks, Rainer [1] http://lists.freedesktop.org/archives/systemd-devel/2011-July/002862.html _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com
