Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site udenva.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!bellcore!decvax!decwrl!amdcad!amd!noao!hao!nbires!isis!udenva!wedgingt
From: wedgingt@udenva.UUCP (Will Edgington/Ejeo)
Newsgroups: net.news.adm,net.news.b
Subject: Re: curious 2.10.3 efficiency situation
Message-ID: <1226@udenva.UUCP>
Date: Thu, 13-Mar-86 15:13:28 EST
Article-I.D.: udenva.1226
Posted: Thu Mar 13 15:13:28 1986
Date-Received: Sat, 15-Mar-86 21:05:15 EST
References: <10428@amdcad.UUCP> <5128@glacier.ARPA> <63@gilbbs.UUCP> <175@desint.UUCP>
Reply-To: wedgingt@udenva.UUCP (Will Edgington/Ejeo)
Organization: U of Denver
Lines: 23
Keywords: uucp spool LCK files
Xref: watmath net.news.adm:560 net.news.b:1322
Summary: really more about uucp LCK files

In article <175@desint.UUCP> geoff@desint.UUCP (Geoff Kuenning) writes:
>One minor problem:  make sure your /etc/rc file has the line
>
>    rm -f /usr/spool/uucp/LCK.XQT
>
>or, once you have had a uuxqt crash, you will never run uuxqt's again!

While you're at it, you might as well:

rm -f /usr/spool/uucp/LCK.*

There sure wasn't *ANY* uucp activity while the system was down, so you
might as well remove them all while you're there.  Terminal lock files
(LCK..tty??) are especially critical; removing them at reboot often means
uucp knows the ports are available for use that much sooner.  Sites with
heavy uucp use will find things just a little bit easier, especially if
they also go down 6 nights a week for backup (as mine do).
-- 
Will Edgington		 | Phone: (303) 871-2081 (work), 722-5738 (home)
Computing Services Staff | USnail: BA 469, 2020 S. Race, Denver CO 80210
University of Denver	 | Home: 2035 S. Josephine #102, Denver CO 80210
Electronic Address (UUCP only): {hplabs, seismo}!hao!udenva!wedgingt
or {boulder, cires, ucbvax!nbires, cisden}!udenva!wedgingt