Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!eecae!netnews.upenn.edu!rutgers!att!alberta!ncc!adec23!mark
From: mark@adec23.UUCP (Mark Salyzyn)
Newsgroups: comp.mail.uucp
Subject: Re: A question about uucp and another about mail
Summary: L.sys time restrictions
Message-ID: <1667@adec23.UUCP>
Date: 9 Mar 89 16:55:09 GMT
References: <414@twwells.uucp> <138@psgdc> <750@twwells.uucp> <9059@b-tech.ann-arbor.mi.us>
Organization: ADEC Systems Inc., Edmonton, Alberta
Lines: 20

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.
Nope, why not set time limits in the L.sys file. The second field is used to
restrict the time of the calls to a particular system. I know that this may
not be what you want, however you could write a short script to edit the L.sys
file to change the time from `None' to `Any' when you want to perform the call.

If the problem is reducing the number of calls to a specific system, then
restrict the time before a re-call (eg: Any,60). I think this may work, but I
believe that some implementations treat this from last call, and some from
last unsuccessful call.

Ciao,
-- Mark Salyzyn