On 2019 Apr 13 18:04:48, you wrote to me:

 >> the next step is triggering the FIDOIN event... you do have that one
 >> enabled scfg, right?

 DD> Yes, but how does it automatically kick off after the BINKPOLL event?

binkit.js automatically touches the /sbbs/data/fidoin.now semaphore...

 DD> Or should it automatically do so and it isn't because of an error?

it should be automatic, AFAIK... as for an error, you didn't show enough log
after the binkit process to be able to tell... it generally looks something
like this in my ubuntu syslog...

this one is from a delivery from another system... it came in via the BINKP
service... you can see the event manager note about FIDOIN and then another one
 for the BINKOUT event which then delivers the outbound mail and may pick up
waiting mail and trigger the sequence again...

===== snip =====

: srvc 0054 BINKP Received file: /sbbs/temp/b2953400.pkt (1.6KB)
: srvc 0054 BINKP Moving '/sbbs/temp/b2953400.pkt' to
'../fido/inbound/b2953400.pkt'.
: srvc 0054 BINKP service thread terminated (0 clients remain, 0 total, 950
served)
: evnt Semaphore signaled for Timed Event: FIDOIN
: evnt Running native timed event: FIDOIN
: evnt FIDOIN Executing external: /sbbs/exec/sbbsecho -ce
: evnt Timed event: FIDOIN returned 0
: evnt Semaphore signaled for Timed Event: BINKOUT
: evnt Running timed event: BINKOUT

===== snip =====

i've trimmed out the date and time stamps along with the system name and the
process name in an effort to shorten the lines enough so they don't wrap all to
 hell but i don't think it'll be enough unless you're reading on a terminal
wider than 90 characters...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... A woman without a man is like a garden without a fence.
---
 * Origin:  (1:3634/12.73)