Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!mcvax!ukc!stc!concurrent!stl!jvc
From: jvc@stl.UUCP (Vic Churchill)
Newsgroups: net.sources.d,net.wanted
Subject: Re: Detecting running processes... this one's portable
Message-ID: 
Date: Fri, 8-Aug-86 08:17:59 EDT
Article-I.D.: stl.305
Posted: Fri Aug  8 08:17:59 1986
Date-Received: Tue, 12-Aug-86 17:13:03 EDT
References:   
Reply-To: jvc@stl.UUCP (Vic Churchill)
Organization: STL,Harlow,UK.
Lines: 25
Keywords: sleep,kill
Xref: mnetor net.sources.d:407 net.wanted:3652

<for new readers, the story so far is about ways and means to
arrange for a process to be started AFTER a specified
process terminates.>
Nice discussion. Now try the following:
I would like a way to run a process for a specified time
duration and then "gracefully" zap it. (Basically, it's to
stop me becoming a net junkie. Limit the habit to a
half-hour at a time!) So something like "fuze foo 30"
has the effect :
       __ run foo __________________ eek!
______/                      ^      ^   ___ back to shell
      \__ sit'n'wait 29 mins | 1min |__/
			     /      /
		a gentle warning   /
			       a killer

There seems to be no way (that I can see) that the csh job
control facilities or the available process id info can allow the
'fuze' process to know the identity of its sibling. Is it
really necessary to start doing ps|fgrep's and so on? 
All suggestions welcomed. (Well, most sensible suggestions
anyway :-) ). 

  this signature not a sentence.
 Vic Churchill (jvc@stl  ...!mcvax!ukc!stl!jvc  +44-279-29531 x 2546)