BASH 1.04 and backgrounded execs

Thread View: gnu.bash.bug

2 messages

[T] Back to Threads [V] Tree View [G] Group Articles

2 total messages Started by David C Lawrence Tue, 23 Jan 1990 03:01

#859

Author: David C Lawrence
Date: Tue, 23 Jan 1990 03:01

26 lines
1352 bytes

Ok, so it's pretty dumb to background an exec.  I did it
absent-mindedly.  It consistently gives BASH hissy fits though:

/us9/staff/tale
sirius:tale (1) export DISPLAY=beethoven:0
/us9/staff/tale
sirius:tale (2) exec xterm &
describe_pid: No such pid (23608)!

Tell tale@cs.rpi.edu to fix this someday.
Mailing a bug report...done.
Stopping myself...Connection closed.

The xterm, in this case, started up fine.

This particular BASH is on a Sun4, OS 4.0.3c.  Yes, I saw it says it
is mailing the bug report, but I've seen it happen a couple of times,
have probably had an auto-report mailed to Brian about it everytime,
but haven't seen anything about it, like Brian saying, "Stop doing
that so it will stop sending me reports because you're an idiot!".  I
just thought the rest of you BASH maintainers might like to know about
it.

Dave
-- 
   (setq mail '("tale@cs.rpi.edu" "tale@ai.mit.edu" "tale@rpitsmts.bitnet"))

Re: BASH 1.04 and backgrounded execs

#860

Author: Chet Ramey
Date: Tue, 23 Jan 1990 16:41

14 lines
984 bytes

In article <9001230301.AA07613@turing.cs.rpi.edu> tale@TURING.CS.RPI.EDU (David C Lawrence) writes:

>sirius:tale (2) exec xterm &
>describe_pid: No such pid (23608)!

This happens to any builtin started in the background, not just exec.  It's
fixed for the next release.

Chet Ramey
-- 
Chet Ramey				"Can't you pay a grad student to 
Network Services Group			 read the manual for you?"
Case Western Reserve University			-- Bill Wisner,
chet@ins.CWRU.Edu				   	to Peter Honeyman

Thread Navigation

This is a paginated view of messages in the thread with full content displayed inline.

Messages are displayed in chronological order, with the original post highlighted in green.

Use pagination controls to navigate through all messages in large threads.

Back to All Threads