Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!lll-lcc!qantel!hplabs!tektronix!uw-beaver!ubc-vision!alberta!ncc!lyndon
From: lyndon@ncc.UUCP (Lyndon Nerenberg)
Newsgroups: net.bugs.uucp
Subject: Re: uucico/uuxqt bugs...howcome?
Message-ID: <728@ncc.UUCP>
Date: Thu, 18-Sep-86 19:21:46 EDT
Article-I.D.: ncc.728
Posted: Thu Sep 18 19:21:46 1986
Date-Received: Wed, 24-Sep-86 00:08:06 EDT
References: <900@gilbbs.UUCP> <612@pyramid.UUCP>
Organization: Nexus Computing Corp.,  Edmonton, AB
Lines: 26
Summary: Don't *touch* the LCK files...

In article <612@pyramid.UUCP>, csg@pyramid.UUCP (Carl S. Gutekunst) writes:
> In article <900@gilbbs.UUCP> mc68020@gilbbs.UUCP (Thomas J Keller) writes:
> >  When it [uucico] finishes, it attempts to spawn
> >a uuxqt process, unless there is a LCK.XQT file in my uucp spool directory.
> >... if the LCK.XQT file is more than an hour old, 
> >uucico blithely spawns another freaking uuxqt process!!!
> [...]
> For your site, using cron to touch the LCK.XQT file is one solution; you can
> [etc...]		       ^^^^^

Be careful how you do this! We run a CT MiniFrame, and this bug may be
specific to CTIX, but...

I set up cron to "touch /usr/spool/uucp/LCK*" once per hour for the same 
reasons. If there are no LCK files in the directory, touch creates a file
named "LCK*". The next time you run "uucico -r1" from cron, it sees queued
up XQT's and trys to run them. *Sometimes* (but *not* always), the presence
of "LCK*" makes uuxqt get very upset, at which point it dumps all the queued
jobs!! The fix is to change your crontab entry:
	find /usr/spool/uucp/LCK* -exec touch {} \;

Has anyone else run into this?
-- 

Lyndon Nerenberg (VE6BBM) 		  {ihnp4,ubc-vision}!alberta!ncc!lyndon
Systems Group - A Div. of Nexus Computing Corp.  		Envoy_100: Unix