From owner-freebsd-gnome@FreeBSD.ORG Sat Apr 12 18:18:00 2008 Return-Path: Delivered-To: gnome@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 19EA8106564A; Sat, 12 Apr 2008 18:18:00 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmmtao103.cox.net (eastrmmtao103.cox.net [68.230.240.9]) by mx1.freebsd.org (Postfix) with ESMTP id 6BFF88FC1A; Sat, 12 Apr 2008 18:17:59 +0000 (UTC) (envelope-from mezz7@cox.net) Received: from eastrmimpo03.cox.net ([68.1.16.126]) by eastrmmtao103.cox.net (InterMail vM.7.08.02.01 201-2186-121-102-20070209) with ESMTP id <20080412181753.MYV4272.eastrmmtao103.cox.net@eastrmimpo03.cox.net>; Sat, 12 Apr 2008 14:17:53 -0400 Received: from mezz.mezzweb.com ([24.255.149.218]) by eastrmimpo03.cox.net with bizsmtp id CiHx1Z00M4iy4EG02iHy1o; Sat, 12 Apr 2008 14:17:58 -0400 Date: Sat, 12 Apr 2008 13:19:49 -0500 To: "Joe Marcus Clarke" From: "Jeremy Messenger" Content-Type: text/plain; format=flowed; delsp=yes; charset=us-ascii MIME-Version: 1.0 References: <47FD09AC.2020907@FreeBSD.org> <1207776230.61729.28.camel@shumai.marcuscom.com> <47FD34E8.2000005@FreeBSD.org> <1207807915.61729.40.camel@shumai.marcuscom.com> <1208022563.82222.22.camel@shumai.marcuscom.com> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <1208022563.82222.22.camel@shumai.marcuscom.com> User-Agent: Opera Mail/9.27 (Linux) Cc: gnome@freebsd.org, cokane@freebsd.org Subject: Re: Seahorse issues X-BeenThere: freebsd-gnome@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNOME for FreeBSD -- porting and maintaining List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 12 Apr 2008 18:18:00 -0000 On Sat, 12 Apr 2008 12:49:23 -0500, Joe Marcus Clarke wrote: > On Sat, 2008-04-12 at 12:42 -0500, Jeremy Messenger wrote: >> On Thu, 10 Apr 2008 01:11:55 -0500, Joe Marcus Clarke >> wrote: >> >> >> > The problem is the fact that FreeBSD's mlock() requires setuid >> > privileges, and thus seahorse cannot allocate secure memory. The >> >> Yesterday, I have found archives about mlock() in freebsd-arch@. >> >> http://lists.freebsd.org/pipermail/freebsd-arch/2006-July/005496.html > > Yes, this thread talks about the problem exactly. The patch I just sent > out attempts to address this concern using a user-settable sysctl. > Peter is suggesting this be handled automatically by setting a > reasonable default limit on RLIMIT_MEMLOCK. Yeah and even rwatson liked his suggest. I like automatically better, but tweak in sysctl is fine with me too. Some hardcore probably prefer sysctl than automatically one. >> It leads to: >> >> http://people.freebsd.org/~kib/overcommit/index.html >> >> I am not sure if it's useful for this issue. > > This doesn't look like it will help this issue. This is dealing with > overcommitting swap. It's what I though so. Cheers, Mezz > Joe -- mezz7@cox.net - mezz@FreeBSD.org FreeBSD GNOME Team http://www.FreeBSD.org/gnome/ - gnome@FreeBSD.org