df@nud.UUCP (Dale Farnsworth, NO7K) (09/29/87)
In article <271@flmis06.ATT.COM> mikel@flmis06.ATT.COM (Mikel Manitius) writes:
->We do this over RFS. The idea is simple, and you don't really need hacks
->into any of the software. The only problem arrises when you export
->/usr/lib/news and the remote system doesn't see itself in the sys file
->when you post something.
->
->This is easily overcome by having a "fake" NEWSLIB directory that gets
->exported, where everything is liked back to the real one, except for
->the sys file, which has a whole bunch of dummy entries for the remote
->systems to forward their stuff to the gateway, and not keep it for
->themselvs.
We use the pseudo machine name "ME" in the sys file and advertise NEWSLIB
along with the database. In fact, we put all the news related files into
a single directory hierarchy (/news) and then advertize the single resource.
As long as only one machine runs sendbatch, users on all machines can read
and post news without problems. We now have a dozen machines here sharing
news through RFS.
-Dalerees@apollo.uucp (Jim Rees) (10/01/87)
We use the pseudo machine name "ME" in the sys file and advertise NEWSLIB
along with the database. In fact, we put all the news related files into
a single directory hierarchy (/news) and then advertize the single resource.
As long as only one machine runs sendbatch, users on all machines can read
and post news without problems. We now have a dozen machines here sharing
news through RFS.
We also use a single /news hierarchy for all our machines. There are
some locking and contention problems that start to show up when you
reach several thousand nodes sharing the same /news (we have about 2200),
but these are easily fixed (I'm sending patches to Rick Adams).
To further simplify matters, our entire network appears as a single
uucp host ("apollo") to the outside world. So the sys file (and most
everything else) is set up just the way it would be on a single
machine.