Hi Eugene, not sure it wil help (and maybe Fred wil point me as a sinner) but try to do the following. - Suppose in /etc/rd.conf in the identity lines you have user: rivendell and audiogroup: rivendell - Then for all caed, ripcd, rdcatchd, jackd launch this as root (in this order): chown rivendell:rivendell /usr/bin/caed (then do it for the others) chmod 6755 /usr/bin/caed (maybe they're in /usr/local/bin).
By doing this you impose that executables will run always under rivendell:rivendell regardless whom they exectued by. The simple ownership for executables, like jackd, it doesn't mean that much. Because even though they belong to 'rivendell' but the user who launch it is 'alessio' they will run as 'alessio' in the end. It's that 'chmod' with the 6 ahead which makes the difference. Now try to launch everything as a normal user (let's say you log in linux as 'alessio'). You open a terminale and do $ jackd -d dummy & (or your favourite jack setup) Now open 'htop' or do a 'ps aux | grep jackd' and you should see that jackd runs under 'rivendell' regardless it was 'alessio' that launched. Now do the same with the rest: Open 'rdadmin' (alessio) -> it will call caed,ripcd,rdcatchd -> but they've been setuid -> they will run as 'rivendell'. Again, check with htop. In this configuration 'caed' (which is responsible of searching for audio resources). It will check these things, in this order: - AudioScience cards - ALSA cards (/etc/asound.conf, rd0, rd1, ...) - JACK server As a debug you can see what's going on by doing this: - Launch jack in terminal as told above - In terminal do: "caed -d" -> it wil tell you what it finds. Again, maybe this is not the correct way to go. Only Fred knows (and most of times it changes from scenario to scenario)... In mine it does its job :-) Hope it helps! Alessio Il giorno lun 25 mag 2015 alle ore 20:33 Eugene <[email protected]> ha scritto: > OK, let's try this again and I'll be more direct. Getting acquainted > with Rivendell Appliance v2.10.2 and want to connect to jackd server in > order to use processing (stereo tool). Here are my specific issues so far: > > (1) Since Jack must be run as same owner as Rivendell daemons... > I checked and seem to have a combination of user/owner assignments (no > doubt revealing my linux ignorance). > > When I ls -l /var/run/rivendell the result is... > > caed and ripcd are "rivendell:root" > jackd and rdcatchd are "root:root" > > so, I changed jackd to "rivendell:root" and the result was still no > evidence of jack in the Rivendell host> Audio resource listing, or > Rivendell in the jack connect list. Yes I restarted rivendell services > with no change. > > Also, if it matters, > When I ls -l /var the result is... > /var/snd is "rivendell:rivendell" > > (2) ...and this is likely a hitch, in Rivendell Manage Hosts>Jack > Settings, I've checked the box to start the server, added the "default" > name, but not sure what goes in the command line(s) for Jack and Jack > clients (if anything). > > Probably all very elementary, but perhaps setting specific to the > appliance. Greatly appreciate any suggestions > > Eugene > > _______________________________________________ > Rivendell-dev mailing list > [email protected] > http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev >
_______________________________________________ Rivendell-dev mailing list [email protected] http://caspian.paravelsystems.com/mailman/listinfo/rivendell-dev
