Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!novavax!twwells!bill
From: bill@twwells.uucp (T. William Wells)
Newsgroups: comp.mail.uucp
Subject: Re: A question about uucp and another about mail
Message-ID: <753@twwells.uucp>
Date: 6 Mar 89 07:04:01 GMT
References: <414@twwells.uucp> <138@psgdc> <750@twwells.uucp> <9059@b-tech.ann-arbor.mi.us>
Reply-To: bill@twwells.UUCP (T. William Wells)
Organization: None, Ft. Lauderdale
Lines: 27
Summary:
Expires:
Sender:
Followup-To:
Distribution:
Keywords:

In article <9059@b-tech.ann-arbor.mi.us> zeeff@b-tech.ann-arbor.mi.us (Jon Zeeff) writes:
: >: > What is the correct way to convince uucp to only perform transfers at
: >: > a single time? What I want is for it to not process all outgoing
: >: > requests until one particular time or until I manually initiate a
: >: > connection....
:
: I don't know about a correct way, but an easy way is to mv uucico to
: uucico.x and then only run it when you want transfers to occur.  You may
: need to create a dummy uucico to prevent some errors.

I've more or less come to the conclusion that something like this is
the only way.  I can't just rename uucico because I have several
systems I talk to and only one on which I want to control the timing
of requests.

However, I already run uucico from within a program; that program is
needed because of a bug in the Telebit firmware and a wierdness in my
DTR line. So all I have to do is to make sure that that program
doesn't call uucico for uunet except when I ask for it.

Sigh.

---
Bill
{ uunet | novavax } !twwells!bill
(BTW, I'm going to be looking for a new job sometime in the next
few months.  If you know of a good one, do send me e-mail.)