Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site pegasus.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxn!ihnp4!pegasus!hansen
From: hansen@pegasus.UUCP (Tony L. Hansen)
Newsgroups: net.news,net.news.group
Subject: Removing net.flame locally, the easy way
Message-ID: <2420@pegasus.UUCP>
Date: Mon, 8-Jul-85 16:14:55 EDT
Article-I.D.: pegasus.2420
Posted: Mon Jul  8 16:14:55 1985
Date-Received: Tue, 9-Jul-85 06:48:13 EDT
References: <3892@alice.UUCP> <2916@nsc.UUCP>
Reply-To: hansen@pegasus.UUCP (60545451-Tony L. Hansen;LZ 3B-315;6243)
Distribution: net
Organization: AT&T Information Systems, Lincroft NJ
Lines: 21
Keywords: chmod, net.flame
Xref: watmath net.news:3599 net.news.group:3238
Summary: chmod -w ~news/net/flame

These suggestions are suitable for a branch node that passes news along, but
doesn't want net.flame locally.

At one point in time, the comp center that I was using disallowed net.jokes
from being read on their machines. Since they didn't want to cut off the
sites that they fed from getting net.jokes, they simply made the net.jokes
directory unwritable. For net.flame:

    chmod -w ~news/net/flame

All news got passed on to the other sites like normal, but none got stored
on the machine as the opens to write the news simply failed.

This had the advantage of not storing the files locally. The disadvantages
were: 1) you still have the transmission cost, and 2) you can't use the 'F'
flag in your sys file to transmit the articles.

Another method is to simply expire net.flame after 1 day.

					Tony Hansen
					[ihnp4!]pegasus!hansen