GNU BASH with Interactive 2.2 Job Control

GNU BASH with Interactive 2.2 Job Control

Post by Howard Wei » Sat, 23 Feb 1991 08:51:09



Has anyone built GNU BASH *with* job control for Interactive UNIX
release 2.2?  The existing job control code uses BSDisms (ie. sigblock,
sigsetmask, wait3).  I have attempted to convert sigblock to SYSV's
sigignore, but wait3 does not move over cleanly other than to waitpid.
Then there is the matter of trying to include <sys/wait.h> which presents
other compilations errors.

Thanks,

Howard Weiss


(301)381-9400 x201

 
 
 

GNU BASH with Interactive 2.2 Job Control

Post by Heiko Blu » Tue, 26 Feb 1991 00:12:10



>Has anyone built GNU BASH *with* job control for Interactive UNIX
>release 2.2?  The existing job control code uses BSDisms (ie. sigblock,
>sigsetmask, wait3).  I have attempted to convert sigblock to SYSV's
>sigignore, but wait3 does not move over cleanly other than to waitpid.
>Then there is the matter of trying to include <sys/wait.h> which presents
>other compilations errors.

i did, and posted some largish diffs to alt.sources about a month
ago. however, those diffs are for bash-1.05 and i think it's not
worthwile to use this very buggy version since 1.07 should come out
soon. i don't know if it will include support for posix job control,
but if it doesn't i'll hack it again.

if you want job control plus command line editing and don't mind
a non-bourne-shellish thing, i'd recommend using tcsh.
--

                  public UNIX source archive [HST V.42bis]:
        scuzzy Any ACU,f 38400 6919520 gin:--gin: nuucp sword: nuucp
                     uucp scuzzy!/src/README /your/home

 
 
 

1. JOB CONTROL FOR JOBS w/o a TTY (using BASH)?

I am running a large computation in IDL (takes 18 hrs) and I
put this job in the background from within bash. IDL usually
runs from an interactive shell, and I would like to be able to
bring IDL back to the foreground after some time (the
computation is done). The problem is, if I exit the shell from
which IDL was initiated, then, although IDL will still run, I
cannot bring it back into the
foreground since the shell from which it was started has died
and any other shell will have no knowledge of this process. I
could
just leave the shell from which IDL was started open, but that
would require me to leave my system unattended (never log
off).

Is there a way to get a BASH shell to "adopt" a process that
was started from another BASH shell? This would allow me to
use the normal job controll built in to BASH to bring my job
back into the
foreground. Any tips would be appreciated!

Steve

2. Defrag of harddisk with ADSM/HSM

3. BASH BASH BASH BASH BASH BASH BASH BASH BASH BASH

4. What do you think of Storm 2000?

5. New version of GNU Emacs with fixed job control

6. How to disable net connection temporily?

7. Job control question (Bash)

8. One Way Cable Modem Setup

9. BASH - job control - backgrnd (^Z) does not work

10. get control on bg job of other bash shell

11. Bash job control

12. bash job control: re-own?

13. Bash Job Control