* Sending Text to Synthesizer @ ace ` Kenny Hitt 0 siblings, 1 reply; 7+ messages in thread From: ace @ UTC (permalink / raw) To: speakup Hello all, My system has been up for over one-hundred days. I have hooked up another keyboard and the synthesizer. Well, now, Speakup will not talk. Isn't there a proc command or something I can to where I can send text to echo? I can log into the box remotely and want to send some text to the synth to see if Speakup didn't just die. I really don't want to reboot! Network Administrator of irc.talkingirc.com http://www.talkingirc.com ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Sending Text to Synthesizer Sending Text to Synthesizer ace @ ` Kenny Hitt ` ace 0 siblings, 1 reply; 7+ messages in thread From: Kenny Hitt @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Hi. Try echoing "none" to /proc/speakup/synth_name. Then, echo the string for the connected synth to /proc/speakup/synth_name. Note, this info assumes you are running speakup 2.0. If you are still using speakup 1.5, then just ignore. Also, it assumes you have the driver for for the connected synth built for speakup 2.0. It can be a module or built in, doesn't matter. Hope this helps. Kenny On Sat, May 07, 2005 at 04:14:24PM -0400, ace wrote: > Hello all, > > My system has been up for over one-hundred days. I have hooked up another > keyboard and the synthesizer. Well, now, Speakup will not talk. Isn't > there a proc command or something I can to where I can send text to > echo? I can log into the box remotely and want to send some text to the > synth to see if Speakup didn't just die. I really don't want to reboot! > > Network Administrator of > irc.talkingirc.com > http://www.talkingirc.com > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Sending Text to Synthesizer ` Kenny Hitt @ ` ace ` killing off loged in users wasRe: " Kenny Hitt ` Steve Holmes 0 siblings, 2 replies; 7+ messages in thread From: ace @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. It worked, thanks. Someone a while ago told me a command I could type to list all of the ttys logged into the box so I could kill them. What is it? Something like ps -auxr|grep ttys but it didn't work. I think I have a frozen console. I might end up rebooting <frown> At 11:38 PM 5/7/2005, you wrote: >Hi. > >Try echoing "none" to /proc/speakup/synth_name. Then, echo the string >for the connected synth to /proc/speakup/synth_name. > >Note, this info assumes you are running speakup 2.0. If you are still >using speakup 1.5, then just ignore. Also, it assumes you have the >driver for for the connected synth built for speakup 2.0. It can be a >module or built in, doesn't matter. > >Hope this helps. > Kenny > >On Sat, May 07, 2005 at 04:14:24PM -0400, ace wrote: > > Hello all, > > > > My system has been up for over one-hundred days. I have hooked up another > > keyboard and the synthesizer. Well, now, Speakup will not talk. Isn't > > there a proc command or something I can to where I can send text to > > echo? I can log into the box remotely and want to send some text to the > > synth to see if Speakup didn't just die. I really don't want to reboot! > > > > Network Administrator of > > irc.talkingirc.com > > http://www.talkingirc.com > > > > > > _______________________________________________ > > Speakup mailing list > > Speakup@braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > >_______________________________________________ >Speakup mailing list >Speakup@braille.uwo.ca >http://speech.braille.uwo.ca/mailman/listinfo/speakup Network Administrator of irc.talkingirc.com http://www.talkingirc.com ^ permalink raw reply [flat|nested] 7+ messages in thread
* killing off loged in users wasRe: Sending Text to Synthesizer ` ace @ ` Kenny Hitt ` Adam Myrow ` Steve Holmes 1 sibling, 1 reply; 7+ messages in thread From: Kenny Hitt @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. Hi. I'm sure there's more than one way to do it, but try who The who command will tell you all the users loged into the system. Then use ps aux|grep username Substitute the user you want to kill for username. Notice the process id for everything running as that user and to kill -9 pid Play around and see what happens. If you take out the bash process for the user on a specific tty, you will usually kill every other process on that tty. Like I said, play around and see how it will work. I'm probably not explaining well, but you will see what I mean by playing. Hope this helps. Kenny On Sun, May 08, 2005 at 02:21:25AM -0400, ace wrote: > It worked, thanks. Someone a while ago told me a command I could type to > list all of the ttys logged into the box so I could kill them. What is > it? Something like ps -auxr|grep ttys but it didn't work. I think I have > a frozen console. I might end up rebooting <frown> > ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: killing off loged in users wasRe: Sending Text to Synthesizer ` killing off loged in users wasRe: " Kenny Hitt @ ` Adam Myrow ` Steve Dawes 0 siblings, 1 reply; 7+ messages in thread From: Adam Myrow @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. On Sun, 8 May 2005, Kenny Hitt wrote: > Hi. I'm sure there's more than one way to do it, but try > > who > > The who command will tell you all the users loged into the system. > > Then use > > ps aux|grep username Actually, "ps -u username" is quicker. This doesn't always work, but sending a hangup "kill -1" to a shell like bash, or tcsh, will often cause all the other processes under that shell to exit. One thing that really isn't taught much is to use "kill -9" as an absolute last resort. Since "kill -9" can't be ignored or trapped, any unsaved data will be lost when the process exits. Generally, the hangup works better for editors and such, as they will usually save any unsaved data in a temporary file. For example, vi clones like vim and elvis will save unsaved data in /var/tmp, and there is a "-r" option to recover them. Pine will save any partial email when sent a terminate or hangup signal, and ask you about it the next time you go to compose a new email. Of course, if you don't want the process to save anything, a -9 will do that. Then, there are the daemons that treat hangup as a command to re-read their log files. It's best to kill those with any script for them, otherwise, try the default signal of 15, or use a "kill -9" as a last resort. ^ permalink raw reply [flat|nested] 7+ messages in thread
* RE: killing off loged in users wasRe: Sending Text to Synthesizer ` Adam Myrow @ ` Steve Dawes 0 siblings, 0 replies; 7+ messages in thread From: Steve Dawes @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. You could also set a time out if the userid has been idel for a defined amount, then automatically logout. I know that this exists, but I don't remember how to set this up. Steve Steve Dawes Calgary Canada. -----Original Message----- From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]On Behalf Of Adam Myrow Sent: Sunday, May 08, 2005 10:00 AM To: Speakup is a screen review system for Linux. Subject: Re: killing off loged in users wasRe: Sending Text to Synthesizer On Sun, 8 May 2005, Kenny Hitt wrote: > Hi. I'm sure there's more than one way to do it, but try > > who > > The who command will tell you all the users loged into the system. > > Then use > > ps aux|grep username Actually, "ps -u username" is quicker. This doesn't always work, but sending a hangup "kill -1" to a shell like bash, or tcsh, will often cause all the other processes under that shell to exit. One thing that really isn't taught much is to use "kill -9" as an absolute last resort. Since "kill -9" can't be ignored or trapped, any unsaved data will be lost when the process exits. Generally, the hangup works better for editors and such, as they will usually save any unsaved data in a temporary file. For example, vi clones like vim and elvis will save unsaved data in /var/tmp, and there is a "-r" option to recover them. Pine will save any partial email when sent a terminate or hangup signal, and ask you about it the next time you go to compose a new email. Of course, if you don't want the process to save anything, a -9 will do that. Then, there are the daemons that treat hangup as a command to re-read their log files. It's best to kill those with any script for them, otherwise, try the default signal of 15, or use a "kill -9" as a last resort. _______________________________________________ Speakup mailing list Speakup@braille.uwo.ca http://speech.braille.uwo.ca/mailman/listinfo/speakup ^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: Sending Text to Synthesizer ` ace ` killing off loged in users wasRe: " Kenny Hitt @ ` Steve Holmes 1 sibling, 0 replies; 7+ messages in thread From: Steve Holmes @ UTC (permalink / raw) To: Speakup is a screen review system for Linux. -----BEGIN PGP SIGNED MESSAGE----- Hash: RIPEMD160 You might try 'ps -t tty#' where # is substituted with each tty of choice. Of course if you are looking at remote users, you would do 'ps - -t pts/#' (I think). If you got a bunch of terminals connect, this is obviously an efficient way to come about. Dunno if there is an easyer way to do this or not. I've tracked down bad terms that way but I have few terminals too. On Sun, May 08, 2005 at 02:21:25AM -0400, ace wrote: > It worked, thanks. Someone a while ago told me a command I could type to > list all of the ttys logged into the box so I could kill them. What is > it? Something like ps -auxr|grep ttys but it didn't work. I think I have > a frozen console. I might end up rebooting <frown> > > At 11:38 PM 5/7/2005, you wrote: > >Hi. > > > >Try echoing "none" to /proc/speakup/synth_name. Then, echo the string > >for the connected synth to /proc/speakup/synth_name. > > > >Note, this info assumes you are running speakup 2.0. If you are still > >using speakup 1.5, then just ignore. Also, it assumes you have the > >driver for for the connected synth built for speakup 2.0. It can be a > >module or built in, doesn't matter. > > > >Hope this helps. > > Kenny > > > >On Sat, May 07, 2005 at 04:14:24PM -0400, ace wrote: > >> Hello all, > >> > >> My system has been up for over one-hundred days. I have hooked up > >another > >> keyboard and the synthesizer. Well, now, Speakup will not talk. Isn't > >> there a proc command or something I can to where I can send text to > >> echo? I can log into the box remotely and want to send some text to the > >> synth to see if Speakup didn't just die. I really don't want to reboot! > >> > >> Network Administrator of > >> irc.talkingirc.com > >> http://www.talkingirc.com > >> > >> > >> _______________________________________________ > >> Speakup mailing list > >> Speakup@braille.uwo.ca > >> http://speech.braille.uwo.ca/mailman/listinfo/speakup > > > >_______________________________________________ > >Speakup mailing list > >Speakup@braille.uwo.ca > >http://speech.braille.uwo.ca/mailman/listinfo/speakup > > Network Administrator of > irc.talkingirc.com > http://www.talkingirc.com > > > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- HolmesGrown Solutions The best solutions for the best price! http://ld.net/?holmesgrown -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.7 (GNU/Linux) iD8DBQFCfi8cWSjv55S0LfERAyFAAKCEsp9I+zPMh78lhM0zTiB2c+YOCQCgqgv2 CsuoJjnUlx/M/soKf5EXB04= =MVp/ -----END PGP SIGNATURE----- ^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~ UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
Sending Text to Synthesizer ace
` Kenny Hitt
` ace
` killing off loged in users wasRe: " Kenny Hitt
` Adam Myrow
` Steve Dawes
` Steve Holmes
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).