TZUTC: -0700   
   MSGID: 53817.sync@1:103/705 2c368836   
   REPLY: 53816.sync@1:103/705 2c368330   
   PID: Synchronet 3.20e-Linux master/cc717b402 Mar 08 2025 GCC 12.2.0   
   TID: SBBSecho 3.23-Linux master/cc717b402 Mar 08 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   NOTE: FSEditor.js v1.105   
     Re: Re: [wiki.synchro.net] page added: howto:freq   
     By: Gamgee to Digital Man on Tue Mar 11 2025 12:12 pm   
      
    >   Re: Re: [wiki.synchro.net] page added: howto:freq   
    >   By: Digital Man to Gamgee on Mon Mar 10 2025 08:42 pm   
    >   
    >  >  >  > Below is a log snip of what I see in sbbs.log when the FREQ comes   
    >  >  >  > in. The entries before and after this snip are just the session   
    >  >  >  > start/stop messages, no other useful information is seen.  I also   
    >  >  >  > snipped the timestamp at the beginning of each line for   
    >  >  >  > readability:   
    >   
    >  >  >  > srvc 0013 BINKP Receiving file: /sbbs/temp/00870073.req (0.0KB)   
    >  >  >  > srvc 0013 BINKP Received file: /sbbs/temp/00870073.req (0.0KB)   
    >  >  >  > srvc 0013 BINKP Deleted file: /sbbs/temp/00870073.req   
    >  >  >  > srvc 0013 BINKP Receiving file: /sbbs/temp/nfx4kkji.req (0.0KB)   
    >  >  >  > srvc 0013 BINKP Received file: /sbbs/temp/nfx4kkji.req (0.0KB)   
    >  >  >  > srvc 0013 BINKP Deleted file: /sbbs/temp/nfx4kkji.req   
    >   
    >  >  > Digital Man, any more thoughts on this?   
    >   
    >  > Nope. I start added some log() statements to binkit.js to find out what's   
    >  > happening.   
    >   
    > Do you mean you are going to add some log statements, or that I should do   
    > that? Because... I don't know how to do that.   
      
   You would edit the file binkit.js and add lines around the .req file handling,   
   for example:   
      
           if (fname.search(/\.req$/i) !== -1) {   
                   log("REQ file received, calling handle_freq");   
                   handle_freq(fname, bp);   
                   remove_file(fname);   
           }   
      
   Then when BinkIt receives a .req file, I'd expect to see that string in your   
   logs.   
      
    >  >  > It seems like BinkIT is not   
    >  >  > recognizing that there is an inbound ".req" netmail, and doesn't   
    >  >  > trigger the FreqIT function.   
    >   
    >  >  > I looked at freqit.js and see that it "loads" fidocfg.js and   
    >  >  > freqit_common.js. That second one requires filebase.js, and in that   
    >  >  > last one I see a comment reference regarding an "unnecessary shim for   
    >  >  > the new Filebase class".  Just a wild guess, but did the new 3.20   
    >  >  > filebase break something?   
    >   
    >  > Doubt it.   
    >   
    > Well, then a followup question would be:  Has FreqIT ever worked in the   
    > past?   
      
   I assume so, but I've never personally used it.   
      
    > I'm just now trying to get it working and don't know if it ever did   
    > before.   
    >   
    > Should I put in a Gitlab issue?  How can I fix this?  Thank you.   
      
   If you want to reach the author (Deuce) that's probably the best way, yes.   
   --    
                                               digital man (rob)   
      
   Rush quote #79:   
   His mind is not for rent to any god or government always hopeful yet discontent   
   Norco, CA WX: 57.6øF, 62.0% humidity, 3 mph WNW wind, 0.03 inches rain/24hrs   
   --- SBBSecho 3.23-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 4/0 88/0 90/0 93/1 103/705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 153/757 7715 154/10 30 110 203/0 218/700 221/0 6 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 550 700 705 240/1120   
   SEEN-BY: 240/5832 266/512 280/464 5003 5006 291/111 292/8125 301/1   
   SEEN-BY: 310/31 320/219 322/757 341/66 200 234 342/200 396/45 423/120   
   SEEN-BY: 460/58 467/888 633/280 712/848 770/1 900/0 102 106 902/0   
   SEEN-BY: 902/19 26 905/0 5019/40 5020/400 5075/35   
   PATH: 103/705 280/464 341/66 902/26 229/426