Xref: utzoo unix-pc.general:2563 comp.sys.att:5988
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!rutgers!rochester!pt.cs.cmu.edu!cadre!pitt!cisunx!jcbst3
From: jcbst3@cisunx.UUCP (James C. Benz)
Newsgroups: unix-pc.general,comp.sys.att
Subject: strange behavior of nohup
Keywords: UNIX PC, nohup
Message-ID: <17168@cisunx.UUCP>
Date: 30 Mar 89 14:29:06 GMT
Reply-To: jcbst3@unix.cis.pittsburgh.edu (James C. Benz)
Distribution: usa
Organization: Univ. of Pittsburgh, Comp & Info Sys
Lines: 25

I have been trying to write a shell script that invokes a home-brew demon
process for an application I've been working on.  On other Unix systems
I've worked on, (3B2) the nohup command allows you to log out of the 
current shell level without killing the nohuped process.  My shell script
on the UNIXPC has a line that goes something like this:

nohup demon options 1>/dev/null 2>/dev/null&

Having executed this line and exiting back to the $ prompt, I then press
^D to exit the shell.  Normally, this would get me back to the ua window
environment, but after running the nohup, ^D hangs the Full-screen Unix
window (Sys V version 3.51) and the only way I can get rid of it is to 
open another Unix window and explicitly kill the demon process that was
run with the nohup.  Once this is done, the hung window disappears and
everything is back to normal.  So what am I missing?  Is there some other
way to accomplish this that won't leave dead windows lying around?  ps -eaf
shows that the parent process for the nohuped process is 1, not the shell
that invoked it, so it seems right, but the window hangs every time.  Is
there a bug here, or am I missing something in the documentation?  Any
suggestions would be appreciated.  Thanks

-- 
Jim Benz 		     jcbst3@unix.cis.pittsburgh.edu     If a modem 
University of Pittsburgh					 answers,
UCIR			     (412) 648-5930			 hang up!