🚀 go-pugleaf

   Yes, well.  I have now had innumerable responses to my queries regarding
XQT lock files.  Many people have suggested touching the file from cron.  AS
it happens, that doesn't work.

   According to a contact at a site with source license, UUCP checks the
CREATION time, as opposed to the modification time of the lock file.  I have
therefore developed a strange but functional script which handles this for
me.  In the very near future, I intend to follow the many suggestions that I
divorce news unbatching from UUXQT.   Here is the script I developed that 
finally seems to have accomplished what I needed:

----------------------------------------------------------------------------
if test -f /usr/spool/uucp/LCK.XQT
then
    if (ps -elf | grep "uucp[a-zA-Z0-9 :]*UUXQT")
    then
        nice --10 copy -o /usr/spool/uucp/LCK.XQT /usr/spool/uucp/newlock
	nice --10 rm /usr/spool/uucp/LCK.XQT
	nice --10 mv /usr/spool/uucp/newlock /usr/spool/uucp/LCK.XQT
	echo "Lock file updated \c" >> /hd1/lib/news/xqt.log
	date >> /hd1/lib/news/xqt.log
    else
	sleep 90
	if (ps -elf | grep "uucp[a-zA-Z0-9 :]*UUXQT")
	then
	    exit 0
	else
	    rm /usr/spool/uucp/LCK.XQT
	    echo "Lock file removed \c" >> /hd1/lib/news/xqt.log
	    date >> /hd1/lib/news/xqt.log
	fi
    fi
fi
--------------------------------------------------------------------------

   Any constructive comments are more than welcome.  I am not a highly 
   expereinced shell programmer, so I'm sure there are better ways to 
   accomplish this task.  Flames regarding this script politely referred
   to /dev/null.

-- 

Disclaimer:  Disclaimer?  DISCLAIMER!? I don't need no stinking DISCLAIMER!!!

tom keller					"She's alive, ALIVE!"
{ihnp4, dual}!ptsfa!gilbbs!mc68020

(* we may not be big, but we're small! *)