From nobody Thu Nov 9 19:59:59 2023 X-Original-To: freebsd-arch@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SRCVB2Yqwz50Fy9 for ; Thu, 9 Nov 2023 20:00:02 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Received: from omta001.cacentral1.a.cloudfilter.net (omta001.cacentral1.a.cloudfilter.net [3.97.99.32]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "Client", Issuer "CA" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4SRCVB1kM7z3S2g; Thu, 9 Nov 2023 20:00:02 +0000 (UTC) (envelope-from cy.schubert@cschubert.com) Authentication-Results: mx1.freebsd.org; none Received: from shw-obgw-4001a.ext.cloudfilter.net ([10.228.9.142]) by cmsmtp with ESMTPS id 14mVra9518jpT1BC5rOEB9; Thu, 09 Nov 2023 20:00:01 +0000 Received: from spqr.komquats.com ([70.66.152.170]) by cmsmtp with ESMTPSA id 1BC3rDz35mxE21BC4rXDsI; Thu, 09 Nov 2023 20:00:01 +0000 X-Authority-Analysis: v=2.4 cv=Cvasz10D c=1 sm=1 tr=0 ts=654d3a41 a=y8EK/9tc/U6QY+pUhnbtgQ==:117 a=y8EK/9tc/U6QY+pUhnbtgQ==:17 a=kj9zAlcOel0A:10 a=BNY50KLci1gA:10 a=6I5d2MoRAAAA:8 a=YxBL1-UpAAAA:8 a=EkcXrb_YAAAA:8 a=IyCreL5s2kJ_fr6SCQ0A:9 a=CjuIK1q_8ugA:10 a=IjZwj45LgO3ly-622nXo:22 a=Ia-lj3WSrqcvXOmTRaiG:22 a=LK5xJRSDVpKd5WXXoEvA:22 Received: from slippy.cwsent.com (slippy [10.1.1.91]) by spqr.komquats.com (Postfix) with ESMTP id 8175C12BF; Thu, 9 Nov 2023 11:59:59 -0800 (PST) Received: by slippy.cwsent.com (Postfix, from userid 1000) id 7B33B348; Thu, 9 Nov 2023 11:59:59 -0800 (PST) X-Mailer: exmh version 2.9.0 11/07/2018 with nmh-1.8+dev Reply-to: Cy Schubert From: Cy Schubert X-os: FreeBSD X-Sender: cy@cwsent.com X-URL: http://www.cschubert.com/ To: Philip Paeps cc: Robert Clausecker , Alexander Leidinger , freebsd-arch@freebsd.org Subject: Re: Any particular reason we don't have sshd oomprotected by default? In-reply-to: References: <8b9484ba83e373ece0e322e14c924da6@Leidinger.net> Comments: In-reply-to Philip Paeps message dated "Thu, 09 Nov 2023 19:20:30 +0800." List-Id: Discussion related to FreeBSD architecture List-Archive: https://lists.freebsd.org/archives/freebsd-arch List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-arch@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 09 Nov 2023 11:59:59 -0800 Message-Id: <20231109195959.7B33B348@slippy.cwsent.com> X-CMAE-Envelope: MS4xfJK3d6l/2j1/P/fp4lrTAgrmdAY+WFp7vgxxoFq1d3zQTDSPOPcXoy43PhC8yxaMAXH0UZvv1YqwN500Z+9PNCD1mRIxyBcyNTJFWwI0vM0PhmGhGgJP 3av6pRdepi57YVClwGEQaxGQ1Mx3CM+I0FCvTHy6tqhVJlpR8UjLKTA+QHrIq068pLbBPrp/YaDbUXdBcgJtlK3KIdDr6he6N+Ln4eFPYO3k7ZvCwy+EwTXV 4iPyv/RUotDAcc7Q6dCTz+VwXdF1u0bdsv+6NUGqdMW6h771l196uhbjK4QEscT/ X-Spamd-Bar: ---- X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:16509, ipnet:3.96.0.0/15, country:US] X-Rspamd-Queue-Id: 4SRCVB1kM7z3S2g In message , Philip Paeps wri tes: > 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. :-) Would that be cron or something that cron has started? -- Cheers, Cy Schubert FreeBSD UNIX: Web: https://FreeBSD.org NTP: Web: https://nwtime.org e^(i*pi)+1=0