From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 8DFC315852A for ; Sat, 24 Aug 2024 09:15:58 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 163B4E2A5D; Sat, 24 Aug 2024 09:15:53 +0000 (UTC) Received: from smtp.hosts.co.uk (smtp.hosts.co.uk [85.233.160.19]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id C0CF9E2A56 for ; Sat, 24 Aug 2024 09:15:52 +0000 (UTC) Received: from 92.40.191.99.threembb.co.uk ([92.40.191.99] helo=[192.168.212.217]) by smtp.hosts.co.uk with esmtpa (Exim) (envelope-from ) id 1shmsB-000000005tk-2Jzj for gentoo-user@lists.gentoo.org; Sat, 24 Aug 2024 10:15:51 +0100 Message-ID: <2b458bbd-0243-4ac5-be00-fa1719a9eada@youngman.org.uk> Date: Sat, 24 Aug 2024 10:15:50 +0100 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [gentoo-user] Firefox, Seamonkey to if I can, and memory limits. To: gentoo-user@lists.gentoo.org References: Content-Language: en-US From: Wol In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Archives-Salt: 00cb77f8-aad5-4a01-ab38-377e74ca0cd4 X-Archives-Hash: ed32075bd74f5f57bd61eef5971bbba6 On 24/08/2024 00:03, Matt Jolly wrote: > I use slices on HPC to limit users from monopolising interactive nodes, > and our batch jobs kill anything that exceeds requested memory (hope > that wasn't 100h into a job!). I do this on login with user slices but > the concept is the same. I used something a bit like that on Pr1mos. I had a batch queue that ran on maximum priority, if users wanted something done quick. But it had a wall-clock limit of 30 secs. I don't think it got used much, but it was nice to know it was there so even if the machine was being hammered you could slip small jobs in quickly. Cheers, Wol