TZUTC: -0400   
   MSGID: 54160.sync@1:103/705 2c78dbb2   
   REPLY: 54155.sync@1:103/705 2c7725bc   
   PID: Synchronet 3.21a-Linux master/79f3aed0a Apr 28 2025 GCC 11.5.0   
   TID: SBBSecho 3.24-Linux master/273e9a093 Apr 28 2025 GCC 12.2.0   
   BBSID: TL-QWK   
   CHRS: CP437 2   
   NOTE: SlyEdit 1.89e (2025-02-09) (DCT style)   
     Re: paging sysop   
     By: Digital Man to Amessyroom on Tue Apr 29 2025 11:36 am   
      
    DM> Re: paging sysop   
    DM> By: Amessyroom to All on Mon Apr 28 2025 11:37 pm   
      
    >> Has there been any changes to bbs.page_sysop   
      
    >> Paging Amessyroom...   
    >> !ERROR opening /sbbs/exec/jsexec.js   
    >> The sysop has been notified.   
    >> [Hit a key]   
      
    >> User  reported it not working, and when trying to recreate noticed   
    >> the above error.   
      
    >> There is not a jsexec.js but a jsexec (executable) in /sbbs/exec.   
      
    >> Not sure if this is in js code for the command shell or c code.   
      
    >> Wondering if anybody else has encountered this. Redownloaded from git   
    >> and rebuilt tonight and the error continues.   
      
    DM> Check what you have configured in SCFG->Chat Features->External Sysop Chat   
    DM> Pagers. Sounds like you've added something there incorrectly. --   
    DM> digital man (rob)   
      
   Could be but even if I clear it and try and page I get the jsexec.js error   
   which I'm not referencing   
   directly.   
      
   [pager:0]   
           cmd=?postmsg.js -i/home/sbbs/page-message.txt -terrol  -   
   mobilenumber@att.net -fAmessyroomn "-sUser Paging You" mail   
           ars=   
           settings=0   
      
   Is what I've tried to add in chat.ini, but it seems when viewed or edited in   
   scfg it is truncated.   
      
   Where I sent an email to my cell #. This works manually if you do jsexec   
   postmsg.js ....    
      
   But like I said, if there is nothing defined in chat.ini or SCFG options for   
   external pager; selecting page still  gets   
   error in classic synchronet command shell and my customized one.   
      
   So there still seems to be something that is triggering the call to jsexec.js   
   which doesn't exist.   
      
   So still at a loss of how to correct the issue.   
      
   error.log shows:   
   term Node 1  !ERROR 2 (No such file or directory) in exec.cpp   
   line 588 (js_execfile) opening "/sbbs/exec/jsexec.js" access=0    
      
   term Node 2  !ERROR 2 (No such file or directory) in exec.cpp line 588   
   (js_execfile) opening "/sbbs/exec/jsexec.js" access=0    
   ---      
   Amessyroom   
   toolazy.synchro.net:2323 (telnet)   
   ---   
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323   
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)   
   SEEN-BY: 10/0 1 102/401 103/1 17 705 105/81 106/201 124/5016 128/187   
   SEEN-BY: 153/7715 154/110 218/0 1 215 601 700 840 860 880 226/30 227/114   
   SEEN-BY: 229/110 114 206 317 400 426 428 470 550 700 705 266/512 280/464   
   SEEN-BY: 291/111 301/1 320/219 322/757 342/200 396/45 460/58 633/280   
   SEEN-BY: 712/848 902/26 5075/35   
   PATH: 103/705 218/700 229/426