RE: Dumb question: Why are exceptions such as SIGSEGV not logged

["David Schwartz" <davids@webmaster.com>]

>     You probably have missed some postings on this thread.
>     This one:

[snip]

	If you think those posts are relvent, you misunderstand my point. Those
posts are from the view "if someone wants to DoS the log files, they already
can", my argument is more, "if someone doesn't want to DoS the log files,
but you make this patch, how can they avoid it?"

>      If application cannot be responsible for its children - it is just
> bad programming practice. Fix applications.
>      Reapping zombies 'just in case if any' sounds really bad.

	If we were to write code to detect bad programming practices and syslog
them, it would be nearly impossible to prevent syslog DoSes. Looping on
'waitpid(WNOHANG)' periodically is a perfectly sane way to reap zombies,
especially in cases where there are issues with signal handling and in
multithreaded programs.

	If an application does something that a programmer could sensibly decide to
and that solves problems that can't always be solved in another way, it
should not result in a syslog entry in the default configuration (unless
it's something the system administrator needs to keep track of for
security/audit reasons).

	An application should be free to terminate however it likes without
programmers getting calls from sysadmins that the application is DoSing the
syslog. If you want a special debug mode, that's fine.

	DS