1. Forum
  2. DOVE-Net
  3. Synchronet Discussion

  • Binkit Issues

    From Dumas Walker@VERT/CAPCITY2 to All on Friday, August 29, 2025 13:33:05
    (1) if a node is set to BinkpPoll = false *but* the system has an outbox defined *and* sbbsecho or binkit has moved the packets for that node into said outbox, binkit will poll the node anyway.

    (a) I don't think it should be moving outbound mail packets into the outbox... I think that is normally only for "non-mail" files
    (b) regardless, if a node is set to BinkpPoll = false, binkit shouldn't be trying to connect to it.

    I use BinkpPoll = false when I have nodes that can call in fine but where the mailers don't answer incoming calls correctly, for example.

    (2) Don't know what is causing this one... will include output... but I have a node where my system tries sending a bunch of mail but where you can see only two packets are reported sent, and no errors except "We got an M_EOB, but there are still 1 files pending M_GOT" (which I thought could be ignored) are displayed:

    JSexec v3.21a-Linux master/123f2d28a - Execute Synchronet JavaScript Module Compiled Jul 12 2025 20:59 with GCC 12.2.0

    Loading configuration files from /home/bbs/ctrl
    JavaScript-C 1.8.5 2011-03-31
    JavaScript: Creating runtime: 8388608 bytes

    Reading script from /home/bbs/exec/binkit.js
    /home/bbs/exec/binkit.js compiled in 0.00 seconds
    BinkIT/2.41 invoked with options: -l 618:250/39
    Attempting poll for node 618:250/39@micronet
    JSBinkP/4 callout to 618:250/39@micronet started
    Connecting to 618:250/39@micronet at gcbbs.net:24554
    Peer version: Mystic/1.12A48
    Authentication successful: secure
    Sending file: /sbbs/fido/out.26a/0000ffda.TH0 (250.1KB)
    We got an M_EOB, but there are still 1 files pending M_GOT
    Sending file: /sbbs/fido/out.26a/0000ffda.FR0 (250.1KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SA0 (250.7KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SU0 (259.1KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.MO0 (252.6KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TU0 (257.9KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.WE0 (250.7KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TH1 (260.0KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.FR1 (250.6KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SA1 (263.0KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SU1 (274.5KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.MO1 (267.4KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TU1 (250.1KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.WE1 (275.6KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.FR2 (255.4KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SA2 (259.2KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.MO2 (281.2KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TU2 (269.3KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.WE2 (250.7KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TH2 (254.3KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SA3 (269.2KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SU2 (267.3KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.MO3 (257.7KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TH3 (252.6KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.FR3 (260.1KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SU3 (279.9KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TU3 (262.9KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.WE3 (281.3KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TH4 (213.7KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.FR4 (236.2KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SA4 (156.9KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.SU4 (69.5KB)
    Sent file: /sbbs/fido/out.26a/0000ffda.SU4 (69.5KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.MO4 (151.1KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.TU4 (95.6KB)
    Sending file: /sbbs/fido/out.26a/0000ffda.WE4 (68.5KB)
    Sent file: /sbbs/fido/out.26a/0000ffda.WE4 (68.5KB)
    /home/bbs/exec/binkit.js executed in 12.32 seconds

    FYI, all of the packets listed exist on this end. I am going to try this node with binkd and see what happens.

    (3) binkit is "hanging" sometimes when it hits a node it cannot connect to, maxing out a whole CPU until I force-stop the sbbs instance -- this is related to problem #1 and would probably be fixed if #1 was working right. That said, I remember asking for a fix a while back to have binkit time when it takes too long to connect, but that is not working in this case.

    Thanks!

    $$
    ---
    � Synchronet � CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP
  • From Digital Man@VERT to Dumas Walker on Friday, August 29, 2025 13:59:08
    Re: Binkit Issues
    By: Dumas Walker to All on Fri Aug 29 2025 01:33 pm

    BinkIt issues should be filed at https://gitlab.synchro.net/main/sbbs/-/issues

    The author (Deuce) doesn't read DOVE-Net, so isn't likely to see your listed issues, respond, or address them (if they are in fact issues) unless they're in GitLab or you reach out to him more directly.
    --
    digital man (rob)

    Synchronet/BBS Terminology Definition #27:
    DSZ = DOS Send ZMODEM (by Chuck Forsberg)
    Norco, CA WX: 93.5�F, 29.0% humidity, 3 mph W wind, 0.00 inches rain/24hrs
    ---
    � Synchronet � Vertrauen � Home of Synchronet � [vert/cvs/bbs].synchro.net
  • From Dumas Walker@VERT/CAPCITY2 to DIGITAL MAN on Saturday, August 30, 2025 09:45:43
    BinkIt issues should be filed at https://gitlab.synchro.net/main/sbbs/-/issues

    The author (Deuce) doesn't read DOVE-Net, so isn't likely to see your listed issues, respond, or address them (if they are in fact issues) unless they're i
    GitLab or you reach out to him more directly.

    It is an issue -- if you set something in a config file as "false" the
    software should not just turn around and do it anyway.


    * SLMR 2.1a * Beware programmers carrying screwdrivers.
    ---
    � Synchronet � CAPCITY2 * capcity2.synchro.net * Telnet/SSH:2022/Rlogin/HTTP