> by default NNTP service uses just one thread to manage
> the received articles each minute:
Correct. The entire NNTP package needs revamping, should there be people
who are interested in doing so.
--- Noel
-
To unsub
That was the problem... by default NNTP service uses just one thread to
manage the received articles each minute:
file://var/nntp/spool
1
1000
Changing the to 1000 for example, fixed the issue.
Re
Humm... I analized the config.xml file and I found:
file://var/nntp/spool
1
6
Could it be this parameter the problem? This means, NNTP Spool is
processed each minute. Right? I will play with this parameters
Hi, some weeks ago, I posted this comment/question about NNTP access to
James 2.2.0 but i didn't receive any comment/answer and it is extrange
because the delay to get the messages after they are posted is really
big (sometimes 20 seconds).
<<
Hi, I am doing more tests with James 2.2.0 using it
Hi, I am doing more tests with James 2.2.0 using its NNTP feature.
I have both: James and NNTP Client (Mozilla) phisically in the same box.
I send a message from Mozilla and... I have to wait an average of 8 to
20 seconds to see the message posted. Of course, I am refreshing my
client all the tim
