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?
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....)
Sysop: | sneaky |
---|---|
Location: | Ashburton,NZ |
Users: | 31 |
Nodes: | 8 (0 / 8) |
Uptime: | 255:22:15 |
Calls: | 2,091 |
Calls today: | 2 |
Files: | 11,141 |
Messages: | 949,103 |