2 Dec
2012
2 Dec
'12
9:16 p.m.
(to the Jack devs)
Any chance of JACK_PROMISCUOUS_SERVER being returned to
working order ?
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
2 Dec
2 Dec
9:31 p.m.
what doesn't work? i've seen people using it on #jack within the last
several months
On Sun, Dec 2, 2012 at 3:16 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
(to the Jack devs)
Any chance of JACK_PROMISCUOUS_SERVER being returned to
working order ?
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev(a)lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev
9:53 p.m.
On Sun, Dec 02, 2012 at 03:31:28PM -0500, Paul Davis wrote:
what doesn't work? i've seen people using it
on #jack within the last
several months
Seems like jack_client_open() fails. Unless the user is the same
one that started jackd. JACK_PROMISCUOUS_SERVER defined for both
server and clients.
jackd version 0.121.3 tmpdir /dev/shm protocol 24
downloaded and installed today.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
10:13 p.m.
the thing to check are the permissions on the nodes under /dev/shm/jack
the main (only) thing that the promiscuous server does is to change those
permissions so that people other than the user that started jack can access
them. your umask or other system settings might interfere with this.
On Sun, Dec 2, 2012 at 3:53 PM, Fons Adriaensen <fons(a)linuxaudio.org> wrote:
On Sun, Dec 02, 2012 at 03:31:28PM -0500, Paul Davis
wrote:
what doesn't work? i've seen people using
it on #jack within the last
several months
Seems like jack_client_open() fails. Unless the user is the same
one that started jackd. JACK_PROMISCUOUS_SERVER defined for both
server and clients.
jackd version 0.121.3 tmpdir /dev/shm protocol 24
downloaded and installed today.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
10:21 p.m.
On Sun, Dec 02, 2012 at 04:13:41PM -0500, Paul Davis wrote:
the thing to check are the permissions on the nodes
under /dev/shm/jack
the main (only) thing that the promiscuous server does is to change those
permissions so that people other than the user that started jack can access
them. your umask or other system settings might interfere with this.
Setting umask for the server gets me past jack_client_open(), but
then then things fail further on. Not clear how exactly ATM.
Ciao,
--
FA
A world of exhaustive, reliable metadata would be an utopia.
It's also a pipe-dream, founded on self-delusion, nerd hubris
and hysterically inflated market opportunities. (Cory Doctorow)
4403
days inactive
4403
days old
linux-audio-dev@lists.linuxaudio.org
4 comments
2 participants
participants (2)
-
Fons Adriaensen -
Paul Davis