csh jobs/tostop bug

[utzoo!decvax!harpo!floyd!vax135!ariel!orion!lime!burdvax!psuvax!sibley]

The article from utah-gr!thomas contained a reasonable analysis of the
"stty tostop" problem, but missed at least one important point.  A little
experimentation shows that most stty commands stop when run in background,
regardless of the setting of "tostop".  I guess this is a feature, so
background jobs can't affect your terminal, similar to the way they can't
change the environment.  At least this is consistent.

Try
	stty tabs &
Whether you have tabs or tostop set or not, this stops with the
	(tty output)
message.  This is a little confusing, as there isn't really any output.
It's just unwilling to change things unless it's in foreground.

Since stty calls are equivalent to ioctl's, I guess ioctl would show the
same behavior.  I can't find any of this in the manual, however.

Dave Sibley
Department of Mathematics
Penn State University
psuvax!sibley