bernhold@qtp.ufl.edu (David E. Bernholdt) (11/15/89)
We are an nntp leaf node and we probably generate fewer than 10 articles per day locally. It seems like running nntplink would be kind of overfill. It seems like we could achieve the *idea* of nntplink by running nntpxmit "on demand" i.e. every time an article is posted. Has anyone given this any thought? Surely there must be other nntp leaf nodes around for which this would be more appropriate? Just curious. -- David Bernholdt bernhold@qtp.ufl.edu Quantum Theory Project bernhold@ufpine.bitnet University of Florida Gainesville, FL 32611 904/392 6365
tale@pawl.rpi.edu (David C Lawrence) (11/16/89)
In <786@orange19.qtp.ufl.edu> bernhold@qtp.ufl.edu (David E. Bernholdt) writes:
David> We are an nntp leaf node and we probably generate fewer than 10
David> articles per day locally. It seems like running nntplink would be
David> kind of overfill. It seems like we could achieve the *idea* of
David> nntplink by running nntpxmit "on demand" i.e. every time an article is
David> posted.
So, have inews do it. If you are running C News you could write it
into the inews shell script. Otherwise it just seems that having cron
check every fifteen minutes or so for a batch will have to do; for ten
articles a day from a leaf node that should be fine. As soon as it
hits the linkers it will be on hundreds if not thousands of sites
within the hour.
Dave
--
(setq mail '("tale@pawl.rpi.edu" "tale@ai.mit.edu" "tale@rpitsmts.bitnet"))