TZUTC: -0700   
   MSGID: 54850.sync@1:103/705 2d27d98d   
   REPLY: 73947.sync@723:320/1 2d27db13   
   PID: Synchronet 3.21a-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0   
   TID: SBBSecho 3.29-Linux master/7acaccaf1 Sep 08 2025 GCC 12.2.0   
   COLS: 80   
   BBSID: VERT   
   CHRS: CP437 2   
   FORMAT: flowed   
   NOTE: FSEditor.js v1.105   
     Re: sbbsecho issue   
     By: Dumas Walker to DIGITAL MAN on Wed Sep 10 2025 08:59 am   
      
    > >  > Node (618:250/1.9) externally locked via:   
    > >  > /sbbs/fido/out.26a/00fa0001.pnt/00000009.bsy (since ??:??)   
    >   
    > > That same message would have been written to the sbbsecho.log file. The   
    > > lock attempt is retried (after the configurable number of BSO lock delay   
    > > seconds) and gives up (and logs a warning about "Giving up") after the   
    > > configured numbe   
    > > of BSO lock attempts. All of these messages would be written to your   
    > > sbbsecho.log file as well as the console. The only reason they would not   
    > > be written to the log file is if you had your "Log Level" set to something   
    > > less (more severe) than "Informational" in echocfg->Global Settings.   
    >   
    > It is set to "Warning".  Is that more or less severe than "Informational"?   
      
   A warning is more severe than informational and that means that Info-level   
   messages would *not* be written to the sbbsecho.log. I recommend you change   
   that back to the default (info) or if/when you're having issues, you change it   
   to Debug.   
      
    > The attempts were set at 60 so I lowered it.  What happens when it "gives   
    > up"?   
      
   It logs a warning ("Giving up after n attempts to lock node x") and continues   
   on doing whatever else it can do.   
      
    > Regardless they were *not* written to the console.   
      
   Right, because you changed the log level.   
      
    > They were written in   
    > the terminal window when sbbsecho was run manually but, in normal   
    > operation, they do *not* show up on the sbbs console or in syslog.   
      
   Correct, because you changed the log level from info to warning which   
   instructed SBBSecho to only log warnings and errors to the sbbsecho.log file.   
   SBBSecho is behaving exactly as designed and documented, it appears to me.   
   --    
                                               digital man (rob)   
      
   Synchronet/BBS Terminology Definition #54:   
   MUD = Multi-User Dungeon   
   Norco, CA WX: 75.3øF, 55.0% humidity, 0 mph SSW wind, 0.00 inches rain/24hrs   
   --- SBBSecho 3.29-Linux   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 1/19 16/0 19/37 40 103/705 105/81 106/201 123/130 128/187   
   SEEN-BY: 129/14 142/104 153/7715 154/10 110 203/0 218/700 221/1 6   
   SEEN-BY: 221/242 226/30 227/114 229/110 206 317 400 426 428 470 700   
   SEEN-BY: 229/705 240/1120 5832 266/512 280/464 5003 291/111 301/1   
   SEEN-BY: 301/113 320/119 219 319 2119 322/757 762 326/101 341/66 342/200   
   SEEN-BY: 396/45 423/81 460/58 633/280 712/848 902/26 5020/1042 5075/35   
   PATH: 103/705 301/1 221/1 320/219 229/426