Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!star.cs.vu.nl!maart
From: maart@cs.vu.nl (Maarten Litmaath)
Newsgroups: comp.unix.questions
Subject: Re: Killing the correct process
Message-ID: <5636@star.cs.vu.nl>
Date: 21 Feb 90 19:44:34 GMT
References: <22332@adm.BRL.MIL> <5312@star.cs.vu.nl> <1212@root44.co.uk> <5382@buengc.BU.EDU> <5615@star.cs.vu.nl> <5405@buengc.BU.EDU>
Sender: news@cs.vu.nl
Reply-To: maart@cs.vu.nl (Maarten Litmaath)
Followup-To: comp.unix.questions
Organization: VU Informatika, Amsterdam, the Netherlands
Lines: 19

In article <5405@buengc.BU.EDU>,
	bph@buengc.BU.EDU (Blair P. Houghton) writes:
)...
)I'm talking about timing-out someone's login, possibly 12-20 hours
)after the killer-process has been started.  Plenty of time.

I think you need a new system call like `killtree()' or `killsession()' to
solve your problem completely:

-	you cannot kill all his processes, as you must leave background
	processes and processes on other terminals alone
-	process groups aren't the answer either

Therefore there's a time window between determining which processes have to
be killed, and actually killing them.  During this interval the user may have
created new processes.
--
  "Ever since the discovery of domain addresses in the French cave paintings
  [...]"  (Richard Sexton)      |  maart@cs.vu.nl,  uunet!mcsun!botter!maart