Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!hsdndev!cmcl2!panix!alexis
From: alexis@panix.uucp (Alexis Rosen)
Newsgroups: news.software.b
Subject: Re: Backup newsfeed plans
Message-ID: <1991Jun29.113222.11780@panix.uucp>
Date: 29 Jun 91 11:32:22 GMT
References: <1991Jun28.112207.939@panix.uucp> <1991Jun28.171354.7219@zoo.toronto.edu>
Organization: PANIX - Public Access Unix Systems of NY
Lines: 28

henry@zoo.toronto.edu (Henry Spencer) writes:
>alexis@panix.uucp (Alexis Rosen) writes:
>>What we'd like to do is set up a backup feed. Can anyone think of any serious
>>problems with the following plan?
>
>You can use existing facilities to get more or less the same effect; many
>people use ihave/sendme links for backup feeds.  (This would work better
>if there were a delayed-ihave/sendme facility; it's easy to tinker one
>up, and an "official" implementation is in the works.)

Hm. I know about ihave/sendme and decided that setting that up, when it will
only be user for two or three two-to-six day periods in the year, is a big
waste of resources. It's also less likely to be acceptable to an admin who's
worried about conserving resources.

Is there a flaw in the first plan? And, could you please elaborate a little
on the "delayed" ihave/sendme? I'm not too clear on what you mean.

Another vague (and more difficult but effective) option comes to mind: the
backup feed could create batches based on timestamps in the active file. You'd
still miss some news, but not all that much, if you allowed for a slop factor
of, oh, maybe one day.

---
Alexis Rosen
Owner/Sysadmin, PANIX Public Access Unix, NYC
alexis@panix.com
{cmcl2,apple}!panix!alexis