• Bug?

    From Sean Dennis@1:18/200 to All on Mon Feb 14 08:14:05 2022
    Hello All,

    I recently discovered that for some reason, uncompressed mail packets are not being tossed in upon receipt and are instead being tossed in much later in queue. This does not seem to affect compressed mail packets. The mail IS tossing but very slowly. So I am going to set up a MBSE test system that is non-production and we're going to debug this. This is the same issue that popped up the last time with my using MBSE (and why, out of frustration, I switched back to my OS/2 set up). This time around I'm going to stick to MBSE and figure out why it's acting this way with uncompressed mail packets. I have two Fidonet links that use uncompressed packets and it's only the mail from these two links that are affected.

    -- Sean

    ... When my phone battery died, I was angry and needed to find an outlet.
    --- GoldED+/LNX 1.1.5-b20180707
    * Origin: Outpost BBS * Johnson City, TN (1:18/200)
  • From Vincent Coen@2:250/1 to Sean Dennis on Mon Feb 14 14:33:46 2022
    Hello Sean!

    Monday February 14 2022 08:14, you wrote to All:

    Hello All,

    I recently discovered that for some reason, uncompressed mail packets
    are not being tossed in upon receipt and are instead being tossed in
    much later in queue. This does not seem to affect compressed mail
    packets. The mail IS tossing but very slowly. So I am going to set
    up a MBSE test system that is non-production and we're going to debug
    this. This is the same issue that popped up the last time with my
    using MBSE (and why, out of frustration, I switched back to my OS/2
    set up). This time around I'm going to stick to MBSE and figure out
    why it's acting this way with uncompressed mail packets. I have two
    Fidonet links that use uncompressed packets and it's only the mail
    from these two links that are affected.

    I had this last month or so, Check in the system.log what processes are running around the same time that the packets arrive.

    I 'think' that it was to do with an instance of the tosser running when the packet arrives so they get ignored until the next time it runs.

    Of course my memory might be wrong :)

    It has not happened this month but was to do with running more than one instance of golded at the same time so when exiting it sets a semophore up while the other instance is still running.

    I am now trying to avoid having more than one instance of golded running.
    This was because I was responding within an area but needed to look at another message for details etc.

    Vincent

    --- Mageia Linux v8 X64/Mbse v1.0.7.24/GoldED+/LNX 1.1.5-b20180707
    * Origin: Air Applewood, The Linux Gateway to the UK & Eire (2:250/1)