Buchan Milne wrote:
also would depend on the design ( hardware wise ) of your network.[EMAIL PROTECTED] wrote:On 31 Jan 2003, Austin Acton wrote:
What I think is the problem is that they want jackd to be able to reschedule any program at some moment in time. For this, they would continuously need the ability to mess with the scheduler.
I would consider this a very non-secure thing, not much better than having it run all the time as root. Though I wonder why that is not possible.
So what's wrong with having jackd (configurable via /etc/sysconfig/jackd or something) start via an init script, and (configurable, disabled by default) be able to run as root?? Do the jack clients need to be running as root or not?Anyway, it seems that this is only possible by sacrificing security: do we want that in the low_lat kernel or not?
Probably not.Obviously the alternatives are even worse (unreliable low latency operation, or running everything as root)But does *everything*, or only jackd, need to run as root?Funny to see how these audio people thing low latencies are worse that a security problem.
Depends what your business is I guess ... Buchan
if you are running through a *nix router/gateway/firewall from the server to the extranet, then the intranet ( local ) security can be lowered for internal use, without a major reduction in security overall.
high tight security on external connection, lowered internal security to purchase the application speed /ease of use that increases productivity.
3d rendering eats cpu capacity, being able to keep as much free for rendering as possible speeds the process up. ( I have seen simple renders of a static scene from 3d mesh take 36+ hours, with only a high security setup. ( firewall / intrusion detection ) if the security level could be reduced on that workstation, then that same render would use less time to accomplish. this same concept will apply to sound editing as well as video compositing.
