| |
VE4KLM > JNOS 07.06.21 02:12z 37 Lines 1238 Bytes #999 (0) @ WW
BID : A0I8P_VE4KLM
Read: GUEST
Subj: nntpserv stability fix
Path: SR1BSZ<EA2RCF<LU9DCE<KA1VSC<VE3CGR<W9GM<N2NOV<VE4KLM
Sent: 210607/0149z @:VE4KLM.#WPG.MB.CAN.NOAM [Winnipeg] $:A0I8P_VE4KLM
>From ve4klm%ve4klm.#wpg.mb.can.noam@n2nov.ampr.org Sun Jun 6 22:05:07 2021
Received: from n2nov.ampr.org by n2nov.ampr.org (JNOS2.0m.5G) with SMTP
id AA211500 ; Sun, 06 Jun 2021 22:05:07 EDT
Message-Id: <A0I8P_VE4KLM@VE4KLM.bbs>
>From: ve4klm@ve4klm.#wpg.mb.can.noam
X-JNOS-User-Port: Uplink (VE4KLM on port axipv) -> Sending message
A test file for anyone running NNTP services, look under rsync, new file :
nntpserv_stability_fix.c
Or grab it from www.langelaar.net/jnos2/nntpserv.c using wget :
wget www.langelaar.net/jnos2/nntpserv.c --no-check-certificates
Copy it to your nntpserv.c, and 'make' ..
Protects (from crashing) when nntpserv gets newnews, and there might
be questionable entries' in history file and / or remote group strings.
This 'should' also allow you to access as many groups from the remote
string as they can send (if that makes any sense). The limit was hardcoded
before and JNOS would crash if the remote sent too many of them. The hard
coded string length was just over 500 bytes. It's dynamic now, so no limit.
I'll move it over to nntpserv.c at some point, but if anyone wants to
test it.
Feel free to submit JNOS logfile entries if you see anything ...
Thanks.
Maiko / VE4KLM
Read previous mail | Read next mail
| |