Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!princeton!phoenix!pucc!IRWIN
From: IRWIN@pucc.UUCP
Newsgroups: news.admin
Subject: Re: Wanted: net.sources feed (comments -- long)
Message-ID: <2966@pucc.Princeton.EDU>
Date: Sun, 14-Jun-87 20:14:18 EDT
Article-I.D.: pucc.2966
Posted: Sun Jun 14 20:14:18 1987
Date-Received: Tue, 16-Jun-87 01:12:18 EDT
References: <1440@ncc.UUCP> <934@maynard.BSW.COM> <15888@gatech.gatech.edu> <10332@decwrl.DEC.COM>
Reply-To: IRWIN@pucc.Princeton.EDU
Organization: Princeton University - Princeton, New Jersey
Lines: 17
Disclaimer: Author bears full responsibility for contents of this article

In article <1440@ncc.UUCP>, lyndon@ncc.UUCP (Lyndon Nerenberg) writes:
 
>Is there any reason that the code for the checkgroups message
>can't be changed to follow the distribution mechanism? It should
>be possible to send out a checkgroups for each of the distribution
>catagories containing only the relevent group names. We would have
>to take out the code that complains about groups to be deleted.
>The check for obsolete groups could be handled by a seperate
>control message, if indeed it's required at all given the potential
>number of alternative groups that may be appearing.
 
In version P 1.2 (a VM/CMS version), checkgroups examines the sys
file to discover what patterns the host claims to receive, and
ignores lines in the checkgroups article which don't match any pattern.
 
Irwin Tillman           BITNET: IRWIN@PUCC
Princeton University    UUCP: {allegra,ihnp4,cbosgd}!psuvax1!PUCC.BITNET!IRWIN