public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: Dave Mielke <dave@mielke.cc>
To: <blinux-list@redhat.com>
Subject: re: job prob
Date: Tue, 19 Mar 2002 07:38:15 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.30.0203190717210.2694-100000@dave.private.mielke.cc> (raw)
In-Reply-To: <200203191155.EAA10392@nyx.nyx.net>

[quoted lines by Brian Tew on March 19, 2002, at 04:55]

>if i start a job with the ampersand at the end, it is backgrounded.
>but if i then fg that job, i cannot suspend it.

I think I know what's going on. If I'm not mistaken, you're the same guy who's
also using the VBii+, and starting bash from rc.local. If I'm remembering
correctly, you're invoking bash via su with "&>/dev/ttyS0" in order to redirect
all output to the VersaBraille. Therein may lie your problem. Speaking to what
old software does (I believe you also said you're using RedHat 5.2) is always
difficult, but here's a possibility.

Bash only automatically turns on its interactive mode if both its standard
input and standard output are connected to a tty. Strictly speaking, standard
output, being connected to /dev/ttyS0, is connected to a tty. The fact that
it's not the foreground tty, however, may be what's causing your problem. Bash
may not think it should start up in interactive mode. You can tell if it's in
interactive mode by looking at the content of the special environment variable
"$-" (dollar minus). If it doesn't contain the ltter "i", then bash isn't in
interactive mode.

-- 
Dave Mielke           | 2213 Fox Crescent | I believe that the Bible is the
Phone: 1-613-726-0014 | Ottawa, Ontario   | Word of God. Please contact me
EMail: dave@mielke.cc | Canada  K2A 1H7   | if you're concerned about Hell.
http://familyradio.com




  parent reply	other threads:[~ UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Brian Tew
 ` Dave Mielke
 ` Dave Mielke [this message]
  -- strict thread matches above, loose matches on Subject: below --
 Brian Tew
 Brian Tew
 ` Dave Mielke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.30.0203190717210.2694-100000@dave.private.mielke.cc \
    --to=dave@mielke.cc \
    --cc=blinux-list@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).