> for exquisite confusion, background jobs may also input from the terminal. if there's a setting that controls that, i'm unaware... In the darker days of my youth, I routinely used this feature with some of the scripts a coworker delivered for company use. I distinctly remember the day in college when we also figured out how to send raw keystrokes from one SSH session to another. We had left a 'yum upgrade' running, and it was waiting for a 'y' to confirm the changes, and we had not yet discovered the wonderous thing known as 'screen', and would rather figure out how to echo keys through /dev/pts0 than kill and restart a process on a new session. On Tue, Nov 27, 2018 at 3:21 PM gregrwm <tclug1 at whitleymott.net> wrote: > For example, it is well known that "background processes" can't use the >> terminal interface. But try start several xterm& (background xterms) and >> you will still get several fully functional xterm windows. > > > background jobs may indeed output to the terminal, unless > stty tostop > is in effect, whereupon the job will receive the TSTP signal upon > attempting output to the terminal. the default result of receiving TSTP is > for the job to be stopped. > > for exquisite confusion, background jobs may also input from the > terminal. if there's a setting that controls that, i'm unaware... > _______________________________________________ > TCLUG Mailing List - Minneapolis/St. Paul, Minnesota > tclug-list at mn-linux.org > http://mailman.mn-linux.org/mailman/listinfo/tclug-list > -- Jeff Chapin President, CedarLug, retired President, UNIPC, "I'll get around to it" President, UNI Scuba Club Senator, NISG, retired -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mailman.mn-linux.org/pipermail/tclug-list/attachments/20181127/a24fbddc/attachment.html>