Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site turtlevax.UUCP
Path: utzoo!watmath!clyde!bonnie!akgua!whuxlm!harpo!decvax!decwrl!turtlevax!ken
From: ken@turtlevax.UUCP (Ken Turkowski)
Newsgroups: net.news,net.wanted.sources,net.unix-wizards
Subject: Re: extension to L (local) flag in sys file
Message-ID: <710@turtlevax.UUCP>
Date: Wed, 3-Apr-85 04:04:12 EST
Article-I.D.: turtleva.710
Posted: Wed Apr  3 04:04:12 1985
Date-Received: Thu, 4-Apr-85 06:54:15 EST
Distribution: net
Organization: CADLINC, Inc. @ Menlo Park, CA
Lines: 18
Xref: watmath net.news:3329 net.wanted.sources:689 net.unix-wizards:12698

Some time ago, someone posted an enhancement to news to allow an
extension of the "L" flag in the sys file to say that articles
from "close" neighbors, as well as articles generated locally,
should be passed on to the other neighbors.  For example,
	nsc:net,fa,usa,na,ca,ba,mod,to.nsc:BFL2:/usr/spool/batch/nsc
should send on articles that have been generated locally, as well
as those generated within 2 hops.  I put in this change, but it seems
as though the number doesn't make a difference.  ALL of our neighbors
get our articles and those of our one-hop neighbors, REGARDLESS of
whether their sys line has L0, L1, or L2.

Has anyone else experienced similar problems?  Any fixes or alternate
ways to get the same effect?
-- 

Ken Turkowski @ CADLINC, Menlo Park, CA
UUCP: {amd,decwrl,hplabs,nsc,seismo,spar}!turtlevax!ken
ARPA: turtlevax!ken@DECWRL.ARPA