Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!lccinc!andrew
From: andrew@lccinc.UUCP (Andrew Scholnick)
Newsgroups: comp.windows.x
Subject: Closing (f.kill) Xterm window doesn't kill process. Is this normal?
Keywords: xterm mwm kill
Message-ID: <107@lccinc.UUCP>
Date: 11 Sep 90 18:23:23 GMT
Organization: Lunayach Communications Consultants, Inc.
Lines: 48

When I have a process running in an Xterm window and I CLOSE (f.kill) 
the window, the process which was running in the window won't die...

I eventually wind up with an overloaded process table unless I
locate processes manually with ps and then kill them...

The processes are started when the window manager (mwm) comes up
with the following line from .startxrc:
	xterm +s -rw -sb -sk -sl 80 2> /dev/null -e myprog &
or from a menu selection defined in .mwmrc as follows:
	"My Prog"   f.exec "xterm  -rw +s -sb -sk -sl 80 -e myprog &"

The program 'myprog' is a shell script which looks like this:
	: Script to do M1 to M25 reports for Ericcson Switch
	# Written by ARS. 7/6/90
	trap "byebye();exit 10" 1 2 3 4 9 15 16 17

	byeby()
	{
	echo "$0: Program exiting abnormally."
	}

	cd mydir
	echo -n "Enter first value: "
	read ans1
	echo -n "Enter second value: "
	read ans2
	my_executable $ans1 $ans2 
	status=$?
	echo " "
	echo -n ":: Press <return> to continue... "
	read ans

If the f.kill is used BEFORE the user "Presses <return> to
continue... " the shell process does not die, only the window goes
away...

Is this normal behavior for xterm/mwm or is it yet another XENIX-386
system/X-windows bug? (;-)

Thanks.

ARS.
-- 
- Andrew R. Scholnick @ LCC, Inc.,  Washington, DC
- andrew@lccinc.LCC.com -or- uunet!lccinc!andrew
-- Objections to anything I write blame on me, NOT my employer.
-- "I'm not dead yet!"  - M. Python