Does this happen often? I have _never_ seen it with a standard ap, without me having done something to cause it predictably, or without having something wrong in the kernel. Killing bash is probably the way to go. Could it be a soft flow control issue? Luke On Tue, 13 Apr 2004, Igor Gueths wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Try going into a spare tty and killing -9 the bash process in the frozen > console. Then you log back in and all is well. > On Tue, Apr 13, 2004 at 09:42:09PM -0400, Alex Snow wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA1 > > > > Hi all. > > just wondering the best solution for thawing a tty that's completely > > frozen. in this particular case lynx was the app that froze but I've > > seen it happen with epic and a few other progs. I try kill -9 the > > process but nothing. > > thanks. > > > > - -- > > > I get the following error messages at bootup, could anyone tell me > > > what they mean? > > > fcntl_setlk() called by process 51 (lpd) with broken flock() emulation > > They mean that you have not read the documentation when upgrading the > > kernel. > > -- seen on c.o.l.misc > > -----BEGIN PGP SIGNATURE----- > > Version: GnuPG v1.2.3 (GNU/Linux) > > > > iD8DBQFAfJbx9XVrM3ri110RAp7QAJ9JxwEF9j8k0oJ3LFuico8rKFIOhwCfSIG4 > > QsUY32nqLXtA/h/AAgIRpbs= > > =EFpg > > -----END PGP SIGNATURE----- > > > > _______________________________________________ > > Speakup mailing list > > Speakup at braille.uwo.ca > > http://speech.braille.uwo.ca/mailman/listinfo/speakup > > - -- > Failure is not an option, it comes bundled with your Microsoft product. > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > > iD8DBQFAfKDuNohoaf1zXJMRAqoqAJ9Wg7K/velUNIAY4T8RwVwrq1An3wCdFMHJ > k4CMGbbdTc5Mwh2vEOyyD5Q= > =vWnT > -----END PGP SIGNATURE----- > > _______________________________________________ > Speakup mailing list > Speakup at braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup >
