Hi The dectalk's say program works fine when executed in an initscript by itself. I put it at the exact same point as I've tried to start speech dispatcher and it works. It doesn't communicate with a server, it communicates with the dectalk libraries. For the record, I'm using slackware, so this init problem isn't tied down to one distribution. I have it executing in rc.local, which means that it executes right before the login prompt. By then, all hardware is up, including sound. None of the log files, speechd, dtk-generic, nor speechd-up indicate any error messages. On Sun, 2 May 2004, Hynek Hanke wrote: > > Hi all, > > there are currently running various threads that complain that > the speech dispatcher's dectalk output module doesn't work if > speech dispatcher is started early during the boot process (before > login). > > I don't know what may cause this, but possibly the problem can be > that the dectalk "say" program can't operate yet when speech-dispatcher > is starting. If it communicates to some server and the server is not > running yet, maybe the say command returns with an error and the output > module dies.
