hansen@pegasus.UUCP (Tony L. Hansen) (07/08/85)
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!hansenwoods@hao.UUCP (Greg Woods) (07/10/85)
> Another method is to simply expire net.flame after 1 day. > > Tony Hansen > [ihnp4!]pegasus!hansen The trouble with that idea is it's too good. It's too easy, and it makes sense. It conserves disk space, while still giving the "hard-cores" on your own site the chance to catch the flames if they really want to. And no one can flame about it! :-) As Steve Martin used to say, NAAAAAH! --Greg -- {ucbvax!hplabs | allegra!nbires | decvax!noao | harpo!seismo | ihnp4!noao} !hao!woods CSNET: woods@NCAR ARPA: woods%ncar@CSNET-RELAY