Limiting INN's NNRP connections per IP
bill davidsen
davidsen at tmr.com
Mon Sep 2 16:38:51 UTC 2002
In article <20020830120522.GA27615 at fantomas.sk>,
Matus fantomas Uhlar <uhlar at fantomas.sk> wrote:
|
| -> > Hmmm if anyone would; However I had the idea having one innd/nnrpd
| -> > master-server, that would maintain databases (active, newsgroups,
| -> > history, overview) and nnrpd clients would only read it.
| ->
| -> I'm not sure what you mean here; if nnrpd inherits databases from innd,
| -> they'll be open read/write, which seems bad. Plus the innd access pattern
| -> is very different from the nnrpd access pattern.
|
| Of course, that is what I meaned "would be hard to do"... but at least
| sharing data between nnrpd's could spare much. Well that's just an idea. I'm
| sorry but i won't have time for doing it :(((
How about all processes have history open r/o, and send changes to an
updater via IPC? Sounds like step one to threading, or at least a way to
get another CPU to help accept incoming articles and do control stuff.
--
bill davidsen <davidsen at tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
More information about the inn-workers
mailing list