Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!uupsi!njin!princeton!phoenix!subbarao
From: subbarao@phoenix.Princeton.EDU (Kartik Subbarao)
Newsgroups: comp.unix.questions
Subject: Re: Was: ctl-Z on process, more explicity question...
Message-ID: <14944@phoenix.Princeton.EDU>
Date: 29 Mar 90 13:51:02 GMT
References: <6000@rouge.usl.edu>
Reply-To: subbarao@phoenix.Princeton.EDU (Kartik Subbarao)
Distribution: usa
Lines: 32

In article <6000@rouge.usl.edu> pcb@gator.cacs.usl.edu (Peter C. Bahrs) writes:
>
>csh and BSD Unix
>Start a job:   prog &
>then logout
>login back in later and do a ps
>job is running but you are not at controlling terminal
>It seems to be a reasonable (which might be the problem) request 
>to 'command' the job to pause and then continue (just like I could do 
>if I did not log out).
>
>using the kill -STOP pid; kill -CONT pid does not work.

kill -STOP and kill -CONT may or may not be specific to a system. The
best way to find out what exactly are the codes is by doing a man page
on sigvec(2). It lists all of the interrup codes, and for example, on 
phoenix (VAX-8700 running Ultrix 2.0)

kill -17 is SIGSTOP
kill -18 is SIGTSTP (There's a difference between them)

and
kill -19 is SIGCONT (Continues after a stop)

That, and more codes are listed as well.

			-Kartik

-- 
subbarao@{phoenix,bogey or gauguin}.Princeton.EDU -|Internet
kartik@silvertone.Princeton.EDU (NeXT mail)       -|	
subbarao@pucc.Princeton.EDU		          - Bitnet