From owner-freebsd-current@FreeBSD.ORG Fri Feb 8 12:46:13 2013 Return-Path: Delivered-To: current@FreeBSD.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 35931A81; Fri, 8 Feb 2013 12:46:13 +0000 (UTC) (envelope-from avg@FreeBSD.org) Received: from citadel.icyb.net.ua (citadel.icyb.net.ua [212.40.38.140]) by mx1.freebsd.org (Postfix) with ESMTP id 4F7D42A9; Fri, 8 Feb 2013 12:46:11 +0000 (UTC) Received: from odyssey.starpoint.kiev.ua (alpha-e.starpoint.kiev.ua [212.40.38.101]) by citadel.icyb.net.ua (8.8.8p3/ICyb-2.3exp) with ESMTP id OAA10755; Fri, 08 Feb 2013 14:46:08 +0200 (EET) (envelope-from avg@FreeBSD.org) Message-ID: <5114F390.4010302@FreeBSD.org> Date: Fri, 08 Feb 2013 14:46:08 +0200 From: Andriy Gapon User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130206 Thunderbird/17.0.2 MIME-Version: 1.0 To: Fabian Keil , zont@FreeBSD.org, current@FreeBSD.org Subject: Re: geli(8) breaks after a couple hours of uptime References: <20130207141833.GA15884@acme.spoerlein.net> <20130207153322.5c371beb@fabiankeil.de> <20130207180153.GX35868@acme.spoerlein.net> <20130208095709.6ae61cff@fabiankeil.de> <20130208114825.GY35868@acme.spoerlein.net> In-Reply-To: <20130208114825.GY35868@acme.spoerlein.net> X-Enigmail-Version: 1.4.6 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 Feb 2013 12:46:13 -0000 on 08/02/2013 13:48 Ulrich Spörlein said the following: > The problem here is that I login via my user account, then either use > sudo or sudo -i for a root shell, this however does not raise the > memorylocked limit. So when I said this works during boot and shortly > after, it's because I haven't started my screen session yet, through > which I do all the work, usually, but have logged in with a direct root > shell. D'oh! > > It looks like 128k as a limit is still too low for geli(8) to work, and > I've set it to 256k now, so that I can use "sudo geli". Can you maybe > revise the patch to not use 1024k as an arbitrary limit, but rather make > sure you test for precisely as much memory as will be needed? > > Also, can we maybe revisit the new 64k default limit, as it will > obviously make peoples work with geli a bit painful, this should work > out of the box. I have some, IMO, better suggestions: - use -c option with sudo - tune your system for your needs - [major] abolish the silliness of tying resource limits to login class and apply resource limits based on user and group IDs; including after su/sudo (subject to local policies) -- Andriy Gapon