Icecast - Oct 2004 - [Jackit-devel] Re: ices-kh dropping jack ports unexpectedly

On Mon, 2004-10-18 at 18:27, Jack O'Quin wrote:
> Karl Heyes <karl@xiph.org> writes:
> 
> > Are you running with realtime privileges, for this you need to start
as
> > root if you want that. Even with realtime privileges there may be odd
> > cases where the scheduling latency is a bit too high, it all depends
on
> > the drivers and kernel version but the current state is not that bad
and
> > getting better.
> 
> There are several ways to gain realtime privileges.  Running as root
> is the simplest, but perhaps the worst solution.  
Just to be clear, with ices, you can drop to a nominated user after the
realtime scheduler is selected. Running as root after that is not
required.

karl

Karl Heyes <karl@xiph.org> writes:
> Are you running with realtime privileges, for this you need to start as
> root if you want that. Even with realtime privileges there may be odd
> cases where the scheduling latency is a bit too high, it all depends on
> the drivers and kernel version but the current state is not that bad and
> getting better.
There are several ways to gain realtime privileges.  Running as root
is the simplest, but perhaps the worst solution.  

This is explained in the JACK FAQ...

  http://jackit.sourceforge.net/docs/faq.php#a52
-- 
  joq

Karl Heyes <karl@xiph.org> writes:
> On Mon, 2004-10-18 at 18:27, Jack O'Quin wrote:
> > Karl Heyes <karl@xiph.org> writes:
> > 
> > > Are you running with realtime privileges, for this you need to
start as
> > > root if you want that. Even with realtime privileges there may be
odd
> > > cases where the scheduling latency is a bit too high, it all
depends on
> > > the drivers and kernel version but the current state is not that
bad and
> > > getting better.
> > 
> > There are several ways to gain realtime privileges.  Running as root
> > is the simplest, but perhaps the worst solution.  
> 
> Just to be clear, with ices, you can drop to a nominated user after the
> realtime scheduler is selected. Running as root after that is not
> required.
That does not solve the problem at all.  If you run jackd as root, you
must run *all* JACK clients as root.  They are not all coded that way,
and some cannot be.  Neither they nor jackd should be entrusted with
God-like superuser powers.
-- 
  joq