Seahorse issues

Jeremy Messenger mezz7 at
Sat Apr 12 18:18:00 UTC 2008

On Sat, 12 Apr 2008 12:49:23 -0500, Joe Marcus Clarke  
<marcus at> 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> 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 .
> 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:
>> 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.


> Joe

mezz7 at  -  mezz at
FreeBSD GNOME Team  -  gnome at

More information about the freebsd-gnome mailing list