From owner-freebsd-questions@freebsd.org Sat Jun 2 23:46:40 2018 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 84338FD0D25 for ; Sat, 2 Jun 2018 23:46:40 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wr0-x231.google.com (mail-wr0-x231.google.com [IPv6:2a00:1450:400c:c0c::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 009BA8113C for ; Sat, 2 Jun 2018 23:46:39 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: by mail-wr0-x231.google.com with SMTP id w7-v6so27633439wrn.6 for ; Sat, 02 Jun 2018 16:46:39 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=ftASg39vLPEUuPj9UIs/ceAPMzPETCzr77Byh3fprUQ=; b=T7ZowgGnU58XZoRDZN4Xbcd3gnhMqawLoqmxDpAT1TZWlaJ5TtXyZ+JpZAWiB0fNm9 5ie4Yfw10B/e2xWjY0RCdboUhcJVJmHbdNZdjWUUseAdWrnBvNHKXXVrHgHrdqwT0W+r IPty10D0GcpIWe8tUZ1Tm3Zty8um9gx5e+fUDYAu9xZ2sdt8WGy7pqnbFFvyCgcVPrci MRVoD8zFeJZ1fa0mYXkW5CfAfmVGz7eLmiF24dXkYzm+oH6VUjc+uGUtlx3J8NhPTmvU gXD5p6R12AeqD7mE0pd9/2KuAttpZCN5hpVF2UDiRA+Oa6UtRszEOWK3oNueAebR6A4+ 55mg== X-Gm-Message-State: APt69E2ihS2onK+xGv3M4ZLs8rQ1H4kDpVo8VrRWIZnL8Y2Im1qbj3MG 0M6/k13QFxRdjNRpI50MBbWK9g== X-Google-Smtp-Source: ADUXVKLGyy5pxTXsQkD2irTbRvaQGm5fyU7lZGOWbMT5MbljHOIy5T5fPnXXM2OhlTEcg54fAPexxw== X-Received: by 2002:adf:8c09:: with SMTP id z9-v6mr3104626wra.142.1527983198668; Sat, 02 Jun 2018 16:46:38 -0700 (PDT) Received: from gumby.homeunix.com ([90.211.23.147]) by smtp.gmail.com with ESMTPSA id s132-v6sm4548523wmf.5.2018.06.02.16.46.36 for (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Sat, 02 Jun 2018 16:46:37 -0700 (PDT) Date: Sun, 3 Jun 2018 00:46:34 +0100 From: RW To: freebsd-questions@freebsd.org Subject: Re: Is it normal that a user can take down the whole system by using too much memory? Message-ID: <20180603004634.5865434d@gumby.homeunix.com> In-Reply-To: <1527981931.2670335.1394316280.09410FC9@webmail.messagingengine.com> References: <1527977770.2651378.1394286400.0806CC5C@webmail.messagingengine.com> <01EE7EEA-03AC-4D71-BA08-B0CEA97EE720@thehowies.com> <1527981931.2670335.1394316280.09410FC9@webmail.messagingengine.com> X-Mailer: Claws Mail 3.16.0 (GTK+ 2.24.32; amd64-portbld-freebsd11.1) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jun 2018 23:46:40 -0000 On Sat, 02 Jun 2018 19:25:31 -0400 Brennan Vincent wrote: > I'm also curious, however, to learn more from an OS design > perspective. Why isn't it possible for the kernel to realize it > should kill `eatmem` rather than make the system unusable? I did something similar a few years ago, and the process was reliably killed.