Seahorse issues

[Jeremy Messenger]

On Sat, 12 Apr 2008 12:49:23 -0500, Joe Marcus Clarke  
<marcus at marcuscom.com> 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
>> <marcus at 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 at .
>>
>> 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 at cox.net  -  mezz at FreeBSD.org
FreeBSD GNOME Team
http://www.FreeBSD.org/gnome/  -  gnome at FreeBSD.org