Re: [orca-list] Alsa-OSS Politics?

[Michael Whapples <mwhapples aim com>]

I hadn't considered running speech-dispatcher under the user. Couple of
questions regarding this:
I know there are files run specific to users at start up, but is there
files run when a user logs out, which could stop speech-dispatcher?
Possibly related to the above, what would happen if two users were
logged in on different terminals? They would need different ports for
speech-dispatcher to use, and so would the clients be able to cope? (An
example of this is, I use multiple text consoles for different things,
and if someone who was also a user of the system were to say "Can I
quickly..." I would probably would have them log in on yet another text
console, so leaving my log ins on the other terminals, so now we may
have multiple user speech-dispatchers at one time)

While you may have answers to the above, and no problems may actually
exist, I am interested as to why the audio output is in module
configuration and not speech-dispatcher's main configuration? You may
have a perfectly good reason for this, if so please enlighten me as the
reason seems to be escaping me.

From
Michael Whapples
On Mon, 2007-11-05 at 09:05 +0100, Tomas Cerha wrote:
> Michael Whapples napsal(a):
> > If Luke is right, then either you would need a user specific set of
> > modules (which would be difficult as speech-dispatcher loads all modules
> > at start up), or have audio output moved from module configuration to
> > where clients can modify setup.
> 
> Hello Michael, this would not be necessary if the whole Speech
> Dispatcher was running under the current user, which, I believe, would
> be the best solution to the problem Luke described.
> 
> Best regards
> 
> Tomas