• tickitcfg

    From Alterego@1:103/705 to Digital Man on Friday, August 30, 2019 11:11:02
    So I was running tickitcfg today - and I couldnt get out of it.

    When I choose "ESC" to exit, regardless of whether I answered yes or no to write the INI file, it kept taking me to the menu.

    So I killed it and lunched it with STDERR going to a file, this is what was in it (of interest):

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    Re-running: tickitcfg
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Why was it "re-running"?

    I lunched it with "jsexec -l tickitcfg 2> /tmp/z"

    BTW: I also manually ran jsexec -l tickit to process some inbound tic files (and some that couldnt be processed because the error didnt exist) - and it was
    stuck in a loop of processing the same two files over and over again - I think related :)


    ...ëîå*

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Alterego on Thursday, August 29, 2019 18:43:57
    Re: tickitcfg
    By: Alterego to Digital Man on Fri Aug 30 2019 11:11 am

    So I was running tickitcfg today - and I couldnt get out of it.

    When I choose "ESC" to exit, regardless of whether I answered yes or no to write the INI file, it kept taking me to the menu.

    So I killed it and lunched it with STDERR going to a file, this is what was in it (of interest):

    JavaScript: Destroying context
    JavaScript: Destroying runtime

    Re-running: tickitcfg
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes
    JavaScript: Initializing context (stack: 16384 bytes)

    Why was it "re-running"?

    I lunched it with "jsexec -l tickitcfg 2> /tmp/z"

    BTW: I also manually ran jsexec -l tickit to process some inbound tic files (and some that couldnt be processed because the error didnt exist) - and it was stuck in a loop of processing the same two files over and over again - I think related :)

    Why are you using -l?

    -l loop until intentionally terminated

    Maybe you wanted to use some other option?

    digital man

    Synchronet/BBS Terminology Definition #61:
    SEXPOTS = Synchronet External Plain Old Telephone System (POTS) service
    Norco, CA WX: 84.8øF, 53.0% humidity, 13 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Alterego@1:103/705 to Digital Man on Friday, August 30, 2019 12:46:24
    Re: tickitcfg
    By: Digital Man to Alterego on Thu Aug 29 2019 06:43 pm

    Why are you using -l?

    Ahh crap, sorry, my bad.

    I use -l <ftn address> with binkit sometimes, and I guess it got into my history.

    (I knew it there was a simple reason....)

    <blush>
    ...ëîå*

    ... Menu: A list of dishes which the restaurant has just run out of.

    ---
    þ Synchronet þ Alterant | an SBBS in Docker on Pi!
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)
  • From Digital Man@1:103/705 to Alterego on Thursday, August 29, 2019 20:38:07
    Re: tickitcfg
    By: Alterego to Digital Man on Fri Aug 30 2019 12:46 pm

    Re: tickitcfg
    By: Digital Man to Alterego on Thu Aug 29 2019 06:43 pm

    Why are you using -l?

    Ahh crap, sorry, my bad.

    I use -l <ftn address> with binkit sometimes, and I guess it got into my history.

    (I knew it there was a simple reason....)

    Then *that* '-l' would need to follow the script name.

    digital man

    This Is Spinal Tap quote #19:
    Oh then, maybe it's not green. Anyway this is what I sleep in sometimes.
    Norco, CA WX: 78.0øF, 63.0% humidity, 5 mph E wind, 0.00 inches rain/24hrs
    --- SBBSecho 3.09-Linux
    * Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)