From: Anthony (avan_at_uwm.edu)
Date: 10/21/03 12:54 EDT
From: Anthony <avan@uwm.edu> Subject: Re: [Ardour-users] Ardour + Jack and user permissions Message-ID: <20031021165434.GA13932@alpha1.csd.uwm.edu> Date: Tue, 21 Oct 2003 11:54:35 -0500 Hi David, this is all covered in the jack faq. You need to patch your kernel to provide capabilites and compile jack with --enable-capabilites. Then start jack using 'jackstart' --ant * David Snopek <xevol@newtonave.net> [Oct 21 03 10:52]: > > I have a studio setup in the basement of my duplex and we have four > musicians living here. So I want to set it up so that each user can have > there own seperate collection of sounds and sessions. I have my > super-fast harddisk mounted on /home to faciltate this. Each user is part > of an "audio" group which lets them read/write to the alsa device. > > So anyone can log in and do: > > jackd -d alsa -d hw & > ardour > > But I really want to use "realtime" mode like this: > > jackd -R -d alsa -d hw > > Unfortunately, only root can set a thread to "realtime". But when I start > jackd as root, ardour reports that no jack server is running unless it is > also run as root. I am assuming that this is because the sockets/fifos in > /dev/shm/ are owned by root:root with only "wx" for the owner. > > I have tried a number of things to fix this but ardour always reports > something like "cannot connect to shared memory". For the record, I > tried: > > (1) Setting up sudo so that anyone in the "audio" group can run jackd as > a special "audio" user whose default group is "audio". This of course > failed immediately because the group permission on the /dev/shm/ stuff > isn't right. I tried chmod'ing it g+rwx to no avail. > > (2) Making an /etc/init.d script that starts jackd as root and > chmod/chown's it so that the "audio" group has "rwx" permission. > > Does anyone have any ideas? I could just setup sudo to allow users to run > both jackd and ardour as root but I am the only person in the household > who really understands Unix-a-likes and don't like the idea of someone > accidently writting to delicate parts of the filesystem. Is there any way > to allow normal users to set threads as "realtime"? Why doesn't changing > the permissions on /dev/shm/* not help? Is there something I can change > in the jack source so the they are created with the right permissions > initially? > > Thanks for any help, > -- David Snopek. > > > > ------------------------------------------------------- > This SF.net email is sponsored by OSDN developer relations > Here's your chance to show off your extensive product knowledge > We want to know what you know. Tell us and you have a chance to win $100 > http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 > _______________________________________________ > Ardour-users mailing list > Ardour-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/ardour-users ------------------------------------------------------- This SF.net email is sponsored by OSDN developer relations Here's your chance to show off your extensive product knowledge We want to know what you know. Tell us and you have a chance to win $100 http://www.zoomerang.com/survey.zgi?HRPT1X3RYQNC5V4MLNSV3E54 _______________________________________________ Ardour-users mailing list Ardour-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ardour-users
This archive was generated by hypermail 2.1.7 : 10/21/03 13:04 EDT