Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ihnp4!ptsfa!ames!cit-vax!tybalt.caltech.edu!sns
From: sns@tybalt.caltech.edu.UUCP
Newsgroups: ca.unix,comp.unix.wizards,comp.unix.xenix,comp.unix.questions
Subject: problems with untamo
Message-ID: <1872@cit-vax.Caltech.Edu>
Date: Thu, 26-Feb-87 22:12:44 EST
Article-I.D.: cit-vax.1872
Posted: Thu Feb 26 22:12:44 1987
Date-Received: Sun, 1-Mar-87 08:36:02 EST
Sender: news@cit-vax.Caltech.Edu
Reply-To: genghis!sns@csvax.caltech.edu (Samuel N. Southard)
Organization: Calfornia Institute of Technology
Lines: 13
Xref: utgpu junk:4827 comp.unix.wizards:1156 comp.unix.xenix:126 comp.unix.questions:1210

I have been trying to get the untamo idle daemon running on my IBM AT/Xenix
2.00 (somewhat Sys V).  I have everything working, except for one slight
problem.  The untamo program uses vhangup, which my xenix does not have.  I
have (with the help of others) found a possible (I think) way around this:
replace the vhangup call code that forks a process, assocites the forked
process with the group of processes that should be killied, and then have the
forked process do a kill(0,SIGHUP), nicely taking care of all the unwanted
processes.  I have been able to do everything except for getting the forked
process associated with the process group.  Avalible information is the
terminal of the processes that need to be killed and the name of the user who
owns the processes to be killed.  Any help would be greatly appreciated.

My cat can quack, can yours?		genghis!sns@csvax.Caltech.Edu