1. Forum
  2. FidoNet
  3. AFTERSHOCK

  • Capacity

    From John Dovey@4:920/1.1 to All on Sat Oct 1 03:26:00 2022
    Hi,
    Something to add to the lost to be looked at please.
    I was out of touch for a week so when I connected again there was a fairly large number of packets and messages. Aftershock froze halfway through processing them. I had to force quit the app and restart.

    Thanks
    John
    --- AfterShock/Android 1.6.8
    * Origin: Firecat Mobile (4:920/1.1)
  • From Benny Pedersen@2:230/0 to John Dovey on Sat Oct 1 13:01:24 2022
    Hello John!

    01 Oct 2022 03:26, John Dovey wrote to All:

    Something to add to the lost to be looked at please.
    I was out of touch for a week so when I connected again there was a fairly large number of packets and messages. Aftershock froze halfway through processing them. I had to force quit the app and restart.

    shit happens, possible fix is to not have compressed pkt files in inbound (nailbomp) so just recieve plain pkt files, and maybe fix to not be on vacation for so long could help aswell, but some of the problems is easy to fix, others needs app updates

    if all is well after restart what is in the debug logs if any ?


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.19.11-gentoo-dist (x86_64))
    * Origin: gopher://fido.junc.eu/ (2:230/0)
  • From Rudi Timmermans@2:292/140 to John Dovey on Sat Oct 1 19:52:04 2022
    Hi John,

    processing them. I had to force quit the app and restart.

    I hope soon Anatoly has free time to work on it, this is not the case yet...


    ---
    Best regards,
    Rudi Timmermans.
    --- AfterShock/Android 1.6.8
    * Origin: Light Station (2:292/140)
  • From Ward Dossche@2:292/854 to John Dovey on Sun Oct 2 12:01:26 2022
    Something to add to the lost to be looked at please.
    I was out of touch for a week so when I connected again there was a
    fairly large number of packets and messages. Aftershock froze halfway through processing them. I had to force quit the app and restart.

    This is historical. After the crash just restart and it picks-up where it stopped. Nothing's lost.

    I don't see the issue ...

    \%/@rd

    --- DB4 - 20220519
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)
  • From Benny Pedersen@2:230/0 to Ward Dossche on Mon Oct 3 21:03:36 2022
    Hello Ward!

    02 Oct 2022 12:01, Ward Dossche wrote to John Dovey:

    Something to add to the lost to be looked at please.
    I was out of touch for a week so when I connected again there was a
    fairly large number of packets and messages. Aftershock froze halfway
    through processing them. I had to force quit the app and restart.

    This is historical. After the crash just restart and it picks-up where
    it stopped. Nothing's lost.

    I don't see the issue ...

    did you notice 2:230/150 had out of space inbound storage for long time ?, i set him down in nodelist until it possible is resolved,

    in binkd.conf

    minfree <bytes> minimal free space so process all bundles is possible, think of zip mailbomp
    minfree-insecure <bytes> same for insecured connections, dont allow less then minfree here

    i dont belive any android devices have free spaces, no matter what device it is

    you see now ?


    Regards Benny

    ... too late to die young :)

    --- Msged/LNX 6.1.2 (Linux/5.19.12-gentoo-dist (x86_64))
    * Origin: gopher://fido.junc.eu/ (2:230/0)
  • From Ward Dossche@2:292/854 to Benny Pedersen on Tue Oct 4 11:56:44 2022
    did you notice 2:230/150 had out of space inbound storage for long time
    ?, i set him down in nodelist until it possible is resolved,

    The sysop of 2:230/150 qualifies as an act for Cirque du Soleil ...

    i dont belive any android devices have free spaces, no matter what device it is

    you see now ?

    Set the max limit of messages and problem solved ... been there, done that ..

    \%/@rd

    --- DB4 - 20220519
    * Origin: Many Glacier - Preserve / Protect / Conserve (2:292/854)