Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!lsuc!dave
From: dave@lsuc.uucp (David Sherman)
Newsgroups: ont.uucp
Subject: file D.siteA1234 can't access
Message-ID: <1987Nov30.235047.7349@lsuc.uucp>
Date: Mon, 30-Nov-87 23:50:45 EST
Article-I.D.: lsuc.1987Nov30.235047.7349
Posted: Mon Nov 30 23:50:45 1987
Date-Received: Wed, 2-Dec-87 02:38:03 EST
Distribution: ont
Organization: Law Society of Upper Canada, Toronto
Lines: 32

> From Umaccs Mon Nov 30 23:13:51 1987
> To: dave
> 
> file /usr/spool/uucp/D.maccsB4397 on lsuc
> can't access

I've always had these messagess on occasion.  Recently I've started
getting lots of them -- sometimes two or three an hour, from lots
of different sites (mnetor, sickkids, maccs, utzoo, tmsoft -- you name it).

My understanding has always been that these messages can appear
because the D file of a [CD] pair gets sent, then the line fails,
and then the C file later refers to the D which is no longer here
to be sent, because it's already gone over.  As such, I've always
assumed I needn't worry about such messages.  Now I'm seeing so
many of them I'm starting to worry a bit.

grep FAIL LOGFILE | egrep -v "call to|LOGIN" does produce quite
a string of things like FAILED (CAN'T READ DATA), BAD READ
(expected 'S' got FAIL), and FAILED (conversation complete),
so maybe I'm just seeing the results of a flaky phone line or
modem.  Do other sites feel that the quality of the connection to
lsuc is bad?  Can you monitor it at all or trace the cause of all
these failures?  Do these error messages represent a possibly serious
problem?

We have no problem with file space in /usr/spool, incidentally.

David Sherman
-- 
{ uunet!mnetor  pyramid!utai  decvax!utcsri  ihnp4!utzoo } !lsuc!dave
Pronounce it ell-ess-you-see, please...