Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!linus!philabs!micomvax!musocs!zap!fortin
From: fortin@zap.UUCP (Denis Fortin)
Newsgroups: news.admin
Subject: --- Multiple UUXQTs causing thrashing ---
Message-ID: <173@zap.UUCP>
Date: Sun, 4-Oct-87 22:21:46 EDT
Article-I.D.: zap.173
Posted: Sun Oct  4 22:21:46 1987
Date-Received: Sun, 18-Oct-87 08:41:58 EDT
Lines: 29
Keywords: Unix, compress, LCK.XQT, thrashing

Greetings...

	I have recently installed News 2.11 on my system (an 
iAPX286 machine running Microport System V/AT 2.2L), and have
arranged a full compressed newsfeed with one of my neighbors.  Everything 
works fine except that I have noticed a few times that the unpacking of
the news seemed to take (much) longer than usual, and on top of that,
the response time of the system was really rotten.  A quick "ps -ef"
informed me that no less than three UUXQTs were running on the system,
each one with associated news-unpack, compress, etc.

	Now, my system has only 2 MB of RAM, and compress is fairly
large...  Running three compress at the same time means that the
swap space starts getting overused, and that the system starts thrashing!

	Each time this has happened, I noticed that there *was* a LCK.XQT
file in /usr/spool/uucp --> shouldn't this prevent the appearance of new
UUXQTs?  (the new ones seem to get spawned off by a "uucico -r1" command
from my uudemon.hr script)

	Anyway, what I'd like to know is: (1) is this normal, and 
(2) what can be done to limit the number of concurrent compresses to
a single one???

	Thanks!
-- 
Denis Fortin,				| fortin@zap.UUCP
CAE Electronics Ltd			| rutgers!mit-eddie!musocs!zap!fortin
The opinions expressed above are my own	| fortin%zap.uucp@uunet.uu.net