Path: utzoo!attcan!uunet!clyde.concordia.ca!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!wuarchive!kuhub.cc.ukans.edu!anu-news!list
From: kenw@NOAH.ARC.AB.CA (Ken Wallewein CDP)
Newsgroups: news.software.anu-news
Subject: RE: Problems (sorry: challenges :-) merging NEWS data bases
Message-ID: <6452*kenw@noah.arc.ab.ca>
Date: 27 Feb 90 23:22:00 GMT
Sender: ANU-NEWS Discussion <ANU-NEWS@NDSUVM1.BITNET>
Reply-To: Ken Wallewein CDP <kenw@NOAH.ARC.AB.CA>
Lines: 45
In-Reply-To:  <9002272200.AB02186@relay.CDNnet.CA>

>...
> This was a somewhat belated addition to the code to support the relevant
> USENET RFC. On very careful inspection of the standard it states that
> newsgroups which no not contain a '.' character are considered local to the
> host (i.e. general, junk, local, control, etc) and are not to be passed to
> neighbouring sites.
>
> >  It appears that, contrary to my interpretation of the documentation
> >(which is clear on the point), NEWS.SYS is _not_ consulted for the ADD FILE
> >command.  When _is_ it consulted regarding additions to the local nodes?
> >Is it ever likely to change?
     
  We seem to have a misunderstanding here.  I do _not_ have my NEWS.SYS
configured to accept all newsgroups; nearly none, in fact.  It contains
only one active line:
     
	calarc:ean_feed,local,slug::
     
  Until recently, we had no NEWS.SYS at all.  I use ADD FILE/CREGRP with
JUNKNODOT turned off, and use no-dot newsgroups such as "info-vax".  I have
no trouble adding items and groups.  To me, that means that NEWS.SYS is not
doing anything.  Is this a bug, a feature, or what?  Up until now, it's
been a convenience, actually.
     
> >   If it were possible to override the NEWS system logicals through the use
> >of user logicals, I would be able to redirect NEWS to use two different
> >data bases.  How hard would that be?  Are there many routines that would be
> >affected?  Have you ever considered building in support for separate data
> >bases?
>
> This then brings up the problems of user logicals driving a program
> installed with SYSPRV. It has the potential to blast your system security
> to shreds. Where NEWS uses SYSPRV to access the file system, the relevant
> logical names used are all translated as SYSTEM EXEC logical names as a
> precaution against such security issues.
     
  Good point.
     
  Actually, it turns out that /JOB/EXEC logicals work, too.  And although I
haven't tried it yet, I'm seriously considering /USER/EXEC logicals created
by a priviledged image.  It appears that this would allow me to actually
use two completely separate data bases; somewhat like NEWSMGR-defined
CLASSes, eh wot?
     
/kenw