home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   JAMNNTPD      Support for the JAMNNTPD software client      2,630 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 1,399 of 2,630   
   mark lewis to Tommi Koivula   
   Response to the LIST command   
   09 Jul 16 08:21:31   
   
   On 07/09/2016 03:14 AM, Tommi Koivula -> Anton Shepelev wrote:   
    TK> On Fri, 8 Jul 2016 23:11:28 +0300 Anton Shepelev wrote:   
      
    AS>> Could  anybody  confirm  that JamNNTPd correctly handles the   
    AS>> LIST command?  According to RFC977 the newsgroups should  be   
    AS>> reported as   
    AS>>                       group last first p   
      
    TK> I believe you're right. Should be fixed here now.   
      
   i've made likely the same fix here...   
      
   void command_list(struct var *var)   
   {   
   [...]   
                if(matchgroup(var->postgroups,g-group))   
   -               sockprintf(var,"%s %lu %lu y" CRLF,g->tagname,min,max);   
   +               sockprintf(var,"%s %lu %lu y" CRLF,g->tagname,max,min);   
      
                else   
   -               sockprintf(var,"%s %lu %lu n" CRLF,g->tagname,min,max);   
   +               sockprintf(var,"%s %lu %lu n" CRLF,g->tagname,max,min);   
             }   
          }   
       }   
   [...]   
      
      
   i've also dressed the PID up a little more... i don't know why there's a   
   SERVER_VERSION and a SERVER_PIDVERSION other than to strip off the .00 from   
   v1.00, v2.00 and such... the 1.1 code should be flying the 1.1 version number   
   in the PID line... the 1.2 code should be flying the 1.2 version number in the   
   PID line...   
      
      
   question: instead of #define the SERVER_PIDVERSION number, why not create it   
   from the SERVER_VERSION number and strip the trailing zeros off? that way only   
   one version number needs to be incremented...   
      
   v0.1  -> PIDVERSION 0.1   
   v0.52 -> PIDVERSION 0.52   
   v1.00 -> PIDVERSION 1   
   v1.10 -> PIDVERSION 1.1   
   v1.15 -> PIDVERSION 1.15   
   v2.00 -> PIDVERSION 2   
      
      
   doing it in code will sure save the remembering to do it manually as well as   
   trying to remember the rules...   
      
   personally, i like my current 1.2m/wpusa where the m means modified and the   
   /wpusa shows that i modified it here ;)   
      
    * Origin: news://news.wpusa.dynip.com | acct req'd to post (1:3634/12)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca