new nntpcache convert needs advice on unusual setup

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hi all...

due to a variety of reasons i've moved from a standard inn setup
to inn + nntpcache, but i'm stuck on how to solve a particular
requirement.

some background: we (rmit computer science) had a news server
which provides two local hierarchies (call them `staff' and
`rmit.cs.*'). `staff' is private to a couple of machines,
`rmit.cs.*' is available within the department, and also gets
exported to the rmit ITS news server (`upstream').

our news server generally had 2.5-3.0G of spool in use, but
the groups we cared about only occupied <100MB of that. this
struck me as an excess waste (99% of the resources consumed in
non-local news), and nntpcache looked like the ideal solution.

so, i'd like to be able to do something like this;
* run a private newsserver on newshost:120, that just serves staff and
  rmit.cs.*
* run nntpcache on newshost:119, talking to newshost:120 and upstream:119
* synchronise rmit.cs.* between newshost:120 and upstream:119

it's this last bit which i'm trying to work out the best way to do.
i don't think inn 2.0 will allow me to have a feed (e.g, via innfeed),
and in any case, if nntpcache can fudge it for me then that's
preferable.

any ideas/suggestions?

luke.

ps: sorry if this is incomprehensible; i've been banging my head
against inn for a few days now, and anything i can do to avoid
doing stuff with it (as opposed to say, in nntpcache :) is a
Good Thing.


[Index of Archives]     [Yosemite]     [Yosemite Campsites]     [Bugtraq]     [Linux]     [Trn]

Powered by Linux