[ale] X hangs at start

[Chris Fowler]

>tty > /dev/null && stty -ixon -ixoff 

Why would you want to send the output of the tty command to /dev/null.
All it does is disply the controlling ttyname to STDOUT.

The only thing I can say, would be that maybe stty was blocking.   But
are you haning on the stty execution.  The only reason I could see to
use this command would be over serial terminals. 

I believe the only benefit of hagin swflow on a vt is to allow the user
to use ^s and ^q to temporarily tell the vt driver to stop sending
output.  ^q will turn flow back on.




On Fri, 2003-03-21 at 11:35, Michael D. Hirsch wrote:
> At either the Jan or Feb ALE Central meeting I asked if anyone could 
> explain why my .Xclients script would hang before it did anything.  I now 
> have additional information, but I still don't understand.  I'm hoping 
> someone can shed some light.
> 
> It turns out that it was hanging in my .bashrc file.  For several years 
> I've had these lines in my .bashrc:
> 	# turn off XON/XOFF, but only for a tty
> 	tty > /dev/null && stty -ixon -ixoff
> I've been using RedHat 8.0 for several months, but after upgrading to KDE 
> 3.1 (and now 3.1.1) that line stopped working.  In fact, it would hang 
> forever when my .Xclients started running after startx.
> 
> Now, I rarely log out or reboot, and I'm sure I ugraded other parts of my 
> system before I did the kde.  It doesn't make sense that a KDE upgrade 
> would break things, so I'm guessing it isn't a KDE problem.  Some other 
> part of the system is hanging me up.
> 
> Any clues?
> 
> Puzzled,
> 
> Michael
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://www.ale.org/mailman/listinfo/ale


_______________________________________________
Ale mailing list
Ale at ale.org
http://www.ale.org/mailman/listinfo/ale