1. Forum
  2. Newsgroups
  3. alt.bbs.synchronet

  • paging sysop

    From Amessyroom@amessyroom@TL-QWK.remove-c57-this to Digital Man on Fri May 2 19:37:17 2025
    From Newsgroup: alt.bbs.synchronet

    To: Digital Man
    Re: paging sysop
    By: Digital Man to Amessyroom on Wed Apr 30 2025 06:48 pm

    You have something trying to execute "?jsexec" - whether that's your custom shell or your configured chat pager, I can't know because I can't see your files. Do some searching through your config files (e.g. ctrl/*.ini) and JS files (e.g. mods/*.js) for "?jsexec" and fix that where you find it. This is something that you did/configured, not a Synchronet issue.

    Finally figured out I had to stop and start sbbs to get the modified
    chat.ini loaded; to read the cleaned value.

    I was expecting logging out and back in would pick up the change, but
    was wrong.

    I see you have updated wiki on quoting stuff also; I'll review that.
    as I don't why ?postmsg.js would cause issue -- unless it was quoting.

    I have successfully setup a python script to be called by
    JavaScript, so I can have username and node # in a sysop page.
    ---
    Amessyroom
    toolazy.synchro.net:2323 (telnet)
    ---
    þ Synchronet þ Too Lazy BBS - toolazy.synchro.net:2323
    --- Synchronet 3.21a-Linux NewsLink 1.2
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.20c-Linux NewsLink 1.2
  • From Digital Man@digital.man@vert.synchro.net.remove-omf-this to Amessyroom on Fri May 2 18:56:57 2025
    From Newsgroup: alt.bbs.synchronet

    To: Amessyroom
    Re: paging sysop
    By: Amessyroom to Digital Man on Fri May 02 2025 07:37 pm

    Re: paging sysop
    By: Digital Man to Amessyroom on Wed Apr 30 2025 06:48 pm

    You have something trying to execute "?jsexec" - whether that's your custom shell or your configured chat pager, I can't know because I can't see your files. Do some searching through your config files (e.g. ctrl/*.ini) and JS files (e.g. mods/*.js) for "?jsexec" and fix that where you find it. This is something that you did/configured, not a Synchronet issue.

    Finally figured out I had to stop and start sbbs to get the modified chat.ini loaded; to read the cleaned value.

    You don't (normally) need to stop and restart sbbs to reload .ini files. When saving changes in SCFG, it automatically flags the sbbs instance to recycle (reload config changes and restart servers and services).

    I was expecting logging out and back in would pick up the change, but
    was wrong.

    Only if the node has been flagged for recycle (as is done by SCFG) or a specific set of config files are hand-edited. Hand-editing chat.ini won't cause an automatic recycle.

    I see you have updated wiki on quoting stuff also; I'll review that.
    as I don't why ?postmsg.js would cause issue -- unless it was quoting.

    Are you talking about the string literals in .ini files? I don't think that has anything to do with your reported "?jsexec" error.

    I have successfully setup a python script to be called by
    JavaScript, so I can have username and node # in a sysop page.

    That shouldn't be necessary. You can directly execute the python script from SBBS and pass the username and node number on the command-line to the python script:
    https://wiki.synchro.net/config:cmdline
    --
    digital man (rob)

    This Is Spinal Tap quote #22:
    David St. Hubbins: Here lies David St. Hubbins... and why not?
    Norco, CA WX: 67.4øF, 63.0% humidity, 8 mph W wind, 0.00 inches rain/24hrs
    --- Synchronet 3.21a-Linux NewsLink 1.2
    * Vertrauen - Riverside County, California - telnet://vert.synchro.net
    --- Synchronet 3.20c-Linux NewsLink 1.2