From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp2.commspeed.net ([216.19.2.41]) by speech.braille.uwo.ca with esmtp (Exim 3.36 #1 (Debian)) id 1HIX30-0000UV-00 for ; Sat, 17 Feb 2007 16:24:46 -0500 Received: (qmail 59505 invoked by uid 1034); 17 Feb 2007 21:24:15 -0000 Received: from mmds-216-19-30-69.mm.az.commspeed.net (HELO YOUR3ADE1B78A3) (216.19.30.69) by smtp2.commspeed.net with SMTP; 17 Feb 2007 21:24:15 -0000 Message-ID: <000c01c752d9$f95e34b0$6401a8c0@YOUR3ADE1B78A3> From: "Keith Hinton" To: Subject: Regarding Speech-Dispatcher, Speechd-up, and ESpeak with Speakup. Date: Sat, 17 Feb 2007 14:24:14 -0700 MIME-Version: 1.0 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2900.2869 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.9 X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.9 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: Sat, 17 Feb 2007 21:24:47 -0000 Hi List, I'm more convinced then ever now that speechd-up is what is crashing. I = have to keep typing "Speechd-up" to restore communication. The question is: Why? What exactly was that backtrace about? Could a chron job be setup to monitor if speechd-up is running, and if = it crashes or whatever, instantly reboot it the instant it crashes? I need a temporary workaround, short of turning off keyboared echo in = Speakup with ESpeak. This, as I have said is on AMD64 machines, = spisifically. Speechd-up does not crash on my Pentium box, no matter what I do, doesn't matter = how fast I type with keyboared echo on, somehow it's able to keep = running. On my AMD Athlon server, however it will crash after a period of time, wich I cannot define. It just will = suddenly crash. As long as ESpeak is being used (Sinse it is so = responsive compared to a laggy Flite) On my AMD that has one gig of RAM, it is severely responsive. So quick, that I believe Speechd-up gets overwelmed with the generic = module reloading, etc. So, Speechd-up chooses to crash. What do you all = think about my question, suggestions? Regards, --Keith.