I have seen this question before, but still don't know the answer.
Arts seems to insist that you have suid set on (see link
Linux-software->arts problem ).
Currently I am looking at the "aRts Status" dialog which says:
Quote:
Artsd should run with realtime scheduling, but it does not (Is artswrapper suid root?).
The aRts sound daemon will not autosuspend right now because there are active modules.
|
Other users complain that they are unable to have sound from more than one software at a time because artswrapper is not "suid root".
I also find that the aRts devices are not 100% immediate in their response - which is vital if you are actually using aRts to do anything important.
So this is a good question - and it deserves a good answer. I will keep researching but sure wouldn't mind the advice of someone who KNOWS the answer. I suspect that anyone doing serious recording will have solved this one long ago
.
For now, I'm going to try going the suid route recommended finally by javaree in the link above:
Quote:
CD to the directory where artswrapper is located (/opt/kde/bin here)
As root type
chmod u+s artswrapper
The thing is: arts wants real-time priority, but you can only set that when running as root. As most people disapprove of 'regular' programs running as root, artswrapper comes into play. artwrapper runs as root (because of the chmod above), sets the real time priority, and then starts arts in this priority (as noon-root) before it exits.
|
