Date: Sat, 12 Apr 2008 13:49:23 -0400 From: Joe Marcus Clarke <marcus@marcuscom.com> To: Jeremy Messenger <mezz7@cox.net> Cc: gnome@freebsd.org, cokane@freebsd.org Subject: Re: Seahorse issues Message-ID: <1208022563.82222.22.camel@shumai.marcuscom.com> In-Reply-To: <op.t9id5keu9aq2h7@mezz.mezzweb.com> References: <47FD09AC.2020907@FreeBSD.org> <1207776230.61729.28.camel@shumai.marcuscom.com> <47FD34E8.2000005@FreeBSD.org> <1207807915.61729.40.camel@shumai.marcuscom.com> <op.t9id5keu9aq2h7@mezz.mezzweb.com>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] On Sat, 2008-04-12 at 12:42 -0500, Jeremy Messenger wrote: > On Thu, 10 Apr 2008 01:11:55 -0500, Joe Marcus Clarke > <marcus@marcuscom.com> wrote: > > <snip> > > 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. > > 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. Joe -- PGP Key : http://www.marcuscom.com/pgp.asc [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.8 (FreeBSD) iEYEABECAAYFAkgA9iMACgkQb2iPiv4Uz4cOdwCfUfuJn2+Jaic1TleYoJRmCaCI wUkAn3sOfTNyrM8lfC6JKpOBV0UrPjmB =x70p -----END PGP SIGNATURE-----help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1208022563.82222.22.camel>