Re: [Jack-Devel] jackdmp 1.9.10 on debian/sid refuse to start with --unlock

On Wed, Jul 17, 2013 at 5:38 AM, Stéphane Letz <[hidden]> wrote:

> AFAIR --unlock was never really implemented in jack2
>
> Stéphane
>
> Le 17 juil. 2013 à 13:45, hermann meyer <[hidden]> a écrit :
>
> > Hi
> >
> > I've just upgraded my debian/sid system, that include a jackdmp update
> to version 1.9.10 (from 1.9.8)
> > Usually I use the -u option --unlock, but now jackd refuse to start with
> that option enabled. It say's
> >  unknown option character
> >
> > I just wonder, is the -u --unlock commandline option removed from
> jackdmp 1.9.10?
> > If so, is there a special reason for that?
> > Or is it debian specific?
> > However, the -u option is still mention in the debian man page, so there
> is at least a bug somewhere which needs to be addressed and solved.
> >
> > greets
> > hermann
>
>
Say again? Does this mean that jack2 mlocks the entire process memory,
including giant GUI libraries like QT and GTK? Or is some other mechanism
in place? Are clients perhaps expected to lock their own critical memory in
JACK2? If so, I think that's a reasonable, but people certainly need to be
made aware of it--maybe the JACK API should even include a wrapper function
for the purpose.

1374251493.13379_0.ltw:2,a <CAGhWSSbwRH+mv13srYN_QA7UEKhy9=yy4XAEEhqfV6beSquwNQ at mail dot gmail dot com>