public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Jacob Schmude <jschmude@adelphia.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: regarding speech-dispatcher, dectalk and the init script
Date: Sun, 2 May 2004 06:09:51 -0400 (Eastern Standard Time)	[thread overview]
Message-ID: <Pine.WNT.4.58.0405020606390.3816@beavis> (raw)
In-Reply-To: <20040502083350.GA1257@volny.cz>

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.


  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Hynek Hanke
 ` Jacob Schmude [this message]
   ` Hynek Hanke
     ` Jacob Schmude
       ` Hynek Hanke
         ` Jacob Schmude
           ` Cheryl Homiak
       ` nick G
         ` dking
           ` Gregory Nowak
       ` Hynek Hanke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.WNT.4.58.0405020606390.3816@beavis \
    --to=jschmude@adelphia.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).