TZUTC: -0600   
   MSGID: 2154.sync_sys@723:1/0 2b956fc9   
   REPLY: 56739.sync_sys@1:103/705 2b963663   
   PID: Synchronet 3.20a-Linux master/d9c5f963f Nov 03 202 GCC 14.2.1   
   TID: SBBSecho 3.21-Linux master/b8260ae62 Nov 08 2024 20:27 GCC 12.2.0   
   BBSID: PHARCYDE   
   CHRS: UTF-8 4   
   On Sat, Nov 09 2024 21:04:32 -0600, you wrote:   
      
   > Weird. You could try increasing the timeout values on this line in   
   > nntpservice.js and see if that makes any difference: cmdline =   
   > client.socket.recvline(/* maxlen: */1024, /* timeout: */(msgbase &&   
   > msgbase.is_open) ? 10 : 300);   
      
   What would be a good starting point?   
      
   > Those values are in seconds, so I'd be surprised if an NNTP client   
   > would send 'A' and then take more than 10 seconds to send the   
   > remaining characters of the command, but worth experimenting with.   
      
   Agreed. I watched the logs while I clicked the subject. It was all    
   logged immediately, not even close to 10 seconds later.   
      
   > A network packet capture (e.g. with Wireshark) could also help tell   
   > what's happening there exactly.   
      
   I have no experience with that kind of stuff. Maybe  nelgin would    
   want to take a crack at it? *nudges nelgin :)   
      
   Regards,   
   Nick   
      
   ... Take my advice, I don't use it anyway.   
   ---   
    ￭ Synchronet ￭ _thePharcyde telnet://bbs.pharcyde.org (Wisconsin)   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 90/1 103/705 105/81 106/201 124/5016 128/187 153/757 7715   
   SEEN-BY: 154/10 30 203/0 218/700 221/0 226/30 227/114 229/110 114   
   SEEN-BY: 229/206 317 400 426 428 470 550 700 705 240/1120 5832 266/512   
   SEEN-BY: 280/464 5003 5006 282/1038 291/111 292/8125 301/1 320/219   
   SEEN-BY: 322/757 341/66 234 342/200 396/45 423/120 460/58 256 1124   
   SEEN-BY: 467/888 633/280 712/848 770/1 5020/400 8912 5054/30 5075/35   
   PATH: 103/705 280/464 460/58 229/426