Date: Sun, 22 Nov 2015 13:49:54 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 204741] [patch] [feature-request] syslogd(8) should be able to protect itself from OOM killer Message-ID: <bug-204741-8@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204741 Bug ID: 204741 Summary: [patch] [feature-request] syslogd(8) should be able to protect itself from OOM killer Product: Base System Version: 10.2-STABLE Hardware: Any OS: Any Status: New Keywords: patch Severity: Affects Some People Priority: --- Component: bin Assignee: freebsd-bugs@FreeBSD.org Reporter: eugen@grosbein.net Keywords: patch Created attachment 163419 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=163419&action=edit syslogd-protect.diff If the system exhausts available memory and swap, it starts to kill processes and report killed processes with syslog facility. syslogd(8) should not be killed or else system administrator has not complete information about the case. Practice shows that syslogd may be killed like any other process. Let's teach syslogd to protect itself from OOM killer. The following patch introduces new command line option "-O" and system administrator is allowed to have a line in its /etc/rc.conf: syslogd_flags="-O" In this case, syslogd became protected. -- You are receiving this mail because: You are the assignee for the bug.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-204741-8>