MSGID: 2:280/464.47 61e998bc   
   REPLY: 1:3634/12.73 61e982b7   
   PID: JamNNTPd/Linux 1   
   CHRS: LATIN-1 2   
   TZUTC: 0100   
   TID: CrashMail II/Linux 1.7   
   mark wrote (2022-01-20):   
      
    ml> ahhh... if i'm reading the output of "ps aux" properly, there is a bit of   
    ml> a memory leak going on... perhaps the crashes i was able to trigger are   
    ml> the result of a combination of some memory leakage over a "long" running   
    ml> time coupled with changing a config or included file? i'll try to set   
    ml> something up to test this possibility further but i'm done manually   
    ml> beating on it by editing files for now ;)   
      
   IIRC the problem with non-standard ports in the nodelist / node line (e.g.   
   24555) was also not always and on every system reproducible. For reference:   
      
   https://github.com/pgul/binkd/issues/15   
      
   (There was more discussion somewhere else, but I cannot find it).   
      
   Interestingly I believe the commit bug also fixed another bug with the node   
   -pipe option as a side effect. Weird things happening seems to be not unusual   
   for binkd.   
      
   ---   
    * Origin: Birds aren't real (2:280/464.47)   
   SEEN-BY: 1/123 15/0 90/1 103/705 105/81 106/201 114/705 709 120/340   
   SEEN-BY: 123/120 131 124/5016 129/305 330 153/250 757 7715 154/10   
   SEEN-BY: 203/0 218/840 220/70 221/0 226/17 30 227/114 229/110 200   
   SEEN-BY: 229/307 317 424 426 550 664 700 240/5832 249/206 250/5 8   
   SEEN-BY: 266/512 267/800 280/464 5003 5555 282/1038 292/854 8125 298/25   
   SEEN-BY: 301/1 305/3 310/31 317/3 320/219 322/757 341/234 342/200   
   SEEN-BY: 396/45 423/120 460/58 633/280 712/848 770/1 100 340 772/210   
   SEEN-BY: 772/220 230 2452/250   
   PATH: 280/464 770/1 317/3 229/426