Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84 / ST 1.0; site saber.UUCP
Path: utzoo!watmath!clyde!cbosgd!ulysses!bellcore!decvax!decwrl!sun!idi!saber!msc
From: msc@saber.UUCP (Mark Callow)
Newsgroups: net.news.adm,net.news.b
Subject: Re: curious 2.10.3 efficiency situation
Message-ID: <1951@saber.UUCP>
Date: Wed, 12-Mar-86 16:50:03 EST
Article-I.D.: saber.1951
Posted: Wed Mar 12 16:50:03 1986
Date-Received: Fri, 14-Mar-86 07:49:14 EST
References: <5044@glacier.ARPA> <5104@glacier.ARPA> <10428@amdcad.UUCP> <5128@glacier.ARPA> <63@gilbbs.UUCP>
Organization: Saber Technology, San Jose, CA
Lines: 15
Xref: watmath net.news.adm:558 net.news.b:1317

>   I understand there is some way to ensure that only one istantiation of
> UUXQT is executed at any one time.  Can someone elaborate on this for me?

There had better be only one instance of uuxqt or you'll have real
problems.  uuzqt uses the lock file /usr/spool/uucp/LCK.XQT to ensure
only one uuxqt is running.

UNNNNFortunately uuxqt ignores the lock file if it is more than a
certain age.  The default age (in 4.2 BSD's uucp at least) is 60
minutes.  This is far too short if you are receiving batched news,
especially if you have unbatchnews niced.
-- 
From the TARDIS of Mark Callow
msc@saber.uucp,  sun!saber!msc@decwrl.dec.com ...{ihnp4,sun}!saber!msc
"Boards are long and hard and made of wood"