From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mta13.mail.adelphia.net ([68.168.78.44] helo=mta13.adelphia.net) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1BKDxW-0006VQ-00 for ; Sun, 02 May 2004 06:12:30 -0400 Received: from beavis.lkwnny.adelphia.net ([69.166.61.22]) by mta13.adelphia.net (InterMail vM.5.01.06.08 201-253-122-130-108-20031117) with ESMTP id <20040502101158.WXTN13425.mta13.adelphia.net@beavis.lkwnny.adelphia.net> for ; Sun, 2 May 2004 06:11:58 -0400 Date: Sun, 2 May 2004 06:09:51 -0400 (Eastern Standard Time) From: Jacob Schmude To: "Speakup is a screen review system for Linux." In-Reply-To: <20040502083350.GA1257@volny.cz> Message-ID: References: <20040502083350.GA1257@volny.cz> X-X-Sender: jschmude@mail.adelphia.net MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: regarding speech-dispatcher, dectalk and the init script X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.4 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 May 2004 10:12:30 -0000 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.