Date: Thu, 09 Nov 2023 19:20:30 +0800 From: Philip Paeps <philip@freebsd.org> To: Robert Clausecker <fuz@fuz.su> Cc: Alexander Leidinger <Alexander@leidinger.net>, freebsd-arch@freebsd.org Subject: Re: Any particular reason we don't have sshd oomprotected by default? Message-ID: <C31C649C-049E-487F-9ADB-C8B3A78C4020@freebsd.org> In-Reply-To: <ZUyTnDAJ3HOppG8h@fuz.su> References: <8b9484ba83e373ece0e322e14c924da6@Leidinger.net> <ZUyTnDAJ3HOppG8h@fuz.su>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2023-11-09 16:09:00 (+0800), Robert Clausecker wrote: > I encountered the same issue a while ago, leaving my system in a > vegetative state. I would propose to add syslogd and cron to the > list. Syslogd because when it dies and you don't notice, you may go > for > a long time without syslogs, cron because a dead cron means no > housekeeping tasks happen, including some which the administrator may > have intended to fix an issue causing an OOM condition (e.g. > periodically restarting services with known memory leaks or cleaning > tmpfs-based file systems). In my experience, cron is more often the cause of an OOM condition than a help to making it stop. :-) Philip -- Philip Paeps Senior Reality Engineer Alternative Enterprises
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?C31C649C-049E-487F-9ADB-C8B3A78C4020>